S32G PC12 pin output level problem

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

S32G PC12 pin output level problem

3,650 Views
jack_huang1
Contributor IV

Dear,

        Product platform: S32G274, NON-AUTOSAR based development of the program has been tested on the same board is no problem. I used 3.0.2 RTD before, but now I use 4.0.1 RTD based on AUTOSAR. Because this problem occurred after 100ms of power-on, while LLCE initialization took place after 200ms, I think it has nothing to do with LLCE. It may be caused by port, which uses MCAL. So it shouldn't have anything to do with AUTOSAR.

       I suspect that the Port driver mistakenly operated the level in the CANTX pin during initialization. I measured the TX pin of CAN:

PC_12/LLCE_CAN0_TX Pin: As shown in the following figure, the green pin is PC_12/LLCE_CAN0_TX. When powered on for about 120ms, it should be during Port initialization. PC12 is pulled down for 110ms and then pulled up.

No pull-down resistors are added to the hardware, which is a directly connected can transceiver. See Attachment 1 for the hardware schematic diagram.

There is no operation for PC_12/LLCE_CAN0_TX except initialization. In addition, this pin configuration is the input, the software can not modify the output level.

In addition, we have done comparative tests, and PC_12 is configured as ordinary input IO, there is no problem.

So I suspect there is a drop down inside the S32G or some other internal chip logic or Port module internal logic.

The following is the comparison test done. In the two tests, only the mode configuration of PC_12 pin is different, and other codes and hardware environments are identical. The software also blocks the initialization of LLCECAN, FLEXCAN, and all code.

PC_12 is configured as the LLCE_CAN0_TX power-on waveform, as shown in Figure 2

PC_12 is configured as a common IO power-on waveform, as shown in Figure 3

         Thank You!

         Best Regards!

0 Kudos
Reply
3 Replies

3,642 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

We do apologize, we are not understanding the overall issue you are seeing. Can you help summarizing what is the issue you are seeing?

 i.e. in the following sentence:

"There is no operation for PC_12/LLCE_CAN0_TX except initialization. In addition, this pin configuration is the input, the software can not modify the output level."

You are talking about a TX pin, which is an output (as seen on the image below), but you are referring to it as input, which we are confused by the statement. Again, we do apologize.

DanielAguirre_0-1690400006228.png

Also, are you using any NXP platform/board? Are you using any LLCE example? In which LLCE version are you seeing this behavior?

Please, let us know.

0 Kudos
Reply

3,588 Views
jack_huang1
Contributor IV

Dear  Daniel-Aguirre:        

        When the PC12 pin is set to LLCE_CAN0_TX, the output of the pin is low, resulting in a Busoff problem. Configure the pin in IO mode and the output level is high. And compared with PJ_01 pin, after the pin is configured as LLCE_CAN1_TX, the output waveform is high and CAN communication is normal. Now we need to confirm what might cause the output of the pin to be pulled down after the pin of PC12 is configured as LLCE_CAN0_TX.          

        At present, I have done the test of progress 1, which is as follows:        

        Mask all tasks, only initialize, and postpone the Port_Init() to call after 1 second, use the oscilloscope to catch the waveform, you can confirm that PC_12/LLCE_CAN0_TX is pulled down after calling Port_Init(), and there is no other operation on the software.

       Port_Init() is called after 1 second, PC_12/LLCE_CAN0_TX wave line, as shown in Figure 1.

       Port_Init() is called after 1 second, PJ_01/LLCE_CAN1_TX waveform, as shown in Figure 2.  

 

      See Attachment 3 for the configuration files and generated code for Port.       

       Thank You!        

        Best Regards!

0 Kudos
Reply

3,577 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

Thanks for your feedback.

Are you using any NXP platform/board? Are you using any LLCE example? In which LLCE version are you seeing this behavior?

We don't seem to obtain this behavior from our side under the provided LLCE examples.

Regarding the Port configuration, there is a "PortPin Level Value" option, you should be able to set the initial value of the pin, which value are you defining?

DanielAguirre_0-1690495953764.png

If you would like for us to review any configuration, help us opening a ticket under the NXP online services, since it is not common for us to provide reviews under the community, we do apologize.

Please, let us know.

0 Kudos
Reply