自14583年芯片上有1024K闪存，我想也许这方面可以通过空气更新。但在文件中，我找不到CICRIBE的COSHOWNING DATASHEET如何更新DA14583.I上面的上下文，你有没有像“AN-B-003：DA14580在AIR（SPOTA）上修补的软件（SPOTA）“，讲述如何在AIT上更新软件。但不仅在DA14580中，也在DA14583中
Keywords:
设备：
嗨Shezhe9，
There is no application document specifically for 14583 and SUOTA. But i suppose that you are able to do that just as da14580, the difference is only the pin configuration of the SPI. You can try to experiment with the proximity application of the SDK5.
谢谢mt_dialog.
谢谢，我注意到这个芯片Contian 1K闪存WtiH SPI总线onchip。这意味着它刚刚将内部闪光作为外部SPI闪光灯。
嗨Shezhe9，你也可以want to read AN-B-010 that is the application for SUOTA and explains it in more detail.As Marios mentions, it references the 14580, but 14583 is just the 14580+FLASH inside), so the same SUOTA scheme works (as documented in the 14580), In SDK5, it is included in the project example for the 14583 proximity reporter project.
BR JE_DIalog
谢谢je先生。另一个question,dou You got any SUOTA sourse code example in both 14580 agent side and host side such as ios app or andriod app?
嗨Shezhe9，
您可以在Proximity_reporter和智能标记参考设计中找到Suota配置文件的实现。就主机侧已发送邮件。
谢谢mt_dialog.
Hi,
The suota module seem to use around 5KB which is driving my implementation past 32K. is there a minimal.implementation of this. Port selection and all that is not needed if that is fixed. also what is the use of the proximity module in the example. I don't think that is required for a custom implementation?
问候
Gayan
Hi gayan_gamage,
没有较小版本的Suota实现。关于示例的接近模块，我不太完全得到你的意思，接近示例包括苏格达配置文件
order to update over the air, the existing proximity firmware. If you just want the SUOTA profile in your custom design you dont have to add the proximity profile or the battery or other profiles that the proximity example implements.
谢谢mt_dialog.
亲爱的mt_dialog，
我还希望使用DA14583和Window PC中的DAT14583和Dialog USB加密狗进行oat函数。
但我无法理解测试环境。
1）将FW_MULTI_PART_SPI.BIN文件放入DA14583中。
2）我应该为Dialog USB加密狗执行哪个项目？
3）哪个程序Shoud在窗口PC中执行？
- >我为'suota发起者进行了一个smartsnippets程序。但是，我无法连接COM端口，因为连接按钮未激活。
嗨Hogyunkim，
2）我想你想用加密狗作为一个中心和583作为一个设备，没有必要下载Dongle上的任何FW，智能片段在连接时会这样做（Whn在智能片段中击中连接。）。
3) You should run the Smart Snippets and the OTA application, that will allow you to use the dongle as a central and download the SUOTA central fw into the dongle, you will have to use UART interface in order for the "Connect" option to be available.
谢谢mt_dialog.
Dear Dialog,
我无法使用我的加密狗激活“连接”按钮。
在上一段时间，我可以连接，但现在我无法连接到我的加密狗。
是否有任何固件来执行USB Dongle？
I already select the right COM port with USB donlge port.
Best regards,
Hi hogynkim,
如果聪明的片段OTA的connect按钮rvices is deactivated is because you are using the JTAG interface in order to connect with the tool and not the UART port. When the Smart Snippets starts, please select the plain UART mode (not the UART/SPI mode). After that open the OTA services and hit the "Connect button", Smart Snippets will indicate "Loading firmware, please wait...." and after that it should indicate that "Firmware loaded successfully" and it will start the scanning procedure. The scanning procedure will finish automatically.
谢谢mt_dialog.
谢谢你的评论。
I succesfully download a new image to DA14583 board with SUOTA.
因此，我将OTA配置文件合并到DSPS项目
After that, I tested again with the merged DSPS project.
但我从下面的SmartSnippet获取了消息。
What did I wrong ? I refered the comment on "How to add the SUOTA profile to my SDK 5.0.3 application ?" page on FAQ.
我还检查了下载图像是正常的。
==============================================================================
[INFO @17-03-14 18:46:01] Establishing Link with target device...
[INFO @17-03-14 18:46:02] Link with target device has been established.
[info @ 17-03-14 18:46:02]特色发现开始了。
[INFO @17-03-14 18:46:03] Characteristics discovery finished.
[info @ 17-03-14 18:46:37]固件下载开始...
[INFO @17-03-14 18:46:37] SPOTAR_IMG_STARTED
[信息@ 17-03-14 18:46:37]内存信息：
0 bytes
[错误@ 17-03-14 18:46:37] spotar_inval_product_hdr
[INFO @17-03-14 18:46:37] Firmware download failed.
[INFO @17-03-14 18:46:37] Target device has been disconnected. Please try to re-establish link.
==============================================================================
Best regards,
嗨Hogyunkim，
您获得的错误表明Flash中的产品标题出现了出现问题，这是您可以拥有这种错误的唯一原因。您的MultiPart图像中是否有产品标题（在地址0x1f000），如果有一个，它是否有适当的产品标题签名0x70和0x52？
谢谢mt_dialog.
Dear Dialog,
我检查了产品标题，我收到了以下数据
[0x1F000] 70 52 00 00 00 80 00 00
[0x1F008] 00 30 01 00 FF FF FF
[0x1F010] FF FF FF FF FF FF FF
......
我认为多部分图像是对的。
我怀疑DA14583中的闪存的SPI通信。
I included the spi.c and spi_flash.c files in sdk_driver folder within DSPS project.
我在user_periph_setup.h文件中配置SPI_PORTS和SPI_PINS。
DSP项目中有任何修复点吗？
Best regards,
嗨Hogyunkim，
你应用on_spotar_status_change()乐趣ction in order for the flash to be enabled since your device is the 583 in order for the application to enable the flash ?
You will be able to find the implementation in the prox_reporter example, here is the implemented code of the function:
void on_spotar_status_change( const uint8_t spotar_event)
{
#f定义（__ da14583__）&&（！spotar_spi_disable）
Int8_t man_dev_id = 0;
man_dev_id = spi_flash_enable（spi_en_gpio_port，spi_en_gpio_pin）;
if（man_dev_id == spi_flash_auto_detect_not_detected）
{
//未识别设备。使用默认参数。
//可选地，这里可以断言错误。
spi_flash_init（spi_flash_default_size，spi_flash_default_page）;
}
if( spotar_event == SPOTAR_END )
{
// Power down SPI Flash
spi_flash_power_down（）;
}
#endif
}
#endif // (BLE_SPOTA_RECEIVER)
/// @} APP
谢谢mt_dialog.
Dear Dialog,
I already put this code into user_sps_device.c file.
I find the root-cause the reason why my DSPS project doesn't work the OTA operation.
原因是我将GPIO0_3设置为下面。
=> gpio_configurepin（gpio_port_0，gpio_pin_3，input_pulldown，pid_spi_di，false）;
Could you let me know why this pin is related to OTA operation.
我想知道其他影响OTA操作的别针。
I am using a DA14580DEVKT-P_VB with DA14583 chip.
我正在使用带有SPI通信的闪存区域。
此外，我没有与PIN0_3连接任何连接。
Best regards,
嗨Hogyunkim，
Since you are using a 583 (and you have defined in your DSPS application that the dev kit used is a 583) there is no use for the GPIO0_3 the pins from the SUOTA sw, if the 583 is selected as a running device then the pins used by SUOTA are pins for the flash of the 583, (2_0 CLK / 2_3 CS / 2_4 MISO / 2_9 MOSI). In case of a 580 then the P0_3 is used as a CS for the external flash.
谢谢mt_dialog.
Dear Dialog,
I also know your comment.
因此，在GPIO0_3引脚上实现了奇怪的套筒操作。
If you test the below environment, then you can reproduce this phenamenon.
1）D14580DEVKT-P_VB，DA14583ATDB-P
2）BLE_APP_OTA.UVPROJX.
+ GPIO_ConfigurePin(GPIO_PORT_0, GPIO_PIN_3, INPUT_PULLDOWN, PID_SPI_DI, false); in set_pad_functions() function.
嗨Hogyunkim，
Yes i am able to replicate what you are experiencing, it seems that when your configure the pin as PID_SPI_DI and when the SUOTA operates (it configures the pins of the SPI module whenever it starts an interaction with the flash) you have two pins that are simultaneously connected to one SPI module. When something like this happens (both pins have PID_SPI_DI so you have two sources in one input) the functionallity of the pin will be assigned to the GPIO that has the smaller GPIO index, therefore to the 03 port pin (and that why the SUOTA doesn't work). What you can do in your case, since i get that you would like to have an additional SPI device on the 583 is to apply the same thing that the SUOTA does (more or less) as far as the configuration of the pins is concerned, dont configure your pins in the periph_init() function with a specific functionallity but have them as PID_GPIO and as soon as you are going to use them, apply the corresponding configuration as soon as you finish de-configure your pins to the PID_GPIO functionallity.
谢谢mt_dialog.
Dear Dialog,
Thanks for your reply.
I understand your comment.
您的评论是，如果我想使用SPI通信的OTA函数，那么我不使用PID_SPI_DI定义，或者我必须在完成OTA函数后使用PID_SPI_DI定义。
I have another question.
Then the PID_SPI_CLK, PID_SPI_EN, PID_SPI_DO definitions doesn't effect to OTA function ?
Best regards,
嗨Hogyunkim，
No it doesn't affect the other SPI pins because those pins and are configured for output functionallity and not as input towards the SPI module.
谢谢mt_dialog.