AN12092 updating the censorship state takes long time

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

AN12092 updating the censorship state takes long time

Jump to solution
838 Views
viktorfellinger
NXP Employee
NXP Employee

Dear support,

 

customer is using MPC5748G and is implementing password-based protection for the debugger (JTAG) in MPC5748GRM, accordance with the guidelines outlined in application note AN12092.pdf.

The implementation has been completed and successfully tested.

During the procedure of updating the censorship state of the device,  it was noted that it necessitates approximately 8 seconds to complete, to be precise we implemented function same as find_1st_DCF_address function mentioned in AN12092.pdf it is only taking approx. 7sec.

Customer is asking on how to minimize this operational time.

 

Best Regards,

Viktor

Tags (2)
0 Kudos
Reply
1 Solution
756 Views
viktorfellinger
NXP Employee
NXP Employee

Hello Petre,

 

Meanwhile customer found the root course on his side : 

“The issue has been successfully resolved through the optimization of our legacy flash write function, resulting in a significant reduction in processing time.

We have tested and verified the results just now."

 

Best Regards,

Viktor

View solution in original post

0 Kudos
Reply
2 Replies
794 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello Viktor,

Well, since this is SW routine, the execution time is dependent on micro settings like BTB, XBAR setting, etc..

For example : Branches with successful BTB target prefetching have an effective execution time of one clock if correctly predicted.

You can also use compilator optimizations for speed.

Also measurement of that 8 seconds can influence the exact time. Do they measure it by trace or any counter in device or just pin toggle?

There could be multiple factors why the execution time of the same c code vary.

Best regards,

Peter

0 Kudos
Reply
757 Views
viktorfellinger
NXP Employee
NXP Employee

Hello Petre,

 

Meanwhile customer found the root course on his side : 

“The issue has been successfully resolved through the optimization of our legacy flash write function, resulting in a significant reduction in processing time.

We have tested and verified the results just now."

 

Best Regards,

Viktor

0 Kudos
Reply