原文：http://blog.feabhas.com/2013/02 ... cortex-m3cortex-m4/

This posting assumes you that you have a working ARM Cortex-M3 base project in Keil uVision. If not, please see the “howto” video: Creating ARM Cortex-M3 CMSIS Base Project in uVision

Divide by zero error

Given the following C function

1. int div(int lho, int rho)
   
2. {
   
3.     return lho/rho;
   
4. }

复制代码

called from main with these arguments

1. int main(void)
   
2. {
   
3.    int a = 10;
   
4.    int b = 0;
   
5.    int c;
   
6.    c = div(a, b);
   
7.    // other code
   
8. }

复制代码

You would expect a hardware “divide-by-zero” (div0) error. Possibly surprisingly, by default the Cortex-M3 will not report the error but return zero.

Configuration and Control Register (CCR)

To enable hardware reporting of div0 errors we need to configure the CCR. The CCR is part of the Cortex-M’s System Control Block (SCB) and controls entry trapping of divide by zero and unaligned accesses among other things. The CCR bit assignment for div0 is:

[4]

DIV_0_TRP

Enables faulting or halting when the processor executes an SDIVor UDIV instruction with a divisor of 0:0 = do not trap divide by 01 = trap divide by 0. When this bit is set to 0, a divide by zero returns a quotient of 0.

So to enable DIV_0_TRP, we can use CMSIS definitions for the SCB and CCR, as in:

1. SCB->CCR |= 0x10;

复制代码

If we now build and run the project you will need to stop execution as it will appear to run forever. When execution is stopped you’ll find debugger stopped in the file startup_ARMCM3.s in the CMSIS default Hard Fault exception handler:

Override The Default Hard Fault_Handler

As all the exceptions handlers are build with “Weak” linkagein CMSIS, it is very easy to create your own Hard Fault handler. Simply define a function with the name “HardFault_Handler”, as in:

1. void HardFault_Handler(void)
   
2. {
   
3.    while(1);
   
4. }

复制代码

If we now build, run and then stop the project, we’ll find the debugger will be looping in our new handler rather than the CMSIS default one (alternatively we could put a breakpoint at the while(1) line in the debugger).

Rather than having to enter breakpoints via your IDE, I like to force the processor to enter debug state automatically if a certain instruction is reached (a sort of debug based assert). Inserting the BKPT (breakpoint) ARM instruction in our code will cause the processor to enter debug state. The immediate following the opcode normally doesn’t matter (but always check) except it shouldn’t be 0xAB (which is used for semihosting).

1. #include "ARMCM3.h"
   
2. void HardFault_Handler(void)
   
3. {
   
4.   __ASM volatile("BKPT #01");
   
5.   while(1);
   
6. }

复制代码

If we now build and run, the program execution should break automatically at the BKPT instruction.

Error Message Output

The next step in developing the fault handler is the ability to report the fault. One option is, of course, to use stdio (stderr) and semihosting. However, as the support for semihosting can vary from compiler to compiler, I prefer to use Instrumented Trace Macrocell (ITM) utilizing the CMSIS wrapper function ITM_SendChar, e.g.

1. void printErrorMsg(const char * errMsg)
   
2. {
   
3.    while(*errMsg != ''){
   
4.       ITM_SendChar(*errMsg);
   
5.       ++errMsg;
   
6.    }
   
7. }

复制代码

Fault Reporting

Now that we have a framework for the Hard Fault handler, we can start reporting on the actual fault details. Within the Cortex-M3’s System Control Block (SCB) is theHardFault Status Register (SCB->HFSR). Luckily again for use, CMSIS has defined symbols allowing us to access these register:

1. void HardFault_Handler(void)
   
2. {
   
3.    static char msg[80];
   
4.    printErrorMsg("In Hard Fault Handler\n");
   
5.    sprintf(msg, "SCB->HFSR = 0x%08x\n", SCB->HFSR);
   
6.    printErrorMsg(msg);
   
7.    __ASM volatile("BKPT #01");
   
8.    while(1);
   
9. }

复制代码

Building and running the application should now result in the following output:

By examining the HFSR bit configuration, we can see that the FORCED bit is set.

When this bit is set to 1, the HardFault handler must read the other fault status registers to find the cause of the fault.

Configurable Fault Status Register (SCB->CFSR)

A forced hard fault may be caused by a bus fault, a memory fault, or as in our case, a usage fault. For brevity, here I am only going to focus on the Usage Fault and cover the Bus and Memory faults in a later posting (as these have additional registers to access for details).

So given what we know to date, our basic Fault Handler:

• checks if the FORCED bit is set ( if ((SCB->HFSR & (1 << 30)) != 0) )
• prints out the contents of the CFSR
  

1. void HardFault_Handler(void)
   
2. {
   
3.    static char msg[80];
   
4.    printErrorMsg("In Hard Fault Handler\n");
   
5.    sprintf(msg, "SCB->HFSR = 0x%08x\n", SCB->HFSR);
   
6.    printErrorMsg(msg);
   
7.    if ((SCB->HFSR & (1 << 30)) != 0) {
   
8.        printErrorMsg("Forced Hard Fault\n");
   
9.        sprintf(msg, "SCB->CFSR = 0x%08x\n", SCB->CFSR );
   
10.        printErrorMsg(msg);
    
11.    }
    
12.    __ASM volatile("BKPT #01");
    
13.    while(1);
    
14. }

复制代码

Running the application should now result in the following output:

The output indicated that bit 25 of the UsageFault Status Register (UFSR)part of the CFSR is set.

UsageFault Status Register

The bit configuration of the UFSR is shown below, and unsurprisingly the outpur shows that bit 9 (DIVBYZERO) is set.

We can now extend the HardFault handler to mask the top half of the CFSR, and if not zero then further report on those flags, as in:

1. void HardFault_Handler(void)
   
2. {
   
3.    static char msg[80];
   
4.    printErrorMsg("In Hard Fault Handler\n");
   
5.    sprintf(msg, "SCB->HFSR = 0x%08x\n", SCB->HFSR);
   
6.    printErrorMsg(msg);
   
7.    if ((SCB->HFSR & (1 << 30)) != 0) {
   
8.        printErrorMsg("Forced Hard Fault\n");
   
9.        sprintf(msg, "SCB->CFSR = 0x%08x\n", SCB->CFSR );
   
10.        printErrorMsg(msg);
    
11.        if((SCB->CFSR & 0xFFFF0000) != 0) {
    
12.          printUsageErrorMsg(SCB->CFSR);
    
13.       }
    
14.    }
    
15.    __ASM volatile("BKPT #01");
    
16.    while(1);
    
17. }
    
18. void printUsageErrorMsg(uint32_t CFSRValue)
    
19. {
    
20.    printErrorMsg("Usage fault: ");
    
21.    CFSRValue >>= 16;                  // right shift to lsb
    
22.    if((CFSRValue & (1 << 9)) != 0) {
    
23.       printErrorMsg("Divide by zero\n");
    
24.    }
    
25. }

复制代码

A run should now result in the following output:

Register dump

One final thing we can do as part of any fault handler is to dump out known register contents as they were at the time of the exception. One really useful feature of the Cortex-M architecture is that a core set of registers are automatically stacked (by the hardware) as part of the exception handling mechanism. The set of stacked registers is shown below:

Using this knowledge in conjunction with AAPCS we can get access to these register values. First we modify our original HardFault handler by:

• modifying it’s name to “Hard_Fault_Handler”
  

• adding a parameter declared as an array of 32–bit unsigned integers.
• 
  

void Hard_Fault_Handler(uint32_t stack[])

Based on AAPCS rules, we know that the parameter label (stack) will map onto register r0. We now implement the actual HardFault_Handler. This function simply copies the current Main Stack Pointer (MSP) into r0 and then branches to our Hard_Fault_Handler (this is based on ARM/Keil syntax):

1. __asm void HardFault_Handler(void) {  MRS r0, MSP  B __cpp(Hard_Fault_Handler) }

复制代码

Finally we implement a function to dump the stack values based on their relative offset, e.g.

1. enum { r0, r1, r2, r3, r12, lr, pc, psr};
   
2. 
   
3. void stackDump(uint32_t stack[])
   
4. {
   
5.    static char msg[80];
   
6.    sprintf(msg, "r0  = 0x%08x\n", stack[r0]);  printErrorMsg(msg);
   
7.    sprintf(msg, "r1  = 0x%08x\n", stack[r1]);  printErrorMsg(msg);
   
8.    sprintf(msg, "r2  = 0x%08x\n", stack[r2]);  printErrorMsg(msg);
   
9.    sprintf(msg, "r3  = 0x%08x\n", stack[r3]);  printErrorMsg(msg);
   
10.    sprintf(msg, "r12 = 0x%08x\n", stack[r12]); printErrorMsg(msg);
    
11.    sprintf(msg, "lr  = 0x%08x\n", stack[lr]);  printErrorMsg(msg);
    
12.    sprintf(msg, "pc  = 0x%08x\n", stack[pc]);  printErrorMsg(msg);
    
13.    sprintf(msg, "psr = 0x%08x\n", stack[psr]); printErrorMsg(msg);
    
14. }

复制代码

This function can then be called from the Fault handler, passing through the stack argument. Running the program should result is the following output:

Examining the output, we can see that the program counter (pc) is reported as being the value 0x00000272, giving us the opcode generating the fault. If we disassemble the image using the command:

fromelf -c CM3_Fault_Handler.axf —output listing.txt

By trawling through the listing (listing.txt) we can see the SDIV instruction at offending line (note also r2 contains 10 and r1 the offending 0).

1. .text
   
2. div
   
3. 0x00000270: 4602          MOV r2,r0
   
4. 0x00000272: fb92f0f1      SDIV r0,r2,r1
   
5. 0x00000276: 4770          BX lr
   
6. .text

复制代码

Finally, if you’re going to use the privilege/non–privilege model, you’ll need to modify the HardFault_Handler to detect whether the exception happened in Thread mode or Handler mode. This can be achieved by checking bit 3 of the HardFault_Handler’s Link Register (lr) value. Bit 3 determines whether on return from the exception, the Main Stack Pointer (MSP) or Process Stack Pointer (PSP) is used.

1. __asm void HardFault_Handler(void)
   
2. {
   
3.   TST lr, #4     // Test for MSP or PSP
   
4.   ITE EQ
   
5.   MRSEQ r0, MSP
   
6.   MRSNE r0, PSP
   
7.   B __cpp(Hard_Fault_Handler)
   
8. }

复制代码

In a later post I shall develop specific handler for all three faults.

Notes:

• The initial model for fault handling can be found in Joseph Yiu’s excellent book “The Definitive Guide to the ARM Cortex-M3”
• The code shown was built using the ARM/Keil MDK-ARM Version 4.60 development environment (a 32Kb size limited evaluation is available from the Keil website)
• The code, deliberately, has not been refactored to remove the hard-coded (magic) values.
• Code available on GitHub at git://github.com/feabhas/CM3_Fault_Handler.git