<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Activity for stm32flash</title><link>https://sourceforge.net/p/stm32flash/activity/</link><description>Recent activity for stm32flash</description><language>en</language><lastBuildDate>Sat, 11 Apr 2026 12:21:53 -0000</lastBuildDate><item><title>Tormod Volden posted a comment on ticket #181</title><link>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#dca5</link><description>Can you please build with address sanitizer and try to reproduce? Are you able to reproduce also when not flashing, just connecting and reading the device info?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 Apr 2026 12:21:53 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#dca5</guid></item><item><title>Ronald Monthero posted a comment on ticket #181</title><link>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#2155/7a87</link><description>Hi Tormod, It turns out that there is a possible race condition or corruption which is overwriting one of the dev structures while traversing the device list. This causes the search loop of device ID list, to terminate early when checking the value of stm-&gt;dev-&gt;id, making the code think the MCU device ID is not found. It's a bit tricky to track this down, as issue occurs randomly. I narrowed it down after several attempts to capture debug details - with a watchpoint enabled for it. as shown below,...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ronald Monthero</dc:creator><pubDate>Tue, 31 Mar 2026 07:56:33 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#2155/7a87</guid></item><item><title>Tormod Volden modified ticket #181</title><link>https://sourceforge.net/p/stm32flash/tickets/181/</link><description>Fix invalid device ID check </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 27 Mar 2026 08:36:32 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/181/</guid></item><item><title>Tormod Volden posted a comment on ticket #181</title><link>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#2155</link><description>Hi, thanks for the bug report and the suggested patch. However I don't understand the attached patch. Apparently it is not the same patch as was used in your testing. What is wrong in the original code that makes it an "invalid check"?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 27 Mar 2026 08:36:06 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#2155</guid></item><item><title>Ronald Monthero posted a comment on ticket #181</title><link>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#0e34</link><description>Details of issue: Error: Unknown/unsupported device (Device ID: 0x483) MCU - stm32h735 stm32flash - v 0.7 == Issue encountered when flashing firmware from linux som =&gt; stm32h735x mcu Proposed solution below with patch attached and tested for my stm32H735 MCU with stm32flash v 0.7 root@ucm-imx93:~# stm32flash -w zephyr.bin -v /dev/ttyLP6 -b 115200 stm32flash 0.7 http://stm32flash.sourceforge.net/ Using Parser : Raw BINARY Size : 498708 Interface serial_posix: 115200 8E1 Unknown/unsupported device...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ronald Monthero</dc:creator><pubDate>Fri, 27 Mar 2026 06:33:52 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/181/?limit=25#0e34</guid></item><item><title>Ronald Monthero created ticket #181</title><link>https://sourceforge.net/p/stm32flash/tickets/181/</link><description>Fix invalid device ID check </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ronald Monthero</dc:creator><pubDate>Fri, 27 Mar 2026 06:14:13 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/181/</guid></item><item><title>Tormod Volden updated merge request #26</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/26/</link><description>Add support for STM32WBA5xxx and STM32WBA6xxx</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 06 Mar 2026 17:10:58 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/26/</guid></item><item><title>Tormod Volden posted a comment on merge request #26</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/26/?limit=25#8f8f</link><description>Thanks Antonio and Francesco!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 06 Mar 2026 17:10:45 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/26/?limit=25#8f8f</guid></item><item><title>Antonio Borneo created merge request #26 on Code</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/26/</link><description>Add support for STM32WBA5xxx and STM32WBA6xxx</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Antonio Borneo</dc:creator><pubDate>Fri, 06 Mar 2026 14:56:35 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/26/</guid></item><item><title>Alex Lennon created ticket #180</title><link>https://sourceforge.net/p/stm32flash/tickets/180/</link><description>Issue resetting a blank then programmed part into run mode</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Lennon</dc:creator><pubDate>Fri, 09 Jan 2026 10:36:14 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/180/</guid></item><item><title>Andrew Yong created ticket #179</title><link>https://sourceforge.net/p/stm32flash/tickets/179/</link><description>v0.8 Release?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Yong</dc:creator><pubDate>Wed, 03 Dec 2025 15:02:11 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/179/</guid></item><item><title>Mikhail posted a comment on ticket #178</title><link>https://sourceforge.net/p/stm32flash/tickets/178/?limit=25#0350</link><description>Error in gd32vw553.conf: "flash 0x08000000 0x083FFFFF" May be deleted / commented debug output in 'parsers/devconfig.c' line 38 "printf("read '%s'\n", filename);"</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mikhail</dc:creator><pubDate>Fri, 14 Nov 2025 18:10:14 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/178/?limit=25#0350</guid></item><item><title>Mikhail created ticket #178</title><link>https://sourceforge.net/p/stm32flash/tickets/178/</link><description>Add reading of MCU parameters from the config file</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mikhail</dc:creator><pubDate>Wed, 12 Nov 2025 06:22:09 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/178/</guid></item><item><title>Mikhail created ticket #177</title><link>https://sourceforge.net/p/stm32flash/tickets/177/</link><description>Add reading of MCU parameters from the config file</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mikhail</dc:creator><pubDate>Mon, 10 Nov 2025 12:33:59 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/177/</guid></item><item><title>Mikhail posted a comment on ticket #175</title><link>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#aadd</link><description>The disassembler says that address 0x0bf90000 jumps to 0x0bf99231—into the OTP. So, the OTP is also included in system memory</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mikhail</dc:creator><pubDate>Fri, 07 Nov 2025 13:32:20 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#aadd</guid></item><item><title>Mikhail posted a comment on ticket #175</title><link>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#82ac</link><description>Sorry, I posted the patch first and only saw the lastest version. "Some values differ from yours.": ram_start: I don't see much of a difference, your value is a little better ram_end: memory is divided into blocks (refman, 2.3.3, Embedded SRAMs). There may be spaces between them. It's probably safer to use only SRAM1. So for 535/545/575/585 -&gt; 0x2000 0000 + 192k = 0x2003 0000. For 59x/5Ax/5Fx/5Gx -&gt; 0x2000 0000 + 768k = 0x200C 0000. Anyway, as far as I understand, these addresses are only used for...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mikhail</dc:creator><pubDate>Fri, 07 Nov 2025 11:13:53 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#82ac</guid></item><item><title>Anonymous posted a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#6b9f</link><description>Is it possible to get a binary for windows?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 07 Nov 2025 09:26:43 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#6b9f</guid></item><item><title>Tormod Volden posted a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#3c03</link><description>Sure. (Sorry, I didn't see the Anonymous post before now.) Binary for 64-bit Windows, not tested.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 07 Nov 2025 09:25:48 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#3c03</guid></item><item><title>Tormod Volden created ticket #176</title><link>https://sourceforge.net/p/stm32flash/tickets/176/</link><description>linting etc fixes merge request</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 07 Nov 2025 09:19:58 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/176/</guid></item><item><title>Tormod Volden posted a comment on ticket #175</title><link>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#a52f</link><description>If you look at the latest git version you can see that I already put in placeholders for these chips, with some values filled in. It even has a complete and active (but not verified) entry for the 585xx chips. Some values differ from yours. So we should try to find out which values are best.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 07 Nov 2025 08:59:40 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#a52f</guid></item><item><title>Tormod Volden posted a comment on ticket #175</title><link>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#7f94</link><description>Thank so much! Can you please also tell where you have the information from (datasheet revision, other document references) so that it can be double-checked? The option bytes and sectors can be tricky for some systems but it helps to know what your assumptions are based on.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 07 Nov 2025 08:49:47 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/175/?limit=25#7f94</guid></item><item><title>Mikhail created ticket #175</title><link>https://sourceforge.net/p/stm32flash/tickets/175/</link><description>Add STM32u5 record into dev_tree</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mikhail</dc:creator><pubDate>Fri, 07 Nov 2025 08:37:00 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/175/</guid></item><item><title>Maren Konrad created ticket #174</title><link>https://sourceforge.net/p/stm32flash/tickets/174/</link><description>Flashing of Intel hex with skipped (0xFF) memory block failed. No write after block happens</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Maren Konrad</dc:creator><pubDate>Thu, 28 Aug 2025 15:00:32 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/174/</guid></item><item><title>Tormod Volden modified ticket #164</title><link>https://sourceforge.net/p/stm32flash/tickets/164/</link><description>Regression: required delay before entering boot loader mode</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 17:04:44 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/164/</guid></item><item><title>Tormod Volden modified a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#d42d</link><description>I would test it with the following line, if someone provide a binary to me: /* {0x489, "STM32U073xx/83xx" , 0x20002170, 0x2000A000, 0x08000000, 0x08040000, 1, p_2k, 0x1FFF7800, 0x1FFF7860, 0x1FFF0000, 0x1FFF6800, 0}, */ Here the reference documents AN2606 rev 66 SRAM Table 209 STM32U073xx/83xx System-mem-addr Table 192 26 Kbytes, starting from address 1FFF0000, STM32U0 – FLASH Memory Flash presentation Flash-Address: Main Memory Page 7 PSize: Page 7 Option Byte: Page Option Bytes are used to early...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 16:31:16 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#d42d</guid></item><item><title>Tormod Volden modified a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</link><description>Thanks! Here is binary with your patch.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 11:52:30 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</guid></item><item><title>Tormod Volden modified a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</link><description>Thanks! Here is binary with your patch. (The attachment ended up in the original post.)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 11:51:38 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</guid></item><item><title>Tormod Volden modified a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</link><description>Thanks! Here is binary with your patch. (The attachment ended up in the original post.)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 11:50:48 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</guid></item><item><title>Tormod Volden modified ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/</link><description>STM32U0 Support - Unknown/unsupported device (Device ID: 0x489)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 11:48:31 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/</guid></item><item><title>Tormod Volden posted a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</link><description>Thanks! Here is binary with you patch.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 11:48:31 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#8140</guid></item><item><title>Anonymous posted a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#d42d</link><description>I would test it with the following line, if someone provide a binary to me: /* {0x489, "STM32U073xx/83xx" , 0x20002170, 0x2000A000, 0x08000000, 0x08040000, 1, p_2k, 0x1FFF7800, 0x1FFF7860, 0x1FFF0000, 0x1FFF6800, 0}, */ Here the reference documents https://www.st.com/content/ccc/resource/technical/document/application_note/b9/9b/16/3a/12/1e/40/0c/CD00167594.pdf/files/CD00167594.pdf/jcr:content/translations/en.CD00167594.pdf SRAM Table 209 STM32U073xx/83xx System-mem-addr Table 192 26 Kbytes, starting...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 25 May 2025 11:29:27 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#d42d</guid></item><item><title>Tormod Volden posted a comment on ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#69c7</link><description>It is possible that it just needs the right parameters in dev_table.c and it will work. I have added placeholders for this device (and all other devices in latest AN2606) in dev_table.c, in hope that people will contribute the missing pieces, after looking up the individual data sheets and testing on their devices.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 09:19:57 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/?limit=25#69c7</guid></item><item><title>Tormod Volden committed [2e0cbb] on Code</title><link>https://sourceforge.net/p/stm32flash/code/ci/2e0cbb52569bb462cd0c28ab8e21173f14822c30/</link><description>dev_table: Add placeholders for all devices in AN2606 rev 66</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 09:14:44 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/ci/2e0cbb52569bb462cd0c28ab8e21173f14822c30/</guid></item><item><title>Tormod Volden committed [d4ac31] on Code</title><link>https://sourceforge.net/p/stm32flash/code/ci/d4ac31c0d782f9630bc9bb292dc59a81a2c18b1e/</link><description>stm32: Remove duplicate version field</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 25 May 2025 09:14:44 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/ci/d4ac31c0d782f9630bc9bb292dc59a81a2c18b1e/</guid></item><item><title>Samuel Lückoff created ticket #173</title><link>https://sourceforge.net/p/stm32flash/tickets/173/</link><description>STM32U0 Support - Unknown/unsupported device (Device ID: 0x489)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Samuel Lückoff</dc:creator><pubDate>Sun, 25 May 2025 07:23:24 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/173/</guid></item><item><title>Danish Shaikh created ticket #172</title><link>https://sourceforge.net/p/stm32flash/tickets/172/</link><description>Unable to do flash write with page erase for STM32G07xx on I2C</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danish Shaikh</dc:creator><pubDate>Tue, 13 May 2025 05:29:19 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/172/</guid></item><item><title>Alex created ticket #171</title><link>https://sourceforge.net/p/stm32flash/tickets/171/</link><description>BUG: CRC calculation doesn't work over UART</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex</dc:creator><pubDate>Tue, 11 Mar 2025 18:07:14 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/171/</guid></item><item><title>Tormod Volden posted a comment on ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#2d6b</link><description>Please see ST's AN2606 document for the details of your chip. And generally, make sure all other UART or SPI lines are quiet.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 03 Jan 2025 23:50:58 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#2d6b</guid></item><item><title>Tormod Volden modified a comment on ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#e748</link><description>Is there something I need to configure on the STM32 side to properly support the stm32flash utility? So far I've not gotten into the STM32 side of things, as another engineer is working on that SW.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 03 Jan 2025 23:38:38 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#e748</guid></item><item><title>Tormod Volden modified a comment on ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#9d93/9dce</link><description>It doesn't matter if I use "echo 1 | tee" or "echo 1". I put my multimeter on BOOT0 &amp; MCU_RSTn pins and added an exit from one stage to another. Both pins are set correctly throughout the script.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 03 Jan 2025 23:38:00 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#9d93/9dce</guid></item><item><title>Patricia Holden posted a comment on ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#9d93/9dce</link><description>It doesn't matter if I use "echo 1 | tee" or "echo 1". I put my multimeter on BOOT0 &amp; MCU_RSTn pins and added an exit from one stage to another. Both pins are set correctly throughout the script. On Thu, Jan 2, 2025 at 5:04 PM Tormod Volden tormod@users.sourceforge.net wrote: Are you sure echo 1 &gt; file isn't interpreted as echo with stdout (file handle 1) redirected? I usually use echo 1 | tee file which avoids any ambiguity (and also because I can use sudo tee easily). [tickets:#170] https://sourceforge.net/p/stm32flash/tickets/170/...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patricia Holden</dc:creator><pubDate>Fri, 03 Jan 2025 23:27:34 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#9d93/9dce</guid></item><item><title>Patricia Holden posted a comment on ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#e748</link><description>Is there something I need to configure on the STM32 side to properly support the stm32flash utility? So far I've not gotten into the STM32 side of things, as another engineer is working on that SW. On Fri, Jan 3, 2025 at 4:34 PM Patricia Holden pholden@nklabs.com wrote: It doesn't matter if I use "echo 1 | tee" or "echo 1". I put my multimeter on BOOT0 &amp; MCU_RSTn pins and added an exit from one stage to another. Both pins are set correctly throughout the script. On Thu, Jan 2, 2025 at 5:04 PM Tormod...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patricia Holden</dc:creator><pubDate>Fri, 03 Jan 2025 23:05:39 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#e748</guid></item><item><title>Tormod Volden posted a comment on ticket #168</title><link>https://sourceforge.net/p/stm32flash/tickets/168/?limit=25#c06a</link><description>Please don't post images of text, just copy and paste the text. Can't you just flash the part at 0x08000000 with one stm32flash invocation and the part at 0x08100000 with another?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Thu, 02 Jan 2025 22:19:01 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/168/?limit=25#c06a</guid></item><item><title>Tormod Volden modified ticket #169</title><link>https://sourceforge.net/p/stm32flash/tickets/169/</link><description>Flashing STM32F446 fails at 30%</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Thu, 02 Jan 2025 22:12:53 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/169/</guid></item><item><title>Tormod Volden posted a comment on ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#9d93</link><description>Are you sure echo 1 &gt; file isn't interpreted as echo with stdout (file handle 1) redirected? I usually use echo 1 | tee file which avoids any ambiguity (and also because I can use sudo tee easily).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Thu, 02 Jan 2025 22:04:02 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#9d93</guid></item><item><title>Tormod Volden posted a comment on ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#f85d</link><description>Just one tip: If you want to set up the serial port using stty and keep stm32flash from reconfiguring the port, use -b 0.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Thu, 02 Jan 2025 21:53:13 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/?limit=25#f85d</guid></item><item><title>Patricia Holden created ticket #170</title><link>https://sourceforge.net/p/stm32flash/tickets/170/</link><description>Unable to program Nucleo-g070rb using stm32flash utility</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patricia Holden</dc:creator><pubDate>Thu, 02 Jan 2025 21:09:29 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/170/</guid></item><item><title>Patricia Holden posted a comment on ticket #134</title><link>https://sourceforge.net/p/stm32flash/tickets/134/?limit=25#be19</link><description>I was wondering if anyone has used the nucleo-g070rb with stm32flash. I'm getting the error: stm32flash 0.7 http://stm32flash.sourceforge.net/ Using Parser : Raw BINARY Size : 91512 Interface serial_posix: 115200 8E1 Failed to init device, timeout. My HW is set up with an AM623 SOC that controls BOOT0 and RSTn on the STM32. We are using a ttyS0, which is configured properly according to dmesg to do the programming. The following is my script for running the programming: // Set ttyS0 to 8bit, even...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Patricia Holden</dc:creator><pubDate>Sat, 21 Dec 2024 04:59:56 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/134/?limit=25#be19</guid></item><item><title>Mario De Weerd created merge request #25 on Code</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/25/</link><description>Add pre-commit configuration/flow and some fixes</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mario De Weerd</dc:creator><pubDate>Thu, 05 Dec 2024 17:07:25 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/25/</guid></item><item><title>Lionel Ains created merge request #24 on Code</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/24/</link><description>Add support for STM32U5Axxx</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lionel Ains</dc:creator><pubDate>Thu, 05 Dec 2024 13:27:35 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/24/</guid></item><item><title>Stefan Riesenberger posted a comment on ticket #169</title><link>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#7df0</link><description>ohhh that worked! Thank you so much! Sorry for bothering your with my incompetence...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stefan Riesenberger</dc:creator><pubDate>Fri, 20 Sep 2024 08:32:47 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#7df0</guid></item><item><title>Tormod Volden posted a comment on ticket #169</title><link>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#e927</link><description>Or .hex file.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 20 Sep 2024 08:21:02 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#e927</guid></item><item><title>Tormod Volden posted a comment on ticket #169</title><link>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#422e</link><description>It seems that you are programming an .elf file directly onto the device. You should extract a binary file from the ELF file and use that instead.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 20 Sep 2024 08:19:15 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#422e</guid></item><item><title>Stefan Riesenberger posted a comment on ticket #169</title><link>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#ea4b</link><description>Using the STM provided programmer tool works fine.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stefan Riesenberger</dc:creator><pubDate>Fri, 20 Sep 2024 07:26:10 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/169/?limit=25#ea4b</guid></item><item><title>Stefan Riesenberger created ticket #169</title><link>https://sourceforge.net/p/stm32flash/tickets/169/</link><description>Flashing STM32F446 fails at 30%</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stefan Riesenberger</dc:creator><pubDate>Fri, 20 Sep 2024 07:25:17 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/169/</guid></item><item><title>Jonathan  Krämer created ticket #168</title><link>https://sourceforge.net/p/stm32flash/tickets/168/</link><description>Address Problems on STM32H742xG/743xG devices</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan  Krämer</dc:creator><pubDate>Mon, 26 Aug 2024 08:19:40 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/168/</guid></item><item><title>Tormod Volden modified ticket #167</title><link>https://sourceforge.net/p/stm32flash/tickets/167/</link><description>Failed to init device using "-i '-dtr&amp;rts,dtr:-dtr&amp;-rts,dtr'" param</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Mon, 17 Jun 2024 21:38:16 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/167/</guid></item><item><title>Anonymous posted a comment on ticket #167</title><link>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#4086/4f7e</link><description>Thanks for your help. I have searched some materials and solved the problem.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 17 Jun 2024 21:37:31 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#4086/4f7e</guid></item><item><title>Tormod Volden posted a comment on ticket #167</title><link>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#4086</link><description>No, I don't think you understand this at all :) These are serial port control lines, for instance on a USB-serial adapter you may find DTR and RTS in addition to the mandatory TX and RX lines. In this context they can be used like GPIOs on the host. For controlling the STM32 boot mode from the host, these lines (or GPIOs) can be hooked up to Reset and BOOT0 on the STM32. If you are setting BOOT0 (and BOOT1) manually, and also reset the STM32 manually, you don't need to think about any "init sequence"....</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 14 Jun 2024 10:31:46 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#4086</guid></item><item><title>Zhifan Ye posted a comment on ticket #167</title><link>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#5f99/1265</link><description>Thanks for your reply. I didn't find DTR and RTS pins on the board, but in a blog I found that DTR controls "Reset" and RTS controls "BOOT0". I wonder if I understand them correctly.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Zhifan Ye</dc:creator><pubDate>Fri, 14 Jun 2024 08:21:46 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#5f99/1265</guid></item><item><title>Tormod Volden posted a comment on ticket #167</title><link>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#5f99</link><description>What are DTR and RTS connected to?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 14 Jun 2024 08:06:14 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/167/?limit=25#5f99</guid></item><item><title>Zhifan Ye created ticket #167</title><link>https://sourceforge.net/p/stm32flash/tickets/167/</link><description>Failed to init device using "-i '-dtr&amp;rts,dtr:-dtr&amp;-rts,dtr'" param</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Zhifan Ye</dc:creator><pubDate>Fri, 14 Jun 2024 07:46:10 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/167/</guid></item><item><title>Tormod Volden updated merge request #23</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/23/</link><description>dev_table.c: Add STM32C011xx (Device ID 0x443)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 17 May 2024 10:52:22 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/23/</guid></item><item><title>Tormod Volden posted a comment on merge request #23</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#f2b6</link><description>Pushed. (I fixed up the option byte end address, and whitespace.)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 17 May 2024 10:52:05 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#f2b6</guid></item><item><title>Tormod Volden committed [0c1d75] on Code</title><link>https://sourceforge.net/p/stm32flash/code/ci/0c1d759b1662611625d820051b2041430b055828/</link><description>dev_table: Add STM32C011xx (Device ID 0x443)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 17 May 2024 10:51:07 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/ci/0c1d759b1662611625d820051b2041430b055828/</guid></item><item><title>Jasper de Zoete posted a comment on merge request #23</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#ad7a/6fb6</link><description>RM0490 rev 3 https://www.st.com/resource/en/reference_manual/rm0490-stm32c0x1-advanced-armbased-32bit-mcus-stmicroelectronics.pdf Most of the information was found in Section 2 and 3</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jasper de Zoete</dc:creator><pubDate>Fri, 17 May 2024 10:34:00 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#ad7a/6fb6</guid></item><item><title>Jasper de Zoete posted a comment on merge request #23</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#d901</link><description>RM0490 rev 3 https://www.st.com/resource/en/reference_manual/rm0490-stm32c0x1-advanced-armbased-32bit-mcus-stmicroelectronics.pdf Most of the information was found in Section 2 and 3</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jasper de Zoete</dc:creator><pubDate>Fri, 17 May 2024 10:33:23 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#d901</guid></item><item><title>Tormod Volden posted a comment on merge request #23</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#ad7a</link><description>Thanks! Do you have a document reference? It is good to have because sometimes ST's documents are not consistent or they change.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Fri, 17 May 2024 10:30:37 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/23/?limit=25#ad7a</guid></item><item><title>Jasper de Zoete created merge request #23 on Code</title><link>https://sourceforge.net/p/stm32flash/code/merge-requests/23/</link><description>dev_table.c: Add STM32C011xx (Device ID 0x443)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jasper de Zoete</dc:creator><pubDate>Fri, 17 May 2024 10:17:41 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/merge-requests/23/</guid></item><item><title>Tormod Volden posted a comment on ticket #166</title><link>https://sourceforge.net/p/stm32flash/tickets/166/?limit=25#be17</link><description>Great that you could connect. You must not flash an ".elf" file, but a raw binary file. You can use the -v option to verify the flashing at the same time. You can also use -r to read back from flash afterwards (while still in the bootloader, before resetting), and compare with the original file.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Tue, 14 May 2024 16:38:37 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/166/?limit=25#be17</guid></item><item><title>Godwin S posted a comment on ticket #166</title><link>https://sourceforge.net/p/stm32flash/tickets/166/?limit=25#df5c</link><description>Hi, Thanks for the response. Now iam able to connect with the device. When iam trying to flash the device iam getting the following result. stm32flash /dev/ttyS1 -w /lib/firmware/mcu_fw/test1_l010rb.elf -b 115200 stm32flash 0.7 http://stm32flash.sourceforge.net/ Using Parser : Raw BINARY Size : 668104 Interface serial_posix: 115200 8E1 Version : 0x31 Option 1 : 0x00 Option 2 : 0x00 Device ID : 0x0447 (STM32L01xxx/02xxx) RAM : Up to 2KiB (0b reserved by bootloader) Flash : Up to 16KiB (size first...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Godwin S</dc:creator><pubDate>Tue, 14 May 2024 16:15:38 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/166/?limit=25#df5c</guid></item><item><title>Tormod Volden posted a comment on ticket #166</title><link>https://sourceforge.net/p/stm32flash/tickets/166/?limit=25#82f6</link><description>"Failed to init device" can be because it is not in bootloader mode, or it has detected some activity on another bootloader channel than the serial port that you are connecting with.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Mon, 13 May 2024 16:16:15 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/166/?limit=25#82f6</guid></item><item><title>Tormod Volden modified ticket #166</title><link>https://sourceforge.net/p/stm32flash/tickets/166/</link><description>Unable to flash STM32L010C6 Using stm32flash</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Mon, 13 May 2024 16:14:17 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/166/</guid></item><item><title>Godwin S created ticket #166</title><link>https://sourceforge.net/p/stm32flash/tickets/166/</link><description>Unable to flash STM32L010C6 Using stm32flash</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Godwin S</dc:creator><pubDate>Mon, 13 May 2024 16:05:13 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/166/</guid></item><item><title>Tormod Volden committed [ece4d4] on Code</title><link>https://sourceforge.net/p/stm32flash/code/ci/ece4d4095795833c845a64c9109e2aaf752b6621/</link><description>dev_table: Fix up option byte range for device 0x497</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 09:39:50 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/ci/ece4d4095795833c845a64c9109e2aaf752b6621/</guid></item><item><title>Tormod Volden committed [9c1c77] on Code</title><link>https://sourceforge.net/p/stm32flash/code/ci/9c1c773c1092b0f8efd18418bda6db1826c57d4f/</link><description>dev_table: Fix typo in flash start for device 0x483</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 09:39:50 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/code/ci/9c1c773c1092b0f8efd18418bda6db1826c57d4f/</guid></item><item><title>Tormod Volden posted a comment on ticket #160</title><link>https://sourceforge.net/p/stm32flash/tickets/160/?limit=25#c383</link><description>I have just added some RPi info to the Hints section in the wiki, based on another report. Since it mentions dtoverlay=miniuart-bt I think it allows using BT (but no serial console). Please let me know how that works, or if the wiki entry can be improved.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 08:38:04 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/160/?limit=25#c383</guid></item><item><title>Tormod Volden posted a comment on ticket #163</title><link>https://sourceforge.net/p/stm32flash/tickets/163/?limit=25#debf</link><description>FWIW, I have added RPi-specific information about this to the Hints section in the wiki, with a contributed pinctrl example.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 08:29:05 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/163/?limit=25#debf</guid></item><item><title>Tormod Volden modified ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/</link><description>STM32F103 Blue Pill with Raspberry Pi 3 Model B</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 08:26:02 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/</guid></item><item><title>Tormod Volden posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#4df1</link><description>Thanks a lot for reporting back with the solution. I have added it to the Hints section in the wiki.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 08:26:02 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#4df1</guid></item><item><title>Tormod Volden modified a wiki page</title><link>https://sourceforge.net/p/stm32flash/wiki/Home/</link><description>Home</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 08:24:22 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/wiki/Home/</guid></item><item><title>Tormod Volden modified a wiki page</title><link>https://sourceforge.net/p/stm32flash/wiki/Hints/</link><description>Hints</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sat, 11 May 2024 08:23:41 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/wiki/Hints/</guid></item><item><title>Thomas Williamson modified a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e897</link><description>Managed to Resolve it For future people having pains, the best config seems to be: dtoverlay=miniuart-bt enable_uart=1 and remove the segment from cmdline.txt: console=serial0,115200 used ttyAMA0 I haven't tried using the gpio control flags as it seems it was depricated from the kernal, written my own using pinctrl for testing. gpio7 is boot0 gpio27 is reset pinctrl 17 op dh pinctrl 27 op dl sleep 0.1 pinctrl 27 op dh sleep 0.2 sudo stm32flash -b 115200 /dev/ttyAMA0 -v -w generic_boot20_pc13.bin...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 18:46:47 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e897</guid></item><item><title>Thomas Williamson modified a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e897</link><description>Managed to Resolve it For future people having pains, the best config seems to be: dtoverlay=miniuart-bt enable_uart=1 and remove the segment from cmdline.txt: console=serial0,115200 used ttyAMA0 I haven't tried using the gpio control flags as it seems it was depricated from the kernal, written my own using pinctrl for testing. pinctrl 17 op dh pinctrl 27 op dl sleep 0.1 pinctrl 27 op dh sleep 0.2 sudo stm32flash -b 115200 /dev/ttyAMA0 -v -w generic_boot20_pc13.bin sleep 0.5 pinctrl 17 op dl pinctrl...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 18:46:16 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e897</guid></item><item><title>Thomas Williamson posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e897</link><description>Managed to Resolve it For future people having pains, the best config seems to be: dtoverlay=miniuart-bt enable_uart=1 and remove the segment from cmdline.txt: console=serial0,115200 used ttyAMA0 I haven't tried using the gpio control flags as it seems it was depricated from the kernal, written my own using pinctrl for testing. ~~~ shell script pinctrl 17 op dh pinctrl 27 op dl sleep 0.1 pinctrl 27 op dh sleep 0.2 sudo stm32flash -b 115200 /dev/ttyAMA0 -v -w generic_boot20_pc13.bin sleep 0.5 pinctrl...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 18:46:06 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e897</guid></item><item><title>Tormod Volden posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#971e/02c3/99c1</link><description>There is an example in the commit 48231f15 message: stty -F /dev/ttyUSB0 raw parenb -parodd -cstopb cs8 115200 time 5 min 0 \ line 0 -brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -iexten \ -echo -echok -echoctl -echoke stm32flash -b 0 /dev/ttyUSB0</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 05 May 2024 18:14:57 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#971e/02c3/99c1</guid></item><item><title>Tormod Volden posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#dfe3</link><description>Disregard that last comment, I read "same thing" but and didn't notice "without".</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 05 May 2024 18:11:06 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#dfe3</guid></item><item><title>Thomas Williamson posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#971e/02c3</link><description>to my understanding I am not using mini-UART. I disabled the bluetooth etc. not familier with stty, will have to have a poke.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 18:10:45 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#971e/02c3</guid></item><item><title>Thomas Williamson posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e7ab/68a9</link><description>Oh no, that is reproducing it! to clarify I only get 'Failed to set terminal flags' on existing ports.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 18:10:03 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e7ab/68a9</guid></item><item><title>Tormod Volden posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e7ab</link><description>if I use rubbish, e.g. /dev/eoviergmio I get the same thing without 'Failed to set terminal flags' That is weird, but I cannot reproduce it: $ ./stm32flash /dev/eoviergmio stm32flash 0.7 http://stm32flash.sourceforge.net/ Error probing interface "serial_posix" Cannot handle device "/dev/eoviergmio" Failed to open port: /dev/eoviergmio</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 05 May 2024 18:08:39 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#e7ab</guid></item><item><title>Tormod Volden posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#1f26</link><description>There is one commit in git that helped for an issue on Raspberry 3 but I am not sure it is the same issue. Worth trying out latest git maybe. https://sourceforge.net/p/stm32flash/tickets/146/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 05 May 2024 17:21:56 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#1f26</guid></item><item><title>Tormod Volden posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#971e</link><description>Are you using the troublesome mini-UART or the other? https://www.raspberrypi.com/documentation/computers/configuration.html#mini-uart-and-cpu-core-frequency Anyway, a workaround could be to configure the port using stty and then run stm32flash with -b 0.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Sun, 05 May 2024 17:16:01 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#971e</guid></item><item><title>Thomas Williamson posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#9d7c</link><description>I've just inserted a USB-Serial, and /dev/ttyUSB0 does work when it's inserted - but we really need to use the internal serial.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 11:28:23 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#9d7c</guid></item><item><title>Thomas Williamson posted a comment on ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#c9fc</link><description>a full prompt example with all details: pi@test-kit:~ $ sudo stm32flash -v -w blink.bin -b 9600 /dev/serial0 stm32flash 0.7 http://stm32flash.sourceforge.net/ Using Parser : Raw BINARY Size : 146013 Failed to set terminal flags Error probing interface "serial_posix" Cannot handle device "/dev/serial0" Failed to open port: /dev/serial0</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 11:13:11 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/?limit=25#c9fc</guid></item><item><title>Thomas Williamson created ticket #165</title><link>https://sourceforge.net/p/stm32flash/tickets/165/</link><description>STM32F103 Blue Pill with Raspberry Pi 3 Model B</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Williamson</dc:creator><pubDate>Sun, 05 May 2024 11:11:12 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/165/</guid></item><item><title>Guillermo posted a comment on ticket #164</title><link>https://sourceforge.net/p/stm32flash/tickets/164/?limit=25#ed5c</link><description>Hi, Thanks for your answer. According to AN2606 almost every STM32 micro needs a minimum delay, so with the current code, whenever the -i option is used to specify a GPIO sequence, an additional delay will always need to be added at the end of the sequence. To make things worse, leaving this delay out does not automatically cause communication failures: in our tests, we only see communication errors on 10-20% of the cases. That's bad becasue if you don't pay attention to this issue (which users may...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Guillermo</dc:creator><pubDate>Mon, 29 Apr 2024 12:54:36 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/164/?limit=25#ed5c</guid></item><item><title>Tormod Volden modified a wiki page</title><link>https://sourceforge.net/p/stm32flash/wiki/Home/</link><description>Home</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Mon, 29 Apr 2024 12:09:25 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/wiki/Home/</guid></item><item><title>Tormod Volden modified ticket #164</title><link>https://sourceforge.net/p/stm32flash/tickets/164/</link><description>Regression: required delay before entering boot loader mode</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Mon, 29 Apr 2024 12:06:51 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/164/</guid></item><item><title>Tormod Volden posted a comment on ticket #164</title><link>https://sourceforge.net/p/stm32flash/tickets/164/?limit=25#de29</link><description>Thanks for your report. The change should have been mentioned in the ChangeLog and release notes. I have added info to the wiki Hints and online ChangeLog pages. I'll keep this bug open to remember to also mention it retroactively in the next release announcement. I think both changes were intentional but not mentioned. The current behaviour seems consistent with the documentation, and the previous 600 ms pause was not documented anywhere AFAICS.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Mon, 29 Apr 2024 12:06:51 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/tickets/164/?limit=25#de29</guid></item><item><title>Tormod Volden modified a wiki page</title><link>https://sourceforge.net/p/stm32flash/wiki/ChangeLog/</link><description>ChangeLog</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tormod Volden</dc:creator><pubDate>Mon, 29 Apr 2024 11:56:30 -0000</pubDate><guid>https://sourceforge.net/p/stm32flash/wiki/ChangeLog/</guid></item></channel></rss>