Posted by ibisek on 2020-01-04 15:00

Hey guys & gals!

I am facing the same issue - just the download doesn’t even start.
My sw4stm32 version is 2.9, java version “1.8.0_121” and running on ubuntu 16.04 (4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux).

The HAL download and installation works just fine, the SPL fails right away - id does not get even downloaded.

When I download the zip file manually (stm32cube_fw_f0_v1100.zip) and unzip it to the ~/.ac6/SW4STM32/firmwares or leave it as a zip archive, it doesn’t change a thing.

I have the firmware also in the CUBE MX directory (as configured in the eclipse firmware path) but that has also zero effect.

Any clues?

(EDIT #1) same behaviour on ubuntu 18.04, 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux, openjdk version “11.0.5” 2019-10-15.

(EDIT #2) with java version “13.0.1” 2019-10-15 (and same outcome with java version “11.0.5” 2019-10-15 LTS) and SW4ST32 v 2.9 and selecting an “Empty project” with Ac6 toolchain it actually initiated the download but failed with
Exception in thread “pool-4-thread-1” java.lang.NullPointerException
at fr.ac6.mcu.utils.internal.download.DownloadThreadPool.afterExecute(DownloadThreadPool.java:63)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

(EDIT #3) The same thing happens for F103.. It seems it is directly related to any SPL firmware. HAL gets downloaded just fine.

(EDIT #4) Just tested the same scenario of downloading SPL firmwares for f103 and f030 on Windows 7 with Java 6 and workbench v. 2.9 while facing exactly the the same problem.

(EDIT #5) It actually managed to download SOME firmware - STM32_Nucleo_FW_V1.2.1. If I did not select custom-defined CPU (f103cb or f030cc in my case) but a Nucleo dev board (Nucleo-F030R8 or Nucleo-F103RB) it DID DOWNLOAD the abovementioned firmwares. Other boards, however, do not proceed with the download. Additionally, this firmware seems to be common for both F0 and F1 families (it always refers to the same firmware), but again do not cover the custom defined CPUs (!) Boundcing from a wall to wall.. ;(

.. and just for the record, the same problem is currently being discussed also HERE