Power on Reset of S32K146-Q144EVBVEVB

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

Power on Reset of S32K146-Q144EVBVEVB

ソリューションへジャンプ
746件の閲覧回数
Nibesh
Contributor III

Hello @danielmartynek 
I am running code to blink an LED. I want to verify the Bootup Delay on it.
Actually, how much time it will take to jump to Application, when we normally Reset the MCU.

Actually I am achieving 4.22ms, for your kind reference I have attached Logic Analyzer image.
I hope you will correlate my doubts.

One more Doubts @danielmartynek  

Will you clarify my one Doubts, on S32K1xx Data Sheet in Page no. 43  Flash Timing Specification for (Program Section execution time) (1KB flash)  is 5ms.
So when the Micro-controller is Powered, does it is taking 5ms to jump into the Application Program?
For you kind reference I took snap from the datasheet. I hope you will check Flash Timing Specifications Image for it.

I hope to hear from you Soon

BR 
Nibesh

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

You can use J15, it powers the MCU regardless of the USB/12V, 5V/3V3 configuration.

danielmartynek_0-1717053360153.png

 

Regards,

Daniel

元の投稿で解決策を見る

8 返答(返信)
627件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @Nibesh,

The boot process is explained in the RM, Section 25.3.3 Boot sequence.

It takes 325us from the point VDD reaches 2.7 V to execution of the first instruction across the operating temperature range of the chip.

danielmartynek_0-1716800982026.png

Then, it is given by the execution time of the custom SW that jumps to the application from the bootloader.

 

Program Section execution time (1KB flash) is time that the FTFC takes to program 1KB of flash, it has nothing to do with the boot process.

 

Regards,

Daniel

0 件の賞賛
返信
616件の閲覧回数
Nibesh
Contributor III

Hello @danielmartynek 

I am achieving 4.2 milli seconds after POR.
Where is the Problem on my side.
If you have any code that I have to run, you can please recommend me?

0 件の賞賛
返信
601件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @Nibesh,

From the start of the execution of the reset routine to the LED driving, the MCU is being initialized.

This includes the startup code and your main.c configuration.

For example, the Clock driver will wait for SOSC clock to be validated, for PLL to be locked etc.

And these all adds up to the 4.2ms you see.

 

Regards,

Daniel

 

 

599件の閲覧回数
Nibesh
Contributor III

Hi @danielmartynek 

Thank you very much Daniel for your response.
Daniel is there any ways or calculations that we can prove theoretical?

If you can help me to prove theoretical that will be more helpful for me.

I hope to hear from you soon!

Thank you

0 件の賞賛
返信
597件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

If you use the RTD drivers, you can refer to the RTD Quality Package, which can be downloaded from the  webpage where you can find the RTD drivers. The package includes the average execution time for each function. But in the end, you need to validate the startup time in your application.

 

Regards,

Daniel

0 件の賞賛
返信
568件の閲覧回数
Nibesh
Contributor III

Hello @danielmartynek 

J104
2-3 (Default)

Reset signal direct to the MCU, use
to reset S32K146.


J107

2-3 (Default)
S32K146 powered by USB micro
connector.


J10
2-3 (Default)
VDD voltage is connected to 5 V

My Connection is like this @danielmartynek 

Which pin should I take for VDD if my VDD is 5V?
I have attached Pic for your reference

0 件の賞賛
返信
532件の閲覧回数
danielmartynek
NXP TechSupport
NXP TechSupport

You can use J15, it powers the MCU regardless of the USB/12V, 5V/3V3 configuration.

danielmartynek_0-1717053360153.png

 

Regards,

Daniel

595件の閲覧回数
Nibesh
Contributor III

Thank you @danielmartynek 
I will check and update you soon regarding it.


BR 
Nibesh


0 件の賞賛
返信