我有一个类似的问题，使用SmartSnippet将.hex文件下载到SPI Flash，基本板上。 The following is stated in the html Help chapter, but I am not clear what the meaning is for "Special firmware is downloaded". I get the similar Timeout message.
On my PCB I am using P0-0 and P0_1 to connect to the FTDI chip, I make those the selections in SmartSnippets, along with P0_7 to control VPP (I have also jumpered VPP from the Motherboard to my PCB).
将范围放在RST引脚（也跳到我的PCB）上，我可以看到PIN基于原理图，只要应该像它一样进入3V。
I have also tried using the P0_4 & P0_5 motherboard pins and run them to my P0_0 & P0_1 pins, just to see if that made a difference. I have tried opening SmartSnippets using just UART and in UART/SPI mode, I even tried JTAG mode.
Something else, I tried disconnecting my PCB completely, then running SmartSnippets. The error is exactly the same, even though no BLE board is connected. This leads me to believe that I don't have something on my PCB connected properly, but if so, why can I run my PCB in debug mode without any issues? Don't they use the same connections for both Debug and OTP programming? (with the addition of the VPP jumper for burning OTP).
A Dialog representative in your region has contacted you offline for troubleshooting. There are no obvious steps that you have missed as far as I can see from your description.
Thanks for your reply, I realized that I could test things a little easier from SmartSnippets by reverting my code to debug (from OTP) then just using the file download feature in the Booter utility.
我得到相同的结果，我的PCB不允许下载，从主板上删除我的PCB给出了相同的错误消息。
But one step closer to getting it figured out, if I now connect the BLE daughter card to the motherboard (my PCB still disconnected) then I am able to successfully download the hex file to the daughter card.
First off, thanks to Dialog for the great support! Mikael at Dialog called me and helped me debug my setup, this was extremely helpful. In particular, having a chance to ask a few key questions about the development environment really helped me to understand what *should* be happening. The nature of the Dialog app notes is that they assume everything will proceed according to instructions. So when things go awry, I am often left scratching my head. But maybe that's just me. Anyway, here is a brief description of what I had previously done, combined with what I learned during the phone call, hopefully I get it right in the retell:
在SmartSnippet中，“板设置”选项卡具有选择“GPIO引脚，可控制晶体管启用高电压......”默认为P0_7。显然，如果没有正确设置，那么我们将无法获得刻录OTP所需的6.8V。---但---- I /我们已经知道这一点，我已经在Murata PCB原理图中验证，P0_7确实控制了6.8V晶体管。
The fatal mistake that I made was then assuming that the P0_7 on the Murata Motherboard was being controlled by SmartSnippets. I was viewing the control flow as starting at SmartSnippets, passing to the FTDI chip on Murata Motherboard, then carrying to the DA14580 on my PCB. Not the case where the OTP burn is concerned.
Turns out, during OTP burn, the P0_7 pin on the Murata motherboard is actually controlled by the P0_7 pin *FROM THE DA14580 ON MY PCB*. So the solution was quite simple, I ran a jumper from the P0_7 pin on my PCB to the P0_7 pin on the Murata Motherboard, and, boom-- I was able to flash the OTP and successfully boot from it.
您好JJW，您使用的是哪个开发板：是主板/ Daugtherboard还是在一个套件中的所有新的基本开发？
BR JE_DIALOG.
你好，
我有一个类似的问题，使用SmartSnippet将.hex文件下载到SPI Flash，基本板上。
The following is stated in the html Help chapter, but I am not clear what the meaning is for "Special firmware is downloaded".
I get the similar Timeout message.
----------从用户指南“SPI Flash Programmer”：
用户可以选择.hex或二进制图像文件，以便将其刻录到SPI闪存。可以使用以下操作：
连接：特殊固件下载到芯片，以允许用户与SPI闪存进行交互。在启用其他操作之前，这是一个强制性的步骤。请注意，此固件与在OTP图像选项卡上按“Connect”按钮时下载的固件不同。如果“CRC不匹配”显示，请再次按“Connect”按钮，然后按下电路板上的硬件重置按钮重新启动下载过程。
轻敲。
Hi JE_Dialog/JJW,
I am trying to burn the OTP on my custom PCB so that I can test it as a standalone device.
当我尝试从SmartSnippet刻录OTP时，我得到相同的错误“超时：重置信号未检测到超过16000毫秒”（完整的日志在下面关闭）。
我正在使用Murata P2ML3078主板（带我的自定义PCB）。
我的自定义PCB仔细阅读主板上的PIN标题，我认为我基于我可以从Keil IDE连接和下载/运行调试模式下载/运行我的固件的事实，我认为我所有所需的连接。
On my PCB I am using P0-0 and P0_1 to connect to the FTDI chip, I make those the selections in SmartSnippets, along with P0_7 to control VPP (I have also jumpered VPP from the Motherboard to my PCB).
将范围放在RST引脚（也跳到我的PCB）上，我可以看到PIN基于原理图，只要应该像它一样进入3V。
I have also tried using the P0_4 & P0_5 motherboard pins and run them to my P0_0 & P0_1 pins, just to see if that made a difference. I have tried opening SmartSnippets using just UART and in UART/SPI mode, I even tried JTAG mode.
Something else, I tried disconnecting my PCB completely, then running SmartSnippets. The error is exactly the same, even though no BLE board is connected. This leads me to believe that I don't have something on my PCB connected properly, but if so, why can I run my PCB in debug mode without any issues? Don't they use the same connections for both Debug and OTP programming? (with the addition of the VPP jumper for burning OTP).
我目前拥有的完整连接列表（10）：
主板< - >我的PCB（DA14580上的引脚）
----------------------------------------
P0_4 (TX) <-> P0.0 (ALT_UART_TX)
p0_5（rx）< - > p0_1（alt_uart_rx）
P0_2（CTS）< - > P0_2（CTS）
P0_3（RTS）< - > P0_3（RTS）
vcc_ext < - > vbat
GND < - > GND
VPP < - > VPP
SWDIO < - > SWDIO
SWCLK < - > SWCLK
RST <-> RST
你看到我错过了吗？
Complete Log Message:
[INFO @ 15-09-23 12:46:00]报头记录已从十六进制文件SPS_DEVICE.HEX中删除。
[INFO @15-09-23 12:46:00] Read 14212 bytes from file sps_device.hex.
[INFO @15-09-23 12:46:10] Firmware File C:\Users\Klim\SmartSnippets\resources\programmer_ES5.bin has been selected for downloading.
[信息@ 15-09-23 12:46:10]与COM31端口的连接已成功打开。
[info @ 15-09-23 12:46:10]开始下载程序...
[动作@ 15-09-23 12:46:11]请按电路板上的硬件重置按钮开始下载过程。
[ERROR @15-09-23 12:46:26] Timeout: Reset signal not detected for more than 16000 msecs.
[信息@ 15-09-23 12:46:26]成功断开了COM31端口。
[INFO @15-09-23 12:46:26] Failed downloading firmware file to the board.
感谢您的任何输入，--- klim
*注意 - 出于某种原因，论坛POST将字符串“P0_UNDERSCORE_0”替换为字符串“****”。所以我不得不将它编辑为“p0-0”所以它会显示。有趣的。
你好，
A Dialog representative in your region has contacted you offline for troubleshooting. There are no obvious steps that you have missed as far as I can see from your description.
嗨mhv_dialog，
Thanks for your reply, I realized that I could test things a little easier from SmartSnippets by reverting my code to debug (from OTP) then just using the file download feature in the Booter utility.
我得到相同的结果，我的PCB不允许下载，从主板上删除我的PCB给出了相同的错误消息。
But one step closer to getting it figured out, if I now connect the BLE daughter card to the motherboard (my PCB still disconnected) then I am able to successfully download the hex file to the daughter card.
当我找到解决方案时，我会在这里发布，谢谢你的帮助， - klim
嗨mhv_dialog，
First off, thanks to Dialog for the great support! Mikael at Dialog called me and helped me debug my setup, this was extremely helpful. In particular, having a chance to ask a few key questions about the development environment really helped me to understand what *should* be happening. The nature of the Dialog app notes is that they assume everything will proceed according to instructions. So when things go awry, I am often left scratching my head. But maybe that's just me. Anyway, here is a brief description of what I had previously done, combined with what I learned during the phone call, hopefully I get it right in the retell:
1.以前，您应该使用Keil IDE为项目构建.hex文件。我们在SmartSnippets的所有人都将指向.hex文件并将其加载到我们的BLE芯片中。但是，您应该知道，在您可以将您的.hex文件刻录到OTP之前，您需要在项目目录的根目录中更改DA14580_CONFIG文件中的某些设置。有几个定义指令，名称表明您想要更改它，但事实证明，至少需要更改的唯一需要更改的是需要的行“#define development_debug 1”更改为0.其他可以留下的其他部分：“#undef app_boot_from_otp”和“#undef read_nvds_struct_from_otp”。在进行这些更改后，请务必清理/重建项目。
2.使用JTAG连接通过SmartSnippet是可能的（和最简单），可以使用JTAG连接来编程。这意味着不需要束PF的连接，特别是UART线P0_4（TX），P0_5（RX），P0_2（CTS）和P0_3（RTS）。所以我断开了那些。现在，当您启动SmartSnippet时，应提供“打开项目/创建项目”屏幕。如果您之前没有尝试使用项目使用SmartSnippet，那么您需要点击“新建”并为项目提供一个名称，不要担心您在这里给出项目的名称，我们真正关心的是那么您选择“JTAG”单选按钮，此时您应该在中央框中看到jlink的序列号。在jlink序列号框中放置复选标记，选择芯片类型（我是DA14580-01）然后点击“打开”。
3.在左侧面板中选择OTP图标（鼠标鼠标以查看它们是什么）然后选择Teh OTP图像选项卡并浏览到您的.hex文件（应在项目中名为'OUT'的文件夹中）。点击“连接”按钮，然后，如果您真的感觉勇敢，请单击“刻录”。您应该在文件下载的日志窗口中看到，并刻录开始（可悲，我的项目仍然存在问题，我将描述下面的问题）。
4.在OTP标题选项卡上（如果未显示选项卡，请在左侧面板中的“OTP程序员”按钮上再次单击“连接”，然后单击“从内存中读取”。这将从您的芯片中读取一些在工厂设置的值（如XTAL校准装饰）。在窗口的顶部有两个应用程序标志参数，他们需要更改为“是”。有一堆其他价值观，我被告知我不需要改变任何一个，所以我没有。其中部分是因为Murata实际上已经“重新包装”的部分（如上面的早期帖子所描述的），他们已经完成了包括外部16MHz Xtal的工作。所以我的情况可能不适用于你，请意识到这一点。所以现在你需要做的就是点击“刻录”，你应该完成。
现在让我继续我悲伤的故事，因为在跟随上述内容之后，我仍然无法编程我的芯片。唐。
不幸的是，某些东西没有正确，但不是一种灾难性的方式。对于主要的十六进制文件的OTP刻录变得准备好了，然后它宣布了一个错误（其中一些非常糟糕的拼写），只是停止。幸运的是，我在VPP线上有一个探针，看看它是否提升了电压，即从未发生过电压，所以我仍然能够在调试模式下使用芯片，因为我在此之前完成。不确定这是问题，我们没有将6.8V获得6.8V到我的PCB，或者如果刻录失败，则在该部分之前失败。
Here is the log that was generated when I hit 'Connect' then 'Burn'.
[信息@ 15-09-25 12:17:17]无法衡量总IR LEN。TDO是恒定的。
[信息@ 15-09-25 12:17:17]无法衡量总IR LEN。TDO是恒定的。
[Info @ 15-09-25 12:17:17]找到了带ID 0x0BB11477的SWD-DP
[INFO @15-09-25 12:17:17] Found Cortex-M0 r0p0, Little endian.
[信息@ 15-09-25 12:17:17] FpUnit：4代码（BP）插槽和0个字幕插槽
[INFO @15-09-25 12:17:17] BTLE device selected.
[INFO @15-09-25 12:17:30] Header records have been removed from hex file sps_device.hex.
[信息@ 15-09-25 12:17:30]从文件sps_device.hex中读取14276字节。
[info @ 15-09-25 12:18:05]固件文件c：\ users \ klim \ smartsnippets \资源\ jtag_programmer.bin已被选中以下载。
[INFO @ 15-09-25 12:18:05] Cortex-M：调试器尝试将PC设置为奇数值。从0x000800b5到0x000800b4的校正寄存器值
[INFO @15-09-25 12:18:05] Successfully downloaded firmware file to the board.
[INFO @15-09-25 12:19:18] Started burning memory with 14276 bytes of data at address 0x40000.
[ERROR @15-09-25 12:19:18] Adddittional error info at address 0x81FEC (MSB first): FF FF FF FE
[错误@ 15-09-25 12:19:19]记忆刻录失败。
你有什么建议,如何测试system further would be greatly appreciated.
谢谢，克林
Hi klim,
此错误的最可能原因可能是OTP编程供应。您可以查看VPP上的电源，并确保应用6.8伏。
Thanks MT_dialog
嗨mt_dialog，
好的，我有解决问题的解决方案上面描述的问题，可能这是罪魁祸首一直与原始的“重置按钮不工作”。在对话中再次感谢Mikael，以帮助我弄清楚问题。
在SmartSnippet中，“板设置”选项卡具有选择“GPIO引脚，可控制晶体管启用高电压......”默认为P0_7。显然，如果没有正确设置，那么我们将无法获得刻录OTP所需的6.8V。---但---- I /我们已经知道这一点，我已经在Murata PCB原理图中验证，P0_7确实控制了6.8V晶体管。
The fatal mistake that I made was then assuming that the P0_7 on the Murata Motherboard was being controlled by SmartSnippets. I was viewing the control flow as starting at SmartSnippets, passing to the FTDI chip on Murata Motherboard, then carrying to the DA14580 on my PCB. Not the case where the OTP burn is concerned.
Turns out, during OTP burn, the P0_7 pin on the Murata motherboard is actually controlled by the P0_7 pin *FROM THE DA14580 ON MY PCB*. So the solution was quite simple, I ran a jumper from the P0_7 pin on my PCB to the P0_7 pin on the Murata Motherboard, and, boom-- I was able to flash the OTP and successfully boot from it.
所以我的设备现在函数独立，并确实应该做的事情。一个非常令人兴奋的里程碑，我希望我对我的斗争的笔记会帮助其他一些开发商也达到这一点。
欢呼，克林