Guest Posted January 22, 2023 Posted January 22, 2023 Dev kit version, with the SD card, not production eMMC version. Its a step up from the nano. And a step behind the Orin. https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-xavier-nx/ Since they discontinued it, even more reason to find an alternative for an OS. 0 Quote
balbes150 Posted January 23, 2023 Author Posted January 23, 2023 22.01.2023 в 16:52, Nurb432 сказал: And again, my limited knowledge of how these things work, it sounds like just a partition table issue for me to sort out, and things like the device tree/etc are already good enough? Replace the DTB name in /boot//grub/grub.cfg with your model (I do not know which one is needed), you can try all the names in a row from the /dtb/nvidia directory. But if you use the wrong DTB, there is a chance of damage (if incorrect supply voltage values are set there). 0 Quote
Guest Posted January 25, 2023 Posted January 25, 2023 No had a chance to do it yet but i did drag the NVIDIA image to work and got the dtb from there to use so no guessing. kernel_tegra194-p3668-0000-p3509-0000.dtb 0 Quote
paisley Posted January 26, 2023 Posted January 26, 2023 On 1/13/2023 at 12:48 PM, balbes150 said: Please check the launch of the latest versions 20230112-current (6.1.4) and 20230112-edge (6.2-rc3) on jetson Nano. I am interested in the general launch of the system from an SD card or USB flash drive. Tried running 6.1.8 EDGE on Jetson Nano. The O/S boots however dmesg is throwing errors and pwm-fan not available. 6.0.19 CURRENT is working fine. dmesg https://pastebin.com/BxSAbePJ lsmod https://pastebin.com/FK2XJa1Y 0 Quote
balbes150 Posted January 26, 2023 Author Posted January 26, 2023 18 минут назад, paisley сказал: pwm-fan not available. PWM causes kernel 6.1\6.2 to panic, so disabled 0 Quote
paisley Posted January 27, 2023 Posted January 27, 2023 OK thanks. I'll keep an eye out for fixes then. 0 Quote
Carlos Estrague Posted March 18, 2023 Posted March 18, 2023 It's not compatibility with latest bootloader? [cide] [0000.125] [L4T TegraBoot] (version 00.00.2018.01-l4t-c536fca9) [0000.131] Processing in cold boot mode Bootloader 2 [0000.135] A02 Bootrom Patch rev = 1023 [0000.139] Power-up reason: pmc por [0000.142] No Battery Present [0000.145] pmic max77620 reset reason [0000.148] pmic max77620 NVERC : 0x40 [0000.151] RamCode = 0 [0000.154] Platform has DDR4 type RAM [0000.157] max77620 disabling SD1 Remote Sense [0000.161] Setting DDR voltage to 1125mv [0000.165] Serial Number of Pmic Max77663: 0xf24c9 [0000.173] Entering ramdump check [0000.176] Get RamDumpCarveOut = 0x0 [0000.179] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8 [0000.184] Last reboot was clean, booting normally! [0000.189] Sdram initialization is successful [0000.193] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000 [0000.199] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000 [0000.205] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000 [0000.211] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000 [0000.216] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000 [0000.222] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000 [0000.228] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000 [0000.234] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000 [0000.250] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000 [0000.256] Platform-DebugCarveout: 0 [0000.259] Nck Carveout Base=0x00000000ff080000 Size=0x00200000 [0000.265] Non secure mode, and RB not enabled. [0000.269] Read GPT from (4:0) [0000.442] Csd NumOfBlocks=124735488 [0000.447] Set High speed to 1 [0000.450] Error mask set in wait for cmd complete with error 0x3 in HwSdmmcWai [0000.460] Command complete wait failed with error 0x3 Interrupt 0x18001 [0000.467] Number of retries left 4 [0000.476] Using GPT Primary to query partitions [0000.480] Read PT from (2:0) [0000.496] Using BFS PT to query partitions [0000.501] Loading Tboot-CPU binary [0000.530] Verifying TBC in OdmNonSecureSBK mode [0000.540] Bootloader load address is 0xa0000000, entry address is 0xa0000258 [0000.547] Bootloader downloaded successfully. [0000.551] Downloaded Tboot-CPU binary to 0xa0000258 [0000.556] MAX77620_GPIO5 configured [0000.559] CPU power rail is up [0000.562] CPU clock enabled [0000.566] Performing RAM repair [0000.569] Updating A64 Warmreset Address to 0xa00002e9 [0000.574] PT: Partition RP1 NOT found ! [0000.578] Warning: Find Partition via PT Failed [0000.582] Bootloader DTB invalid, fallback to kernel DTB. [0000.588] PT: Partition DTB NOT found ! [0000.592] Warning: Find Partition via PT Failed [0000.596] Error is 1 [/code] Not created DTB partition and partition RP1 not found huh? 0 Quote
Bob Warren Posted April 18, 2023 Posted April 18, 2023 Just wondering what the current state of this is? Since the device is now reaching EOL and the supported version of Ubuntu is now EOL. 0 Quote
nanianmichaels Posted October 7, 2023 Posted October 7, 2023 Hello everyone. Rather late to this thread, but I'm currently trying out a Jetson Nano 4GB (Devkit, no eMMC) I had in my closet. I've already installed the most recent Jetpack (4.6.1), and ran the standard apt update and upgrade commands. From what I could tell after some Google-Fu, I have a 2020.4 version of u-boot. Unfortunately, when I drop in an SD card (or USB drive, for that matter) with Armbian (tried both bookworm and jammy, and jammy with and without a desktop interface), I only get the NVIDIA POST screen, and then a black screen on my monitor. Am I doing something wrong? Any help is appreciated! Thanks in advance. 0 Quote
sledge33 Posted November 17, 2023 Posted November 17, 2023 I have the same problem like nanianmichaels. I have a jetson nano dev-kit 2GB. I tried Armbian 23.8 Bookworm Cinnamon. I ran official Jetpack 4.6.1 before, since I read it should automatically update u-boot. Running/Booting Armbian 23.8 Bookworm Cinnamon from SD-Card gets stuck at Nvidia Startup Screen. 0 Quote
Thomas B Posted December 6, 2023 Posted December 6, 2023 I have the same problem as nanianmichaels and sledge33: No output on HDMI after the Nvidia logo. But otherwise the system is running and can be reached via network. No desktop version installed as it should be used as a server - but using the command line on a display would be helpful as fallback in case of LAN problem or misconfiguration. Device: Jetson Nano 4 GB Developer Kit Arbian version: Armbian_23.8.1_Jetson-nano_jammy_current_6.1.50 0 Quote
Carlos Estrague Posted January 8 Posted January 8 Under Debian 12 image seems cause hangs usb working Any idea why? For some reason disable after init boot . This poblem not happen in Ubuntu image . 0 Quote
Ben M Posted February 17 Posted February 17 For anyone else struggling to boot the Armbian builds on https://www.armbian.com/jetson-nano/ You need to install the newest JetPack packages on your device with the official Nvidia build first (ubuntu 18.04, kernel 4.9), so that the uboot bootloader is upgraded. Especially if you just pulled your Jetson Nano from the closet and you haven't used it in a long time. Here's the upgrade procedure: You need to open /etc/apt/sources.list.d/nvidia-l4t-apt-source.list and modify the repository to use the lastest version of JetPack. For instance if the file says: deb https://repo.download.nvidia.com/jetson/common r32.4 main deb https://repo.download.nvidia.com/jetson/t210 r32.4 main Then you need to change it into this, as 32.7 is currently the most recent version of jetpack that is still compatible with the old Jetson Nanos: deb https://repo.download.nvidia.com/jetson/common r32.7 main deb https://repo.download.nvidia.com/jetson/t210 r32.7 main You can now do: sudo apt-get update sudo apt-get upgrade sudo apt-get full-upgrade It will upgrade everything Nvidia related and will also upgrade the bootloader, you should see something like this: Setting up nvidia-l4t-bootloader (32.7.4-20230608212426) ... 3448-300-0000--1--jetson-nano-devkit- Starting bootloader post-install procedure. Update bootloader completed. Reboot the target system for changes to take effect. Then reboot once into the old SD so that the bootloader gets upgraded on the next reboot. Then you can flash Armbian to an SD card and it should boot. With the uboot upgrade I was able to boot Armbian_community_24.5.0-trunk.19_Jetson-nano_bookworm_current_6.6.16_minimal.img I don't seem to have HDMI output but LAN and ssh works. Probably best to have another SD card so you can quickly swap back your old one with the official Nvidia build if you need to. 0 Quote
Jakub Posted May 28 Posted May 28 (edited) Hi friends Anyone being able to run any of the newest Armbian builds on Jetson Nano + HDMI and/or DisplayPort? PS. I have updated bootloader, system starts itself. It's simply super frustrating that the board lost support even it's still fine to play with. Happy to test any ideas - I have 3 jetson nano devices (one running docker + home assistant and few services organizing IoT home stuff on custom build ubuntu 22), 2 ready for any tests, quite power-full laptop so I can do builds in minutes and some knowledge. Need someone to team-up with so maybe we can finally get the Armbian's build fully functional? Edited May 28 by Jakub 0 Quote
Jakub Posted May 30 Posted May 30 (edited) can this be a problem? [🐳|🚸] Kernel DTB-only for development [ Copying preprocessed version of nvidia/tegra210-p3450-0000.dtb ] '/armbian/cache/sources/linux-kernel-worktree/6.1__arm64__arm64/arch/arm64/boot/dts/nvidia/.tegra210-p3450-0000.dtb.dts.tmp' -> '/armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.dts' arch/arm64/boot/dts/nvidia/tegra210.dtsi:1874.15-1885.4: Warning (unique_unit_address): /usb@7d000000: duplicate unit-address (also used in node /usb-phy@7d000000) arch/arm64/boot/dts/nvidia/tegra210.dtsi:1912.15-1923.4: Warning (unique_unit_address): /usb@7d004000: duplicate unit-address (also used in node /usb-phy@7d004000) arch/arm64/boot/dts/nvidia/tegra210.dtsi:410.37-421.4: Warning (interrupt_provider): /interrupt-controller@50041000: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210.dtsi:442.37-453.4: Warning (interrupt_provider): /interrupt-controller@60004000: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210.dtsi:488.22-503.4: Warning (interrupt_provider): /gpio@6000d000: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts:174.17-416.5: Warning (interrupt_provider): /i2c@7000d000/pmic@3c: Missing #address-cells in interrupt provider arch/arm64/boot/dts/nvidia/tegra210.dtsi:841.26-948.4: Warning (interrupt_provider): /pmc@7000e400: Missing #address-cells in interrupt provider also defined at arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts:419.15-428.4 arch/arm64/boot/dts/nvidia/tegra210.dtsi:1420.39-1430.5: Warning (interrupt_provider): /aconnect@702c0000/interrupt-controller@702f9000: Missing #address-cells in interrupt provider also defined at arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts:618.33-620.5 [🐳|🚸] Kernel DTB-only for development [ Preprocessed FDT dest: /armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.dts ] [🐳|🚸] Kernel DTB-only for development [ Preprocessed FDT normalized: /armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.normalized.dts ] [🐳|🚸] Kernel DTB-only for development [ Preprocessed FDT normalized, no phandles: /armbian/output/nvidia-tegra210-p3450-0000.dtb--6.1-legacy.preprocessed.normalized.nophandles.dts ] Edited May 30 by Jakub 0 Quote
Helio Perroni Filho Posted July 12 Posted July 12 I was able to boot my Jetson Nano to the latest Bookworm build (Armbian_community_24.8.0-trunk.314_Jetson-nano_bookworm_current_6.6.36_minimal.img.xz) using the procedure described by Ben M. As was the case for him, there is no display output (either HDML or DisplayPort), but I can get local networking if I plug the Nano to my laptop's Ethernet port and create a Shared Connection. However, although I can ping the Nano over the local network, any attempts to SSH to it fail with a "Connection refused" error: $ ping 10.42.0.32 PING 10.42.0.32 (10.42.0.32) 56(84) bytes of data. 64 bytes from 10.42.0.32: icmp_seq=1 ttl=64 time=0.876 ms 64 bytes from 10.42.0.32: icmp_seq=2 ttl=64 time=0.766 ms 64 bytes from 10.42.0.32: icmp_seq=3 ttl=64 time=0.773 ms 64 bytes from 10.42.0.32: icmp_seq=4 ttl=64 time=1.05 ms ^C $ ssh -v root@10.42.0.32 OpenSSH_8.9p1 Ubuntu-3ubuntu0.10, OpenSSL 3.0.2 15 Mar 2022 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to 10.42.0.32 [10.42.0.32] port 22. debug1: connect to address 10.42.0.32 port 22: Connection refused ssh: connect to host 10.42.0.32 port 22: Connection refused Any idea as to why is that? Is it because of the Ethernet connection (as opposed to Wi-Fi), or is SSH not enabled by default? Either way, how can I add the appropriate configurations directly on the SD card? I know that e.g. Raspbian allows a Wi-Fi connection to be pre-configured by editting the wpa_supplicant.conf file, but I'm not sure how to do it on Armbian. 0 Quote
Igor Posted July 14 Posted July 14 On 7/12/2024 at 10:49 PM, Helio Perroni Filho said: or is SSH not enabled by default? It is, but perhaps something else is wrong, ... this device is not monitored by our team anymore, so its hard to say. Did you wait long enough? On 7/12/2024 at 10:49 PM, Helio Perroni Filho said: allows a Wi-Fi connection to be pre-configured https://docs.armbian.com/User-Guide_Networking/#automatic-configuration-on-first-boot 0 Quote
ArmOnJetson Posted September 18 Posted September 18 Since this is an old thread and I spent way too much time trying to get an OS working on the Jetson Nano, here's a bit of info on what worked and didn't work. For brevity, I'll just list the things I struggled with. I'm currently running the v24.11 rolling Armbian Linux 6.6.51-current-arm64 version on the Jetson Nano which is booting from an SSD. HDMI & Displayport output do not work. Keep this in mind, I used a serial connection with a TTL to USB adapter to setup the Jetson Nano. To get WiFi working: (I tried network manager, wpa_supplicant, etc, none of it worked) sudo nmcli device wifi connect “mySSID” password “myPassword” To boot from a USB device, flash the image with BalenaEtcher, etc and then edit the following file: /boot/armbianEnv.txt Add the following and change the PARTUUID to the one from your storage device. (Run sudo blkid to get the PARTUUID) rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u rootdev=PARTUUID=73b59773-eeca-2144-9da5-aea82ed1899b So it's still possible to run the current OS on the jetson, as long as no graphical output is needed. 0 Quote
joseph2025 Posted September 27 Posted September 27 (edited) Hello This version and archive versions do not work on Jetson Nano The green LED is on but there is no Screen https://www.armbian.com/jetson-nano/ Edited September 27 by joseph2025 0 Quote
ArmOnJetson Posted October 3 Posted October 3 Hello joseph2025, The HDMI and Displayport output DO NOT WORK. There's no way around that. If you want to use Armbian on the Jetson Nano, you will have to use it headless and remote connect to it via SSH, the USB, or serial connection. Everything else, beside the display output, does work. 0 Quote
ArmOnJetson Posted November 15 Posted November 15 (edited) Is Armbian finally broken on the Jetson Nano? Upgraded my install to the Linux v6.6 25.02 version and it does not complete a boot anymore. Neither on my upgraded Armbian, nor on a fresh install. The bootlog doesn't even tell anything interesting. Edit: Does anyone have a link to an Armbian 24.11 image, that I can install instead of the current 25.02 one? Below the bootlog, where it gets stuck with the 25.02 image. [ 1.583513] ledtrig-cpu: registered to indicate activity on CPUs [ 1.593473] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available [ 1.603948] drop_monitor: Initializing network drop monitor service [ 1.611220] NET: Registered PF_INET6 protocol family [ 2.296894] Freeing initrd memory: 53328K [ 2.353291] Segment Routing with IPv6 [ 2.357098] In-situ OAM (IOAM) with IPv6 [ 2.361194] NET: Registered PF_PACKET protocol family [ 2.366721] Key type dns_resolver registered [ 2.377905] registered taskstats version 1 [ 2.382740] Loading compiled-in X.509 certificates [ 2.395868] Key type .fscrypt registered [ 2.399939] Key type fscrypt-provisioning registered [ 2.431191] Key type encrypted registered [ 2.435273] AppArmor: AppArmor sha1 policy hashing enabled [ 2.440839] ima: No TPM chip found, activating TPM-bypass! [ 2.446387] Loading compiled-in module X.509 certificates [ 2.451850] ima: Allocated hash algorithm: sha1 [ 2.456434] ima: No architecture policies found [ 2.461021] evm: Initialising EVM extended attributes: [ 2.466157] evm: security.selinux [ 2.469468] evm: security.SMACK64 [ 2.472778] evm: security.SMACK64EXEC [ 2.476435] evm: security.SMACK64TRANSMUTE [ 2.480522] evm: security.SMACK64MMAP [ 2.484177] evm: security.apparmor [ 2.487574] evm: security.ima [ 2.490532] evm: security.capability [ 2.494101] evm: HMAC attrs: 0x1 [ 2.512924] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.525700] clk: Disabling unused clocks [ 2.542482] Freeing unused kernel memory: 9664K [ 2.566901] Checked W+X mappings: passed, no W+X pages found [ 2.572745] Run /init as init process Edited November 15 by ArmOnJetson 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.