Problems with IOS in f283335 hex file

Alex Yakovenko

Other Parts Discussed in Thread: UNIFLASH

1) When you build the project in CCS set generation *.hex file of the firmware.
2) Until a time (until the project became big) *.hex file through a third-party boot loader C2Prog.
3) After the project became more (as far as I know didn't catch this moment) *.hex file is sutured to the controller, but the controller after a reset to start the program refuses. (tried to mark all 8-nil sectors in memory manual for firmware)
4) Starting proximally UniFlash slipping him the firmware file but in a format *.out all stitched and the controller normally starts after reset.

Has anyone faced such a problem? May C2prog there is a limit in the free version the size of drilled or hex file in CCS are not always correctly compiled?

over 8 years ago

0 stevenh over 8 years ago

Guru 19935 points

Hello Alex,

According to www.codeskin.com/programmer, there isn't any size limitation to C2Prog.

Are you sure the *.out file is the same code and/or compiled the same way (same options) as the *.hex file?

Stephen

0 Alex Yakovenko over 8 years ago in reply to stevenh

Intellectual 290 points

Yes, the project settings remained from the time when he was smaller, and *.hex file stitched and worked (setting there one to compile *.hex in CCS v5).

0 stevenh over 8 years ago in reply to Alex Yakovenko

Guru 19935 points

Are you saying the hex file now works? If not, convert the out file to a hex file and compare the converted file to the original hex file.

0 Alex Yakovenko over 8 years ago

Intellectual 290 points

found what was wrong, incorrectly generated hex in CCS, it was broadcast in hex to configure it according to spru513h. The link helped.

C2000™︎ microcontrollers

C2000 microcontrollers forum

Problems with IOS in f283335 hex file