SUOTA and production header

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
7 posts / 0 new
Last post
hqf2013
Offline
Last seen:6 months 3 days ago
加入:2018-09-13 07:15
SUOTA and production header

Hi Dialog,

I am following the SUOTA tutorial to update my custom DA14585 board with an external flash. It can update my firmware correctly. But I found the production header is not the same as the tutorial. The BD address always 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF. I tried to write a new value in address 0x380032. After reboot, the address of my device didn't changed. Besides the OTP method, is there any new method to update the BD address? Thanks.

Device:
PM_Dialog
Offline
Last seen:2 days 11 hours ago
工作人员
加入:2018-02-08 11:03
Hi hqf2013,

Hi hqf2013,

If you would like to have SUOTA functionality and update the DB address, you can change it from the each image that you will download. So, each image will have its own BD address, and after the firmware update, the BD address will be changed. Can you please clarify your last question? What do you mean with “besides OTP method is there a method to update the bd address” ? If you have already burnt the DD address in the OTP header, the application will take the BD address from the OTP. Otherwise, the application will take the BD address from the CFG_NVDS_TAG_BD_ADDRESS definition in the da1458x_config_advanced.h header file. If the BD address is written in OTP header this value will be ignored.

谢谢,PM_DIalog

hqf2013
Offline
Last seen:6 months 3 days ago
加入:2018-09-13 07:15
Thank you PM_DIalog. We didn

Thank you PM_DIalog. We didn't burn the OTP header and we know that OTP header will have the highest priority. We just checked the SDK 5.0.4 for DA14583 and found follows:

/// Device BD address
struct bd_addr dev_bdaddr __attribute__((section("retention_mem_area0"), zero_init));
....
...
bool nvds_read_bdaddr_from_da14583_flash(void)
{
....
}

These function and definition have removed from the SDK 6.0.10 for DA14585. Is there any problem for the DA14585 to get the BD address from the external flash? Thanks.

PM_Dialog
Offline
Last seen:2 days 11 hours ago
工作人员
加入:2018-02-08 11:03
Hi hqf2013,

Hi hqf2013,

If I understood correctly, you would like to store the BD address into the external SPI flash and read it from there? Did I understand correctly?

谢谢,PM_DIalog

hqf2013
Offline
Last seen:6 months 3 days ago
加入:2018-09-13 07:15
Yes. I am trying to do this.

Yes. I am trying to do this.

PM_Dialog
Offline
Last seen:2 days 11 hours ago
工作人员
加入:2018-02-08 11:03
Hi hqf2013,

Hi hqf2013,

Yes, you can store the BD address into the external SPI flash and read it from there. Although, there is not any API like nvds_read_bdaddr_from_da14583_flash(), so you should follow this procedure in the 585 in order to read the BD address from the SPI flash.

Thanks, PM_Dialog

hqf2013
Offline
Last seen:6 months 3 days ago
加入:2018-09-13 07:15
Ok. Thanks.

Ok. Thanks.