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

TMS320F28P650SK: Sysconfig/DCSM programming error for 0-pin flash boot

Wayne Huang
Genius 17005 points

Part Number: TMS320F28P650SK
Other Parts Discussed in Thread: C2000WARE, SYSCONFIG, UNIFLASH

Hi champs,

 

I am asking this for our customer.

Environment:

CCS 12.8.1

C2000ware V6.0

Sysconfig V1.25

Uniflash 9.3.0

They use Sysconfig/DCSM to generate dcsm.asm/cmd files, and the setting is shown below.

image.png

 

image.png

 

However, they got errors below when programming on CCS 12.8.1 and Uniflash 9.3.0 even with a new device (new OTP for the first-time programming).

It seems there is something wrong when programming DCSM_OTP_Z1_LINKPOINTER where they don't touch in Sysconfig/DCSM.

They can run the programmed devices without issues.

But they are confused why there is such an error.

Is there anything wrong with our Sysconfig and/or CCS/Uniflash flash programming?

Would you please clarify it?

image.png

  • 0
    TI__Mastermind 18840 points

    Hi Wayne,

    Does the same error occur when you comment out the Z1OTP_JLM_ENABLE lines in dcsm.asm? You can copy dcsm.asm/dcsm.cmd over and remove the DCSM module in SysConfig so the files don't get overwritten.

    Can you also send a screenshot of values at address 0x78000 - 0x78020 in the CCS memory browser?

    Best,
    Matt

  • 0 in reply to Matt Kukucka
    TI__Genius 17005 points

    Hi Matt,

    Because this is for OTP, which the user may need to replace with a new device if there is anything wrong, is it possible that you can verify these first on the socket board on your side and confirm what to do to us?

    Besides, because these files are generated by Sysconfig, the user does not prefer to manually change them.

  • 0 in reply to Wayne Huang
    TI__Genius 17005 points

    Hi Matt,

    The user has verified this error does not occur if they comment out lines 11-13 below as you asked.

    This is the memory dump for 0x78000 - 0x78020.

    Would you please update/fix Sysconfig to generate the right codes accordingly?

  • +1 in reply to Wayne Huang
    TI__Mastermind 18840 points

    Hi Wayne,

    Thank you confirming that for me. Since all OTP locations except the link pointers and JLM_ENABLE locations being protected with ECC, there must be some unintended behavior when only JLM_ENABLE (and not the link pointer) is being programmed (even if with default values).

    Can you recommend the following workaround (verified on my setup Slight smile):

    1. Enable configuration of the ZONE1 LINKPOINTER + Zone-Select Block section
      1. Do NOT select "Update the LINKPOINTER" or change the current (default) LINKPOINTER value
    2. Disable "Program Zone-Select Block"

    This effectively uncomments only the link pointer configuration lines (with the default link pointer values). Thus, the ZSB, JLM_ENABLE, and link pointers won't be programmed and will unblock the customer's the original issue.

    Best,
    Matt