Upgrading Firmware in SBMS0

[Soggy Paws]

I think I have successfully upgraded our "spare" SBMS0.  I couldn't find a step-by-step here on electrodacus.com.

What I found was this link from 2020, plus Dacian's comments in the recent discussion about his new firmware. "New Firmware soon to be released"

https://groups.google.com/g/electrodacus/c/mlqSLOcVAbI/m/S8E7vWYAAgAJ

As soon as Dacian confirms that my result looks correct (haven't powered the spare SBMS0 up, but results output by the programmer software), I'll put together my notes which consolidates Dacian's 2 posts and some Googling.

Here's my log file and a screenshot from the programming software you have to download and install.

Hope this will help someone else who's not an electrical engineer used to flashing microprocessors.

[Dacian Todea (electrodacus)]

Yes it seems you successfully upgraded the firmware to version 6.0c.  Since a few days ago I made a small modification related to diversion with max power point so if you still have those connected you can upload this latest version https://electrodacus.com/SBMS0/sbms0-v03d-v61c.bin.zip

This is the latest on how to connect the SBMS0 for updating the firmware but that older posts I made are also valid https://groups.google.com/g/electrodacus/c/pWpo8UhwBlI/m/rqlrPVBlBAAJ

I never used the STM32CubeProgrammer but I imagine that should be fairly simple to use.

There is no chance to brick the SBMS0 because the boot loader is build in to microcontroller in hardware so even if wires disconnect during programing you can always just write the firmware again.

[Soggy Paws]

If you don't use the STM32CubeProgrammer, what do you use to write the firmware to the SBMS0?  

I googled "How to update my Electrodacus SBMS0 with STLink 2.0", and that's what AI suggested with step-by-step instructions.  It's info about connections weren't quite right (I used yours that you linked above), but the process of using the STM software was useful and apparently correct.  Other than the fact that the download is nearly 1GB, and then another GB to install (on Windows), it was free (had to give up my email address).

Note that my cheap-o STLink connection pins are slightly different order than yours, so you do have to pay attention to what your STLink is labeled.

[Dacian Todea (electrodacus)]

My computers are all running Linux for the past 25 years.  It seems since 2018 STM32CubeProgramer is available on Linux also but it was not available when I started working on this project.

So I use the EclipeIDE when writing the code and that has ST-Link configured as an external tool for convenience.

ST-Flash is a command line utility that is just around 27kB and is simply used like this st-flash write firmware.bin 0x08000000   

ST-Flash is open source and available for Linux, Windows and MAC

I find it silly that they bundle everything in that STM32F373 and so is that huge 1GB install when ST-Flash is just a 27kB executable file.

[Trydan Am Ddim]

I updated the firmware of the SBMS0 in my campervan to version 6.1c this evening. Purchased the HiLetgo version of the ST-Link V2 Programmer to do the update and used the latest version, V2.23.0 of the STM32 Cube programmer on Windows 11.  As was mentioned on this forum, this is free software you only need to give them an e-mail address which they use to send you a link to download the software.

Just got the HiLegGo ST-Link today and while the $5 versions of the ST-Link are also likely to work, a small number of the feedback for those on Amazon mentioned that they were not recognized by the Cube programming software. I “splurged” an extra $5 for the HiLetgo version rather than potentially having to waste time trying to figure out what was wrong if the cheaper programmer did not work and perhaps might never be made to work - unlike Soggy Paws I don’t have a “spare” SBMS0!

The ST-Link and its associated serial number was instantly recognized by the Cube Programming software, so this was encouraging. However, when it came to downloading the software into the SBMS0 I ran into a snag as the software had the Error message of No STM32 target found. The issue turned out to be the jumpers I had between the ST-Link and the SBMS0 …

When wiring these up, I followed the details Dacian provided in the April 19 entry on his conversation “New SBMS0 Firmware soon to be released”. I was aware that not all ST-Link programmers have the same pinouts and had compensated for the fact my programmer was different from Dacian’s. I had triple checked everything before connecting the programmer to the USB port on my computer; as I had previously mentioned - I had no spare SBMS0!

When making the connections to the SBMS0 I was aware that the pins on its programming connector are slightly narrower and closer together (2mm pitch vs 0.1”) than the pins on ST-Link. The supplied jumper leads that came with the ST-Link fitted the programmer’s pins well but were a bit loose on the individual pins on the SBMS0. Additionally, they were a bit of a tight fit when the jumpers where next to each other as the plastic around each pin was likely designed assuming the greater 0.1” pitch between pins. However, despite this I was able to place the required jumpers and “felt” that each pin was getting a good electrical connection.

When the programmer failed to find the STM32 target, I decided to use a different set of jumper cables. While these were also designed for “standard” 0.1” pitch pins, they did not have plastic pieces on the ends. This made all the difference, as I was able to use a pair of pilers to gently squeeze them to reduce their diameter to more snuggly fit the programming pins on the SBMS0. With these new jumpers in place the Cube programmer had no difficulty in finding the STM32 target in the SBMS0 and programming was done in less than 30 seconds.

Immediately noticed some very cool things about the new firmware, will play with it properly over then next few days. 

[sailingharry]

I haven't yet done my upgrade.  I have the ST-Link and want to do the upgrade, but a combination of procrastination and some fear/hesitation have pushed it off.  Real life experience by field operatives such as you (Trydan)  and Soggy Paws have been very valuable.  Thanks for taking the time to share.