Online BootLoader method, no need to use C2000hex to get flash program data
[Copy link]
I have been studying DSP online BootLoader recently. I found that the .out file generated by CCS compilation cannot directly generate hex files and bin files. After searching, I learned that I can use the C2000hex tool to convert the .out file to a .hex file, and use the hex file for BootLoader, but I still think hex files are troublesome because hex files are codes represented in ASCII form. Algorithms are also needed for conversion. Through trial and actual operation, I found that when simulating the application, CCS->Tools->SaveMemery can be used to export and store the current flash content into a file, and this file is the same as the bin file. The configuration of SaveMemery is as follows:
One more thing to say here is that for a highly efficient BootLoader, that is, not to write a large piece of useless "0xFFFF", then you need to choose a suitable length in Save Memery, and do not read out invalid memery. However, if the Begin of the program is very far away from the address of the program, for example, my own experimental plan is to put the BootLoader program at 0x300000----0x30FFFF, Begin is 0x30FFF6; the application program is just at 0x310000----0x33FFFF, Begin is 0x33FFF6; from the simulation point of view, my program only occupies 0x310000 to 0x312c71. If the Memery is fully exported from 0x310000----0x33FFFF, then several times more invalid memery will be written. At this time, you can choose to only export the memory from 0x310000 to 0x312c71, or make it a slightly larger integer, and then read out 0x33FFF6 of Begin again and only write this address.
After actual operation and comparison with document analysis, there are no problems.
|