Example MPC5744P 1b+2b_RAM_ECC_error_injection GHS714

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

Example MPC5744P 1b+2b_RAM_ECC_error_injection GHS714

Example MPC5744P 1b+2b_RAM_ECC_error_injection GHS714

********************************************************************************
* Detailed Description:
* Purpose of the example is to show how to generate Multi-bit or Single-bit ECC
* error in internal RAM (user must choose it in the option at the end of main
* function).
* ECC fault is generated with using of core register E2EECSR. If error injection
* is enabled (E2EECSR0[INVC]=1) and certain mask is set (E2EECSR0[CHKINVT]),
* subsequent write to SRAM creates error in SRAM array.
* When corrupted data is read the IVOR1 exception handler is called in case of
* multi-bit ECC error (IVOR1 exception occurs) and FCCU_Alarm_Interrupt handler
* is called in case of single-bit ECC error (FCCU interrupt occurs).
* Both function calls MEMU handler.
* The example displays notices in the terminal window (connector J19 on
* MPC57xx_Motherboard)(19200-8-no parity-1 stop bit-no flow control on eSCI_A).
* No other external connection is required.
* ------------------------------------------------------------------------------
* Test HW:         MPC57xx_Motherboard + MPC5744P-144DC
* MCU:             PPC5744PFMLQ8,0N15P,QQAA1515N, Rev2.1B
* Fsys:            200 MHz PLL with 40 MHz crystal reference
* Debugger:        Lauterbach Trace32
* Target:          internal_FLASH, RAM
* Terminal:        19200-8-no parity-1 stop bit-no flow control
* EVB connection:  default
********************************************************************************

Attachments
%3CLINGO-SUB%20id%3D%22lingo-sub-1117504%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EExample%20MPC5744P%201b%2B2b_RAM_ECC_error_injection%20GHS714%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1117504%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E********************************************************************************%3CBR%20%2F%3E*%20Detailed%20Description%3A%3CBR%20%2F%3E*%20Purpose%20of%20the%20example%20is%20to%20show%20how%20to%20generate%20Multi-bit%20or%20Single-bit%20ECC%3CBR%20%2F%3E*%20error%20in%20internal%20RAM%20(user%20must%20choose%20it%20in%20the%20option%20at%20the%20end%20of%20main%3CBR%20%2F%3E*%20function).%3CBR%20%2F%3E*%20ECC%20fault%20is%20generated%20with%20using%20of%20core%20register%20E2EECSR.%20If%20error%20injection%3CBR%20%2F%3E*%20is%20enabled%20(E2EECSR0%5BINVC%5D%3D1)%20and%20certain%20mask%20is%20set%20(E2EECSR0%5BCHKINVT%5D)%2C%3CBR%20%2F%3E*%20subsequent%20write%20to%20SRAM%20creates%20error%20in%20SRAM%20array.%3CBR%20%2F%3E*%20When%20corrupted%20data%20is%20read%20the%20IVOR1%20exception%20handler%20is%20called%20in%20case%20of%3CBR%20%2F%3E*%20multi-bit%20ECC%20error%20(IVOR1%20exception%20occurs)%20and%20FCCU_Alarm_Interrupt%20handler%3CBR%20%2F%3E*%20is%20called%20in%20case%20of%20single-bit%20ECC%20error%20(FCCU%20interrupt%20occurs).%3CBR%20%2F%3E*%20Both%20function%20calls%20MEMU%20handler.%20%3CBR%20%2F%3E*%20The%20example%20displays%20notices%20in%20the%20terminal%20window%20(connector%20J19%20on%3CBR%20%2F%3E*%20MPC57xx_Motherboard)(19200-8-no%20parity-1%20stop%20bit-no%20flow%20control%20on%20eSCI_A).%20%3CBR%20%2F%3E*%20No%20other%20external%20connection%20is%20required.%3CBR%20%2F%3E*%20------------------------------------------------------------------------------%3CBR%20%2F%3E*%20Test%20HW%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20MPC57xx_Motherboard%20%2B%20MPC5744P-144DC%3CBR%20%2F%3E*%20MCU%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20PPC5744PFMLQ8%2C0N15P%2CQQAA1515N%2C%20Rev2.1B%3CBR%20%2F%3E*%20Fsys%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20200%20MHz%20PLL%20with%2040%20MHz%20crystal%20reference%3CBR%20%2F%3E*%20Debugger%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Lauterbach%20Trace32%3CBR%20%2F%3E*%20Target%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20internal_FLASH%2C%20RAM%3CBR%20%2F%3E*%20Terminal%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2019200-8-no%20parity-1%20stop%20bit-no%20flow%20control%3CBR%20%2F%3E*%20EVB%20connection%3A%26nbsp%3B%20default%3CBR%20%2F%3E********************************************************************************%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1117504%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E********************************************************************************%3CBR%20%2F%3E*%20Detailed%20Description%3A%3CBR%20%2F%3E*%20Purpose%20of%20the%20example%20is%20to%20show%20how%20to%20generate%20Multi-bit%20or%20Single-bit%20ECC%3CBR%20%2F%3E*%20error%20in%20internal%20RAM%20(user%20must%20choose%20it%20in%20the%20option%20at%20the%20end%20of%20main%3CBR%20%2F%3E*%20function).%3CBR%20%2F%3E*%20ECC%20fault%20is%20generated%20with%20using%20of%20core%20register%20E2EECSR.%20If%20error%20injection%3CBR%20%2F%3E*%20is%20enabled%20(E2EECSR0%5BINVC%5D%3D1)%20and%20certain%20mask%20is%20set%20(E2EECSR0%5BCHKINVT%5D)%2C%3CBR%20%2F%3E*%20subsequent%20write%20to%20SRAM%20creates%20error%20in%20SRAM%20array.%3CBR%20%2F%3E*%20When%20corrupted%20data%20is%20read%20the%20IVOR1%20exception%20handler%20is%20called%20in%20case%20of%3CBR%20%2F%3E*%20multi-bit%20ECC%20error%20(IVOR1%20exception%20occurs)%20and%20FCCU_Alarm_Interrupt%20handler%3CBR%20%2F%3E*%20is%20called%20in%20case%20of%20single-bit%20ECC%20error%20(FCCU%20interrupt%20occurs).%3CBR%20%2F%3E*%20Both%20function%20calls%20MEMU%20handler.%20%3CBR%20%2F%3E*%20The%20example%20displays%20notices%20in%20the%20terminal%20window%20(connector%20J19%20on%3CBR%20%2F%3E*%20MPC57xx_Motherboard)(19200-8-no%20parity-1%20stop%20bit-no%20flow%20control%20on%20eSCI_A).%20%3CBR%20%2F%3E*%20No%20other%20external%20connection%20is%20required.%3CBR%20%2F%3E*%20------------------------------------------------------------------------------%3CBR%20%2F%3E*%20Test%20HW%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20MPC57xx_Motherboard%20%2B%20MPC5744P-144DC%3CBR%20%2F%3E*%20MCU%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20PPC5744PFMLQ8%2C0N15P%2CQQAA1515N%2C%20Rev2.1B%3CBR%20%2F%3E*%20Fsys%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20200%20MHz%20PLL%20with%2040%20MHz%20crystal%20reference%3CBR%20%2F%3E*%20Debugger%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Lauterbach%20Trace32%3CBR%20%2F%3E*%20Target%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20internal_FLASH%2C%20RAM%3CBR%20%2F%3E*%20Terminal%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2019200-8-no%20parity-1%20stop%20bit-no%20flow%20control%3CBR%20%2F%3E*%20EVB%20connection%3A%26nbsp%3B%20default%3CBR%20%2F%3E********************************************************************************%3C%2FP%3E%3C%2FLINGO-TEASER%3E
No ratings
Version history
Last update:
‎02-20-2021 06:36 AM
Updated by: