bdiGDB for GNU Debugger, BDI2000 | User Manual 34 |
3.2.4 Part [FLASH]
The Telnet interface supports programming and erasing of flash memories. The bdiGDB system has to know which type of flash is used, how the chip(s) are connected to the CPU and which sectors to erase in case the ERASE command is entered without any parameter.
CHIPTYPE type | This parameter defines the type of flash used. It is used to select the cor- | |||
| rect programming algorithm. |
| ||
| format | AM29F, AM29BX8, AM29BX16, I28BX8, I28BX16, | ||
|
| AT49, AT49X8, AT49X16, STRATAX8, STRATAX16, | ||
|
| MIRROR, MIRRORX8, MIRRORX16, | ||
|
| M58X32, AM29DX16, AM29DX32 | ||
| Example: | CHIPTYPE AM29F | ||
CHIPSIZE size | The size of one flash chip in bytes (e.g. AM29F010 = 0x20000). This value | |||
| is used to calculate the starting address of the current flash memory bank. | |||
| size | the size of one flash chip in bytes | ||
| Example: | CHIPSIZE | 0x80000 | |
BUSWIDTH width | Enter the width of the memory bus that leads to the flash chips. Do not en- | |||
| ter the width of the flash chip itself. The parameter CHIPTYPE carries the | |||
| information about the number of data lines connected to one flash chip. | |||
| For example, enter 16 if you are using two AM29F010 to build a 16bit flash | |||
| memory bank. |
|
|
|
| with | the width of the flash memory bus in bits (8 16 32) | ||
| Example: | BUSWIDTH | 16 | |
FILE filename | The default name of the file that is programmed into flash using the Telnet | |||
| ’prog’ command. This name is used to access the file via TFTP. If the file- | |||
| name starts with a $, this $ is replace with the path of the configuration file | |||
| name. This name may be overridden interactively at the Telnet interface. | |||
| filename | the filename including the full path or $ for relative path. | ||
| Example: | FILE | F:\gnu\arm\bootrom.hex | |
|
| FILE | $bootrom.hex | |
FORMAT format [offset] | The format of the file and an optional address offset. The optional param- | |||
| eter "offset" is added to any load address read from the program file. | |||
| format | SREC, BIN, AOUT, ELF or COFF | ||
| Example: | FORMAT SREC | ||
|
| FORMAT ELF 0x10000 | ||
WORKSPACE address | If a workspace is defined, the BDI uses a faster programming algorithm | |||
| that runs out of RAM on the target system. Otherwise, the algorithm is pro- | |||
| cessed within the BDI.The workspace is used for a 1kByte data buffer and | |||
| to store the algorithm code. There must be at least 2kBytes of RAM avail- | |||
| able for this purpose. |
|
| |
| address | the address of the RAM area | ||
| Example: | WORKSPACE 0x00000000 |
© Copyright | V 1.04 |