You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For STM32L433CC device on custom board, and possibly for all STM32 devices, call to GPIO_Full_Init(); added in in mbed_overrides.c leads to all GPIOs being reset, including SWD pins. This leads to the debugger losing connection to the target, leading in turn to a SIGTRAP. Target is not affected by the loss of debugger and enters main correctly.
Target(s) affected by this defect ?
STM32L433CC on custom board, but probably all targets where SWD pins are configurable as GPIOs.
Toolchain(s) (name and version) displaying this defect ?
ARM GCC 8.1.0
GNU GDB 8.1
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.6.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.4
How is this defect reproduced ?
Create new mbed program, compile and start debug session. Connection to target should be lost with SIGTRAP.
The text was updated successfully, but these errors were encountered:
Description of defect
For STM32L433CC device on custom board, and possibly for all STM32 devices, call to
GPIO_Full_Init();
added in inmbed_overrides.c
leads to all GPIOs being reset, including SWD pins. This leads to the debugger losing connection to the target, leading in turn to a SIGTRAP. Target is not affected by the loss of debugger and entersmain
correctly.Target(s) affected by this defect ?
STM32L433CC on custom board, but probably all targets where SWD pins are configurable as GPIOs.
Toolchain(s) (name and version) displaying this defect ?
ARM GCC 8.1.0
GNU GDB 8.1
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.6.0
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.4
How is this defect reproduced ?
Create new mbed program, compile and start debug session. Connection to target should be lost with SIGTRAP.
The text was updated successfully, but these errors were encountered: