• State Resolved
  • Locked Locked
  • Replies 20 replies
  • Subscribers 84 subscribers
  • Views 820 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F2800137: How to burning the OTP and Flash content with UNIFLASH?

Shaoxing Ke
Expert 3590 points
Part Number: TMS320F2800137
Other Parts Discussed in Thread: UNIFLASH

Hi Experts,

I am asking for my customer here.

Customer has the two project here, one is second bootloader with DCSM, another is Customer's APP. And DCSM with all Secure RAM and Flash on the F2800137 Chip. So, they download the .out files with twice.

And then they using the UniFlash to read the User OTP and Flash Content to convert to single file here, you can refer to the below figure.

At last, we use the convert to single file to program burning the new devices# f2800137 by UniFlash, it not work and reports the below error.

Do you have any suggestion? How to combine two .out files and complete the burning with DCSM? Thanks.

ERROR:

(ERRORI C28xx_CPU1: Trouble Removing Breakpoint with the Aation"Remain Halted" at ox8422: (Error -1066 @ 0x8422) Unable to set/clear requested breakpoint- Verify that the
breakpoint address is in valid memory. (Emulation package 9.8.0.00235).

(ERROR] C28x_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x8422: (Error -1066 @ 0×8422) Unable to set/clear requested breakpoint. Verify that the breakpoin address is in valid memory. (Emulation package 9.8.0.00235)

 [WARNING] C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

[ERROR] C28×x_CPU1: Error during Flash programming (Flash algorithm returned error code 0x00000009, FMSTAT (STATCMD on some devices) 0×00000000). Operation cancelled.

(ERRORI c28xx_CPU1: File Loader: Memory write failed: Unknown error
 (ERROR] C28×x_CPU1:Trouble Setting Breakpoint with the Action "Remain Halted" at 0x8058: (Error -1066 @ 0×8058) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.8.0.00235)

  • 0
    TI__Guru* 87105 points

    Hi Shaoxing,

    Saw your offline message to me on this.

    If not the combined file, are they able to load the separately downloaded files successfully?  First the flash app and then the DCSM file?  That helps to know if it is because of combining them Or due to some other issue.

    Thanks and regards,

    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Expert 3590 points

    Hi Vamsi,

    We load the separately downloaded files successfully, but the combined file will fail by UniFlash. 

    Due to customer using UniFlash on the Production line Programming. They need to use UniFlash to Programming the combined out. file. So please see the where the error is? Thanks.

  • 0 in reply to Shaoxing Ke
    TI__Guru* 87105 points

    Hi Shaoxing,

    Thank you for confirming that the customer is able to program using the individual downloaded files (from Uniflash), but not the combined files.  This tells me that this may not be a flash programming issue; but might be related to the combined file.  Before we conclude that for further investigation, let us do one more thing.

    Can you generate debug server log and the verbose output and share with us?

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Expert 3590 points

    Hi Vamsi,

    Sure. You can also refer to the above log I have attached figure. Please help to see flash programming issue where it is. Thanks.

  • 0 in reply to Shaoxing Ke
    TI__Expert 3590 points

    Hi Vamsi,

    I let customer try programming the combined files(Read by UniFlash) to chip by CCS, it was successful.

    But we load the combined files by UniFlash, it failed and report the below ERROR:

    (ERRORI C28xx_CPU1: Trouble Removing Breakpoint with the Aation"Remain Halted" at ox8422: (Error -1066 @ 0x8422) Unable to set/clear requested breakpoint- Verify that the
    breakpoint address is in valid memory. (Emulation package 9.8.0.00235).

    (ERROR] C28x_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x8422: (Error -1066 @ 0×8422) Unable to set/clear requested breakpoint. Verify that the breakpoin address is in valid memory. (Emulation package 9.8.0.00235)

     [WARNING] C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    [ERROR] C28×x_CPU1: Error during Flash programming (Flash algorithm returned error code 0x00000009, FMSTAT (STATCMD on some devices) 0×00000000). Operation cancelled.

    (ERRORI c28xx_CPU1: File Loader: Memory write failed: Unknown error
     (ERROR] C28×x_CPU1:Trouble Setting Breakpoint with the Action "Remain Halted" at 0x8058: (Error -1066 @ 0×8058) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.8.0.00235).

  • 0 in reply to Shaoxing Ke
    TI__Expert 3590 points

    Hi Vamsi,

    We also check the Operation failed chip Flash and OTP content, and OTP has content, Flash is empty. Could you help look into on this case? Thanks.

  • 0 in reply to Shaoxing Ke
    TI__Guru* 87105 points

    Hi Shaoxing,

    Please confirm if my understanding is correct or not: CCS is able to load the combined file that you downloaded from the Uniflash.  But, Uniflash is failing - when you give the combined file, Uniflash is programming the DCSM OTP and then it is failing - correct?  

    Are the boot-mode pins configured for wait-boot?

    Thanks and regards,

    Vamsi

  • 0 in reply to Shaoxing Ke
    TI__Guru**** 450031 points
    Shaoxing Ke said:
    I let customer try programming the combined files(Read by UniFlash) to chip by CCS, it was successful.

    Can you provide this combined file? You can send via private E2E message if you do not wish to share publicly.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Expert 3590 points

    Hi Ki,

    I have sent to the email to you. Thanks.

  • 0 in reply to Vamsi Gudivada
    TI__Expert 3590 points

    Hi Vamsi,

    The combined file is read by UniFlash, which includes OTP and Flash content.

    #1. We use the combined file to programming the new chip F2800137 by CCS, it is succeed. 

    #2. And then we use the combined file to programming the another new chip F2800137 by UniFlash, it is failed. Am I clear? Thanks.

  • 0 in reply to Shaoxing Ke
    TI__Guru* 87105 points

    Hi Shaoxing,

    Yes, it is clear.  Ki will help you further on this issue.

    Thanks and regards,

    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Guru**** 450031 points

    Hi Shaoxing,

    I got your message. Let us continue discussion in the existing e-mail thread.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Expert 3590 points

    Hi Ki,

    Any updates from your side here?

  • 0 in reply to Shaoxing Ke
    TI__Guru**** 450031 points

    Yes, please see Vamsi's last e-mail regarding the DSCM OTP fields.

  • 0 in reply to Ki
    TI__Expert 3590 points

    Hi Ki.

    Please focus on the question: why UniFlash failed the first time programming on new chip here? Am I clear?

  • 0 in reply to Shaoxing Ke
    TI__Guru**** 450031 points
    Shaoxing Ke said:
    Please focus on the question: why UniFlash failed the first time programming on new chip here? Am I clear?

    Yes it is clear. However, I will need to unlock my device before I can try to reproduce the issue with UniFlash. Let us continue discussion on the e-mail thread.

  • 0 in reply to Ki
    TI__Expert 3590 points

    Hi Ki,

    Please use another new chip to reproduce the issue with UniFlash. Thanks a lot!

  • 0 in reply to Shaoxing Ke
    TI__Expert 3590 points

    Hi Ki,

    This issues has been going on for ten days, could you please look into this? why UniFlash failed the first time programming on new chip here? 

  • 0 in reply to Shaoxing Ke
    TI__Expert 3590 points

    Hi Experts,

    Very thanks for your help.

    Could you guarantee that there will be no same issue with UniFlash8.3 later?

  • +1 in reply to Shaoxing Ke
    TI__Guru**** 450031 points
    Shaoxing Ke said:
    Very thanks for your help.

    Is the issue now resolved?

    Shaoxing Ke said:
    Could you guarantee that there will be no same issue with UniFlash8.3 later?

    The workaround that Luke described was involves functionality that came after UniFlash 8.0 but before UniFlash 8.3. Hence it is in UniFlash 8.3 and will remain so in future UniFlash versions.

    For others following the thread, the issue is with changing the security settings (passwords) with older versions of the tools. The issue arises due to a change in security architecture and when the security setting is read, it gets loaded so a new password takes effect and the device gets locked. To fix this, a change was made in API to not do verification for security settings. This fix has been implemented in current CCS and UniFlash versions.