my board is JETSON-IO-BASE-A Rev2, its showing
Please refer to Guidance to tell if you are using a NV developer kit - #5 and Debug tips when you hit any issue (fail to boot/ keep reboot ...etc) - #8 by mohan11
failed to start network service, failed to start rpc bind portmap service, failed to start dispatcher deamon for systemd-networkd, failed to start save/restore sound car state, failed to restore /etc/resolv.conf, failed to start avahi mDNS/DNS-SD stack, failed to start ubuntu live cd stack, timed out waiting for device sys-subsystem-net-device-multi.user.device. , timed out waiting for device dev-getty.device. ,failed to start daemon for power management, timeout waiting for device dev-ttys0.device. , failed to start account service. ,failed to start realtimekit scheduling policy service, failed to start snap daemon.
still wont work after refering to [Guidance to tell if you are using a NV developer kit - #5] and [Debug tips when you hit any issue (fail to boot/ keep reboot …etc) - #8 by mohan11]
Please Advice
You need to flash, I don’t think there is any hope in recovering. Incidentally, the Waveshare probably uses a custom carrier board layout, which in turn means the device tree (firmware) will differ from NVIDIA’s. You will need to use Waveshare’s flash software. However, if Waveshare states that you can use NVIDIA’s flash software, then you will use the URL at the end to find your release (and it implies the same carrier board layout in that case):
https://developer.nvidia.com/linux-tegra
do i download the [Driver Package (BSP)] or [Sample Root Filesystem]?
or is it possible to give me a step by step guide to it? that would be great.
and most of the solution everywhere starts by using the ubuntu inside the working nvdia jetson while i cant even boot up in the first place only just error codes like in the picture i gave above
I do want to caution and say again that we are talking about developer kit software in the URLs below. Waveshare would have its own software in some cases (only if the electrical layout of their carrier board differs from a dev kit).
In the past there was only command line flash. In that case you would have used the driver package, unpacked as a regular user (this produces subdirectory “Linux_for_Tegra/”), and the sample rootfs would have been unpacked with sudo into “Linux_for_Tegra/rootfs/”. Then you would have run the command (from “Linux_for_Tegra/”) “sudo ./apply_binaries.sh”. Then you would have the ability to flash a recovery mode Jetson as many times as you wanted.
However, the GUI (with extra capabilities) runs this as well, and the GUI is recommended. You would download JetPack from the JetPack URL. Follow instructions for that on your Ubuntu host PC, and it will do pretty much everything else. You’ll just need to make sure the Jetson is in recovery mode. Note that items can be unchecked in JetPack if you don’t want them, but it isn’t always obvious.
ok let me give it a try and see what happens, i’ll be back
right now i ran in to a problem because my usb wont recognise when i plug the usb-b from my pc to my jetson nano and i cant continue with sdkmanager
SDK Manager is about to flash your Jetson Nano module
WSL users:
From Windows terminal: attach the USB of the device to the Linux distribution:
usbipd.exe wsl attach --busid --auto-attach --distribution
Could not detect a board(refresh)
Keep in mind that the Jetson must be in recovery mode for the detection to work. Was the Jetson started in recovery mode? Also, if WSL2 is used (original WSL won’t stand a chance of working), then it is up to you to pass through the Jetson to WSL2; failing this is the same as no USB detection.
If we get past the above, then a micro-B USB cable which isn’t provided by NVIDIA (or perhaps by Waveshare) is very very suspect to be a problem. There are many “charger” cables out there which claim to support data transfer, but quite literally they have at most two strands of 32 gauge wire for data and simply fail any challenge at all to conditions. I would estimate that two out of three charger cables will fail; one would have to go through about three brands charger cables to find one which actually works for sustained transfer. The NVIDIA dev kits come with a quality micro-B USB cable, but I don’t know what Waveshare comes with.
If there is still an issue when we know that (A) the Jetson is in recovery mode, (B) WSL2 is used with proper USB passthrough, and (C) the cable is good, then it possibly comes down to signal quality issues which might be solved by moving to a different USB port on the host PC; if a USB HUB is used, then you might try direct USB connection without a HUB, or the inverse, that if no HUB is used, try through a HUB (changing the HUB can actually act as something like an adapter for the RF quality).
im pretty sure that the usb-b that before when it was working shows me data when im connected through my home pc and has it own file
look probably im going to give up trying, been up for 3 days now trying to figure it out and i have 0 progress, every error leads to another bigger error. and frankly i just wanted if it is possible to guide me step by step from the moment i rm -rf -no-preserve-root / in my Waveshare Jetson Nano 4GB Development/Expansion Kit Alternative Solution of B01 Kit Come with Carrier Board Jetson Nano Module.
I’m tired boss, Please Advice.
Jetson must be in recovery mode to be honest i cant really tell, one source says it it the recovery mode others say its only bootloader menu, and honestly i have no clue where is the recovery mode and how to access it i tried the connector pins in A02 and B01which has no results and i cant find anything online specificly for my Waveshare Jetson Nano 4GB Development/Expansion Kit Alternative Solution of B01.
Waveshare has their own support for this particular model. If this were a dev kit, then there would be two pins which could be momentarily shorted together, or have a momentary button on it (Waveshare is likely different in how they expose the pins). One pin is the recovery pin, the other pin is a ground pin. Waveshare would have a diagram of this, or a mention of how to put it in recovery mode. The 40-pin header is not the correct connector. On the dev kits the header is something like 10-pin single row right angle under the module, and only visible at the bottom along the edge. Commercial module versions (which Waveshare would use) will differ, and so I cannot tell you specifically where those pins are. Is there any documentation from Waveshare?
so far i cant see from their part anywhere yet, but i already contacted the customer support from waveshare themself and im waiting for a reply.