search

flathub / com.st.STM32CubeIDE

https://flathub.org/apps/details/com.st.STM32CubeIDE
2 stars 8 forks source link

fix usb flashing and various updates #18

Closed ssievert42 closed 1 year ago

ssievert42 commented 1 year ago

This should fix #2 #15 and #16 In order for usb flashing to work, the user needs to manually add a udev rule specific to the used device, for which I added a brief explanation to the application description. Things that were changed:

I have been using this version for the past semester with a STM32 Nucleo-L476RG, and flashing and debugging seems to work fine :)

flathubbot commented 1 year ago

Started test build 17260

flathubbot commented 1 year ago

Build 17260 successful To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/129623/com.st.STM32CubeIDE.flatpakref
FakeShemp commented 1 year ago

Awesome! Thanks for taking the time to make this work again!

GladOSkar commented 1 year ago

Hey @ssievert42 sorry to bother you, but i can't get this to work. I added the udev rule and restarted everything, but i still get "No ST-LINK detected". I know the connection is fine because i can mount it as a mass storage device and see no error in the host system. Is there any other trick or way to debug? Thanks!

ssievert42 commented 1 year ago

Hey @GladOSkar sadly I don't have the hardware anymore to test this :( Are you sure you used the correct usb device id? I am by no means an expert on udev rules; the one I put in the description seemed to work fine for the device we were given. You could try some of the ids listed here if the one you see when doing lsusb doesn't do the trick. One more thing (how I figured out that the thing needed libusb) could be to try running stlink-server from inside the sandbox and have a look at what it spits out. Just do flatpak run --command=bash com.st.STM32CubeIDE to get a shell inside the sandbox. From there you should be able to start stlink-server -d5 or just try stlink-server --help to see what other options there are.

GladOSkar commented 1 year ago

@ssievert42 Thanks, those commands were what i was looking for wrt debugging. Will try them as soon as i can :)

GladOSkar commented 1 year ago

@ssievert42 Well, PEBKAC. I named the udev rule .rule instead of .rules. Everything works now. Thanks, your debugging commands helped a lot!

ssievert42 commented 1 year ago

@GladOSkar I guess that one is at least partially on me for writing "a file" in the description :sweat_smile: Glad I could help you :)