which exactly command to execute to see correct output?
Hm, I noticed that even if I power OFF/ disconnect the power cable, but then touch the NX module the sequence of the input continues perhaps due to electromagnetic input/sink from touch
first make sure you have minicom installed.
apt install minicom if it is not already there.
The following list of arguments can be used to alter minicom’s behavior from the command line:
The serial port baud rate used by the external device–typically a SOM.
The device name for the serial port being used.
Show a list of arguments that minicom accepts
So you need to know what serial port you are using on you collecting machine, Again if you are using TTL serial ports make sure voltages match.
If you just type in minicom
you get a window where you can set up all of your setting for that port and use it as your default connection.
you can check serial ports using
Down the bottom of the list will be the ones you are interested in .
Check with the tegra documentation to find which pins correspond to which ports you should use, so the physical connections.
once you have TX - RX for each machine and reverse you will be able to set everything from within minicom by selecting that port.
It just depends what ports you want to connect and having the wires or jumpers leads t hook up.
From what you displayed before it looks like a framing error or speed setting is wrong. choose the speed to match the NX device. Likewise the stop bits and parity. Just the same as if you were using a usb to serial TTL cable.
It could of course just be electrical noise, but it does not look like that.
what machine are you using as a data collector? I have forgotten?
The other thing is to make sure there is a common ground.
Often does not matter, but is more correct and may stop voltages from floating about and reduce “noise”.
So you should have a ground pin 9 to pin 9
All I can think of at the moment.
were the output the same each time you started the NX?
[J14]: 12-pin button header. Brings out system power, reset, force recovery, UART
console, and other signals:
• Pin 1 connects to LED cathode to indicate System Sleep/Wake (Off when system
is in sleep mode).
• Pin 2 connects to LED anode.
• Pins 3 and 4 are respectively UART Receive and Send.
• Pins 5 and 6 disable auto power-on if connecte
according to Jerry Chang:
there’re 3 UARTs available on Xavier NX,
UART0 to M2
UART1 to 40PIN
UART2 to debug
So what you want is pin 4 (TX) on J14 NX to be connected to pin to RX pin of AGX devkit [ 10 of 40 pin header]
Then use /dev/ttyTHS1 on the xavier with mincom or gtkterm,
setting appropriate speed, stop bits and parity.
He’s replacing a UART in cable with the Xavier. The Xavier is just used as a UART TX/RX/GND, and can pretend the Xavier is just a host PC with the serial terminal reading the Xavier’s UART (no USB cable required, just twisted pair wire plus ground). Assumes the 40-pin header pins 8 and 10 of the NX are serial console.
That’s something I couldn’t answer. Possibly through manipulation of boot environment variables since they can do macro expansion (at least on most releases…not sure if the newer UEFI has macro expansion).