10-29-2020, 04:50 AM
I agree with your claim
The content you pointed out is PCIEx and USB 2 items.
But, Here, I will give my view only on USB.
[Symptoms]
1. USB drive cannot be detected
I checked with 7 enclosures.
All are products of different manufacturers or models, not the same model
The breakdown of the 7 units I confirmed is as follows
・ 4 units using JMicron devices.
・ 3 units using ASMedia devices.
Two enclosures using ASMedia devices could be detected.
All enclosures using JMicron devices could not be detected.
2. Stack just before kernel boots
If a USB device is connected to the USB 2.0 port
・ Regardless of device type (For example: mouse or keyboard, etc.)
This symptom occurs.
This is a problem with U-Boot software.
---
[Workaround]
1. USB drive cannot be detected
When the enclosure is connected via a "self-powered" USB3.0-HUB,
All of the above 7 units can be detected now.
* I think it is important to be a Self-Powered HUB
Because I don't think that improvement can be expected when using BUS-Powered HUB.
Therefore, I haven't dared to try it.
2. Stack just before kernel boots
Do not connect any kind of device to the USB 2.0 port.
---
[Other]
About power supply
According to the official standard, the current supply capacity required for VBUS is
500mA for USB2.0 / 900mA for USB3.0
It is stipulated as.
On the other hand, the design value of Rockpro64 is 750mA for USB2.0 / 1450mA for USB3.0 (see the circuit diagram).
Also, according to the data sheet of the relevant part (SY6280AAC), the variation error is about +- 25%, so
It is designed to meet the official standards even in the worst case.
Next is the HDD drive.
The standard HDD device requires the maximum current when the motor starts up.
The value is about 1000mA for a standard 2.5-inch drive.
The supply capacity of the USB 2.0 port is 500mA according to the official standard, so
If you connect a 2.5 HDD to the USB 2.0 port, it can't be helped even if it doesn't work.
(* If there are no other problems,
For devices with relatively low current consumption, such as "SSD / USB-Sitck", we can expect it to work properly.
However, due to the problem of "2. Stack just before kernel boot", it will stack with high probability.
)
This means that no matter how powerful an external power supply is prepared, the effect commensurate with it cannot be obtained.
Because the current supply capacity of VBUS is limited on the board by the value according to the official standard.
It is natural that even if the external power supply is strengthened more than necessary, there is no effect.
On the other hand, the USB3.0 port has a current supply capacity of 1000mA or more, so
If it is a standard 2.5 inch drive, most of it will work.
---
You insist in this thread that "there is no problem with the power supply".
I also agree with your claim.
The symptom you pointed out is
"U-Boot has not yet reached a sufficient level of perfection"
It is due to that.
------
The following is a log when three 2.5-HDDs are connected via USB3.0-HUB.
A mouse is connected to the USB 2.0 port to confirm the problem.
In this case, I have a very high probability of encountering a "stack befor kernel boot" issue.
If I disconnect the device from the USB 2.0 port, it is boot properly.
* The "U-Boot" I used to check the operation was obtained from the following github tree.
"U-boot-ci-2020.10-rockpro64-spi"
I used the one that got the above and built it.
The content you pointed out is PCIEx and USB 2 items.
But, Here, I will give my view only on USB.
[Symptoms]
1. USB drive cannot be detected
I checked with 7 enclosures.
All are products of different manufacturers or models, not the same model
The breakdown of the 7 units I confirmed is as follows
・ 4 units using JMicron devices.
・ 3 units using ASMedia devices.
Two enclosures using ASMedia devices could be detected.
All enclosures using JMicron devices could not be detected.
2. Stack just before kernel boots
If a USB device is connected to the USB 2.0 port
・ Regardless of device type (For example: mouse or keyboard, etc.)
This symptom occurs.
This is a problem with U-Boot software.
---
[Workaround]
1. USB drive cannot be detected
When the enclosure is connected via a "self-powered" USB3.0-HUB,
All of the above 7 units can be detected now.
* I think it is important to be a Self-Powered HUB
Because I don't think that improvement can be expected when using BUS-Powered HUB.
Therefore, I haven't dared to try it.
2. Stack just before kernel boots
Do not connect any kind of device to the USB 2.0 port.
---
[Other]
About power supply
According to the official standard, the current supply capacity required for VBUS is
500mA for USB2.0 / 900mA for USB3.0
It is stipulated as.
On the other hand, the design value of Rockpro64 is 750mA for USB2.0 / 1450mA for USB3.0 (see the circuit diagram).
Also, according to the data sheet of the relevant part (SY6280AAC), the variation error is about +- 25%, so
It is designed to meet the official standards even in the worst case.
Next is the HDD drive.
The standard HDD device requires the maximum current when the motor starts up.
The value is about 1000mA for a standard 2.5-inch drive.
The supply capacity of the USB 2.0 port is 500mA according to the official standard, so
If you connect a 2.5 HDD to the USB 2.0 port, it can't be helped even if it doesn't work.
(* If there are no other problems,
For devices with relatively low current consumption, such as "SSD / USB-Sitck", we can expect it to work properly.
However, due to the problem of "2. Stack just before kernel boot", it will stack with high probability.
)
This means that no matter how powerful an external power supply is prepared, the effect commensurate with it cannot be obtained.
Because the current supply capacity of VBUS is limited on the board by the value according to the official standard.
It is natural that even if the external power supply is strengthened more than necessary, there is no effect.
On the other hand, the USB3.0 port has a current supply capacity of 1000mA or more, so
If it is a standard 2.5 inch drive, most of it will work.
---
You insist in this thread that "there is no problem with the power supply".
I also agree with your claim.
The symptom you pointed out is
"U-Boot has not yet reached a sufficient level of perfection"
It is due to that.
------
The following is a log when three 2.5-HDDs are connected via USB3.0-HUB.
A mouse is connected to the USB 2.0 port to confirm the problem.
In this case, I have a very high probability of encountering a "stack befor kernel boot" issue.
If I disconnect the device from the USB 2.0 port, it is boot properly.
* The "U-Boot" I used to check the operation was obtained from the following github tree.
"U-boot-ci-2020.10-rockpro64-spi"
I used the one that got the above and built it.
Code:
U-Boot TPL 2020.10 (Oct 28 2020 - 18:33:53)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.10 (Oct 28 2020 - 18:33:53 +0900)
Trying to boot from SPI
NOTICE: BL31: v2.3(release):bd260fc
NOTICE: BL31: Built : 08:29:28, Oct 24 2020
NOTICE: BL31: Rockchip release version: v1.1
...
...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus usb@fe3a0000: USB OHCI 1.0
Bus usb@fe3c0000: USB EHCI 1.00
Bus usb@fe3e0000: USB OHCI 1.0
Bus dwc3@fe800000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus dwc3@fe900000: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus usb@fe3a0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3c0000 for devices... 1 USB Device(s) found
scanning bus usb@fe3e0000 for devices... 1 USB Device(s) found
scanning bus dwc3@fe800000 for devices... 1 USB Device(s) found
scanning bus dwc3@fe900000 for devices... cannot reset port 1!?
Device not responding to set address.
USB device not accepting new address (error=80000000)
cannot reset port 3!?
6 USB Device(s) found
scanning usb for storage devices... 3 Storage Device(s) found
Hit any key to stop autoboot: 0
=> usb stor
Device 0: Vendor: WDC WD50 Rev: 0 Prod: 00BEVT-75A0RT0
Type: Hard Disk
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Device 1: Vendor: WDC WD16 Rev: 8101 Prod: 00BEVT-26ZCT0
Type: Hard Disk
Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
Device 2: Vendor: ASMT Rev: 0 Prod: 2115
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
=> usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
u-boot EHCI Host Controller
1 Hub (12 Mb/s, 0mA)
U-Boot Root Hub
1 Hub (480 Mb/s, 0mA)
| u-boot EHCI Host Controller
|
+-2 Hub (480 Mb/s, 100mA)
| USB2.0 HUB
|
+-3 Human Interface (1.5 Mb/s, 98mA)
G-Tech Wireless Dongle
1 Hub (12 Mb/s, 0mA)
U-Boot Root Hub
1 Hub (5 Gb/s, 0mA)
U-Boot XHCI Host Controller
1 Hub (5 Gb/s, 0mA)
| U-Boot XHCI Host Controller
|
+-2 Hub (5 Gb/s, 0mA)
| |
| +-4 Mass Storage (5 Gb/s, 224mA)
| | Jmicron External Disk 3.0 987654321010
| |
| +-5 Mass Storage (5 Gb/s, 2mA)
| | Jmicron USB3.0 External HDD 873930CE4
| |
| +-6 Mass Storage (5 Gb/s, 0mA)
| ASMT ASM105x 00000000000000000000
|
+-3 Hub (480 Mb/s, 0mA)
=> run bootcmd_usb0
...