Hey, I have bought carrier bord of jetson nano, som module, heatsink and connected together, I have flashed image into sd card as this website (https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-devkit) but when i am starting jetson nano by connecting power, monitor etc. My monitor is only showing continue booting and not doing anything, and when i search about this error i have found similar problem asked by someone on nvidia official website(Jetson nano first time boot stuck at "continue booting") and i have also tried to setup jetson nano with help of sdk but in sdk it is showing module not connected.
When you purchase a module separately from a carrier board, it implies you are not using a developer’s kit. Separate modules are the ones which are supported with warranty transfer during resale, so on. One of the defining characteristics of any Nano which is a commercial module is that it has eMMC memory, and no longer boots via SD card. SD card boot is usually not supported, but usually the boot content can be on eMMC, and the rootfs can usually (I won’t guarantee) be put on SD card if you so choose. However, those are special procedures.
The third party carrier board tends to imply that it might not be an exact electrical layout match to the dev kit carrier board. When this occurs (and most third party carrier boards do this) the device tree has to change to tell the module where to find things on the carrier board. The manufacturer of that carrier board will either provide a device tree to use with the stock flash software, or else will provide their own flash software with an edited device tree. On the rare occasion when their carrier board is an exact electrical layout match to the dev kit they will simply state that you can use the NVIDIA flash software without modification.
Incidentally, a dev kit without eMMC has the SD card slot on the module itself, but a commercial module won’t have an SD card slot…that slot will instead be on the carrier board. Drivers and device tree differ during boot stages, so although Linux itself does not have any issue with that, the reason for differences in flash will come from boot content. Jetsons do not have a traditional BIOS, and thus everything that might be considered a BIOS and the boot content are in partitions. For an eMMC model, those are in the eMMC of the module, and for SD card dev kit models, this is in QSPI memory on the module. All of those require flashing of the module itself, and not just an SD card.
If you have official documents from the relevant source, then what they attempt to achieve using an initrd (initial ramdisk) is to create a kind of “adapter” in either eMMC or QSPI memory. That initrd is always understood by bootloaders as it doesn’t really have a full filesystem…it’s just a filesystem tree in RAM. The pointer to the boot device within the module will never point directly at the SD card, but is instead set in the module during flash; what that pointer points at will then point to the actual rootfs. The initrd flash is useful because you can put driver modules in the initrd containing drivers needed for other rootfs devices (the kernel itself is usually on some device which that pointer can reach directly). Thus the initrd flash can set up those pointers and is not the same as the default flash.
I won’t be able to help with the initrd flashing (I don’t have any extra devices to test with), but you should first find the instructions from the third party carrier board manufacturer for what flash software to use. Then expect to flash an eMMC model since you purchased a separate module (the flash options are different compared to SD card model, so I would expect a failure…the SD card is normally not a root device on those models). You could still ask questions here, but until you get the correct flash software and flash target there isn’t much point in talking about initrd flashes.
Hey, Thanks for help. now I have completed setup with the help of sdk manager but now when i have started my jetson nano after giving it power it works good, but it is showing this computer has only 476 mb disk space remaining. Please tell me how to deal eiththis problem.
It sounds like this is a third party carrier board, but you’ve never mentioned brand or model. If you have an SD card, then you could mount this on “/usr/local” or “/home” (after copying original content), and thus free up space by putting this on the SD card, which is fairly simple. Or, you could mount the SD card as the rootfs (leaving the kernel, device tree, and in general “/boot” on the eMMC), which uses initrd flash. However, you’d need the flash software and instructions from the third party carrier board vendor (or at least a statement from them that the NVIDIA flash software is 100% interchangeable; it is unlikely to be a match since the carrier board has an SD card slot).
You might consider what you want to do after checking these:
df -H -Tsudo du -h -s /usr/localsudo du -h -s /home