LPUART LIN baudrate deviation issue

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

LPUART LIN baudrate deviation issue

1,513 Views
riglesias2021
Contributor III

Hi, I am using LPUART1 as an instance for using s32k sdk LIN STACK with baud rate = 19200bps and Im having the following issue:

The LPUART module seems to have 2 different divisors for the input clock configured for this peripheral:

riglesias2021_0-1646930549879.png

The BAUD divider (sbr), which is just a modulo divide rate, and the OSR divider (osr), which is an oversampling ratio for the baud rate generated.

I´m trying to improve the accuracy of the baud rate generated for the LIN communication, so i´m trying different clock configurations, because reference manual says that FIRC and SIRC clock have different deviation accross temperature:

riglesias2021_1-1646930815301.png

Following this image, i was expecting that using FIRC clock with this peripheral, the baud rate accuracy will improve, but my results are showing the following: 

riglesias2021_2-1646930946379.png

Notes:

(CalculatedBaud = lpuartSourceClock / (osr*sbr)

CANoe error = baud rate deviation reported by CANoe in percentage of 100 (%)

The best accuracy i could achieve, is 0.5% deviation respect LIN master baud rate, using SIRC and 8Mhz for the clock, but in the other configurations with the FIRC, which is suppossed to be more precise, i could only achieve 2% of desviation. 

I reviewed the osr and sbr parameters calculated by the NXP lin stack and they seem to be OK, so at this point i dont understand why the baud rate generated is not that good as the obtained with the SIRC...

Hope the explanation is clear enough and thank you for the help

 

 

0 Kudos
Reply
5 Replies

1,484 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @riglesias2021 ,

I haven't calculated it yet, however, the equestion that you use is not correct:

danielmartynek_0-1646996551001.png

Can you double-check?

 

Thanks,

BR, Daniel

0 Kudos
Reply

1,481 Views
riglesias2021
Contributor III

Thats the same formula i used, the difference is the NXP Lin stack decrements the OSR before setting it to the LPUART registers, so the result is the same

0 Kudos
Reply

1,475 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @riglesias2021,

I just tested it with the S32K118 EVB and lpuart_echo_s32k118 (RTM 4.0.2) example.

Only changes:

  • PTC3 as TX
  • FIRC_DIV2 48MHz LPUART functional clock
  • SBR 0x64 = 100, OSR = 0x18 = 24

danielmartynek_0-1647012439670.png

 

And the TX signal looks correct:

danielmartynek_1-1647012523802.png

 

Can you please scope the following:

  • TX signal
  • LIN signal
  • FIRCDIV2 at CLKOUT

 

Thanks,

BR, Daniel

 

0 Kudos
Reply

1,459 Views
riglesias2021
Contributor III

Hello, thank you for the reply.

 

From my side it seems that the FIRC precission was corrected after enabling the "FIRC Regulator". I cant find too much information about this regulator in the s32k118 reference manual, but it seems that this feature improves the clock deviation so my issue was corrected after enabling this feature.

 

Thank you.

0 Kudos
Reply

1,456 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @riglesias2021,

Thanks for the updated.

This seems to be correct.

Answer from the design team:

"The FIRCREGOFF bit is used to control an internal regulator used by the FIRC internal circuit. In order to guarantee the operation frequency of the FIRC, the application must make sure to set this bit. Otherwise, FIRC operational frequency may get out of spec."

 

Regards,

Daniel

0 Kudos
Reply