用户数据单次存储到OTP image
项目需求从MCU发送蓝牙名称到14585 (无外flash),并保存到OTP。请问怎么读写OTP?直接往地址填入数据?是否需要擦除,是否有区块页概念?
项目需求从MCU发送蓝牙名称到14585 (无外flash),并保存到OTP。请问怎么读写OTP?直接往地址填入数据?是否需要擦除,是否有区块页概念?
请问,软件调试完后,想要烧写程序到OTP中,我用的芯片是WLCSP封装的,烧写口用的是UART P04和P05口,其他管脚接的是VBAT3V和地,VPP接6.8V外部电源,烧写软件用的是Smartsnippets,但是烧写时Smartsnippets提示需要复位信号,是不是芯片RST管脚必须外接高电平复位信号,OTP才能烧写成功?
我看有的单层板,芯片的RST是直接接地的,如果接地是如何烧写的?
Hello,
I have one question regarding the file programmer_es5.bin, mentioned in the AN-B-020.
I'm using a PAN1740 module and I need to burn custom firmware in its OTP. I have sucessfully established UART communication between SmartSnippets and the module, since I can load the firmware through the booter funcionality.
Hello,
I'm currently trying to burn the OTP on a DA14580 using a JLink interface and SmartSnippets.
When I open a new SS project, I select the JTag button and the software recognizes the JLink device successfully, however upon hitting the connect button in the OTP tab I get an answer stating that it was unable to establish a connection.
Because we want to modify the BD address in DA14580 when FW is burned to SPI flash, how can we do this?
(Let every device have the different BD address.)
Method 1:
我们在SPI flash烧弗兰克-威廉姆斯。如果它是可能的,我们可以modify the BD adress by modifing the BD address of hex file? (Do not compile again.)
如果我们能做到这一点,请让我们知道to do.
HI, I am trying to test OTP programming, but when I start to burn OTP to my 14580 chip, I found that there are already some data in the address range of 0x40000 to 0x41600 and the software also warn me that "memory segment already burned!"
So do my 14580 is already broken? what should the OTP looks like when it is new? or I have to set some kind of offset to do the burning? please help me.
Hello Dialog_Support,
My project is in final stage. I want to download the firmware on custom board using OTP.
can anyone help me what pins to connect from hardware and procedure to download .HEX file via OTP.
Are there any changes i have to do it in firmware file.
Thanks and Regards
Rohit
Hello,
I'm about to program the OTP of some dev boards, but wanted to check what I should do with the remapping flag, as there is conflicting views from Dialog (the two posts are linked below).
https://support.dialog-semiconductor.com/how-program-otp-proximity-repor...
https://support.dialog-semiconductor.com/load-program-otp-memory
Hi Dialog team,
I am having issue with writing by PLT.
1. I do not know whether writing of XTAL trim succeeded or not
Even if I look at log, I can not judge whether I could write.
I will attach a log.
Is this written?
Will not log like "write success" come out?
2. The calculated value of XTAL trim changes every time
The XTAL trim is calculated on the same chip, but the value changes each time.
why?
The value should not change, right?
Hello,
I have three questions regarding the OTP header of the device. For background, we have devices that have already been OTP programmed (both the OTP Image section and the OTP header section).
1. It is my understanding that devices that have been OTP'd can change bits from nonzero to zero. Is this in fact possible, and if so, how does one connect to a device that has already been one-time-programmed?