AWR2944: Chip Activation Issue About ErrorCode 07

Part Number: AWR2944

Tool/software:

Hello Experts

   we use AWR2944BS chips in our vehicle radar, in order to meet customers' demands, we need to active these chips before programming by Xmodem protocal.

But with the mass production, we often come across a problem that the UART often record a errorcode 07 during the period of activation 

  I did an investigation about this errorcode, for the details as below:

Next is the sequences of DC POWER ON:

1. DC power supplied 12V for radar PCBA

2. delay 500ms 

3. DC power supplied 1.7V for activation circuit (spec ±0.05V)

4. delay 1000ms

5. Datas transfer by Xmodem protocol 

6. 1.7V power off

7. delay 1500ms

8. 12V power off 

I also used the oscilloscope to probe for the 1.7V signal, for the details as below:

For the errorcode records, details as below:

  C
# Key programming sequence initiated

# Waiting for x509 CustCertificate ...

# IPC message for CustCertificate received

#
# Decrypting extensions..
#

 * MPK Options: 0x0

 * MEK Options: 0x0

 * MPK Opt P1 : 0x0

 * MPK Opt P2 : 0x0

 * MEK Opt    : 0x0

* SMPKH Part 1 BCH code: 0x20f65682

* SMPKH Part 2 BCH code: 0x000f704c

* SMPK Hash (part-1,2):

0xce0c44734447afec12ba0b2226c3bdbc15576d212323ece46a9c4ccd6a463e4100

0x7086083fee572a09a9496dbed447a9f13f9cf535fad75b18e0ee095a4e783c6200

* SMEK Hash: 0x716ded828b2731a19c961aa866ca07fcb99603d52ea1b3fa9d5b23c19e99c60a2ca76a82e34fa0a12cfc4d7cc5352bb0ec74e313ddd42edfda52832055b662bf

* BMPKH Part 1 BCH code: 0x4006cd64

* BMPKH Part 2 BCH code: 0x806234dd

* BMPK Hash (part-1,2):

0xc090ae52abdb03fee89446518eb34f23c971fe29c0094e52d0a4f303fc8d7c7500

0x6ae38cc1830a7aa8bd5abc2901d76bf7f7780544543f136eb6b67069af7d1bf100

* BMEK Hash: 0x83b1b25a53f4863a27d4e2ddc496771d31a3b131bc74b959eecc3475900ff19ac82c062da18e8cb0b646219b379d987392b3df7919c666fd3fa14952552e699e

EXT OTP extension disabled

MSV extension disabled



[u32] key_cnt : 0x303


[u32] key_REV : 0x101

* SWREV_SBL: 0x0000000100000001


* SWREV_HSM: 0x0000000100000001


* SWREV_APP: 0x000000000000000000000001000000000000000000000001

* KEYWR VERSION: 0x200001

#
# Programming Keys..
#


* MSV and MSV_BCH:

[u32]  MSV:0x0

[u32]  MSV+BCH:0x0
MSV extension disabled
MSV_BCH extension disabled

[u32]  MSV:0x0

[u32]  MSV+BCH:0x0


* SWREV SBL:
bl: 1, r: 1 d: 0x0
bl: 1, r: 2 d: 0x0
Programmed 2/2 rows successfully
bl: 1, r: 1 d: 0x1
bl: 1, r: 2 d: 0x1


* SWREV HSMRT:
bl: 1, r: 3 d: 0x0
bl: 1, r: 4 d: 0x0
Programmed 2/2 rows successfully
bl: 1, r: 3 d: 0x1
bl: 1, r: 4 d: 0x1


* SWREV APP:
bl: 1, r: 5 d: 0x0
bl: 1, r: 6 d: 0x0
bl: 1, r: 7 d: 0x0
bl: 1, r: 8 d: 0x0
bl: 1, r: 9 d: 0x0
bl: 1, r: 10 d: 0x0
Programmed 6/6 rows successfully
bl: 1, r: 5 d: 0x0
bl: 1, r: 6 d: 0x0
bl: 1, r: 7 d: 0x1
bl: 1, r: 8 d: 0x0
bl: 1, r: 9 d: 0x0
bl: 1, r: 10 d: 0x1

* EXT OTP:
EXT OTP extension disabled


* BMPKH, BMEK:
Programmed 8/8 rows successfully
Programmed 1/1 rows successfully


Programmed 8/8 rows successfully
Programmed 1/1 rows successfully
Programmed 8/8 rows successfully
Programmed 1/1 rows successfully


* SMPKH, SMEK:

Programmed 8/8 rows successfully
Programmed 1/1 rows successfully


Programmed 8/8 rows successfully
Programmed 1/1 rows successfully
Programmed 8/8 rows successfully
Programmed 1/1 rows successfully


* KEYCNT:
[u32] keycnt: 0x0
Programmed 1/1 rows successfully
[u32] keycnt: 0x303


* KEYREV:
[u32] keyrev: 0x0
Programmed 1/1 rows successfully
[u32] keyrev: 0x101

# Cust_Keys programmed successfully
  C
# Key programming sequence initiated

# Waiting for x509 CustCertificate ...

# IPC message for CustCertificate received

#
# Decrypting extensions..
#

 * MPK Options: 0x0

 * MEK Options: 0x0

 * MPK Opt P1 : 0x0

 * MPK Opt P2 : 0x0

 * MEK Opt    : 0x0

* SMPKH Part 1 BCH code: 0x20f65682

* SMPKH Part 2 BCH code: 0x000f704c

* SMPK Hash (part-1,2):

0xce0c44734447afec12ba0b2226c3bdbc15576d212323ece46a9c4ccd6a463e4100

0x7086083fee572a09a9496dbed447a9f13f9cf535fad75b18e0ee095a4e783c6200

* SMEK Hash: 0x716ded828b2731a19c961aa866ca07fcb99603d52ea1b3fa9d5b23c19e99c60a2ca76a82e34fa0a12cfc4d7cc5352bb0ec74e313ddd42edfda52832055b662bf

* BMPKH Part 1 BCH code: 0x4006cd64

* BMPKH Part 2 BCH code: 0x806234dd

* BMPK Hash (part-1,2):

0xc090ae52abdb03fee89446518eb34f23c971fe29c0094e52d0a4f303fc8d7c7500

0x6ae38cc1830a7aa8bd5abc2901d76bf7f7780544543f136eb6b67069af7d1bf100

* BMEK Hash: 0x83b1b25a53f4863a27d4e2ddc496771d31a3b131bc74b959eecc3475900ff19ac82c062da18e8cb0b646219b379d987392b3df7919c666fd3fa14952552e699e

EXT OTP extension disabled

MSV extension disabled



[u32] key_cnt : 0x303


[u32] key_REV : 0x101

* SWREV_SBL: 0x0000000100000001


* SWREV_HSM: 0x0000000100000001


* SWREV_APP: 0x000000000000000000000001000000000000000000000001

* KEYWR VERSION: 0x200001

#
# Programming Keys..
#


* MSV and MSV_BCH:

[u32]  MSV:0x0

[u32]  MSV+BCH:0x0
MSV extension disabled
MSV_BCH extension disabled

[u32]  MSV:0x0

[u32]  MSV+BCH:0x0


* SWREV SBL:
bl: 1, r: 1 d: 0x0
bl: 1, r: 2 d: 0x0
Writing to efuse row failed!
Error Status Code: 7
Error in programming SWREV
debug_response: 0x4000000
bl: 1, r: 1 d: 0x0
bl: 1, r: 2 d: 0x0


* SWREV HSMRT:
bl: 1, r: 3 d: 0x0
bl: 1, r: 4 d: 0x0
Writing to efuse row failed!
Error Status Code: 7
Error in programming SWREV
debug_response: 0x4000000
bl: 1, r: 3 d: 0x0
bl: 1, r: 4 d: 0x0


* SWREV APP:
bl: 1, r: 5 d: 0x0
bl: 1, r: 6 d: 0x0
bl: 1, r: 7 d: 0x0
bl: 1, r: 8 d: 0x0
bl: 1, r: 9 d: 0x0
bl: 1, r: 10 d: 0x0
Writing to efuse row failed!
Error Status Code: 7
Error in programming SWREV APP REV
debug_response: 0xC000000
bl: 1, r: 5 d: 0x0
bl: 1, r: 6 d: 0x0
bl: 1, r: 7 d: 0x0
bl: 1, r: 8 d: 0x0
bl: 1, r: 9 d: 0x0
bl: 1, r: 10 d: 0x0

* EXT OTP:
EXT OTP extension disabled


* BMPKH, BMEK:
Writing to efuse row failed!
Error Status Code: 7
Writing to efuse row failed!
Error Status Code: 7
Programmed 0/1 rows successfully
Error in programming BMPKH part 1
debug_response: 0xC000800

# Cust_Keys program failure

I wonder if there are something wrong that caused this 07 issue in the sequences of DC POWER ON? 

are these sequences of DC POWER ON correct? besides this, are there other potential factors causing this problem?

thanks