My sd cards with ubuntu inside don't boot anymore

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

Hello to everyone.

During the last 3 days I tried to boot my nano again,but it always failed. I have two sd cards. The first one is 200 GB large ; the second one is 120 gb large. I’ve used the first one for a long time booting the nano from USB and it always worked. I have written on both the sd cards the “jetson-nano-jp461-sd-card-image-b01.img” img file using dd. I have always used the kiwibird sd card to usb adapter,for the first and the second one without problems. But on the last 3 days the situation changed. Im not able anymore to boot the sd cards. No matter what I do,they won’t boot. Below you can read the log captured by minicom :

U-Boot 2020.04-g4335beb (Nov 22 2022 - 09:21:37 -0800)                                    
                                                                                          
SoC: tegra210                                                                             
Model: NVIDIA Jetson Nano Developer Kit                                                   
Board: NVIDIA P3450-0000                                                                  
DRAM:  4 GiB                                                                              
MMC:   sdhci@700b0000: 1, sdhci@700b0600: 0                                               
Loading Environment from SPI Flash... SF: Detected mx25u3235f with page size 256 Bytes, eB
*** Warning - bad CRC, using default environment                                          
                                                                                          
In:    serial                                                                             
Out:   serial                                                                             
Err:   serial                                                                             
Net:   No ethernet found.                                                                 
Hit any key to stop autoboot:  0                                                          
MMC: no card present                                                                      
Card did not respond to voltage select!                                                   
starting USB...                                                                           
Bus usb@7d000000: tegrausb: Invalid dr_mode 2 for host mode                               
probe failed, error -1                                                                    
Bus xusb@70090000: Loading XUSB FW blob from RP4 partition ...                            
SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB           
                                                                                          
Firmware size 126464                                                                      
Firmware timestamp: 0x5f23e558, Version: 50.26 release                                    
                                                                                          
Register HCSParams1: 9000124 NbrPorts: 9                                                  
Starting the controller                                                                   
USB XHCI 1.00                                                                             
scanning bus xusb@70090000 for devices... 2 USB Device(s) found                           
       scanning usb for storage devices... 0 Storage Device(s) found                      
                                                                                          
Device 0: unknown device                                                                  
                                                                                          
Device 0: unknown device                                                                  
No ethernet found.                                                                        
missing environment variable: pxeuuid                                                     
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/00000000                                                    
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/0000000                                                     
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/000000                                                      
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/00000                                                       
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/0000                                                        
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/000                                                         
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/00                                                          
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/0                                                           
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/default-arm-tegra210-p3450-0000                             
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/default-arm-tegra210                                        
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/default-arm                                                 
No ethernet found.                                                                        
missing environment variable: bootfile                                                    
Retrieving file: pxelinux.cfg/default                                                     
No ethernet found.                                                                        
Config file not found                                                                     
No ethernet found.                                                                        
No ethernet found.                                                                        
Tegra210 (P3450-0000) #

I don’t understand what’s the error.

3

Hi,
does directly putting the card onto the Micro SD card slot on the device make any changes?
Can you first verify if your card and card reader are good on other PCs?
I’m not sure what’s the purpose of using an USB adapter when you already have a SD card slot.

4

Hello.

yesterday I tried a lot of time to boot the board using only the sd card. It never booted and the error is never gone away. I’ve also removed every USB devices attached to the board to be sure. I have detached keyboard,mouse,and the sdcard to usb adapter,keeping only the sd card slot attached,but I haven’t been able to remove that error. Is that an hardware error ? I’ve tried to boot it via usb because the board it was rarely able to boot through the sd card. It worked like this from the very beginning. To boot it through the sd card I should detach and reattach the slot a lot of time,until it fits well under the plate and at the end,after a lot of tries,it will boot. I’m sad. I’m scared that my board is broken forever. Please help me. Can / should I hardly reset the board ?

5

Just one question here. Have you tried to flash the device with sdkmanager?

This is to make sure those bootloader software to get cleaned up and reset. If you just keep using sdcard, usb boot. Then it cannot reset your bootloader.

6

I didn’t know that. I thought that it was enough to write the official “jetson-nano-jp461-sd-card-image” to the sd card using the “dd” command from the terminal. So,should I dedicate a whole disk to Ubuntu 18.04 if I want to flash the device with the sdkmanager ? Or is it enough to install Ubuntu 18.04 as a virtual machine ?

7

VM is not guaranteed. Some users have their trick to make it work. But we don’t officially support VM.
Better finding a native x86 ubuntu host.

8

When I flash the sd card with the SDK manager should I keep the barrell jack connected to the board ?

9

Yes, you need. And you need to follow the developer kit user guide document to put the board into recovery mode. The board can only get flashed when it is in recovery mode.

10

Hello.

as indicated by the manual,to put my board (model B01) in recovery mode,I should close jumper 9 and 10. I did it. At the same time,I’ve connected the mini usb cable from the board to the PC and I ran the SDK manager on ubuntu 18.04 installed phisically. Unfortunately,it says that It can’t detect the board. I’ve attached the screen below :

Istantanea_2023-05-13_19-12-36
Istantanea_2023-05-13_19-12-36497×883 51.5 KB

Istantanea_2023-05-13_18-55-55
Istantanea_2023-05-13_18-55-551431×826 161 KB

On ubuntu 18.04 :

# lsusb | grep -i nvidia
nothing.

it is not detected even if I see the yellow led that turns on when I attach the usb cable from the board to the PC. What happens ? Where is the error ? thanks.

PS : (the colored wires which enable the serial console aren’t attached to the USB port of my PC)

11

Hi,
your picture is not quite clear, and it’s hard to tell if the jumper is placed correctly. Are you sure the two pins are connected together using the jumper?
image
Use one like this.

12

I have closed the pin called “GND” and the pin called “FC REC”. “GND” is the number 9 and “FC REC” is the n. 10.

Istantanea_2023-05-13_19-23-41
Istantanea_2023-05-13_19-23-411920×1080 149 KB

the picture is pretty clear.

13

Hello. Can you click on the image to zoom it ? it will not infect your pc with a virus. I’m in trouble here. I’m not able to put the board in recovery mode. Do you have any idea about why it does not work ? can you give me a little bit more support ? Thanks.

14

Hi,
I mean they have to be connected “together”… From the picture, it seems like you just put two individual covers on the FC REC pin and the GND pin, which is not going to have any effect on enabling force recovery mode.
Am I wrong here?

15

One question here. Did you remember to connect the power jack after you put jumper on recover pin. Your 1st picture shows the power cable is still not connected.

16

no. I used one jumper to cover pins 9 and 10. This jumper :

WhatsApp Image 2023-05-14 at 13.08.24
WhatsApp Image 2023-05-14 at 13.08.241152×2048 405 KB

and yes,I have attached also the power jack. One question here : do I need to use two jumpers to put the board in recovery mode ? The first jumper should be placed to cover the two pins that you see below ?

WhatsApp Image 2023-05-14 at 13.11.34
WhatsApp Image 2023-05-14 at 13.11.341152×2048 291 KB

it seems to be needed to power on the board using the barrell jack. If those two pins aren’t covered,power does not come to the board. So,a jumper goes there and another jumper is used to cover pins 9 and 10 ? is that right ? because at the moment I’m covering only pins 9 and 10,not the two pins that you see on the picture and I see that the board is powered only by the usb cable,but probably the amount of power it gets is not enough. Actually I have only one jumper available. I need to buy more.

17

That I need to use 2 jumpers is confirmed also here :

where it says :

  • Ensure that the Jetson Nano is powered off. There is no need for the SD card/USB storage/network cable to be connected
  • Connect the micro USB cable to the micro USB port on the Jetson Nano, don’t plug the other end to the PC yet
  • Enable Force Recovery Mode (FRC) by placing a jumper across the FRC pins on the Jetson Nano
    • For board revision A02, these are pins 3 and 4 of header J40
    • For board revision B01, these are pins 9 and 10 of header J50
  • Place another jumper across J48 to enable power from the DC jack and connect the Jetson Nano to the DC jack J25
  • Now connect the other end of the micro USB cable to the PC and remove the jumper wire from the FRC pins

what I don’t understand is this sentence :

There is no need for the SD card/USB storage/network cable to be connected.

Do I need to do the same in my case ?

18

You need sdcard conncted. That article is not doing the same thing as what you are going to do. Please only refer to its steps for recovery mode.

When it comes to flash, just let sdkmanager do the rest of part.

1 Like
19

There are some confused points on the whole process. The fact that,when I connect the USB cable to the PC and I see the yellow light turn on,it let me think that the board is already powered. And even the fact that,when I plug in the barrell jack into the hole,the yellow light does not turn on because it is already turned on. In short terms,a newbie does not understand well what he should do,which cables should be connected,which lights should be turned on,and so on. And above all that we need to use two jumpers. This should not be taken for granted. I’m not sure that the confusing point is very well explained on the official nvidia instructions. But maybe I’m wrong. About one thing I’m sure : the explanations I found on the talos.dev website are very good,really accurate. My advice is to improve your instructions,making them more clear,like the talos.dev ones.

20

Hi,

You can read developer kit guide document. There is another pin on the carrier board to tell which power supply to be used.

One case is power supplied by the micro usb. And another case is powered by the power jack.

22

ok I did what suggested. It didn’t work :

[  918.297557] usb 1-13.3: new full-speed USB device number 14 using xhci_hcd
[  918.385569] usb 1-13.3: device descriptor read/64, error -32
[  918.581570] usb 1-13.3: device descriptor read/64, error -32                                     
[  918.769556] usb 1-13.3: new full-speed USB device number 15 using xhci_hcd
[  918.857567] usb 1-13.3: device descriptor read/64, error -32
[  919.045885] usb 1-13-port3: attempt power cycle
[  919.649575] usb 1-13.3: new full-speed USB device number 16 using xhci_hcd
[  919.674269] usb 1-13.3: not running at top speed; connect to a high speed hub
[  919.675298] usb 1-13.3: New USB device found, idVendor=0955, idProduct=7f21, bcdDevice= 1.02
[  919.675300] usb 1-13.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  919.675301] usb 1-13.3: Product: APX
[  919.675303] usb 1-13.3: Manufacturer: NVIDIA Corp.
[  933.946083] usb 1-13-port3: disabled by hub (EMI?), re-enabling...
[  933.946377] usb 1-13.3: USB disconnect, device number 16
[  934.169501] usb 1-13.3: new full-speed USB device number 17 using xhci_hcd
[  934.257515] usb 1-13.3: device descriptor read/64, error -32
[  934.453517] usb 1-13.3: device descriptor read/64, error -32                                     
[  934.641499] usb 1-13.3: new full-speed USB device number 18 using xhci_hcd
[  934.729510] usb 1-13.3: device descriptor read/64, error -32
[  934.925860] usb 1-13-port3: attempt power cycle
[  935.737511] usb 1-13.3: new full-speed USB device number 19 using xhci_hcd
[  935.758203] usb 1-13.3: not running at top speed; connect to a high speed hub
[  935.759215] usb 1-13.3: New USB device found, idVendor=0955, idProduct=7f21, bcdDevice= 1.02
[  935.759221] usb 1-13.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  935.759224] usb 1-13.3: Product: APX
[  935.759227] usb 1-13.3: Manufacturer: NVIDIA Corp.
[  935.993998] usb 1-13-port3: disabled by hub (EMI?), re-enabling...
[  935.994272] usb 1-13.3: USB disconnect, device number 19
[  936.217487] usb 1-13.3: new full-speed USB device number 20 using xhci_hcd
[  936.305497] usb 1-13.3: device descriptor read/64, error -32
[  936.501507] usb 1-13.3: device descriptor read/64, error -32                                     
[  936.689490] usb 1-13.3: new full-speed USB device number 21 using xhci_hcd
[  936.777503] usb 1-13.3: device descriptor read/64, error -32
[  936.977433] usb 1-13.3: device descriptor read/64, error -32                                     
[  937.081811] usb 1-13-port3: attempt power cycle
[  937.685487] usb 1-13.3: new full-speed USB device number 22 using xhci_hcd
[  937.688474] usb 1-13.3: Device not responding to setup address.
[  937.896497] usb 1-13.3: Device not responding to setup address.
[  938.101491] usb 1-13.3: device not accepting address 22, error -71
[  938.181486] usb 1-13.3: new full-speed USB device number 23 using xhci_hcd
[  938.184491] usb 1-13.3: Device not responding to setup address.
[  938.392506] usb 1-13.3: Device not responding to setup address.
[  938.597494] usb 1-13.3: device not accepting address 23, error -71
[  938.597841] usb 1-13-port3: unable to enumerate USB device                                       
[ 1147.420783] usb 1-13-port3: Cannot enable. Maybe the USB cable is bad?
[ 1148.272778] usb 1-13-port3: Cannot enable. Maybe the USB cable is bad?
[ 1148.273095] usb 1-13-port3: attempt power cycle
[ 1149.440757] usb 1-13-port3: Cannot enable. Maybe the USB cable is bad?
[ 1150.292756] usb 1-13-port3: Cannot enable. Maybe the USB cable is bad?
[ 1150.293074] usb 1-13-port3: unable to enumerate USB device
[ 1197.596386] usb 1-13-port3: Cannot enable. Maybe the USB cable is bad?
[ 1243.440037] usb 1-13-port3: Cannot enable. Maybe the USB cable is bad?
[ 1247.252029] usb 1-13-port3: Cannot enable. Maybe the USB cable is bad?
[ 1327.638948] usb 1-13.3: new full-speed USB device number 39 using xhci_hcd
[ 1327.726958] usb 1-13.3: device descriptor read/64, error -32
[ 1327.922961] usb 1-13.3: device descriptor read/64, error -32
[ 1328.110951] usb 1-13.3: new full-speed USB device number 40 using xhci_hcd
[ 1328.198956] usb 1-13.3: device descriptor read/64, error -32
[ 1328.394955] usb 1-13.3: device descriptor read/64, error -32
[ 1328.503263] usb 1-13-port3: attempt power cycle
[ 1329.106938] usb 1-13.3: new full-speed USB device number 41 using xhci_hcd
[ 1329.109772] usb 1-13.3: Device not responding to setup address.
[ 1329.317779] usb 1-13.3: Device not responding to setup address.
[ 1329.522931] usb 1-13.3: device not accepting address 41, error -71
[ 1329.602934] usb 1-13.3: new full-speed USB device number 42 using xhci_hcd
[ 1329.605769] usb 1-13.3: Device not responding to setup address.
[ 1329.813766] usb 1-13.3: Device not responding to setup address.
[ 1330.018949] usb 1-13.3: device not accepting address 42, error -71
[ 1330.019269] usb 1-13-port3: unable to enumerate USB device

I tried two different USB cables.