Package Details: stm32cubeprog 2.18.0-3

Git Clone URL: https://aur.archlinux.org/stm32cubeprog.git (read-only, click to copy)
Package Base: stm32cubeprog
Description: An all-in-one multi-OS software tool for programming STM32 products.
Upstream URL: https://www.st.com/en/development-tools/stm32cubeprog.html
Keywords: programmer stm32
Licenses: custom:SLA0048
Provides: stm32cubeprogrammer
Submitter: yjun
Maintainer: taotieren (GPereira, akumaexs, CloverGit)
Last Packager: CloverGit
Votes: 9
Popularity: 0.40
First Submitted: 2021-01-15 20:39 (UTC)
Last Updated: 2025-03-26 11:49 (UTC)

Dependencies (8)

Required by (0)

Sources (7)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

justinkb commented on 2022-05-12 11:30 (UTC)

Missing two make dependencies, namely fontconfig and gsfonts

The build fails in a chroot environment without those present, due to java giving a NPE because it can't find fonts

<deleted-account> commented on 2022-04-25 09:40 (UTC)

For the Failed creating new xdo instance, putting in a wait for the xvfb server to start resolves the problem for me. I put it at 10s, and it worked. I have not tried any smaller values, but 0s fails.

Replace

xvfb-run --auto-servernum --server-args="-screen 0 1920x1080x24" -w 0 ./${pkgname}.xvfb

with

xvfb-run --auto-servernum --server-args="-screen 0 1920x1080x24" -w 10 ./${pkgname}.xvfb

mnhunter commented on 2022-03-08 11:33 (UTC) (edited on 2022-03-08 11:35 (UTC) by mnhunter)

not build

 please wait for minutes ......

Failed creating new xdo instance
Command line arguments: 
Exception in thread "main" java.awt.AWTError: Can't connect to X11 window server using ':101' as the value of the DISPLAY variable.
    at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)...
..........

OS - manjaro, pamac. over yay - same thing. After entering $export DISPLAY=:100 the "...server using:101" - incremental count and not solved.

arilink commented on 2022-03-07 11:29 (UTC)

@yjun When will you be online, looking forward to your help

arilink commented on 2022-02-28 03:31 (UTC)

Is there any developer of stm32cubeprog, I have some problems when trying to call stm32cubeprog.dll and need help from developers

serh commented on 2022-01-15 11:04 (UTC)

Looks like en.stsw-link007-v3-9-3.zip fails the checksum check again, but the version is unchanged.

The new sha256 is: 3452ad87ddb2b0e9b8be30603ed70fb886310d1398afabfd7d3f2bff94ee28d9

yjun commented on 2021-12-08 08:09 (UTC)

@Seas0 Thanks! done.

Seas0 commented on 2021-12-08 03:35 (UTC) (edited on 2021-12-08 03:36 (UTC) by Seas0)

Just apply this patch(it updates stlink updater file name and checksum, and bumps its version to 3.9.3):

diff --git a/.SRCINFO b/.SRCINFO
index f23acbc..95ae791 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,7 +1,7 @@
 pkgbase = stm32cubeprog
    pkgdesc = An all-in-one multi-OS software tool for programming STM32 products.
    pkgver = 2.9.0
-   pkgrel = 3
+   pkgrel = 4
    url = https://www.st.com/en/development-tools/stm32cubeprog.html
    arch = x86_64
    license = custom:SLA0048
@@ -13,10 +13,10 @@ pkgbase = stm32cubeprog
    provides = stm32cubeprogrammer
    options = !strip
    source = en.stm32cubeprg-lin_v2-9-0.zip::https://www.st.com/content/ccc/resource/technical/software/utility/group0/af/f8/e3/60/56/b9/42/9d/stm32cubeprg-lin_v2-9-0/files/stm32cubeprg-lin_v2-9-0.zip/jcr:content/translations/en.stm32cubeprg-lin_v2-9-0.zip
-   source = en.stsw-link007_V2-38-27.zip::https://st.com/content/ccc/resource/technical/software/firmware/group1/4e/80/8d/29/e0/c7/4e/13/stsw-link007_V2-38-27/files/stsw-link007_V2-38-27.zip/jcr:content/translations/en.stsw-link007_V2-38-27.zip
+   source = en.stsw-link007-v3-9-3.zip::https://www.st.com/content/ccc/resource/technical/software/firmware/group1/16/ac/ae/04/0b/01/42/5a/stsw-link007-v3-9-3/files/stsw-link007-v3-9-3.zip/jcr:content/translations/en.stsw-link007-v3-9-3.zip
    source = stm32cubeprog.xdotool
    sha256sums = 53b3648bd0297330b4e82eaba80d69d9fa50ac8e57a41c32d00ac32ca77ccad9
-   sha256sums = bb0c1849aa26fac956618c07cb81e29c68676d28ae630ce7a2498968dcfef33e
+   sha256sums = 56666bd0985fa403008b0a88194266a92dcf346232fa0f4de8a9d072bee62318
    sha256sums = 3194268b73572c4e0fb69e51145f989e85c0415d1c2d932d115708b0c514b005

 pkgname = stm32cubeprog
diff --git a/PKGBUILD b/PKGBUILD
index 4d0c446..e5e1f6a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -6,8 +6,8 @@
 pkgname="stm32cubeprog"
 _pkgname="STM32CubeProgrammer"
 pkgver=2.9.0
-_stlink_updater_ver=2.38.27
-pkgrel=3
+_stlink_updater_ver=3.9.3
+pkgrel=4
 pkgdesc="An all-in-one multi-OS software tool for programming STM32 products."
 arch=('x86_64')
 url="https://www.st.com/en/development-tools/stm32cubeprog.html"
@@ -32,17 +32,18 @@ provides=("${pkgname}rammer")
 options=('!strip')
 _pkg_main_name="${pkgname//prog/prg}-lin_v${pkgver//./-}"
 _pkg_main_url_index="af/f8/e3/60/56/b9/42/9d"
-_stlink_updater_name="stsw-link007_V${_stlink_updater_ver//./-}"
-_stlink_url_index="4e/80/8d/29/e0/c7/4e/13"
+_stlink_updater_name="stsw-link007-v${_stlink_updater_ver//./-}"
+_stlink_url_index="16/ac/ae/04/0b/01/42/5a"
 # stm32cubeprog
 ## https://www.st.com/content/st_com_cx/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/stm32cubeprog/_jcr_content/get-software/get-software-table-body.nocache.html/st-site-cx/components/containers/product/get-software-table-body.html
 # stsw-link007
 ## https://www.st.com/content/st_com_cx/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/stsw-link007/_jcr_content/get-software/get-software-table-body.nocache.html/st-site-cx/components/containers/product/get-software-table-body.html
+
 source=("en.${_pkg_main_name}.zip::https://www.st.com/content/ccc/resource/technical/software/utility/group0/${_pkg_main_url_index}/${_pkg_main_name}/files/${_pkg_main_name}.zip/jcr:content/translations/en.${_pkg_main_name}.zip"
-        "en.${_stlink_updater_name}.zip::https://st.com/content/ccc/resource/technical/software/firmware/group1/${_stlink_url_index}/${_stlink_updater_name}/files/${_stlink_updater_name}.zip/jcr:content/translations/en.${_stlink_updater_name}.zip"
+        "en.${_stlink_updater_name}.zip::https://www.st.com/content/ccc/resource/technical/software/firmware/group1/${_stlink_url_index}/${_stlink_updater_name}/files/${_stlink_updater_name}.zip/jcr:content/translations/en.${_stlink_updater_name}.zip"
         "${pkgname}.xdotool")
 sha256sums=('53b3648bd0297330b4e82eaba80d69d9fa50ac8e57a41c32d00ac32ca77ccad9'
-            'bb0c1849aa26fac956618c07cb81e29c68676d28ae630ce7a2498968dcfef33e'
+            '56666bd0985fa403008b0a88194266a92dcf346232fa0f4de8a9d072bee62318'
             '3194268b73572c4e0fb69e51145f989e85c0415d1c2d932d115708b0c514b005')

 prepare() {

apaulsen commented on 2021-12-07 23:28 (UTC)

Strange, I definitely had a different hash earlier, and then you got a different one, and now it's back to the original. It's passing the check now anyway.

yjun commented on 2021-12-07 15:52 (UTC) (edited on 2021-12-07 15:53 (UTC) by yjun)

@apaulsen hi, that's interesting. I redownloaded en.stsw-link007_V2-38-27.zip and checked the sha256sum, the checksum is same as the old one, so I reverted last commit, maybe you could try to redownload new zip file to slove the error.

# https://st.com/content/ccc/resource/technical/software/firmware/group1/4e/80/8d/29/e0/c7/4e/13/stsw-link007_V2-38-27/files/stsw-link007_V2-38-27.zip/jcr:content/translations/en.stsw-link007_V2-38-27.zip

bb0c1849aa26fac956618c07cb81e29c68676d28ae630ce7a2498968dcfef33e en.stsw-link007_V2-38-27.zip

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »