雷竞技电竞平台对话半导体客户支持- CLI https://support.dialog-semiconductor.com/resource-keywords/cli SmartSnippets命令行OTP燃烧失败 https://support.dialog-semiconductor.com/smartsnippets-command-line-otp-burning-fails < div class = "字段field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >论坛:,< / div > < div class = "字段条目" > < div class =”field-item甚至“rel = " sioc: has_container " > < a href = " /论坛/ dialog-smartbond-bluetooth-low-energy - % E2 % 80% 93 -工具”“=“sioc:容器sioc:论坛”属性= " rdfs: labelskos: prefLabel”数据类型= " " >对话框Smartbond蓝牙低能量——工具< / > < / div > < / div > < / div > < div class =”字段field-name-body field-type-text-with-summary field-label-hidden”> < div class = "字段条目" > < div class =”field-item甚至“财产=“内容:编码”> < p >在生产线设置我们试图使用SmartSnippets命令行接口烧OTP头和OTP自定义代码。两者都可以在Windows GUI中工作,但在命令行中失败。

程序工作下载:

C:\Program Files\ smartnippets \bin> smartnippets .exe -type booter -chip DA14580-
01 -jtag 518110536 -file "C:\Users\a1t4czz\ smartnippets \resources\jtag_program
.bin"
无法测量总IR len。TDO恒定高。
不能测量总IR len。TDO恒定高。与ID 0 < br / >发现SWD-DP x0bb11477 < br / >发现Cortex-M0 r0p0,小端字节序。
BTLE设备被选中。
BTLE设备被选中。
Using default GPIO pin Id: P1_2。
XPSR的t位是0,但应该是1。 Changed to 1.
Firmware File c:\users\a1t4czz\smartsnippets\resources\jtag_programmer.bin has b
een selected for downloading.
Cortex-M: Debugger tries to set PC to odd value. Corrected register value from 0
x000800B5 to 0x000800B4
Successfully downloaded firmware file to the board.

But trying to burn anything fails:

C:\Program Files\SmartSnippets\bin>smartsnippets.exe -type otp -chip DA14580-01
-jtag 518110536 -cmd write_field -offset 0x7F00 -data 1234A5A5
Could not measure total IR len. TDO is constant high.
Could not measure total IR len. TDO is constant high.
Found SWD-DP with ID 0x0BB11477
Found Cortex-M0 r0p0, Little endian.
FPUnit: 4 code (BP) slots and 0 literal slots
BTLE device selected.
Using default baudrate: 57600 Bd.
Failed burning OTP field at address 0x47F00.

C:\Program Files\SmartSnippets\bin>smartsnippets.exe -type otp -chip DA14580-01
-jtag 518110536 -cmd write_custom_code -file "C:\svn\BLEtooth\FW\DA14580_DSPS_3.
150.2 device\dk_apps\keil_projects\sps\sps_device\out\sps_device.hex" -offset 0x
0
Could not measure total IR len. TDO is constant high.
Could not measure total IR len. TDO is constant high.
Found SWD-DP with ID 0x0BB11477
Found Cortex-M0 r0p0, Little endian.
FPUnit: 4 code (BP) slots and 0 literal slots
BTLE device selected.
Using default baudrate: 57600 Bd.
Read 14208 bytes from file c:\svn\bletooth\fw\da14580_dsps_3.150.2 device\dk_app
s\keil_projects\sps\sps_device\out\sps_device.hex.
Reading OTP memory contents. Needed to check addresses that have already been bu
rned.
Started burning memory with 14520 bytes of data at address 0x40000.
Failed writing bytes at address 20000000.
OTP Memory burning failed.

Note that I do only have the SWD interface connected to a JTAG programmer. I do NOT have a UART connection. But since the SmartSnippets GUI works I am thinking that the hardware connections are ok. I have also checked the supply voltage and the programming voltage, both look ok.

Am I missing some step?

Device: 
2016年4月6日星期三08:56:08 +0000 rkpu 3172年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/smartsnippets-command-line-otp-burning-fails#comments
使用SmartSnippets命令行燃烧OTP映像 https://support.dialog-semiconductor.com/burning-otp-image-using-smartsnippets-command-line < div class = "字段field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >论坛:,< / div > < div class = "字段条目" > < div class =”field-item甚至“rel = " sioc: has_container " > < a href = " /论坛/ dialog-smartbond-bluetooth-low-energy - % E2 % 80% 93 -工具”“=“sioc:容器sioc:论坛”属性= " rdfs: labelskos: prefLabel”数据类型= " " >对话框Smartbond蓝牙低能量——工具< / > < / div > < / div > < / div > < div class =”字段field-name-body field-type-text-with-summary field-label-hidden”> < div class = "字段条目" > < div class =”field-item甚至“财产=“内容:编码”> < p >你好,< br / >我有SmartSnippets 3.6并成功烧几个模块的otp通过the SmartSnippets GUI.
I want to do the same burning through the cli so we could burn many modules easily.
Using the GUI, the first burning process is to go to the "OTP Image" tab after clicking the "OTP Programmer" sidebar button, choosing the compiled hex file and then clicking "Connect" and "Burn".
I assume that the equivalent cli command is "-type otp -cmd write_custom_code".
However, the documentation says:
"Burns file to OTP memory. Makes the assumption that a valid firmware file has already been downloaded (e.g. through use of the uartBooter command above)."

Does the "Burn" button call the "-type booter" before calling the "-type otp -cmd write_custom_code"? Do I have to call both commands?

I used the GUI Booter sidebar button just for testing the program: load the code to the memory without burning the OTP, check that it works, restart (disconnect and reconnect power and usb) and then go to the OTP Programmer sidebar button...

Thanks

2015年2月11日星期三16:04:39 +0000 奥伦 1117年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/burning-otp-image-using-smartsnippets-command-line#comments