Every time s32k3 runs to Mcu_DistributePllClock, the following error is reported.

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

Every time s32k3 runs to Mcu_DistributePllClock, the following error is reported.

ソリューションへジャンプ
3,307件の閲覧回数
ct5ctl
Contributor II

I just started to contact s32k series products.

Every time s32k3 runs to Mcu_DistributePllClock, the following error is reported. What is the problem?

ct5ctl_0-1675738221774.png

 

ct5ctl_0-1675738077797.png

 

 

0 件の賞賛
返信
1 解決策
3,165件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @ct5ctl,

This is all you need to change in the configuration tool and update the generated code:

  • FXOSC  to 40MHz
  • PLL to (/2 * 48)

danielmartynek_0-1676296293749.png

 

元の投稿で解決策を見る

0 件の賞賛
返信
13 返答(返信)
3,289件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @ct5ctl,

Which S32K3 part do you have?

Do you use a certain RTD example or is it your custome code?

If it is your code, please share it so that we can test it on our side.

Is the HSE_FW enabled on the chip?

 

Regards,

Daniel

0 件の賞賛
返信
3,277件の閲覧回数
ct5ctl
Contributor II

And when I use a non-mcal example, the following error will be reported when I run to Clock_Ip_Init(&Clock_Ip_aClockConfig[0]);, which is also related to pll. Is pll not set?

ct5ctl_1-1675929697628.png

ct5ctl_0-1675929560511.png

 

0 件の賞賛
返信
3,267件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @ct5ctl,

If you did not program the HSE_FW, it is not enabled, and we can exclude that.

Do you use an EVB or your own board?

Which RTD version do you use?

Can you update the letest one?

 

Thanks,

Daniel

0 件の賞賛
返信
3,250件の閲覧回数
ct5ctl
Contributor II

The development board I use is S32K344_257BGA, as shown in the figure below

ct5ctl_0-1675946911548.jpeg

The RTD version I am using now is 2.0.1, I try to download and install the latest version of RTD (in the red frame), including mcal and sdk. But my s32ds can't recognize the latest version of RTD, what's the reason?

ct5ctl_1-1675947085349.pngct5ctl_2-1675947120495.pngct5ctl_3-1675947143010.png

 

 

0 件の賞賛
返信
3,245件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Can you try updating to 2.0.2 only.

Thank you.

0 件の賞賛
返信
3,228件の閲覧回数
ct5ctl
Contributor II

Is there something wrong with my clock setting?

ct5ctl_0-1676006096125.png

 

0 件の賞賛
返信
3,210件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @ct5ctl,

Thanks for providing the EVB version and the clock configuration.

The board has 40MHz crystal according the schematic of the S32K3-T-Box.

Can you change it in the configuration tool?

 

Thank you,

BR, Daniel

0 件の賞賛
返信
3,194件の閲覧回数
ct5ctl
Contributor II

The chip package I had previously selected was 256 and now switched to the correct chip package 172.

ct5ctl_0-1676098156475.png

The current situation is: every time I debug to Mcu_DistributePllClock(), it will get stuck, as shown in the figure below

ct5ctl_1-1676098260586.png

 

 

0 件の賞賛
返信
3,197件の閲覧回数
ct5ctl
Contributor II

And The main control chip package of my EVB is s32k344MaxQFP-172, As shown below

ct5ctl_2-1676097081844.png

 

0 件の賞賛
返信
3,201件の閲覧回数
ct5ctl
Contributor II
Forgive me, can you tell me how to switch to 40MHz crystal in the configuration tool? Or give me some tutorials related to clock setting
Thank you
0 件の賞賛
返信
3,166件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @ct5ctl,

This is all you need to change in the configuration tool and update the generated code:

  • FXOSC  to 40MHz
  • PLL to (/2 * 48)

danielmartynek_0-1676296293749.png

 

0 件の賞賛
返信
3,231件の閲覧回数
ct5ctl
Contributor II

hi, I tried to update to the 2.0.2 version of the RTD (Include mcal and sdk) and use a CAN example of the RTD, but it still reports an error at Mcu_DistributePllClock()

ct5ctl_1-1676005834474.pngct5ctl_2-1676005863249.png

ct5ctl_0-1676005802091.png

 

0 件の賞賛
返信
3,279件の閲覧回数
ct5ctl
Contributor II
Hi Daniel, thank for your reply.
But I still get an error when I use the RTD example
My debuger is Multilink.
And how to enable the HSE_FW ?
0 件の賞賛
返信