2025-09-21 11:56 AM - last edited on 2025-09-22 5:38 AM by Andrew Neil
I’m developing a Zigbee end-device app on STM32WB55 (Zigbee_OnOff_Client_SED), following ST’s Zigbee guide, but my debugger keeps showing “Target is not responding, retrying…” . I disabled low power (CFG_FULL_LOW_POWER=0 / CFG_LPM_SUPPORTED=0), set Connect under reset in CubeIDE, and updated the ST-LINK, but the issue persists and the node won’t join my network. Could this be the CPU2 wireless firmware (RFD vs FFD) or a FUS/Option Bytes problem? If anyone has a proven recovery checklist (mass erase under reset, correct CPU2 image, OB settings, etc.) or other tips to make SWD reliable and get the device to join, I’d really appreciate it.
2025-09-23 3:15 AM
Hello @Azizzr02
I believe posting this question in the ST Wireless Forum could help you get more targeted advice, especially regarding whether your issue is related to the CPU2 wireless firmware (RFD vs FFD), the FUS version, or Option Bytes configuration.
BR,
Ghofrane
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.