DRA829J-Q1: Secure Key OTP programming through automation - DRA829

Saravanakumar Balasubramanian

Part Number: DRA829J-Q1
Other Parts Discussed in Thread: DRA829

We are doing test automation for the Nexus Oncore controller project using DRA829 secure processor.

In this we are facing challenges while doing secure key OTP programming through automation software.

The same procedure if we are doing manually and we could able to flash the secure key correctly, but through automation software, we could not able to flash the secure key.

Eventhough the log file shows that all the nine secure key images were transferred, we could not able to flash U-boot image after that, and the boards hangs when we are flashing the second U-boot image itself. But if we do the secure key programming manually for all the nine images, then we could able to flash the U-boot image and the processor is booting.

Please let us know, whether we need to take care of any timing that we should take care while flashing the secure key images.

We are also powering off and powering on the board between each image flashing through automation software.

Request your support on priority since, BH has started mass production and we are struck due to this issue.

over 3 years ago

0 Keerthy J over 3 years ago

TI__Guru**** 171060 points

Hi Saravana,

Can you share the log of where exactly the hang happens? I believe you are using 9 different images to burn all the fields that you want to program.
Where is it getting stuck? How are you trying to automate and where is it getting stuck?

Details of SDK version also will help us.

Thanks,
Keerthy

0 Saravanakumar Balasubramanian over 3 years ago in reply to Keerthy J

Prodigy 190 points

Hi Keerthy,

I have attached the terminal log during OTPimage flashing. We are not able to capture MCU_UART to serial port data since we are running virtual Linux in windows installed system.

log_flash_otp_15_01_02_2023.txt

Regards

Saravanakumar

0 Keerthy J over 3 years ago in reply to Saravanakumar Balasubramanian

TI__Guru**** 171060 points

Hi Saravana,

Once the images are burnt on to the OTP region we need to power off and Power on the board in order to actually push the data on to the memory. So if that is not happening in the automation then the writes will not take effect. A Power on cycle is needed. That might be one difference with and without automation.

Regards,

Keerthy

0 Saravanakumar Balasubramanian over 3 years ago in reply to Keerthy J

Prodigy 190 points

Hi Keerthy,

We are giving reboot commands in code and we are controlling the supply through relay. Any timing needs to be maintained for this power cycle?

Regards

Saravanakumar

0 Keerthy J over 3 years ago in reply to Saravanakumar Balasubramanian

TI__Guru**** 171060 points

No. Reboot cannot do the complete power on cycle & reboot is not sufficient for the values to get burnt to OTP. The hardware design mandates
a PoR cycle. That is the reason why it works for you when you do manually.

- Keerthy

0 Saravanakumar Balasubramanian over 3 years ago in reply to Keerthy J

Prodigy 190 points

Hi Keerthy,

We are giving reboot commands that will cut off the relay and make it on once again. So PoR will be trigerred. We are not giving the soft reset in U-boot. Can it be debugged if we share the MCU_UART serial data during OTP flashing.

Regards

Saravanakumar

0 Keerthy J over 3 years ago

TI__Guru**** 171060 points

Saravanakumar Balasubramanian said:
The same procedure if we are doing manually and we could able to flash the secure key correctly, but through automation software, we could not able to flash the secure key.

This is what still interesting to me. When you do manually what is the time taken for POR cycle? What is the time taken when you automate?
Can you add like a 2-3 second delay between off and On?

The big log you shared I could not decipher anything.

Processors

Processors forum

DRA829J-Q1: Secure Key OTP programming through automation - DRA829