Lora-STM32WL-devkit + STM32CubeIDE = Fail

Started by JeanBonnot, June 25, 2023, 11:16:20 AM

Previous topic - Next topic

JeanBonnot

Hello everybody,


Devkit is not recognized as genuine ST Device !

OpenOcd give :

openocd -f interface/cmsis-dap.cfg -c "cmsis_dap_vid_pid 0x15ba 0x0044" -c "transport select swd" -c "adapter speed 1000" -f "target/stm32wlx.cfg"
Open On-Chip Debugger 0.12.0 (2023-06-21) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
swd
adapter speed: 1000 kHz
none separate
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: FW Version = 1.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : clock speed 500 kHz
Info : SWD DPIDR 0x6ba02477
Info : [stm32wlx.cpu0] Cortex-M4 r0p1 processor detected
Info : [stm32wlx.cpu0] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for stm32wlx.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : device idcode = 0x10016497 (STM32WLE/WL5x - Rev 'unknown' : 0x1001)
Info : RDP level 0 (0xAA)
Info : flash size = 256 KiB
Info : flash mode : single-bank
Info : device idcode = 0x10016497 (STM32WLE/WL5x - Rev 'unknown' : 0x1001)
Info : RDP level 0 (0xAA)
Info : OTP size is 1024 bytes, base address is 0x1fff7000
undefined debug reason 8 (UNDEFINED) - target needs reset
Info : dropped 'gdb' connection (error -400)
Info : accepting 'gdb' connection on tcp/3333
undefined debug reason 8 (UNDEFINED) - target needs reset
Info : dropped 'gdb' connection (error -400)


So : STM32WLE/WL5x - Rev 'unknown' : 0x1001

"unknown" is strange, no ?

Then STM32CubeIDE when Run->Debug (F11) give this popup:

"Could not verify ST device! Please verify that the latest version of the GDB-server is used for the connection."


How to check if my  Lora-STM32WL-devkit is genuine or not ?

Thx

LubOlimex

QuoteThen STM32CubeIDE when Run->Debug (F11) give this popup:

"Could not verify ST device! Please verify that the latest version of the GDB-server is used for the connection."

This probably means it can't establish connection to the board at all, which I believe is expected unless they improved their support. Last time I checked I couldn't integrate LoRa-STM32WL-DevKit with STM32CubeIDE. I had to compile elf with STM32CubeIDE and then download the elf to the board via OpenOCD (when using USB). Did they add CMSIS-DAP support? Here is where my fears were confirmed in the past:

https://community.st.com/t5/stm32cubeide-mcu/cannot-debug-with-cmsis-dap-openocd-cubeide-in-win10/td-p/221224

Did you stumble upon this:

https://www.olimex.com/Products/IoT/LoRa/LoRa-STM32WL-DevKit/resources/USB-programming-STM32WL.txt

The alternative is using JTAG instead of the USB, make sure the JTAG tool is compatible with STM32CubeIDE.
Technical support and documentation manager at Olimex