Hi,
This is a long shot... but will the PLT for any reason cause a qspi image write to fail (code 168)?
我编写了使用UART和CLI_Programmer.exe的DA14681-01的电路板，它运行正常。
I then tried to transition using the PLT but I keep getting qspi image write failed. I noticed when I try the DA14681-00 it does get passed the write but im not using that hardware.
I use the the plt with same setup to flash code onto the dev board for da14681-01 just fine.
这是我的日志文件：
软件：DA1458X / DA1468X生产线
Software version: v_4.2.0.160
PLTD DLL版本：v_4.2.0.160
PDLL Version: v_4.2.0.160
UDLL版本：v_4.2.0.160
生产测试祝福firmware version:
Production test APP firmware version:
Flash programmer firmware version: 00.03
Date: 2018-01-25
Start Time: 11:26:20.080
结束时间：11：26：30.166
Station ID: Test_station_1
Device ID: 1
COM港口：136
BD地址：00：00：00：00：00：12
||||
#####################################################################################################
| 11：26：23.948 | dut_udll_fw_download_init |启动| UDLL固件下载初始化。固件是= [C：\用户\ kyle \桌面\ prodtool \ da1458x_da1468x_plt_v_4.2.0.160 \ executables \ binaries \ uartboot_681_01.bin]。
|11:26:23.973 |DUT_UDLL_FW_DOWNLOAD_START | STARTED |UDLL firmware download started OK. Firmware is=[C:\Users\kyle\Desktop\ProdTool\DA1458x_DA1468x_PLT_v_4.2.0.160\executables\binaries\uartboot_681_01.bin].
| 11：26：28.814 | dut_udll_fw_download_ok |通行证| UDLL固件下载OK。固件是= [C：\用户\ kyle \桌面\ prodtool \ da1458x_da1468x_plt_v_4.2.0.160 \ executables \ binaries \ uartboot_681_01.bin]。
| 11：26：28.821 | dut_udll_fw_download_ok |通行证| UDLL固件下载OK。固件是= [C：\用户\ kyle \桌面\ prodtool \ da1458x_da1468x_plt_v_4.2.0.160 \ executables \ binaries \ uartboot_681_01.bin]。
|11:26:28.829 |DUT_UDLL_FW_VER_GET_INIT | STARTED |UDLL 'firmware version get' operation initialized.
|11:26:28.837 |DUT_UDLL_FW_VER_GET_STARTED | STARTED |UDLL 'firmware version get' operation started.
| 11：26：28.890 | DUT_UDLL_FW_VER_GET_OK |通过| UDLL“固件版本获取”操作结束了确定。UDLL版本= [v_4.2.0.160]，固件版本= [00.03]
|11:26:28.897 |DUT_UDLL_QSPI_ERASE_INIT | STARTED |QSPI erase operation initialized. QSPI erase test name=[Erasing boot].
|11:26:28.905 |DUT_UDLL_QSPI_ERASE_STARTED | STARTED |QSPI erase operation started. QSPI erase test name=[Erasing boot]. Erase QSPI from address [0] for [16534] bytes.
|11:26:29.146 |DUT_UDLL_QSPI_ERASE_OK | PASS |QSPI erase operation ended OK. QSPI erase test name=[Erasing boot].
|11:26:29.154 |DUT_UDLL_QSPI_IMG_WR_INIT | STARTED |QSPI image write operation initialized. QSPI image write test name=[header]. Image to write is [C:\Users\kyle\Desktop\pingLatest\truncatedAppImage.bin].
| 11：26：29.162 | dut_udll_qspi_img_wr_started |启动| QSPI图像写操作开始。QSPI图像写入测试名称= [标题]。编写的图像是[c：\ users \ kyle \ desktop \ pinglatest \ truncatedappimage.bin]。
|11:26:29.574 |DUT_UDLL_ACTION_RESPONSE_ERROR | ERROR |UDLL device responded with error. QSPI image write test name=[header]. Image is [C:\Users\kyle\Desktop\pingLatest\truncatedAppImage.bin].Current device status=[120].
|11:26:29.583 |DUT_UDLL_QSPI_IMG_WR_FAILED | FAIL |QSPI image write operation FAILED. QSPI image write test name=[header]. Image is [C:\Users\kyle\Desktop\pingLatest\truncatedAppImage.bin].Current device status=[120].
先感谢您，
凯尔
Im using a different flash chip. How Do I add support for new flash chip with the plt?
Hi kylekclee,
Well, if you are using a different flash on the board that you are trying to program, then most probably you dont use the default cli_programmer (the cli_programmer used as downloaded from the SDK) but a modified version of the cli_programmer that will include the flash that you are using on your device. In order to support a new flash you should add the flash in the uartboot project and then rebuild the cli_programmer (the cli_programmer will inlcude the updated image of the uartboot that will include your flash). So what you will have to do is add the flash in the uartboot project rebuild the cli_programmer (building the cli_programmer will first build its dependencies which includes the uartboot). Are the above valid ? Have you performed any changes to the uartboot.bin during development in order to program your flash ? If so which flash you are using and can you share the additions made for supporting this flash ?
Thansk MT_dialog
Hi,
我修改了UartBoot.bin以添加内存支持的步骤位于底部，但我也遵循部分4.4.2的UM-B-040_DA1458x_DA1468x_Production_Line_Tool_Libraries_4v2.pdf(Screen shot attatched) and added the additional FW files located inProdTool\DA1458x_DA1468x_PLT_v_4.2.0.160\source\production_line_tool\fw_files\DUT\DA1468x-DA15xxx然后重新编译Uartboot.bin。
I put the output binary inprodtool \ da1458x_da1468x_plt_v_4.2.0.160 \可执行文件\二进制文件并重命名为UartBoot_681_01.bin。
I didnt recompile the cli_programmer when testing to see if I correctly made the uartbootbin . I was using someones previous cli_programmer. I will try compile cli_programmer and program the board that to verify I did the uartboot.bin correctly
***********STEPS FOR UART BOOT BIN**********
1）将qspi_mx25r8035.h复制到sdk：sdk \ memory \ criness（Project文件夹）;物理位置是\ sdk \ bsp \ memory \ crompite
2）打开custom_config_qspi.h和#include“bsp_defaults.h”之前包含以下代码行：
#define dg_configflash_header_file“qspi_mx25r8035.h”
#define dg_configflash_manufacturer_id macronix_id.
#define dg_configFLASH_DEVICE_TYPE MX25R8035_SERIES
#define dg_configflash_deny mx25r8035_size.
3) Open qspi_automode.c
a) go to line 88 and add #include "qspi_mx25r8035.h"
b) go to line 102 and add &flash_mx25r8035_config to the flash_config_table[]
Thank you,
凯尔
Hi kylekclee,
据我所知，步骤是合适的，如果您从UM-B-040生产线工具库上的4.4.2段落遵循的指示，那么您已经在PLT上应用了正确的更改以支持闪存，因此如果CLI程序员能够在开发期间与指定的闪存进行通信，那么我不认为这是一个闪存问题（请使用闪存的.h文件验证，并且CLI_Programmer在使用时运行发展）。您能分享与您正在使用的闪存相对应的QSPI_MX25R8035.H文件，并检查我们是否有相同的闪光灯，以便尝试使用我们的H / W和PLT？此外，由于您已编译了PLT文件的UartBoot.bin，您也可以分享吗？
Thanks MT_dialog