Hi,
This is a long shot... but will the PLT for any reason cause a qspi image write to fail (code 168)?
I programmed my board that is using a da14681-01 using the uart and cli_programmer.exe and it works just fine.
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.
Here is my log file:
Software: DA1458x/DA1468x Production Line
Software version: v_4.2.0.160
PLTD DLL version: v_4.2.0.160
PDLL Version: v_4.2.0.160
UDLL Version: 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
End Time: 11:26:30.166
Station ID: Test_station_1
Device ID: 1
COM port: 136
BD address: 00:00:00:00:00:12
| | | |
##########################################################################################################################
|11:26:23.948 |DUT_UDLL_FW_DOWNLOAD_INIT | STARTED |UDLL firmware download initialized. Firmware is=[C:\Users\kyle\Desktop\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 firmware downloaded 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.821 |DUT_UDLL_FW_DOWNLOAD_OK | PASS |UDLL firmware downloaded 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.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 | PASS |UDLL 'firmware version get' operation ended OK. UDLL version=[v_4.2.0.160], Firmware version=[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 | STARTED |QSPI image write operation started. QSPI image write test name=[header]. Image to write is [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].
Thank you in advance,
Kyle
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,
The steps I modified the uartboot.bin to add memory support are at the bottom but I also followed section4.4.2ofUM-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-DA15xxxthen recompiled uartboot.bin.
I put the output binary inProdTool\DA1458x_DA1468x_PLT_v_4.2.0.160\executables\binariesand renamed it 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) Copy qspi_mx25r8035.h into the sdk: sdk\memory\include (Project Folder) ; The physical location is \sdk\bsp\memory\include
2) Open custom_config_qspi.h and before #include "bsp_defaults.h" include the following lines of code:
#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_DENSITY 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,
Kyle
Hi kylekclee,
As far as i can tell the steps are proper, and if you followed the directions from the 4.4.2 paragraph on the UM-B-040 Production Line Tools Libraries, then you have applied the proper changes on the PLT in order to support the flash, so if the CLI programmer was able to communicate with the specified flash during development then i dont think that it is a flash issue (please verify that with the .h file for the flash and that the cli_programmer operates as it should when used for development). Can you please share the qspi_mx25r8035.h file that corresponds to the flash that you are using and check if we have an identical flash to give it a try with our h/w and the PLT? Also since you have compiled the uartboot.bin for the PLT file can you also share that as well ?
Thanks MT_dialog