Troubleshooting

1. Flashing JetPack

Issue	Resolution
NVIDIA APX not detected via `lsusb`	Try a different USB cable or USB port. Verify jumper is firmly placed on J7 pins 3 and 4.
Flash script fails immediately	Re-run `sudo ./tools/l4t_flash_prerequisites.sh` and ensure all dependencies are installed.
`apply_binaries.sh` reports missing files	Verify the rootfs was extracted into `Linux_for_Tegra/rootfs/` (not a subdirectory of rootfs/).
Flash stalls at rootfs copy	USB 2.0 ports are significantly slower. Use a USB 3.0 port on the host PC if available.
Board boots to recovery on every power-on	Remove the jumper from J7 pins 3 and 4 before powering on for normal boot.
`oem-config` not launching on first boot	Reconnect display. If headless, SSH to the board and run: `sudo/usr/sbin/oem-config-debconf`
NVMe not detected in `lsblk`	Ensure the NVMe SSD is correctly seated in the M.2 Key-M slot. Check that the M.2 retention screw is secure.

Debug Commands

To view detailed flash logs for diagnosis:

# View flash logs (on host PC during/after flashing)
cat ~/jetpack_flash/Linux_for_Tegra/logs/flash_*.log
 
# View kernel boot messages (on Jetson after first boot)
sudo dmesg | grep -iE 'error|warn|nvme|tegra'
 
# Check NVIDIA driver status
sudo dmesg | grep -i nvidia

2. Image Bringup — LVDS

Issue	Resolution
Jetson not detected via `lsusb`	Try a different USB cable or USB port. Ensure the jumper is correctly placed on J7(3rd and 4th pins).
Video node `/dev/video0` not found	Ensure the LVDS pin configuration was completed using jetson-io.py. Re-run the configuration if needed.
Black screen / no video output from GStreamer	Verify the CSI cable is connected to J13 Connector. Check that `rc.local` was executed successfully.
Flash script fails	Ensure all dependency packages are installed. Re-run apt install and try again.

Debug Commands

To view kernel-level debug messages related to the LT9211C driver:

sudo dmesg | grep -i lt9211c

Review the output for any error or warning messages. These logs can help identify initialization failures or communication errors.

3. Image Bringup — LVDS + MIPI

Issue	Resolution
Jetson not detected via `lsusb`	Try a different USB cable or USB port. Ensure the jumper is correctly placed on FC REC and GND.
Video node `/dev/video0` not found	Ensure the LVDS and MIPI pin configuration was completed using jetson-io.py. Re-run the configuration if needed.
Black screen or no output from GStreamer	Verify the Kel cable is connected to J13 and J18. Check that rc.local was executed successfully.
Flash script fails	Ensure all dependency packages are installed. Re-run apt install and try again.

Debug Commands

To view kernel-level debug messages related to the LT9211C driver:

sudo dmesg | grep -i lt9211c

Review the output for any error or warning messages. These logs can help identify initialization failures or communication errors.

4. Camera Power Guide

Issue	Resolution
GUI window does not open	Ensure `python3-gi` and GTK3 are installed: `sudo apt install python3-gi gir1.2-gtk-3.0`
Service fails to start	Check service file paths and GPIO permissions. Run `journalctl --user -u lvds-gpio.service` for details.
Camera not detected after selection	Confirm camera cable is seated firmly in the correct port (CAM0 for LVDS, CAM1 for MIPI).
Permanent mode not applied on boot	Ensure `display_pop_up.py` is added to the desktop autostart. Check `/opt/display-mode/permanent_mode` content.
Permission denied writing `permanent_mode`	Run the script with `sudo` or grant write permission to `/opt/display-mode/`.
Both cameras show no output	Verify power supply can support dual-camera load. Check both services are running with `systemctl --user status`.

Debug Commands

To view kernel-level debug messages related to camera GPIO and driver initialization:

sudo dmesg | grep -i gpio
sudo dmesg | grep -i camera
sudo dmesg | grep -i lt9211

5. Contact Support

If the issue persists after following all troubleshooting steps, please contact Oppila Microsystems technical support:

Email: support@oppila.in | Website: www.oppila.in