Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    labkab
    @labkab
    so can work or not with sin/cos ?
    not as absolute encoder but as incremental..
    Nico Stute
    @crinq
    yes
    WolframMalukker
    @WolframMalukker
    Update on the screwed up F3 boards-It's not the board. The boards are good to go
    There is something in the firmware being sent, on either the F4 or F3 board. No comms between the boards
    I checked with a blink sketch first, then did the I/O twiddle check, all flight controls return nominal values.
    on the F3 board, that is. I haven't checked my F4's, as they're the ones that seemed to work properly and will talk to servoterm and take a flash from servoterm properly
    The F3 boards will take firmware from DFU mode, or from an STLink debugger, but will not take a firmware load from an F4 board
    Does anyone have a set of DFU files that they can send from a working 4.3 board? The ones I grabbed from the github are the ones that do not appear to work, and I have not had any luck getting a toolchain built on windows.
    At least, the toolchain I have got working may or may not be generating functional firmware.
    issyvarsano
    @issyvarsano
    @WolframMalukker why you would use windows at all?
    WolframMalukker
    @WolframMalukker
    @issyvarsano Why wouldn't I? The only linux machines I have are out in the unheated shop, or across town in the lab. When I come home to work at night, my electronics workbench has a windows machine sitting on it.
    WolframMalukker
    @WolframMalukker
    Update: Double checking the BOM here, the F3 board uses an 8.000Mhz crystal, correct? The BOM says 8Mhz, the kicad schematic is calling out a 20Mhz part. That makes a big difference.
    John Dammeyer
    @jcdammeyer
    @issyvarsano @WolframMalukker I was never able to get programming or upgrading working from my Windows machine. Ultimately I created a Raspberry Pi3 image, installed the correct software and from there on was able to program them. I kept the MicroSD, marked in a bag for STMBL, so if I have to update or upgrade theoretically I just have to set it up. No worry about going into the shop or screwing around with the crappy browser that it's all organized around.
    Seppo Pietarinen
    @spietari
    I believe it should be 8MHz, I'm using this part https://jlcpcb.com/parts/componentSearch?isSearch=true&searchTxt=C157341
    issyvarsano
    @issyvarsano
    @WolframMalukker @jcdammeyer If you insist so much to use windows , the simple way is to use cygwin .
    John Dammeyer
    @jcdammeyer
    @issyvarsano It's not a matter of insisting on using Windows. It's that Windows is the only OS that supports the development software I've been using for the last 30 years. Easy to say, use Linux, if all you do is check email and browse the web. Different if the only IDE for Microchip PIC16 and PIC18 series was Windows. Or how about what was the Motorola M9S12. That IDE and compiler also only available on Windows. Oh then a friend who detests windows so much it's caused arguments between us had to buy a laptop with WIN-10 on it so he could use the Free Fusion 360. When asked why he didn't use the free Linux stuff he claimed there wasn't anything out there worth using. Lazarus is catching up to Delphi and RAD Studio but has a long way to go. The free Schematic Capture and Layout also have a long way to go to catch up to Protel/Altium. And I use AlibreCAD and now MecSoftCAM (was AlibreCAM). The list goes on and on for what isn't available for Linux or is of lower quality compared to Windows. So it's a no brainer. Yes, the core OS as an embedded kernel may well be used in more devices like Android phones and routers etc. but the reality is most desktops and most companies use Windows.
    5 replies
    issyvarsano
    @issyvarsano
    @jcdammeyer ok. if tou insist to use windows , there is no problem, install the toolchain , install python , add the path , fix the make to point the right place
    but the make file is made exclusively to be used in linux enviorment , so little touch is needed , also dfu uitil is not availabe for linux , you need to fix that as well
    sorry , dfu is not available for windows
    issyvarsano
    @issyvarsano
    or make new project in vs-code , add the compiler , and do it. thats also will work.
    John Dammeyer
    @jcdammeyer
    @issyvarsano Can I send you the invoice for the hours of labour that this will take? My client will also require some Linux Programming so you'll provide the free hours of support? And If I did change over to Linux exactly how does that earn me any extra money?
    WolframMalukker
    @WolframMalukker
    "DFU not available for windows???? It certainly is, I've been using it! It's available from STMicroelectronics. I'll get it fixed.
    andypugh
    @andypugh
    Not helpful, but I do all my STMBL programming with a Mac (And I think that Rene does too?)
    @WolframMalukker Where are you? I could probably flash your board with my outdated (very) setup here that certainly seemed to work.
    WolframMalukker
    @WolframMalukker
    I'm in Kentucky, USA
    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
    DMS-Sci
    @DMS-Sci
    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.
    DMS-Sci
    @DMS-Sci
    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
    WolframMalukker
    @WolframMalukker
    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.
    John Dammeyer
    @jcdammeyer
    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.
    Updating STMBL Firmware-0_2.pdf
    I've pasted in the doc I wrote back in 2018 to use a Pi3 for programming a STMBL.
    DMS-Sci
    @DMS-Sci
    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.
    WolframMalukker
    @WolframMalukker
    Ok gents
    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.
    WolframMalukker
    @WolframMalukker
    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.
    Seppo Pietarinen
    @spietari
    Please download a zip containing my whole STMBL folder, including my latest known working binaries. Commit 713e464, compiled on Aug 18th. https://www.dropbox.com/s/rczuvvafy74t04a/stmbl.zip?dl=0
    I posted notes on how I set up the env, compiled and uploaded on Sep 25th.
    WolframMalukker
    @WolframMalukker
    Thanks, Seppo. I'll let you know if the problem persists.
    kubabuda
    @kubabuda
    JLCPCB.com extended their $2/5 pcs prototyping pricing on aluminium boards