Arm basics: MMU anomaly vector table remapping

/************************************************************************************************************** ****
Reference:
Description: Re-encounter these words when learning a bare-metal interrupt, this time to figure it out.

*************************************************************************************************************** ***/

This three words for a long time did not understand, today a little bit clear to write down. Physical address is the main line, others are foil. The CPU is only going along this road, what is the way to rely on the MMU, in the 0x30000000 after the address is memory.           Just say one thing: Why use the MMU to interrupt. This is because after the exception, the CPU will automatically run to 0 address, but the program is started in the memory, but the vector table is not at the real 0 address, in 0x30000000 this time will appear a flicker, cheat it 0x30000000 is 0 address, so can. The MMU is a liar, the CPU is a honest person, it will also run to 0 address, but the real content is actually the same content as the beginning of the 0x30000000 address. This is a process of remapping.
After the interruption also has an address, 8 kinds of different exception types to 8 addresses, will automatically run to the various addresses to execute, but this address is what code to rely on their own decision, can let it "Hello world", can do nothing.