您好对话团队，
we are currently working on a DA14583 device with Ibeacon product, while on our R&D stage we are facing issue on working with this SOC, I'm listing it out, kindly support as , thank you.
1) why smart snippet not supporting the *hex* output file generated from keil MDK 5.25, is it will support only *.bin* file , if so how to generate it using (hex to bin) on a windows 10 PC (any alternative software for that).
2）由于SoC是新的市场，我们可以详细介绍使用Smart Scompet及其工作台的详细信息。
3）在固件上燃烧的批量生产的实践是什么，因为它看起来复杂且耗时，而燃烧OTP并按下重置以检测然后刻录固件，您可以建议一个帮派编程器将处理这些序列。
Device:
Hi jagath,
https://support.dialog-semiconductor.com/connectivity/reference-designs?qt-view__reference_designs__block_3=7#qt-view__reference_designs__block_3
Thanks, PM_Dialog
Hi Pm_dialog,
感谢您的直接响应，我们的工程师将审查您的建议并发布我们的Quires。
嗨pm_dialog，
As i download the dialog battery powered Ibeacon example program and build the program using keil 5.25 and debug the program using the DA14580 Development Kit - Pro with the DA14583 daughter board . The program runs fine on this debug environment.
But i'am facing a problem when i tried to flash the program on to my target board of DA 14583 using UART method using smart snippet.
problem: (getting no response from the board after flashing)
1）我的问题是，我是否必须将引导加载程序程序与此对话框固件或对话框ICon固件组成，也由引导加载程序组成。
2) if i want to combine it, is any GUI tool to do this other then the long method in the UM-B-012.
Hi jagath,
您能否在使用Smartsnippet时尝试烧掉SPI Flash时提供更多信息？您是否能够成功刻录SPI闪存，583无法启动，或者您无法刻录它？另外，如果您能够将固件下载到Sysram，请告诉我吗？你能试着用SDK的另一个BLE拼写刻录SPI闪光吗？583芯片已烧毁引导加载程序，由SPI Flash默认靴子
Thanks, PM_Dialog
Hi PM_Dialog,
1）我可以成功闪烁，我也可以读取烧焦的闪光灯。583启动问题我不确定，以及任何检查它的方法。
2) and what i have to do with the OTP flash, can be felt without doing that ..?? , for the dialog i beacon example.
Hi jagath,
Are you able to boot when downloading firmware to SysRAM through UART? Could you please check if you have the same issue when downloading firmware from one other example of the SDK?
Thanks, PM_Dialog
嗨pm_dialog，
1）没有靴子没有发生，是的，我下载了BLE裸骨，它在我的目标板上也没有响应，SPI Flash编程方法通过UART接口。我附上了烧记报告，请找到它。
Hi jagath,
As I have already mentioned on my previous post, my recommendation was just to download directly code to Sysram and not burn the SPI flash through the UART interface. So please try to download into SysRAM any example code to the 583. For downloading code to the SysRAM you will have to build the project for a 583 board (there is an option at the top of the Keil IDE that will allow you to do so and select 583 from the drop down menu). Then you will have to click into the “debug” button and run your code. Regarding the fact that you are not able to boot from flash, from the picture that you have attached I see that the image that is burned in the flash lacks of the bootable header that the Smart Snippets attaches (that is if you click yes when the tool prompts you for burning a bootable image). So when you hit the burn the tool will prompt you for a making the image bootable you should click on the “Yes” in order to be able to boot from flash.
Thanks, PM_Dialog
嗨pm_dialog，
As i have mention earlier it works fine on the debug mode over the development board, but my scenario will be burning same firmware on the target board, and on burning the FW on the SRAM will be non-volatile right..?? .
I have tired the option by clicking "YES" also , still it didn't works , And Should i burn the boot loader image on the OTP image header.??.. thanks in advance.
嗨pm_dialog，
并且我是通过在闪存程序员上选择“是”来连接烧记报告。
Hi jagath,
我建议您将代码直接下载到Syram中，以确认您使用的设备是否能够运行启用BLE启用的固件，并且它不是您的问题的解决方案。关于您无法在SPI Flash中的583上运行信标代码，您是否尝试重置电路板以再次运行引导加载程序，并最终从SPI Flash加载固件？您不应该在OTP上刻录任何东西，以解决您的问题。请注意，583的OTP已使用583引导加载程序刻录，用于直接从预定义的SPI引脚启动，然后检查具有不同接口的其他引脚。我试图用583连接的Pro devkit板上的信标软件在我身边复制你的问题，我能够看到设备广告。如果这不适用于您正在处理的自定义板上，那么如果存在问题，则必须使用分析仪检查引导过程。
Thanks, PM_Dialog
Hi Pm_dialog,
我们已经开发了自己的固件，具有定制的广告数据，它适用于目标板DA14583，但不是对话框IBeAcon和其他示例的FW。我缺少的地方。
在开发板14580上使用JTAG连接器，引脚如下，无法将设备连接到调试模式，就像DA14583的子板一样。
on the J5 header pin 26 --> SWDIO on the target board
28---> SWCLK on the target board
1--> vbat
2--> gnd
and toggle sw connected to vbat --> reset
我必须连接din。
Hi jagath,
对不起，但我无法理解你的问题，所以请你更多地解释一下吗？如果我能够抓住你的意思，你已经设计了使用DA14583芯片的自定义PCB，并且您已开发出您的自定义板上的自己的固件？虽然，您无法从SDK下载任何默认固件到您的自定义板。我明白了吗？请您可以清楚您的问题是JTAG连接器吗？您是否使用任何DA14580开发套件连接您的定制板？
Thanks, PM_Dialog
Hi dialog_pm
我们有一个自定义与da14583 SOC在我t and we are burning the Fw by flash spi ,Using uart method with help of 14580 devp pro kit. My Fw runs well since we use the bin file format. but your example program genrate hex file when I try to burn the example program it burns sucessfully but the program boot seems not to be executing.
To run my target board on a debug mode I try to make it run as the daughter board which I suceed using Jtag of your example program .. but facing problem in the jtag connectivity. So correct me on the jtag header pins.
Hi jagath,
When you download firmware to the SPI flash, you use the binary file format in order to burn it. However, the SmartSnippets toolbox converts automatically the hex file to binary file format.
Below are the required connections for programming your custom board using JTAG interface:
您可以在此处找到更多信息«发展套件和参考设计»标签常见问题（常见问题）我们的支持网站的页面。点击下面的链接才能访问FAQ页面：
https://support.dialog-semicondiondiondum/guide/frequencess-asked-questions.
Thanks, PM_Dialog