S32G LLCE gateway

[Balavanth_1993]

Hello Community,

I am working on Core M7,currently testing with Sample LLCE examples, getting following errors.

Error in final launch sequence:

Failed to execute MI command:
load "C:\\Users\\LAB\\workspaceS32DS.3.4\\Can_Llce_DS_S32G274A_M7\\Debug_RAM\\Can_Llce_DS_S32G274A_M7.elf"
Error message from debugger back end:
Load failed
Failed to execute MI command:
load "C:\\Users\\LAB\\workspaceS32DS.3.4\\Can_Llce_DS_S32G274A_M7\\Debug_RAM\\Can_Llce_DS_S32G274A_M7.elf"
Error message from debugger back end:
Load failed
Load failed

[bpe]

This problem description is missing several important details:

1. The original name of the demo you are trying to load. LLCE Gateway software
package of the recent release does not include a demo of the name
"Can_Llce_DS_S32G274A_M7"

2. The type of the board used, home design or a reference/development system,
if it is an NXP development board, the exact board model.

3. If any other demo created in S32DS from an example worked.

4. The model of the hardware probe used to control the target board.

Best Regards,
Platon

[Balavanth_1993]

Hello Platon,

The router integration example implements the following scenario

1. LLCE (CAN) IPC(M7)-IPC(A53)-GMAC​
2. Board debugger name: S32 debug probe.
3. Currently I am using S32G-VNP-RDB2 ,S32G Vehicle Network Processing, Reference Design board 2.
4. This board belongs to NXP for reference/development purpose we are using
5. Here I am working for core M7 side.
6. Using S32 design studio for S32 platform 3.4
7. for this  currently testing CAN2CAN,and CANloopback example from Sample LLCE folder

Please guide if my going path is wrong.

Best Regards,

Balavanth

[bpe]

Thank you for providing details, however, your recent update does not
allow to unambiguously identify the software example you are trying to run. In
particular, the two software demos you mentioned, Router integration example and
CAN2CAN LLCE demo, belong to different software packages, each of them has it's own
list of dependencies and requires different build and startup procedures. They
cannot be combined together in any way.

For the reason explained above, the only, actually
very generic recommendation I can give based on the information you shared, is
to test your debug connection by clicking the "Test connection" button in the
debug settings window as shown below:

You can get to it by clicking the Debug Settings shortcut on the Dashboard:

Hope this helps,
Platon