SPNZ195z PBIST#4 Errata workaround vs HALCoGen 3.08.01 errata_PBIST_4()

Charles Johnston

Other Parts Discussed in Thread: HALCOGEN

Hello,

This question has been lost in other threads, so I'll post it as a new thread.

Is the workaround for PBIST#4 listed in the TMS570LS31x/21x errata (SPNZ195C, Feb 2013) sufficient, or is the extra code in the HALCoGen function errata_PBIST_4() necessary? The errata says "Ignore the first PBIST result after power up and re-run the PBIST Test. The second execution of the PBIST test will provide correct results". I interpret this as "run pbist twice at powerup."

Thanks, Charlie Johnston

over 11 years ago

0 Jean-Marc Mifsud over 11 years ago

TI__Mastermind 22375 points

Charles,

I've forwarded your question to our Halcogen and Safety experts.
I will check that this question is answered.

0 Prathap over 11 years ago

TI__Genius 14205 points

Hi Charlie,

There might be a corner case ( very very rare though) that even second time PBIST execution might not help. HALCoGen workaround is recommended since it's more reliable.

I will check with Errata document owner, whether there will be any update to the document.

0 Pashan None over 11 years ago in reply to Prathap

Genius 5660 points

Hello Prathap,

For the CORNER CASE you mentioned, does VIM INTREQ_85 flag will be SET at the end of PBIST Run even though PBIST ROM Read didn't occur correctly?

Usuall for PBIST Run End, there is a VIM Channel 85 Interrupt. Does VIM Interrupt 85 occur when errata PBIST#4 occurs?

Please help me understand it better.
Thank you.
Regards
Pashan

0 Charles Johnston over 11 years ago in reply to Prathap

Expert 2690 points

Hi Prathap,

Any update from the errata owner?

Thanks, Charlie

0 Dave Livingston over 11 years ago in reply to Charles Johnston

TI__Expert 4695 points

Charles,

SPNZ199 has the latest update to PBIST#4, which says it is enough to loop on the PBIST algorithm checking the execution time was as expected. That is enough to catch PBIST#4, the workaround implemented in HALCogen has our lessons learned and best practices.

Thank you,

Forum Support

0 Charles Johnston over 11 years ago in reply to Dave Livingston

Expert 2690 points

Hi Dave,

My question is about the TMS570LS31x/21x errata (SPNZ195C, Feb 2013) which has a different workaround.

Thanks, Charlie

0 Dave Livingston over 11 years ago in reply to Charles Johnston

TI__Expert 4695 points

Charlie,

Yes, we are in the process of publishing updated errata and SPNZ195C PBIST#4 will be updated to match SPNZ199b (revised January 2014). Please use the latest workaround for the errata.

Thank you,

Forum Support

Arm-based microcontrollers

Arm-based microcontrollers forum

SPNZ195z PBIST#4 Errata workaround vs HALCoGen 3.08.01 errata_PBIST_4()