雷竞技电竞平台对话半导体客户支持- OTP DA14585 https://support.dialog-semiconductor.com/resource-keywords/otp-da14585 在 OTP VPP销 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/otp-vpp-pin < 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:Forum" property="rdfs:label skos:prefLabel" datatype="">Dialog Smartbond Bluetooth Low Energy - Hardware (device &

它基于DA14585 MSK物联网设计。我只做了大约15个板

作为这个产品的开发/测试平台。我对DA14585_DB_IOT+VC_SCH中所示的DA14585使用了相同的引脚。在这个原理图中，

引脚38只是发送到没有放置的电容器。因此，在看到这个并读取DA14585的数据表之后，似乎这个引脚不需要

。所以在我的设计中，我没有连接这个大头针(就像你没有)。现在我读到，我需要有二级引导加载程序，以

引导从我安装的外部闪存(正如安装在您的MSK设计)。 So in order to install the secondary bootloader

I suppose I need access to that pin 38 to set it to 6.8 volts for the OTP programming. I cant gain access to that pin now with the boards I had made.

Is this true? Is there a away around having to use this pin while still being able to boot from the external flash? How did you do this at the factory

(did you use a zif programmer or something like that) as I am surpised that you had the OTP programmed ahead of time on the chips before they

were soldered on the board (?) as there doesnt appear to be anything connected to your pin 38 on the schematic.

Please help. Thank you.

Keywords: 
OTP DA14585
Device: 
DA14580
 2019年3月13日星期三04:15:28 +0000 克雷格·弗拉纳根 293297年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/otp-vpp-pin#comments OTP不能读 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/otp-cannot-read < 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: label skos: 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 / >我想写点东西OTP。
我正在使用“otp_write_words”函数来写OTP。
我写了一些数据到地址0x7F8FDF0在我的代码如下步骤…< br / > 1。写入0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01
2。读取地址，得到0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x01 ==>正确的< br / > 3。写入0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x02
4。读取地址，得到0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x03 ==> correct, because (0x01 | 0x02) = 0x03

However, I found that sometimes it is weird.
I have written data into the OTP, but after reading, It became to 0x00. Some bytes which I wrote 0x00, but it became 0x80.
1. Write 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x11
2. Read the address, got 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x11 ==> correct
3. Write 0x00 0x00 0x00 0x00 0x00 0x00 0x22 0x00
4. Read the address, got 0x00 0x00 0x00 0x00 0x00 0x80 0x22 0x00 ==> incorrect, It should be 0x22 0x11 and a byte became 0x80??

Why? I have no idea.

After rounds of reading and writting, I can't read anything from OTP.
I traced the code, I found it got stuck in "ASSERT_WARNING_OTPC_MODE(HW_OTPC_MODE_STBY);" of "hw_otpc_manual_read_on" function.

How can I recover it?

By the way, I use Product Line Tool to write some data such as "Trim Value for the XTAL16M oscillator".
Should I write some code to read it and set the value?

Thanks a lot.

Keywords: 
OTP DA14585
Device: 
DA14585
 Tue, 26 Sep 2017 10:43:07 +0000 stanley_yeh 96682年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/otp-cannot-read#comments