• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 525 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Message Log Prints

Justin Antony G
Intellectual 775 points

Hi,

Sometimes i observer some invalid prints in the DSP/BIOS message log window of CCS:

 

97413   *** ERROR: 0xfefd1409 0xfefd1409 *** 

100221   *** ERROR: 0xff16fef8 0xff16fef8 ***

16253176   *** ERROR: 0xea15f0fa 0xea15f0fa ***

16286072   *** ERROR: 0xf602f9ec 0xf602f9ec ***

24970100   *** ERROR: 0x1d0000f4 0x1d0000f4 ***

25329019   *** ERROR: 0x4011010 0x4011010 ***

25919356   *** ERROR: 0xf6fceef3 0xf6fceef3 ***

33064185   *** ERROR: 0xe08f506 0xe08f506 ***

42596728   *** ERROR: 0x60103f8 0x60103f8 ***

 

I use SYS_Error() in my code at few places.

I'm using CCS version: 3.3.82.13 , cgtools: 6.1.19 and DSP/BIOS: 5.33.04.

This is observed from the DSP L2 memory dump taken from field. Most of the time the prints in "Message Log" are valid. When i see the above mentioned prints i also observe that the DSP L2 Memory dump is not proper. So do the prints mean the DSP-Dump is corrupted?

Regards,

Justin

  • 0
    TI__Mastermind 32475 points

    Justin,

    If the const strings for the Message Logs are placed in memory that is corrupted, then the prints themselves will be corrupted.  There is also the Log buffer and the RTA buffer that is sent to the Host which could be corrupted.  The Message Log strings are placed in the .const section.  One suggestion would be to try to place this section in a memory segment that you know won't get corrupted.  If that doesn't solve the problem then I would suggest you do the same for the Log buffer and then the RTA buffer.

    Judah