Jetson Nano failing to start, nothing on screen, LED on

@WayneWWW Hi again… yes, thanks for the tip. I guessed adding .sh to access the file directly would solve the problem. Yet, doesn’t help at the end. I am not 100% sure if the name I used is correct - how do you get the list of possible devices!? I tried different things:
-from your list: P3448, Jetson Nano devkit (in quotes), Jetson-Nano-devkit, maybe…
-looked in the conf files and went for p3448-0000. Guessing it is the correct ID, since it didn’t come with “Invalid target board”…
So… I used “sudo ./flash.sh p3448-0000 mmclkb0p1” and didn’t get the “invalid target name” but “invalid target rootdev(mmclkb0p1)”. Yet, it seem to be correct (since following help “rootdev for t210ref:” is listing this as the external SDCARD/eMMC.

If using the sdkmanager GUI, it just cannot find the board, using automatic or manual settings. It keeps on failing/trying, and giving the following message in red:
“Could not detect Nvidia Jetson device connected to USB. Verify that: 1. is connected to this host machine with a USB cable. 2. Jetson’s Ubuntu OS is up and running. 3. Ubuntu ‘System configuration wizard’ is completed on the device. This can be validated by running the ‘lsusb’ command on your host, and look for “0955:7f21” (NVIDIA Corp). Or use the ‘Manual Setup’ instead.”

It makes sense since Jetson’s Ubuntu OS is not up and running, but the board stuck before even starting anything.

To confirm starting in recovery mode, I have been following your instructions from another thread (see previous posts) to start the board.

Using barrel power supply (5V, 2.5A):
-connect pins on J48
-connect recovery pins (3 & 4) on J40
-connect reset pins (5 & 6)
-plug power supply
-remove reset’s jumper
-remove recovery’s jumper…

Using USB only:
-no J48 jumper.
-jumper on recovery (3 & 4) J40
-plug USB
(-remove jumper)

The thing is that no device shows up either way, using power supply or USB only. Neither USB (lsusb) or disk (blkid). No new device shows up in /dev when I connect the board.

The state is still the same: using USB power, nothing happen, but LEDs are on (power and both green and orange on Ethernet). Using power supply, nothing happen at all (no LED turns on).

Hi,

Sorry I didn’t notice your previous command has 2 typos and fixed only the first one…
It is “mmcblk0p1”. You have another typo.

Actually, we have lots of document on download center. You could check the quick start guide on nano.

Also, the board name. If you are using the nano from devkit, then please use jetson-nano-qspi-sd.

sudo ./flash.sh jetson-nano-qpsi-sd mmcblk0p1.

and it seems you are not putting the device into recovery mode…

It does not matter you are using barrel power supply or usb. Take barrel power as example.

  1. connect the micro usb cable on your nano devkit to host.
  2. connect pins on J48 to make sure it is using barrel power as source
  3. -plug power supply
  4. -connect recovery pins
  5. -connect reset pins
  6. “remove the reset pins”
  7. “remove he recovery pins”
  8. check the lsusb command on your host.

@WayneWWW

Hi again. Well spotted, about the typo… even if I checked the correct name in the help prompts of the flash.sh, I just could not make the difference… you may want to update your tutorial (https://elinux.org/Jetson/General_debug) because it is -obviously- quite misleading. I copied and pasted the line from your example to make sure I would actually not make a typo…

The given name (jetson-nano-qpsi-sd) desn’t seem to work. Seem this is my turn to spot a typo… from the flash.sh:

"if [[ “${ext_target_board}” == “jetson-nano-qspi” ||*

  • “${ext_target_board}” == “p3448-0000” ||*
  • “${ext_target_board}” == “p3448-0000-sd” ]]; then*"

Yet, if fixing both target board and device, now the the error is: probing the target board failed.

Using power supply or not, following carefully the order of adding and removing jumpers, the board is just dead when using J48 and power supply, and stuck with LEDs on when using USB power. Nothing blinks or changes when adding/removing recovery’s jumpers (except LEDs are of when reset jumper is on, using USB power).

Nothing shows up in the lsusb listing. No new device shows up in /dev.

Many thanks and sorry for this. I just updated the page.

Also, one more question, could you flip over your devkit and see whether your board is A02 or B01?

@WayneWWW

You may want to check previous reply again. I was editing while you posted that… not that it is changing the outcome.

What do you mean by flip over the devkit? Checking the silk print underneath? Ha, I see the rev print now. It is A02 (from the line 180-13449-DAAF-A02). Only one camera port (I would have ordered B01 if knew there would be two available! The project I want to work on involve stereo vision)…

If your command is correct, but the board is not in recovery mode, it will show below.

~/nvidia/nvidia_sdk/JetPack_4.3_Linux_P3448/Linux_for_Tegra$ sudo ./flash.sh jetson-nano-qspi-sd mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 3.1
###############################################################################
Error: probing the target board failed.
       Make sure the target board is connected through 
       USB port and is in recovery mode.

Thus I think your command is correct. And if you are using a A02 board, then your steps to put device in recovery mode are also right.

Unfortunately I think this board is broken. Please file the RMA request to let the customer service help you.
Recovery mode is not decided by software but only hardware. If recovery mode cannot be entered, then it is hardware issue.

BTW, You can still try the recovery mode steps few times before RMA. It is a little tricky so maybe trying more times would really confirm the board is dead.

Sometimes other forum users make it work by changing to other micro usb cable too…

@WayneWWW

Yes, the error message is the one I received… I’d agree, think the command is correct. I have repeated the recovery steps a few time already, and doubt I could not make it correctly in the lot. Yet, I’ll try again with another cable, in case.

It seem obvious to me that the board isn’t starting at all. Shouldn’t the power LED blink at some stage, when starting/entering recovery mode? I just cannot remember exactly but find it really suspicious it remains so constantly on (on USB power) or off (J48).

Anyway… to me, the main clue is that nothing ever shows up when connecting to the computer. Shouldn’t the device be showing up in /dev when connected, even if not in recovery mode (to know if I can confirm it is able to connect with or without entering it - in case I do it wrong)?

If the device is not in recovery mode, the cable will not recognize the device as a usb device, so /dev will have nothing.

Thus, checking lsusb should be sufficient. You could refer to the Jetson Nano Developer Kit User Guide in the download center for the detail about the recovery pins.

Hello @WayneWWW,

Well, could not say if I did everything correctly, but tried again today without success.

Using USB power, J48 and power supply. Different USB cables, tested for power and data… thinking I’ll give up and contact support to fill in RMA.

Thanks for your time and attention. Maybe a last question?.. about the power LED (disregarding the ethernet port’s). Should it turn on when the board is powered through J48 (barrel and power supply)?

Guessing jumper over reset pins would turn it off, but then turn on again when removing it? Any specific behaviour with the recovery pin on or off?

In my case, nothing happens anyway:

  1. LED is on when powered with USB, off when reset is on, come back on when reset off. Jumper over recovery don’t even make it blink.
  2. LED is off when powered through barrel. Nothing is even only making it blink.
  3. no matter power used, connected screen remain off (showing inbuilt “no signal” message).

The power led will turn on when power supply is connected. Please go ahead for RMA.

Hello @WayneWWW,

As I thought… the LED don’t even blink when powered from barrel, no way to get anything happening.

Anyway. Just back from live chat and all good. Waiting for news from the replacement team.

Cheers!