Request

• Options available when receiving return data marked as “bad”
1) Pass the bad data to the core Worst choice! Only for PQ2s.
− It will cause further damage to the system with the propagated bad data!
2) Stall further execution of the code Little bit better choice.
− This is the PQ3 products’ implementation choice!
− Side effect is that core will hang unless an asynchronous machine check handler
in place to rescue.
3) Terminate the memory transaction while prevent the load instruction
from completion. Pause further code execution. Best Choice!
− e500mc core’s implementation choice!
− This is the Synchronous Error Report Machine Check feature in e500mc core.
− Core’s memory transaction is terminated with a data error such that the core is
not hung awaiting the transaction to return good data
− Stops further propagation of bad data by taking a synchronous error report
machine check.
− Code execution is paused and wait for further information from the other
asynchronous machine check or interrupt handler to resolve this exception.
TM
34
Freescale, the Freescale logo, AltiVec, C-5, CodeTEST, CodeWarrior, ColdFire, ColdFire+, C-Ware, the Energy Efficient Solutions logo, Kinetis,
mobileGT, PowerQUICC, Processor Expert, QorIQ, Qorivva, StarCore, Symphony and VortiQa are trademarks of Freescale Semiconductor, Inc.,
Reg. U.S. Pat. & Tm. Off. Airfast, BeeKit, BeeStack, CoreNet, Flexis, MagniV, MXC, Platform in a Package, QorIQ Qonverge, QUICC Engine,
Ready Play, SafeAssure, the SafeAssure logo, SMARTMOS, TurboLink, Vybrid and Xtrinsic are trademarks of Freescale Semiconductor, Inc. All
other product or service names are the property of their respective owners. © 2012 Freescale Semiconductor, Inc.