HI dialog,
I am currently using PLT broad for production testing, but keep getting "INTERNAL SYSTEM ERROR" when PLT doing erase flash operation, if I don't select erase flash option, write flash is ok and my broad can boot. Also, the broad actually can erase the flash when I check the flash using jlink, so what would be to cost this problem, please help, thank you.
And for the broad, I only connected the RX TX VBAT and GND
here is the log from the software and params.xml in Attachment
just find out there are V4.3, but still have error
Software: DA1458x/DA1468x Production Line
Software version: v_4.3.0.310
PLTD DLL version: v_4.3.0.310
PDLL Version: v_4.3.0.310
UDLL Version: v_4.3.0.310
Production test BLE firmware version:
Production test APP firmware version:
Flash programmer firmware version: 0003_PLT_v4.3
Date: 2018-08-17
Start Time: 17:07:27.341
End Time: 17:07:34.565
Station ID: Test_station_1
Device ID: 2
COM port: 59
DUT IC: DA14681-01
COM port: 0
BD address: 00:00:00:00:00:05
| | | |
##########################################################################################################################
|17:07:30.829 |DUT_UDLL_FW_DOWNLOAD_INIT | STARTED |UDLL firmware download initialized. Firmware is=[D:\WORK\DA1458x_DA1468x_PLT_v_4.3.0.310\executables\binaries\uartboot_68x.bin].
|17:07:30.850 |DUT_UDLL_FW_DOWNLOAD_START | STARTED |UDLL firmware download started OK. Firmware is=[D:\WORK\DA1458x_DA1468x_PLT_v_4.3.0.310\executables\binaries\uartboot_68x.bin].
|17:07:33.894 |DUT_UDLL_FW_DOWNLOAD_OK | PASS |UDLL firmware downloaded OK. Firmware is=[D:\WORK\DA1458x_DA1468x_PLT_v_4.3.0.310\executables\binaries\uartboot_68x.bin].
|17:07:33.895 |DUT_UDLL_FW_DOWNLOAD_OK | PASS |UDLL firmware downloaded OK. Firmware is=[D:\WORK\DA1458x_DA1468x_PLT_v_4.3.0.310\executables\binaries\uartboot_68x.bin].
|17:07:33.897 |DUT_UDLL_FW_VER_GET_INIT | STARTED |UDLL 'firmware version get' operation initialized.
|17:07:33.910 |DUT_UDLL_FW_VER_GET_STARTED | STARTED |UDLL 'firmware version get' operation started.
|17:07:33.955 |DUT_UDLL_FW_VER_GET_OK | PASS |UDLL 'firmware version get' operation ended OK. UDLL version=[v_4.3.0.310], Firmware version=[0003_PLT_v4.3]
|17:07:33.957 |DUT_UDLL_QSPI_INIT_INIT | STARTED |QSPI initilization operation initialized.
|17:07:33.970 |DUT_UDLL_QSPI_INIT_STARTED | STARTED |QSPI initilization operation started.
|17:07:34.004 |DUT_UDLL_QSPI_INIT_FAILED | FAIL |QSPI initilization operation FAILED. Jedec ID is [0xef, 0x60, 0x17].Current device status=[227].
|17:07:34.006 |DUT_UDLL_QSPI_INIT_FAILED | FAIL |QSPI initilization operation FAILED. Jedec ID is [0xef, 0x60, 0x17].Current device status=[227].
Hello,
Q1: What68x-deviceis used ... what isprintedon the device?
Q2: Whatwiring/connections are made to your application-board? e.g. Tx 1.3 and Rx 2.3 ... where Vbat?
Q3: can youdisablethe debugger-settings ... these can have negative impact in the timing of the PLT when using a slower PC.
Q4:选择的生产tests' in the TAB 'General'
Thanks.
//HM
p.s.1 after testing please send Params.xml again and the log-file with errors (if there are any ...).
p.s.2 new update of PLT-software is available on the website (V4.3)
thank you
A1: I am using 14681-01 with 8M of ext FLASH
A2: I am using Tx 1.3 and Rx 2.3
A3: already disable
A4: Production tests run ok
param and log file attached
after the update, I am getting QSPI initilization operation FAILED. Jedec ID is [0xef, 0x60, 0x17].Current device status=[227].
and I have test my 14681 Development Kit broad, no error, saying QSPI initilization operation ended OK. Jedec ID is [0xef, 0x60, 0x14].
after a bit of research, 0x17 and 0x14 is related to flas size, which Development Kit broad is using 1Mbit flash and I am using 8Mbit flash, so the PTL can't program a broad with 8Mbit flash? I can program it using toolbox with both jlink and UART port.
it get worst actually after update, at least I can program the flash with version 4.2, now I can only do product test....please help, thnaks
Hello,
Q1:Can you do the same test using V4.3-solftware?
Q2:What kind of QSPI-type-number are you using?
The error is a 'Jedec ID error', which is given when a QSPI-memory is used which is not recognized.
FW can be adapted, so that the PLT works on your QSPI.
//HM
hi,
I am already using V4.3, so it give me this error.
I am using winbond's flash, W25Q80 8Mbit one, but some is W25Q64 64Mbit, can you guys make the FW support all winbond's flash which larger than 1M? like...only check Jedec ID 0xef , 0x60..., anyway, thank you very much
hi,
just checked, we use winbond w25q64 64Mbit and w25q80 8Mbit QSPI FLASH, but still I will be grateful if you guys can make it support a range of flash size, thank you very much!
HI dialog,
any update for the problem?
Hi andoridfm2013,
We are searching your request and we will get back to you as soon as possible.
Thanks, PM_Dialog
hi Dialog Dev.
any update about the FW for the PLT? We are close to do production at factory, we need the PLT broad working, thank you.
Hi Dialog Dev.
it is almost two week since I have the problem, I don't understand the difficultly to change uartboot_68x.bin 's Jedec ID checking, which I don't understand too, why you will have such Jedec ID restriction even I use the same brand of flash but just different size? this is a production tool, a factory tool, if I can do it in SmartSnippets Toolbox with Jlink, why I can't using that in such professional tools?
Moreover, this Jedec ID error didn't exist in version 4.2, I can write program to flash, but as in the first post, it have other problem. Can you please fix this bug faster? I love this $850 USD production tools, the testing function is amazing, save me a lot of time, but just one utmost important function, program burning, is unusable to me at this point. I am still looking for the firmware update or any status upon this problem.
Hi andoridfm2013,
Sorry for the delay.
InUM-B-040in chapter4.4.2Building the DA1468x Memory Programmer Firmwareis explained.
A newuartboot.binfile has to be made, with different QSPI-settings. This bin-file is created out of the _SDK_1.0.10.1072 (or newer).
The new uartboot.bin isreplacingthe old one, located in the PLT-firmware (under ... / executables/binaries/...).
//HM
HI Dialog_HM,
ok, follow the PDF UM-B-040, copy the file in PLT source folder to project "uartboot" and change ID in qspi_w25q80ew.h, the PLT software can use it without error, Thank you~
Hi andoridfm2013,
高兴你找到你的问题able to recognize the QSPI-memory. I have also found areadme.md-file in the SDK 1.0.2.1078 part of theuartboot/sdk. The readme.md is copied in a pdf-file and you can find it attached.
Thanks, PM_Dialog