Hi, Dialog !
We are using the smartsnippets command line to burn the OTP to prepare for the mass production, and we meet a question:
I have burned the OTP successfully using the SmartSnippets software and then export the header file. But we always get the info during burning the OTP header file through command line .
"Timeout while waiting to receive the most significant byte of packet length<1000msecs>"
"Failed buring OTP Header."
Using command are as follows: the first command can download the image file into RAM and work normally.
SmartSnippets.exe -type booter -chip DA14580-01 -com_port 9 -file "C:\smart_tag_AAD2_EXT.hex"
SmartSnippets.exe -type otp -chip DA14580-01 -com_port 9 -firmware "C:\smart_tag_AAD2_EXT.hex" -cmd write_header -file "C:\otp_header.hex"
More detailed infomation in the attachment. Look forward to your reply, thanks!
Hi zuma,
If you want to burn the OTP header please use the below commands:
C:\Program Files (x86)\SmartSnippets\bin>SmartSnippets.exe -type booter -chip DA14580-01 -com_port 30 -file "C:\Users\.....\SmartSnippets\resources\programmer_ES5.bin"
C:\Program Files (x86)\SmartSnippets\bin>SmartSnippets.exe -type otp -chip DA14580-01 -com_port 30 -cmd write_header -file "C:\test\testing_otp_burning.hex"
or try the following
C:\Program Files (x86)\SmartSnippets\bin>SmartSnippets.exe -type otp -chip DA14580-01 -com_port 30 -firmware "C:\Users\mtzanida\SmartSnippets\resources\programmer_ES5.bin" -cmd write_header -file "C:\test\testing_otp_burning.hex"
The firmware -firmware_file command that you are setting is the firmware file that should be downloaded to 580 before executing the command. Please check in Smart Snippets in the help option the User Guide pdf, in the bottom of the document it has the commands and syntax that Smart Snippets takes.
Thanks MT_dialog
Hi, MT_dialog,
Thanks for your reply. I have tested the commands you provided above, but it didn't work with my own firmware.
My header file can be burned successfully with the firmware "programmer_ES5.bin".
Is there anything wrong with my firmware ? or something ignored when i compile my code ?
i also find the same problem in the posthttp://support.dialog-semiconductor.com/otp-programming-1.
He seems have problem with CLI tool through JTAG, and i use UART.
i also try to shorten my cable, but there is not a little effect.
Hi zuma,
I dont quite get it, since you 've burned your OTP header what is the problem, you cant burn your fw image ? The programmer_ES5.bin is the firmware that is downloaded in the 580 in order for your OTP to be burned. Please check the document i ve indicated in my previous post about how the CLI works. In order to burn the software image to the OTP you must issue another command -cmd write_custom_code.
Thanks MT_dialog