I’m working on our custom carrier board with TX2 NX SOM. When I test the RS232 connection, the TX2 NX can send messages correctly but it can not receive (messages returns back to the host).
Additionally, while TX2 NX’s RS232 connection confirmed and rebooting, some messages received to the host PC like that:
welcome to lk adc initialized chip_revision initialized speedo initialized dt initialized clk_init_mrq: mrq handler registered 383 clocks registered clock initialized reset initialized i2c5 controller initialized i2c10 controller initialized initialized i2c mrq handling i2c initialized thermal initialized fuse initialized soctherm initialized aotag initialized cvc initialized regulator initialized dvs initialized t186_dvs initialized pm initialized tegra186_reset initialized uart initialized sku_init: not sku 00 sku initialized modules initialized tag initialized avfs_clk_platform initialized parse_possible_parent_table: pllp_bb not in allowed parent table for axi_cbb clock_dt initialized powergate initialized avfs_gpu initialized clock_gpu initialized debugfs_mrq initialized emc initialized gpmu2bpmp initialized mc_init_mrq: mrq handler registered mc initialized pg_mrq initialized pg_legacy_mrq initialized pm_post initialized ppm initialized uphy_dt initialized uphy initialized mrq initialized tag is 91572a54614f84d0fd0c270beec2c56f tag_lateinit initialized clock_debugfs initialized thermal_test initialized avfs_clk_platform_post initialized avfs_debugfs initialized clock_pto initialized cvc_dt initialized debugfs_cons_init initialized dvs_debugfs initialized rm initialized edp initialized gboost initialized powergate_debug initialized regulator_post initialized sku_debugfs initialized speedo_debugfs initialized soctherm_debug initialized aotag_hsm initialized sc7_diag initialized starting app shell entering main console loop ]
I have also tested with Xavier NX and Nano (Jetpack 4.5.0) but I have not seen these messages before. Has anyone encountered this before?