Toolchain generation for imx-morty

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Toolchain generation for imx-morty

1,764 Views
erikraynolds
Contributor IV

I have built under Ubuntu/Linux 14.04 an Yocto image imx-morty for i.MX6QP with bitbake fsl-image-qt5.

Now I want to generate the cross-toolchain for this image as follows

root@02849625e4d5:/home/root/fsl-morty-bsp/build-x11/tmp/deploy/sdk# sh fsl-imx-x11-glibc-x86_64-fsl-image-qt5-cortexa9hf-neon-toolchain-4.9.11-1.0.0.sh

I got stuck. 

I have used standard version of "tar" package 1.27-1. As problems prevail I did downgraded it to version to 1.26 version with no success.

Here is the toolchain's generation where I got stuck at

NXP i.MX Release Distro SDK installer version 4.9.11-1.0.0
==========================================================
Enter target directory for SDK (default: /opt/fsl-imx-x11/4.9.11-1.0.0):
You are about to install the SDK to "/opt/fsl-imx-x11/4.9.11-1.0.0". Proceed[Y/n]? y
Extracting SDK..........................................................................................................................................................................................................................................................................................................................................tar: ./sysroots/cortexa9hf-neon-poky-linux-gnueabi/lib/firmware: Directory renamed before its status could be extracted
tar: ./sysroots/cortexa9hf-neon-poky-linux-gnueabi/lib: Directory renamed before its status could be extracted
tar: ./sysroots/cortexa9hf-neon-poky-linux-gnueabi/var: Directory renamed before its status could be extracted
tar: Exiting with failure status due to previous errors

How this issue can be fixed?

How to generate cross toolchain correctly.

Labels (1)
Tags (1)
1 Reply

1,273 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Erik Raynolds,

From the description is looks like you already extracted the toolchain using the meta-toolchain or meta-toolchain-qt5 recipes and the installer is placed on the deploy/sdk directory as it should.

I would just run it a little differently, I’m not sure if this could have been the cause of the problem but it wouldn’t hurt to try.

$ ./ fsl-imx-x11-glibc-x86_64-fsl-image-qt5-cortexa9hf-neon-toolchain-4.9.11-1.0.0.sh

I have extracted the toolchain in previous BSPs, I haven’t tested the 4.9.11. If the problem continues let us know.

Regards,

0 Kudos
Reply