Karis
June 17, 2021, 4:11am
1
Hi,
Platform:TX2-NX
We got the some issues below.
Which pin is tx and rx of canbus?
In Jetson_TX2_NX_pinmux_config.xlsm,it shows the pin 143 is CAN-TX.
In Jetson_TX2_NX_Datasheet_v1.0.pdf,It shows the pin 143 is CAN-RX.
ttyTCU0 fail
After I use the command below,the system stuck about three seconds and reboot.
I connect a i2c device,but I can’t see the device in any i2c bus.
GPIO fail
We checked the pinmux、pin offset values and calculator the gpio number.
We connect leds to GPIOs,control the gpio by /sys/class/gpio.
We use the same carrier board,if it with Xavier-NX module the Uart、GPIO、cnbus are work well,but are not working with TX2-NX .
Karis
hello Karis,
note, Xavier series and TX2 series were using different GPIO header files,tegra194-gpio.h for Xavier, and tegra186-gpio.h for TX2.
Karis
June 17, 2021, 6:56am
4
Hi JerryChang,
We Know this,so we use the tegra186-gpio.h to calculator the gpio number,and test it.
Thanks for you reply.
Karis
hello Karis,
to clarify,
please also refer to Topic 178430 ,$L4T_Sources/r32.5.1/Linux_for_Tegra/source/public/hardware/nvidia/platform/t18x/lanai/kernel-dts/tegra186-p3636-0001-p3509-0000-a01.dts
+ mttcan@c310000 {
+ status = "okay";
+ };
Karis
June 18, 2021, 7:01am
8
Hi JerryChang,
We will test it,Thanks!
Another issues needs your help,Thanks.
Karis
hello Karis,
here’re my updates…
Which pin is tx and rx of canbus?
see comment #7 ,
ttyTCU0 fail
may I know what’s your actual use-case?$ dmesg | grep "command line" for the details of the console settings,
I connect a i2c device,but I can’t see the device in any i2c bus.
it usually a regulator issue to make i2c registrations failed. you may dig into kernel logs to see if any i2c no ack failures.
GPIO fail
GPIO can’t drive much load, the resistor of LED is too little, that will grab too much current and so the voltage on little resistor will be much less than 3.3V. please check Topic 54279 as see-also.
Karis
June 23, 2021, 8:35am
10
Hi JerryChnag,
We will check and test it,Thanks!
Karis
Karis
July 1, 2021, 3:32am
12
may I know what’s your actual use-case?$ dmesg | grep "command line" for the details of the console settings,
Hi Jerry,
We want to chekck the uart function is working well in our board.
I have those problems blow.
/dev/TTYTCU0 is for ?
How do I know pin UART0 is in /dev/TTYTHS0 or /dev/TTYTHS1 or …?
nvidia@linux:~$ dmesg | grep "command line"
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x1772e0000 gpt rootfs.slot_suffix= tegra_fbmem=0x800000@0x96081000 lut_mem=0x2008@0x9607e000 usbcore.old_scheme_first=1 tegraid=18.1.2.0.0 maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2031647.1 vpr_resize bl_prof_dataptr=0x10000@0x175840000 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2
For i2c
We can’t find the i2c7
[0001.439] I> fixed regulator driver initialized
[0001.461] I> register 'maxim' power off handle
[0001.466] I> virtual i2c enabled
[0001.469] I> registered 'maxim,max77620' pmic
[0001.473] I> tegrabl_gpio_driver_register: register 'max77620-gpio' driver
[0001.482] I> Find /i2c@c250000's alias i2c7
[0001.486] I> Reading eeprom i2c=7 address=0x50
[0001.516] I> Device at /i2c@c250000:0x50
[0001.519] I> Reading eeprom i2c=7 address=0x57
[0001.548] I> Device at /i2c@c250000:0x57
[0001.552] I> Find /i2c@3160000's alias i2c0
[0001.556] I> Reading eeprom i2c=0 address=0x50
[0001.561] E> I2C: slave not found in slaves.
[0001.565] E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start true.
[0001.573] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.579] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 at 0x00000000 via instance 0.
[0001.588] E> eeprom: Failed to read I2C slave device
[0001.593] I> Eeprom read failed 0x3526070d
[0001.598] I> Find /i2c@3180000's alias i2c2
[0001.602] I> Reading eeprom i2c=2 address=0x54
[0001.606] I> Enabling gpio chip_id = 2, gpio pin = 9
[0001.611] C> GPIO driver for chip_id 0x2 could not be found
[0001.616] E> cam_eeprom_read: Can't get gpio driver
[0001.621] I> Eeprom read failed 0x4d4d000d
[0001.625] I> Reading eeprom i2c=2 address=0x57
[0001.629] I> Enabling gpio chip_id = 2, gpio pin = 9
[0001.634] C> GPIO driver for chip_id 0x2 could not be found
[0001.639] E> cam_eeprom_read: Can't get gpio driver
[0001.644] I> Eeprom read failed 0x4d4d000d
I2C bus list:
nvidia@linux:~$ i2cdetect -l
i2c-3 unknown 3190000.i2c N/A
i2c-1 unknown c240000.i2c N/A
i2c-8 unknown 31e0000.i2c N/A
i2c-6 unknown 31c0000.i2c N/A
i2c-4 unknown Tegra BPMP I2C adapter N/A
i2c-2 unknown 3180000.i2c N/A
i2c-0 unknown 3160000.i2c N/A
i2c-9 unknown i2c-2-mux (chan_id 0) N/A
i2c-10 unknown i2c-2-mux (chan_id 1) N/A
i2c-5 unknown 31b0000.i2c N/A
Karis
hello Karis,
check this, Serial communication between Jetson nano and Arduino through GPIO - #9 by JerryChang it shows the mappings for serial ports of ttyTHS*, and UART*Unable to read eeprom on tx2 nx board - #8 by JerryChang to modify device tree and enable /dev/i2c-7 interface.
system
August 31, 2021, 2:23am
14
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
