This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I'm trying to generate TI TXT files for BSL loading. I've done this successfully with previous projects. In a project that I inherited, the tool insists on generating a file with the .hex extension even though it is configured for TI TXT. This .hex file appears to have the same format as a TI TXT file, but it causes the 'Python Firmware Upgrader' to crash. Can anyone explain why it does this?
One of my original projects generates this output:
**** Build of configuration Debug for project msp430-hid-fifo ****
"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Invoking: MSP430 Hex Utility'
"C:/ti/ccsv6/tools/compiler/ti-cgt-msp430_4.4.5/bin/hex430" --memwidth=8 --romwidth=8 --ti_txt -o "msp430-hid-fifo.txt" "msp430-hid-fifo.out"
Translating to TI-TXT format...
The inherited project generates this output with the same Hex Utility settings:
**** Build of configuration test2 for project USB2ANY ****
"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Invoking: MSP430 Hex Utility'
"C:/ti/ccsv6/tools/compiler/ti-cgt-msp430_4.4.5/bin/hex430" --memwidth=8 --romwidth=8 --ti_txt -o "USB2ANY.hex" "USB2ANY.out"
Translating to TI-TXT format...
Thanks,
Ren
Hi Ren!
I remember getting a .hex file instead of a .txt file from earlier days. And the program for flashing the file did not accept it. I simply renamed the extension from .hex to .txt and everything was fine. Did you try this already?
Dennis
**Attention** This is a public forum