- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm working with BCM94343WWCD1 platform and is setting debug environment but have an error below.
target build combination : "snip.mcs-BCM94343WWCD1-FreeRTOS-LwIP-SDIO-debug download debug run no_dct"
console log :
Downloading Bootloader ...
No changes detected
Downloading Application ...
No changes detected
Resetting target
GNU gdb (GDB) 7.7
Copyright (C) 2014 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-pc-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"...
Reading symbols from build/snip.mcs-BCM94343WWCD1-FreeRTOS-LwIP-SDIO-debug/binary/snip.mcs-BCM94343WWCD1-FreeRTOS-LwIP-SDIO-debug.elf...done.
.gdbinit_attach:1: Error in sourced command file:
Remote communication error. Target disconnected.: No error.
(gdb) Target running
Open OCD log
1 Info : only one transport option; autoselect 'jtag'^M
2 trst_and_srst separate srst_nogate trst_push_pull srst_push_pull connect_assert_srst^M
3 adapter speed: 1000 kHz^M
4 adapter_nsrst_delay: 100^M
5 jtag_ntrst_delay: 100^M
6 Warn : target name is deprecated use: 'cortex_m'^M
7 jtag_init^M
8 Warn : Using DEPRECATED interface driver 'ft2232'^M
9 Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...^M
10 Info : max TCK change to: 30000 kHz^M
11 Info : clock speed 1000 kHz^M
12 Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)^M
13 Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06431041 (mfg: 0x020, part: 0x6431, ver: 0x0)^M
14 Warn : JTAG tap: stm32f4xx.bs UNEXPECTED: 0x06431041 (mfg: 0x020, part: 0x6431, ver: 0x0)^M
15 Error: JTAG tap: stm32f4xx.bs expected 1 of 1: 0x06413041 (mfg: 0x020, part: 0x6413, ver: 0x0)^M
16 Error: Trying to use configured scan chain anyway...^M
17 Warn : Bypassing JTAG setup events due to errors^M
18 Info : stm32f4xx.cpu: hardware has 6 breakpoints, 4 watchpoints^M
19 Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)^M
20 Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06431041 (mfg: 0x020, part: 0x6431, ver: 0x0)^M
21 Warn : JTAG tap: stm32f4xx.bs UNEXPECTED: 0x06431041 (mfg: 0x020, part: 0x6431, ver: 0x0)^M
22 Error: JTAG tap: stm32f4xx.bs expected 1 of 1: 0x06413041 (mfg: 0x020, part: 0x6413, ver: 0x0)^M
23 Error: Trying to use configured scan chain anyway...^M
24 Warn : Bypassing JTAG setup events due to errors^M
25 Info : accepting 'gdb' connection on tcp/3333^M
26 Info : device id = 0x10006431^M
27 Info : flash size = 512kbytes^M
28 Info : Auto-detected RTOS: FreeRTOS^M
It seems the wrong config file cause error.
I'm using BCM9WCD1EVAL1.cfg and stm32f4x.cfg which are included by default SDK
Does anyone have an idea?
Thanks,
Soohwan.
Solved! Go to Solution.
- Labels:
-
Debug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Soohwan,
It looks that "eclipse debug" launch "build", but for us need only debug.
Press in eclipse, green "bug" dropdown button and select wiced-sdk debug .
If problem, go to again green "bug" dropdown button and select debug configuration, select "wiced-sdk debug" configuration, and "disable auto build" and press Debug button
BR.
Darius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
What is additional word "debug" in make string?
"snip.mcs-BCM94343WWCD1-FreeRTOS-LwIP-SDIO-debug download debug run no_dct"
Maybe, try remove it.
To debug, need use eclipse debug command.
BR.
Darius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Darius,
The word "debug" you highlighted in red is used for download debug symbol
to target,
if not use the word , the gdb start log wouldn't appear, that's why I used
the word "debug".
BTW, how can I use eclipse debug commnad?
BR.
Soohwan.
2017-08-23 15:24 GMT+09:00 sqlsql_2244756 <community-manager@cypress.com>:
<http://www.cypress.com>
Cypress Developer Community
<https://community.cypress.com/?et=watches.email.thread>
<question> Open OCD debug error with BCM94343WWCD1
reply from sqlsql_2244756
<https://community.cypress.com/people/sqlsql_2244756?et=watches.email.thread>
in WICED Studio Wi-Fi/Combo Forums - View the full discussion
<https://community.cypress.com/message/140743?et=watches.email.thread#140743>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In WICED SDK for debug you must use eclipse debug command.
How to use read startup doc in
doc/WICED-QSG204.pdf
BR.
Darius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Darius,
As you replied, I checked the doc and it seems correct that I remove second
"debug" word in the build string.
However after downloading debug image and lauch the debug by F11 the SDK
display an error
like "tools/makefiles/wiced_config.mk:565: *** No platform specified.
Options are: BCM94343WWCD1. Stop."
and I traced this error and it seems to come from different $(MAKECMDGOALS)
value,
when first build (build for debug image download to EVB) the
"$(MAKECMDGOALS)" correct and there was no error.
but the second build when lauchingn debugger , the variable
"$(MAKECMDGOALS)" changed
and it doesn't include nessasarry components that make is looking for.
first build variable
MAKEFILE MAKECMDGOALS=snip.mcs-BCM94343WWCD1-FreeRTOS-LwIP-SDIO-debug
no_dct OTA2_SUPPORT is disabled
when launching debug the variable is like below
MAKEFILE MAKECMDGOALS=Default OTA2_SUPPORT is disabled
Do you have any idea?
BR
Soohwan.
2017-08-23 18:07 GMT+09:00 sqlsql_2244756 <community-manager@cypress.com>:
<http://www.cypress.com>
Cypress Developer Community
<https://community.cypress.com/?et=watches.email.thread>
<question> Open OCD debug error with BCM94343WWCD1
reply from sqlsql_2244756
<https://community.cypress.com/people/sqlsql_2244756?et=watches.email.thread>
in WICED Studio Wi-Fi/Combo Forums - View the full discussion
<https://community.cypress.com/message/140749?et=watches.email.thread#140749>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Soohwan,
It looks that "eclipse debug" launch "build", but for us need only debug.
Press in eclipse, green "bug" dropdown button and select wiced-sdk debug .
If problem, go to again green "bug" dropdown button and select debug configuration, select "wiced-sdk debug" configuration, and "disable auto build" and press Debug button
BR.
Darius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Darius,
As you informed me I fixed the configuration and it seems go further one
step more,
however the following error occurred!
Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run. Try "help target".
Don't know how to run. Try "help target".
is it also related configuration?
BR
Soohwan
2017-08-24 17:20 GMT+09:00 sqlsql_2244756 <community-manager@cypress.com>:
<http://www.cypress.com>
Cypress Developer Community
<https://community.cypress.com/?et=watches.email.thread>
<question> Open OCD debug error with BCM94343WWCD1
reply from sqlsql_2244756
<https://community.cypress.com/people/sqlsql_2244756?et=watches.email.thread>
in WICED Studio Wi-Fi/Combo Forums - View the full discussion
<https://community.cypress.com/message/140809?et=watches.email.thread#140809>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Compare other configuration options..
Check path to arm-none-eabi-gdb.exe
Check options ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Darius,
Thanks for your kind answer, but I still have error, so I reinstall hole SDK and run default snip.scan for debug test.
firstly when I post the issue for the first time, there was Open OCD config section in the "debug configuration"
however after I reinstall the SDK it disappeared, anyhow, your environment in the picture in your answer also doesn't have Open OCD debug
configuration section too.
the followings are my situation so far.
1. set break point
2. debug image build and download (double click the build string in the following picture)
3. check "debug configuration"
3-1. C/C++ Application settings
(main tab)
(Debugger tab)
3-2. check "GDB Hardware Debugging"
(main tab)
(Debugger tab)
(startup tab)
4. start debug at "GDB Hardware Debugging" by pushing "debug" button.
5.after launching debugger , I got following screen.
"No source available for "0x80005b6"
I was expecting break stop at the point I set which is "wiced_init" , but instead stopping at the point,
it seems to be stopped somewhere else that I don't know where, and it seems GDB is working but it isn't the way I expect.
At this point if I press "Resume" like int the following picture, GDB seems to work with "wwd_bus_protocol.c"
But I didn't set break point in that file.
Do you have any idea?
BR,
Soohwan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Congratulation Soohwan!
Your debugger begun working.
Advices:
After first stop, reinit your breakpoint (remove-add).
Sometimes need delete all breakpoints in breakpoints windows
Sometimes need manualy delete openocd gdb task from windows task manager.
My WICED-SDK 3.7 so pictures can be some different. Additional I have installed plugins, but this for jlink jtag adapter.
BR.
Darius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Darius,
Thanks for your great help.
I finally managed to stop at the break point I set
BTW, I still wonder what's the difference between the configuration in the
following picture
in your answer you only mentioned "GDB hardware Debugging" right?
But I set both section "C/C++ Applictaion" and "GDB hardware Debugging"
Do you know what's the differece?
which section should I focus on?
The reason I am asking is that the only debugger launch by "GDB hardware
Debugging"
result in debugger working however when I laucn debugger by "C/C++
Applictaion"
I always get an error like below
Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run. Try "help target".
Don't know how to run. Try "help target".
BR
Soohwan
2017-08-25 16:35 GMT+09:00 sqlsql_2244756 <community-manager@cypress.com>:
<http://www.cypress.com>
Cypress Developer Community
<https://community.cypress.com/?et=watches.email.thread>
<question> Open OCD debug error with BCM94343WWCD1
reply from sqlsql_2244756
<https://community.cypress.com/people/sqlsql_2244756?et=watches.email.thread>
in WICED Studio Wi-Fi/Combo Forums - View the full discussion
<https://community.cypress.com/message/140882?et=watches.email.thread#140882>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
》in your answer you only mentioned "GDB hardware Debugging" right?
Yes you right.
》But I set both section "C/C++ Applictaion" and "GDB hardware Debugging"
》Do you know what's the differece?
》which section should I focus on?
Dont use "C/C++ Applictaion" configuration.
I think it was created by eclipse at first time you pressed F11 or "bug" button.
Eclipse dont have in history last config... and created new default.
At first time need press drop down "bug" button and select wiced pre config.
Second time you can try press F11 or bug button..
Later you can delete "C/C++ Applictaion" configuration.
BR.
Darius
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, Darius,
Thanks, everything is clear now.
BR
Soohwan.