cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

New Contributor II

Hi,

I am working on BCM943909WCD1, and whenever I placing debug break point(s) in "ota2_bootloader.c", the following error pops up.

pastedImage_0.png

The "ota2_bootloader.c" file is present in that particular directory, yet "No source file" error pops up.

Kindly help and do let me know if I need to share more relevant snippets.

Thanks in advance!

0 Likes
Reply
1 Solution
Employee

Hi,

OTA2 bootloader is downloaded by default when ota2_example application is executed.

If you want to debug the ota2_boatloader specifically please use the make target : waf.ota2_bootloader-NoOS-NoNS-BCM943909WCD1_3-P320-SoC.43909 and perform clean operation before the build target.

For OTA2 implementation, please go through the OTA2 document in : 43xxx_Wi-Fi/doc/WICED-OTA2.pdf

Can you please let us know the specific reason to debug ota2_bootloader and any other issues you're facing while running OTA2.

Thanks.

View solution in original post

2 Replies
Employee

Hi,

OTA2 bootloader is downloaded by default when ota2_example application is executed.

If you want to debug the ota2_boatloader specifically please use the make target : waf.ota2_bootloader-NoOS-NoNS-BCM943909WCD1_3-P320-SoC.43909 and perform clean operation before the build target.

For OTA2 implementation, please go through the OTA2 document in : 43xxx_Wi-Fi/doc/WICED-OTA2.pdf

Can you please let us know the specific reason to debug ota2_bootloader and any other issues you're facing while running OTA2.

Thanks.

View solution in original post

New Contributor II

Hi KotnaniK_71

Thank you for your swift response and help.

I have run into another issue, where whenever I build "snip.pers-BCM943909WCD1_3.B1-ThreadX-NetX_Duo-debug ota2_download" configuration, a dialog box with the message: "openocd-all-brcm-libftdi.exe stopped working" pops up. Any help on that?

The log obtained from "openocd_log.txt" is below:

" trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst

trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst

adapter speed: 100 kHz

adapter_nsrst_delay: 100

Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.

jtag_ntrst_delay: 100

Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED

Info : clock speed 100 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: BCM43909.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

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

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: BCM43909.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

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 "

The motivation behind debugging ota2_bootloader.c is to understand the code flow and eventually be able to integrate wolfSSL library.

0 Likes
Reply