I have my new carrier booting now, but here is my situation:
The thing I dd to get it to boot was to remove the Type C configuration from the device tree. Before it was removed, on a carrier that had Type C, it would boot and the Debug Uart would bring up the dialog to setup the language, etc. It would interact and I would eventually get a prompt. On the new carrier without the Type C, it gets to the place that says:
Please complete system configuration setup on the serial port provided by Jetson’s USB device mode connection. e.g. /dev/ttyACMx where x can 0, 1, 2 etc.
And stops.
The only difference is the removal of the Type C as descibed in the Adaptation guide. Any ideas?
I am loading 36.4.3. I have 2 types carriers. One is being debugged, the other is a working 3rd party carrier. The 3rd party carrier has 2 USB Type C connectors. When I bring up the module on that carrier with my config files, it boots into the headless display configuration screen. When I put the module on my new carrier, it crashes in UEFI due to the non-existent type C port. When I follow the guidance to remove the USB Type C, then it doesn’t crash and finishes booting, but it never goes to the Welcome screen. It does this regardless of which carrier I am using.