1. Use the 27 W USB-C PD adapter shipped with the device.
2. If unavailable, power the DC terminal block from a 12 to 32 V supply (45 W minimum at full load).
3. Confirm wire polarity: Pin 1 = Chassis Ground, Pin 2 = DC Negative, Pin 3 = DC Positive.
4. Try a different USB-C cable. Long or low-quality cables often drop PD negotiation.

1. Replace the 5 V source with a 15 V USB-C PD adapter or a 12 to 32 V DC supply on the terminal block.
2. For long DC cable runs, prefer a 24 V adapter with thicker conductors to compensate for voltage drop.
3. Reboot after restoring nominal voltage so the PCIe bus re-enumerates.

1. Switch to a 45 W (15 V / 3.0 A) USB-C PD adapter or a DC supply sized for 45 W continuous.
2. Mount the device with the cooling surface facing up and leave at least 25 mm clearance in enclosed cabinets.
3. Verify with vcgencmd get_throttled that the CM5 is not hitting the under-voltage bit.

1. Disconnect all power from the device.
2. Move the SW1 switch to OFF to disable the hardware watchdog while you finish bring-up.
3. Reapply power and verify the device stays up. Re-enable the watchdog once your application actively pets it.

1. Plug a cable from ETHERNET 0 into an internet-connected router to give the device a known-good path.
2. Hand-tighten the two LTE antennas on the SMA connectors labeled L.
3. Wait two minutes. If still red, open the remote terminal or HDMI shell and run systemctl status sixfab-connect to inspect the agent.

1. Hand-tighten both antennas on the SMA connectors labeled L. Never connect the Wi-Fi antenna (RP-SMA male) to an LTE port.
2. Move the device near a window or use an external high-gain antenna.
3. Confirm the modem is attached and check signal quality:
   terminal shell

   mmcli -L
   mmcli -m 0 --signal-get

4. If the modem reports registered but throughput is low, switch carriers from the ALPON Cloud console.

1. Install the supplied Wi-Fi antenna on the RP-SMA male port labeled W.
2. Use WPA2-PSK or WPA3-Personal. Enterprise EAP profiles require extra setup via nmcli or Sixfab Connect.
3. Connect from Sixfab Connect (Connect to Wi-Fi), or over SSH:
   terminal shell

   nmcli device wifi list
   nmcli device wifi connect "YOUR_SSID" password "YOUR_PASS"

1. Use ETHERNET 0 for performance-sensitive traffic. It is the native CM5 Ethernet and the only PoE-capable port.
2. If you must use ETHERNET 1, avoid attaching high-bandwidth USB 3.0 devices to the shared hub.
3. Never connect a PoE source to ETHERNET 1. It does not accept PoE.

1. Use an IEEE 802.3at (PoE+) Class 4 injector or switch that delivers 37 to 57 V.
2. Connect PoE to ETHERNET 0 only. ETHERNET 1 cannot accept power.
3. Check the sticker on the enclosure; the PoE module is a factory option and cannot be field-added.

1. Verify you are running at 12 V DC or 15 V USB-C PD minimum. See Power and Boot.
2. Check the driver and PCIe enumeration:
   terminal shell

   lspci | grep -i deepx
   lsmod | grep dxrt
   ls -l /dev/dxrt*

3. If PCIe enumerates but the driver is missing, reinstall it:
   terminal shell

   sudo apt update
   sudo apt install --reinstall -y libdxrt

4. If lspci does not list the DEEPX device, power down, open the enclosure, and reseat the DEEPX DX-M1 M.2 module. Apply ESD precautions.

source /usr/lib/libdxrt/dxrt-venv/bin/activate
python -c "import dx_engine; print(dx_engine.__version__)"

For scripts, invoke the venv Python directly: /usr/lib/libdxrt/dxrt-venv/bin/python my_script.py.

Start the container with the device and --privileged:

docker run --rm --privileged   --device /dev/dxrt0   -v /opt/models:/models   alpon-infer:latest

For docker-compose, set privileged: true and devices: ["/dev/dxrt0"].

1. Recompile with a lower input resolution (for example 640×640 instead of 1280×1280).
2. Switch to a lighter model variant (nano or small instead of large or x).
3. Quantize or prune the model before re-exporting to ONNX, then recompile with dx-com.

1. Recompile the ONNX graph with PPU enabled:
   terminal (host PC) shell

   dx-com --ppu -i yolov8n.onnx -o yolov8n.dxnn

2. Redeploy the resulting .dxnn. PPU-compiled nano-class YOLO models reach roughly 50 FPS at 1280×720 and 20 to 25 FPS at 1920×1080.
3. Monitor with dxtop to confirm the NPU is saturated rather than the CPU.

1. Switch to a CNN-based equivalent (YOLOv5/v7/v8, SSD, ResNet, MobileNet, EfficientNet, U-Net).
2. If you must keep a transformer head, run it on the CM5 CPU and offload only the CNN backbone to the NPU.
3. Check the DEEPX release notes for the current supported-operator list before compiling.

1. Connect with the correct user: ssh alpon@<DEVICE_IP> or ssh alpon@alpon-<MAC>.local.
2. If the local network is unreachable, use the browser-based remote terminal in Sixfab Connect. It works even when only cellular is up.
3. As a last resort, attach HDMI and a USB keyboard for local login.

1. Open the Sixfab Connect remote terminal. It authenticates through the cloud agent and does not require your local password.
2. From that shell, run sudo passwd alpon to set a new password.
3. If the remote terminal is unreachable and you have no HDMI access, contact Sixfab support with the device serial number for a recovery procedure. Do not attempt to re-flash the eMMC without guidance.

# Verify connectivity first
ping -c 3 deb.debian.org
 
# Repair any half-configured packages
sudo dpkg --configure -a
sudo apt -f install
 
# Refresh and retry
sudo apt update
sudo apt upgrade -y

If a repository's GPG key is missing, reinstall it from the Sixfab or DEEPX documentation before running apt update again. Reboot when a kernel or firmware package was upgraded.

1. Plug HDMI before powering on. Hot-plug detection is best-effort on the CM5.
2. Use a certified HDMI cable and a monitor that supports 1080p at 60 Hz.
3. If the monitor stays blank, verify over SSH that the device booted, then reboot with HDMI already connected.

1. Check the LED legend above. If the Cellular LED is red, fall back to Ethernet by plugging ETHERNET 0 into a wired router.
2. From a local shell, inspect the agent:
   terminal shell

   systemctl status sixfab-connect
   journalctl -u sixfab-connect -n 200

3. If the agent is stuck, restart it:
   terminal shell

   sudo systemctl restart sixfab-connect

1. In Sixfab Connect, choose Manual registration.
2. Enter the serial number printed next to the QR code.
3. Follow the on-screen prompts to bind the device to your organization.

1. Confirm the device is Online and the Sixfab Connect agent is healthy.
2. Rebuild your image for arm64: docker buildx build --platform linux/arm64 -t my-image .
3. Check available disk with df -h /. Prune unused images: docker image prune -a.