Booting Prod_Test from OTP Memory

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
Fri, 2018-09-21 13:25
#1
MarkusMehlichHSM
Offline
Last seen:6 months 2 weeks ago
加入:2017-07-11 14:40
Booting Prod_Test from OTP Memory

Hi,

is it possible to boot the Prod_Test software from OTP Memory?

I can programm the Prod_Test software to the PAN1740 (DA14580) with the RF Master and everything works fine.
I can also write our release software and the OTP header to the OTP memory and it works.

But when i try to program the Prod_Test software to the OTP Memory it seemingly doesn't boot.

Is there something i have to consider?

Thanks Markus

Device:
DA14580
Tue, 2018-09-25 21:17
PM_Dialog
Offline
Last seen:3 days 18 hours ago
工作人员
加入:2018-02-08 11:03
Hi MarkusMehlichHSM,

Hi MarkusMehlichHSM,

Could you please clarify if you programmed the application flags in OTP header? Also, could you please explain how you know that the devices is not able to boot? Are you sending commands over UART and it is not working?

Thanks, PM_Dialog

Wed, 2018-09-26 07:40
MarkusMehlichHSM
Offline
Last seen:6 months 2 weeks ago
加入:2017-07-11 14:40
Hello,

Hello,

the applications flags are definitely programmed. I tried it several times and of course all boards are broken now.

I think the device doesn't boot, because the device doesn't answer if I send commands with the RF Master. And the LED on the board is not switched on. But all that works if I program the DA14580 via UART.

Thanks for your help.

Markus

结婚,2018-09-26 41
(Reply to #3)
MT_dialog
Offline
Last seen:2 months 1 day ago
工作人员
加入:2015-06-08 11:34
Hi MarkusMehlichHSM,

Hi MarkusMehlichHSM,

I dont see any limitation for bunring the prod_test in the OTP, the device should properly operate. Also burned a pro kit's daughter board in order to verify this with the production test tool for the 580 and i am perfectly able to communicate with the fw and execute the RF and sleep commands. I suppose that this is not due an issue with the UART since you mentioned that if you download using the UART the device responds to the UART commands of the Smart Snippets, also i suppose that you have tried doing this on more than one device. Is there anything else that you 've changes in the OTP header beside the application flags ? Have you changed anything in the prod_test (perhaps the device stucks due to an ASSERTION in the code). What you can do to check if the device is stack in any assertion or executes code you can attach the debugger while the device has booted (right after reset - remove the initialization file and in the Settings remove the "Reset after connect" option). As soon as you do this you can start a debug session and you should see in the disassembly window the address that the device has stopped.

The device should boot as soon as you hit the reset, and should be ready to accept UART commands, you should see the responsed in green in the Smart Snippets Toolbox.

Thanks MT_dialog

Accepted answer