Hi all,
I flashed the jetpack package to SD Card.
My monitor doesn’t support HDMI and I pulgin a Convertor to Convert HDMI to VGA, but in this way, Jetson nano doesn’t any disply, I before tested without convertor and I conected the HDML directly to monitor, it’s work. now I monitor dosen’t support HDMI, I want to configure the username and pass using SSH. How I solve the problem?
If you don’t have Hdmi monitor to configure user account, you could connect the micro usb cable to nano and open /dev/ttyACM0 to use oem-config.
Sorry, I’m new in this work, your mean that I must connect micro usb power then connect to nano with ssh from host system, right? I don’t oem-config, please guaidance me. thanks
No, not ssh. Please use some tools like minicom or picocom to open the device (/dev/ttyACM0) on your host.
I installed minicom and my jetson is connected to local Lan cable and mico usb power, it’s ok? if so, what do I do then? I typed the dmesg | grep tty then get these results:
[ 0.000000] console [tty0] enabled
[ 0.733719] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[198827.863753] cdc_acm 1-12:1.2: ttyACM0: USB ACM device
Hi,
Do you know how to use minicom to open /dev/ttyACM0?
Please try to search usage of minicom over the internet.
Yes I install minicom and opencv /dev/ttyACM0, but I have some problem,
To re-enable oem-config manually on an SD card
1.Select a source device of the same type as the target device(s) on which all necessary packages have been installed.
2.Enter this command to install the following packages on the source device to enable oem-config for the next reboot: ubiquity, oem-config, and oem-config-gtk:
$ sudo apt-get install --no-install-recommends ubiquity oem-config oem-config-gtk
3.Remove the package nvidia-l4f-oem-config:
$ sudo dpkg --purge nvidia-l4t-oem-config
11.Power off the source device and remove the SD card from it, then insert it into in the host system.
12.Mount partition #1 of the SD card (an ext4 filesystem) on the host, using a mount point of your choice.
13.Apply any Jetson-specific binaries to partition #1 of SD card. The appropriate files are listed in nv-oem-config, and are applied by the apply_binaries script. Enter these commands to run the script:
$ cd Linux_for_Tegra
$ sudo ./apply_binaries.sh -r
Where represents the partition #1 of SD card mount point.
14.Set nv-oem-config.target as the default.target:
$ cd $root/etc/systemd/system
$ sudo rm default.target
$ sudo ln -s /lib/systemd/system/nv-oem-config.target default.target
15.Run jetson-disk-image-creator.sh to create a new SD card image with modified rootfs:
$ cd Linux_for_Tegra/tools
$ sudo ROOTFS_DIR= ./jetson-disk-image-creator.sh -o sd-blob.img -b jetson-nano -r 100
Where represents partition #1 of the SD card on its mount point. For details, see To generate an image to be flashed to an SD card.
16.Enter this command to unmount the device mounted in step 11:
$ umount $root
17.Flash sd-blob.img to the new SD card. For details, see Flashing to an SD Card.
I have problem in the mount SD car on hosy sytem and I don’t know in the step 13, cd Linux_for_Tegra where this directory?
Linux_for_Tegra is the driver package that could be installed by either sdkmanager or direct download from our download center.
You could try sdkmanager first if you are new to such tools. Please note that you need to have a 18.04/16.04 ubuntu host for this tool.
Thanks, I don’t know before I done this work with SDK mangaer and jetson was launched but cause conflict in my host system package like cuda , …