i.MX8 ULP EVK - core-image-minimal-secure-boot build problem

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

i.MX8 ULP EVK - core-image-minimal-secure-boot build problem

ソリューションへジャンプ
1,172件の閲覧回数
ddresser
Contributor III

Hello,
I am trying to build a minimal secure boot exmple for an i.MX8 ULP EVK board using these commands


# repo init -uhttps://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.23-2.0.0_security-reference-design.xml
# DISTRO=fsl-imx-wayland MACHINE=imx8ulp-lpddr4-evk source imx-setup-release.sh -b buil
echo "CST_PATH = \"/my/path/to/cst-3.4.1\"" >> conf/local.conf
# bitbake core-image-minimal-secure-boo


I have generated the certs and keys with CST.


I am seeing this error:


ERROR: cargo-native-1.75.0-r0 do_compile: ExecutionError('/home/ddresser/src/imx-yocto-bsp-secureboot/build/tmp/work/x86_64-linux/cargo-native/1.75.0/temp/run.do_compile.19360', 101, None, None)
ERROR: Logfile of failure stored in: /home/ddresser/src/imx-yocto-bsp-secureboot/build/tmp/work/x86_64-linux/cargo-native/1.75.0/temp/log.do_compile.19360
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: Using rust targets from /home/ddresser/src/imx-yocto-bsp-secureboot/build/tmp/work/x86_64-linux/cargo-native/1.75.0/rust-targets/
| NOTE: cargo = /home/ddresser/src/imx-yocto-bsp-secureboot/build/tmp/work/x86_64-linux/cargo-native/1.75.0/cargo-1.74.0-x86_64-unknown-linux-gnu/bin/cargo
| NOTE: /home/ddresser/src/imx-yocto-bsp-secureboot/build/tmp/work/x86_64-linux/cargo-native/1.75.0/cargo-1.74.0-x86_64-unknown-linux-gnu/bin/cargo build -v --frozen --target x86_64-unknown-linux-gnu --release --manifest-path=/home/ddresser/src/imx-yocto-bsp-secureboot/build/tmp/work/x86_64-linux/cargo-native/1.75.0/rustc-1.75.0-src/src/tools/cargo//Cargo.toml
| error: could not execute process `rustc -vV` (never executed)
|
| Caused by:
|  Exec format error (os error
| WARNING: exit code 101 from a shell command.
ERROR: Task (virtual:native:/home/ddresser/src/imx-yocto-bsp-secureboot/sources/poky/meta/recipes-devtools/rust/cargo_1.75.0.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2232 tasks of which 2231 didn't need to be rerun and 1 failed.Summary: 1 task failed:
 virtual:native:/home/ddresser/src/imx-yocto-bsp-secureboot/sources/poky/meta/recipes-devtools/rust/cargo_1.75.0.bb:do_compile


I have tried cleaning and rebuilding cargo-native and rust with the same results. Any suggestions are appreciated. Thanks.

0 件の賞賛
返信
1 解決策
1,116件の閲覧回数
ddresser
Contributor III

I resolved this by updating the repo manifest.  I submitted a pull request with a fix.

https://github.com/nxp-https://github.com/nxp-imx/imx-manifest/pull/8/imx-manifest/pull/8 

元の投稿で解決策を見る

5 返答(返信)
1,117件の閲覧回数
ddresser
Contributor III

I resolved this by updating the repo manifest.  I submitted a pull request with a fix.

https://github.com/nxp-https://github.com/nxp-imx/imx-manifest/pull/8/imx-manifest/pull/8 

1,105件の閲覧回数
Harvey021
NXP TechSupport
NXP TechSupport

Thanks for the note, will inform the owner to have an update.

You can also work with other BSP - like the one for reference - L6.6.36_2.1.0-DOCS 

 

Regards

Harvey

 

Regards

Harvey

 

0 件の賞賛
返信
1,139件の閲覧回数
ddresser
Contributor III

FYI, running the command as it appears in the doc gives this:

ddresser@elmore:~/src/imx-yocto-bsp-secureboot$ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.52-2.2.0_security-reference-design.xml

Downloading Repo source from https://gerrit.googlesource.com/git-repo

fatal: manifest 'imx-6.6.52-2.2.0_security-reference-design.xml' not available

fatal: manifest imx-6.6.52-2.2.0_security-reference-design.xml not found

================================================================================

Repo command failed: UpdateManifestError

        Unable to sync manifest imx-6.6.52-2.2.0_security-reference-design.xml

0 件の賞賛
返信
1,139件の閲覧回数
ddresser
Contributor III

Thanks for the response.  Yes, I have tried that.

I am using the process:

10.9.1.3 Yocto setup for secure boot build

from https://www.nxp.com/docs/en/user-guide/IMX_LINUX_USERS_GUIDE.pdf 

I am able to build the non-secure boot process from the same document successfully.

I just noticed that the document specifies the `imx-6.6.52-2.2.0_security-reference-design.xml` on the `imx-linux-scarthgap` branch

repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap - m imx-6.6.52-2.2.0_security-reference-design.xml

However, that branch has this version of the file:

imx-6.6.23-2.0.0_security-reference-design.xml`

I see references to the 6.6.52 version in the commit notes, but don't see that file.

0 件の賞賛
返信
1,152件の閲覧回数
Harvey021
NXP TechSupport
NXP TechSupport

Hello,

Have you tried to bitbake -c cleanll cargo; bitbake cargo?

And assume that your host to build is version of Ubuntu 22.04 and all packages for host setup not missed.

 

Regards

Harvey

0 件の賞賛
返信