9 Replies Latest reply on Mar 2, 2020 5:17 AM by AditiB_81

    [Murata Type1LD] Download firmware on a custom board

    MaGh_4580961

      Hi everybody,

       

      I hope you can help me in solving this problem.

      I have a custom board with Murata Type1LD mounted on it.

      I have an application developed and tested on Type1LD evaluation board that I'd like to download on my custom board.

       

      The micro is part of a jtag chain with other 3 mcu. It is the last in this chain.

      Using ULINK2 with both IAR and Keil I'm able to detect the micro on the board. In keil I'm also able to download a .elf or a .hex.

       

      Anyway, I'm not sure how to download the whole image of my application on the board.

       

      I'm evaluating two different options:

       

           1. Use a J-Link to download the firmware via WICED (6.2) but I'm still not able to do it.

               I found something in this forum but nothing helped me

               (this oneDownloading through Jlink Segger in WICED SDK 6.2 and future releases seemed to be the solution but didn't work, for example)

               the error I have is

       

      "Downloading Bootloader ...

                Building apps lookup table

                "**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB           access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that           you have the correct target and JTAG device plugged in. ****"

                Downloading DCT ...

                "**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB           access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that           you have the correct target and JTAG device plugged in. ****"

                syntax error at -e line 1, near "+ )

                "

           2. Build a complete .hex or .elf image to be downloaded on the board.

               I'm able to do it but the application doesn't work.

               I built my application by combining bootloader, DCT and application but it didn't work. I think I probably miss something.

       

      Does anyone have any suggestion about one (or both ) of the above points?

       

      Thanks to anyone who will help.

      Marco

        • 2. Re: [Murata Type1LD] Download firmware on a custom board
          AditiB_81

          Hi,

          For downloading the firmware via WICED onto your platform with JLINK you may need to make the following changes:

          1. Change jlink driver to libusbk (internally, Zadig was used)

          2. Add the line below to /tools/OpenOCD/jlink.cfg

          reset_config trst_and_srst srst_push_pull

           

          Following link will help:

          OpenOCD -WICED

          Thanks

          • 3. Re: [Murata Type1LD] Download firmware on a custom board
            MaGh_4580961

            Hi AditiB_81,

             

            thank you for your reply.

            Unfortunately, I already tried to follow the steps of the thread you linked, but it didn't work.

            In addition, I read that changing jlink driver is useful only with WICED Studio version older than 6.2.

             

            By changing the driver I'm not able to see J-link in Keil anymore.

             

            Above there is the content of openocd_log.txt, maybe it could help

             

            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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

            Info : Hardware version: 10.10

            Info : VTarget = 3.399 V

            Info : clock speed 1000 kHz

            Error: JTAG scan chain interrogation failed: all zeroes

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

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

            Error: stm32f4xx.cpu: IR capture error; saw 0x00 not 0x01

            Warn : Bypassing JTAG setup events due to errors

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            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 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 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116

            in procedure 'ocd_bouncer'

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

            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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

            Info : Hardware version: 10.10

            Info : VTarget = 3.399 V

            Info : clock speed 1000 kHz

            Error: JTAG scan chain interrogation failed: all zeroes

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

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

            Error: stm32f4xx.cpu: IR capture error; saw 0x00 not 0x01

            Warn : Bypassing JTAG setup events due to errors

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            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 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 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116

            in procedure 'ocd_bouncer'

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

            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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

            Info : Hardware version: 10.10

            Info : VTarget = 3.399 V

            Info : clock speed 1000 kHz

            Error: JTAG scan chain interrogation failed: all zeroes

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

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

            Error: stm32f4xx.cpu: IR capture error; saw 0x00 not 0x01

            Warn : Bypassing JTAG setup events due to errors

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            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 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 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116

            in procedure 'ocd_bouncer'

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

            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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

            Info : Hardware version: 10.10

            Info : VTarget = 3.399 V

            Info : clock speed 1000 kHz

            Error: JTAG scan chain interrogation failed: all zeroes

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

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

            Error: stm32f4xx.cpu: IR capture error; saw 0x00 not 0x01

            Warn : Bypassing JTAG setup events due to errors

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            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 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 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116

            in procedure 'ocd_bouncer'

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

            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_push_pull 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

            post_init_psoc6_setup

            Info : J-Link V10 compiled Jan  7 2020 16:51:47

            Info : Hardware version: 10.10

            Info : VTarget = 3.399 V

            Info : clock speed 1000 kHz

            Error: JTAG scan chain interrogation failed: all zeroes

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

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

            Error: stm32f4xx.cpu: IR capture error; saw 0x00 not 0x01

            Warn : Bypassing JTAG setup events due to errors

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Invalid ACK (0) in DAP response

            Error: Could not initialize the debug port

            embedded:startup.tcl:21: Error:

            in procedure 'sflash_write_file'

            in procedure 'sflash_init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 261

            in procedure 'init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 155

            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 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 'stm32f4xx.cpu' called at file "./tools/OpenOCD/stm32f4x.cfg", line 116

            in procedure 'ocd_bouncer'

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

             

            • 4. Re: [Murata Type1LD] Download firmware on a custom board
              MaGh_4580961

              Update

               

              As I already wrote, the chip is the last of a jtag chain made with other 3 mcu.

              By accessing the chip direcly (we are able to remove some resistors to "isolate" the chip) I'm now able to see, at least, the stm32 but still I'm not able to download the application correctly.

               

              Hereafter the "new" openocd_log.txt

               

              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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

              Info : Hardware version: 10.10

              Info : VTarget = 3.393 V

              Info : clock speed 1000 kHz

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Info : stm32f4xx.cpu: hardware has 6 breakpoints, 4 watchpoints

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Error: checksum mismatch

               

               

              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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

              Info : Hardware version: 10.10

              Info : VTarget = 3.393 V

              Info : clock speed 1000 kHz

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Info : stm32f4xx.cpu: hardware has 6 breakpoints, 4 watchpoints

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              auto erase enabled

              Info : device id = 0x30006441

              Info : flash size = 1024kbytes

              Info : Padding image section 0 with 636 bytes

              wrote 16384 bytes from file build/waf.bootloader-NoOS-MurataType1LD/binary/waf.bootloader-NoOS-MurataType1LD.stripped.elf in 0.735000s (21.769 KiB/s)

              shutdown command invoked

              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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

              Info : Hardware version: 10.10

              Info : VTarget = 3.393 V

              Info : clock speed 1000 kHz

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Info : stm32f4xx.cpu: hardware has 6 breakpoints, 4 watchpoints

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Error: checksum mismatch

               

               

              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_push_pull 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 : J-Link V10 compiled Jan  7 2020 16:51:47

              Info : Hardware version: 10.10

              Info : VTarget = 3.393 V

              Info : clock speed 1000 kHz

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Info : stm32f4xx.cpu: hardware has 6 breakpoints, 4 watchpoints

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              auto erase enabled

              Info : device id = 0x30006441

              Info : flash size = 1024kbytes

              wrote 16384 bytes from file build/snip.websocket_server-MurataType1LD/DCT.stripped.elf in 0.665000s (24.060 KiB/s)

              shutdown command invoked

              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_push_pull 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

              post_init_psoc6_setup

              Info : J-Link V10 compiled Jan  7 2020 16:51:47

              Info : Hardware version: 10.10

              Info : VTarget = 3.393 V

              Info : clock speed 1000 kHz

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Info : stm32f4xx.cpu: hardware has 6 breakpoints, 4 watchpoints

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              27116 bytes written at address 0x20000000

              downloaded 27116 bytes in 0.392000s (67.552 KiB/s)

              entry_address= 536888725

              stack_address= 536907640

              buffer_size= 16384

              pc (/32): 0x20004595

              Total write size is 390466.

              writing 16384 bytes at 4096

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20005b9c msp: 0x20008f18

              loadimage address 536870940 foffset 0 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.238000s (67.227 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200055d0 msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20005b70 msp: 0x20008f30

              ****************** Result: OK

              writing 16384 bytes at 20480

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20006262 msp: 0x20008f18

              loadimage address 536870940 foffset 16384 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.252000s (63.492 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200055fc msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006220 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 36864

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20006258 msp: 0x20008f18

              loadimage address 536870940 foffset 32768 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.239000s (66.946 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200061b8 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20006258 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 53248

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20005b78 msp: 0x20008f18

              loadimage address 536870940 foffset 49152 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.239000s (66.946 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200061ba msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x200061f6 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 69632

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20004670 msp: 0x20008f30

              loadimage address 536870940 foffset 65536 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.239000s (66.946 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100080b pc: 0x200061c0 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006222 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 86016

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20005b98 msp: 0x20008f18

              loadimage address 536870940 foffset 81920 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.242000s (66.116 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20005334 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005b86 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 102400

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006230 msp: 0x20008f18

              loadimage address 536870940 foffset 98304 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.241000s (66.390 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x20005308 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x200061c8 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 118784

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20005bae msp: 0x20008f18

              loadimage address 536870940 foffset 114688 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.238000s (67.227 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100140b pc: 0x200061be msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x200061d2 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 135168

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006218 msp: 0x20008f18

              loadimage address 536870940 foffset 131072 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.239000s (66.946 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200061b8 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005b8a msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 151552

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x2000626a msp: 0x20008f18

              loadimage address 536870940 foffset 147456 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.239000s (66.946 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20005328 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x2000625a msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 167936

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006218 msp: 0x20008f18

              loadimage address 536870940 foffset 163840 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.238000s (67.227 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x2000533c msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20005b76 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 184320

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200061e8 msp: 0x20008f18

              loadimage address 536870940 foffset 180224 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.237000s (67.511 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x2000533c msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005bac msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 200704

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005b8a msp: 0x20008f18

              loadimage address 536870940 foffset 196608 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.238000s (67.227 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20005326 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005b8a msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 217088

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005b94 msp: 0x20008f18

              loadimage address 536870940 foffset 212992 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.237000s (67.511 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100080b pc: 0x200061c0 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006228 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 233472

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20006262 msp: 0x20008f18

              loadimage address 536870940 foffset 229376 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.238000s (67.227 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x200061c2 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005b8e msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 249856

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006230 msp: 0x20008f18

              loadimage address 536870940 foffset 245760 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.238000s (67.227 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x2000618c msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x87001c0b pc: 0x2000620a msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 266240

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200061e0 msp: 0x20008f18

              loadimage address 536870940 foffset 262144 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.235000s (68.085 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x2000533c msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x2000625e msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 282624

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20006258 msp: 0x20008f18

              loadimage address 536870940 foffset 278528 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.233000s (68.670 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x200055de msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x2000466e msp: 0x20008f30

              ****************** Result: OK

              writing 16384 bytes at 299008

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20005ba0 msp: 0x20008f18

              loadimage address 536870940 foffset 294912 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.234000s (68.376 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20005338 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20006258 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 315392

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x20006202 msp: 0x20008f18

              loadimage address 536870940 foffset 311296 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.236000s (67.797 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200055e8 msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005b86 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 331776

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20005ba6 msp: 0x20008f18

              loadimage address 536870940 foffset 327680 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.242000s (66.116 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x2000531e msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20006260 msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 348160

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x20006256 msp: 0x20008f18

              loadimage address 536870940 foffset 344064 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.238000s (67.227 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200061c2 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x2000622a msp: 0x20008f18

              ****************** Result: OK

              writing 16384 bytes at 364544

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x4100000b pc: 0x20004694 msp: 0x20008f30

              loadimage address 536870940 foffset 360448 16384

              16384 bytes written at address 0x2000001c

              downloaded 16384 bytes in 0.239000s (66.946 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x6100000b pc: 0x2000618a msp: 0x20008e88

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x0100000b pc: 0x20006258 msp: 0x20008f18

              ****************** Result: OK

              writing 13634 bytes at 380928

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x8100000b pc: 0x200061d6 msp: 0x20008f18

              loadimage address 536870940 foffset 376832 13634

              13634 bytes written at address 0x2000001c

              downloaded 13634 bytes in 0.195000s (68.279 KiB/s)

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x20005322 msp: 0x20008e78

              target halted due to debug-request, current mode: Handler SVCall

              xPSR: 0x2100000b pc: 0x200061dc msp: 0x20008f18

              ****************** Result: OK

              shutdown command invoked

              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_push_pull 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

              post_init_psoc6_setup

              Info : J-Link V10 compiled Jan  7 2020 16:51:47

              Info : Hardware version: 10.10

              Info : VTarget = 3.393 V

              Info : clock speed 1000 kHz

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Info : stm32f4xx.cpu: hardware has 6 breakpoints, 4 watchpoints

              Info : JTAG tap: stm32f4xx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4)

              Info : JTAG tap: stm32f4xx.bs tap/device found: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Warn : JTAG tap: stm32f4xx.bs       UNEXPECTED: 0x06441041 (mfg: 0x020 (STMicroelectronics), part: 0x6441, ver: 0x0)

              Error: JTAG tap: stm32f4xx.bs  expected 1 of 1: 0x06413041 (mfg: 0x020 (STMicroelectronics), part: 0x6413, ver: 0x0)

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

              Warn : Bypassing JTAG setup events due to errors

              Error: timed out while waiting for target halted

              TARGET: stm32f4xx.cpu - Not halted

              in procedure 'sflash_write_file'

              in procedure 'sflash_init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 261

              in procedure 'init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 155

              in procedure 'ocd_bouncer'

              in procedure 'transport'

              in procedure 'ocd_bouncer'

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

              in procedure 'reset' called at file "./tools/OpenOCD/stm32f4x.cfg", line 125

              in procedure 'ocd_bouncer'

               

               

              in procedure 'sflash_write_file'

              in procedure 'sflash_init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 261

              in procedure 'init' called at file "apps/waf/sflash_write/sflash_write.tcl", line 155

              in procedure 'ocd_bouncer'

               

              • 5. Re: [Murata Type1LD] Download firmware on a custom board
                AditiB_81

                Hi,

                I successfully downloaded an application(snip.scan) on MurataType1LD device by doing the changes I suggested to you. You may recheck the steps again:

                ->Connect the Jlink segger to host PC. To download an application using j-link Segger, you need to change the jlink driver to libusbK.

                -> Replace Driver

                ->Check the device manager of host PC to verify that J-link segger appears under libusbK USB devices.

                ->Add the line below to /tools/OpenOCD/jlink.cfg

                   reset_config trst_and_srst srst_push_pull

                ->Make Target - snip.scan-MurataType1LD JTAG=jlink WIPE=1 download run (Specify the application and platform accordingly)

                I did these changes on WICED STUDIO version 6.4 and it worked. Let me know if you face errors.

                 

                Thanks

                 

                1 of 1 people found this helpful
                • 6. Re: [Murata Type1LD] Download firmware on a custom board
                  MaGh_4580961

                  Hi AditiB_81,

                   

                  I did the step you seggested again. Unfortunately, the results were the same. I attached "openocd_log.txt" and "jlink.cfg"

                  The console, instead, shows the following

                   

                   

                  ...and I don't know why if I clean and compile again the message changes (not to log)

                   

                   

                  I'm using WICED Studio 6.2.

                   

                  Thanks,

                  Marco

                  • 7. Re: [Murata Type1LD] Download firmware on a custom board
                    AditiB_81

                    Hi,

                    I successfully downloaded the application in MurataType1LD device which is supported by WICED SDK. Could you tell that the custom board you are using to download your application, is it supported by WICED SDK or is it your own kit?

                     

                    Thanks

                    1 of 1 people found this helpful
                    • 8. Re: [Murata Type1LD] Download firmware on a custom board
                      MaGh_4580961

                      Hi AditiB_81,

                       

                      we have a custom board with MurataType 1LD mounted on it.

                      I guess that since MurataType 1LD is supported by WICED Studio and if the connections to the module are ok I should have no problem. Am I right?

                       

                      What seems strange to me is that, as you can see from the log file attached in the previous reply, J-Link debugger is recognized but I'm not able to download the application (one of the errors is "Error: timed out while waiting for target halted")

                      • 9. Re: [Murata Type1LD] Download firmware on a custom board
                        AditiB_81

                        Hi,

                        Could you provide us with your j-link hardware connections and how are you connecting it (wiring or cable)?

                        PFA image to get an idea of the connection of my setup

                         

                        Thanks