Search Results

Search results 1-2 of 2.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Can't connect Jlink to STM32WL55RG after upgrade to FUS v1.2

    igor.c - - J-Link/Flasher related

    Post

    I received excelled support from Segger via other channel. Results: - My observation was misleading. Issue is not FUS but in application firmware I had flashed on device (ST' example Projects/P-NUCLEO-WB55.Nucleo/Applications/BLE/BLE_HeartRate/Binary/BLE_HeartRate_reference.hex) - This example disables SWD debugger support in runtime. - Enable CFG_DEBUGGER_SUPPORTED=1 in app_conf.h h to keep debugger working. - STM32CubeIDE overrides this (partially) by connection under reset. Following sequence…

  • [SOLVED] Can't connect Jlink to STM32WL55RG after upgrade to FUS v1.2

    igor.c - - J-Link/Flasher related

    Post

    Hello all, I'm working on NUCLEO-WL55RG, that I upgraded to FUS v1.2 and stack (from ST SDK stm32cubewb_v1-14-0) using STM32CubeProgrammer. After upgrade it is possible to connect target in boot-loader mode (boot0 = 1) as described in (wiki.segger.com/ST_STM32WB). But it is not possible to connect target using JLink Probe (JLinkExe or Ozone) in normal/application mode (boot0 = 0). This means JLink probe can't be used for application debugging. When STM32CubeIDE is used then application on target…