• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 416 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.

Compiler: simulation EEPROM Use question

runli du
Prodigy 30 points

Other Parts Discussed in Thread: TMS570LS0714, HALCOGEN

Tool/software: TI C/C++ Compiler

hello:

I used the official simulation EEPROM library on chip TMS570LS0714，I have encountered the following two：
1.The phenomenon of writing EEPROM has failed in a development board.Only one block will always fail to write，Other block writes are successful.
2.When the EEPROM is read and written all the time, the EEPROM content is cleared.Twice so far.The first problem is fixed after this issue occurs.
What are the possible reasons for these problems(No ECC errors are handled in the code)?
thank you very much.
  • 0
    TI__Mastermind 21425 points
    Hello,
    Are you using FEE Driver generated by HALCoGen?

    Best regards,
    Miro
  • 0 in reply to Miro
    Prodigy 30 points

    hello:

    Yes, I used it.

    I have a guess on this issue,If I use two FEE configurations, will it cause the above two problems?

    Best regards,
    runli

  • 0 in reply to runli du
    TI__Guru**** 200206 points

    Hi Runli,

    Can you please share your FEE configuration in HALCoGen (HALCoGen file *.hcg)? Do you use async write or sync write? If you use asyc write API, please don't do any other FEE write until the state machine become idle .

    I'd like to know:

    1. number of many virtual sectors

    2. number of physical flash sectors for each virtual sector

    3. number of data block, and size of the each data block

    Be aware of that the total size of your data block (plus the header) should be smaller than the size of the virtual sector.