search

Infineon / mtb-example-psoc6-dual-cpu-empty-app

This is a minimal starter Dual-CPU application template for PSoC 6 MCU devices.
Other
0 stars 1 forks source link

Fail to start CM4 core on CY8CPROTO-063-BLE #2

Open jonasdaugalas opened 1 year ago

jonasdaugalas commented 1 year ago

Prerequisites

Can you reproduce the problem reliably? Yes

Did you check current release notes for known issues? Don't known where to find them

If this is not the latest release, have you checked newer releases?

Description:

With a debugger attached to the empty dual cpu application, stepping over the line proj_cm0p/main.c#62 I see that the CM4 core fails to start.

Steps to Reproduce:

  1. Launch Modus Toolbox 3.0 IDE for Windows.
  2. Connect CY8CPROTO-063-BLE via USB to my Windows laptop.
  3. Create "New Application" -> board "CY8CPROTO-063-BLE" -> "Dual-CPU Empty PSoC6 App"
  4. Click "Dual-CPU_Empty_PSoC6_App Debug MultiCore (KitProg3_MiniProg4)"
  5. When debugging starts, step over line 62 of the proj_cm0p/main.c.
  6. Observe Suspended: Signal: SIGINT:Interrupt in the CM4 debugging panel.

image

Expected Result:

No SIGINT in the CM4 startup.

Actual Result:

SIGINT in the CM4 startup.

Frequency 6/6:

Build/Commit: I don't know where to check. When I click "README on Github" in the Project Creator it points me to master branch. image

Target: CY8PROTO-063-BLE

Host OS and Version: Windows 10 Enterprise, Version 22H2, Windows Feature Experience Pack 120.2212.4190.0

Compiler:

arm-none-eabi-gcc.exe (GNU Arm Embedded Toolchain 10.3-2021.07) 10.3.1 20210621 (release)

Environment Eclipse IDE for ModusToolbox™

Version: 3.0.0 Eclipse Build ID: 2749 See the ModusToolbox™ Tools Package build number in your ModusToolbox™ installation folder, at ModusToolbox/tools_3.0/version-3.0.0.xml.

THANKS!
yugandhar436 commented 1 year ago

Hello,

Did you check the section 7.4 Multi-core debugging in ModusToolbox user guide ? I will check at my end and get back to you soon. mtb_user_guide.pdf

Thanks, P Yugandhar.

jonasdaugalas commented 1 year ago

Dear Yugandhar,

thanks for the prompt response. Indeed I had not checked the "Multi-core debugging" section in the documentation, but after taking the precautions mentioned there I still see the same problem.

Instead of stepping over the main.c , I tried simply resuming the debugging right after it enters the main function of the CM0P. I observe the same result in the CM4 execution: the SIGINT detected by the debugger.

Thanks, Jonas