Hello Team
May I ask one question about S32 Debug probe(with S32E)?
When I used the made project with S32 Debug probe, it is showing like below Error code :200 at the using Lunch Group for S32 Debugger.
Also Console is showing like below.
However if I used below S32 Debugger with M33, it is working well.
I think that error is occurring with R core side...but I did not have any more information about the error.
May I ask, did you know about Error code : 200?
Thank you.
Hi @Luke_Chun ,
You can see additional information about the root cause of the failure in the GDB traces console. If the GDB traces does not appear in your eclipse console, then you need to make it visible from here: Window->Preferences look for GDB and make sure you have 'Show the GDB traces...' checked:
Then you should see something like this in the IDE Console:
As you can see I was able to reproduce your scenario - you have the board set up to as M33 boot core, and so this core will be enabled after power on (the R52 cores will be disabled). In order to debug the rest of the cores, the debugger will enable those cores - all this logic is encapsulated in some python scripts that are being run when you press the debug button - in the S32Debugger launch configuration, Initialization script.
And so we have multiple python scripts for different scenarios: single core debug, multicore, attach from first instruction.
In multicore use case, if the s32z2e2_generic_bareboard.py is used on the initial core , only that core will be enabled. Even if the same script is being set on the secondary cores, the enabling part of the secondary cores will be skipped.
The recommendation in multicore scenarios is to use on the initial core, M33 on you use case this python script: s32z2e2_generic_bareboard_all_cores.py .Just press Browse next to the script name got to s32z2e2 folder and choose this script. So your Debug Configuration on the M33 core, that is the initial core (the first core that will be launched in the debug session) should have this setting:
Please give it a try. Hope this helps!
Best regards,
Alexandra
Hi @Luke_Chun ,
You can see additional information about the root cause of the failure in the GDB traces console. If the GDB traces does not appear in your eclipse console, then you need to make it visible from here: Window->Preferences look for GDB and make sure you have 'Show the GDB traces...' checked:
Then you should see something like this in the IDE Console:
As you can see I was able to reproduce your scenario - you have the board set up to as M33 boot core, and so this core will be enabled after power on (the R52 cores will be disabled). In order to debug the rest of the cores, the debugger will enable those cores - all this logic is encapsulated in some python scripts that are being run when you press the debug button - in the S32Debugger launch configuration, Initialization script.
And so we have multiple python scripts for different scenarios: single core debug, multicore, attach from first instruction.
In multicore use case, if the s32z2e2_generic_bareboard.py is used on the initial core , only that core will be enabled. Even if the same script is being set on the secondary cores, the enabling part of the secondary cores will be skipped.
The recommendation in multicore scenarios is to use on the initial core, M33 on you use case this python script: s32z2e2_generic_bareboard_all_cores.py .Just press Browse next to the script name got to s32z2e2 folder and choose this script. So your Debug Configuration on the M33 core, that is the initial core (the first core that will be launched in the debug session) should have this setting:
Please give it a try. Hope this helps!
Best regards,
Alexandra
