DA14683 USB Dev Kit QSPI Flash loading Error

7 posts / 0 new
Last post
Thomas Donhauser
Offline
Last seen: 1 day 8 hours ago
Joined: 2019-10-20 10:45
DA14683 USB Dev Kit QSPI Flash loading Error

Hi

I'm using the DA14683 USB-Development  Kit with SDK_1.0.14.1081. We currently evaluating BLE-SOCs for a new development. I personally like the DA14682/3 most. Also there is tons of information - unfortunately not often reflecting current versions. That makes it hard to distinguish between something that is worthwhile to read it or not...

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?

 

 

 

Device: 
PM_Dialog
Offline
Last seen: 9 hours 2 min ago
Staff
Joined: 2018-02-08 11:03
Hi Thomas Donhauser,

Hi Thomas Donhauser,

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:

https://www.dialog-semiconductor.com/sites/default/files/user_manual_um-b-057_1.pdf

Thanks, PM_Dialog

Thomas Donhauser
Offline
Last seen: 1 day 8 hours ago
Joined: 2019-10-20 10:45
The SmartSnipptes Studio

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 https://www.dialog-semiconductor.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 PROGRAMMING

..

......................................

The syntax of the command is incorrect.

So what can I do?

THX,

Thomas

Thomas Donhauser
Offline
Last seen: 1 day 8 hours ago
Joined: 2019-10-20 10:45
One of two Problem solved!

One of two Problem solved!

After I understood what and how to 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.

Any hint how to setup the QSPI-debug configuration in the right way? 

THX,

Thomas

PM_Dialog
Offline
Last seen: 9 hours 2 min ago
Staff
Joined: 2018-02-08 11:03
Hi 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:

  1. Select freertos_retarget from the “Project Explorer”
  2. Hit the hammer and select DA14683-00- Debug_QSPI
  3. Erase the QSPI Flash be executing the erase_qspi_jtag script
  4. Program the QSPI Flash by executing the program_qspi_jtag script
  5. Reset the board and start the debug procedure.

Thanks, PM_Dialog

Thomas Donhauser
Offline
Last seen: 1 day 8 hours ago
Joined: 2019-10-20 10:45
Problem solved!

Problem solved!

To reset the board after loading the new firmware solved the problem! The picture attached from above helped also. After I loaded the *.bin instead the *.elf file I was able to debug the code. But the configuration is a little bit different to your advice. It maybe that you are not using the lastest version in the default configuration. So this is my config for program_qspi_jtag:

Location: ${build_files}${workspace_loc}/utilities/scripts/qspi/program_qspi_jtag.bat

Working directory: ${build_files}${workspace_loc}/utilities/scripts/qspi

Argument: "${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

PM_Dialog
Offline
Last seen: 9 hours 2 min ago
Staff
Joined: 2018-02-08 11:03
Hi Thomas Donhauser,

Hi Thomas Donhauser,

Glad that you figured your issue out and thanks for your inputs.

Thanks, PM_Dialog