Hi
我正在使用具有SDK_1.0.14.1081的DA14683 USB开发套件。我们目前正在评估BLE-SOC，以实现新的发展。我个人喜欢DA14682 / 3。还有很多信息 - 遗憾的是，不经常反映当前版本。这使得很难区分值得读或不值得注意的东西......
I'm able to run the demo project freertos_retarget in RAM. Now I want to do the same from QSPI Flash but I'n not able to load the program into the QSPI-flash. I end up constantly with this error message:
Exception occurred executing command line.
Cannot run program "C:\Projects\DA1468x\utilities\scripts\qspi\program_qspi_jtag_win.launch" (in directory "C:\Projects\DA1468x\projects\dk_apps\templates\freertos_retarget"): CreateProcess error=193, %1 is not a valid Win32 application
In all the tutorials I see the external tools are already configured in SmatSnippets Studio. But In fact that is not right. I needed to septup by my own, not knowing how to do right exactly. This is some kind of frustrating to me.
So are any useful explicit links or hints that my solve my problem, answer my questions?
嗨托马斯唐豪斯，
Can you please indicate the version of SmartSnippets Studio that you are working? Have you built the freertos_retarget. project for QSPI ? In general, you should use built the project for QSPI (Debug or Release : please see the hammer from the SmartSnippets Studio), then you should erase the QSPI flash and after that you should program it. Please let me know if you know further steps in order to burn the QSPI Flash.
Also, I would suggest you to take a look at the below user manual:
//www.wsdof.com/sites/default/files/user_manual_um-b-057_1.pdf
Thanks, PM_Dialog
The SmartSnipptes Studio version is 2.0.10.1468. I reinstalled everything this morning with Ozone_Windows_V270b_x86.exe and Setup_SystemView_V252d.exe. The older versions of the both tools, recommend by SmartSnipptes install-process are now longer available -so I installed the newer releases. And I also built the corresponding QSPI. I also executed the program_qspi_config_win configuration als described in//www.wsdof.com/sites/default/files/user_manual_um-....
I guess my main-mistake was to setup the path to the external tool to:
C:\Projects\DA1468x\utilities\scripts\qspi\program_qspi_jtag_win.launch
instead of
C：\ Projects \ Da1468x \ Utilities \ scripts \ qspi \ program_qspi_jtag.bat.
Now I'm able to execute the program_qspi_jtag.bat command-file but I get this brand new error-message:
......................................
..
.. QSPI编程
..
......................................
命令的语法不正确。
So what can I do?
THX,
Thomas
One of two Problem solved!
我明白,如何configure (see picture) the external tool program_qspi_jtag.bat the upload works now.
The last problem now is to assign / connect the source-code to the QSPI-debug session as it is for the RAM-debug session. The error I get is:
No source available for "0x13ce"
shown in a tab named 0x13ce next to main.c where the first breakpoint is set.
任何提示如何以正确的方式设置QSPI-Debug配置？
THX,
Thomas
Hi Thomas,
Please check the attached screenshot in order to find how the program_qspi_jtag configurations should be.,
Can you please send me a screenshot with the error?
Ensure that you have followed the steps below:
Thanks, PM_Dialog
问题解决了！
加载新固件后重置电路板解决问题！从上面附加的图片帮助了。在我加载* .bin之后，而不是* .elf文件我能够调试代码。但是配置与您的建议有点不同。也许您不使用默认配置中最新版本。所以这是我的program_qspi_jtag的配置：
Location:$ {build_files} $ {workspace_loc} /实用程序/脚本/ qspi/program_qspi_jtag.bat
Working directory:$ {build_files} $ {workspace_loc} /实用程序/脚本/ qspi
争论：“$ {projectloc} / $ {config_name：$ {projectname}} / $ {projectname} .bin”
For Arguments I've used 3 version and all of them worked, which is not quit clear to me why. Number 3 is obvious - just the absolte path to the bin file. Only number 1 and 2 are interessting, because ist is not clear to me what the difference is if --jlink_path is given or not. But nevertheless - I have a solution.
1) "--jlink_path" "${jlink_path}" "${projectLoc}\${config_name:${projectName}}\${projectName}.bin"
2）“$ {projectloc} \ $ {config_name \ $ {projectname}} \ $ {projectname} .bin”
3) "C:\Projects\DA1468x\projects\dk_apps\templates\freertos_retarget\DA14683-00-Debug_QSPI\freertos_retarget.bin"
THX,
Thomas
嗨托马斯唐豪斯，
很高兴您认为您的问题，感谢您的意见。
Thanks, PM_Dialog