|
![]() Development Tools
![]() problem in banked code upgrade using command prompt based FlashUtilCL.exe
|
| next newest topic | next oldest topic |
| Author | Topic: problem in banked code upgrade using command prompt based FlashUtilCL.exe |
|
sdave New Member |
I wanted to upgrade the code space using FlashUtilCL.exe with DOS command prompt utility and JTAG. I have used code banking. please let us know the step by step by instruction to dump the code in device f130. I have followed the below steps but i could not get success in it. IP: Logged |
|
Tsuneo Member |
I suppose you are working on Keil. "1) converted mycode.omf into mycode.hex using OH51.exe" Which linker do you use? - OH51 hex converter doesn't support banked code. "Using OC51" for BL51 from Keil "2) FlashUtilCL.exe Download mycode.hex 1 0 0" FlashUtilCL.exe Download mycode.b00 1 0 0 Tsuneo IP: Logged |
|
Tsuneo Member |
Continued from another topic of the same title, "problem in banked code upgrade using command prompt based FlashUtilCL.exe"
Umm.. SRecord - win32 Then, the procedure is revised as follows. 1) OC51 - Convert original banked-omf file into separated-object files of each bank > OC51 mycode.omf mycode.B01, mycode.B02, mycode.B03 are generated. 2) OH51 - Convert each separated-object file to HEX file > OH51 mycode.B01 HEX (mycode_B01.hex) 3) Srecord - Split "common" part and banked part For Bank 0, For other banks, 4) FlashUtilCl - Write them to the FLASH > FlashUtilCL.exe Download mycode_B00.hex 1 0 0 Tsuneo IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() |
|
Have you seen our MCU Knowledge Base?