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

TMS320F28379D: F2837xD Serial Flash problem

Sandy12108
Intellectual 345 points
Part Number: TMS320F28379D


Tool/software:

Hi,

I have a serial flash program that was developed in house that has been used to download multiple TI processors.  I have now added support for the F2837xD processor.  Serial flashing of application code works as long as the device is unlocked.  When adding security codes to the application and downloading to the device with JTAG, the serial flash program is unable to successfully unlock the device.  Below is the serial stream where it attempts to unlock the device.  I have commented out parts of the security code for obvious reasons, but I will leave a few values for you to compare to the values that were used in the code for locking the device.  Z2 is set to all 0xFF's and when it attempts to unlock it is successful.  I have tried swapping bytes, etc.  If you look at the serial stream, you will see that attempting to unlock Z1 results in 0x6000 which is an unlock error and that unlocking Z2 results in 0x1000 which is no error.   I would appreciate any suggestions on why I am receiving this error and/or how to trouble-shoot this error.  Thanks in advance!

Sandy 

This is from the program that is being downloaded, as I stated, Z2 is all FF's.

.long 0xA465xxxx    ;Z1-CSMPSWD0

.long 0xxxxxxxxx    ;Z1-CSMPSWD1

.long 0x7B46xxxx   ;Z1-CSMPSWD2

.long 0xxxxxxx9D   ;Z1-CSMPSWD3

[11/02/2025 14:25:30] Written data (COM7)
e4 1b 10 00 0a 00 a4 65 xx xx xx xx xx xx 7b 46
xx xx xx xx xx 9d 07 07 1b e4
[11/02/2025 14:25:30] Read data (COM7)
2d e4
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
1b
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
0c
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
0a
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
60
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
78
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
56
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
34
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
12
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
00
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
7e
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
01
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
1b
[11/02/2025 14:25:30] Written data (COM7)
2d
[11/02/2025 14:25:30] Read data (COM7)
e4
[11/02/2025 14:25:30] Written data (COM7)
2d 2d
[11/02/2025 14:25:34] Written data (COM7)
e4 1b 10 00 0b 00 ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff fb 0f 1b e4
[11/02/2025 14:25:34] Read data (COM7)
2d e4
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
1b
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
0c
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
00
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
0b
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
00
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
00
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
10
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
78
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
56
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
34
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
12
[11/02/2025 14:25:34] Written data (COM7)
2d
[11/02/2025 14:25:34] Read data (COM7)
00

  • 0
    TI__Mastermind 28220 points

    Hi Sandy,

    The OTP structure (including the location of the CSM passwords) varies between different TI processors. Which TI processor were you using previously? Did you make any updates to your serial flash programmer to account for the change?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Intellectual 345 points

    Hi Luke,

    Thank you for your response.

    I am using the Serial Flash Programming of C2000 Microcontrollers as a guide for downloading to the TMS320F28379D processor.  The flash kernel API that is downloaded initially as part of the process is unique to the 28379D processor and is based on examples from TI.  Other TI processor(s) that are supported have their own unique flash kernel API that is downloaded first.  If the location is incorrect then why does the Unlock CPU1-Zone 2 with a password of all 0xFF's return a NO_ERROR result?

    Thank you in advance!

    Sandy

  • 0 in reply to Sandy12108
    TI__Mastermind 28220 points

    Did you modify any part of the serial flash programmer to specify your custom CSM passwords? Did you secure the flash via the GRABSECT registers or configure the boot mode select pins to use flash boot?

    Thank you,

    Luke

  • +1 in reply to Luke Jones
    Intellectual 345 points

    Luke,

    I found the problem, the flash API modules were not correctly processing the passwords; once that was corrected, the module unlocks.

    Thank you,

    Sandy