| |||
| Home > Programming Flash with RealView Debugger > Troubleshooting | |||
If you are having problems programming an image to Flash, check the following:
Does the BCD file correctly describe the Flash memory area for your board, and does it specify the correct FME file?
Does your target connection have the correct BCD file assigned to it?
Is the icon for the Flash area in the Map tab green, and are the Flash memory locations in the Memory pane 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 this is not, then:address
Display the Project Properties for the project that you are using to build the Flash image.
Change the value for the linker setting BUILD.Link_advanced.Ro_base to
a valid value.
Rebuild the FME file.
If you built the image using the compilation tools directly,
see the --ro_base linker option in the RealView
Developer Kit v2.2 Linker and Utilities Guide.
Does your Flash image have the same endianness as the FME file?
Build your Flash image
and FME file with the correct endianness. Set either the Compilation.Endianness setting
for the ARM compiler or Assembly.Endianness setting
for the ARM assembler in the Project Properties.
To check the endianness of the FME file, use the dispflash command.
If you built the image using the compilation tools
directly, see the --littleend or --bigend options
in RealView Developer Kit v2.2 Compiler and Libraries
Guide or in RealView Developer Kit v2.2 Assembler
Guide.
Make sure that your target hardware and connection configurations 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?