We refer to x and enable the use of UART 4/UART TD, but it does not work. Please assist in analyzing the reason. Complete the following steps:
Configure the pins of UART TD
bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
Delete the reuse of rx and tx
platform/t23x/concord/kernel-dts/cvb/tegra234-p3737-fixed-regulator.dtsi
Testing
The problem has been resolved because the configuration of two files, bootloader/t186ref/BCT/tgra234-mb1-bct-pnmux-p3701-0000-a04.dtsi and bootloader/tegra234-mb1-bct-gpio-p3701-0000.dtsi, was not successfully burned to SPI flash. After manually configuring the registers, it was successful.
busybox devmem 0x02434020 w 0x400
busybox devmem 0x02434018 w 0x450
busybox devmem 0x02434010 w 0x400
busybox devmem 0x02434008 w 0x450
May I ask how to burn the modified bootloader/t186ref/BCT/tegra234-mb1-bct-pnmux-p3701-0000-a04.dtsi and bootloader/tegra234-mb1-bct-gpio-p3701-0000.dtsi to SPI flash?
hello 1712127445,
basically, you should re-flash the board completely to apply pinmux changes.
here’re steps in brief for you reference.
(1) Generate device tree files and name them as pinmux.dtsi and gpio.dtsi (remember to modify the #include in pinmux.dtsi for gpio.dtsi)
(2) Put pinmux/gpio device trees to correct path
pinmux.dtsi in <Linux_for_Tegra>/bootloader/t186ref/BCT/
gpio.dtsi & padvoltage in <Linux_for_Tegra>/bootloader/
(3) Modify the following line in <Linux_for_Tegra>/p3701.conf.common
- PINMUX_CONFIG="tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi";
+ PINMUX_CONFIG="pinmux.dtsi";
(4) Flash the board to apply the change
you may refer to developer guide, Changing the Pinmux as see-also.
Question 1：
Can the command “./flash.sh -r -k A_cpu-bootloader jetson-agx-orin-devkit mmcblk0p1”be used to download pinmux without downloading the entire image？
Question 2：
I use the method of modifying pinmux by directly modifying bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi and bootloader/tegra234-mb1-bct-gpio-p3701-0000.dtsi , and then executing it “./Flash.sh - r - k A_cpu bootloader jetson-agx-orin devkit mmcblk0p1" or “./Flash.sh jetson-agx-orin-devkit mmcblk0p1”, but the final modifications to pinmux did not take effect. May I ask if my approach is feasible?
hello 1712127445,
here’s a sample command-line to flash only QSPI.
$ sudo BOARDSKU=XXXX FAB=XXX ./flash.sh --qspi-only --no-systemimg jetson-agx-orin-devkit mmcblk0p1
May I ask if “sudo BOARDSKU=XXXX FAB=XXX ./flash.sh --qspi-only --no-systemimg jetson-agx-orin-devkit mmcblk0p1” needs to add a signature after enabling the secure boot function?
hello 1712127445,
you’ll need to reflash the board completely if you have secureboot enabled.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
