S32G LLCE LAN slave node can't send responses?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32G LLCE LAN slave node can't send responses?

Jump to solution
1,355 Views
Alex_mjl
Contributor II

Hi NXP,

    I am using the S32G274ARDB2 development board. Run the "Lin_Llce_DS_S32G274A_M7" project in the S32DS software on the board.  When the project was running at this point, there was no waiting for CH3 responses:

企业微信截图_17053216952465.png

 On the hardware, I connected LLCE CH2 and LLCE CH3 together as a loopback.

    Is there any problem with me doing this?

Tags (1)
0 Kudos
Reply
1 Solution
1,254 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Can you help us confirm that under your example you have the following settings?

For LLCE v1.0.5

DanielAguirre_0-1705681043124.png

With this, we have the following outcome from our side:

DanielAguirre_1-1705681077646.png

Please, let us know.

View solution in original post

0 Kudos
Reply
7 Replies
1,343 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Which LLCE version are you using? Also, what are you referring to as "there was no waiting for CH3 responses"? We see that the code you are referring to is waiting for CH2 which is waiting for the response of CH3, as told under the code.

As for the connection, the following is told under the LLCE documentation, we find the following:

DanielAguirre_0-1705341745701.png

For which, we expect a connection between CH2 and CH3, hence we don't see a problem.

Are you seeing any problems with the current example?

Please, let us know.

0 Kudos
Reply
1,333 Views
Alex_mjl
Contributor II

Hi,

The version used is 'S32G_LLCE_1_0_5'.  I just ran "Master Node sends a header with RESPONSE_RX. The master will read the response published by the slave node" this part of the code in CASE2. As a result, I see that CH2 sends the frame header. But CH3 does not responses. And the code keeps running in this loop. 'LinStatus' return 'LIN_RX_NO_RESPONSE'.

Alex_mjl_0-1705370449178.png

 

0 Kudos
Reply
1,318 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Looking into the "Lin_Llce_DS_S32G274A_M7" example under LLCE v1.0.5, we cannot find the #if preprocessor instructions shown under your capture:

DanielAguirre_0-1705431702852.png

Below will be the non-modified example:

DanielAguirre_1-1705432247235.png

 

For which we assume you have modified the example, which modifications have you done? Does the example behave the same without modifications?

Are you using any debugger?

Please, let us know.

0 Kudos
Reply
1,301 Views
Alex_mjl
Contributor II

Hi,

Even if I don't make any changes to the example project, the phenomenon is the same. As I said above, my changes are just to make debugging LIN easier.

Can you use the 'S32G274A-RDB2' development board to reproduce my problem?

I want to confirm whether this TJA1124 can only be the master and cannot send respond packets. Or is there something wrong with my understanding?

Alex_mjl_0-1705545028030.png

 

0 Kudos
Reply
1,283 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for your feedback. We seem to be able to reproduce the behavior you are seeing under the specific LLCE version, but it we use LLCE-FW v1.0.4 we don't see it. Under LLCE v1.0.4 we see the following:

DanielAguirre_0-1705613883957.png

Where it is working as expected. 

Let us verify what modifications are implemented under LLCE v1.0.5 that makes the example not behave as the previous version. We do apologize for the inconvenience and for any delay from our side.

Please, let us know.

0 Kudos
Reply
1,255 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Can you help us confirm that under your example you have the following settings?

For LLCE v1.0.5

DanielAguirre_0-1705681043124.png

With this, we have the following outcome from our side:

DanielAguirre_1-1705681077646.png

Please, let us know.

0 Kudos
Reply
1,202 Views
Alex_mjl
Contributor II

Hi Daniel,

Thanks for your support. I changed the interrupt priority based on your advice, and it now works fine on V1.0.5.

Alex_mjl_0-1705889023603.png

 

0 Kudos
Reply