13 Replies Latest reply on May 6, 2020 4:45 AM by RaD_4001476

    Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4

    RaD_4001476

      Hi,

       

      I am unable to download the image to Inventek 43362 module using olimex ARM-USB-TINY-H debugger.

       

      Below is the make target used:

      gct.google-ISM43362_M3G_L44-ThreadX-NetX-SDIO JTAG=Olimex_ARM-USB-TINY-H download run

       

      I get the below error, when I check the Openocd log file:

       

      Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)

      Licensed under GNU GPL v2

      For bug reports, read

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

      trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst

      adapter speed: 1000 kHz

      adapter_nsrst_delay: 100

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

      jtag_ntrst_delay: 100

      Warn : target name is deprecated use: 'cortex_m'

      jtag_init

      Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND

      Error: no device found

      Error: unable to open ftdi device with vid 15ba, pid 002a, description 'Olimex OpenOCD JTAG ARM-USB-TINY-H', serial '*' at bus location '*'

       

      I have installed the Open OCD drivers as per the instructions provided in Olimex_README.txt (43xxx_Wi-fi\tools\OpenOCD)

       

      Below is the message I get when I run testlibusb.exe

       

      D:\IOT_Payload\libusb-win32-bin-1.2.6.0\bin\x86>testlibusb.exe

       

      Dev #0: 0000 - 0000

        Dev #1: 15BA - Olimex OpenOCD JTAG ARM-USB-TINY-H

        Dev #2: 15BA - Olimex OpenOCD JTAG ARM-USB-TINY-H

       

      Can some one help me on this ?

       

      Thanks,

      Regards,

      Raghu

        • 1. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
          MuraliR_36

          Hi

           

          Could you try reinstalling the USB drivers using Zadig?

          Also, this looks like this is an issue with the platform files for ISM43362_M3G_L44 module.

          I tried this out with BCM943362WCD4 module and the image download succeeds without any issues.

           

          Thanks

          1 of 1 people found this helpful
          • 2. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
            RaD_4001476

            Hi,

             

            You mentioned about issue in the Platform files.

             

            In general, what configurations pertaining to the debugger have to be changed in the platform files or any other files?

            Also, when you say platform files are these the files which you are referring to ?

            Under platforms folder (ISM43362_M3G_L44)

            platform.c

            platform.h

            platform_config.h

             

            Regards,

            Raghu

            • 3. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
              MuraliR_36

              Hi Raghu

               

              Could you share your platform files so that i can look into it and revert back to you with the changes that maybe required?

               

              Thanks

              Murali

              • 4. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                RaD_4001476

                Hi Murali,

                 

                Find the platform files attached.

                 

                Regards,

                Raghu

                • 5. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                  RaD_4001476

                  Hi Murali,

                   

                  Any updates on the setting changes?

                   

                  Thanks,

                  Regards,

                  Raghu

                  • 6. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                    MuraliR_36

                    Hi Raghu

                     

                    I compiled and downloaded my app on BCM943362WCD4 module using the platform make file shared by you. Everything seems to be working fine. And i don't think that there's any issue with the platform.c .h and the config.h files as these files, usually don't affect the download procedure.

                    Also the error is listed as

                    Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND

                    Error: no device found

                    Just to be sure that this issue isn't being caused by the USB drivers, could you please uninstall the drivers and try reinstalling them using Zadig?

                    if the issue persists, try contacting Inventek.

                     

                    Thanks

                    Murali

                    1 of 1 people found this helpful
                    • 7. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                      RaD_4001476

                      Hi Murali,

                       

                      OK, I will retry with Zadig.

                      Can you let me know the libusb version which you are using ?

                      I currently have installed 1.2.6 version

                       

                      Thanks,

                      Raghu

                      • 8. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                        MuraliR_36

                        Hi Raghu

                         

                        The driver version of the installed Olimex OpenOCD JTAG ARM-USB-TINY-H driver is 6.1.7600.16385.

                        The driver version of the installed libusb is 3.0.7.0 (I'm guessing this is because of the onboard FTDI chip).

                         

                        Thanks

                        Murali

                        • 9. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                          RaD_4001476

                          Hi Murali,

                           

                          I installed the drivers using zadig. Now I am getting a different set of errors when I check in the openocd logs.

                          Do you have any idea what on what could be the reason for the below errors?

                           

                          Open On-Chip Debugger 0.10.0+dev-00227-g0d15c62 (2018-03-27-15:19)

                          Licensed under GNU GPL v2

                          For bug reports, read

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

                          trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst

                          adapter speed: 1000 kHz

                          adapter_nsrst_delay: 100

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

                          jtag_ntrst_delay: 100

                          Warn : target name is deprecated use: 'cortex_m'

                          jtag_init

                          Info : clock speed 1000 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: stm32f2xxx.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

                          embedded:startup.tcl:21: Error:

                          in procedure 'init'

                          in procedure 'ocd_bouncer'

                          in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578

                          in procedure 'stm32f2xxx.cpu' called at file "./tools/OpenOCD/stm32f2x.cfg", line 116

                          in procedure 'ocd_bouncer'

                          at file "embedded:startup.tcl", line 21

                          embedded:startup.tcl:21: Error:

                          in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578

                          in procedure 'stm32f2xxx.cpu' called at file "./tools/OpenOCD/stm32f2x.cfg", line 116

                          in procedure 'ocd_bouncer'

                          at file "embedded:startup.tcl", line 21

                           

                          Thanks,

                          Raghu

                          • 10. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                            MuraliR_36

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

                             

                            --> Looks like there's some issue with the hardware connections.

                             

                            As i mentioned before, this looks like an issue with the inventek module as it works fine with the BCM943362WCD4. Please contact Inventek for a possible solution.

                            1 of 1 people found this helpful
                            • 12. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                              JeGu_1699796

                              Hi DiBa_1995216

                              Has this issue been solved? We encountered exactly the same issue today. Is there any solution ?

                              WICED6.4 + ISM4343-WBM-L151 (SSBWMN12)

                               

                              =========log=========================================================

                               

                              MBPRX:43xxx_Wi-Fi xavieryin$ pwd

                              /Users/xavieryin/Documents/WICED-Studio-6.4/43xxx_Wi-Fi

                              MBPRX:43xxx_Wi-Fi xavieryin$ "./tools/OpenOCD/OSX/openocd-all-brcm-libftdi" -s "./tools/OpenOCD/scripts" -f ./tools/OpenOCD/jlink.cfg -f ./tools/OpenOCD/stm32f4x.cfg -f ./tools/OpenOCD/stm32f4x-flash-app.cfg -c "verify_image_checksum build/waf.bootloader-NoOS-ISM4343_WBM_L151/binary/waf.bootloader-NoOS-ISM4343_WBM_L151.stripped.elf" -c shutdown

                              Open On-Chip Debugger 0.10.0+dev-00227-g3de019de (2018-03-28-15:02)

                              Licensed under GNU GPL v2

                              For bug reports, read

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

                              trst_and_srst separate srst_nogate trst_push_pull srst_push_pull connect_assert_srst

                              adapter speed: 1000 kHz

                              adapter_nsrst_delay: 100

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

                              jtag_ntrst_delay: 100

                              jtag_init

                              Info : J-Link Lite-Cortex-M V8 compiled Sep 15 2016 12:05:01

                              Info : Hardware version: 8.00

                              Info : VTarget = 3.261 V

                              Info : clock speed 1000 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: stm32f4xx.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

                              embedded:startup.tcl:21: Error:

                              in procedure 'init' called at file "./tools/OpenOCD/stm32f4x-flash-app.cfg", line 32

                              in procedure 'ocd_bouncer'

                              in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578

                              in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 117

                              in procedure 'ocd_bouncer'

                              at file "embedded:startup.tcl", line 21

                              embedded:startup.tcl:21: Error:

                              in procedure 'jtag_init' called at file "../WICED-OpenOCD/src/jtag/core.c", line 1578

                              in procedure 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 117

                              in procedure 'ocd_bouncer'

                              at file "embedded:startup.tcl", line 21

                              • 13. Re: Unable to connect to Inventek 43362 using Olimex ARM-USB-TINY-H debugger in WICED SDK 6.4
                                RaD_4001476

                                Hi JeGu,

                                 

                                I didn't get any resolution for this. The issue is not solved.

                                 

                                Regards