Forums - FAIL TO FLASH IN QCA4020

1 post / 0 new

or Register

FAIL TO FLASH IN QCA4020

buela.g

Join Date: 23 Dec 21

Posts: 1

Posted: Sat, 2023-03-18 08:01

Top

Hi,

We followed the instructions mentioned in the silex document(https://www.silextechnology.com/hubfs/Resource%20PDF/140-00217-100-App%20Note-SX-ULPGN-BTZ-Development-QuickStartGuide.pdf) to set up the environment for Silex-SX ULPGN BTZ 2000.

The above document mentioned using QCA4020 SDK: QCA4020.OR.3.4 QCA OEM SDK+CDB r00002.1 as a repository. We followed this document( https://docs.qualcomm.com/bundle/80-YA121-140/resource/80-YA121-140.pdf) to build and flash the onboard demo example. However, the Onboard demo example did not work as intended and it got stuck in the wlan_enable function and hangs there indefinitely.

So we tried using QCA4020.OR.3.5 QCA OEM SDK+CDB r00006.1.

We made the necessary changes following the Qualcomm document for the Onboard demo example to work. The demo example was able to build and it successfully flashed. However, this also failed to produce the output(getting failed to connect to socket -1 error). When we again tried to flash the board we are not able to flash and got the following error.

GNU MCU Eclipse 64-bits Open On-Chip Debugger 0.10.0+dev-00404-g20463c28 (2018-01-23-12:30)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

adapter speed: 5000 kHz

Info : clock speed 5000 kHz

Error: JTAG scan chain interrogation failed: all ones

Error: Check JTAG interface, timings, target power, etc.

Error: Trying to use configured scan chain anyway...

Error: QM4.cpu: IR capture error; saw 0x0f not 0x01

Warn : Bypassing JTAG setup events due to errors

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

ECould Not Find C:\Users\silex\qca4020-or-3-4_qca_oem_sdk-cdb-r00002.1\target\quartz\demo\Helloworld_demo\build\gcc\output\firmware_table.bin

rror: JTAG-DP STICKY ECould Not Find C:\Users\silex\qca4020-or-3-4_qca_oem_sdk-cdb-r00002.1\target\quartz\demo\Helloworld_demo\build\gcc\output\generated_partition_table.xml

RROR

ErCould Not Find C:\Users\silex\qca4020-or-3-4_qca_oem_sdk-cdb-r00002.1\target\quartz\demo\Helloworld_demo\build\gcc\output\generated_fwd_table.xml

ror: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Could not initialize the debug port

Info : Listening on port 3333 for gdb connections

Error: JTAG scan chain interrogation failed: all ones

Error: Check JTAG interface, timings, target power, etc.

Error: Trying to use configured scan chain anyway...

Error: QM4.cpu: IR capture error; saw 0x0f not 0x01

Warn : Bypassing JTAG setup events due to errors

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

[2023-03-18 19:48:54,404] INFO: Checking for files to add to the image for Firmware Descriptor Table 0 File:gen_fwd_table.py:662 Function:gen_xml_program

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ER[2023-03-18 19:48:54,404] INFO: Done Generating XML file to program. File:gen_fwd_table.py:700 Function:gen_xml_program

ROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: InvaStarting GDB Server....

lid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Invalid ACK (7) in DAP response

Error: JTAG-DP STICKY ERROR

Error: Could not initialize the debug port

Error: Target not examined, reset NOT asserted!

in procedure 'reset' called at file "qca402x_openocd.cfg", line 93

in procedure 'ocd_bouncer'

[2023-03-18 19:48:54,483] INFO: flash_through_gdb.py version 1.0.5 File:flash_through_gdb.py:582 Function:main

[2023-03-18 19:48:54,502] DEBUG: Output Directory is gdbout/ File:flash_through_gdb.py:614 Function:main

[2023-03-18 19:48:54,502] DEBUG: Search Path 1 .\output/ File:flash_through_gdb.py:626 Function:main

[2023-03-18 19:48:54,502] DEBUG: Search Path 2 ..\..\..\..\..\bin\cortex-m0\threadx\ File:flash_through_gdb.py:626 Function:main

[2023-03-18 19:48:54,502] DEBUG: Search Path 3 ..\..\..\..\..\bin\wlan/ File:flash_through_gdb.py:626 Function:main

[2023-03-18 19:48:54,502] DEBUG: Search Path 4 ./ File:flash_through_gdb.py:626 Function:main

[2023-03-18 19:48:54,502] INFO: Will write file ./firmware_table.bin into sectors [0, 0] File:flash_through_gdb.py:661 Function:main

[2023-03-18 19:48:54,502] DEBUG: C:/Program Files (x86)/GNU Tools ARM Embedded/6 2017-q2-update/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 6-2017-q2-update) 7.12.1.20170417-git

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:

<http://www.gnu.org/software/gdb/bugs/>.

Find the GDB manual and other documentation resources online at:

<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".

Type "apropos word" to search for commands related to "word".

[2023-03-18 19:48:54,546] INFO: GDB can run without shell=true File:flash_through_gdb.py:420 Function:_check_need_shell

gdbout/gdb_commands.txt:1: Error in sourced command file:

localhost:3333: No connection could be made because the target machine actively refused it.

[2023-03-18 19:48:56,606] ERROR: Unable to open the file 'gdbout/command_result.log'

File:flash_through_gdb.py:241 Function:_check_status

Traceback (most recent call last):

File "..\..\..\..\..\build\tools\flash/flash_through_gdb.py", line 234, in _check_status

f = open(self.cmd_status_file , 'rb')

FileNotFoundError: [Errno 2] No such file or directory: 'gdbout/command_result.log'

[2023-03-18 19:48:56,606] WARNING: The last command return error

File:flash_through_gdb.py:244 Function:_check_status

[2023-03-18 19:48:56,620] ERROR: Failed to write to start sector=0, num sectors=1 File:flash_through_gdb.py:664 Function:main

Flash Operation Completed Successfully...

Kindly provide some insight on how to rectify this error while flashing.

Forum vote up/down

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.

Sort By

Filter Results