yabo国际娱乐Dialog Semiconductor客户支持- 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

你好我已经在一个应用程序上工作了一段时间了。它是基于DA14585 MSK物联网设计。我刚刚做了大约15块板

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

引脚38只是被发送到一个没有放置的电容器。因此,在看到这一点和阅读DA14585的数据表后,似乎这个引脚不

所需要。所以在我的设计中,我没有连接这个大头针(因为你没有)。现在我读到,我需要有辅助引导加载程序,以

引导从外部闪存我已经安装(安装在您的MSK设计以及)。因此,为了安装辅助引导加载器

,我想我需要访问引脚38,将其设置为6.8伏特用于OTP编程。 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: 
Device: 
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

亲爱的支持团队,
我正在尝试写一些东西到OTP。
我正在使用函数“otp_write_words”来写OTP。我把一些数据写入地址0x7F8FDF0在我的代码中,如下步骤…
1。写0x00 0x00 0x00 0x00 0x00 0x00 0x01
读取地址,得到0x00 0x00 0x00 0x00 0x00 0x00 0x01 ==>正确
写“0x00 0x00 0x00 0x00 0x00 0x00 0x02
”4。读取地址,得到0x00 0x00 0x00 0x00 0x00 0x00 0x03 ==>正确,因为(0x01 | 0x02) = 0x03

然而,我发现有时它是奇怪的。
我已经将数据写入OTP,但读取后变为0x00。一些字节我写的0x00,但它变成了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: 
Device: 
星期二,2017年9月26日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