My Jetson DevKit started to behave erratically and today stopped to boot completely, I suspect it is a hardware issue. Here are some screenshots of a boot process. I’d be glad for any help to find a possible issue.
Thanks in advance.
Hi alariq,
What’s your Jetpack version in use?
Are you using Jetson Nano devkit with eMMC or SD module?
Please share the full serial console log instead of the screenshot.
Jetson Nano & NX Style - Serial Debug Console - JetsonHacks
SD card on the module. Will try to share the serial console log. Tried it, but that time it did not work for some reason (
Here is the capture. I had to use different Base board for it because it did not produce any output on original one. But overall problems with booting are still there.
minicom.cap.txt (59.9 KB)
And now just a minute after I sent minicom capture it actually booted. Here is a good capture
minicom3.cap.txt (21.8 KB)
I observed this behaviour before.
However now after a minute or two it printed some errors and reboot itself again:
minicom4.cap.txt (4.6 KB)
Are you using the devkit board or custom carrier board for Jetson Nano?
How did you flash the SD card?
[ 31.870990] mmc0: Data CRC error
It seems there’s error from your SD card.
Could you change another SD card and flash it again?
Are you using the devkit board or custom carrier board for Jetson Nano?
No it is same dev kit type board.
How did you flash the SD card?
I used dd
But it worked fine for over a month or so
Will try to use different SD card
Tried a different SDcard it booted, but then after several minutes again hang.
On the other hand I got a new DevKit and tried to use original SD card and had no issues there (at least for the amount of time I was testing the system)
Do you mean the issue is coming from the older devit board?
I would like to check the full serial console log from it could work until it gets hang.
Yes I mean same board, with new card it booted but then after several minutes gave same error.
Now I got a new SD card, flashed new image (standard from here https://developer.nvidia.com/embedded/learn/get-started-jetson-nano-devkit#setup). First time it worked, used minicom /dev/ttyACM0 to finish first time setup, but I selected wrong time zone and then decided to reboot, after reboot it does not work. I am really out of ideas. I’ve attached full log from debug serial here with fresh SD card and some other SD card (which btw worked just yesterday!)
Also, it is a bit strange but it looks like, the problem happens after I power DevKit after it has been out at low temp, but that is not confirmed.
fresh-sd-card.txt (20.9 KB)
other-sd-card.txt (39.3 KB)
I have some more info. I’ve got my last working Jetson Nano :) Module(M) + BaseBoard(BB)
And what I see is that SD card is fine. Also
NewM + NewBB = OK (obviously)
NewM + OldBB = OK,
OldM + NewBB = Fail
OldM + OldBB = Fail (yeah this is why I started the thread)
So it is a problem with Module, but I cannot understand why it happens.
Edit: However, I cannot proceed with install, if I use text mode (dev/ttyACM0) it just says: “System configuration setup wasn’t completed. Please reboot device and try again” right when “Installing System” dialog starts (after I set my username, timezone, hostname, etc).
If I use Display it says that install script crashed.
Do you mean the issue for the specific module?
[0002.135] eeprom_init: EEPROM read failed
..
probe failed, error -1
It seems your SD card doesn’t be flashed completely.
Could you put the SD card on the devkit board and use SDKM to flash it?
i tried to:
sudo ./flash jetson-nano-qspi-sd mmcblk0p1
using old SD card and fresh new one. I get issue similar to: this (first post)
so then I tried to flash on spi.
sudo ./flash jetson-nano-qspi mmcblk0p1
this was successful, but then it could not boot (I’ve attached log file)
minicom.txt (19.3 KB)
Edit: then I tried to also use card reader and put SD card there it moved a bit further (see attached file)
minicom-cardreader.txt (21.5 KB)
but still could not boot.
Edit2: ok I just realized that it did not flash spi correctly as well, even though ./flash.sh script said it was ok. I just noticed last partition written was: VER, there was no write to APP partition! Then I took module and changed base board and it went fine (flashing on sd card) and I can finish setup after this over /dev/ttyACM0. I am lost
Funny thing, then I change back to old baseboard and I can boot… Maybe microusb was faulty there, no idea. But with old Module it still does not work
Ok, regarding SPI flash it is me being stupid, as I understand from examining config files it should create it on SD card, and when I used my only fully working devkit it worked there, so I am planning to use it as flasher :) and try to use card on another module + baseboard
It would not work if you only flash qspi since there’s no rootfs yet.
Is there any issue if you use another SD card?
Yes. I had to use working BaseBoard to flash SD qspi-sd and then I could use it on the one which was not working (could not flash) but there is still original one which will not regognize SD card anyway
Do you mean that the current issue is specific to one devkit board which could not be flashed successfully?
If so, please share the full flash log for further check.
Honestly, I do not know what to share more, I’ve already shared a bunch of logs, nothing new.
All you shared is serial console logs.
I would suggest you put SD card on your devkit and use the flash command to flash your board.
During flash, there should be flash log showed on your host. Please share this log for further check.