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: Program DCSM Zx LINKPOINTER

Part Number: TMS320F280049


Hi champs,

In general, we leave the highest 3-bit to zero when programming OTP LINKPOINTER. For example, we program data 0x1FFFFFFE into OTP LINKPOINTER.

My customer told me that he could program LINKPOINTER by using Flash API and data 0xFFFFFFFE before, but now he fails to program LINKPOINTER with that data value, is it possible? He is now wondering maybe we have new revision of F280049 devices recently and cause this difference, as I know, we don't have new revision of silicon, do we?

Regards,

Luke

  • Hi Luke,

    Programming LINKPOINTER by using Flash API with the upper 3 bits as 1 was never possible on any of the F280049 devices. As you can see, these are OTP (One Time Programmable) locations. Hence cannot be erased once programmed.

    Thanks & Regards
    Pramod

  • Pramod,

    I meant my customer programs LINKPOINTER by using Flash API and data 0xFFFFFFFE, and then he checks the LINKPOINTER content is 0x1FFFFFFF, means that he fails to program this LINKPOINTER.

    But he insists that he could program LINKPOINTER with data 0xFFFFFFFE without problem before, means that the LINKPOINTER content was 0x1FFFFFFE, is it possible?

    Regards,

    Luke

  • Hi Luke,

    The programming of LINKPOINTER to 0xFFFFFFFE isn't possible as the part will already be shipped from TI with the value of 0x1FFFFFFF. 

    But he insists that he could program LINKPOINTER with data 0xFFFFFFFE without problem before, means that the LINKPOINTER content was 0x1FFFFFFE, is it possible?

    This means that the bits which are already 0 need to to go back to 1's (bits 31:29). This is and has not been possible ever for TMS320F280049 as these are OTP locations and TI ships the parts after zeroing the 3 MSB bits. 

    Hope this is clear.

    Thanks & Regards

    Pramod

  • Pramod,

    My customer told me he used 0xFFFFFFFE to program LINKPOINTER before, and he could program the LSB of LINKPOINTER from 1 to 0 without problem, means that the content of LINKPOINTER is 0x1FFFFFFE.

    However, if he uses 0xFFFFFFFE to program LINKPOINTER now, then the content of LINKPOINTER will be 0x1FFFFFFF, means that he fails to program the LSB of LINKPOINTER, he is wondering what cause this difference and asks for an answer, do we have a silicon revision?

    This question is about LSB of LINKPOINTER, not MSB 3 bits, hope this is clear.

    Regards,

    Luke

  • Hi Luke,

    I understood that the concern is with the LSB. However, what the customer is trying isn't possible as the MSBs has already been zeroed out. The Flash tool will see that the MSB's which are already zero are being attempted to be made 1 which is a violation and therefore throws an error.

    My customer told me he used 0xFFFFFFFE to program LINKPOINTER before, and he could program the LSB of LINKPOINTER from 1 to 0 without problem, means that the content of LINKPOINTER is 0x1FFFFFFE.

    As per this, the customer is trying to program the LSB's understood. But for the programming to succeed, the MSB's which are already 0 has to be taken care of.

    he is wondering what cause this difference and asks for an answer, do we have a silicon revision?

    As I have mentioned before, there is no silicon revision for the device which should cause this behavior to change.

    Having said this, Can you check with the customer if they happen to have the earlier silicon where they claim this was possible?

    Thanks & Regards
    Pramod