| поискавой системы для электроныых деталей |
|
PM0056 датащи(PDF) 144 Page - STMicroelectronics |
|
|
|||||||||||||||||||||||||||||
PM0056 датащи(HTML) 144 Page - STMicroelectronics |
|
144 / 156 page ![]() Core peripherals PM0056 144/156 DocID15491 Rev 5 Bit 10 IMPRECISERR: Imprecise data bus error When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current process is higher than the bus fault priority, the bus fault becomes pending and becomes active only when the processor returns from all higher priority processes. If a precise fault occurs before the processor enters the handler for the imprecise bus fault, the handler detects both IMPRECISERR set to 1 and one of the precise fault status bits set to 1. 0: No imprecise data bus error 1: A data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. Bit 9 PRECISERR: Precise data bus error When the processor sets this bit is 1, it writes the faulting address to the BFAR. 0: No precise data bus error 1: A data bus error has occurred, and the PC value stacked for the exception return points to the instruction that caused the fault. Bit 8 IBUSERR: Instruction bus error The processor detects the instruction bus error on prefetching an instruction, but it sets the IBUSERR flag to 1 only if it attempts to issue the faulting instruction. When the processor sets this bit is 1, it does not write a fault address to the BFAR. 0: No instruction bus error 1: Instruction bus error. Bit 7 MMARVALID: Memory Management Fault Address Register (MMAR) valid flag If a memory management fault occurs and is escalated to a hard fault because of priority, the hard fault handler must set this bit to 0. This prevents problems on return to a stacked active memory management fault handler whose MMAR value has been overwritten. 0: Value in MMAR is not a valid fault address 1: MMAR holds a valid fault address. Bits 6:5 Reserved, must be kept cleared Bit 4 MSTKERR: Memory manager fault on stacking for exception entry When this bit is 1, the SP is still adjusted but the values in the context area on the stack might be incorrect. The processor has not written a fault address to the MMAR. 0: No stacking fault 1: Stacking for an exception entry has caused one or more access violations. Bit 3 MUNSTKERR: Memory manager fault on unstacking for a return from exception This fault is chained to the handler. This means that when this bit is 1, the original return stack is still present. The processor has not adjusted the SP from the failing return, and has not performed a new save. The processor has not written a fault address to the MMAR. 0: No unstacking fault 1: Unstack for an exception return has caused one or more access violations. |
|
ссылки URL |
| Вашему бизинису помогли Аллдатащит? [ DONATE ] |
Что такое Аллдатащит | реклама | контакт | Конфиденциальность | Ссылка на техническое описание | обмен ссыками | поиск по производителю All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |