Hi, trying to switch from ST-Link to J-Link without much success.
A- STM32L476RCTx based custom board
B- OpenSTM32 / AC6 GCC based toolchain
C- Nucleo-64 L476RG based ST-Link v2.1 debugger
D- Using 'STM32 ST-LINK Utility.exe', did a 'Erase Chip'.
0x1FFF7800 = FFEFF8AA 00100755 FFFFFFFF 00000000
0x1FFF7810 = 7FFF0000 8000FFFF FF00FFFF 00FF0000
0x1FFF7820 = FF00FFFF 00FF0000 FFFFFFFF FFFFFFFF
Works, slow but works (limited to 4 breakpoints though, if you want to have success with 'step out'/'run to')
-> log_stlink.txt
E- Added GNU MCU Eclipse plugin from gnu-mcu-eclipse.github.io/plugins/install/
F- Made a connector custom bridge gnu-mcu-eclipse.github.io/developer/j-link-stm32-boards/
G- Connected the J-Link, configured a 'GDB SEGGER J-Link Debugging' based configuration (default)
This doesn't work like expected, flash is not performed successfully, PC get stuck somewhere in a rather random place.
H- To be sure it is not a bridge problem, I removed J-Link and switched to ST-Link firmware from segger.com/products/debug-prob…j-links/st-link-on-board/
I- Executed 'JLinkSTM32.exe' (11) then 'JLink.exe' to get option bytes ('mem32 0x1FFF7800,C')
1FFF7800 = FFEFF8AA 00100755 FFFFFFFF 00000000
1FFF7810 = 7FFF0000 8000FFFF FF00FFFF 00FF0000
1FFF7820 = FF00FFFF 00FF0000 FFFFFFFF FFFFFFFF
Got the same problem.
-> log_jlink_flash.txt
Any idea ?
A- STM32L476RCTx based custom board
B- OpenSTM32 / AC6 GCC based toolchain
C- Nucleo-64 L476RG based ST-Link v2.1 debugger
D- Using 'STM32 ST-LINK Utility.exe', did a 'Erase Chip'.
0x1FFF7800 = FFEFF8AA 00100755 FFFFFFFF 00000000
0x1FFF7810 = 7FFF0000 8000FFFF FF00FFFF 00FF0000
0x1FFF7820 = FF00FFFF 00FF0000 FFFFFFFF FFFFFFFF
Works, slow but works (limited to 4 breakpoints though, if you want to have success with 'step out'/'run to')
-> log_stlink.txt
E- Added GNU MCU Eclipse plugin from gnu-mcu-eclipse.github.io/plugins/install/
F- Made a connector custom bridge gnu-mcu-eclipse.github.io/developer/j-link-stm32-boards/
G- Connected the J-Link, configured a 'GDB SEGGER J-Link Debugging' based configuration (default)
This doesn't work like expected, flash is not performed successfully, PC get stuck somewhere in a rather random place.
H- To be sure it is not a bridge problem, I removed J-Link and switched to ST-Link firmware from segger.com/products/debug-prob…j-links/st-link-on-board/
I- Executed 'JLinkSTM32.exe' (11) then 'JLink.exe' to get option bytes ('mem32 0x1FFF7800,C')
1FFF7800 = FFEFF8AA 00100755 FFFFFFFF 00000000
1FFF7810 = 7FFF0000 8000FFFF FF00FFFF 00FF0000
1FFF7820 = FF00FFFF 00FF0000 FFFFFFFF FFFFFFFF
Got the same problem.
-> log_jlink_flash.txt
Any idea ?