File tree Expand file tree Collapse file tree 2 files changed +12
-4
lines changed Expand file tree Collapse file tree 2 files changed +12
-4
lines changed Original file line number Diff line number Diff line change 1
1
# Connect to jlink gdb server
2
2
target extended-remote :2331
3
3
4
- # load the firmware into ROM
5
- load
4
+ # It seems more reliable to reset the chip before loading the new firmware. It
5
+ # is also how they do it in the example in the wiki:
6
+ # https://kb.segger.com/J-Link_GDB_Server#Console
6
7
7
8
# Reset the CPU
8
9
monitor reset
9
10
11
+ # load the firmware into ROM
12
+ load
13
+
10
14
# break Reset_Handler
11
15
# break HardFault_Handler
12
16
# break NMI_Handler
Original file line number Diff line number Diff line change 1
1
# Connect to jlink gdb server
2
2
target extended-remote :2331
3
3
4
- # load the firmware into ROM
5
- load
4
+ # It seems more reliable to reset the chip before loading the new firmware. It
5
+ # is also how they do it in the example in the wiki:
6
+ # https://kb.segger.com/J-Link_GDB_Server#Console
6
7
7
8
# Reset the CPU
8
9
monitor reset
9
10
11
+ # load the firmware into ROM
12
+ load
13
+
10
14
# Set VTOR (Vector Table Offset Register) to where the firmware is located
11
15
set *(uint32_t*)0xE000ED08 =0x10000
12
16
# Set stack pointer to initial stack pointer according to exception table.
You can’t perform that action at this time.
0 commit comments