TMS320F28388D: Debugger changes boot-order of CPU1 and CPU2

Flurin Bühler

Part Number: TMS320F28388D

Tool/software:

When I start my F28388 project without debugger, I keep CPU2 and CM in reset until CPU1 starts CPU2 and CM using Device_bootCPU2() and Device_bootCM().
This allows me to assign IOs, peripherals and memory to each CPU before CPU2 and CM start.

When I use the debugger, the chip behaves differently. When I hit the play button the CPU2 and/or CM start independently and run no matter if CPU1 allows this or not.
This way they try to access memory or peripherals that are not yet available.

Is there a way to configure the debug-configuration such that CPU2 and CM stop and wait until CPU1 starts when the debugger is connected?

Thanks,

Flurin

8 months ago

+1 Benjamin Collier 8 months ago

TI__Mastermind 32206 points

Hi Flurin,

Flurin Bühler said:
When I use the debugger, the chip behaves differently. When I hit the play button the CPU2 and/or CM start independently and run no matter if CPU1 allows this or not.
This way they try to access memory or peripherals that are not yet available.

Honestly I think the easiest way to configure this would be to use the IPC_sync() function to stop CPU2 and CM until CPU1 acknowledges the flags used in IPC_sync().

Best Regards,

Ben Collier

0 Flurin Bühler 8 months ago in reply to Benjamin Collier

Prodigy 60 points

Thanks! That is certainly an option. But still the CPU would boot in a slightly different way if the debugger is used.Would modifying the .gel file also work? E.g. remove the calls to GEL_Run() on CPU2 and CM?

0 Benjamin Collier 8 months ago in reply to Flurin Bühler

TI__Mastermind 32206 points

Flurin Bühler said:
E.g. remove the calls to GEL_Run() on CPU2 and CM?

I think this would work. You just need to stop CPU2 and CM from running to main.

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F28388D: Debugger changes boot-order of CPU1 and CPU2