OMAP4 SYSLINK概述.ppt

MMU Fault Handling Ducati Exceptions (Data Aborts) Ducati can crash due to other reasons than MMU faults, and these errors are handled using SYS error mechanism. Ducati sends SYS error event to device manger handler on A9 side. Event is notified to registered users in A9. Expectations from Users Register for Sys error notification On error notification, close the IPC handle(s) See the next slide for sequence flow Ducati Exceptions (Data Aborts) Ducati Hang Ducati hangs, where one process in Ducati spins in a while loop are detected using GP timer/Watchdog like mechanism. Expectations from Users Register for hang notification On event notification, close the IPC handles A9 Process Abnormal Termination Ducati component/task need to know when the A9 process terminated abnormally to release the corresponding Ducati resources. Such occurrence is communicated using PID_DEATH event to Ducati. The Ducati component registers with SysLink framework to receive this notification. See the following slide for sequence flow illustrating the case where the A9 process that exchanged buffer with Ducati is terminated. A9 Process Abnormal Termination SysLink Daemon Crash SysLink Daemon is in charge of loading the Base Image and setting up IPC Ducati is put in reset state upon SysLink Daemon crash. Expectations from Users Register for PROC_STOP event On event notification, close the IPC handles See the following slide for sequence flow SysLink Daemon Crash Ducati Crash Info - Example Error Type MMU Fault (Source core not identifiable) SysError (Source core (SysM3 or AppM3) is identified) Execution State Type of task (Task, Swi, Hwi) Task handle Address and size of stack Internal state registers snapshot Stack Stack of the offending thread Bottom up (Grow from bottom to top) 0xbebebebe marks unfilled blocks Depends on type of build profile (whole_program_debug results in optimized (shorter) stack Ducati Crash Info - Locating Error Source Note PC(R15) from Execution State Look up the