| |||
| Home > Programming Flash with RealView Debugger > Troubleshooting | |||
If you are having problems programming an image to Flash, check the following:
Does the board/chip definition correctly describe the Flash memory area for your board, and does it specify the correct FME file?
Does your Debug Configuration have the correct board/chip definition assigned to it?
Is the icon for the Flash area in the Memory Map tab green, and are the Flash memory locations in the Memory view shown with a yellow background?
This indicates that the Flash_type setting
does not point to a valid FME file, or is not set.
Is the image you are loading a valid Flash image?
Use the dispflash utility to display information about the FME file, and examine the following line:
Routine Code PC-rel. Can load at address
The must
be a valid RAM area on your board. If it is not, then rebuild the
FME file with the address--ro_base linker
option.address
Does your Flash image have the same endianness as the FME file?
To check the endianness of the FME file, use the dispflash command described in .
Rebuild the image using the compiler and assembler
options --littleend or --bigend as
appropriate.
Make sure that your targets and Debug Configuration have the correct endianness assigned.
If you have created your own FME file:
Have you correctly specified the Flash and board settings in the AME files?
Are your Flash algorithms correct?
See also:
Creating algorithms for a Flash type supported by RealView Debugger
Creating algorithms for a Flash type not provided with RealView Debugger
Assigning your board/chip definitions to a Debug Configuration
ARM® Compiler toolchain Using the Assembler
ARM® Compiler toolchain Assembler Reference
ARM® Compiler toolchain Using the Compiler
ARM® Compiler toolchain Compiler Reference
ARM® Compiler toolchain Using the Linker
ARM® Compiler toolchain Linker Reference.