Safety Sboot CMU FC testing - plugin HFREF and LFREF ref values are not as per the calculations

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

Safety Sboot CMU FC testing - plugin HFREF and LFREF ref values are not as per the calculations

541件の閲覧回数
Irshad2225
Contributor III


Hi, 

For CMU_FC_14, CMU_FC_15, and CMU_FC_21, the reference LFREF and HFREF values are too high to match the calculated values.
In sBoot_PtocmuFcArray, LFREF starts with zero.
I have observed that, with the minimum frequency as zero, LFREF can be 3. not zero.

Providing below reference values from the debugger.
sBoot_PtocmuFcArray values - where the calculated HFREF(sBoot_maxFreqsArray ) & LFREF(Boot_minFreqsArray) are being compared with .

image.png

Providing HFREF & LFREF calculations below.

 clock monotorFIRC_CLFFref ~%F ref MHzMonitored clockFmon ~%BusClockF mon,F bus MHz RCCR[REF_CNT]Fmon_var_MaxFmon_var_MinFref_var_MaxFref_var_MinHTCR[HFREF]LTCR[LFREF]
10CMU_FC_14_GMAC0_TX_CLKFXOSC_CLK0.00540GMAC0_TX_CLK5GMAC0_TX_CLK9.68010.089.1240.00239.9982415
11CMU_FC_15_GMAC_TS_CLKFXOSC_CLK0.00540GMAC0_TS_CLK5GMAC0_TS_CLK9.68010.089.1240.00239.9982415
16CMU_FC_21_GMAC0_RX_CLKFXOSC_CLK0.00540GMAC0_RX_CLK5GMAC0_RX_CLK258026.2523.7540.00239.9985644

Above are the HFREF and LFREF values as per my calculations.

Table. Comparison between calculated values vs sBoot_PtocmuFcArray 

Calculated valuessBoot_PtocmuFcArray values
HFREFLFREFHFREFLFREF
2415167772150
2415167772150
5644167772150


The reference values cannot be achieved even with the higher frequencies.

This might not be a calculation issue, as the same formula has been applied to the remaining CMU_FCs and those got passed.

Is this an issue in plugins/configurations???


タグ(6)
0 件の賞賛
返信
7 返答(返信)

502件の閲覧回数
Joey_z
NXP Employee
NXP Employee

Hi, Irshad2225

Thank you for contacting us.

Refer to your picture, it is unable for current CMU if the FCE=0. In addition, The REF_CNT value is 0.

BR

Joey

 

0 件の賞賛
返信

494件の閲覧回数
Irshad2225
Contributor III
Hi Joey,

Even when the REF_CNT = 100 or 80 is configured, the above-mentioned CMUs' LFREF and HFREF remain the same with REF_CNT=0, only to the CMU_FC_14, CMU_FC_15, and CMU_FC_21.



0 件の賞賛
返信

492件の閲覧回数
Irshad2225
Contributor III
I have enabled FCE too, in the code, as it was not getting enabled automatically.
Mentioned in the below thread:
https://community.nxp.com/t5/S32G/Safety-Sboot-CMU-FC-testing-Not-enabling-CMU-FC-check-before/m-p/2...
0 件の賞賛
返信

491件の閲覧回数
Irshad2225
Contributor III

Irshad2225_0-1750691808708.png

 

0 件の賞賛
返信

441件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi, Irshad2225

Thank you for your information.

I understand what you mean. Since these API in Safety are for customers to use, in order to better support you in debugging and identifying problems, could you share your code?

You can provide this information easier by creating a new case at: https://support.nxp.com.

Can attach this link: Safety Sboot CMU FC testing - plugin HFREF and LFREF ref values are not as per the calculations - NX... inter to the new ticket. 

BR

Joey

0 件の賞賛
返信

415件の閲覧回数
Irshad2225
Contributor III
Hi Joey,

Does sboot require, pheripheral initialisations before testing configurations?.

Below subchapter is mentioned from sboot_UM.pdf.
6.5.1 Function Calls during Start-up
The sBoot software does not require any initialisation function to be called during start.

Regards,
Irshad
0 件の賞賛
返信

406件の閲覧回数
Joey_z
NXP Employee
NXP Employee

hi,Irshad2225

Thank you for your information.

According to The manual, The sBoot software does not require any initialization function to be called during start_up. However, Software drivers for the PMIC and it's communication interface must be present in the system and properly initialized before sBoot can start testing the FCCU error output
pins.

Joey_z_0-1750924452355.png

Hope it can help you.

BR

Joey

 

0 件の賞賛
返信