PLT making bin.cached file for DA14681-01 (AE) & SUOTA

⚠️
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.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
7 posts / 0 new
Last post
Mon, 2017-10-23 19:28
#1
kylekclee
Offline
Last seen:3 years 2 weeks ago
加入:2017-10-10 19:08
PLT making bin.cached file for DA14681-01 (AE) & SUOTA

I was able to flash and get the pxp_reporter_681_01.bin.cached onto the DA14681-01 dev board with the PLT and file from DA1458x_DA1468x_PLT_v_4.1.0.132\executables\binaries.

But I wasn't sure how to get my own bin to flash onto the dev board. I tried the bin2img script with the documentation found in UM-B-041_DA1458x_DA1468x_Production_Line_Tool_4v0.pdf but the options only allowed for DA14681-00(AD)(SEE IMAGE ATTATCHED) . Are there updated instructions for flashing the DA14681-01(AE) or other methods to use?

I'm also interested in flashing SUOTA_loader along with the file, if there are instructions for those as please point me in that direction

Thank you,
Kyle

Attachment:
PDF iconbin2img.pdf
Device:
DA1468x
Tue, 2017-10-24 16:19
MT_dialog
Offline
Last seen:3 months 3 days ago
Staff
加入:2015-06-08 11:34
Hi kylekclee,

Hi kylekclee,

The bin2image.exe takes the argument AD (or the other arguments) in order to construct an image for the AD silicon version of the SoC if that argument is not passed then the tool will construct the image using the default value which is the AE silicon, this is what the command line mentions when it refers to the different headers.

Regarding burning the suota loader along with your image with the PLT, i am checking with the PLT expert on that, i will let you know as soon as i ve got that info.

Thanks MT_dialog

Accepted answer
Fri, 2017-10-27 01:19
(Reply to #2)
kylekclee
Offline
Last seen:3 years 2 weeks ago
加入:2017-10-10 19:08
Thank you for the response,

Thank you for the response, it worked.
Have you gotten any info from the PLT expert?

Fri, 2017-10-27 16:35
(Reply to #3)
MT_dialog
Offline
Last seen:3 months 3 days ago
Staff
加入:2015-06-08 11:34
Hi kylekclee,

Hi kylekclee,

Sorry, not yet, still waiting for a suggestion from the experts.

Thanks MT_dialog

Thu, 2017-11-02 17:01
(Reply to #4)
MT_dialog
Offline
Last seen:3 months 3 days ago
Staff
加入:2015-06-08 11:34
Hi kylekclee,

Hi kylekclee,

Unfortunatelly there is no tool or a fixed method to have the entire structure of a SUOTA enabled device in one single binary in order to be burned with the PLT tool, what is suggested though as a work around is the following procedure.

  • Burn the SUOTA enabled fw in the qspi flash (along with the bootloader and the relevant SUOTA headers) using the suota_initial_flash_jtag_win script provided with the SDK.
  • After burning the flash you can use the Smart Snippets Toolbox and the QSPI Programmer in order to Read the data from the QSPI flash and then hit the "Save" button in order to save the entire flash in a single binary file.
  • Then you can use that file which will include all the appropriate info for a SUOTA enabled image.

Thanks MT_dialog

Thu, 2017-11-02 17:51
(Reply to #5)
kylekclee
Offline
Last seen:3 years 2 weeks ago
加入:2017-10-10 19:08
I did something similar.

I did something similar. After looking at the developer guide for suota, the guts of suota_initial_flash_jtag_win script and compared it to the QSPI memory reading from smart snippets toolbox on a hex editor

I came up with these 3 parts to flash on the PLT:

1.I took the ble_suota_loader.bin and ran the bin2image.exe and flashed that to 0x00000
2. Made an image file from mkimage.exe and took the first 36 bytes from the image and flashed it to 0x1F000 ( I only kept the first 36 bytes to copy the smart studio memory layout)
3. Flashed the main firmware built with SUOTA enabled and did NOT run it through the bin2image.exe and flashed it to 0x20000

These 3 files took about 36 seconds to flash on the PLT versus 3 minutes and 21 seconds using the entire binary file from smart snippets

Accepted answer
Fri, 2017-11-03 16:33
(Reply to #6)
MT_dialog
Offline
Last seen:3 months 3 days ago
Staff
加入:2015-06-08 11:34
Hi kylekclee,

Hi kylekclee,

谢谢指示您的解决方案,我吃晚饭pose that this will help quite a few users. The reason that the method suggested is taking quite a long time is because you actually burn the entire flash instead of portions at specific offsets.

Best Regards MT_dialog