TMS320C5535: Program works when flashed from debugger, but not when flashed from an EEPROM

Tsvetolin ,

I had done as you suggested. I complied my code in release mode (Optimization level = 2) and changed the blink rate of the LED from 1 second to 2 seconds.

Unfortunately, the same issue persists.  When the c5535 is flashed using the XDS110 debugger the LED successfully blinks every 2 seconds indefinitely. When the c5535 boots from the I2C EEPROM, the LED blinks only 4 times (every 2 seconds) and then stops blinking.

When I reverted back to the code where the LED blinks every second and compiled it in release mode, the only noticeable difference is that the LED blinks correctly 8 times (as opposed to 3 times in the original post) before the LED stops blinking.

What troubleshooting step would you suggest next?

Best, 

Eddie

Tsvetolin, 

Unfortunately I have not been able to find the solution for this problem. The EEPROM I'm using is 512kb and the .bin files is only 58kb, so it's not an issue with the .bin size. 

I have found that modifying the .cmd file changes the behavior of the LED blinking, so perhaps the problem is how the memory is being allocated in the DSP? 

This .cmd file causes the LED to stop blinking after 8 times: Stops Blinking.zip

I changed the .cmd in this file and now the LED doesn't blink at all: Doesnt Blink at All.zip

I have included the .cmd, .hex, .bin, and .map file for you to review in each zip folder. 

I would also like to point out that when I flash using the XDS110 debugger, both the .cmd files above causes the LED to blink as expected (1 second intervals indefinitely). The LED only stops blinking when the c5535 boots from the EEPROM. 

Best, 

Eddie

Michail and Tsvetolin, 

Thank you for your investigative work.

Within the actual program itself, I'm able to successfully initialize ESBR, GPIO, GPT, and the interrupts. Isn't it enough for the registers to be initialized within the program itself, or is it mandatory for the boot loader to initialize those peripherals? 

I'm willing to give this solution a try but I have never used the register configuration feature before and would probably cause the bootloader to fail if I tried. Could you provide a reference or step-by-step guide for how to do this?    

Best, 

Eddie

Michail,

Here are the zip files with the .out files added:

8780.Stops Blinking.zip

1565.Doesnt Blink at All.zip

Just a friendly reminder that the only difference between these two files is the .cmd file. 

Best, 

Eddie

Michail, 

The settings I used can be seen below:

I did my best to follow the recommended commands from SPRABL7D

Best, 

Eddie

Michail,

I believe that I am already driving the XDS110 without a .GEL file, but please tell me if I'm wrong:

Best, 

Eddie

Hi Eddie and minkyo seo,

so when you have the same problem can we compare some details to triage the case:

- are you using custom boards or dev ones

- what is the main clock frequency of your C5535

- what type of EEPROM is connected; it can be of type 24xx with array from 8kBytes to 64kBytes and must accept 400kHz clock

Please let's clarify both of your configurations

Thanks,

Michail

Michail, 

For my application, the C5535 is on a custom board. The clock frequency of my processor is 100MHz running at 1.3V. 

I have verified that the EEPROM I'm using meets specs, but you can go ahead and see the EEPROM I'm using for yourself. The voltage I'm driving the EEPROM at is 3.3V, which also meets specs.

Best, 

Eddie

Hi

In my case, if I put long long code, It doesn't boot well.

but if I change long long to Int32, It works well.

I need to use long long code. why does problem occure with long long ?

please give me details. Thanks

and I attached part of my code. please check

/////////////////// global var 
// if i change long long to Int32, it works, but I need to use long long
long long anfdsum1d=0;
long long anfdsum2d=0;
long long dc0[32];
long long dc1[32];
long long dc2[32];
long long dc3[32];
long long dc4[32];
long long dsum[32];
long long temp_out;




for(i=0; i<32; i++)
{

   dc0[i] = Right_TempBuf[i] * nAnfcoef[0]; 
	dc0[i] = dc0[i]>>11;           

   dc1[i] = anfdsum1d * -nAnfcoef[2];
   dc1[i] = dc1[i]>>13;


   dc2[i] = anfdsum2d * -nAnfcoef[3]; 
   dc2[i] = dc2[i] >> 13;



   dc3[i] = anfdsum1d * nAnfcoef[5]; 
   dc3[i] = dc3[i] >> 13;

   dc4[i] = anfdsum2d * nAnfcoef[6]; 
   dc4[i] = dc4[i] >> 13;

   dsum[i] = dc0[i] + dc1[i]; 
   dsum[i] = dsum[i] + dc2[i]; 
   dsum[i] = dsum[i]*nAnfcoef[1];
   dsum[i] = dsum[i]>>13;

   temp_out = dsum[i]*nAnfcoef[4]; 
   temp_out = temp_out>>13;
   temp_out = temp_out + dc3[i]; 
   temp_out = temp_out +dc4[i];;
   temp_out = temp_out>>2;

   notch_out_sig2[i] = (LDATA)(temp_out<<16);
   notch_out_sig[i] = temp_out;

   anfdsum2d = anfdsum1d; 
   anfdsum1d = dsum[i]; 


}

Minkyo Seo,

According to the following post:

https://e2e.ti.com/support/processors/f/791/t/768697?tisearch=e2e-sitesearch&keymatch=64%20bit%20c5000

the C55X compiler does not support 64 bit data types. Unfortunately, the absolute max is 40 bits, so you'll have to restraint your program according to that limitation. 

Best, 

Eddie