Timeline for Cortex M7 goes to HardFault immediately after reset
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 17, 2018 at 1:40 | vote | accept | user4574 | ||
| S Dec 3, 2018 at 23:10 | history | suggested | selectstriker2 |
revise arm tag
|
|
| Dec 3, 2018 at 21:04 | review | Suggested edits | |||
| S Dec 3, 2018 at 23:10 | |||||
| Dec 3, 2018 at 20:40 | answer | added | old_timer | timeline score: 2 | |
| Dec 3, 2018 at 2:57 | answer | added | user4574 | timeline score: 2 | |
| Dec 2, 2018 at 18:47 | comment | added | user4574 | @Elliot Alderson The default boot location is selectable via some bits you can set in flash. It can be set to boot from an internal ROM, or from the start of flash. | |
| Dec 2, 2018 at 18:38 | comment | added | user4574 | @Elliot Alderson I believe the processor is reading my vector table at reset. The reason for my belief is that following reset the PC is actually being set to the value contained in the table. The stack pointer is also being set correctly. | |
| Dec 2, 2018 at 13:03 | comment | added | Elliot Alderson | Why don't you take a look at the assembly code generated by your C compiler. One issue I see is that the default location for the reset vector is 0x00000004, not 0x00400000. Is your processor relocating the interrupt vectors? | |
| Dec 2, 2018 at 5:59 | history | asked | user4574 | CC BY-SA 4.0 |