CCSTUDIO-THEIA: Debugging Cortex M4

Olivier Compondu

Prodigy 10 points

Part Number: CCSTUDIO-THEIA
Other Parts Discussed in Thread: TMDSCNCD28388D

I am currently evaluating the TMDSCNCD28388D using the onboard XDS100V2 and CCS 20.4.0.13.

I am using the standard examples:

led_ex1_c28x_cm_blinky_cpu1
led_ex1_c28x_cm_blinky_cm

Status: Both projects load and run correctly in standalone mode (both LEDs blink).

The Issue: Debugging CPU1 works perfectly. However, when I debug the CM core, I lose control over the GPIOs. Even though the connection to the CM is established, I cannot toggle the pins. It appears that CPU1 retains or takes back the GPIO master ownership during the CM debug session.

6 days ago

0 Peter Luong1 6 days ago

TI__Mastermind 19281 points

Hi Olivier,

What GPIOs are you experiencing this with? I've taken a look at the example code and there is only an explicit write for LED2

GPIO_setMasterCore(DEVICE_GPIO_PIN_LED2, GPIO_CORE_CM);

This means the CM core will only be able to retain access to LED2 GPIO, all other GPIOs are still owned by CPU1

Regards,

Peter

0 Olivier Compondu 5 days ago in reply to Peter Luong1

Prodigy 10 points

Hi Peter,

I realize that. But I expect the CM to retain access to the LED2 IOs during debugging. Apparently, that is not happening.

Best regards, Olivier

0 Peter Luong1 2 days ago in reply to Olivier Compondu

TI__Mastermind 19281 points

Hi Olivier,

Even during debugging, the ownership of peripherals is maintained. If you need to be able to access the peripherals during debugging, you can change the ownership in the CPU1 debugging and then manipulate the peripheral from the CM debug session

Regards,

Peter

C2000™︎ microcontrollers

C2000 microcontrollers forum

CCSTUDIO-THEIA: Debugging Cortex M4