• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 270 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.

TMS570LS3137: regarding FEE_virtual sectors in FEE_EEPROM

surya gupta
Prodigy 70 points
Part Number: TMS570LS3137
Other Parts Discussed in Thread: HALCOGEN

Hello good morning.,

Iam working an application, so I need to store some values in the EEPROM memory locations of TMS570LS3137 i.e., Bank-7(64KB), Iam configuring the 4 physical sectors into 2 virtual sectors.,In configuration of virtual sector size, Iam unable to get want is meant by Fapi_FlashSectorType is it decides the size of the virtual sector? if it is how? and one more question

In tms570ls3137 we have 31 physical sectors for the total flash memory,but in the types.h Fapi_FlashSectorType are 64 ? why?

I need to use this feature(access eeprom) in top of my application,Is I need to call an interrupt for every write and read cycle?

iam new to the devolpment application.,

please give me some answers regarding above questions.,

thanks in advance.,

surya prakash gupta 

  • +1
    TI__Guru 69891 points

    Hi Surya,

    surya gupta said:
    Iam unable to get want is meant by Fapi_FlashSectorType is it decides the size of the virtual sector? if it is how?

    Fapi_FlashSectorType won't decides the virtual sector size, it is a enum type structure and which will give a value to the each physical sector of EEPROM.

    Example:

    Fapi_FlashSector0 with value 0, Fapi_FlashSector1 with value 1 and Fapi_FlashSector2 with value 2 etc...

     Actually, the actual virtual sector size would be decided by the Start Sector and End Sector values we are giving in the Fee_VirtualSectorConfiguration.

    For example, the above configuration indicates that virtual sector-1 will be start at physical sector-0 of Bank-7 and end at physical sector-0  of Bank-7 so that means one physical sector-0 of Bank-7 is used for virtual sector-1.

    Similarly virtual sector-2 will be start at physical sector-1 of Bank-7 and end at physical sector-1 of Bank-7 so that means one physical sector-1 of Bank-7 is used for virtual sector-2. and same thing applicable for other virtual sectors.

    These configurations can be easily change from HALCoGen

    Note: Fapi_FlashSectorType doesn't implies any size, the physical sector sizes are already fixed and given in TRM, so when we mention start and end sectors in above configurations then that many physical sectors will get assigned to the corresponding virtual sector.

    --

    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    TI__Guru 69891 points

    Hi Surya,

    surya gupta said:
    Iam unable to get want is meant by Fapi_FlashSectorType is it decides the size of the virtual sector? if it is how?

    Fapi_FlashSectorType won't decides the virtual sector size, it is a enum type structure and which will give a value to the each physical sector of EEPROM.

    Example:

    Fapi_FlashSector0 with value 0, Fapi_FlashSector1 with value 1 and Fapi_FlashSector2 with value 2 etc...

     Actually, the actual virtual sector size would be decided by the Start Sector and End Sector values we are giving in the Fee_VirtualSectorConfiguration.

    For example, the above configuration indicates that virtual sector-1 will be start at physical sector-0 of Bank-7 and end at physical sector-0  of Bank-7 so that means one physical sector-0 of Bank-7 is used for virtual sector-1.

    Similarly virtual sector-2 will be start at physical sector-1 of Bank-7 and end at physical sector-1 of Bank-7 so that means one physical sector-1 of Bank-7 is used for virtual sector-2. and same thing applicable for other virtual sectors.

    These configurations can be easily change from HALCoGen

    Note: Fapi_FlashSectorType doesn't implies any size, the physical sector sizes are already fixed and given in TRM, so when we mention start and end sectors in above configurations then that many physical sectors will get assigned to the corresponding virtual sector.

    surya gupta said:
    In tms570ls3137 we have 31 physical sectors for the total flash memory,but in the types.h Fapi_FlashSectorType are 64 ? why?

    This is because the F021 Flash API is common for all the hercules devices

    So, the configurations are given for maximum possibility. If you verify the max sectors possible in hercules devices would be 64 so the Fapi_FlashSectorType is given for 64, end of the day this is just enum type which implies numbers to the sectors, so there won't be any issue.

    surya gupta said:
    I need to use this feature(access eeprom) in top of my application,Is I need to call an interrupt for every write and read cycle?

    No need, you can also call them in polling mode as well. There is an example in HALCoGen for FEE(Flash Emulated EEPROM), please refer that example

    --

    Thanks & regards,
    Jagadish.

  • +1 in reply to jagadish gundavarapu
    Prodigy 70 points

    Dear Jagadish.,

    Thank you so much for your clear explanation regarding my issue., I clearly understand the issue., thank you so much 

  • 0 in reply to surya gupta
    TI__Guru 69891 points

    Hi Surya,

    My pleasure. Please click on resolve button to close the issue.

    --

    Thanks & Regards,
    Jagadish.