# Nvidia jetson nano not booting **URL:** \ **Category:** Jetson Nano\ **Tags:** boot\ **Created:** [March 27, 2024, 1:57pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618 "2024-03-27T13:57:08Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![kevin227](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@kevin227](https://forums.developer.nvidia.com/u/kevin227)\ **Post date:** [March 27, 2024, 1:57pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618/1 "2024-03-27T13:57:08Z")
I’ve written the jetpack on my sd card but Jetson Nano won’t boot. this is the error I get. ![Screenshot 2024-03-27 at 15.56.34](https://global.discourse-cdn.com/nvidia/original/4X/5/c/a/5ca494aed614558631a4f059812eb260405c9dab.jpeg) ---
**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\ **Post date:** [March 27, 2024, 4:55pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618/2 "2024-03-27T16:55:01Z")
It is quite likely you must flash the Nano itself once. Only the operating system is on the SD card, but the equivalent of a BIOS plus boot content must be compatible, and this is stored in the QSPI of the Nano module. You’d want the newest L4T R32.x (L4T is just Ubuntu plus NVIDIA drivers) found here: [https://developer.nvidia.com/linux-tegra](https://developer.nvidia.com/linux-tegra) You will need a Linux host PC to perform that flash with the Jetson in recovery mode. After that different SD cards should work. ---
**Author:** ![thami](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@thami](https://forums.developer.nvidia.com/u/thami)\ **Post date:** [April 5, 2024, 12:35pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618/3 "2024-04-05T12:35:10Z")
The on checking if the device is on Recovery mode, after having followed all steps in the Guide, the following error message is displayed: jetson-nano-emmc.conf: line 31: /home/swift/Linux\_for\_Tegra/p3448-0000.conf.common: No such file or directory ############################################################################### # L4T BSP Information: # R32 , REVISION: 7.1 ############################################################################### Error: probing the target board failed. Make sure the target board is connected through USB port and is in recovery mode. The device however appears after entering the **lsusb** command Please help ---
**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\ **Post date:** [April 5, 2024, 1:28pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618/4 "2024-04-05T13:28:38Z")
Is it correct that you are manually installing content for flash on the host PC? The file layout would be different if you used JetPack/SDK Manager. If you are manually unpacking, then steps are like this (assumes you’ve downloaded and are in some directory that you can create the content in, and the directory is `ext4` format): 1. Unpack the “driver package” as a regular user. Do _not_ use `sudo`. 2. This would have created `Linux_for_Tegra/`. `cd` into “`Linux_for_Tegra/rootfs/`”. 3. Unpack the “sample root filesystem” _ **with `sudo`** _. 4. `cd` back to “`Linux_for_Tegra/`”. 5. Run “`sudo ./apply_binaries.sh`”. From that point forward you can flash. From `Linux_for_Tegra/` examine this: `ls -l jetson*.conf` The `.conf` files, if you remove the `.conf` suffix, are flash targets. The ones starting with “`jetson-`” are just aliases for the technical description. In turn, the technical description is a combination of the module model and carrier board model. Note that you have a dev kit that runs on an SD card; this model does not have eMMC. If you wanted to flash QSPI on a nano dev kit, then looking at those `.conf` files, you might pick this as a flash target: `jetson-nano-qspi` (because there is a `jetson-nano-qspi.conf`; you could also just choose `jetson-nano-devkit` since that is what this is, and you can look at the model each alias points to and see that the `jetson-nano-devkit` target and `jetson-nano-qspi` are actually the same thing for this case) ---
**Author:** ![thami](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@thami](https://forums.developer.nvidia.com/u/thami)\ **Post date:** [April 8, 2024, 1:16pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618/5 "2024-04-08T13:16:43Z")
Yes I am manually unpacking the driver package. This fix could not solve the issue. Could it be that the host machine is running on Ubuntu 22.04LTS, If that’s the case is there a way I can get a hold of the Ubuntu 185.04LTS version? I could not find any online. Should I fail to get Ubuntu 18.04 LTS, is there another alternative method i can use? Also, if the device LED does not turn green (To show it has entered Recovery Mode) does running **lsusb** command and having the device appear on the list enough to confirm if the device is in recovery mode? ---
**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\ **Post date:** [April 8, 2024, 5:48pm UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618/6 "2024-04-08T17:48:52Z")
Normally manual command line unpack and install would work on different “flavors” of Linux. There are other requirements as well sometimes, e.g., QEMU might be involved (and there is a static package as well). You will need Ubuntu 18.04 LTS (or you might see it as 18.05 if patched) to use JetPack/SDK Manager (the GUI front end and “smart” network layer). There are many alternatives if using command line, there are not really any alternatives to use the GUI (sometimes you can use Ubuntu 20.04 and lie to the software with some changes in “`/etc`” for the GUI, but this has no relation to command line). Note that if a file is missing, then if the GUI wants that file, then this too would fail. What was your exact command line for the flash after a manual install? If you `cd` to the “`Linux_for_Tegra/`” directory, what do you see from this command: `ls \*.conf.common’ Also, from that same `Linux_for_Tegra/` directory, what do you see from: `cat rootfs/etc/nv_tegra_release` ---
**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\ **Post date:** [April 23, 2024, 8:18am UTC](https://forums.developer.nvidia.com/t/nvidia-jetson-nano-not-booting/287618/7 "2024-04-23T08:18:23Z")
Closed on April 23, 2024, 8:18am UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.