So I’ve implemented serial using UART7 (uartg in the device tree) and made the tty device available according to this topic.
Furthermore, I’ve made the changes to the BPMP device tree so that it shouldn’t put debug information onto that serial port as per this topic.
The TX is working fine, but I am still seeing extra bytes interleaved into the RX line, driving the bus concurrently, and also when the external device isn’t trying to drive it. Am I missing something here?
SPE also uses uart7 for initial log, But once kernel tries to configure it for HSUART, it should be registered as ttyHS.
could you please share more details or logs to indicate your issue with RX for reference,
thanks
I’ve attached a loopback cable to the serial port and have the following logs from socat.
Note, in the following example, I sent
‘testing’
‘testing’
‘testing’
‘1234’
The rest of the messages were not sent from socat, and just appeared on the serial port.
# socat /dev/ttyTHS6,b115200,raw,echo=0 - testing testing testing testing testing testing 1234 1234 command not found command not found ] command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ] error: line too long command not found ] ]
I dug into the issue further, noting the similarities to the issue caused by the bpmp using the serial port, and have discovered that I changed the incorrect bpmp dtb file.
I was changing the one specified in the BPFDTB_FILE variable, which is given to the flash script through the jetson-tx2.conf file
(tegra186-a02-bpmp-quill-p3310-1000-a00-00-te770d-ucm2.dtb), where as it appears the flash procedure is flashing tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb to the partition.
Is there some explanation for why it is using a dtb file other than the one that is being specified in the configuration?
you should also look into general configuration file, p2771-0000.conf.common
there’s process_board_version() to check board versions, and it’ll replace BPFDTB_FILE according to your FAB values.
hence,
I would recommend for checking flashing messages to confirm the correct binaries.
thanks