Forums - HelloWorld Demo does not start on QCA4020

3 posts / 0 new
Last post
HelloWorld Demo does not start on QCA4020
gerhard.marihart
Join Date: 30 Jun 20
Posts: 2
Posted: Wed, 2020-07-15 09:29

I've build the Demo on Windows. i used Toolchain "6_2-2016q4-20161216" and SDK "qca4020-or-3-2_qca_oem_sdk-cdb.git".

I've configured the jumpers as described and installed FTDI and WinUSB. Eclipse for C++ on Windows is used.

compiling and linking without errors ("Generate Linkerscripts..." takes a time).

Programming is done from Eclipse with flash_openocd.bat. 

The errors are: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED 8but I think that does not matter, because the flash gets programmed).

But 44 lines bellow there is a warning: No executable has been specified and target does not support.

Open On-Chip Debugger 0.10.0 (2017-06-09) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
For bug reports, read
adapter speed: 5000 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 5000 kHz
Info : JTAG tap: QM4.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
Info : JTAG tap: auto0.tap tap/device found: 0x300160e1 (mfg: 0x070 (Qualcomm), part: 0x0016, ver: 0x3)
Warn : AUTO auto0.tap - use "jtag newtap auto0 tap -irlen 11 -expected-id 0x300160e1"
Info : QM4.cpu: hardware has 6 breakpoints, 4 watchpoints
C:\ekeydev\Qualcomm\qca4020-or-3-2_qca_oem_sdk-cdb.git\target\quartz\demo\Helloworld_demo\build\gcc\output\firmware_table.bin konnte nicht gefunden werden
C:\ekeydev\Qualcomm\qca4020-or-3-2_qca_oem_sdk-cdb.git\target\quartz\demo\Helloworld_demo\build\gcc\output\generated_partition_table.xml konnte nicht gefunden werden
C:\ekeydev\Qualcomm\qca4020-or-3-2_qca_oem_sdk-cdb.git\target\quartz\demo\Helloworld_demo\build\gcc\output\generated_fwd_table.xml konnte nicht gefunden werden
Info : JTAG tap: QM4.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)
Info : JTAG tap: auto0.tap tap/device found: 0x300160e1 (mfg: 0x070 (Qualcomm), part: 0x0016, ver: 0x3)
Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x000001c0 msp: 0x10000154
    TargetName         Type       Endian TapName            State       
--  ------------------ ---------- ------ ------------------ ------------
 0* QM4.cpu            cortex_m   little QM4.cpu            halted
[2020-07-15 18:21:56,688] INFO: Checking for files to add to the image for Firmware Descriptor Table 0 File:gen_fwd_table.py:658 Function:gen_xml_program 
[2020-07-15 18:21:56,696] INFO: Done Generating XML file to program. File:gen_fwd_table.py:696 Function:gen_xml_program 
Starting GDB Server....
[2020-07-15 18:21:56,826] INFO: flash_through_gdb.py version 1.0.5 File:flash_through_gdb.py:581 Function:main 
[2020-07-15 18:21:58,017] DEBUG: Output Directory is gdbout/ File:flash_through_gdb.py:613 Function:main 
[2020-07-15 18:21:58,017] DEBUG: Search Path 1 .\output/ File:flash_through_gdb.py:625 Function:main 
[2020-07-15 18:21:58,017] DEBUG: Search Path 2 ..\..\..\..\..\bin\cortex-m0\threadx\ File:flash_through_gdb.py:625 Function:main 
[2020-07-15 18:21:58,017] DEBUG: Search Path 3 ..\..\..\..\..\bin\wlan/ File:flash_through_gdb.py:625 Function:main 
[2020-07-15 18:21:58,017] DEBUG: Search Path 4 ./ File:flash_through_gdb.py:625 Function:main 
[2020-07-15 18:21:58,023] INFO: Will write file ./firmware_table.bin into sectors [0, 0] File:flash_through_gdb.py:660 Function:main 
[2020-07-15 18:21:58,024] DEBUG: C:/Program Files (x86)/GNU Tools ARM Embedded/6_2-2016q4-20161216/bin/arm-none-eabi-gdb.exe --command="gdbout/gdb_commands.txt" --batch File:flash_through_gdb.py:436 Function:run 
GNU gdb (GNU Tools for ARM Embedded Processors) 7.12.0.20161204-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word".
[2020-07-15 18:21:58,075] INFO: GDB can run without shell=true File:flash_through_gdb.py:420 Function:_check_need_shell 
Info : accepting 'gdb' connection on tcp/3333
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x000001c0 in ?? ()
Loading section RAM_FOM_APPS_RO_REGION, size 0x5c58 lma 0x10046000
Loading section RAM_FOM_APPS_RW_REGION, size 0x5d4 lma 0x10080000
Start address 0x100462c2, load size 25132
Transfer rate: 292 KB/sec, 8377 bytes/write.
Breakpoint 1 at 0x1004614c: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c, line 125.
 
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c: No such file or directory.
"WRITE ./firmware_table.bin, offset=0 start_sector=0 num_sectors=1"Restoring binary file ./firmware_table.bin into memory (0x10081e20 to 0x10082e20)
 
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 in /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c
Info : dropped 'gdb' connection (error -400)
[2020-07-15 18:21:58,772] DEBUG: C:/Program Files (x86)/GNU Tools ARM Embedded/6_2-2016q4-20161216/bin/arm-none-eabi-gdb.exe --command="gdbout/gdb_commands.txt" --batch File:flash_through_gdb.py:436 Function:run 
Info : accepting 'gdb' connection on tcp/3333
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x1004614c in ?? ()
Loading section RAM_FOM_APPS_RO_REGION, size 0x5c58 lma 0x10046000
Loading section RAM_FOM_APPS_RW_REGION, size 0x5d4 lma 0x10080000
Start address 0x100462c2, load size 25132
Transfer rate: 238 KB/sec, 8377 bytes/write.
Breakpoint 1 at 0x1004614c: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c, line 125.
 
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c: No such file or directory.
"READ gdbout/firmware_table.bin_readback, append=0 start_sector=0 num_sectors=1"
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 in /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c
Info : dropped 'gdb' connection (error -400)
[2020-07-15 18:21:59,447] INFO: Data successfully flashed to disk for ./firmware_table.bin File:flash_through_gdb.py:677 Function:main 
[2020-07-15 18:21:59,447] INFO: Will write file .\output/Quartz_HASHED.elf into sectors [35, 150] File:flash_through_gdb.py:660 Function:main 
[2020-07-15 18:21:59,447] DEBUG: C:/Program Files (x86)/GNU Tools ARM Embedded/6_2-2016q4-20161216/bin/arm-none-eabi-gdb.exe --command="gdbout/gdb_commands.txt" --batch File:flash_through_gdb.py:436 Function:run 
Info : accepting 'gdb' connection on tcp/3333
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x1004614c in ?? ()
Loading section RAM_FOM_APPS_RO_REGION, size 0x5c58 lma 0x10046000
Loading section RAM_FOM_APPS_RW_REGION, size 0x5d4 lma 0x10080000
Start address 0x100462c2, load size 25132
Transfer rate: 282 KB/sec, 8377 bytes/write.
Breakpoint 1 at 0x1004614c: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c, line 125.
125 /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.2.r1-00005-QZHW-1_20191212_175623/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c: No such file or directory.
 

What can be wrong. I've spent 3 days to find a solution.

 

  • Up0
  • Down0
gerhard.marihart
Join Date: 30 Jun 20
Posts: 2
Posted: Fri, 2020-07-17 00:40

I've fixed the error "LIBUSB_ERROR_NOT_SUPPORTED" by uninstalling VisualGDB.

But the warning "No executable has been specified and target does not support." still exists. The application doesn't start.

  • Up0
  • Down0
mistry Moderator
Join Date: 18 Apr 18
Posts: 56
Posted: Mon, 2020-08-10 15:21

Hi,

Were you able to resolve the error?

Can you try to follow the steps shown here: https://developer.qualcomm.com/project/hello-world-w-qca4020-dev-kit

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.