how to start with clock_ip_ReferencePoints

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

how to start with clock_ip_ReferencePoints

Jump to solution
336 Views
jimmy623
Contributor I

In S32k358, how can I use  already defined clk ?

Thanks!

 

jimmy623_0-1718285913351.png

 

0 Kudos
Reply
1 Solution
211 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @jimmy623,

I see, it is a bug in RTD 3.0.0, it has been fixed in RTD 4.0.0

 

Regards,

Daniel

View solution in original post

0 Kudos
Reply
9 Replies
318 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @jimmy623,

The references can be used by other RTD drivers.

Such as BaseNXP Osif Config, see below.

There is no list of drivers dependent on the clock reference points.

danielmartynek_0-1718354112906.png

 

Regards,

Daniel

 

0 Kudos
Reply
286 Views
jimmy623
Contributor I

How can i use to LPUART driver ?

default Baud rate is 40M ,which mismatch to Reference design.

Thanks!

jimmy623_0-1718674157426.png

jimmy623_1-1718674289966.png

 

0 Kudos
Reply
269 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @jimmy623,

The LPUART modules are clocked either by AIPS_PLAT_CLK or AIPS_SLOW_CLK depending on the number of the instance, this cannot be changed. Refer to the RM.

danielmartynek_0-1718692142774.png

 

Regards,

Daniel

0 Kudos
Reply
267 Views
jimmy623
Contributor I

This is a Bug?

 

jimmy623_1-1718693326375.png

 

jimmy623_0-1718693247334.png

 

0 Kudos
Reply
265 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Which RTD version is it?

 

Thank you.

0 Kudos
Reply
263 Views
jimmy623
Contributor I
RTD AUTOSAR 4.7
0 Kudos
Reply
261 Views
danielmartynek
NXP TechSupport
NXP TechSupport

That is the Autosar version, I mean RTD version.

For example, in this version, it is correct:

danielmartynek_0-1718705944216.png

danielmartynek_1-1718705969722.png

 

Regards,

Daniel

 

 

0 Kudos
Reply
215 Views
jimmy623
Contributor I

I will check RTD 4.0 later

 

jimmy623_0-1718767373703.pngjimmy623_1-1718767416221.png

jimmy623_2-1718767633620.png

 

 

0 Kudos
Reply
212 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @jimmy623,

I see, it is a bug in RTD 3.0.0, it has been fixed in RTD 4.0.0

 

Regards,

Daniel

0 Kudos
Reply