mmm okay – still not having great joy getting the Jetson booting up… new errors on display after a successful re-flash…
Failed to start: OP-TEE Client Supplicant
Failed to start: Rule-based manager for device events and files
// just looping between these two errors…
*** Please note that this reply is generated by LLM automatically ***
It seems like you’re experiencing issues with your Jetson AGX Orin device after a successful reflash. The errors you’re encountering, “Failed to start OPTEE Client Supplicant” and “Failed to start Rulebased manager for device events and files,” suggest that there might be some issues with the boot process or the configuration of your device.
To troubleshoot these errors, let’s break down what each of these services does and how they relate to the boot process:
OPTEE Client Supplicant: OPTEE stands for Open Portable Trusted Execution Environment. It’s a trusted execution environment (TEE) that provides a secure environment for executing sensitive code. The OPTEE Client Supplicant is responsible for managing the communication between the normal world (the Linux operating system) and the secure world (the TEE). If this service fails to start, it might indicate issues with the TEE configuration or the secure boot process.
Rulebased manager for device events and files: This service is likely related to the management of device events and files, possibly as part of the device’s security or access control mechanisms. If this service fails to start, it could indicate issues with the device’s configuration or the management of device events.
Given the nature of these errors, here are some potential steps you could take to troubleshoot the issue:
Verify the boot configuration: Ensure that the boot configuration is correct and that the device is set to boot from the correct device (e.g., the SD card or eMMC). You can check the boot configuration by editing the extlinux.conf file on the boot partition.
Check the TEE configuration: Verify that the TEE configuration is correct and that the OPTEE Client Supplicant is properly configured. You can check the TEE configuration by editing the tee.cfg file on the boot partition.
Verify the device tree: Ensure that the device tree is correctly configured and that it matches the hardware configuration of your device. You can check the device tree by editing the tegra194-p2888-0001-p2822-0000.dtb file on the boot partition.
Check for firmware updates: Ensure that the firmware is up to date, as outdated firmware can cause issues with the boot process.
Try a different boot mode: Try booting the device in a different mode, such as recovery mode or safe mode, to see if the issue persists.
Check the system logs: Check the system logs for any error messages that might indicate the cause of the issue.
Reflash the device: If none of the above steps resolve the issue, try reflashing the device again to ensure that the firmware is correctly installed.
In comparison to other Jetson devices, the Jetson AGX Orin series has a similar boot process and configuration. However, the specific configuration files and boot modes might differ. Therefore, it’s essential to consult the documentation specific to your device to ensure that you’re using the correct configuration files and boot modes.
If you’re still experiencing issues after trying the above steps, it might be helpful to provide more information about your device, such as the exact model number and the version of the firmware you’re using. Additionally, providing the full error messages and system logs can help to further diagnose the issue.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Which version of Jetpack did you flash ?
You filed this topic in Orin AGX forum. Are you sure this is what you are using now?
Actually didn’t hear any of this error log on a Orin AGX platform in the past few years. Do you have full error log to share?
Hi Wayne, yes this is for the Jetson AGX Orin unit…I’ll try to pull the error logs and attach…
The USB to TTL serial adapter got 4x connectors - not sure where they need to plug in (without damaging anything)
some dmesg stuffs:
[16542.302970] usb 1-3: new high-speed USB device number 17 using xhci_hcd
[16542.429025] usb 1-3: New USB device found, idVendor=0955, idProduct=7023, bcdDevice= 4.01
[16542.429039] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[16542.429043] usb 1-3: Product: APX
[16542.429047] usb 1-3: Manufacturer: NVIDIA Corp.
[16573.598625] wlp0s20f3: disconnect from AP 58:d9:d5:d3:fc:96 for new auth to 58:d9:d5:d3:fc:a6
[16573.642604] wlp0s20f3: authenticate with 58:d9:d5:d3:fc:a6 (local address=e0:c2:64:b5:cd:5e)
[16573.643483] wlp0s20f3: send auth to 58:d9:d5:d3:fc:a6 (try 1/3)
[16573.689856] wlp0s20f3: authenticated
[16573.691341] wlp0s20f3: associate with 58:d9:d5:d3:fc:a6 (try 1/3)
[16573.700233] wlp0s20f3: RX ReassocResp from 58:d9:d5:d3:fc:a6 (capab=0x1111 status=0 aid=2)
[16573.707697] wlp0s20f3: associated
[16573.724304] wlp0s20f3: Limiting TX power to 20 (20 - 0) dBm as advertised by 58:d9:d5:d3:fc:a6
Bus 001 Device 017: ID 0955:7023 NVIDIA Corp. APX
[17137.098003] usb 1-3: New USB device found, idVendor=0955, idProduct=7023, bcdDevice= 4.01
[17137.098017] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[17137.098021] usb 1-3: Product: APX
[17137.098024] usb 1-3: Manufacturer: NVIDIA Corp.
The above logs does not really tell you to which tty I need to connect to… according to some articles online this is the one, apparently → > /dev/ttyUSB0
Below I found some info after a Google search on how I am supposed to wire the 4x lose wires from the adapter cable to “somewhere” on the Jetson board – but there are so many “options” and not clearly marked … (I don’t want to just randomly plug cables in and see what happens - can’t risk damaging the unit…)
Wire the cable
Hi,
If this is a Orin AGX devkit, then you don’t need the usb ttl cable.
The micro usb port on the board is a integrated one that you could just connect micro usb cable from it to host for serial log.