12 Replies Latest reply on Feb 9, 2020 6:59 PM by YuxianL_01

    miniprog4 cannot find cy8cproto-063-ble or my proc6 board

    SuMa_296631

      I have just purchased a Miniprog4 as I want to use ModusToolbox (V2).

      I also have a CY8CPROTO-063-BLE development board and a board I made up myself.

      Using the (Windows based) PROC Creator I can use the programmer on the CY8PROTO-063 BLE to program the device and, after I snapped it off the main board, to program my own board.

      In the Modus Toolbox environment I can also use the snapped off programmer to both boards. However it is inconvenient to measure the current going to my own board (which I want to do to find the deep sleep current) which is why I purchased the MiniProg 4.

      However the Modus Toolbox environment can find the MiniProg4 quite happily but it always says (in red):

       

      Started by GNU MCU Eclipse

      Error: kitprog3: failed to acquire PSoC device

      (in black)

      Info: clock speed 1000kHz

      (back to read)

      Error: DAP 'psoc6.cpu' initialization failed (check connection, power, etc.)

       

      for both the prototyping board and mine.

      I'm suspicious of the part about the power as the 'Target Power' led on the MiniProg4 does not light so I assume it is not providing power to the boards.

      Is that a correct interpretation?

      How to get the MiniProg4 to power the boards?

      Susan

        • 1. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
          SuMa_296631

          Fixed it.

          I needed to download and run the Cypress programmer on my iMac.

          That let me upgrade the firmware, select the right processor etc. and turn on the target power.

          Susan

          • 2. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
            RakshithM_16

            Hi SuMa_296631,

             

            Yes, your interpretation is correct. By default, MiniProg 4 does not power the device when used with ModusToolbox 2.0.

             

            Steps to enable MiniProg 4 to power the device -

            1.  Click on Run tab in Menu bar and click on Run Configurations as shown -

            2. Select Debugger tab in the Run Configurations window as shown -

            3. Add the 3 lines of commands after "-c "source [find target/psoc6.cfg]" " line in the Config options as shown -

             

            The commands are as follows -

            > -c "kitprog3 power_config on 3300"

            > -c "init"

            > -c "kitprog3 power_control on"

            4. Click on Apply and then Run.

             

            This should toggle the power and you should be able to program the device successfully.

             

            Another easy way is to download Cypress Programmer and program your device using the same.

             

            Hope this helps,

            Regards,

            Rakshith M B

            • 3. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
              SuMa_296631

              Hello Rakshith,

              I have marked your response as the correct one as it also answers the other thing that I was grumbling about in my mind - why do I need another program just to turn on the power.

              Yours is the solution - mine was a work-around

              Susan

              • 4. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                SuMa_296631

                If I make the Config Options exactly as you have specified:

                 

                -s "${openocd_path}/../scripts"

                -s "./libs/TARGET_CY8CPROTO-063-BLE/COMPONENT_BSP_DESIGN_MODUS/GeneratedSource"

                -c "source [find interface/kitprog3.cfg]"

                -c "source [find target/psoc6.cfg]"

                -c "kitprog power_config on 3300"

                -c "init"

                -c kitprog3 power_control on"

                -c "psoc6 sflash_restrictions 1"

                -c "if [catch {program ${cy_prj_path}/build/CY8CPROTO-063-BLE/Debug/mtb-example-psoc6-empty-app.hex} ] { echo {** Program operation failed **} } else { echo {** Program operation completed successfully **} }"

                -c "reset_config srst_only;reset run;psoc6.dap dpreg 0x04 0x00;shutdown"

                 

                then I get:

                 

                ** Programming Finished **

                ** Program operation completed successfully **

                srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst

                target halted due to breakpoint, current mode: Thread

                xPSR: 0x61000000 pc: 0x0800000c msp: 0x08000870

                Error: psoc6.cpu.cm4 -- clearing lockup after double fault

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

                xPSR: 0x61000003 pc: 0x8008f3ee msp: 0x080477e0

                Polling target psoc6.cpu.cm4 failed, trying to reexamine

                Info : psoc6.cpu.cm4: hardware has 6 breakpoints, 4 watchpoints

                shutdown command invoked

                 

                so the target power is turn on but the app is not run, even after a local 'reset'.

                (This is not much use for me in that I really need to have the app run without the debugger so that the 'deep sleep' command will actually put the MCU into deep sleep.)

                 

                If I try the commands as you have specified in the "Debug Configurations" I get various errors, mainly around the fact that some commands need to be executed before and/or after the "configure" and "init" commands.

                What works for me is:

                 

                -s "${openocd_path}/../scripts"

                -s "./libs/TARGET_CY8CPROTO-063-BLE/COMPONENT_BSP_DESIGN_MODUS/GeneratedSource"

                -c "source [find interface/kitprog3.cfg]"

                -c "puts stderr {Started by GNU MCU Eclipse}"

                -c "source [find target/psoc6.cfg]"

                -c "kitprog3 power_config on 3300"

                -c "psoc6.cpu.cm4 configure -rtos auto -rtos-wipe-on-reset-halt 1"

                -c "gdb_port 3332"

                -c "psoc6 sflash_restrictions 1"

                -c "init; reset init"

                -c "kitprog3 power_control on"

                 

                At least this works in that the power is turned on, the code is uploaded and the debugger starts and can run/debug the app.

                Susan

                • 5. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                  RakshithM_16

                  Hi SuMa_296631,

                   

                  1. Please let me know where you made the changes and please share the screenshot of the window.

                  2. Please let me know the Launch Configuration that you selected to program and debug your device. Can you please try erasing your device using Cypress Programmer and repeat the above mentioned steps to program your device and see if this resolves your issue.

                  3. The steps mentioned was to program the device and not for debug. For debug -

                  • Open Run Configurations.
                  • Select <project_name> Debug (KitProg3) under GDB OpenOCD Debugging
                  • Click on the Debugger tab and in Config options: add

                                 a) -c "kitprog3 power_config on 3300" after -c "source [find target/psoc6.cfg]"

                                 b) -c "kitprog3 power_control on" after -c "init; reset init"

                  • So your Config options: should be similar to -

                            -s "${openocd_path}/../scripts"

                            -s "./libs/TARGET_CY8CPROTO-063-BLE/COMPONENT_BSP_DESIGN_MODUS/GeneratedSource"

                            -c "source [find interface/kitprog3.cfg]"

                            -c "puts stderr {Started by GNU MCU Eclipse}"

                            -c "source [find target/psoc6.cfg]"

                            -c "kitprog3 power_config on 3300"

                            -c "psoc6.cpu.cm4 configure -rtos auto -rtos-wipe-on-reset-halt 1"

                            -c "gdb_port 3332"

                            -c "psoc6 sflash_restrictions 1"

                            -c "init; reset init"

                            -c "kitprog3 power_control on"

                  • Click on <project_name> Debug (KitProg3) to start a debug session.

                   

                  Please let me know if the steps mentioned solves your issue.

                   

                  Hope this helps,

                   

                  Thanks and Regards,

                  Rakshith M B

                  • 6. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                    SuMa_296631

                    1 For the run configurations:

                    Screen Shot 2019-12-08 at 17.05.29 .png

                    The complete set of 'config options' is in my previous reply.

                    2: The launch configuration is the ""BLE_Find_Me program (KitProg3)" one in the 'launches' area:

                    Screen Shot 2019-12-08 at 17.09.45 .png

                    3: Those are the settings I have.

                    Susan

                    • 7. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                      DheerajK_81

                      In the config options you specified, you missed the line highlighted in bold:

                      -s "${openocd_path}/../scripts"

                      -s "./libs/TARGET_CY8CPROTO-063-BLE/COMPONENT_BSP_DESIGN_MODUS/GeneratedSource"

                      -c "source [find interface/kitprog3.cfg]"

                      -c "source [find target/psoc6.cfg]"

                      -c "kitprog power_config on 3300"

                      -c "init; reset init"

                      -c kitprog3 power_control on"

                      -c "psoc6 sflash_restrictions 1"

                      -c "if [catch {program ${cy_prj_path}/build/CY8CPROTO-063-BLE/Debug/mtb-example-psoc6-empty-app.hex} ] { echo {** Program operation failed **} } else { echo {** Program operation completed successfully **} }"

                      -c "reset_config srst_only;reset run;psoc6.dap dpreg 0x04 0x00;shutdown"

                       

                      Please add this line and it will work.

                       

                      Regards,

                      Dheeraj

                      1 of 1 people found this helpful
                      • 8. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                        SuMa_296631

                        Unfortunately that makes no difference.

                        The full 'config options' text is:

                         

                        -s "${openocd_path}/../scripts"

                        -s "./libs/TARGET_CY8CPROTO-063-BLE/COMPONENT_BSP_DESIGN_MODUS/GeneratedSource"

                        -c "source [find interface/kitprog3.cfg]"

                        -c "source [find target/psoc6.cfg]"

                        -c "kitprog3 power_config on 3300"

                        -c "init; reset init"

                        -c "kitprog3 power_control on"

                        -c "psoc6 sflash_restrictions 1"

                        -c "if [catch {program ${cy_prj_path}/build/CY8CPROTO-063-BLE/Debug/mtb-example-psoc6-ble-findme.hex} ] { echo {** Program operation failed **} } else { echo {** Program operation completed successfully **} }"

                        -c "reset_config srst_only;reset run;psoc6.dap dpreg 0x04 0x00;shutdown"

                         

                        The form that this is display in is:

                        Screen Shot 2019-12-22 at 17.27.18 .png

                        Clicking the "BLE_Find_Me Program (KitProg3)" link in the "Launches" section gives:

                         

                         

                        Open On-Chip Debugger 0.10.0+dev-2.2.0.249 (2019-09-10-18:38)

                        Licensed under GNU GPL v2

                        For bug reports, read

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

                        adapter speed: 1500 kHz

                        adapter speed: 1000 kHz

                        ** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable

                        cortex_m reset_config sysresetreq

                        cortex_m reset_config vectreset

                        ocd_gdb_restart

                        Info : CMSIS-DAP: SWD  Supported

                        Info : CMSIS-DAP: FW Version = 2.0.0

                        Info : CMSIS-DAP: Interface Initialised (SWD)

                        Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1

                        Info : CMSIS-DAP: Interface ready

                        Info : kitprog3: powering up target device using KitProg3 (VTarg = 3300 mV)

                        Info : VTarget = 3.301 V

                        Info : kitprog3: acquiring PSoC device...

                        Info : clock speed 1000 kHz

                        Info : SWD DPIDR 0x6ba02477

                        Info : psoc6.cpu.cm0: hardware has 4 breakpoints, 2 watchpoints

                        ***************************************

                        ** Silicon: 0xE2F0, Family: 0x100, Rev.: 0x23 (B2)

                        ** Detected Device: CYBLE-416045-02

                        ** Detected Main Flash size, kb: 1024

                        ** Flash Boot version 1.20.1.42

                        ** Chip Protection: NORMAL

                        ***************************************

                        Info : psoc6.cpu.cm4: hardware has 6 breakpoints, 4 watchpoints

                        Info : Listening on port 3333 for gdb connections

                        Info : Listening on port 3334 for gdb connections

                        Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.

                        Info : kitprog3: acquiring PSoC device...

                        target halted due to debug-request, current mode: Thread

                        xPSR: 0x61000000 pc: 0x00000f00 msp: 0x08047800

                        --------------------------------------------

                        Failed to acquire PSoC 6 device in Test Mode

                        --------------------------------------------

                        target halted due to debug-request, current mode: Thread

                        xPSR: 0x01000000 pc: 0x00000f00 msp: 0x08047800

                        Info : kitprog3: powering up target device using KitProg3 (VTarg = 3300 mV)

                        Warn : SFlash programming allowed for regions: USER, TOC, KEY

                        Warn : Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.

                        Info : kitprog3: acquiring PSoC device...

                        target halted due to debug-request, current mode: Thread

                        xPSR: 0x61000000 pc: 0x00000f00 msp: 0x08047800

                        --------------------------------------------

                        Failed to acquire PSoC 6 device in Test Mode

                        --------------------------------------------

                        target halted due to debug-request, current mode: Thread

                        xPSR: 0x01000000 pc: 0x00000f00 msp: 0x08047800

                        ** Programming Started **

                        auto erase enabled

                        Info : Flash write discontinued at 0x100014d0, next section at 0x10002000

                        Info : Padding image section 0 at 0x100014d0 with 304 bytes (bank write end alignment)

                         

                        [  9%] [##                              ] [ Erasing     ]

                        [ 18%] [#####                           ] [ Erasing     ]

                        [ 27%] [########                        ] [ Erasing     ]

                        [ 36%] [###########                     ] [ Erasing     ]

                        [ 45%] [##############                  ] [ Erasing     ]

                        [ 54%] [#################               ] [ Erasing     ]

                        [ 63%] [####################            ] [ Erasing     ]

                        [ 72%] [#######################         ] [ Erasing     ]

                        [ 81%] [#########################       ] [ Erasing     ]

                        [ 90%] [############################    ] [ Erasing     ]

                        [100%] [################################] [ Erasing     ]

                         

                        [100%] [################################] [ Programming ]

                        Info : Padding image section 1 at 0x1000f902 with 2 bytes

                        Info : Padding image section 2 at 0x1000fc46 with 2 bytes

                        Info : Padding image section 3 at 0x1000fe86 with 2 bytes

                        Info : Padding image section 4 at 0x1001004a with 2 bytes

                        Info : Padding image section 5 at 0x100103e6 with 2 bytes

                        Info : Padding image section 6 at 0x100107da with 2 bytes

                        Info : Padding image section 7 at 0x10010aea with 2 bytes

                        Info : Padding image section 8 at 0x10010b1a with 2 bytes

                        Info : Padding image section 9 at 0x10010bae with 2 bytes

                        Info : Padding image section 10 at 0x100110f2 with 2 bytes

                        Info : Padding image section 11 at 0x10011216 with 2 bytes

                        Info : Padding image section 12 at 0x10011486 with 2 bytes

                        Info : Padding image section 13 at 0x100115a2 with 2 bytes

                        Info : Padding image section 14 at 0x1001186e with 2 bytes

                        Info : Padding image section 15 at 0x10011cde with 2 bytes

                        Info : Padding image section 16 at 0x10011e06 with 2 bytes

                        Info : Padding image section 17 at 0x10011e8a with 2 bytes

                        Info : Padding image section 18 at 0x100125f6 with 2 bytes

                        Info : Padding image section 19 at 0x10012bf2 with 2 bytes

                        Info : Padding image section 20 at 0x100130be with 2 bytes

                        Info : Padding image section 21 at 0x10013236 with 2 bytes

                        Info : Padding image section 22 at 0x10013322 with 2 bytes

                        Info : Padding image section 23 at 0x1001350e with 2 bytes

                        Info : Padding image section 24 at 0x1001357a with 2 bytes

                        Info : Padding image section 25 at 0x1001375a with 2 bytes

                        Info : Padding image section 26 at 0x10013992 with 2 bytes

                        Info : Padding image section 27 at 0x10013a9e with 2 bytes

                        Info : Padding image section 28 at 0x10013eba with 2 bytes

                        Info : Padding image section 29 at 0x1001428e with 2 bytes

                        Info : Padding image section 30 at 0x1001471e with 2 bytes

                        Info : Padding image section 31 at 0x100149fa with 2 bytes

                        Info : Padding image section 32 at 0x10014db2 with 2 bytes

                        Info : Padding image section 33 at 0x10015346 with 2 bytes

                        Info : Padding image section 34 at 0x100155e6 with 2 bytes

                        Info : Padding image section 35 at 0x1001598a with 2 bytes

                        Info : Padding image section 36 at 0x10015bfa with 2 bytes

                        Info : Padding image section 37 at 0x10015ed2 with 2 bytes

                        Info : Padding image section 38 at 0x100162da with 2 bytes

                        Info : Padding image section 39 at 0x1001656e with 2 bytes

                        Info : Padding image section 40 at 0x10016846 with 2 bytes

                        Info : Padding image section 41 at 0x100168f6 with 2 bytes

                        Info : Padding image section 42 at 0x10016996 with 2 bytes

                        Info : Padding image section 43 at 0x10016b9e with 2 bytes

                        Info : Padding image section 44 at 0x10016e2e with 2 bytes

                        Info : Padding image section 45 at 0x1001734a with 2 bytes

                        Info : Padding image section 46 at 0x10017e06 with 2 bytes

                        Info : Padding image section 47 at 0x10017fce with 2 bytes

                        Info : Padding image section 48 at 0x100181ca with 2 bytes

                        Info : Padding image section 49 at 0x1001838e with 2 bytes

                        Info : Padding image section 50 at 0x1001a522 with 2 bytes

                        Info : Padding image section 51 at 0x1001a7de with 2 bytes

                        Info : Padding image section 52 at 0x1001a876 with 2 bytes

                        Info : Padding image section 53 at 0x1001aa0e with 2 bytes

                        Info : Padding image section 54 at 0x1001ab12 with 2 bytes

                        Info : Padding image section 55 at 0x1001b4aa with 2 bytes

                        Info : Padding image section 56 at 0x1001b96a with 2 bytes

                        Info : Padding image section 57 at 0x1001c4ee with 2 bytes

                        Info : Padding image section 58 at 0x1001c56a with 2 bytes

                        Info : Padding image section 59 at 0x1001c7d2 with 2 bytes

                        Info : Padding image section 60 at 0x1001c98e with 2 bytes

                        Info : Padding image section 61 at 0x1001ccde with 2 bytes

                        Info : Padding image section 62 at 0x1001cdae with 2 bytes

                        Info : Padding image section 63 at 0x1001d35a with 2 bytes

                        Info : Padding image section 64 at 0x1001d8fe with 2 bytes

                        Info : Padding image section 65 at 0x1001db22 with 2 bytes

                        Info : Padding image section 66 at 0x1001dcbe with 2 bytes

                        Info : Padding image section 67 at 0x1001e032 with 2 bytes

                        Info : Padding image section 68 at 0x1001f01a with 2 bytes

                        Info : Padding image section 69 at 0x1001f412 with 2 bytes

                        Info : Padding image section 70 at 0x1001f5ee with 2 bytes

                        Info : Padding image section 71 at 0x1001f79a with 2 bytes

                        Info : Padding image section 72 at 0x1001fc36 with 2 bytes

                        Info : Padding image section 73 at 0x1001fcca with 2 bytes

                        Info : Padding image section 74 at 0x1001fd72 with 2 bytes

                        Info : Padding image section 75 at 0x10020a6e with 2 bytes

                        Info : Padding image section 76 at 0x10021072 with 2 bytes

                        Info : Padding image section 77 at 0x10021f86 with 2 bytes

                        Info : Padding image section 78 at 0x100228b6 with 2 bytes

                        Info : Padding image section 79 at 0x10022b9a with 2 bytes

                        Info : Padding image section 80 at 0x10022d1a with 2 bytes

                        Info : Padding image section 81 at 0x100232de with 2 bytes

                        Info : Padding image section 82 at 0x10023b8e with 2 bytes

                        Info : Padding image section 83 at 0x10024356 with 2 bytes

                        Info : Padding image section 84 at 0x100243ce with 2 bytes

                        Info : Padding image section 85 at 0x1002446e with 2 bytes

                        Info : Padding image section 86 at 0x100246b6 with 2 bytes

                        Info : Padding image section 87 at 0x10024dda with 2 bytes

                        Info : Padding image section 88 at 0x10024df6 with 2 bytes

                        Info : Padding image section 89 at 0x10024f4e with 2 bytes

                        Info : Padding image section 90 at 0x100252a2 with 2 bytes

                        Info : Padding image section 91 at 0x1002544a with 2 bytes

                        Info : Padding image section 92 at 0x10025eb2 with 2 bytes

                        Info : Padding image section 93 at 0x100272ae with 2 bytes

                        Info : Padding image section 94 at 0x10027b02 with 2 bytes

                        Info : Padding image section 95 at 0x10027d16 with 2 bytes

                        Info : Padding image section 96 at 0x1002833e with 2 bytes

                        Info : Padding image section 97 at 0x1002843e with 2 bytes

                        Info : Padding image section 98 at 0x100286ea with 2 bytes

                        Info : Padding image section 99 at 0x100288ee with 2 bytes

                        Info : Padding image section 100 at 0x10028db2 with 2 bytes

                        Info : Padding image section 101 at 0x10029092 with 2 bytes

                        Info : Padding image section 102 at 0x1002962a with 2 bytes

                        Info : Padding image section 103 at 0x10029766 with 2 bytes

                        Info : Padding image section 104 at 0x10029f62 with 2 bytes

                        Info : Padding image section 105 at 0x1002a046 with 2 bytes

                        Info : Padding image section 106 at 0x1002a92e with 2 bytes

                        Info : Padding image section 107 at 0x1002b582 with 2 bytes

                        Info : Padding image section 108 at 0x1002c3be with 2 bytes

                        Info : Padding image section 109 at 0x1002c776 with 2 bytes

                        Info : Padding image section 110 at 0x1002d1d6 with 2 bytes

                        Info : Padding image section 111 at 0x1002d2ea with 2 bytes

                        Info : Padding image section 112 at 0x1002df1a with 2 bytes

                        Info : Padding image section 113 at 0x1002e0a6 with 2 bytes

                        Info : Padding image section 114 at 0x1002e76a with 2 bytes

                        Info : Padding image section 115 at 0x1002f32a with 2 bytes

                        Info : Padding image section 116 at 0x1002f402 with 2 bytes

                        Info : Padding image section 117 at 0x1002f5f6 with 2 bytes

                        Info : Padding image section 118 at 0x1002f6b6 with 2 bytes

                        Info : Padding image section 119 at 0x1002f78e with 2 bytes

                        Info : Padding image section 120 at 0x1002f7f6 with 2 bytes

                        Info : Padding image section 121 at 0x1002fd7e with 2 bytes

                        Info : Padding image section 122 at 0x100301e2 with 2 bytes

                        Info : Padding image section 123 at 0x100305de with 2 bytes

                        Info : Padding image section 124 at 0x1003078a with 2 bytes

                        Info : Padding image section 125 at 0x1003083a with 2 bytes

                        Info : Padding image section 126 at 0x10031336 with 2 bytes

                        Info : Padding image section 127 at 0x100314de with 2 bytes

                        Info : Padding image section 128 at 0x10032188 with 120 bytes (bank write end alignment)

                         

                        [  4%] [#                               ] [ Erasing     ]

                        [  7%] [##                              ] [ Erasing     ]

                        [ 10%] [###                             ] [ Erasing     ]

                        [ 13%] [####                            ] [ Erasing     ]

                        [ 16%] [#####                           ] [ Erasing     ]

                        [ 19%] [######                          ] [ Erasing     ]

                        [ 22%] [#######                         ] [ Erasing     ]

                        [ 25%] [########                        ] [ Erasing     ]

                        [ 29%] [#########                       ] [ Erasing     ]

                        [ 32%] [##########                      ] [ Erasing     ]

                        [ 35%] [###########                     ] [ Erasing     ]

                        [ 38%] [############                    ] [ Erasing     ]

                        [ 41%] [#############                   ] [ Erasing     ]

                        [ 44%] [##############                  ] [ Erasing     ]

                        [ 47%] [###############                 ] [ Erasing     ]

                        [ 50%] [################                ] [ Erasing     ]

                        [ 54%] [#################               ] [ Erasing     ]

                        [ 57%] [##################              ] [ Erasing     ]

                        [ 60%] [###################             ] [ Erasing     ]

                        [ 63%] [####################            ] [ Erasing     ]

                        [ 66%] [#####################           ] [ Erasing     ]

                        [ 69%] [######################          ] [ Erasing     ]

                        [ 72%] [#######################         ] [ Erasing     ]

                        [ 75%] [########################        ] [ Erasing     ]

                        [ 79%] [#########################       ] [ Erasing     ]

                        [ 82%] [##########################      ] [ Erasing     ]

                        [ 85%] [###########################     ] [ Erasing     ]

                        [ 88%] [############################    ] [ Erasing     ]

                        [ 91%] [#############################   ] [ Erasing     ]

                        [ 94%] [##############################  ] [ Erasing     ]

                        [ 97%] [############################### ] [ Erasing     ]

                        [100%] [################################] [ Erasing     ]

                         

                        [ 15%] [####                            ] [ Programming ]

                        [ 16%] [#####                           ] [ Programming ]

                        [ 19%] [######                          ] [ Programming ]

                        [ 25%] [########                        ] [ Programming ]

                        [ 30%] [#########                       ] [ Programming ]

                        [ 37%] [###########                     ] [ Programming ]

                        [ 45%] [##############                  ] [ Programming ]

                        [ 52%] [################                ] [ Programming ]

                        [ 61%] [###################             ] [ Programming ]

                        [ 68%] [#####################           ] [ Programming ]

                        [ 76%] [########################        ] [ Programming ]

                        [ 83%] [##########################      ] [ Programming ]

                        [ 91%] [#############################   ] [ Programming ]

                        [ 98%] [############################### ] [ Programming ]

                        [100%] [################################] [ Programming ]

                        wrote 202752 bytes from file /Users/Susan/mtw/BLE_Find_Me/build/CY8CPROTO-063-BLE/Debug/mtb-example-psoc6-ble-findme.hex in 7.948228s (24.911 KiB/s)

                        ** Programming Finished **

                        ** Program operation completed successfully **

                        srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst

                        target halted due to breakpoint, current mode: Thread

                        xPSR: 0x61000000 pc: 0x0800000c msp: 0x08000870

                        Error: psoc6.cpu.cm4 -- clearing lockup after double fault

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

                        xPSR: 0x61000003 pc: 0x8008f3ee msp: 0x080477e0

                        Polling target psoc6.cpu.cm4 failed, trying to reexamine

                        Info : psoc6.cpu.cm4: hardware has 6 breakpoints, 4 watchpoints

                        shutdown command invoked

                         

                        (I thought you should see the entire output in case there is something further up that is the root cause.)

                        So it seems to erase the device, program it but fails to run. As before, performing a hard reset on the MCU itself does not work either.

                        Susan

                        • 9. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                          DheerajK_81

                          Hello Susan,

                           

                          I have the exact same openocd configurations and used the Blinky Find Me example and it is running perfectly fine. Please let me know how you have connected the Miniprog4 and the CYPROTO_063_BLE board? I have connected the 5 pins of the Miniprog4 directly to the 5 programming pins of the MCU. The 5 pins being VTARG, GND, RESET, SWDCLK, SWDIO.

                           

                          Regards,

                          Dheeraj

                          1 of 1 people found this helpful
                          • 10. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                            SuMa_296631

                            OK - I finally had some time to come back to this and it may be that I have a faulty board. I tried with another CY8CPROTO-063-BLE kit and it works.

                            The arrangement was that I had snapped off the programmer from the board, soldered a male header to the 5 holes near where the programmer used to be and then plugged the MiniProg4 onto those pins. The soldering on the header is OK (I checked very carefully) so there may be something else on the board that I have damaged in some way. The connections were all the right way around.

                            Anyway, it looks like the MiniProg4 is good and the set up for the Modus Toolbox is OK.

                            I'm puzzled as to why it works with the debugger and not with the 'release' version on the 'broken' board but at least I now have an environment that works and I can move forward. (Perhaps it is for another thread as to what the differences are between the 'debug' and 'release' arrangements.)

                            Thanks for the help and for your patients.

                            Susan

                            • 11. Re: miniprog4 cannot find cy8cproto-063-ble or my proc6 board
                              DheerajK_81

                              Glad to know it works!

                               

                              Yes sure, feel free to create a post on the community whenever you get stuck, happy to help!

                               

                              Regards,
                              Dheeraj