• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 575 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.

CCS/TMS320F28335: The memory area of .cinit can not be properly loaded

ShawnYu
Intellectual 265 points
Part Number: TMS320F28335


Tool/software: Code Composer Studio

Hello,

When we use CCS8.3 to load program into 28335 chips, there's a chance about 1%-2% that the memory area which was allocated to .cinit is empty.

The associated memory allocation is shown below:

FLASHD : origin = 0x320000, length = 0x008000

.cinit : > FLASHD PAGE = 0
.switch : > FLASHD PAGE = 0
IQmathTablesRam : > FLASHD, PAGE = 0

I've checked all the abnormal chips, most of the memory including the .switch area and IQmathTablesRam area were loaded properly, only the .cint area was filled with 0xFFFF instead of the expected data.

We'vd tried different versions of CCS, but the problem was still there.

In addition, if I try to load the program a second time, the .cinit area can be written as normal.

I wonder if there are any configuration or program problems that are causing this phenomenon.

Regards.

  • 0
    TI__Guru* 87155 points

    Shawn,

    Thank you for brining this to our attention.  

    Are you using the same .out file in both failing and passing devices?  Any other differences between the two - power supply, emulator etc.?  

    Did you try erasing entire flash before loading?  

    Did you get any error when loading to flash?

    Did verify and checksum fail during load?

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Intellectual 265 points

    Thanks for your reply.

    To your questions:

    Q: Are you using the same .out file in both failing and passing devices? 

    A: Yes, the problem occured in our production process, the operators used the same .out file for continuous burning operations.

    Q: Any other differences between the two - power supply, emulator etc.?  

    A: We've checked the power supply and changed the emulator cable, but it didn't seem to work.

    Q: Did you try erasing entire flash before loading?  

    A: "Flash program setting" is "Erase, program, verify", and all the sectors are selected.

     

    Q: Did you get any error when loading to flash?

    A: The operators told me there were no pop-up dialogs or other obvious prompts, but maybe they've missed some imformation. 

    Q: Did verify and checksum fail during load?

    A: In the first two production assignments, the operators used the default verification option "Fast verification". After that, I asked them to use "Full verification", but still no useful information was obtained. 

  • 0 in reply to ShawnYu
    TI__Guru* 87155 points

    Shawn,

    Thank you.  If not a pop-up, please check if console window showed any error message.

    Verification and checksum should fail if this happens.

    Can you share your linker cmd file once?

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Guru* 87155 points

    Shawn,

    Thank you for sending the linker cmd file offline.  I don't see any issue with how the cinit is allocated in the linker cmd file.

    Can you check whether the checksum (available in CCS on-chip flash plugin GUI) matches in both failing and passing cases?  

    Also, please share your map file.

    Thanks and regards,
    Vamsi