ckaya
October 23, 2018, 10:26am
1
Hi,
We have Jetson TX2 module and its evaluation board and we can use HDMI and USB ports without problem. However if I plug that jetson module to our carrier board, I cannot use HDMI and USB ports. lsusb returns nothing. I checked the schematics of both evaluation board and our carrier board but there is not a diffrences of the signals.
There is an EEPROM on the datasheet of evaluation board on page 24, it says “Carrier board config”. Does this EEPROM hold configuration parameters of these ports for Linux to enable/disable them? Or what could be the problem? Module and Linux on it are same.
Linux also prints logs below when I use it with our carrier board.
[ 164.709091] tegra-i2c 3190000.i2c: --- register dump for debugging ----
[ 164.716180] tegra-i2c 3190000.i2c: I2C_CNFG - 0x22c00
[ 164.721453] tegra-i2c 3190000.i2c: I2C_PACKET_TRANSFER_STATUS - 0x10001
[ 164.728105] tegra-i2c 3190000.i2c: I2C_FIFO_CONTROL - 0x1c
[ 164.733722] tegra-i2c 3190000.i2c: I2C_FIFO_STATUS - 0x800040
[ 164.739595] tegra-i2c 3190000.i2c: I2C_INT_MASK - 0x6c
[ 164.744751] tegra-i2c 3190000.i2c: I2C_INT_STATUS - 0x2
[ 164.750017] tegra-i2c 3190000.i2c: i2c transfer timed out addr: 0x50
Each carrier board needs its own device tree. Unless your board is an exact replica to the dev board the module won’t work on both boards without the device tree edits.
FYI, at least on the dev carrier, 0x50 i2c is the HDMI’s DDC wire (the EDID query of capabilities). This would not explain USB issues, but it would explain lack of video.
Don’t know what the EEPROM will have.
ckaya
October 24, 2018, 9:21am
4
Thank you for your help.
I found a modified device tree from auvidea.com for TX2 and I used it. Good news is, I can use second USB2 port (pins B42, B43). However I have some problems.
Our design is, we use all USB ports: Second USB port is for external devices like USB memory stick etc. and USB3 port (both USB3 side and USB2 side) is directly connected to SMARC module running Windows on. After applying auvidea’s device tree, Windows started to complain about USB port. It says “Last usb device you connected to this computer is malfunctioned and Windows does not recognize it.”
what should I do in order to use all USB ports?
you can find auvidea’s device tree patch here:www.auvidea-pcb.com/firmware/tx2/1.6/auvidea-kernel-J90-J120-v1.6.zip
ckaya
November 1, 2018, 6:33am
6
Hi DaneLLL,
Thank you for the links.
Actually we are not workking with Auvidea. I just saw they had that patch and tried to apply it.
ckaya
November 2, 2018, 1:06pm
7
Hi DaneLLL,
I compiled Linux and device tree but still Windows thinks USB port is malfunctioned. This USB3 port should be slave (Windows is host) and I think I have to set this port as slave but couldn’t find any information about how to set it as slave.
You can find device tree files attached.
device_tree_files.tar.gz (3.02 KB)
If the port is connected to a Linux system, does the port show up with “lsusb”? Windows hides a lot of details and can be painful to debug USB. If you can verify under a Linux host that the device is or is not seen as USB, then you can go on to the question of what kind of device the Jetson emulates (which in turn would say whether a special driver is needed on the host to make use of the device).
FYI, a Jetson with a port in device mode can be self-connected to one of the Jetson’s other connectors…a USB cable between the device port and host port of the same system. There is no reason the Jetson couldn’t look at its own USB, and if you don’t have a separate Linux host, then try lsusb of the Jetson connected to itself. The Jetson won’t care that it is both host and device.
You can monitor a Jetson or Linux host for some information at the moment of connect by running “dmesg --follow” prior to connect. For a micro-OTG port there will probably be a message when a type-B connector is inserted (used on a device), and if there is a device present, then there will also be a message when the type-A connector (used on a host) connects. This would probably provide information about errors.
If you do see the device connect, then it will have an ID shown in “lsusb”. You can use the ID to limit query to that one device, and then get verbose details. For example, if the ID is ‘0955:7c18’ (it won’t be that, it’s just an example), then verbose listing goes like this:
sudo lsusb -d 0955:7c18 -vvv
ckaya
November 14, 2018, 8:15am
9
Hi,
I tried to put USB3 into otg mode by using commands in this link: https://devtalk.nvidia.com/default/topic/1029128/jetson-tx2/tx2-connectivity-and-usb-3-0-otg/post/5234988/#5234988
However I got kernel errors and Jetson restarted itself. You can find all files I used.
BTW, I used Jetpack 3.3
output after running configfs_msc_l4t.sh:
nvidia@tegra-ubuntu:~$ sudo ./configfs_msc_l4t.sh
[ 453.293396] sysfs: cannot create duplicate filename '/devices/virtual/android_usb/android0'
[ 453.301886] ------------[ cut here ]------------
[ 453.306516] WARNING: at ffffffc00024402c [verbose debug info unavailable]
[ 453.313295] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack nf_nat br_netfilter overlay fuse bcmdhd pci_tegra bluedroid_pm
[ 453.331738]
[ 453.333235] CPU: 4 PID: 2605 Comm: mkdir Not tainted 4.4.38 #1
[ 453.339063] Hardware name: quill (DT)
[ 453.342724] task: ffffffc1cafbcb00 ti: ffffffc1dcccc000 task.ti: ffffffc1dcccc000
[ 453.350208] PC is at sysfs_warn_dup+0x5c/0x80
[ 453.354561] LR is at sysfs_warn_dup+0x5c/0x80
[ 453.358914] pc : [<ffffffc00024402c>] lr : [<ffffffc00024402c>] pstate: 60000145
[ 453.366301] sp : ffffffc1dcccfac0
[ 453.369614] x29: ffffffc1dcccfac0 x28: ffffffc1dcccc000
[ 453.374945] x27: ffffffc000b5e000 x26: 0000000000000000
[ 453.380274] x25: 0000000000000000 x24: 0000000000000000
[ 453.385604] x23: ffffffc1dfeec380 x22: 0000000000000000
[ 453.390932] x21: ffffffc07ac69438 x20: ffffffc000ffcca8
[ 453.396259] x19: ffffffc06e88a000 x18: 0000000000000a03
[ 453.401587] x17: 00000000004202f8 x16: ffffffc0001e4440
[ 453.406916] x15: 0000007f87125cc0 x14: 736563697665642f
[ 453.412244] x13: 2720656d616e656c x12: 6966206574616369
[ 453.417570] x11: 6c70756420657461 x10: 65726320746f6e6e
[ 453.422900] x9 : 0000000000000754 x8 : 0000000000000001
[ 453.428229] x7 : ffffffc1dcccc000 x6 : 0000000000000000
[ 453.433557] x5 : 0000000000000000 x4 : 0000000000000000
[ 453.438884] x3 : 0000000000000000 x2 : 0000000000000000
[ 453.444212] x1 : 0000000000000000 x0 : 000000000000004f
[ 453.449539]
[ 453.451442] ---[ end trace 0fbad93eb7bbdcfe ]---
[ 453.456059] Call trace:
[ 453.458512] [<ffffffc00024402c>] sysfs_warn_dup+0x5c/0x80
[ 453.463909] [<ffffffc00024414c>] sysfs_create_dir_ns+0x98/0xa0
[ 453.469741] [<ffffffc00033fb94>] kobject_add_internal+0xa8/0x314
[ 453.475743] [<ffffffc000340074>] kobject_add+0x90/0xdc
[ 453.480881] [<ffffffc000572000>] device_add+0xd8/0x584
[ 453.486016] [<ffffffc0005726e0>] device_create_groups_vargs+0xf8/0x124
[ 453.492538] [<ffffffc0005727a0>] device_create+0x60/0x68
[ 453.497850] [<ffffffc00072e4d4>] gadgets_make+0x228/0x314
[ 453.503246] [<ffffffc00024747c>] configfs_mkdir+0x110/0x344
[ 453.508817] [<ffffffc0001dfbb4>] vfs_mkdir+0xe8/0x180
[ 453.513865] [<ffffffc0001e44ac>] SyS_mkdirat+0x6c/0xbc
[ 453.519002] [<ffffffc000084ff0>] el0_svc_naked+0x24/0x28
[ 453.524526] kobject_add_internal failed for android0 with -EEXIST, don't try to register things with the same name in the same directory.
[ 453.536910] ------------[ cut here ]------------
[ 453.541524] WARNING: at ffffffc00033fc80 [verbose debug info unavailable]
[ 453.548302] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack nf_nat br_netfilter overlay fuse bcmdhd pci_tegra bluedroid_pm
[ 453.566719]
[ 453.568212] CPU: 4 PID: 2605 Comm: mkdir Tainted: G W 4.4.38 #1
[ 453.575248] Hardware name: quill (DT)
[ 453.578904] task: ffffffc1cafbcb00 ti: ffffffc1dcccc000 task.ti: ffffffc1dcccc000
[ 453.586381] PC is at kobject_add_internal+0x194/0x314
[ 453.591426] LR is at kobject_add_internal+0x194/0x314
[ 453.596470] pc : [<ffffffc00033fc80>] lr : [<ffffffc00033fc80>] pstate: 80000045
[ 453.603854] sp : ffffffc1dcccfb20
[ 453.607162] x29: ffffffc1dcccfb20 x28: ffffffc1dcccc000
[ 453.612487] x27: ffffffc000b5e000 x26: 0000000000000000
[ 453.617813] x25: 0000000000000000 x24: 0000000000000000
[ 453.623138] x23: ffffffc1dfeec380 x22: 0000000000000000
[ 453.628463] x21: 00000000ffffffef x20: ffffffc1dfeec380
[ 453.633788] x19: ffffffc06cfa0410 x18: 0000000000000a03
[ 453.639115] x17: 00000000004202f8 x16: ffffffc0001e4440
[ 453.644441] x15: ffffffc000b62a60 x14: ffffffc000b62a60
[ 453.649767] x13: 0000000000000000 x12: 000003fffffffc00
[ 453.655093] x11: 0000000000003370 x10: 00000000000008b0
[ 453.660419] x9 : ffffffc1dcccf8e0 x8 : ffffffc1cafbd410
[ 453.665746] x7 : 00000000000001e3 x6 : 00000000010b97a1
[ 453.671074] x5 : 0000000000000000 x4 : ffffffc1cafbd418
[ 453.676400] x3 : ffffffc07aca674c x2 : ffffffc1e225b228
[ 453.681724] x1 : 0000000000000000 x0 : 000000000000007d
[ 453.687051]
[ 453.688858] ---[ end trace 0fbad93eb7bbdcff ]---
[ 453.693470] Call trace:
[ 453.695924] [<ffffffc00033fc80>] kobject_add_internal+0x194/0x314
[ 453.702011] [<ffffffc000340074>] kobject_add+0x90/0xdc
[ 453.707148] [<ffffffc000572000>] device_add+0xd8/0x584
[ 453.712280] [<ffffffc0005726e0>] device_create_groups_vargs+0xf8/0x124
[ 453.718798] [<ffffffc0005727a0>] device_create+0x60/0x68
[ 453.724108] [<ffffffc00072e4d4>] gadgets_make+0x228/0x314
[ 453.729505] [<ffffffc00024747c>] configfs_mkdir+0x110/0x344
[ 453.735074] [<ffffffc0001dfbb4>] vfs_mkdir+0xe8/0x180
[ 453.740120] [<ffffffc0001e44ac>] SyS_mkdirat+0x6c/0xbc
[ 453.745254] [<ffffffc000084ff0>] el0_svc_naked+0x24/0x28
mkdir: cannot create directory â/config/usb_gadget/g1â: Cannot allocate memory
./configfs_msc_l4t.sh: line 7: /config/usb_gadget/g1/idVendor: No such file or directory
./configfs_msc_l4t.sh: line 8: /config/usb_gadget/g1/idProduct: No such file or directory
./configfs_msc_l4t.sh: line 9: /config/usb_gadget/g1/bcdUSB: No such file or directory
mkdir: cannot create directory â/config/usb_gadget/g1/strings/0x409â: No such file or directory
./configfs_msc_l4t.sh: line 11: /config/usb_gadget/g1/strings/0x409/manufacturer: No such file or directory
./configfs_msc_l4t.sh: line 12: /config/usb_gadget/g1/strings/0x409/product: No such file or directory
./configfs_msc_l4t.sh: line 13: /config/usb_gadget/g1/strings/0x409/serialnumber: No such file or directory
mkdir: cannot create directory â/config/usb_gadget/g1/configs/b.1â: No such file or directory
mkdir: cannot create directory â/config/usb_gadget/g1/functions/mass_storage.mscâ: No such file or directory
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 7.90209 s, 136 MB/s
mke2fs 1.42.13 (17-May-2015)
Discarding device blocks: done
Creating filesystem with 262144 4k blocks and 65536 inodes
Filesystem UUID: 60c2bb52-7371-47ed-9535-a23621954057
Superblock backups stored on blocks:
32768, 98304, 163840, 229376
Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
./configfs_msc_l4t.sh: line 21: /config/usb_gadget/g1/functions/mass_storage.msc/lun.0/file: No such file or directory
ln: failed to create symbolic link '/config/usb_gadget/g1/configs/b.1/f1': No such file or directory
./configfs_msc_l4t.sh: line 24: /config/usb_gadget/g1/UDC: No such file or directory
output of echo 0x1 > /sys/class/extcon/extcon0/state:
root@tegra-ubuntu:/home/nvidia# echo 0x1 > /sys/class/extcon/extcon0/state
[ 849.076489] tegra-xotg xotg: update_vbus_state: VBUS detected
root@tegra-ubuntu:/home/nvidia# [ 849.186044] tegra-usb-cd usb_cd: notification status (0x0, 0x1)
[ 849.192408] tegra-usb-cd usb_cd: set current 0ma
[ 849.197711] tegra-xudc-new 3550000.xudc: exiting ELPG
[ 849.220098] tegra-xudc-new 3550000.xudc: exiting ELPG done
[ 849.225692] tegra-xudc-new 3550000.xudc: device mode on
[ 849.431722] android_work: did not send uevent (0 0 (null))
[ 849.484803] android_work: did not send uevent (0 0 (null))
[ 849.517696] Unable to handle kernel NULL pointer dereference at virtual address 0000001f
[ 849.526184] pgd = ffffffc0014b6000
[ 849.529882] [0000001f] *pgd=000000026cda4003, *pud=000000026cda4003, *pmd=000000026cda5003, *pte=00e8000003881707
[ 849.542072] Internal error: Oops: 96000006 [#1] PREEMPT SMP
[ 849.547673] Modules linked in: fuse ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack nf_nat br_netfilter overlay bcmdhd pci_tegra bluedroid_pm
[ 849.566201] CPU: 0 PID: 2619 Comm: kworker/0:2 Tainted: G W 4.4.38 #1
[ 849.573772] Hardware name: quill (DT)
[ 849.577464] Workqueue: events android_work
[ 849.581581] task: ffffffc1c1bde400 ti: ffffffc1e3a50000 task.ti: ffffffc1e3a50000
[ 849.589074] PC is at kobject_uevent_env+0x54/0x66c
[ 849.593875] LR is at android_work+0xb0/0x1c4
[ 849.598154] pc : [<ffffffc000340634>] lr : [<ffffffc00072e670>] pstate: 80000045
[ 849.605550] sp : ffffffc1e3a53c80
[ 849.608871] x29: ffffffc1e3a53c80 x28: ffffffffffffffff
[ 849.614215] x27: 0000000000000000 x26: ffffffc1e3a53d50
[ 849.619558] x25: 0000000000000002 x24: ffffffc000ba6000
[ 849.624902] x23: ffffffc1f6644600 x22: 0000000000000000
[ 849.630242] x21: ffffffc0013d9000 x20: ffffffc000f80d80
[ 849.635584] x19: ffffffc1e0345c80 x18: 0000000000008090
[ 849.640926] x17: 0000000000000000 x16: 0000000000000000
[ 849.646269] x15: ffffffc000b62a60 x14: ffffffc000b62a60
[ 849.651610] x13: 0000000000000001 x12: 00002cb45e2d744b
[ 849.656952] x11: ffffffc000b629d0 x10: 00000000000008b0
[ 849.662294] x9 : ffffffc1e3a53d20 x8 : ffffffc1c1bded10
[ 849.667636] x7 : ffffffc1f663f5a0 x6 : 0000000000034c64
[ 849.672979] x5 : 0000000000000000 x4 : ffffffffffffffff
[ 849.678319] x3 : ffffffc0013d9e40 x2 : ffffffc1e3a53d50
[ 849.683662] x1 : 0000000000000002 x0 : ffffffffffffffff
[ 849.689005]
[ 849.690509] Process kworker/0:2 (pid: 2619, stack limit = 0xffffffc1e3a50020)
[ 849.697645] Call trace:
[ 849.700105] [<ffffffc000340634>] kobject_uevent_env+0x54/0x66c
[ 849.705947] [<ffffffc00072e670>] android_work+0xb0/0x1c4
[ 849.711271] [<ffffffc0000bc2d0>] process_one_work+0x154/0x434
[ 849.717022] [<ffffffc0000bc6e4>] worker_thread+0x134/0x40c
[ 849.722518] [<ffffffc0000c1f30>] kthread+0xe0/0xf4
[ 849.727321] [<ffffffc000084f90>] ret_from_fork+0x10/0x40
[ 849.733296] ---[ end trace 310c4835df971eb9 ]---
[ 849.743796] Unable to handle kernel paging request at virtual address ffffffffffffffd8
[ 849.751725] pgd = ffffffc07a6be000
[ 849.755135] [ffffffffffffffd8] *pgd=00000000fa16a003, *pud=00000000fa16a003, *pmd=0000000000000000
[ 849.764146] Internal error: Oops: 96000005 [#2] PREEMPT SMP
[ 849.769723] Modules linked in: fuse ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack nf_nat br_netfilter overlay bcmdhd pci_tegra bluedroid_pm
[ 849.788243] CPU: 0 PID: 2619 Comm: kworker/0:2 Tainted: G D W 4.4.38 #1
[ 849.795813] Hardware name: quill (DT)
[ 849.799497] task: ffffffc1c1bde400 ti: ffffffc1e3a50000 task.ti: ffffffc1e3a50000
[ 849.806990] PC is at kthread_data+0x4/0xc
[ 849.811009] LR is at wq_worker_sleeping+0x10/0xc4
[ 849.815718] pc : [<ffffffc0000c25f8>] lr : [<ffffffc0000bd190>] pstate: 600000c5
[ 849.823112] sp : ffffffc1e3a53870
[ 849.826432] x29: ffffffc1e3a53870 x28: ffffffc1e3a50000
[ 849.831776] x27: 0000000000000000 x26: ffffffc00124e000
[ 849.837118] x25: 0000000000000000 x24: ffffffc000b53aa0
[ 849.842459] x23: 0000000000000000 x22: ffffffc1c1bde990
[ 849.847801] x21: ffffffc001220000 x20: ffffffc1c1bde400
[ 849.853141] x19: ffffffc1f663f580 x18: ffffffc000bd50a0
[ 849.858482] x17: 000000000000000e x16: 0000000000000007
[ 849.863823] x15: 0000000000000001 x14: 0000000000000007
[ 849.869164] x13: 000000000000000e x12: 0000000000000013
[ 849.874506] x11: 000000000000001a x10: 00000000000e3800
[ 849.879847] x9 : 00000000000e3800 x8 : 00000000000000ad
[ 849.885191] x7 : 0000000000000000 x6 : 00000000007bb480
[ 849.890534] x5 : ffffffc1f663f580 x4 : ffffffc1f663ff60
[ 849.895874] x3 : 000000000001af3b x2 : ffffffc1f6621000
[ 849.901214] x1 : 0000000000000000 x0 : 0000000000000000
[ 849.906555]
[ 849.908056] Process kworker/0:2 (pid: 2619, stack limit = 0xffffffc1e3a50020)
[ 849.915190] Call trace:
[ 849.917649] [<ffffffc0000c25f8>] kthread_data+0x4/0xc
[ 849.922716] [<ffffffc000b536d0>] __schedule+0x348/0x6d4
[ 849.927947] [<ffffffc000b53aa0>] schedule+0x44/0xa8
[ 849.932834] [<ffffffc0000a7b94>] do_exit+0x5b8/0x9a8
[ 849.937809] [<ffffffc000089bd8>] bug_handler.part.3+0x0/0x7c
[ 849.943482] [<ffffffc00009c820>] __do_kernel_fault.part.7+0x74/0x84
[ 849.949755] [<ffffffc00009a98c>] do_page_fault+0x350/0x444
[ 849.955247] [<ffffffc00009ab40>] do_translation_fault+0xc0/0xf0
[ 849.961173] [<ffffffc000081434>] do_mem_abort+0x40/0xa0
[ 849.966404] [<ffffffc000084540>] el1_da+0x18/0x78
[ 849.971122] [<ffffffc00072e670>] android_work+0xb0/0x1c4
[ 849.976438] [<ffffffc0000bc2d0>] process_one_work+0x154/0x434
[ 849.982187] [<ffffffc0000bc6e4>] worker_thread+0x134/0x40c
[ 849.987681] [<ffffffc0000c1f30>] kthread+0xe0/0xf4
[ 849.992480] [<ffffffc000084f90>] ret_from_fork+0x10/0x40
[ 849.998311] ---[ end trace 310c4835df971eba ]---
[ 850.008502] Fixing recursive fault but reboot is needed!
[ 876.112651] Watchdog detected hard LOCKUP on cpu 0
[ 876.117297] ------------[ cut here ]------------
[ 876.122114] WARNING: at ffffffc00013edf8 [verbose debug info unavailable]
[ 876.128905] Modules linked in: fuse ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack nf_nat br_netfilter overlay bcmdhd pci_tegra bluedroid_pm
[ 876.147435]
[ 876.148944] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G D W 4.4.38 #1
[ 876.156083] Hardware name: quill (DT)
[ 876.159754] task: ffffffc1ece9be80 ti: ffffffc1eceb4000 task.ti: ffffffc1eceb4000
[ 876.167254] PC is at watchdog_timer_fn+0x230/0x33c
[ 876.172052] LR is at watchdog_timer_fn+0x230/0x33c
[ 876.176849] pc : [<ffffffc00013edf8>] lr : [<ffffffc00013edf8>] pstate: 600001c5
[ 876.184245] sp : ffffffc1eceb7ae0
[ 876.187565] x29: ffffffc1eceb7ae0 x28: 0000000000000000
[ 876.192912] x27: ffffffc00124db30 x26: ffffffc1f6690278
[ 876.198256] x25: ffffffc00121c2d8 x24: ffffffc1eceb7dc0
[ 876.203598] x23: 0000000000000000 x22: 000000000000032c
[ 876.208942] x21: ffffffc00124d000 x20: ffffffc00121c000
[ 876.214286] x19: ffffffc00121c260 x18: 0000000000000500
[ 876.219629] x17: 0000007fb2552240 x16: ffffffc0001e6610
[ 876.224972] x15: ffffffc000b62a60 x14: 0000000000000001
[ 876.230315] x13: 00000000007b0c3b x12: 000a5d86167fe773
[ 876.235656] x11: 0000000000000000 x10: 0000000000010002
[ 876.240998] x9 : 00000000000007f3 x8 : 0000000000000000
[ 876.246339] x7 : ffffffc00128fd00 x6 : ffffffc001265738
[ 876.251680] x5 : 0000000000000000 x4 : 0000000000000000
[ 876.257021] x3 : 0000000000000000 x2 : 0000000000010001
[ 876.262362] x1 : ffffffc1eceb4000 x0 : 0000000000000026
[ 876.267702]
[ 876.269873] ---[ end trace 310c4835df971ebb ]---
[ 876.274496] Call trace:
[ 876.276958] [<ffffffc00013edf8>] watchdog_timer_fn+0x230/0x33c
[ 876.282804] [<ffffffc000107d64>] __hrtimer_run_queues+0x140/0x350
[ 876.288907] [<ffffffc0001087c4>] hrtimer_interrupt+0x9c/0x1e0
[ 876.294665] [<ffffffc0009169a4>] tegra186_timer_isr+0x24/0x30
[ 876.300420] [<ffffffc0000f5650>] handle_irq_event_percpu+0x84/0x290
[ 876.306690] [<ffffffc0000f58a0>] handle_irq_event+0x44/0x74
[ 876.312269] [<ffffffc0000f8ba8>] handle_fasteoi_irq+0xb4/0x188
[ 876.318108] [<ffffffc0000f4c70>] generic_handle_irq+0x24/0x38
[ 876.323859] [<ffffffc0000f4f78>] __handle_domain_irq+0x60/0xb4
[ 876.329700] [<ffffffc000081774>] gic_handle_irq+0x5c/0xb4
[ 876.335106] [<ffffffc000084740>] el1_irq+0x80/0xf8
[ 876.339908] [<ffffffc000800e5c>] cpuidle_enter+0x18/0x20
[ 876.345227] [<ffffffc0000e8354>] call_cpuidle+0x28/0x50
[ 876.350458] [<ffffffc0000e84f8>] cpu_startup_entry+0x17c/0x340
[ 876.356299] [<ffffffc00008ee44>] secondary_start_kernel+0x12c/0x164
[ 876.362570] [<0000000080081acc>] 0x80081acc
files.tar.gz (3.74 KB)
DaneLLL
November 14, 2018, 8:41am
10
Hi ckaya,
And this topic is not about otg function on devkit. Please make a new post.
I do see gadget is involved in one of the stack traces:
[ 453.497850] [<ffffffc00072e4d4>] gadgets_make+0x228/0x314
Do beware that gadget runs in kernel space. If you go to device mode and gadget is incorrectly configured it will crash and burn. I would suggest that until all other bugs are resolved you avoid device mode. Keep the port in host mode until you are sure nothing else is wrong. If going into device mode triggers an error, then your gadget setup is probably incorrect.