Jetson Nano Fails to boot up

Hi all,

My Jetson nano was working fine but now when I plug in and turn on my Jetson nano I am met with a black screen and the following.

1.1764221 tegrado tegradc. 1: dpd enable lookup fail:-19

1.3300841 imx219 7-0010: imx219_board_setup: error during 12c read probe (-121)

1.3301541 imx219 7-0010: board setup failed

1.3539911 imx219 8-0010: imx219_board_setup: error during 12c read probe (-121)

1.354051] imx219 8-0010: board setup failed

1.7971001 EXT4-fs (mncbIkOp1): write access unavailable, cannot proceed
mount: /mnt: cannot mount /deu/mncb1k0p1 read-only.

bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
bash 4.4#

Any advice would be appreciated!

Hi talhabashir2000,

Are you using the devkit or custom board?
Is that eMMC or SD card version?

There’s a similar issue as yours.
Please refer the following link to check if it could help.
Jetson Bootup problem - tegradc.1 dpd enable lookup fail:-19, error during i2c read probe - #2 by mahesh.ksingh711

Hi I am using a devkit and the SD card version, I don’t have another SD card at the moment which means I could not use the solution outlined in the thread you linked, is there any other way to fix this?

You could re-flash the devkit through SDK Manager or flash script.

For SDK Manager, you should use a standalone Ubuntu 18.04 as your host PC and refer to the following instruction to flash your board.
Install Jetson Software with SDK Manager :: NVIDIA SDK Manager Documentation

For flash script, you could refer to the following instruction for detailed usage.
NVIDIA Jetson Linux Driver Package Software Features : Flashing and Booting the Target Device | NVIDIA Docs
In your case, the basic command would be the following:

$ sudo ./ jetson-nano-devkit mmcblk0p1

Is it possible to flash using a windows 11 PC, i don’t have access to a Linux OS system at the moment.

Some of the flash software is Linux binary executable, so Windows cannot execute that. Also, some Linux kernel services are required which is not present in WSL2. Someone once mentioned that there is some way to add this to WSL2, but it sounded “difficult” and not particularly well documented. Some VMs will work, but it is not officially supported because often a VM does not correctly recapture USB after a disconnect/reconnect. In the long run you’d be far less frustrated by a dual boot with Ubuntu 18.04.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.