Description of problem: Outdated stlink app from mga9 repos. Version-Release number of selected component (if applicable): stlink-gui-1.7.0-2.mga9 How reproducible: Looks like stlink release is 1.8.0 https://github.com/stlink-org/stlink/releases/tag/v1.8.0 Steps to Reproduce: If possible please update it.
Assigning to the maintainer!
CC: (none) => geiger.david68210Assignee: bugsquad => zen25000
Is stlink-1.7.0-2 broken in some way or missing support for a particular new hardware device? If not then this request would be outside the Mageia updates policy. Please read the 'Purpose' and 'Version Policy' sections here: https://wiki.mageia.org/en/Updates_policy#Purpose Version 1.8.0 will be available in Mageia 10 when it is released.
"An update shall be issued to either correct a defect in an application" and there are many bug fixes listed. Even if it were not, support for many new targets added, the version we have is 3 years elder than 1.8.0.
CC: (none) => fri
(In reply to Morgan Leijström from comment #3) > "An update shall be issued to either correct a defect in an application" > and there are many bug fixes listed. > > Even if it were not, support for many new targets added, the version we have > is 3 years elder than 1.8.0. OK I have pushed stlink-1.8.0-1 to 9/core/updates_testing. @mesb mesb Would you please test the above with your devices and confirm that there are no issues. I suspect there will not be anyone in QA with suitable test devices and cables. Once confirmed I will submit an advisory.
Keywords: (none) => NEEDINFO
Well, it starts fine. But doesn't see my device at all. I have created an issue for 1.8.0 to see if i am doing something wrong with this software. Will share more data when done.
Did the previous version work for you?
At least it detects some of it's ids, but refuses doing something. I was hope 1.8.0 were fixed this behaviour, but it's not.
I have just tested 1.8.0 using a ST-LINK V2 interface dongle to connect to a nanovna and it appears to be working fine (in cauldron). I noted that you must have the device (e.g. nanovna) in DFU mode before stlink will connect. I am attaching a screenshot. I also dumped the device memeory to a file successfully. I will test in Mga9 later and report back.
Created attachment 14695 [details] Screenshot
Keywords: NEEDINFO => (none)
I think I am using some stlink v2 clone that looks like a USB flash drive in a green color. It works fine with w10 original stlink utility and I wasn't requested to switch it into some DFU mode. Will try to look closer on a weekend.
(In reply to mesb mesb from comment #10) > I think I am using some stlink v2 clone that looks like a USB flash drive in > a green color. That sounds similar to mine. Plug it in and run lsusb in a terminal. You should see a line something like: Bus 002 Device 006: ID 0483:3748 STMicroelectronics ST-LINK/V2 > > It works fine with w10 original stlink utility and I wasn't requested to > switch it into some DFU mode. I was wrong about that - it appears to work (certainly for reading) without setting the device into DFU mode - I'm maybe thinking of dfu-util. > > Will try to look closer on a weekend. It is working here just the same in Mageia 9 as in Cauldron, the memory dumps from my nanovna in both systems are binary equal. See how you go and thanks for your report. There does currently seem to be program launch problem with the version in Mageia 9 repositories that I was not aware of, so I will be adding an advisory for this update to fix it.
An updated stlink package is in 9/core/updates-testing. It is working for me without issues as is the same version in cauldron. Suggested Advisory ################################### stlink has been updated to version 1.8.0 which has many bug fixes and adds support for new devices since the 1.7.0 version it is replacing. See the upstream changelog. [1] References: ################################### https://bugs.mageia.org/show_bug.cgi?id=33568 https://github.com/stlink-org/stlink/blob/testing/CHANGELOG.md [1] Updated packages in 9/core/updates_testing ################################### stlink-debuginfo-1.8.0-1.mga9.x86_64.rpm lib64stlink1-1.8.0-1.mga9.x86_64.rpm lib64stlink-devel-1.8.0-1.mga9.x86_64.rpm lib64stlink1-debuginfo-1.8.0-1.mga9.x86_64.rpm stlink-gui-debuginfo-1.8.0-1.mga9.x86_64.rpm stlink-gui-1.8.0-1.mga9.x86_64.rpm stlink-debugsource-1.8.0-1.mga9.x86_64.rpm From: stlink-1.8.0-1.mga9.src.rpm Testing ################################## This requires a device that uses an STMicroelectronics device supported by stlink and a USB dongle like the STMicroelectronics ST-LINK/V2 to interface it with the computer. Probably the only testing that is practical for QA to do is to check that it installs and that the GUI runs from the desktop main menu .desktop file.
Assignee: zen25000 => qa-bugs
Source RPM: (none) => stlink
Keywords: (none) => advisory
Install test: using MCC, drakrpm as user would (i have testing repo enabled) Selected stlink-gui-1.8.0-1.mga9, dialogue to select the lib per dependency, accepted, let it install. Launched it by Plasma menu, under development. Seem OK, fail to connect of course I can launch file select dialogue...
Whiteboard: (none) => MGA9-64-OKKeywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0208.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED