DA1469x program_qspi.py output

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
11 posts / 0 new
Last post
toshiyo
Offline
Last seen:1 year 7 months ago
加入:2019-02-28 19:04
DA1469x program_qspi.py output

Dear Dialog_PM,

I am trying to run the script program_qspi.py. The script ran successfully, however it gave me the following output : "No image, no header selected. Nothing to do." What does this mean and is this output expected?

Thank you for your time.

Device:
PM_Dialog
Offline
Last seen:6 hours 26 min ago
Staff
加入:2018-02-08 11:03
Hi toshiyo,

Hi toshiyo,

The safest way to program the DA1469x is to run the program_qspi_xxxx scripts through SmartSnipptes studio. Please check the attached snapshots. To access configuration menu alternatively navigate to Run > External Tools

  1. program_qspi_config : This will open a pop up window with a summary of the current QSPI configuration and

supported device. So, choose the DA1469x-00 and the flash that you are using. For ProDK of the DA1469x family

select MX25U3235F. Finally, you will be asked to insert an address about: Active FW image address and Update FW image address. Please keep in both entries the default value 0x2000. This script will create an image head in the top of firmware image and it will by appended into program_qspi.py.

  1. erase_qspi_xxxx (through jtag or uart): The best practice is to erase the QSPI flash before programming it
  2. program_qspi_xxxx (through jtag or uart):Finally, program the QSPI flash with your firmware.

Thanks, PM_Dialog

toshiyo
Offline
Last seen:1 year 7 months ago
加入:2019-02-28 19:04
Dear Dialog_PM,

Dear Dialog_PM,

Thank you for your help. I have implemented your suggestions, however when trying to program the qspi flash with my firmware, I reached an error 'Launching program_qspi_jtag' has encountered a problem. Variable references empty selection: ${project_loc}. How do I resolve this error?

Thank you for your time.

PM_Dialog
Offline
Last seen:6 hours 26 min ago
Staff
加入:2018-02-08 11:03
Hi toshiyo,

Hi toshiyo,

Please go to the external tools configurations and you should have the same configurations with the attached snapshot.

"program_qspi.py" "--jlink" "--jlink_path" "${jlink_path}" "--prod_header" "${project_loc}/${config_name:${project_name}}/${project_name}.bin"

Thanks, PM_Dialog

toshiyo
Offline
Last seen:1 year 7 months ago
加入:2019-02-28 19:04
Dear PM_Dialog,

Dear PM_Dialog,

I have checked my external tools configurations. They are the same as your attached snapshot.

Unfortunately, I still cannot run the program as I receive the following error [attached in screenshot]. Is there a specific value that the config_name should be and how should I correct the value [since the software seems to find the argument to be null] ?

Thank you.

Attachment:
PM_Dialog
Offline
Last seen:6 hours 26 min ago
Staff
加入:2018-02-08 11:03
Hi toshiyo,

Hi toshiyo,

Could you please indicate the version of the SmartSnippets that you are using?

Thanks, PM_Dialog

toshiyo
Offline
Last seen:1 year 7 months ago
加入:2019-02-28 19:04
Dear PM_Dialog,

Dear PM_Dialog,

Its v2.0.8

Thank you.

PM_Dialog
Offline
Last seen:6 hours 26 min ago
Staff
加入:2018-02-08 11:03
Hi toshiyo,

Hi toshiyo,

Please try the following steps:

  1. Delete the .metadata from the workspace SDK root folder.
  2. 不rt any SDK project. For instance, the freertos_retarget
  3. 不rt the python_scripts
  4. Select the freertos_retarget from the Project Explorer and press the DA1469x-00-Debug_QSPI
  5. The DA1469x-00-Debug_QSPI should be generated
  6. Open the external tool configurations and hit to the “Variables”
  7. Hit to the “Edit Variables” and make sure you have the same configurations.
  8. The configName should be the DA1469x-00-Debug_QSPI
  9. If you have the same configurations, having selected the DA1469x-00-Debug_QSPI from the Project Explorer window:
  • Run the program_qspi_config script
  • Run the erase_qspi_xxxx (through jtag or uart) script
  • Run the program_qspi_xxxx (through jtag or uart) script

After the stepsabove you should be able to program your board. I tested from my side. Let me aske you something. Are you using any of our development boards or you have a custom board?

Thanks, PM_Dialog

Attachment:
toshiyo
Offline
Last seen:1 year 7 months ago
加入:2019-02-28 19:04
Dear PM_Dialog,

Dear PM_Dialog,

Thank you for the response. I am using the DA14695-00HQDEVKT-U kit.

I tried following the steps you mentioned. Unfortunately, when I tried to complete step 4, I encountered three errors. I have attached a screenshot of those errors to this post. I would truly appreciate any advice you might have regarding this problem.

Thank you for your time,

Daniel

PM_Dialog
Offline
Last seen:6 hours 26 min ago
Staff
加入:2018-02-08 11:03
Hi toshiyo,

Hi toshiyo,

That means that the setup doesn't generate the linker scripts in order for the make to complete the build, before the actual build occurs, eclipse will have to generate the linker scripts from the mem.ld.h file and construct a mem.ld file in the build folder. In your case, the file is never built and as a result the tool is not able to find the mem.ld file. This can be due to a number of reasons, like the makefile.targets file isn't in the project directory, or a missing configuration etc. It seems that either the installation of the Smart Snippets has issues, or you haven't properly imported the projects. Be aware that the SDK along with the Smart Snippets tool should operate out of the box without any additional configuration. Since you have correctly installed the tool, all the projects should compile out of the box. In addition, this kind of error that you are seeing, might be related with your workspace. Let’s try the following:

  1. Uninstall completely the SmartSnippets studio from the control panel and try to re-install it. Please follow step-by-step the section 1 SmartSnippets™ Installation in theUM-B-057 SmartSnippets Studio User Manual
  2. Let’s move the SDK out the C:/Users location – I’ve seen this cause issues with administrative rights. For example, move a fresh SDK located here at the following without any spaces: C:\Dialog\DA1468x_DA15xxx_SDK_1.0.12.1075
  3. Since it’s a fresh SDK, the root folder should not contain the .metadata. If it exists, delete any .metadata that was created within the project directory to start a new workspace.
  4. Open the Smart Snippets Studio again and you can select a generic workspace
  5. Project Explorer应该是空白的。
  6. Right click into the Project Explorer and navigate to:
    1. 不rt…
    2. General / Existing Projects into Workspace
    3. Press Next>
    4. From the Select root directory browse to C:\Dialog\DA1468x_DA15xxx_SDK_1.0.12.1075
    5. Deselect all the projects and select only the freertos_retarget and the python_scripts. After that press finish
  7. With freertos_retarget selected, just click to the DA1469x-00-Debug_QSPI
  8. 当构建完成后,运行program_qspi_config script
  9. Run the erase_qspi_xxxx (through jtag or uart) script
  10. Run the program_qspi_xxxx (through jtag or uart) script

Thanks, PM_Dialog

toshiyo
Offline
Last seen:1 year 7 months ago
加入:2019-02-28 19:04
This worked! Thank you.

This worked! Thank you.