Hello, after I define s with CFG_READ_BDADDR_FROM_DA14583_FLASH, I read it after burning with SmartSnippets according to the process, and the data displayed is exactly the same as the content to be burned by bin. There is no mistake in the process of converting the file. After I press reset, 583 ota failed.
Is it a secondary boot file or procedure that needs to be modified?(I don't know why the buzzer will sound when the 583 module is powered on, but it will not sound when it is debugged.)
Thanks.
Device:
Hi GGQ_in,
Could you please try to describe what you are trying to accomplish and that your issue is? In which SDK example you are working? Do you have SUOTA functionality?
Thanks, PM_Dialog
Hi PM_Dialog,
I want to OTA 583 module. I used the ble_app_ota and secondary_bootloader examples in SDK5.0.4.With the SUOTA function, I used this program to successfully make 580 OTA.And then made OTA for 583 based on this basic modification, But failed.There was no error in the process, and when I pressed the reset key, 583 did not change.
The difference between 583 and 580 is that 583 is read from internal FLASH and 580 is not it?
The following is the sw reset function. Do I need to modify the assembly function or is it a problem when reading 583 from flash?
__asm void sw_reset(void)
{
LDR r0,=0x20000000 //将0x20000000 给R0 Reg
LDR r1,[r0,#0] //将0x20000000地址中的数 读取给r1，也就是栈地址传给r1
MOV sp,r1 //将栈地址给sp指针
LDR r2,[r0,#4] //复位地址给r2
BX r2 //跳转到复位地址开始运行
}
Thanks.
Hi GGQ_in,
If you are starting a new design, we would strongly recommend to start with DA14531 or DA14585/586 products and our latest SDK6.0.14, as it is much more improved. We have a lot of code examples and improved documentation, and there is also software roadmap support. There is not any software roadmap support for DA14580 product family and SDK5. Moreover, in SDK6, adding SUOTA functionality in your project is straight-forward procedure.
Please check DA14531:
//www.wsdof.com/products/connectivity/bluetooth-low-energy/products/da14531
Additionally the DA14531 SmartBond TINY™ Module is now released! Follow the link below to find datasheet, documentation and HW collaterals for the module:
//www.wsdof.com/products/bluetooth-module-da14531-smartbond-tiny
Also, Dialog Serial Port Service (DSPS) and CodeLess are now available for the DA14531!
To answer your question, since you are interested in adding SOTA, please take a look at the following application note:
//www.wsdof.com/sites/default/files/an-b-010_da14580_using_suota_0.pdf
Did you follow this document?
Thanks, PM_Dialog
Hi GGQ_in,
If you are starting a new design, we would strongly recommend to start with DA14531 or DA14585/586 products and our latest SDK6.0.14, as it is much more improved. We have a lot of code examples and improved documentation, and there is also software roadmap support. There is not any software roadmap support for DA14580 product family and SDK5. Moreover, in SDK6, adding SUOTA functionality in your project is straight-forward procedure.
Please check DA14531:
//www.wsdof.com/products/connectivity/bluetooth-low-energy/products/da14531
Additionally the DA14531 SmartBond TINY™ Module is now released! Follow the link below to find datasheet, documentation and HW collaterals for the module:
//www.wsdof.com/products/bluetooth-module-da14531-smartbond-tiny
Also, Dialog Serial Port Service (DSPS) and CodeLess are now available for the DA14531!
To answer your question, since you are interested in adding SOTA, please take a look at the following application note:
//www.wsdof.com/sites/default/files/an-b-010_da14580_using_suota_0.pdf
Did you follow this document?
Thanks, PM_Dialog
Hi PM_Dialog,
Thank you for your advice.At present, I have 583 modules, so I want to use this module for internal FLASH burning and writing.
当下载在调试模式下,它可以normall运行y. When doing FLASH burning and writing, the contents read are as shown in the figure,but after hardware reset can not execute normally,Although I have updated the flash_programmer. Bin file, along with the guidance ofAn-b-010_da14580_using_suota_0.pdffile, the pin of spi has also been modified.
Do I need to pay attention to the pin of spi for OTA and OTA for internal flash burning of 583？
Thanks.
Hi GGQ_in,
My apologies but still I am not able to understand what the issue is.
According to the attached screenshot from SmartSnippets Toolbox, what is the .bin file that you are using? Is it the muilti-binary image? After burning that binary, does the device start advertising correctly?
Please try to use the prox_reporter example according to the application note.
Thanks, PM_Dialog
Hi PM_Dialog,
The bin file I am using is the muilti-binary image, and the device has not started advertising.Now I've done two tests, and the results are different:
1. I changed the pin in the secondary boot file, project file and resources\flash_programmer. Bin file back to the pin of 580.When I debug download the second boot file to the module again, the module runs the program written by burning, and the module broadcasts.
2. After I configured the spi pin in resources\flash_programmer. Bin into the spi pin corresponding to DA14583, SmartSnippets spi FLASH failed to read and write and wipe.Do you have the successful 583 module flash_programmer.bin let me to study?
Thanks.
Hi GGQ_in,
In the SmartSnippets Toolbox, can you please check that you are using the correct SPI pin configuration? This can be found in “Board setup” tab.
Thanks, PM_Dialog
Hi,
My version of SmartSnippets is 3.6, and the "Board setup" TAB does not have spi pins to choose from.
Thanks.
Hi GGQ_in,
Please try to open again the SmartSnippets Toolbox (SST). You should get a pop-up window like the attached screenshots. Could you please check that you have similar configuration?
If the left column is empty, you should press the “New” button and set a name (you can add any name / description you want).
You should see the either the JTAG number or the COM port at least.
Please also check the SST user manual (link is provided below)
http://lpccs-docs.dialog-semiconductor.com/SmartSnippetsToolbox5.0.8_UM/getting_started/getting_started.html
Thanks, PM_Dialog