I have a same issue as Debug the CM4 core
Programming successfull debug fails:
psoc creator error dbg.0006
I am using P6 BLE pioneer kit
I have PSoC Creator 4.4, The latest PDL 3.1.3 and psoc Prorammer version is 3.29.0.
I've tried the workaround as well with the infinite loop. The device stoped, but "nowhere". I mean: Not in the infinite loop. I saw the disassemly window, and line -1
then i pressed step into in debug window, I got another error:
psoc creator error dbg.0007
the run request failed encountered error (cannot find bounds of current function)
The request to run the application on the target failed. Make sure that your code is valid and that the selected target supports debugging.
Could somebody help with any good advise please?
Many thanks in advance!
I am using PSoC6 BLE pioneer kit. Cy8ckit-062-ble. I've tried the sample projects as well. I tried sample /example project which use unly CM0 its fine. When any FW uses CM4 the debug halts in the beginning. I tried also to use an example with only CM4 and put some code to the CM4. And i tried to debug there, and this code also halted with the same error.
I'm afraid I cannot share here the project as it is an Arrow ESC project and confidential (as far as I know here anybody can see it)
Could you please advise a channel where i could share it?
Many thanks in advance
May be I'm missing some points, but I wonder with which core are you starting the debugger?
When I start a debugger for PSoC 6 in PSoC Creator, the first dialog shows two choice
Note: Somehow I can not upload image right now, so I will try with text
[-] KitProg3 (CMSIS-DAP/BULK/xxx)
PSoC 63 CY8C6347BZI-BLD53 (CM0p)
PSoC 63 CY8C6347BZI-BLD53 (CM4)
If I select (CM0p) I can debug main_cm0p.c but I can not debug main_cm4.c.
And if I select (CM4) I can debug main_cm4.c but main_cm0p is already running even before I select resume button in the debugger.
P.S. With my sample program below, you can try switching between cm0p and cm4 without debugger.
Although, I think this could be a rare case, in case you cm4 core is dead, you will not receive "CM4:>" prompt
when you type "cm4" at the initial prompt of "CM0P:>"