S32K_multicore_trace32_normal_multilink_hardware_fault

Zhougw — Fri, 20 Oct 2023 01:42:11 GMT

I use core0 and core2 of S32K3, use core0 to start core2.

with trace32, after load elf of core0 and core2, core2 show buss error, after core0 run mcu_setmode, core2 become normal(no bus error)., run core2 mannually, LED and CAN is OK.

no debugger after downloaded elf, LED and CAN is OK.

with multilink+s32ds, after load elf of core0 and core2, core0 is in main function, core2 triggerred hardware fault. debug cann't go on.

with multilink+s32ds, empty project core0 and core2 start at the same time, no bus error.

I guess it is because when core0 is in the entry of main function, core2 haven't started, when debugger connect core2, hardware fault triggerred.

if I want to use core0 to start core2, and i want to use multilink+s32ds to debug, how can I solve this problem. the same elf works fine with trace32 or with no debugger, so the problem is in multilink+s32ds.

Re: S32K_multicore_trace32_normal_multilink_hardware_fault

juan_see — Mon, 23 Oct 2023 14:56:48 GMT

Hi @Zhougw ,

Could you please create a support request ticket on the PEmicro website? Please click on the "Support Requests" link

https://www.pemicro.com/support/index.cfm

That way, the issue can be investigated by PEmicro engineers.

topic Re: S32K_multicore_trace32_normal_multilink_hardware_fault in S32 Design Studio

S32K_multicore_trace32_normal_multilink_hardware_fault

Re: S32K_multicore_trace32_normal_multilink_hardware_fault