Hello,
I have installed the latest ModusToolbox and am trying to develop on the PSoC 62S2 Wi-Fi BT Pioneer Kit.
Unfortunately, I receive the following error when trying to program or debug the board using Modus Toolbox IDE:
* The detected device does not match the configuration file in use.
* Flash programming will not work. Please use the "psoc6_2m.cfg"
* configuration file, or attach a kit that matches the configuration file.
I have checked and psoc6_2m.cfg is in use. The real issue seems to be that only the Cortex-M0 core is detected during programming. See below the complete debug log: psoc6.cpu.cm0 is found, but cm4 is not. Bizarre.
Additionally, there is another worrying line because I am using Apple M1 based MacBook Pro and not x86 Intel MacBook.
Launching GDB: /Applications/ModusToolbox/tools_2.4/gcc/bin/arm-none-eabi-gdb
This GDB was configured as \"--host=x86_64-apple-darwin10 --target=arm-none-eabi\
Complete log from the debug terminal below:
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.30.1155
Info : KitProg3: Pipelined transfers enabled
Info : VTarget = 3.288 V
Info : kitprog3: acquiring the device (mode: reset)...
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x6ba02477
Info : psoc6.cpu.cm0: hardware has 4 breakpoints, 2 watchpoints
***************************************
** Silicon: 0xE453, Family: 0x102, Rev.: 0x12 (A1)
** Detected Device: CY8C624ABZI-S2D44
** Detected Main Flash size, kb: 2048
** Flash Boot version: 3.1.0.378
** Chip Protection: UNKNOWN
Started by GNU MCU Eclipse
*******************************************************************************
***************************************
terminate command invoked
* The detected device does not match the configuration file in use.
* Flash programming will not work. Please use the "psoc6_2m.cfg"
* configuration file, or attach a kit that matches the configuration file.
*******************************************************************************
Info : psoc6.dap: powering down debug domain...
Looking for ideas how to fix this bizarre issue and program/debug the board.
Thanks,
Dimi
