• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 83 subscribers
  • Views 801 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.

TMS320F280049: User-configurable DCSM OTP Bank0/1 locations value for blank device

Tomas Lehotsky
Intellectual 995 points
Part Number: TMS320F280049


Hello,

I am developing the code for blank check(or verify) of the flash memory locations of TMS320F280049 device. I am meeting with situation that blank device have non-blank values(other than 0xFFFF) on the DCSM OTP addresses. I am attached the readed value of DCSM OTP Bank 0 where you can see the readed value. 

the memory content of DCSM OTP flash:

My questions:

1. Why doesn't have the new device DCSM OTP flash addresses sets to 0xFFFF?

2. The flash API blank check function results in fail status because the values is not blank, thus how can I perform the initial blank check of the device(before programming), if the device is not blank?

3. Are the values, that you can see in the memory browser above, consider as the default values of the all TMS320F280049 device which will be manufactured in the future?

Thank you for your answers!

Best regards,

Tomas

  • 0
    TI__Guru** 115631 points

    Hi Tomas,

    1. Why doesn't have the new device DCSM OTP flash addresses sets to 0xFFFF?

    Security logic on new device has been changed which makes device BLOCK if passwords are ALL_1 hence one of password value in all zone select blocks are programmed such that ECC value is still ALL_1.

    2. The flash API blank check function results in fail status because the values is not blank, thus how can I perform the initial blank check of the device(before programming), if the device is not blank?

    You should not be doing blank check for the OTP location.

    3. Are the values, that you can see in the memory browser above, consider as the default values of the all TMS320F280049 device which will be manufactured in the future?

    Correct. Please refer the DCSM section in device TRM for the same.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Guru 14640 points
    I decided to look at the 0x78000 memory on my F280049 ControlCard, and I see that same pattern. (I fully expected to see FFFF's, because the OTP has not even attempted to be programmed.)

    However, on the F28379D ControlCard, the memory at 0x78000 (Also User OTP) is all FFFF's.
  • 0 in reply to Todd Anderson78572
    TI__Guru** 115631 points
    Todd,

    As I mentioned, security logic on new devices (F280049 onwards) has been changed. F2837xD device was released before F280049.

    Vivek Singh
  • 0 in reply to Vivek Singh
    Intellectual 995 points

    Hi Vivek,

    first of all, thank you for your answer. So, if the real situation with TMS320F280049 is that some locations in DCSM have from the manufacture non-blank values, I can consider this values as default "blank" values. My idea is, that I can test "before known values" with actual data in the DCSM flash of other TMS320F280049 device and compare it. If the values matches, I can say that the device is blank. Or not?

    Best regard,

    Tomas

  • 0 in reply to Tomas Lehotsky
    TI__Guru** 115631 points
    Tomas,

    Yes, you can do that. default values are provided in device TRM.

    Vivek Singh