If you have a .hex or .s19 file, that will do fine, I can generate a working DFU and load that.
I've already done that to get a blinkdammit.dfu sketch made and installed...and it does blink appropriately
I just think that the premade f3.dfu and f4.dfu that I have is no good for whatever reason-I doubt many people use them so it's not inconcivable that they have a bug in them
I have tried to get the prebuilt firmware installed via the git/servoterm methods but while F4 installs fine the F3 always fails
A few more tips if you haven't tried this already... Connect the USB directly to the F3 board. Then use the tip of a piece of braided wire to short out the boot pads on the F3 board, keep your hand there, and power on the F3 board with 24v DC. You have to short out the boot pads AS you power on the F3 board. This should get it into bootloader mode.
Now the F3 board alone is powered on. Go to your computer and open up terminal and type "lsusb" This will show the connected USB devices... if you don't see something that says STM microcontroller or something like that, then try the boot process again. If you aren't able to get the USB device to show up at all, then maybe your board is fried. I accidentally fried one F3 board by connecting the power the wrong way.
Once you confirm that the computer (in my case a RasPi 4) can see your F3 board as a USB device, then type in "make f3_all_btburn" and that should flash the F3 board. You'll see some stuff go across the screen as it sayd downloading
If you have a RasPi 4, I can send you an image of my SD card that I used to flash 50 boards
Those only work for linux-based machines. I've already mentioned that I am using a windows machine-and I can follow all of those instructions up to "make f3_all_btburn, and where my process differs is that I open up DFUse.exe and select F3.dfu, and write that to the board.
As I've said in a separate thread. I know that. Which is why I created a Pi3 image and compiled and programmed my 3 STMBLs with that. And this forum isn't or shouldn't be about Linux/Windows wars. The reality is if you want to easily program a STMBL you need Linux and a Pi3 is so cheap. If someone can't afford that then perhaps a DIY STMBL is also not a good idea.
I've pasted in the doc I wrote back in 2018 to use a Pi3 for programming a STMBL.
I used a RasPi 4 to flash the firmware to the boards, then a Windows 10 laptop to run Servoterm and successfully test the motor. If your F3 board isn't showing up as a connected USB device then maybe the board is messed up.
For the 100th time, the board shows up exactly how it should on windows 10.
I can load the firmware, and verify with ST's tools that it writes properly
I do not think that the F3.dfu firmware that is included with the STMBL archive is any good-that's what I'm getting at.
I think that when it's compiled from source, it works fine-otherwise too many people would be having issues.
But it appears I'm the only person who has used the ST tools to do a DFU style upload.
That's what started the whole request for someone who could readily compile the firmware on a known working toolchain, and send over the .hex or .s19 output, which is easily converted to .dfu and uploaded.
I posted notes on how I set up the env, compiled and uploaded on Sep 25th.
Thanks, Seppo. I'll let you know if the problem persists.
JLCPCB.com extended their $2/5 pcs prototyping pricing on aluminium boards
Hey, should we get Mesa 7I94 for stmbl, is that as plug and play as it looks?
@rabrabar it is.
On the LinuxCNC side, yes.
It should all auto-detect.
Once more what is the command to enable step/dir command? Which part of the git outlines step/dir details?
read the integrator manual
Located in which folder?
step/dir: link enc_cmd enc_cmd0.mode = 1
I would like to flash my completly new soldered stmbl.
But the Board only pops up as STM32 BOOTLOADER and not as stm in dfu mode
Can someone give me a hint?
what OS are you flashing from?
If Windows, yo MUST use the bootloader jumper to get it in DFU mode. To do this, you must un-power both boards, short the boot jumper, power whichever board you're programming and then unshort the boot jumper. THEN it will appear as a DFU device
if it shows up as STM32 BOOTLOADER it is in dfu mode
@issyvarsano which integrator manual?
@rabrabar if you want to use it with linuxcnc , then you need to read the manualfrom the linuxcnc web
So therefore it is not recognized from DfuSeDemo and I am not able to flash it.
I will try it again otherwise i think I have to flash it via SWD.
@Paule2002 The manual was written by a Mac user. It is possible that the reported status for DFU mode is different in Windows. If Nico says that "STM32 BOOTLOADER" == DFU mode then I would proceed on the basis that he is correct.