|ARM Technical Support Knowledge Articles|
Applies to: Evaluator-7T
It is possible for the end user to erase/reprogram the flash memory on the Evaluator-7T board by means of the flash-resident Boot Strap Loader (BSL) software, or with a JTAG debug interface unit such as Multi-ICE. It is therefore possible to inadvertantly erase a flash image which is still required.
If the BSL is intact, and a boot prompt can be seen on a serial terminal or terminal emulator, it may be possible to reprogram images such as Angel from the boot prompt. Refer to the Evaluator-7T User Guide for details.
The Samsung KS32C50100 microcontroller's memory map is highly configurable by writing to various system control registers. At reset, Evaluator-7T's flash memory appears at the reset vector (0x0) and both the microcontroller's internal SRAM and the Evaluator-7T's on-board SRAM are inaccessible.
Soon after reset, the BSL sets up the memory map to give access to all the memory devices on the Evaluator-7T board, and the microcontroller's internal SRAM.
If the BSL has been run, and it has configured the memory map, then it should be possible to run a flash programmer executable on the Evaulator-7T board using a JTAG debug solution such as Multi-ICE and ARM's AXD debugger. The flash programmer executable, flash_sst*.li' and the complete 512KB flash image 'efi0065*.bin' are provided on the CD which is supplied with the Evaluator-7T.
If the BSL has become corrupted or completely erased, the memory map will not be set up, and the board will be rendered inoperative. Since there is no RAM visible to the processor at this point, it is not possible to run a flash programming image from a debugger across the JTAG port. Thus, the memory map must first be manually configured by a JTAG debugger before a flash programmer can be downloaded and run on the system.
A readme file containing instructions for reprogramming the original flash image on an Evaluator-7T board, and all necessary image files are contained in the 81KB zipfile Eval7t_recover.zip.
You will need a Multi-ICE interface unit and either the ADW or AXD debugger to perform this procedure.
Article last edited on: 2008-09-09 15:47:33
Did you find this article helpful? Yes No
How can we improve this article?