1843988_en-US

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

1843988_en-US

1843988_en-US

S32K324 Lpuart_lin Master Continually Returning Status "LPUART_LIN_IP_STATUS_TX_BUSY"

Hi,

I am using the S32K324 in a project, and am running into issues using the Lpuart_lin driver. Executing the function "Lpuart_Lin_Ip_SendFrame" returns "LPUART_LIN_IP_STATUS_SUCCESS", however when polling the LIN instance's status after it returns "LPUART_LIN_IP_STATUS_TX_BUSY". All subsequent calls to "Lpuart_Lin_Ip_SendFrame" return a fail.

I checked the RX and TX lines going into my LIN transcoder, as well as the LIN output and I can see a 650 microsecond low pulse followed by nothing. There is no data sent apart from this break, which is seen on all 3 lines.

Any ideas as to what could be causing the issue? I have attached the file containing the Init and Send functions I have created.

Thanks!


EDIT: Wanted to add, the LIN instance has a "CurrentNodeState" of "LPUART_LIN_IP_NODE_STATE_SEND_BREAK_FIELD".

Re: S32K324 Lpuart_lin Master Continually Returning Status "LPUART_LIN_IP_STATUS_TX_BUSY"

hello @PetrS 

I have encountered the same problem now, when MCU sends as host, LPUART_LIN_IP_STATUS_TX_BUSY, and
the LIN instance has a "CurrentNodeState" of "LPUART_LIN_IP_NODE_STATE_SEND_BREAK_FIELD".

But now the api for rerouting interrupts seems to have been removed, leaving only the IntCtrl_Ip_Init function.

I can't find another solution, please tell me if there is another way to check my error.


Re: S32K324 Lpuart_lin Master Continually Returning Status "LPUART_LIN_IP_STATUS_TX_BUSY"Hi Petr,

Thanks for the response, I had already added the interrupt handler to IntCtrl_Ip. The issue turned out to be, I was initializing the interrupt and configuring the interrupt routing after initializing the LIN.

Now that I am initializing the interrupt before the LIN I am successfully sending LIN frames.

Thanks!
Re: S32K324 Lpuart_lin Master Continually Returning Status "LPUART_LIN_IP_STATUS_TX_BUSY"

Hi,

it looks like driver interrupt is not called to next frame bytes are not processed. Try to check that.
You can also refer to RTD demo examples.

BR, Petr

タグ(1)
評価なし
バージョン履歴
最終更新日:
‎11-21-2025 04:17 PM
更新者: