The nano freezes on the backplane of its own design after booting into the desktop. DP work,but USB did not work。

Hi @xinzhenren

If we need to check your usb issue, we need your result of “lsusb” and the schematic of your custom board design too.

Also, please remember to connect a usb device when dumping lsusb.


如果還需要確認你的usb issue的話我們需要 lsusb command的結果, 還有你們自己做的底板的線路圖. 可以只給usb的部份就好

Hi, Compared with USB not working, the problem of crashing( cpu woking, desktop programs don’t respond ) after entering the desktop is more urgent. Do you have any suggestions? Thanks.
您好,相较于USB不工作这个问题,进入桌面就假死(cpu工作,但桌面程序无响应)这个问题是更紧急的,请问您有什么建议来排查这个原因么?谢谢。

請問一下你怎麼判斷desktop don’t respond這件事情…

您好,桌面没有出现图标,我设置的自启动Qt程序也没有运行,只有右上角的时间是正常的,但如果断电重启,时间又会恢复到上次上电的时间。

Hi,

能麻煩你先在serial console上打下面command然後回傳結果嗎?

export DISPLAY=:0
xrandr

Hi, this is what is displayed. 您好,这是输入 export DISPLAY=:0 xrandr后显示的结果。
minicom_nano_xrandr.txt (881 Bytes)

alton@alton:~$ export DISPLAY=:0xrandr
Screen 0: minimum 8 x 8, current 4480 x 2160, maximum 16384 x 16384
HDMI-0 connected primary 640x350+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   640x350       85.08*+
DP-0 connected 3840x2160+640+0 (normal left inverted right x axis y axis) 620mm x 340mm
   3840x2160     60.01*+  29.99  
   2560x1440     59.96  
   1920x2160     60.00  
   1920x1080     60.00    59.95    50.00  
   1680x1050     59.96  
   1440x900      59.89  
   1280x1024     75.03    60.00  
   1280x960      60.00  
   1280x720      60.00    59.94    50.00  
   1024x768      75.03    70.07    60.01  
   832x624       75.05  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   720x400       70.04  
   640x480       75.00    72.81    67.06    59.94  

請問一下現在你說螢幕卡著的是指HDMI 還是 DP?

另外, 請問HDMI螢幕是什麼樣的螢幕? 640x350@85 這個解析度似乎不是太常見…

Hi, is DP.I use a chip to split the HDMI signal into two and transmit it to the DVI interface and the HDMI interface to connect the display. Unfortunately, now HDMI and DVI do not have a signal, and they cannot be displayed after being connected to the monitor. During the test, neither HDMI nor DVI had a monitor connected. Although DP has a signal, it will get stuck.
I try to open the Qt program through the serial console, and it returns something like this:

您好,DP卡住了。
是这样的,我采用芯片将HDMI信号一分为二,分别传输至DVI接口和HDMI接口来连接显示器。很可惜,现在HDMI和DVI都没有信号,连接到显示器后都无法显示,在测试的过程中,HDMI和DVI都没有连接显示器。虽然DP有信号,但是会卡住。
我尝试通过serial console 开启Qt程序,会返回如下指令:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
qt.qpa.screen: QXcbConnection: Could not connect to display 
Could not connect to any X display.

Hi,

…這個問題跟螢幕卡住沒有關係. 你的螢幕根本沒卡住
你跑Qt之前本來就也要跑export DISPLAY=:0 不然X display找不到…

還有那個HDMI切成兩個的轉接設計我們這邊不支援. 麻煩不要這樣使用.

And that HDMI 1 to 2 design is not what we support. Please do not use such design.

您好,按照您说的,dp似乎是没有卡住的。原因是HDMI虽然没有输出给显示屏,但是输出给了“HDMI 1to2”的芯片,当插入DP时,系统把DP连接的显示作为扩展显示器了,让我们以为是卡住的状态,但其实没有。非常感谢您的耐心解答,我接下来将继续测试USB等功能。
Hello, as you said, the dp does not seem to be stuck. The reason is that the HDMI signal is not output to the display, but the chip of “HDMI 1to2” is given, and when the DP is plugged in, the system uses the DP-connected display as an extended display, making us think that it is stuck, but it is not. Thank you very much for your patience, I will continue to test USB and other functions next.

1 Like

您好,我不是简单的将HDMI信号1 to 2,而是采用芯片将HDMI 1 to 2,请问这样也不可以吗,但我现在确实想并联几个屏幕同时显示相同内容。谢谢。
Hello, I am not simply dividing HDMI signal 1 to 2, but using the chip to divide HDMI 1 to 2, is this not okay? But I do want to parallel several screens to display the same content at the same time now. Do you have any suggestions, thank you.

我們的driver只支援一個螢幕的edid讀取跟送出信號.

不確定你那個芯片實際上是怎運作的.

USB_schematic.pdf (777.6 KB)

minicom_lsUSB.txt (3.4 KB)

您好,这是关于USB的原理图,和输入lsusb command得到的结果。我在TYPEA USB3.0(原理图中的J32 )的接口插入了一个鼠标,但似乎并没有被识别到。MICRO_B (J28) 似乎可以正常工作。
Hi @WayneWWW , This is the schematic of USB ,and the result of “lsusb”. A mouse was plugged into TYPEA USB 3.0(J32 in schematic ), but it was not recognized and did not work properly. MICRO_B (J28) seems to work fine.

HI, We did not change the schematic given by the official when designing USB, my understanding is that there is no need to change the device tree, but USB is not working now, please give me a little advice.
您好,我们在设计USB的时候没有更改官方给出的原理图,我的理解是不用更改设备树的,但USB现在并没有工作,请您给我一点建议。

Do you get 3.3 V on VDD_3V3_SYS or 3V3_IO_PG? R511 R478 (C339) need to be no stuff. This could be affecting RTS5411S USB3 HUB power on/off control.

Hello, thank you very much for your advice. In my carrier board, R511, R478, C339 are not soldered. VDD_3V3_SYS or 3V3_IO_PG is 3.3V. But my USB didn’t work.
您好,非常感谢您的建议。在我的底板中,R511,R478, C339 没有被焊上。VDD_3V3_SYS or 3V3_IO_PG是3.3v的。但我的USB没有工作。

Please refer to the document here.

https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3261/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/adaptation_and_bringup_nano.html#wwpID0E0DM0HA → porting usb.

Hi,I found that my crystal oscillator is not working. The HUB_XTAL_OUT (pin75) of the RTS5411S-GRT is high.Are you experiencing a similar issue? Thanks!
我发现我的晶振不工作。RTS5411S-GRT的HUB_XTAL_OUT(pin75)为高电平。您有遇到类似的问题嘛?谢谢

I do not have a Realtek source so I opted for no USB 3 HUB. What is the purpose of TPS2051BDBVR by the way? You mentioned MICRO_B (J28) works but I am confused in what capacity?

I suggest reading the doc Wayne posted above.