I already have same config in my DTS.
default {
gpio-input = <0x5 0xbc 0xbd 0xbe 0xc1 0xa9 0xca 0x3a 0x3d 0x3e 0x41 0xe4>;
gpio-output-low = <0x97 0x98 0xcb 0x38 0x3b 0x3c 0x3f 0x40 0x42>;
gpio-output-high = <0x6 0xbb 0xe7>;
linux,phandle = <0x41>;
phandle = <0x41>;
};
Did saw it like the pin 14,50,79,194(0x0e,0x32, 0x4f, 0xc2) in your dump file.
If i correct understand, i have to add it to gpio-output-low, like it And when made a new DTS file.
gpio-output-low= <0x6 0xbb 0xe7 0x0e 0x32 0x4f 0xc2>;
Did you check the voltage if program to gpio-output-high
Could i do it by jetson-io.py ?
No, jetson-io.py can’t configure as GPIO pin only for native function pins.
Is it correct to make a file?
sudo dtc -I dts -O dtb output.txt -o tegra210-p3448-0000-p3449-0000-a02-new.dtb
and after that I must to change extlinux.conf to new file name?
I changed conf file and reboot. but nothing change I have 1.8V. How to check?
nvidia@nvidia-desktop:~/jetson-gpio/samples$ sudo cat /sys/kernel/debug/gpio
[sudo] password for nvidia:
gpiochip0: GPIOs 0-255, parent: platform/6000d000.gpio, tegra-gpio:
gpio-0 ( )
gpio-1 ( )
gpio-2 ( |pcie_wake ) in hi
gpio-3 ( )
gpio-4 ( )
gpio-5 ( )
gpio-6 ( |vdd-usb-hub-en ) out hi
gpio-7 ( )
gpio-8 ( )
gpio-9 ( )
gpio-10 ( )
gpio-11 ( )
gpio-12 (SPI1_MOSI )
gpio-13 (SPI1_MISO )
gpio-14 (SPI1_SCK |sysfs ) in hi IRQ
gpio-15 (SPI1_CS0 )
gpio-16 (SPI0_MOSI )
gpio-17 (SPI0_MISO )
gpio-18 (SPI0_SCK )
gpio-19 (SPI0_CS0 )
gpio-20 (SPI0_CS1 )
gpio-21 ( )
gpio-22 ( )
gpio-23 ( )
gpio-24 ( )
gpio-25 ( )
gpio-26 ( )
gpio-27 ( )
gpio-28 ( )
gpio-29 ( )
gpio-30 ( )
gpio-31 ( )
gpio-32 ( )
gpio-33 ( )
gpio-34 ( )
gpio-35 ( )
gpio-36 ( )
gpio-37 ( )
gpio-38 (GPIO13 )
gpio-39 ( )
gpio-40 ( )
gpio-41 ( )
gpio-42 ( )
gpio-43 ( )
gpio-44 ( )
gpio-45 ( )
gpio-46 ( )
gpio-47 ( )
gpio-48 ( )
gpio-49 ( )
gpio-50 (UART1_RTS |sysfs ) in lo IRQ
gpio-51 (UART1_CTS )
gpio-52 ( )
gpio-53 ( )
gpio-54 ( )
gpio-55 ( )
gpio-56 ( )
gpio-57 ( )
gpio-58 ( )
gpio-59 ( )
gpio-60 ( )
gpio-61 ( )
gpio-62 ( )
gpio-63 ( )
gpio-64 ( )
gpio-65 ( )
gpio-66 ( )
gpio-67 ( )
gpio-68 ( )
gpio-69 ( )
gpio-70 ( )
gpio-71 ( )
gpio-72 ( )
gpio-73 ( )
gpio-74 ( )
gpio-75 ( )
gpio-76 (I2S0_FS )
gpio-77 (I2S0_DIN )
gpio-78 (I2S0_DOUT |sysfs ) out hi
gpio-79 (I2S0_SCLK |sysfs ) in lo IRQ
gpio-80 ( )
gpio-81 ( )
gpio-82 ( )
gpio-83 ( )
gpio-84 ( )
gpio-85 ( )
gpio-86 ( )
gpio-87 ( )
gpio-88 ( )
gpio-89 ( )
gpio-90 ( )
gpio-91 ( )
gpio-92 ( )
gpio-93 ( )
gpio-94 ( )
gpio-95 ( )
gpio-96 ( )
gpio-97 ( )
gpio-98 ( )
gpio-99 ( )
gpio-100 ( )
gpio-101 ( )
gpio-102 ( )
gpio-103 ( )
gpio-104 ( )
gpio-105 ( )
gpio-106 ( )
gpio-107 ( )
gpio-108 ( )
gpio-109 ( )
gpio-110 ( )
gpio-111 ( )
gpio-112 ( )
gpio-113 ( )
gpio-114 ( )
gpio-115 ( )
gpio-116 ( )
gpio-117 ( )
gpio-118 ( )
gpio-119 ( )
gpio-120 ( )
gpio-121 ( )
gpio-122 ( )
gpio-123 ( )
gpio-124 ( )
gpio-125 ( )
gpio-126 ( )
gpio-127 ( )
gpio-128 ( )
gpio-129 ( )
gpio-130 ( )
gpio-131 ( )
gpio-132 ( )
gpio-133 ( )
gpio-134 ( )
gpio-135 ( )
gpio-136 ( )
gpio-137 ( )
gpio-138 ( )
gpio-139 ( )
gpio-140 ( )
gpio-141 ( )
gpio-142 ( )
gpio-143 ( )
gpio-144 ( )
gpio-145 ( )
gpio-146 ( )
gpio-147 ( )
gpio-148 ( )
gpio-149 (GPIO01 )
gpio-150 ( )
gpio-151 ( )
gpio-152 ( )
gpio-153 ( )
gpio-154 ( )
gpio-155 ( )
gpio-156 ( )
gpio-157 ( )
gpio-158 ( )
gpio-159 ( )
gpio-160 ( )
gpio-161 ( )
gpio-162 ( )
gpio-163 ( )
gpio-164 ( )
gpio-165 ( )
gpio-166 ( )
gpio-167 ( )
gpio-168 (GPIO07 )
gpio-169 ( )
gpio-170 ( )
gpio-171 ( )
gpio-172 ( )
gpio-173 ( )
gpio-174 ( )
gpio-175 ( )
gpio-176 ( )
gpio-177 ( )
gpio-178 ( )
gpio-179 ( )
gpio-180 ( )
gpio-181 ( )
gpio-182 ( )
gpio-183 ( )
gpio-184 ( )
gpio-185 ( )
gpio-186 ( )
gpio-187 ( |? ) out hi
gpio-188 ( )
gpio-189 ( |Power ) in hi IRQ
gpio-190 ( |Forcerecovery ) in hi IRQ
gpio-191 ( )
gpio-192 ( )
gpio-193 ( )
gpio-194 (GPIO12 )
gpio-195 ( )
gpio-196 ( )
gpio-197 ( )
gpio-198 ( )
gpio-199 ( )
gpio-200 (GPIO11 )
gpio-201 ( |cd ) in lo IRQ
gpio-202 ( |pwm-fan-tach ) in hi IRQ
gpio-203 ( |vdd-3v3-sd ) out hi
gpio-204 ( )
gpio-205 ( )
gpio-206 ( )
gpio-207 ( )
gpio-208 ( )
gpio-209 ( )
gpio-210 ( )
gpio-211 ( )
gpio-212 ( )
gpio-213 ( )
gpio-214 ( )
gpio-215 ( )
gpio-216 (GPIO09 |sysfs ) in lo IRQ
gpio-217 ( )
gpio-218 ( )
gpio-219 ( )
gpio-220 ( )
gpio-221 ( )
gpio-222 ( )
gpio-223 ( )
gpio-224 ( )
gpio-225 ( |hdmi2.0_hpd ) in hi IRQ
gpio-226 ( )
gpio-227 ( )
gpio-228 ( |extcon:extcon@1 ) in lo IRQ
gpio-229 ( )
gpio-230 ( )
gpio-231 ( )
gpio-232 (SPI1_CS1 )
gpio-233 ( )
gpio-234 ( )
gpio-235 ( )
gpio-236 ( )
gpio-237 ( )
gpio-238 ( )
gpio-239 ( )
gpiochip1: GPIOs 504-511, parent: platform/max77620-gpio, max77620-gpio, can sleep:
gpio-505 ( |spmic-default-output) out hi
gpio-507 ( |vdd-3v3-sys ) out hi
gpio-510 ( |enable ) out lo
gpio-511 ( |avdd-io-edp-1v05 ) out lo
Hi,
I’ve checked all pins to read input & set output, it work perfectly, but our app still doesn’t work with lora.
It fall down with message “DIO3 mapping error”, in app DIO3 is configured to PIN13 which has name “SPI_2_SCK” or BCM=27 and set like INPUT pin. I checked it pin through simple_imput.py connected to GND & 3V3, I have 0 & 1, that is normal.
other DIO0, DIO1, DIO3 were checked too and worked.
Can i portate ISO Jetson Xavier to Jetson Nano?
Have a check with gpio sysfs for DI03 if can export it and control it.
Hi,
I checked it with SYSFS, how can you see, I can set direction IN.
nvidia@nvidia-desktop:~$ sudo echo 14 > /sys/class/gpio/
nvidia@nvidia-desktop:~$ sudo echo 14 > /sys/class/gpio/export
nvidia@nvidia-desktop:~$ sudo echo 1 > /sys/class/gpio/gpio14/value
echo: write error: Operation not permitted
nvidia@nvidia-desktop:~$ cat /sys/class/gpio/gpio14/direction
in
It has only one state “Hi”. What does it mean?
nvidia@nvidia-desktop:~$ sudo cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-255, parent: platform/6000d000.gpio, tegra-gpio:
gpio-0 ( )
gpio-1 ( )
gpio-2 ( |pcie_wake ) in hi
gpio-3 ( )
gpio-4 ( )
gpio-5 ( )
gpio-6 ( |vdd-usb-hub-en ) out hi
gpio-7 ( )
gpio-8 ( )
gpio-9 ( )
gpio-10 ( )
gpio-11 ( )
gpio-12 (SPI1_MOSI )
gpio-13 (SPI1_MISO )
gpio-14 (SPI1_SCK |sysfs ) in hi
Is Jetson have PULL_DOWN on PINs 7, 11, 12, 13 if are working to IN? If isn’t could I made PULL_DOWN to GND by resistor 10kOmhs?
In our code PINs 7, 11, 12, 13 is working to IN with RISING mode, I think, in RISING mode PINs must have PULL DOWN, isn’t it?
I found that tread, my be I have a same problem?
Hi,
I connected an oscilloscope to all SPI pins and I found that Jetson didn’t send signal at SCK (pin 23). All functions are enabled. Why is?
Enabled functions (pins):
- spi1 (19,21,23,24,26)
Bank: 1 Reg: 0x70003050 Val: 0x0000e044 → spi1_mosi_pc0
Bank: 1 Reg: 0x70003054 Val: 0x0000e044 → spi1_miso_pc1
Bank: 1 Reg: 0x70003058 Val: 0x0000e044 → spi1_sck_pc2
Bank: 1 Reg: 0x7000305c Val: 0x0000e048 → spi1_cs0_pc3
Bank: 1 Reg: 0x70003060 Val: 0x0000e048 → spi1_cs1_pc4
I measurement signal SCK at the Raspberry 3 and Jetson Nano are have a different voltage level 3.36V & 2.46V accordingly
Did you apply the PINMUX configure generate by jetson-io.py?
Could you try if loopback test working?
Did you apply the PINMUX configure generate by jetson-io.py?
yes, I added to extlinux.conf new FDT path.
Could you try if loopback test working?
yes, it’s work with out problem
Could you check the signal by scope while doing the loopback test.
Tested
spi0.0 is ~ 3.3V MISO & MOSI
nvidia@nvidia-desktop:~/spidev-test$ sudo ./spidev_test -v -s 500000
spi mode: 0x0
bits per word: 8
max speed: 500000 Hz (500 KHz)
TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒.
RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒.
spi1.0 is ~ 3.3V MISO & MOSI & SCK
nvidia@nvidia-desktop:~/spidev-test$ sudo ./spidev_test -v -s 500000 -C -D /dev/spidev1.0
spi mode: 0x4
bits per word: 8
max speed: 500000 Hz (500 KHz)
TX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒.
RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....▒..................▒.
I don’t understand, why without SX127x I have 3.3V on pins, with SX127x not more than 2.5V
Hi,
In finally the Jetson has lost the 3.3V on GPIO header. I don’t know why, but it wasn’t external influences.
After cable disconnected 3,3v is returned.
Yellow - it is MISO = max 3.52V
Blue - it is MOSI = max 2.68V
Why MOSI (Mster Output) lower than base voltage?
