- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#1
ST / Re: Debugging the Lora-STM32WL...
Last post by Volker - April 03, 2025, 07:02:18 PMQuoteThis basically means you can use STM32CubeIDE to build the binary. But then you need to download it to the board via OpenOCD and you CAN NOT configure STM32CubeIDE to use OpenOCD, you have to download stand-alone OpenOCD, ignore STM32CubeIDE and use the stand-alone OpenOCD and the commands described in this document:
We are am two steps further. Seems as if ST did improve the support for debuggers from version 1.10 to 1.17:
1. We are able to launch the internal debugger with UI in STM32CubeIDE.
We made a screenshot as a proof.-) Of course we did also document the configuration. However, we do not know how to upload screenshots here.
Please see them here: https://community.st.com/t5/stm32cubeide-mcus/cannot-debug-with-cmsis-dap-openocd-cubeide-in-win10/td-p/221224
We launch openocd of the package STM32CubeIDE version 1.17 without uploading the program by the following commands in power shell:
cd C:\ST\STM32CubeIDE_1.17.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.debug.openocd_2.3.100.202501240831\resources\openocd\st_scripts
C:\ST\STM32CubeIDE_1.17.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.openocd.win32_2.4.100.202501161620\tools\bin\openocd.exe -f interface/cmsis-dap.cfg -c "cmsis-dap vid_pid 0x15ba 0x0044" -c "transport select swd" -c "adapter speed 2000" -f "target/stm32wlx.cfg"
Response is:
Open On-Chip Debugger 0.12.0+dev-00608-gd8ed48fef (2025-02-06-11:17) [https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read http://openocd.org/doc/doxygen/bugs.html
swd
adapter speed: 2000 kHz
stm32wlx_cti_prepare_restart_one
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 4000 kHz
Info : SWD DPIDR 0x6ba02477
Info : [stm32wlx.cm4] Cortex-M4 r0p1 processor detected
Info : [stm32wlx.cm4] target has 6 breakpoints, 4 watchpoints
Info : [stm32wlx.cm4] Examination succeed
Info : starting gdb server for stm32wlx.cm4 on 3333
Info : Listening on port 3333 for gdb connections
### End of response ###
Then we launch the debugger from the STM32CubeIDE.
Response in power shell:
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 4000 kHz
Info : SWD DPIDR 0x6ba02477
Info : [stm32wlx.cm4] Cortex-M4 r0p1 processor detected
Info : [stm32wlx.cm4] target has 6 breakpoints, 4 watchpoints
Info : [stm32wlx.cm4] Examination succeed
Info : starting gdb server for stm32wlx.cm4 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
undefined debug reason 8 (UNDEFINED) - target needs reset
[stm32wlx.cm4] halted due to breakpoint, current mode: Thread
xPSR: 0x01000000 pc: 0x08003094 msp: 0x20008000
Info : Padding image section 0 at 0x08000138 with 8 bytes
Info : Padding image section 1 at 0x0801f8cc with 4 bytes (bank write end alignment)
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0x20009000
Error: allocating working area failed
Warn : falling back to programming without a flash loader (slower)
Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (70932 ms). Workaround: increase "set remotetimeout" in GDB
[stm32wlx.cm4] halted due to breakpoint, current mode: Thread
xPSR: 0x01000000 pc: 0x08003094 msp: 0x20008000
### End of response ###
Remark: It might also be possible to launch openocd.exe from the STM32CubeIDE version 1.17.
2.
Open BB-STM32WLE-WAN.ioc by double clicking in STM32CubeIDE. Look for the yellow exclamation marks.
Correction: Sorry, this is wrong. According to manual dm00104712.pdf, page 86 the exclamation marks do just indicate constraints due to other settings. They do not indicate contradictory settings.
#2
ST / Re: Debugging the Lora-STM32WL...
Last post by LubOlimex - April 03, 2025, 03:54:15 PM>As reported earlier going back to version 1.10.0 of CubeSTM32 did not help
Going back to older version of CubeSTM32 is required if you wish to build the Olimex demo project without issues, HOWEVER programming and debugging will NOT work via STM32CubeIDE directly since it doesn't support CMSIS. Check these threads of complains:
https://community.st.com/t5/stm32cubeide-mcus/cmsis-dap-debugger-in-stm32cubeide/td-p/765900
https://community.st.com/t5/stm32cubeide-mcus/cannot-debug-with-cmsis-dap-openocd-cubeide-in-win10/td-p/221224
As I mention in the text document:
"Some others (like STM32CubeIDE) do not and require first building the binary and then uploading manually."
This basically means you can use STM32CubeIDE to build the binary. But then you need to download it to the board via OpenOCD and you CAN NOT configure STM32CubeIDE to use OpenOCD, you have to download stand-alone OpenOCD, ignore STM32CubeIDE and use the stand-alone OpenOCD and the commands described in this document:
https://www.olimex.com/Products/IoT/LoRa/LoRa-STM32WL-DevKit/resources/USB-programming-STM32WL.txt
Debugging without the graphical interface would be a pain.
The alternative is using software that supports CMSIS programming like Keil uVision or IAR EW for ARM.
I will do some tests and a video about the first complaint about the unreliability. Have to check myself first.
Going back to older version of CubeSTM32 is required if you wish to build the Olimex demo project without issues, HOWEVER programming and debugging will NOT work via STM32CubeIDE directly since it doesn't support CMSIS. Check these threads of complains:
https://community.st.com/t5/stm32cubeide-mcus/cmsis-dap-debugger-in-stm32cubeide/td-p/765900
https://community.st.com/t5/stm32cubeide-mcus/cannot-debug-with-cmsis-dap-openocd-cubeide-in-win10/td-p/221224
As I mention in the text document:
"Some others (like STM32CubeIDE) do not and require first building the binary and then uploading manually."
This basically means you can use STM32CubeIDE to build the binary. But then you need to download it to the board via OpenOCD and you CAN NOT configure STM32CubeIDE to use OpenOCD, you have to download stand-alone OpenOCD, ignore STM32CubeIDE and use the stand-alone OpenOCD and the commands described in this document:
https://www.olimex.com/Products/IoT/LoRa/LoRa-STM32WL-DevKit/resources/USB-programming-STM32WL.txt
Debugging without the graphical interface would be a pain.
The alternative is using software that supports CMSIS programming like Keil uVision or IAR EW for ARM.
I will do some tests and a video about the first complaint about the unreliability. Have to check myself first.
#3
New Products release / RT1010Py now have USB drag and...
Last post by olimex - April 03, 2025, 02:54:10 PMRT1010Py is running MicroPython on Cortex M7 @ 500Mhz and now tanks to Robert Hammelrath got usbtinyuf2 bootloader so you can update you MicroPython firmwares with simple drag and drop like on PICO https://olimex.wordpress.com/2025/04/03/rt1010py-the-micropython-board-running-at-500mhz-now-got-tinyuf2-bootloader-so-you-can-drag-and-drop-your-micropython-firmware-same-way-as-you-do-on-raspberry-pico/ #micropython #nxp #usb
#4
ST / Re: Debugging the Lora-STM32WL...
Last post by Volker - April 03, 2025, 01:01:21 PMQuoteif you wish to use external programmer
We wish to use a reliable programmer and source level debugger, no matter if internal or external.
In addition it makes no sense for us to operate the processor without the base board.
We have more or less successfully the devkit programmed and debugged using the internal debugger as reported on this thread, see
https://www.olimex.com/forum/index.php?topic=9750.msg45722#msg45722
However, the upload fails in 3 of 4 cases. And when it does not fail, the upload takes several minutes as the flash programmer does not work for whatever reason.
Can Olimex provide a reliable configuration for the software and internal debugger for this kit as a starting point for their customers? It doesn't help to hear that it did once work at Olimex.
(As reported earlier going back to version 1.10.0 of CubeSTM32 did not help.)
#5
AM3352 / Re: Custom Android Single Boar...
Last post by LubOlimex - April 03, 2025, 10:34:19 AMWe have designs with AM335x chips, check:
https://www.olimex.com/Products/SOM/AM335X/AM3352-SOM-EVB/open-source-hardware
https://www.olimex.com/Products/SOM/AM335X/AM3352-SOM/
The good news is you can use any hardware and software resources we have published even without a purchase.
Notice that the SOM board is not open-source hardware (only PDF export of the schematic is available). Also we don't provide Android for the boards, just Linux.
https://www.olimex.com/Products/SOM/AM335X/AM3352-SOM-EVB/open-source-hardware
https://www.olimex.com/Products/SOM/AM335X/AM3352-SOM/
The good news is you can use any hardware and software resources we have published even without a purchase.
Notice that the SOM board is not open-source hardware (only PDF export of the schematic is available). Also we don't provide Android for the boards, just Linux.
#6
AM3352 / Custom Android Single Board Co...
Last post by AnsleyRempel - April 03, 2025, 10:21:36 AMI am hoping to make a custom single board computer capable of running Android. I've made boards with microcontrollers, but I want to move up to making boards with microprocessors. I'm looking for a simple, open-source hardware board with decent software support that I can base the design around so that I don't have to modify the kernel or anything, and the BeagleBone Black looks pretty appealing. This is just a learning experience, nothing commercial.
I was hoping to find some success stories out there of custom PCBs based on the BeagleBone Black schematic like you do for microcontrollers like the ESP32, but I'm not able to find any. Is there a reason that people aren't making custom boards based on the BeagleBone Black, or am I totally missing them?
I was hoping to find some success stories out there of custom PCBs based on the BeagleBone Black schematic like you do for microcontrollers like the ESP32, but I'm not able to find any. Is there a reason that people aren't making custom boards based on the BeagleBone Black, or am I totally missing them?
#8
A10 / Re: RESET_N pin
Last post by LubOlimex - April 02, 2025, 11:12:48 AM1) It is not correct to have less than 4.5V applied to the power jack. Isn't it easier to ensure that the board never gets less than 4.5V? Maybe use Li-Po battery to keep it always alive?
2) RESET_N is not the proper pin for resetting the board, it just resets the processor but many voltages remain. The proper way to reset the board is the way the on-board RESET button is routed - to PWRON pin of the AXP209, maybe if you don't have other way - use the pads of the RESET button and lead the pin to a GPIO to toggle it (aka instead of manually pressing the RESET button toggle via GPIO).
2) RESET_N is not the proper pin for resetting the board, it just resets the processor but many voltages remain. The proper way to reset the board is the way the on-board RESET button is routed - to PWRON pin of the AXP209, maybe if you don't have other way - use the pads of the RESET button and lead the pin to a GPIO to toggle it (aka instead of manually pressing the RESET button toggle via GPIO).
#9
ST / Re: Debugging the Lora-STM32WL...
Last post by LubOlimex - April 02, 2025, 10:57:04 AMAlright, I figured it out. I was wrong before and didn't check thoroughly, sorry for this.
So it turns out that you can't program the top board (aka BB-STM32WL-ANT) via the pins of the bottom board using external programmer (STLINK/V2 in this case). This is due to the hardware design. The "C D G" pins are suitable only for programming the main chip of the bottom board STM32L052K8U3.
The SWDIO/SWDCLK pins of the top board (BB-STM32WL-ANT) are not directly routed to any header of the bottom board. They go straight to the STM32L052K8U3.
This means if you wish to use external programmer you would need to remove BB-STM32WL-ANT from the bottom board and use wires to connect to it directly, check the schematic:
https://www.olimex.com/Products/IoT/LoRa/BB-STM32WL/resources/BB-STM32WL_RevC.pdf
Use CON2 for debugging SWDIO SWCLK are pins 1 and 2 and then power from pin 7 with 3.3V and pin 8 GND.
Alternatively, use the USB programmer as explained here:
https://www.olimex.com/Products/IoT/LoRa/LoRa-STM32WL-DevKit/resources/USB-programming-STM32WL.txt
Pay attention to the STM32CubeIDE notice - it doesn't support DAP-CMSIS which means you need to build the code then upload the resulting binary via OpenOCD.
I will edit my previous posts.
I've added a notice to our hardware designers to explore ways to allow programming of top board via the bottom board using external programmer for future hardware revisions.
So it turns out that you can't program the top board (aka BB-STM32WL-ANT) via the pins of the bottom board using external programmer (STLINK/V2 in this case). This is due to the hardware design. The "C D G" pins are suitable only for programming the main chip of the bottom board STM32L052K8U3.
The SWDIO/SWDCLK pins of the top board (BB-STM32WL-ANT) are not directly routed to any header of the bottom board. They go straight to the STM32L052K8U3.
This means if you wish to use external programmer you would need to remove BB-STM32WL-ANT from the bottom board and use wires to connect to it directly, check the schematic:
https://www.olimex.com/Products/IoT/LoRa/BB-STM32WL/resources/BB-STM32WL_RevC.pdf
Use CON2 for debugging SWDIO SWCLK are pins 1 and 2 and then power from pin 7 with 3.3V and pin 8 GND.
Alternatively, use the USB programmer as explained here:
https://www.olimex.com/Products/IoT/LoRa/LoRa-STM32WL-DevKit/resources/USB-programming-STM32WL.txt
Pay attention to the STM32CubeIDE notice - it doesn't support DAP-CMSIS which means you need to build the code then upload the resulting binary via OpenOCD.
I will edit my previous posts.
I've added a notice to our hardware designers to explore ways to allow programming of top board via the bottom board using external programmer for future hardware revisions.
#10
A10 / Re: RESET_N pin
Last post by shridhar - April 02, 2025, 10:34:10 AMInput supply applied to power jack.