OpenEmbedded for Tegra
-
|
looks like Problem installing a built image for Orin Nano on nvme. i build the image and flash the broad . setup-env --machine jetson-orin-nano-devkit-nvme
bitbake demo-image-base
tar -zxvf ~/Documents/tegra-demo-distro/build/tmp/deploy/images/jetson-orin-nano-devkit-nvme/demo-image-base-jetson-orin-nano-devkit-nvme.tegraflash.tar.gz
sudo ./doflashhere the internal part flash log: at the output in UART console: i'm not success to flash the rootfs, beacause it's hang on Setp3, the script can't found the board. the local.conf just add: in my case, my board has been fused. i fuse my do_install:append:tegra234() {
# Remove the existing eks.img installation
rm ${D}${datadir}/tegraflash/eks.img
# Install the custom eks_t234.img file
install -m 0644 /home/ubuntu/Documents/tegra-demo-distro/build/conf/eks_t234.img ${D}${datadir}/tegraflash/eks.img
}i use |
Beta Was this translation helpful? Give feedback.
Answered by
imoyakin
Aug 20, 2024
Replies: 4 comments 2 replies
-
|
Hi @imoyakin |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
thanks i'm joining the discussion group |
Beta Was this translation helpful? Give feedback.
-
|
the uart log may not complete |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have fixed this issue by follow this article case $chip_sku in
00)
;;
D3|D4)
BPF_FILE=$(echo "$BPF_FILE" | sed -e"s,T.*-A1,TE980M-A1,")
;;
D5|D6)
BPF_FILE=$(echo "$BPF_FILE" | sed -e"s,T.*-A1,TE950M-A1,")
;;
*)
echo "ERR: unrecognized chip SKU: $chip_sku" >&2
exit 1
;;just modify I don't know why, my board's sku is 003, but it can't be started by 980M, but only by 950M. Maybe there's some confusion in the nvidia factory. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for letting us know about this. The problem here is that when signing occurs during the build, the default chip SKU is being used when processing the boot firmware, and that default is not correct for the Orin Nano. Sounds like that's also a problem in stock L4T/JetPack. I think we'll need to add a way to set a default chip SKU on a per-machine basis. |
Beta Was this translation helpful? Give feedback.
Answer selected by
imoyakin
-
|
Hi @imoyakin I'm facing exactly the same problem using an Orin Nano 4G. As the only problem seems to be signing during build I managed to overcome it adding the following variables to my custom machine instead of modifying |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have fixed this issue by follow this article
in
/meta-tegra/recipes-bsp/tegra-binaries/tegra-helper-scripts/tegra234-flash-helper.shfile,just modify
TE980MtoTE950M.I don't know why, my board's sku is 003, but it can't be started by 980M, but only by 950M. Maybe there's some confusion in the nvidia factory.