Loading...
 
Skip to main content

System Workbench for STM32

Forum List Topic List

Forums » System Workbench for STM32 » Workbench can't see downloaded firmware
 
Thread actions
Print this page
  • Print all pages

    • Workbench can't see downloaded firmware

    Posted by grzegorzn on 2017-12-07 14:21
    I create new project and want it to be StdPeriph based. Workbench says the firmware wasn't found locally so I click Download target firmware. Download is finshed and... nothing happens. Workbench still doesn't see the firmware. It was however successfuly downloaded and I can find it in C:\Users\usr\AppData\Roaming\Ac6\SW4STM32\firmwares. There are ZIP and XML files. Why Workbench doesn't see the firmware it downloaded? How can I proceed with the project creator?
    Reads: 13999
    Posted by christelle.burguera on 2017-12-07 14:37

    Hi grzegorzn !

    Which version are you using ?

    We corrected this issue with the patch 2.3.1.
    You must update your Workbench. if you need help for that, you can read the Help contents > SystemWorkbench for STM32 User Guide > Tips and tricks > Update site mechanism

    Let me know if you're ok
    Christelle


         Posted by grzegorzn on 2017-12-07 14:44

    I don't know. The setup file was named just install_sw4stm32_win_64bits-latest.exe. The Eclipse IDE doesn't show Workbench version. How can I check the version?

    I have Tips and tricks in Help but there is nothing about update and patches.


    Posted by christelle.burguera on 2017-12-07 14:50

    go to Help Menu and open the "About" dialog, click in the "installation details" button, "Features" tab and find for the version of fr.ac6.feature.mcu.ide feature.

    To udpate your installation with the Update site mechanism :

    • Launch Eclipse.
    • Update the tool by Help > Check for updates...
    • Restart Eclipse

    ◦Either automatically if Eclipse proposes it
    ◦By exiting Eclipse and restarting it otherwise.


         Posted by grzegorzn on 2017-12-07 15:12
    It's 2.3.0.201710240950 and after update it's 2.3.1.201711101414. Unfortunately update didn't help. I still cannot create the project, Workbench doesn't see firmware it downloaded.

    Posted by christelle.burguera on 2017-12-07 15:36

    So,
    - which library ?
    - can you send me, just after your try to create your project, the .log you find in your workspace, under the folder .metadata ?


         Posted by grzegorzn on 2017-12-07 15:44

    I'd like to use StdPeriph but when I select Cube HAL the problem is the same.
    The .log file is attached.

    .log (17.97 Kb)
    Posted by cartu38 on 2017-12-07 15:55 France

    Hello,

    You're expecting to work with which target ?

    You're saying .zip and .xml files are present within your local Ac6 directory ... do you have such .zip extracted content available too at same place ?

    Thanks for sharing such details.

    Br,
    cartu38


         Posted by grzegorzn on 2017-12-07 16:03
    The target is NUCLEO-F446RE board. The ZIP is not extracted.
    Posted by cartu38 on 2017-12-07 16:17 France

    Hi back,

    Based on NUCLEO-F446RE target usage expecting to rely on StdPeriph firmware you should have a C:\Users\\AppData\Roaming\Ac6\SW4STM32\firmwares\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0 directory extracted from stm32f4_dsp_stdperiph_lib_v180.zip file.

    Do you have such .zip file ? If yes please could you have a try to extract it by yourself. Once such done please have a new try to create a project (takes care .zip file & extracted content are required to enable firmware package automated detection). On my side such is working fine with latest version you have (no need to unzip by myself).

    According your provided .log analysis sounds some toolchain extraction issue has happened too at first product launch. This issue plus lack of extracted firmware content may be related to some disk space issue ... please double check.

    Feel free to share back !

    Br,
    Vincent

         Posted by grzegorzn on 2017-12-07 16:35

    Yes, I have this file. I can extract it and create the project manually. There is no problem with that, I was using Eclipse for STM32 projects for a few years. Now I wanted to give System Workbench a try and see if the project creator can save me some work and be an alternative to standalone Eclipse. But it seems it can't, I have to do everything as before.

    Indeed there was toolchain extraction problem. I think it was because the Workbench wasn't run as administrator. When I started Workbench as administrator the extraction succeded.

    There are 26 GB of free space on disk.

    Posted by cartu38 on 2017-12-07 16:43 France

    Is, having proceeded to handmade extraction, solving firmware package finder issue at new project "Project Firmware Configuration" wizard page ?

    If not please double check System Workbench > Firmware Installation preferences are including your local repository within firmware search path.


         Posted by grzegorzn on 2017-12-07 17:03

    I was refering to extracting to same place, e.g. Desktop, and manually adding lib files to project, without creator.

    Extracting to the same directory as downloaded ZIP file, so Workbench can notice it fails, because of "Path too long" error. The ZIP path itself (C:\Users\User\AppData\Roaming\Ac6\SW4STM32\firmwares\.tmp_STM32FirmwareInstall_2364644042357059320.zip) is 103 characters. ZIP also contains long paths which adds to a number grater than 260 characters limit. An example:
    C:\Users\User\AppData\Roaming\Ac6\SW4STM32\firmwares\.tmp_STM32FirmwareInstall_2364644042357059320\stm32f4_dsp_stdperiph_lib_v180\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0\Libraries\CMSIS\Documentation\Core\html\_c_o_r_em_i_s_r_aexceptions_pg.html
    This is 245 characters, near the limit. And in the ZIP there are file with even longer names. So I suspect it can be the cause of creator failing to extract the firmware.
    Related article: http://news.softpedia.com/news/microsoft-removes-260-characters-path-length-limit-in-windows-10-redstone-504596.shtml

    Posted by cartu38 on 2017-12-07 17:31 France

    Trick is I'm relying myself on Win7. No issue about firmware install related to windows path length. If you get a look to System Workbench itself files you'll see even longer paths ...
    On my side having a try to unzip firmware file relying on 7-Zip within an artificially deep repository I'm not getting issue.

    I'll try to get a try on a Win10 host just in case.

    In the meantime as sounds you're able to extract manually required firmware on your desktop. Could you have a try to set your desktop path as first path within System Workbench > Firmware installation preferences search path ?. Have a new try then to create a project. Firmware install should occur relying on such first path ...

    Please share back !

    Posted by cartu38 on 2017-12-08 08:23 France

    Hello,

    I've got chance to ping a win10 host. No issue at all ...

    Br,
    cartu38

         Posted by grzegorzn on 2017-12-08 12:40

    So maybe it's something different than path length.

    I changed the download path to desktop and the firmware is downloaded to desktop but not extracted.

    I ran Process Monitor to find some clues. I see that System Workbench downloads the ZIP file, writes the task XML file and then reads a few times the downloaded ZIP file. Then it tries to open directory C:\Users\User\AppData\Roaming\Ac6\SW4STM32\firmwares\.tmp_STM32FirmwareInstall_6602110389395471109\STM32F4xx_DSP_StdPeriph_Lib_V1.8.0 but it doesn't exist. Then it looks for:
    C:\Users\User\.stm32cubemx
    C:\Users\User\.stm32cubeup
    They don't exist and Workbench enumerates all directories in C:\Users\User\AppData\Roaming\Ac6\SW4STM32\firmwares but doesn't look inside. Then it gives up.

    Posted by cartu38 on 2017-12-08 14:34 France

    Sounds all such is expected behavior except unzip is failing 😑.

    Just to provide you some clue about what you're able to see Thanks Process Monitor.
    1) You're requesting for some firmware setup as identified not available already within firmware search path you can specify Thanks dedicated preferences.
    2) Firmware process download is initiated within some temp directory created as child of first path of firmware search path. .xml file is basically download process trace.
    3) Once download completed, a .zip file should be available. Such zip file is checked a bit (checksum ,...) prior moving next step
    4) Expected behavior here if .zip is confirmed as fine is content extraction about
    5) Back once extraction done some checks are performed to confirm data integrity
    6) If all is ok temporary material is promoted to expected area (first path of firmware search path) and temporary repository removed.
    7) Firmware setup process is then considered as finished. Firmware finder is invoked back. Finder should find obviously fresh installed firmware package ...

    As within your current session step 4 is failing, step 7 finder process is failing to find within primary path expected firmware package (as not installed due to fail) and so is scanning back your full search path (which is including CubeMx tool default repositories ...)

    Unfortunately I've no clue to explain why unzip process is failing on your side ... 😑. I've no local issue and you're first end user to complain about. I'm definitively convinced you're facing some issue but which ?

    Not an explanation about but workable work around should be to uncompress by yourself .zip file within an area part of search path. Having .zip & extracted material available within search path, firmware finder should be able to get your local firmware installation allowing you to go ahead ...

    Feel free to comment / share back.

         Posted by grzegorzn on 2017-12-08 17:00

    If I extract the ZIP into C:\Users\User\AppData\Roaming\Ac6\SW4STM32\firmwares\STM32F4xx_DSP_StdPeriph_Lib_V1.8 then the firmware cannot be found. Process Monitor shows Workbench doesn't look for that folder anyway. It tries to open "STM32F4xx_DSP_StdPeriph_Lib_V1.8" after ZIP download but it happens every time in different temp subfolder. Not firmwares directly.

    I performed tests on 4 virtual machines (Win10, Win2008, 2 x Win7) and everywhere problem is the same.

    As for toolchain extraction it's connected with installation directory. If I install to Program files I have to run Workbench as admin to finish toolchain installation. If I install Workbench in default path then toolchain install itself without running Workbench as admin. Why does Workbench installer have problem with Program files folder? It's default place for application on Windows. Workbench should install to Program Files as default. The other observation is that when installing in Program Files there are some windows form Windows Installer (MSI) shown which don't show when installing to default path.

    Posted by cartu38 on 2017-12-11 09:05 France

    Thanks already to your dedication to analyze such issue !

    1) About Program files directory usage.
    - Sounds to me such "special" directory is write protected by OS if end user is not identified as admin. My guess is to install System Workbench for STM32 under such root directory you have to use admin mode. Once such done tool chain extraction is occurring at first tool launch. If at that point you're only regular end user ... OS is not allowing you to write any more at that place.
    - About extra pop-up at install sounds such are related to STLink drivers setup. Double check has to be done but maybe space character within "Program files" directory name is not so well supported. If confirmed should be fixed asap.

    2) About firmware install issue ... sounds to me it cannot be related to same concerns as such is considered as local to end user data ... still not able to point what may be issue here ...


     
    Collapse/expand modules below