The Kingston memory got a LED, which blink when plugged for normal use, may be while reading. With the new ftd it doesn't do anything.
Anyway this is a little issue, for my usage may not be urgent.
There was a time that the u-boot didn't find mmc then triyng to probe the USB. This time with the UMS plugged I get this$this->bbcode_second_pass_code('', 'PC event = 0x0
usb_current_limit_ctrl: unlock_current = 0')
I stopped the autoboot and checking$this->bbcode_second_pass_code('', '=> usb start
starting USB...
USB0: USB1: scanning bus 0 for devices... 3 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
=> usb info
1: Hub, USB Revision 1.10
- U-Boot Root Hub
- Class: Hub
- PacketSize: 8 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 0.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 2 Interval 255ms
2: Hub, USB Revision 2.0
- USB2.0 Hub
- Class: Hub
- PacketSize: 64 Configurations: 1
- Vendor: 0x05e3 Product 0x0610 Version 50.152
Configuration: 1
- Interfaces: 1 Self Powered Remote Wakeup 100mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms
- Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms
3: Mass Storage, USB Revision 2.0
- Kingston DataTraveler 2.0 000AEB920172SK861C01001F
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x0951 Product 0x1607 Version 2.0
Configuration: 1
- Interfaces: 1 Bus Powered 200mA
Interface: 0
- Alternate Setting 0, Endpoints: 2
- Class Mass Storage, Transp. SCSI, Bulk only
- Endpoint 1 In Bulk MaxPacket 512
- Endpoint 2 Out Bulk MaxPacket 512
1: Hub, USB Revision 1.10
- U-Boot Root Hub
- Class: Hub
- PacketSize: 8 Configurations: 1
- Vendor: 0x0000 Product 0x0000 Version 0.0
Configuration: 1
- Interfaces: 1 Self Powered 0mA
Interface: 0
- Alternate Setting 0, Endpoints: 1
- Class Hub
- Endpoint 1 In Interrupt MaxPacket 2 Interval 255ms
')
Hence, as I can see, the u-boot doesn't fail to handle the usb. I think it might be a missing bit to pass to the kernel.
Later I'll experiment to revert the
usb declarations from the rk3288-miniarm to the rk3288-tinkerS. the miniarm is the working one.
EDITI modified the
dtf, but I did it with poor knowledge.
Then are coming some error$this->bbcode_second_pass_code('', '[ 4.267610] OF: /usb@ff540000: could not get #phy-cells for /qos@ffad0100
[ 4.275908] OF: /usb@ff580000: could not get #phy-cells for /qos@ffad0180
[ 4.285058] OF: /usb@ff500000: could not get #phy-cells for /qos@ffad0000')