Package Details: sw4stm32 2.9-1

Git Clone URL: (read-only)
Package Base: sw4stm32
Description: SystemWorkbench for STM32
Upstream URL:
Licenses: custom
Submitter: MicroJoe
Maintainer: robertfoster
Last Packager: robertfoster
Votes: 9
Popularity: 0.41
First Submitted: 2017-01-28 15:05
Last Updated: 2019-05-14 21:05

Dependencies (6)

Required by (0)

Sources (5)

Latest Comments

1 2 Next › Last »

vnd commented on 2019-09-06 12:16

I'm having the same issue as rp68

rp68 commented on 2019-05-26 07:12

Hi. I have this issue :

[ Unpacking finished ] File execution failed
com.izforge.izpack.api.exception.IzPackException: An error occured- in com.izforge.izpack.installer.bootstrap.Installer.main() at

  • in com.izforge.izpack.installer.bootstrap.Installer.start() at

  • in com.izforge.izpack.installer.bootstrap.Installer.launchInstall() at

  • in com.izforge.izpack.installer.bootstrap.Installer.launchAutomatedInstaller() at

  • in com.izforge.izpack.installer.automation.AutomatedInstaller.doInstall() at

  • in com.izforge.izpack.installer.panel.AbstractPanels.switchPanel() at
  • in com.izforge.izpack.installer.automation.AutomatedPanels.switchPanel() at
  • in com.izforge.izpack.installer.automation.AutomatedPanels.switchPanel() at
  • in com.izforge.izpack.panels.install.InstallPanelAutomationHelper.runAutomated() at
  • in at
  • in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at Caused by: com.izforge.izpack.api.exception.InstallerException: File execution failed- in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at
  • in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at
  • in com.izforge.izpack.installer.unpacker.UnpackerBase.executeFiles() at

an idea ? thanks

2lafru commented on 2019-01-05 10:25

If you're having weird issues with debugging (like being unable to pause execution for a second time, for example), it's because by default, the package creates projects using the system-wide openocd and arm-none-eabi-gdb. You need, for each project, after creation, to specify that it should use sw4stm32's own versions of openocd and gdb. To do this, do the following (for each path, replace the XXXXXXXXs with what's actually in your directories. This can vary depending on the versions) :

Right click on the project -> Properties -> C/C++ Build -> Settings -> Tool Settings -> MCU Settings -> set the path to /usr/lib/sw4stm32/plugins/fr.ac6.mcu.externaltools.arm-none.linuxXXXXXX/tools/st-gnu-arm-gcc-XXXXXXXX/bin/ -> Apply -> Then click on Run/Debug Settings category on the left -> select the only configuration, it should be named "[your project name] Debug" -> Edit... -> Debugger -> Modify the GDB command field to "/usr/lib/sw4stm32/plugins/fr.ac6.mcu.externaltools.arm-none.linuxXXXXXXXX/tools/st-gnu-arm-gcc-XXXXXXXXX/bin/arm-none-eabi-gdb" -> Modify also the OpenOCD Command field to "/usr/lib/sw4stm32/plugins/fr.ac6.mcu.externaltools.openocd.linuxXXXXXXXX/tools/openocd/bin/openocd" -> Apply -> OK -> Apply -> OK

edward-p commented on 2018-11-21 08:47

Since most of aur helpers have no root access, it's necessary to copy udev rules manually into $pkgdir/etc/udev/rules.d/

    # Copy udev rule manually
    for r in $(ls $HOME/.installation/*.rules); do
        install -Dm644 $r \

The_Loko commented on 2018-10-11 15:16

This IDE bundles arm-none-eabi-* tools and openocd but the variable containing the path (${openstm32_compiler_path}) is empty. You can check how debug configurations use that variable by default on the debugger settings.

robertfoster commented on 2018-09-12 13:25

@DCengineer @2lafru I can't test the edits. What do you recommend? To add arm-none-eabi-gdb and openocd as runtime deps? Let me know

ph1r3ph0x commented on 2018-09-07 07:01

I just installed version 2.5 with success (directly from openstm32). It had no problems installing udev rules, however I don't have cubemx installed. I haven't tried to debug yet but everything compiles just fine. This aur package failed to install. So maybe updating it and removing the udev part from pkgbuild will help?

2lafru commented on 2018-06-21 19:01

DCengineer is right. Even without stm32cubemx, the udev rules have to be deleted during installation. And sw4stm32 isn't able to use its own gdb and openocd; so debugging is broken. Can't find a way to suspend and resume execution.

DCengineer commented on 2018-04-13 21:49

This package seems to conflict with stm32cubemx, because they both try to install stlink udev rules. I was able to get both packages installed, but I had to remove the stlink rules during the installation process. Also, I had to use arm-none-eabi-gdb and the AUR openocd package in order to get debugging to work.

znuxor commented on 2017-11-22 16:56

Probably not a secure solution, but changing the owner of /opt/sw4stm32 (sudo chown -R /opt/sw4stm32) is a feasible solution to allow installation of the compiler.

Adding read/write access to the directory and its subdirectories is probably a better idea.