cancel
Showing results for 
Search instead for 
Did you mean: 

Error during SDK extraction

UVV
Associate III

This page mentions that you are supposed to use tar xf for SDK extraction. Unfortunately this doesn't work for the latest SDK 6.6 (scarthgap), it looks like the SDK is just a tar archive and not compressed.

 

$ tar xf en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gz 
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
$ tar xzf en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gz
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
$ file en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gz
en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gz: gzip compressed data, from Unix, original size modulo 2^32 934342372 gzip compressed data, unknown method, ASCII, was "", encrypted, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32 934342372

 

But you get rid of the extension or pass it through `gunzip` first, then everything works:

$ gunzip en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gz
$ tar xf en.SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar

 

So it's either the command is not correct, or a compression is missing. Either way, I suggest to use tar.xz instread, because it provides a better compression ratio, and tar xJf for extraction respectively.

6 REPLIES 6
Kevin HUBER
ST Employee

Hello @UVV ,

Thank you for reporting this issue. 

We are looking at it to fix it.

 

Best Regards,

Kevin

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Charles-Renoir
ST Employee

Hello @UVV ,

Our technical team is investigating the issue that is not yet reproducible and may depend on some configuration at user end.

Could you please help us to fix this and provide details about your configuration: machine, browser, location (IP), time of download ?

Thanks a lot.
Charles

Original download: 02.01.2025, 11:27 CET, MacOS, Firefox 133.0.3, Belgian IP address (VPN).

Tried again: 08.02.2025, 17:56 CET, Linux, Firefox 115.9, German IP address (no VPN).

Same result.

 

embeddedbro
Associate III

I am also having this issue

 

I am also having this issue

easily reproducible. 

Charles-Renoir
ST Employee

Hi @embeddedbro , @UVV ,

Our SW team tested on a Linux machine and there is no problem to unpack the SDK downloaded on st.com. They did that on a platform as specified in this document: https://wiki.st.com/stm32mpu/wiki/PC_prerequisites

Please make sure to check the note related to https://wiki.st.com/stm32mpu/wiki/PC_prerequisites#Windows_PC as there are limitations with WSL2.

If your build environment is compliant with these prerequisites, you should not have the unpack issue, neither any other issue during the build.

If you still have a problem, you could check the md5 checksum. There might be some download issue with the package on your end.

md5sum: 42d81e5f6a5f8de4e82bcc9fdf93c43f  SDK-x86_64-stm32mp1-openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11.tar.gz

Let me know if you need further support on that topic.