-
|
Was anyone able to get Orin NX running with upcoming meta-tegra (wip-l4t-r36.2.0-dp) ? I have Orin NX 8Gb in JNX42 carrier board. If I set the machine to p3768-0000-p3767-0001, then unpacked the tegraflash archive in deploydir and run ./doflash the flash of QSPI is successfull. However if I run ./initrd-flash afterwards, it boots the kernel but it gets stuck. It seems kernel does not see any pci-e and usb devices. This is full log of ./initrd-flash. Content of .env.initrd-flash. If I use official sdkmanager, there are some workarounds about otg and mass storage gadget needed to flash the board, but even without them kernel sees nvme and usb just fine. I also tried meta-tegra master with p3768-0000-p3767-0001 and that woked. I also had to do this change in wip-l4t-r36.2.0-dp. --- a/recipes-devtools/python/python3-kconfiglib-tegra_14.1.0.bb
+++ b/recipes-devtools/python/python3-kconfiglib-tegra_14.1.0.bb
@@ -5,6 +5,8 @@ LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=712177a72a3937909543eda3ad1bfb7c"
SRC_URI[md5sum] = "4ad68618824d4bad1d1de1d7eb838bba"
SRC_URI[sha256sum] = "bed2cc2216f538eca4255a83a4588d8823563cdd50114f86cf1a2674e602c93c"
+PN = "python3-kconfiglib"
+
PROVIDES = "python3-kconfiglib"
inherit pypi setuptools3As without it I get following build error. Or should this kconfiglib-tegra package really be hosted there? Failed to fetch URL https://files.pythonhosted.org/packages/source/k/kconfiglib-tegra/kconfiglib-tegra-14.1.0.tar.gzAny insight would be appricciated. |
Beta Was this translation helpful? Give feedback.
Answered by
madisongh
Apr 28, 2024
Replies: 2 comments 2 replies
-
|
I've tested with a 16GB Orin NX module (SKU 0000) on the WIP R36.2 branch and that worked. It's possible that we have some settings wrong for the 0001 SKU in the configurations on that branch, which might be affecting things. As for the kconfiglib problem, the right fix is probably to set |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
It seems sdkmanager is loading a different BPFDTB file. So I did this in machine configuration. --- a/conf/machine/p3768-0000-p3767-0001.conf
+++ b/conf/machine/p3768-0000-p3767-0001.conf
@@ -12,4 +12,7 @@ EMMC_BCT ?= "tegra234-p3767-0001-sdram-l4t.dts"
TEGRA_FLASHVAR_WB0SDRAM_BCT ?= "tegra234-p3767-0001-wb0sdram-l4t.dts"
+TEGRA_BOARDSKU ?= "0001"
+TEGRA_FLASHVAR_BPFDTB_FILE ?= "tegra234-bpmp-3767-0001-3509-a02.dtb"
+
require conf/machine/p3768-0000-p3767-0000.confAfter that kernel was able to see nvme driver in initrd phase. However the flashing gets always stuck at that stage 5. This is the log from the debug uart of the Orin. After resetting the board, ROM is stuck in recovery mode, always waiting on USB. Not sure why that happened, as initrd phase should not touch QSPI boot firmwares I guess. After re-flashing QSPI with ./doflash, I was able to get to the running system. But I don't see ethernet interface. SDK manager seems to use the very same device tree "tegra234-p3768-0000+p3767-0001-nv.dtb", so I don't know what's the issue here. I can't see any ethernet node to be set with status = okay in that dtb. So maybe there are some overlays needed? Or is there some runtime patching happening? Edit: The ethernet problem was caused by missing r8168 module. I was building core-image-minimal which does not include MACHINE_EXTRA_RRECOMMENDS. Still not sure why the initrd flashing is not succeeding and ROM is stuck in recovery afterwards. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
How long did you wait for step 5 to complete? It takes several minutes for the SPI flash to be programmed with the boot firmware. I don't see the text from the initrd flashing scripts in the serial console log you attached above, but it looks like they did run, since the NVME drive did get exported. As for the missing Ethernet interface, check that you've included the driver in your build. From the log, it looks like you used a |
Beta Was this translation helpful? Give feedback.
Answer selected by
loblik
-
|
You are right, I've not waited enough. I was not aware Yes, later I found out about missing module not installed in minimal image. Using I've created pull requests for kconfiglib and Orin NX 8Gb machine config adjustment. Thanks for the support. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How long did you wait for step 5 to complete? It takes several minutes for the SPI flash to be programmed with the boot firmware. I don't see the text from the initrd flashing scripts in the serial console log you attached above, but it looks like they did run, since the NVME drive did get exported.
As for the missing Ethernet interface, check that you've included the driver in your build. From the log, it looks like you used a
core-image-minimalimage, so it's likely that several drivers were not included. Switching tocore-image-baseshould work better in that case.