Forums - Problem flashing with JTAG

2 posts / 0 new
or Register
Last post
Problem flashing with JTAG
ArneTM
Join Date: 28 Feb 19
Posts: 2
Posted: Wed, 2019-07-03 11:22
Top

When I try to flash the board I get the following console output. I think the problem has something to do with the missing files in the first few lines, but I don't now how to fix this. 

Quote:

F:\QCA4020\Project\SDK\QCA4020.OR.3.0_00011.1\target\quartz\demo\Helloworld_demo\build\gcc>flash_openocd.bat
F:\QCA4020\Project\SDK\QCA4020.OR.3.0_00011.1\target\quartz\demo\Helloworld_demo\build\gcc\output\firmware_table.bin could not be found
F:\QCA4020\Project\SDK\QCA4020.OR.3.0_00011.1\target\quartz\demo\Helloworld_demo\build\gcc\output\generated_partition_table.xml could not be found
F:\QCA4020\Project\SDK\QCA4020.OR.3.0_00011.1\target\quartz\demo\Helloworld_demo\build\gcc\output\generated_fwd_table.xml could not be found
Open On-Chip Debugger 0.10.0 (2018-07-28) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
For bug reports, read
adapter speed: 5000 kHz
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
[2019-07-03 19:22:11,163] INFO: Checking for files to add to the image for Firmware Descriptor Table 0 File:gen_fwd_table.py:673 Function:gen_xml_program
Info : Listening on port 3333 for g[d2019-07-03 19:22:11,165] INFO: Done Generating XML file to program. File:gen_fwd_table.py:711 Function:gen_xml_program
b connections
Info : JTAG tap: QM4.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba0Starting GDB Server....
0, 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.
[2019-07-03 19:22:11,233] INFO: flash_through_gdb.py version 1.0.5 File:flash_through_gdb.py:596 Function:main
[2019-07-03 19:22:11,233] ERROR: Path None does not point to a file File:flash_through_gdb.py:483 Function:gdb_check_availability
[2019-07-03 19:22:11,234] CRITICAL: The given GDB path is not valid File:flash_through_gdb.py:603 Function:main
Flash Operation Completed Successfully...
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x000001c0 msp: 0x10000154
    TargetName         Type
SUCCESS: The process "openocd.exe" with PID 17776 has been terminated.
 

 

  • Up0
  • Down0
Re: Problem flashing with JTAG
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Wed, 2019-07-03 12:08
Top

While flashing through openocd we will check for "firmware_table.bin", "generated_partition_table.xml" and "generated_fwd_table.xml" under output directory.

If there are no files available we will try to generate during the flashing procedure:

[2019-07-03 19:22:11,163] INFO: Checking for files to add to the image for Firmware Descriptor Table 0 File:gen_fwd_table.py:673 Function:gen_xml_program
[2019-07-03 19:22:11,165] INFO: Done Generating XML file to program. File:gen_fwd_table.py:711 Function:gen_xml_program

However from the provided logs, the issue is due to invalid path for GDB :
[2019-07-03 19:22:11,233] ERROR: Path None does not point to a file File:flash_through_gdb.py:483 Function:gdb_check_availability
[2019-07-03 19:22:11,234] CRITICAL: The given GDB path is not valid File:flash_through_gdb.py:603 Function:main

kindly check if GDB is installed and PATH is added to environment variable. (arm-none-eabi-gdb --version)

You should observer below logs if GDB is available:
[2019-07-03 12:03:55,257] DEBUG: C:/QCA402X/6 2017-q2-update/bin/arm-none-eabi-gdb.exe --command="gdbout/gdb_commands.txt" --batch File:flash_through_gdb.py:451 Function:run
GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417-git

 

  • 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.