The DA1468x SDK driver subsystem currently supports a specific set of QSPI flash devices and the MX25R1635F is not supported. It provides, however, the capability to add support for other flash devices as well. I would highly suggest you to have a look at the10.2.1.7 Adding support for a new flash device一部分UM-B-044用户手册:DA1468X软件平台参考(HTML)user manual. You can download this user manual form our DA1468x support portal. Did you follow the procedure described in this document? Also, can you please clarify that it is working well? Does the device boot correctly? If you read the first address of flash memory0x08000000.then you must extract theQQ.价值。要执行此操作,请运行调试会话并暂停代码执行。然后在“内存浏览器”显示窗口中(如果未显示“转到”菜单工具“窗口 - >”showView-> MemoryBrowser“编写上述地址。这是一种检查闪存的正确功能的方法。
嗨,pm_dialog 我认为我们已经完成了“UM-B-044用户手册:DA1468X软件平台参考”中描述的必要过程--10.2.1.7为新的闪存设备部分添加支持“。我们所做的是如下: 1. prepared "qspi_mx25r1635f.h" , and added several macro such as "#define dg_configFLASH_MANUFACTURER_ID MACRONIX_ID ... #define dg_configFLASH_HEADER_FILE "qspi_mx25r1635.h"..." in "custom_config_qspi.h" of , and also added them in "custom_config.h" of . Relative config file please check attachment file.
2. Build the "uartboot" project
3. Build the "cli_programmer" project , "libprogrammer" project
bootloader file not specified, using internal uartboot.bin
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00001000 Writing to address: 0x00000000 offset: 0x00001000 chunk size: 0x00001000 Writing to address: 0x00000000 offset: 0x00002000 chunk size: 0x00001000 写作到地址:0x00000000偏移:0x00003000块大小:0x00001000 。。。 写作到地址:0x00000000偏移量:0x00018000块大小:0x00001000 Writing to address: 0x00000000 offset: 0x00019000 chunk size: 0x00000a70 Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00000002 done.
................................................................................................................... 。。 。。FINISHED 。。 ...................................................................。...................。。。。。。。。。 //////// //////////////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////////////////////////////////// However , it can't boot correctly , stucking in printf"DA14681-01...DA14681-01..." . I think that is the sdk1.0.6 can't support for adding new flash.
By the way , why sdk1.0.12 download chunk size is 0x2000, but sdk1.0.6 chunk size is 0x1000. And according to "AN-B-045_QSPI_loader_SupportingFiles" , DA14681 supported MX25RXX35F series QSPI flash device , why we still should add config file to support it?
嗨,pm_dialog 1. SDK1.0.6:成功下载,但未成功启动。 SDK1.012: Download unsuccessfully, can't boot. 2. While using SDK1.0.6 , after burnning image , it can't target the cpu when runing a debug session. So we can't locate where the code gets stuck. And faild to read first address of flash memory 0x08000000. 3.我们无法使用Smart Scippets Toolbox读取/编写MX25R1635F。 谢谢!
We have never tested the mx25r1635f flash, I a have already mentioned. However, I will ask the team if there is any problem with the latest version of SKS and the toolbox, and I will get back to you as soon as I have a proper answer.
古兴,
The DA1468x SDK driver subsystem currently supports a specific set of QSPI flash devices and the MX25R1635F is not supported. It provides, however, the capability to add support for other flash devices as well. I would highly suggest you to have a look at the10.2.1.7 Adding support for a new flash device一部分UM-B-044用户手册:DA1468X软件平台参考(HTML)user manual. You can download this user manual form our DA1468x support portal. Did you follow the procedure described in this document? Also, can you please clarify that it is working well? Does the device boot correctly? If you read the first address of flash memory0x08000000.then you must extract theQQ.价值。要执行此操作,请运行调试会话并暂停代码执行。然后在“内存浏览器”显示窗口中(如果未显示“转到”菜单工具“窗口 - >”showView-> MemoryBrowser“编写上述地址。这是一种检查闪存的正确功能的方法。
Thanks, PM_Dialog
嗨,pm_dialog
我认为我们已经完成了“UM-B-044用户手册:DA1468X软件平台参考”中描述的必要过程--10.2.1.7为新的闪存设备部分添加支持“。我们所做的是如下:
1. prepared "qspi_mx25r1635f.h" , and added several macro such as "#define dg_configFLASH_MANUFACTURER_ID MACRONIX_ID ... #define dg_configFLASH_HEADER_FILE "qspi_mx25r1635.h"..." in "custom_config_qspi.h" of , and also added them in "custom_config.h" of . Relative config file please check attachment file.
2. Build the "uartboot" project
3. Build the "cli_programmer" project , "libprogrammer" project
4. Build application project and do "program_qspi_jtag_win" , but the console print follow info:
"///////////////////////////////////////////////////////////////////////////////////////////////////////////////////
配置保存到C:\ Users \ Admini〜1 \ AppData \ Local \ Temp \ CFG_2779.INI文件。
e:\ debugproject \ da1468x_sdk_btle_v_1.0.8_prj \ utilities \ scripts \ qspi>“.. \ .. \ .. \ .. \ .. \ .. \ cli_programmer.exe”--cfg“c:\ users \ admini〜1 \ appdata \ local \ temp\ cfg_2779.ini“ - prod-id da14681-01 gdbserver write_qspi_exec”e:\ debugproject \ da1468x_sdk_btle_v_1.0.8_prj \ projects \ dk_apps \ templates \ freertos_retarget \ da14681-01-refoy_qspi \ freertos_retarget.bin“
cli_programmer 1.23
Copyright (c) 2016 Dialog Semiconductor
bootloader file not specified, using internal uartboot.bin
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00002000
Verify writing to qspi address 0x0 failed. Retrying ...
写入QSPI失败。中止。
Write executable failed: unknown error (1)
“”//////// ////////////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////////////////////////
我们在SDK1.0.12上进行了上面的测试。
But we can successfully download the image on sdk1.0.6 without changing driver subsystem (with w25q08e default driver), console info on sdk1.0.6:
//////// ////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Script file read successfully.
Processing script file...
j-link连接尚未建立,但命令要求。
Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled Apr 21 2017 11:08:06
Hardware version: V9.40
S/N: 59410355
License(s): RDI, GDB, FlashDL, FlashBP, JFlash
vtref = 3.332v.
睡眠(1000)
Selecting 4000 kHz as target interface speed
选择SWD作为当前目标接口。
目标连接未建立,但命令要求。
Device "CORTEX-M0" selected.
Found SW-DP with ID 0x0BB11477
No AP preselected. Assuming that AP[0] is the AHB-AP
AP-IDR: 0x04770021, Type: AHB-AP
AHB-AP ROM:0xE00FF000(基本ADDR。第一rom表)
Found Cortex-M0 r0p0, Little endian.
fpUnit:4代码(BP)插槽和0个字幕插槽
CoreSight components:
ROMTbl[0] @ E00FF000
romtbl [0] [0]:e000000,cid:b105e00d,pid:000bb008 scs
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 000BB00A DWT
Romtbl [0] [2]:E0002000,CID:B105E00D,PID:000BB00B FPB
Cortex-M0已识别。
写DeadBeef - > 07FD0000
写DeadBeef - > 07FD0004
写DeadBeef - > 07FD0008
Writing DEAD10CC -> 07FD000C
Writing 00000001 -> 400C3050
睡眠(1000)
重置延迟:0毫秒
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
PC = 07F01E8A, CycleCnt = 00000000
R0 = 00000008,R1 = 50003300,R2 = 00000001,R3 = E000E1FF
R4 = 00000002,R5 = 00000000,R6 = 00000004,R7 = 00000000
R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF
r12 = ffffffff.
SP(R13)= 07FE0410,MSP = 07FE0410,PSP = FFFFFFFFC,R14(LR)= 07F00443
XPSR = 01000000: APSR = nzcvq, EPSR = 01000000, IPSR = 000 (NoException)
CFBP = 00000000, CONTROL = 00, FAULTMASK = 00, BASEPRI = 00, PRIMASK = 00
Script processing completed.
cli_programmer 1.22
Copyright (c) 2016 Dialog Semiconductor
bootloader file not specified, using internal uartboot.bin
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00001000
Writing to address: 0x00000000 offset: 0x00001000 chunk size: 0x00001000
Writing to address: 0x00000000 offset: 0x00002000 chunk size: 0x00001000
写作到地址:0x00000000偏移:0x00003000块大小:0x00001000
。。。
写作到地址:0x00000000偏移量:0x00018000块大小:0x00001000
Writing to address: 0x00000000 offset: 0x00019000 chunk size: 0x00000a70
Writing to address: 0x00000000 offset: 0x00000000 chunk size: 0x00000002
done.
...................................................................................................................
。。
。。FINISHED
。。
...................................................................。...................。。。。。。。。。
//////// //////////////////////////////////////////////////////////////////////////////////// //////////////////////////////////////////////////////////////////////////////////////////////
However , it can't boot correctly , stucking in printf"DA14681-01...DA14681-01..." . I think that is the sdk1.0.6 can't support for adding new flash.
等你回答,谢谢!
By the way , why sdk1.0.12 download chunk size is 0x2000, but sdk1.0.6 chunk size is 0x1000.
And according to "AN-B-045_QSPI_loader_SupportingFiles" , DA14681 supported MX25RXX35F series QSPI flash device , why we still should add config file to support it?
古兴,
对不起,但我有点混淆了你的描述。当您使用SDK1.0.12时,您可以编程MX25R1635F SPI Flash,但DA14680无法启动?但是当您使用SDK SDK1.0.6时,您无法编程SPI Flash?请注意,当前版本的SDK为1.0.14版。您正在处理的SDK版本是非常旧的版本O SDK,您不再支持它们了。因此,我强烈建议您进入最新版本的OD SDD并从我们的支持门户下载它。您能否澄清代码卡在哪里?DIDI您按照我之前帖子中描述的程序进行操作,以确保SPI Flash正常运行?此外,您可以使用智能代码段Toolbox读/写SPI Flash吗?
Thanks, PM_Dialog
嗨,对话
您能否向我们提供有关如何在DA14681上使用MX25R1635F的一些建议?
嗨,pm_dialog
1. SDK1.0.6:成功下载,但未成功启动。
SDK1.012: Download unsuccessfully, can't boot.
2. While using SDK1.0.6 , after burnning image , it can't target the cpu when runing a debug session. So we can't locate where the code gets stuck. And faild to read first address of flash memory 0x08000000.
3.我们无法使用Smart Scippets Toolbox读取/编写MX25R1635F。
谢谢!
古兴,
Could you please let us know if you still have any issue with the SPI flash driver?
Thanks, PM_Dialog
Hi ,dialog
问题仍然存在。使用SmartSinpet时,SDK1.0.6可以刻录MX25R1635F,但在SDK1.0.12中失败。使用软件版本为4.4.3.1420时,它可以读取或写入闪光灯,但在较新版本4.8.3.1804中失败。似乎只有旧的SDK或工具箱可以支持MX25R1635F。
古兴,
We have never tested the mx25r1635f flash, I a have already mentioned. However, I will ask the team if there is any problem with the latest version of SKS and the toolbox, and I will get back to you as soon as I have a proper answer.
Thanks, PM_Dialog