嗨对话框，
正如我们所知，只有一个小于32k的垃圾箱文件。
The size of my bin file is 32,652 is less than 32KB and is very close to 32KB.
but it can't be burned to DA14580 OTP.
我们正在优化有限公司de size.
Any idea about the issue at the moment ? thanks!
Device:
⚠️
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.
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.
Thu, 2017-10-19 04:50
＃1
Less than 32KB Bin file but can't program DA14580 OTP
添加对话框PLT工具的日志文件。谢谢！
--------------------------------------------------------------------------
time> | | |
##########################################################################################################################
|16:14:53.439 |DUT_UDLL_FW_DOWNLOAD_INIT | STARTED |UDLL firmware download initialized. Firmware is=[D:\DA1458x_DA1468x_PLT_v_4.1.0.132\DA1458x_DA1468x_PLT_v_4.1.0.132\executables\binaries\flash_programmer_580.bin].
|16:14:53.486 |DUT_UDLL_FW_DOWNLOAD_START | STARTED |UDLL firmware download started OK. Firmware is=[D:\DA1458x_DA1468x_PLT_v_4.1.0.132\DA1458x_DA1468x_PLT_v_4.1.0.132\executables\binaries\flash_programmer_580.bin].
| 16：14：55.045 | dut_udll_fw_download_ok |通行证| UDLL固件下载OK。固件是= [D：\ da1458x_da1468x_plt_v_4.1.0.132 \ da1a58x_da1468x_plt_v_4.1.0.132 \可执行文件\二进制文件\ flash_programmer_580.bin]。
| 16：14：55.056 | dut_udll_fw_download_ok |通行证| UDLL固件下载OK。固件是= [D：\ da1458x_da1468x_plt_v_4.1.0.132 \ da1a58x_da1468x_plt_v_4.1.0.132 \可执行文件\二进制文件\ flash_programmer_580.bin]。
|16:14:55.069 |DUT_UDLL_FW_VER_GET_INIT | STARTED |UDLL 'firmware version get' operation initialized.
|16:14:55.080 |DUT_UDLL_FW_VER_GET_STARTED | STARTED |UDLL 'firmware version get' operation started.
|16:14:55.093 |DUT_UDLL_FW_VER_GET_OK | PASS |UDLL 'firmware version get' operation ended OK. UDLL version=[v_4.1.0.132], Firmware version=[v_5.0.4_PLT_v4.1]
|16:14:55.169 |DUT_UDLL_OTP_IMG_WR_INIT | STARTED |OTP image write operation initialized. Image to write is [C:\Users\909552\Desktop\ble_boot_2017092820.bin].
| 16：14：55.169 | dut_udll_otp_img_wr_started |启动| OTP图像写操作已开始。写入编写的图像是[C：\ Users \ 909552 \ Desktop \ ble_boot_2017092820.bin]。
| 16：14：55.185 | DUT_UDLL_OTP_IMG_WR_FAILED |失败| OTP图像写入操作失败。图像是[C：\ Users \ 909552 \ Desktop \ ble_boot_2017092820.bin] .current设备状态= [194]。
| 16：14：55.185 | DUT_UDLL_OTP_IMG_WR_FAILED |失败| OTP图像写入操作失败。图像是[C：\ Users \ 909552 \ Desktop \ ble_boot_2017092820.bin] .current设备状态= [194]。
嗨Jacky_SZ,
The OTP totals in 32K bytes, which means 32.768 bytes, out of those bytes you should remove the 256 bytes which is the OTP header so the total amount of memory that can be used by the image is 32.512 bytes, so you should check the fw that you have in order to save 140 bytes in order to reach the maximum of the OTP, i am not aware what its been used in your project and how you can save some space. In general from the SDK side there aren't much to do since the code is quite optimized, so will have to check what modules you have used and what can be ommited, for example if you are not using the TRNG module you can undefine it and that will save you some space (but there will be no trully random number generation). Additionally in the user_modules_config.h file you there are some swicthes in order to include or remove some dialog API's you can remove some of those modules and apply your minimal API's in order to save some space. Last i suppose that the compilation is done with the CFG_DEVELOPMENT_DEBUG undefined, since this will occupy additional space in your image.
Thanks MT_dialog
Does the space 32512 bytes include the NVDS used by application? Now my project built image size is 32440(CODE:29652,RO-DATA 2308,RW-DATA 168), and my project is based on Dialog official ANCS sample project. I can now burn my image into my board without any problem. Why? I suppose 32440 is larger than 32768-256(header)-256(NVDS) = 32256.
Hi cgha,
Can you please indicate the chip and the SDK that you are using in your product? Is it DA14580 and SDK5.0.4? Also, have you bunt the OTP with the application code? Or you are booting from System-RAM or external SPI Flash?
You can also create a new forum thread as this one is very old and closed.
Thanks, PM_Dialog
Yes, my application is based on sdk 5.0.4 and DA14580-01, the image is burned into on chip OTP .
Hi cgha,
It’s expected that you are able to burn the 32256 bytes image in the OTP, as the NVDS is a part of the image. The maximum image that you can burn is 32.512 bytes (32K – 256 bytes (header) ).
Thanks, PM_Dialog
I got it, Thanks!