Generete HEX file from OUT file using Code Composer 3.3

Hi,

 You said that after upgrading to CCS 3.3 your .out is not working(Hex utility)....

 Do you mean your .out file was working with older versions of CCS.?? And you were able to burn the converted file from hex utility to EEProm and boot from it.??

Hi, That´s something like that. What happens is when I compile the same project in CCS 3.3, the out file is ok (I´m able to run it with a JTAG tool). But when I convert it to a hex file (using HEX55) and burn this converted file to EEPROM the boot doesn´t work.

I believe it is a worng project configuration. I check out all compile and link options in CCS 3.1 and CCS3.3 and they are the same.

Could you have any  idea what I could try out?

Hi Ana,

A lot of times the program will work with the emulator because of the initializations made in the GEL file. Take a look at the GEL file and see if it is initializing the PLL, EMIF. etc.... Than make sure that you make this initializations at the beginning of "main".

Hi Ana,

If your .out file is working correctly using JTAG and CCS, then your Build Options are ok.  Can you post your hex55 command line and/or .cmd file that drives the conversion of the .out file?  If it's not missing GEL configuration  as noted above, then this is the next point to look at.

Since you had boot working with CCS3.1 I assume you are confident that the flash programming is not a problem.  Is this correct?

Regards.

Hi Tommy,

the hex55 command line used is "hex55.exe -b -boot -serial8 final-5502", where final-5502 is my out file, and the file generated is "final-5502.b00".

I check the GEL configuration and they are the equal in CCS 3.1 and CCS 3.3.

I´m sure it isn´t a burn problem because I use the same programmer, memory and board to test.

Just to remember, I use an I2C EEPROM (24XX) to store my code and the board boots from it.

Thank for all reply, by now I couldn´t try it on CCS 4.0, and I don´t know if I will get the same issue.

Hi Ana,

Based on your last post, I have a couple of questions:
1. Are you using C5502 DSP?
2. Your memory is I2C EEPROM meaning connection to DSP is through I2C interface?
3. Are you using Boot Mode 110b on your board?
4. What version of Code Gen tools are you using in CCS3.3?

Have you looked at the App Note: Using the TMS320VC5501/C5502 Bootloader (http://www-s.t.com/sc/techlit/SPRA911)?  Section 2.6.5 contains details on using hex55 utility to create boot table for flash.  There are a couple of options suggested here that are not in your command line listed above: -v5510:2 (CPU version) and entry point (-e,entry point address>.  I also don't see the output format specification either.  Which are you using?

Regards.

Hi Tommy,

Some answers to your questions

1. Yes, I'm using C5502 DSP

2. Yes, the code is burned in a I2C EEPROM and it is read through I2C interface

3. Yes, one point that could guarantee there wans't a hardware problem because I tried the two out file - generated by CCS3.1 and CCS3.3 - into the same board, and the one genereted by CCS3.1 is ok and the other isn't

4. The hex tool version is 3.2.2

I will check the App Note you suggested hopping to get a new thing to try.

Regards

Hi Ana,

    It might be problem with the hex utility.. Use -v5502 option while converting form hex utility.. If the boot loader format is wrong then boot loader doesnt work.

   Try using new version of hex utility. New version avaialable is hex 4.4.0.

Regards,

JP

Hi  jayaprakash,

Do you know where i find the new version of hex55 utility to make download?

Thanks.

Hi Jose,

 I dont know the site where its available.

Give me e mail ID, i ill forward.