Tool/software:
Hello,
I have programmed a custom bootloader and tested it as follows.
Loaded two apps via debugger into the respective sectors in the flash. I start these without any problems via the bootloader.
Now i generate an intel hexfile of the applications using the c2000 hex utility and programm them via flashapi.
However, these do not run.
Have compared the loaded application debbuger vs the loaded application via flashapi. there are some differences via memory dump (picture).
Picture: left side loaded via debugger vs. right side programmed via flash api
What I have already checked:
- i compared .hex file output vs. flash memory that was programmed via flashapi
What could be the problem that the software cannot start after programming via Flashapi? What could be the reason for the memory section having this difference?
Output build:
Building secondary target: "A50P002A02_CPU1.hex"
Invoking: C2000 Hex Utility
"C:/ti/ccs1250/ccs/tools/compiler/ti-cgt-c2000_22.6.1.LTS/bin/hex2000" --memwidth=16 --romwidth=16 --diag_wrap=off --intel -o "A50P002A02_CPU1.hex" "A50P002A02_CPU1.out"
Translating to Intel format...
"A50P002A02_CPU1.out" codestart ==> codestart
"A50P002A02_CPU1.out" .switch ==> .switch
"A50P002A02_CPU1.out" .init_array ==> .init_array
"A50P002A02_CPU1.out" .cinit ==> .cinit
"A50P002A02_CPU1.out" .text.1 ==> .text.1
"A50P002A02_CPU1.out" .text.2 ==> .text.2
"A50P002A02_CPU1.out" .TI.ramfunc ==> .TI.ramfunc
"A50P002A02_CPU1.out" .const ==> .const
Finished building secondary target: "A50P002A02_CPU1.hex"
Best regards,
Daniel
