In this manner, I can verify that the dump\convert was successful.
out file (as CCS does not allow selection of. I figured I would then go into CCS 5.5 and compare the. I programmed my target board with the generated hex file from the memory dump. But, I cannot see how to do this with the MSP430 & CCS 5.5. Have done this for years with different products, parts and tools. So, I program the boot, download the app using our field tool via serial port (as a field person would do), then dump the flash and give the file to manufacturing so they have a single step programming process. Also, some revision information gets put into some far off flash segments away from real code. The boot loader protects the vectors from being overwritten by the application. That is very plausible, believe me -)īasically, I have a boot loader. Why can't that be a preconfigured file type for saving memory? Maybe it is and I missed it. hex as a preconfigured step so this is obviously a common format. The compiler allows a post-build step to. They each have lines at the same address with different data. This produced two files with the extensions. Then I ran the hex430 utility with the -i option for Intel hex. I ran it with no options, which defaults it TI-hex. So, I went to the compiler directory and copied hex430 to the directory where I saved (dumped) memory to a.
dat with some variability on the formatting or. When I save memory, there are no options for standard programmer formats, Intel hex, S-rec, whatever. I need to save the memory from the MSP430 into a. Other Parts Discussed in Thread: UNIFLASH
0 kommentar(er)
