Forums - Breakpoint in Thread not hit

19 posts / 0 new
Last post
Breakpoint in Thread not hit
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Fri, 2018-12-07 07:24

I'm using the Helloworld_demo application to experiment with the platform.

Debugging appears to be working correctly and breakpoints work correctly including breakpoint at app_start, however breakpoints once the program has entered the thread created by  "Result = qurt_thread_create(&Thread_Handle, &Thread_Attribte, HelloWorld_Thread, NULL);" , don't ever get hit but the program is running as the serial port shows the correct output.

The Console shows this:

Error: address + size wrapped (0xfffffffe, 0x00000004)

Error: JTAG-DP STICKY ERROR

Error: Failed to read memory at 0xfffff000
Error: address + size wrapped (0xfffffffe, 0x00000004)
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0xfffff000
 
And earlier on shows:
invalid command name "speed"
invalid command name "endian"
invalid command name "jtagconf"
 
Any help on this would be greatly appreciated!
 
 
 
  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Fri, 2018-12-07 14:56

Kindly make sure you have followed the instructions on Section: 3.7.2 JTAG debug mode  from document QCA402x (CDB2x) Development Kit User Guide 80-YA121-140.

Kindly reset the device and try debugging again with J31 pin 1 and 2 connected.

  • Up0
  • Down0
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Mon, 2018-12-10 08:47

I have just run through the instructions again, and still debugging is entered correctly hits the breakpoint at app_start, then when I press continue it continues to run and never hits the breakpoint set in the function HelloWorld_Thread(). An output can be seen on the serial port and as such I'm sure it's running past the breakpoint I have set.

I can also confirm that I have reset the device and that J31 pin 1 and 2 are connected.

Could it be an issue relating to the PATH, I do have highlighted issues about things not being able to be resolved in the code editor but this hasn't effected building the program.

  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Mon, 2018-12-10 16:28

The Console shows this:

Error: address + size wrapped (0xfffffffe, 0x00000004)
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0xfffff000
Error: address + size wrapped (0xfffffffe, 0x00000004)
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0xfffff000

The above error traces occur when the path is not valid such as different demo path being processed during debug scenario.
In such cases, the hashed elf fails to match the original Quartz.elf instruction address and breakpoint results in failed to read memory.

invalid command name "speed"
invalid command name "endian"
invalid command name "jtagconf"

The above "invalid command name" are warning traces, they are part of the GDB server configuration and can be ignored

Kindly check the Path settings and make sure appropriate path location has been set for build/flash and debug.

  • Up0
  • Down0
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Tue, 2018-12-11 02:49

I've just deleted everything and started again, I followed the development getting started guide and I'm still getting the same issue. I'm quite stuck here... I believe all the paths match that of the development guide.

Is the Flashing Script working okay? Here is an extract:

Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
"READ gdbout/wlan_fw_img.bin_readback, append=1 start_sector=194 num_sectors=7"
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 in /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c
Info : dropped 'gdb' connection (error -400)
[2018-12-11 10:48:30,650] INFO: Data successfully flashed to disk for ..\..\..\..\..\bin\wlan/wlan_fw_img.bin File:flash_through_gdb.py:692 Function:main 
[2018-12-11 10:48:30,650] INFO: Will erase sectors on range [3, 18] File:flash_through_gdb.py:658 Function:main 
[2018-12-11 10:48:30,650] 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:451 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 0x5b4c lma 0x10046000
Loading section RAM_FOM_APPS_RW_REGION, size 0x3ac lma 0x10080000
Start address 0x100462c2, load size 24312
Transfer rate: 258 KB/sec, 8104 bytes/write.
Breakpoint 1 at 0x1004614c: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/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.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c: No such file or directory.
$1 = "ERASE start_sector=3 num_sectors=16"
 
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 in /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c
Info : dropped 'gdb' connection (error -400)
[2018-12-11 10:48:32,078] INFO: Will erase sectors on range [19, 34] File:flash_through_gdb.py:658 Function:main 
[2018-12-11 10:48:32,078] 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:451 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 0x5b4c lma 0x10046000
Loading section RAM_FOM_APPS_RW_REGION, size 0x3ac lma 0x10080000
Start address 0x100462c2, load size 24312
Transfer rate: 289 KB/sec, 8104 bytes/write.
Breakpoint 1 at 0x1004614c: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/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.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c: No such file or directory.
$1 = "ERASE start_sector=19 num_sectors=16"
 
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 in /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c
Info : dropped 'gdb' connection (error -400)
[2018-12-11 10:48:32,717] INFO: Will erase sectors on range [1, 2] File:flash_through_gdb.py:658 Function:main 
[2018-12-11 10:48:32,717] 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:451 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 0x5b4c lma 0x10046000
Loading section RAM_FOM_APPS_RW_REGION, size 0x3ac lma 0x10080000
Start address 0x100462c2, load size 24312
Transfer rate: 260 KB/sec, 8104 bytes/write.
Breakpoint 1 at 0x1004614c: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c, line 125.
125 /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c: No such file or directory.
 
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
$1 = "ERASE start_sector=1 num_sectors=2"
 
Breakpoint 1, main_c () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c:125
125 in /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/storage/tools/jtagprogrammer/src//JtagProgrammer.c
Info : dropped 'gdb' connection (error -400)
[2018-12-11 10:48:33,431] INFO: Script finished processing generated_fwd_table.xml File:flash_through_gdb.py:718 Function:main 
Flash Operation Completed Successfully...
SUCCESS: The process "openocd.exe" with PID 9520 has been terminated.
 

 

 

  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Thu, 2018-12-13 10:08

From the provided log, the flashing of device is successful.

​Can try the manual way of debugging on terminal prompt to confirm if there if there is an issue with debug setup irrespective of IDE.

Refer to Section: 3.7.2.2 Debugging through GDB of document QCA402x (CDB2x) Development Kit User Guide 80-YA121-140.

  • Up0
  • Down0
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Mon, 2018-12-17 05:52

Hey there, I attempted to debugging in command promt and this is what happened after I continued the debug a number of times:

 
C:\QCA4020.OR.3.0_00011.1\target\quartz\demo\Helloworld_demo\build\gcc>arm-none-
eabi-gdb -x v2\quartzcdb.gdbinit
GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417
-git
Copyright (C) 2017 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".
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x000001c0 in ?? ()
JTAG tap: QM4.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xb
a00, ver: 0x4)
JTAG tap: auto0.tap tap/device found: 0x300160e1 (mfg: 0x070 (Qualcomm), part: 0
x0016, ver: 0x3)
Only resetting the Cortex-M core, use a reset-init event handler to reset any pe
ripherals or configure hardware srst support.
target halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x00007106 msp: 0x10032ba0
invalid command name "speed"
invalid command name "endian"
invalid command name "jtagconf"
Breakpoint 1 at 0x100a0c22: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00
078-QZHW-1_20181109_142759/b/ioesw_proc/core/boot/build/ioe_ram_ipt/cortex-m4/AR
NFRI/sbl//sbl.o.i, line 57.
add symbol table from file "../../../../../bin/cortex-m4/IOE_ROM_IPT_IMG_ARNNRI_
patched_syms.elf" at
        .text_addr = 0x10000
warning: section .text not found in C:\QCA4020.OR.3.0_00011.1\target\bin\cortex-
m4\IOE_ROM_IPT_IMG_ARNNRI_patched_syms.elf
warning: Loadable section "sockcall__i.t_errno" outside of ELF segments
warning: Loadable section "sockcall__i.t_getname" outside of ELF segments
warning: Loadable section "sockcall__i.t_getpeername" outside of ELF segments
warning: Loadable section "sockcall__i.t_getsockname" outside of ELF segments
warning: Loadable section "sockcall__i.t_getsockopt" outside of ELF segments
warning: Loadable section "sockcall__i.t_listen" outside of ELF segments
warning: Loadable section "sockcall__i.t_recv" outside of ELF segments
warning: Loadable section "sockcall__i.t_recvfrom" outside of ELF segments
warning: Loadable section "soselect__i.t_select" outside of ELF segments
warning: Loadable section "sockcall__i.t_send" outside of ELF segments
warning: Loadable section "sockcall__i.t_sendto" outside of ELF segments
warning: Loadable section "sockcall__i.t_setsockopt" outside of ELF segments
warning: Loadable section "sockcall__i.t_shutdown" outside of ELF segments
warning: Loadable section "sockcall__i.t_socket" outside of ELF segments
warning: Loadable section "sockcall__i.t_socketclose" outside of ELF segments
warning: Loadable section "tcp6__i.tcp6_rcv" outside of ELF segments
warning: Loadable section "tcp6__i.tcp6_send" outside of ELF segments
warning: Loadable section "tcp_usr__i.tcp_attach" outside of ELF segments
warning: Loadable section "tcp_timr__i.tcp_canceltimers" outside of ELF segments
 
warning: Loadable section "tcpcksum__i.tcp_cksum" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_close" outside of ELF segments
warning: Loadable section "tcp_zio__i.tcp_data_upcall" outside of ELF segments
warning: Loadable section "tcp_usr__i.tcp_disconnect" outside of ELF segments
warning: Loadable section "tcp_in__i.tcp_dooptions" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_drop" outside of ELF segments
warning: Loadable section "tcp_timr__i.tcp_fasttimo" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_findbuf" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_freeassmq" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_getseq" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_init" outside of ELF segments
warning: Loadable section "tcp_in__i.tcp_input" outside of ELF segments
warning: Loadable section "tcp_in__i.tcp_mss" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_newtcpcb" outside of ELF segments
warning: Loadable section "soselect__i.tcp_notify" outside of ELF segments
warning: Loadable section "tcp_out__i.tcp_output" outside of ELF segments
warning: Loadable section "tcp_zio__i.tcp_pktalloc" outside of ELF segments
warning: Loadable section "tcp_zio__i.tcp_pktfree" outside of ELF segments
warning: Loadable section "tcp_in__i.tcp_pulloutofband" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_putseq" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_quench" outside of ELF segments
warning: Loadable section "tcp_in__i.tcp_reass" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_respond" outside of ELF segments
warning: Loadable section "tcp_out__i.tcp_setpersist" outside of ELF segments
warning: Loadable section "osporttk__i.tcp_sleep" outside of ELF segments
warning: Loadable section "tcp_timr__i.tcp_slowtimo" outside of ELF segments
warning: Loadable section "tcp_subr__i.tcp_template" outside of ELF segments
warning: Loadable section "nptcp__i.tcp_tick" outside of ELF segments
warning: Loadable section "tcp_timr__i.tcp_timers" outside of ELF segments
warning: Loadable section "tcp_usr__i.tcp_usrclosed" outside of ELF segments
warning: Loadable section "tcp_usr__i.tcp_usrreq" outside of ELF segments
warning: Loadable section "osporttk__i.tcp_wakeup" outside of ELF segments
warning: Loadable section "tcp_in__i.tcp_xmit_timer" outside of ELF segments
warning: Loadable section "tcp_zio__i.tcp_xout" outside of ELF segments
warning: Loadable section "tcpport__i.tcpinit" outside of ELF segments
warning: Loadable section "ssl_cert__i.timeCompare" outside of ELF segments
warning: Loadable section "osporttk__i.tk_del" outside of ELF segments
warning: Loadable section "osporttk__i.tk_event_clear" outside of ELF segments
warning: Loadable section "osporttk__i.tk_event_create" outside of ELF segments
warning: Loadable section "osporttk__i.tk_event_delete" outside of ELF segments
warning: Loadable section "osporttk__i.tk_event_set" outside of ELF segments
warning: Loadable section "osporttk__i.tk_event_wait" outside of ELF segments
warning: Loadable section "osporttk__i.tk_get_ticks" outside of ELF segments
warning: Loadable section "osporttk__i.tk_init_os" outside of ELF segments
warning: Loadable section "osporttk__i.tk_msec_delay" outside of ELF segments
warning: Loadable section "osporttk__i.tk_mutex_create" outside of ELF segments
warning: Loadable section "osporttk__i.tk_mutex_free" outside of ELF segments
warning: Loadable section "osporttk__i.tk_mutex_pend" outside of ELF segments
warning: Loadable section "osporttk__i.tk_mutex_post" outside of ELF segments
warning: Loadable section "netmain_mod__i.tk_netmain" outside of ELF segments
warning: Loadable section "nettick__i.tk_nettick" outside of ELF segments
warning: Loadable section "osporttk__i.tk_new" outside of ELF segments
warning: Loadable section "osporttk__i.tk_res_lock" outside of ELF segments
warning: Loadable section "osporttk__i.tk_res_unlock" outside of ELF segments
warning: Loadable section "osporttk__i.tk_sem_create" outside of ELF segments
warning: Loadable section "osporttk__i.tk_sem_free" outside of ELF segments
warning: Loadable section "osporttk__i.tk_sem_pend" outside of ELF segments
warning: Loadable section "osporttk__i.tk_sem_post" outside of ELF segments
warning: Loadable section "osporttk__i.tk_sem_post_isr" outside of ELF segments
warning: Loadable section "osporttk__i.tk_sleep" outside of ELF segments
warning: Loadable section "osporttk__i.tk_stats" outside of ELF segments
warning: Loadable section "osporttk__i.tk_suspend" outside of ELF segments
warning: Loadable section "osporttk__i.tk_wake" outside of ELF segments
warning: Loadable section "osporttk__i.tk_yield" outside of ELF segments
warning: Loadable section "uart_os__i.uart_clock_close" outside of ELF segments
warning: Loadable section "uart_os__i.uart_clock_open" outside of ELF segments
warning: Loadable section "uart__i.uart_close" outside of ELF segments
warning: Loadable section "uart__i.uart_dsr_cb" outside of ELF segments
warning: Loadable section "uart_os__i.uart_get_properties" outside of ELF segmen
ts
warning: Loadable section "uart_os__i.uart_issue_power_votes" outside of ELF seg
ments
warning: Loadable section "uart_os__i.uart_mem_bank_issue_vote" outside of ELF s
egments
warning: Loadable section "uart_os__i.uart_mem_bank_release_vote" outside of ELF
 segments
warning: Loadable section "uart_os__i.uart_mem_in_ram" outside of ELF segments
warning: Loadable section "uart__i.uart_open" outside of ELF segments
warning: Loadable section "uart__i.uart_receive" outside of ELF segments
warning: Loadable section "uart_os__i.uart_release_power_votes" outside of ELF s
egments
warning: Loadable section "uart_os__i.uart_tlmm_close" outside of ELF segments
warning: Loadable section "uart_os__i.uart_tlmm_open" outside of ELF segments
warning: Loadable section "uart__i.uart_transmit" outside of ELF segments
warning: Loadable section "udp6__i.udp6_alloc" outside of ELF segments
warning: Loadable section "udp6__i.udp6_chk_mc" outside of ELF segments
warning: Loadable section "udpsock6__i.udp6_chk_overlapped_binding" outside of E
LF segments
warning: Loadable section "udpsock6__i.udp6_data_upcall" outside of ELF segments
 
warning: Loadable section "udp6__i.udp6_deliver_mc" outside of ELF segments
warning: Loadable section "udp6__i.udp6_maxalloc" outside of ELF segments
warning: Loadable section "udp6__i.udp6_open" outside of ELF segments
warning: Loadable section "udp6__i.udp6_rcv" outside of ELF segments
warning: Loadable section "udp6__i.udp6_send" outside of ELF segments
warning: Loadable section "udpsock6__i.udp6_sockaddr" outside of ELF segments
warning: Loadable section "udpsock6__i.udp6_sockbind" outside of ELF segments
warning: Loadable section "udpsock6__i.udp6_socksend" outside of ELF segments
warning: Loadable section "udpsock6__i.udp6_soinput" outside of ELF segments
warning: Loadable section "tcpcksum__i.udp_cksum" outside of ELF segments
warning: Loadable section "udpsock__i.udp_close" outside of ELF segments
warning: Loadable section "udpsock__i.udp_lookup" outside of ELF segments
warning: Loadable section "udpsock__i.udp_socket" outside of ELF segments
warning: Loadable section "udpsock__i.udp_soinerr" outside of ELF segments
warning: Loadable section "udpsock__i.udp_soinput" outside of ELF segments
warning: Loadable section "udpsock__i.udp_usrreq" outside of ELF segments
warning: Loadable section "udp6__i.udpswap" outside of ELF segments
warning: Loadable section "ininit__i.update_packets" outside of ELF segments
warning: Loadable section "quartz_ram_stubs__i.user_post_setup" outside of ELF s
egments
warning: Loadable section "quartz_ram_stubs__i.user_pre_setup" outside of ELF se
gments
warning: Loadable section "in_utils__i.uslash" outside of ELF segments
warning: Loadable section "ip6mc__i.v6_lookup_mcast" outside of ELF segments
warning: Loadable section "flash_nor__i.vendor_error_check" outside of ELF segme
nts
warning: Loadable section "strrcl_main__i.vote_for_suspend" outside of ELF segme
nts
warning: Loadable section "api_ioctl__i.wait_for_coex_stats" outside of ELF segm
ents
warning: Loadable section "api_ioctl__i.wait_for_get_stats" outside of ELF segme
nts
warning: Loadable section "api_ioctl__i.wait_scan_done" outside of ELF segments
warning: Loadable section "cust_hw_spi__i.wait_spi_done" outside of ELF segments
 
warning: Loadable section "coex__i.wlan_coex_callback_handler" outside of ELF se
gments
warning: Loadable section "cust_stack_iniche__i.wlan_create_device" outside of E
LF segments
warning: Loadable section "cust_stack_iniche__i.wlan_dev0_pkt_send" outside of E
LF segments
warning: Loadable section "cust_stack_iniche__i.wlan_dev1_pkt_send" outside of E
LF segments
warning: Loadable section "cust_stack_iniche__i.wlan_dev_close" outside of ELF s
egments
warning: Loadable section "cust_stack_iniche__i.wlan_dev_init" outside of ELF se
gments
warning: Loadable section "cust_stack_iniche__i.wlan_dev_stats" outside of ELF s
egments
warning: Loadable section "cust_api_stack_txrx__i.wlan_drv_buf_dequeue" outside
of ELF segments
warning: Loadable section "cust_api_stack_txrx__i.wlan_drv_buf_enqueue" outside
of ELF segments
warning: Loadable section "cust_api_stack_txrx__i.wlan_drv_buf_purge_queue" outs
ide of ELF segments
warning: Loadable section "cust_api_stack_txrx__i.wlan_drv_buf_queue_empty" outs
ide of ELF segments
warning: Loadable section "cust_stack_iniche__i.wlan_pkt_send" outside of ELF se
gments
warning: Loadable section "quartz_ram_stubs__i.wlan_set_deviceid" outside of ELF
 segments
warning: Loadable section "wmi__i.wmi_bssfilter_cmd" outside of ELF segments
warning: Loadable section "api_init__i.wmi_cmd_process" outside of ELF segments
warning: Loadable section "wmi__i.wmi_cmd_send" outside of ELF segments
warning: Loadable section "wmi__i.wmi_cmd_start" outside of ELF segments
warning: Loadable section "wmi__i.wmi_config_11v_cmd" outside of ELF segments
warning: Loadable section "wmi__i.wmi_control_rx" outside of ELF segments
warning: Loadable section "wmi__i.wmi_control_rx2" outside of ELF segments
warning: Loadable section "wmi__i.wmi_control_rx_p2p" outside of ELF segments
warning: Loadable section "wmi__i.wmi_control_rx_xtnd" outside of ELF segments
warning: Loadable section "wmi__i.wmi_data_hdr_add" outside of ELF segments
warning: Loadable section "wmi__i.wmi_data_hdr_remove" outside of ELF segments
warning: Loadable section "wmi__i.wmi_dix_2_dot3" outside of ELF segments
warning: Loadable section "wmi__i.wmi_dot3_2_dix" outside of ELF segments
warning: Loadable section "wmi__i.wmi_dset_host_cfg_cmd" outside of ELF segments
 
warning: Loadable section "wmi__i.wmi_get_control_ep" outside of ELF segments
warning: Loadable section "wmi__i.wmi_implicit_create_pstream" outside of ELF se
gments
warning: Loadable section "wmi__i.wmi_init" outside of ELF segments
warning: Loadable section "wmi__i.wmi_meta_add" outside of ELF segments
warning: Loadable section "wmi__i.wmi_p2p_set_noa" outside of ELF segments
warning: Loadable section "wmi__i.wmi_p2p_set_oppps" outside of ELF segments
warning: Loadable section "wmi__i.wmi_qos_state_init" outside of ELF segments
warning: Loadable section "wmi__i.wmi_sdpd_send_cmd" outside of ELF segments
warning: Loadable section "wmi__i.wmi_send_socket_cmd" outside of ELF segments
warning: Loadable section "wmi__i.wmi_set_appie_cmd" outside of ELF segments
warning: Loadable section "wmi__i.wmi_set_control_ep" outside of ELF segments
warning: Loadable section "wmi__i.wmi_set_wnm_sleep_period_cmd" outside of ELF s
egments
warning: Loadable section "wmi__i.wmi_set_wnm_sleep_response_cmd" outside of ELF
 segments
warning: Loadable section "wmi__i.wmi_shutdown" outside of ELF segments
warning: Loadable section "wmi__i.wmi_socket_cmd" outside of ELF segments
warning: Loadable section "wmi__i.wmi_storerecall_recall_cmd" outside of ELF seg
ments
warning: Loadable section "ram_stubs__i.xport_quartz_shutdown" outside of ELF se
gments
warning: Loadable section "ram_stubs__i.xport_quartz_start" outside of ELF segme
nts
warning: Loadable section "ROM_FOM_RO_REGION__ro-data" outside of ELF segments
warning: Loadable section "ROM_STDLIBS_RO_REGION" outside of ELF segments
warning: Loadable section "ROM_LINKER_SYMS__ro-data" outside of ELF segments
warning: Loadable section "ROM_MOM_MISSIONROM_RW_REGION__rw-data" outside of ELF
 segments
warning: Loadable section "ROM_SOM_MISSIONROM_RW_REGION__rw-data" outside of ELF
 segments
warning: Loadable section "ROM_STDLIBS_RW_REGION" outside of ELF segments
warning: Loadable section "ROM_FOM_MISSIONROM_RW_REGION__rw-data" outside of ELF
 segments
Breakpoint 2 at 0x100a0172: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00
078-QZHW-1_20181109_142759/b/ioesw_proc/core/boot/sbl//sbl1_mc.c, line 344.
Breakpoint 3 at 0x10fbc: file /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.1.0.r4-00
013-QZFPGA-1_20170509_214818/b/ioesw_proc/core/v2/rom/drivers/debugtools/err/src
/apps_proc/arm//err_jettison_core_m4.s, line 83.
(gdb) c
Continuing.
 
Breakpoint 1, _main () at /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZH
W-1_20181109_142759/b/ioesw_proc/core/boot/build/ioe_ram_ipt/cortex-m4/ARNFRI/sb
l//sbl.o.i:57
57      /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_14275
9/b/ioesw_proc/core/boot/build/ioe_ram_ipt/cortex-m4/ARNFRI/sbl//sbl.o.i: No suc
h file or directory.
(gdb) c
Continuing.
 
Breakpoint 2, sbl1_main_ctl (pbl_shared=0x10032f78) at /local/mnt/workspace/CRMB
uilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/boot/sbl//sbl
1_mc.c:344
344     /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_14275
9/b/ioesw_proc/core/boot/sbl//sbl1_mc.c: No such file or directory.
(gdb) c
Continuing.
Invalid ACK (7) in DAP response
 
Program stopped.
sbl1_main_ctl (pbl_shared=0x10032f78) at /local/mnt/workspace/CRMBuilds/CNSS_W.Q
Z.3.0-00078-QZHW-1_20181109_142759/b/ioesw_proc/core/boot/sbl//sbl1_mc.c:347
347     in /local/mnt/workspace/CRMBuilds/CNSS_W.QZ.3.0-00078-QZHW-1_20181109_14
2759/b/ioesw_proc/core/boot/sbl//sbl1_mc.c
(gdb)
  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Mon, 2018-12-17 12:17

From the provided information, the Openocd-JTAG debugging is failing in both command line and Eclipse IDE:

Breakpoint 2, sbl1_main_ctl (pbl_shared=0x10032f78) (gdb) c
Continuing.
Invalid ACK (7) in DAP response

Program stopped.
(gdb)

The reason for above error "Invalid ACK (7) in DAP response" could be an issue with jumper settings.
Can you provide us your setup images in any shared link to verify the jumper connections and also let us know the hardware version you are using ?

  • Up0
  • Down0
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Fri, 2019-01-11 01:45

Sorry for the delay, had to move onto another project for a while, please find the image of how the board is currently setup at the following link: https://imgur.com/TgDKeZ0

 

  • Up0
  • Down0
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Tue, 2019-01-15 07:28

Any ideas? I'm starting to get pressed on the project again!

Kind Regards

  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Tue, 2019-01-15 11:31

Unable to view the attachment. Could you share the image vis google drive ?
 

  • Up0
  • Down0
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Wed, 2019-01-16 01:33
  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Thu, 2019-01-17 10:01

The jumper settings are good as expected and there should be any issue while debugging using GDB session.
Could you check with new jumper pins and wires for the connection again to confirm no issues with the connection setup.
As sometimes, we have seen similar issue when the cables are loose or jumper pins are broken inside.

Kindly rebuild the image, flash and try to debug with the replaced jumper connections.

  • Up0
  • Down0
CHoggard
Join Date: 30 Nov 18
Posts: 8
Posted: Fri, 2019-01-18 01:26

I replaced all the jumper connection with new jumpers and have attempted to rebuild, reflash, and debug, with no joy the same output as last time so far as I can tell.

here is an short extract:

    TargetName         Type       Endian TapName            State       
--  ------------------ ---------- ------ ------------------ ------------
 0* QM4.cpu            cortex_m   little QM4.cpu            halted
Started by GNU MCU Eclipse
Info : accepting 'gdb' connection on tcp/3333
semihosting is enabled
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
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, semihosting
Info : dropped 'gdb' connection (error -400)
Info : accepting 'gdb' connection on tcp/3333
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
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: 0x81000000 pc: 0x00007106 msp: 0x10032ba0, semihosting
invalid command name "speed"
invalid command name "endian"
invalid command name "jtagconf"
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
Error: JTAG-DP STICKY ERROR
Error: Failed to read memory at 0x01050230
  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Thu, 2019-01-31 11:43

The only suspect is the devcfgSleepData not turned off.
Can you confirm the instructions listed in Section 3.7.2 JTAG debug mode of QCA402x(CDB2x) Development Kit User Guide are followed ?

Please execute below instrucitons and let me know your observations:

build.bat clobber
build.bat prepare 4020
Modify DevCfg_master_devcfg_out_cdb.xml and turn off "devcfgSleepData".
build.bat t 4020 cdb
flash the image.
Install jumper on J31  "1 and 2".
Execute "openocd -f qca402_openocd.cfg" on terminal
Open another terminal and run "arm-none-eabi-gdb -x v2\qcartzcdb.gdbinit"
on the gdb screen try to set "p g_sleepAllowLowPowerMode =0" and run continue.
Try to enable required break point and verify if you are able to hit the break point.



 

  • Up0
  • Down0
mmad
Join Date: 7 Jul 16
Posts: 13
Posted: Fri, 2019-05-17 00:44

I am having exactly the same problem,

the breakpoint is not hit

the last one, which is effective, is inside App_Start, when building with ThreadX, for FreeRtos it does not stop even there

btw the variable is g_sleepAllowLowPowerModes, but it does not help either

BR

  • Up0
  • Down0
gdutka
Join Date: 21 Jun 19
Posts: 7
Posted: Wed, 2019-06-26 13:40

Hello,

 Has this issue been solved. I am having the exact same problem in this thread an a solution would really help me get going in the right direction.

thanks

  • Up0
  • Down0
mmad
Join Date: 7 Jul 16
Posts: 13
Posted: Thu, 2019-06-27 23:14

No, the issue is still not solved

Debugging from command line GDB is not a solution for me.

It takes too much effort, the same counts for flashing image each time, it takes many minutes.

For the older chip there was on option to laod code directly to RAM which was fast. It is apparently not available here.

Working with this platform is a pain

  • Up0
  • Down0
gdutka
Join Date: 21 Jun 19
Posts: 7
Posted: Fri, 2019-06-28 05:09

Ok, thank you for your feedback.

 

Just out of curiosity then. What is the best way to debug this evaluation Kit. It seems like there is no real way of debugging applications on this board. Is this correct? Someone somehwere must have this working

 

Regards,

 Gian

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