[U-Boot] Problems with USB mass storage on at91sam9263
I have problems with usb mass storage in u-boot.
We have our own at91sam9263 board, but I experience exactly the same problems on the standard at91sam9263ek. And the usb-port AND memory stick works fine in linux. I have tried both FAT and FAT32. Below follows an edited screendump of some usb commands with a u-boot snapshot version from 13.01.2009.
I have seen that there has been done a lot of work on the usb code in the last months, but it seems to have calmed down. Is the 2009-01-rc1 and/or the current snapshot supposed to work? Is there anything I can do to avoid this problem?
Best regards,
Pål Bakken
And the edited screen-dump:
-----------------------------------------
U-Boot 2009.01-rc1 (jan. 13 2009 - 14:42:22)
DRAM: 64 MB NAND: 256 MiB In: serial Out: serial Err: serial Hit any key to stop autoboot: 1
DUnf-Boot2009> usb start
(Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... ERROR: USB-error: STALL: TD was moved to the Done Queue because the endpoint returned a STALL PID (4) ERROR: USB-error: STALL: TD was moved to the Done Queue because the endpoint returned a STALL PID (4) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) : 225 more of the same error? :-) : ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) Device NOT ready Request Sense returned 00 00 00 1 Storage Device(s) found
DUnf-Boot2009> usb tree
Device Tree: 1 Hub (12MBit/s, 0mA) | OHCI Root Hub | |?-2 Mass Storage (12MBit/s, 100mA) TTI-MSA USB 2.0 Mobile Disk FF04091900068
DUnf-Boot2009> usb info
1: Hub, USB Revision 1.10 - OHCI 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: Mass Storage, USB Revision 2.0 - TTI-MSA USB 2.0 Mobile Disk FF04091900068 - Class: (from Interface) Mass Storage - PacketSize: 64 Configurations: 1 - Vendor: 0x126f Product 0x1325 Version 1.0 Configuration: 1 - Interfaces: 1 Bus Powered 100mA - ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
Interface: 0 - Alternate Setting 0, Endpoints: 3 - Class Mass Storage, Transp. SCSI, Bulk only - ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
- Endpoint 1 In Bulk MaxPacket 64 - Endpoint 2 Out Bulk MaxPacket 64 - Endpoint 3 In Interrupt MaxPacket 2 Interval 1ms
DUnf-Boot2009> usb storage Device 0: Vendor: Rev: Prod: Type: Removable Hard Disk Capacity: not available
Hello,
2009/1/14 Paal Bakken pabakken@online.no:
I have problems with usb mass storage in u-boot. We have our own at91sam9263 board, but I experience exactly the same problems on the standard at91sam9263ek. And the usb-port AND memory stick works fine in linux. I have tried both FAT and FAT32. Below follows an edited screendump of some usb commands with a u-boot snapshot version from 13.01.2009.
The current version should work, indeed a lot has been done in that area for these cores. However, IIRC there were some problems with the bootstrap code not initialising the PLLB correctly, which resulted in similar errors. I thought that Stelian got it to work finally on this particular core as well, so maybe he can confirm this. (I concentrated the patches on the sam9261)
Kind Regards,
Remy
(Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... ERROR: USB-error: STALL: TD was moved to the Done Queue because the endpoint returned a STALL PID (4) ERROR: USB-error: STALL: TD was moved to the Done Queue because the endpoint returned a STALL PID (4) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) : 225 more of the same error? :-) : ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) Device NOT ready Request Sense returned 00 00 00 1 Storage Device(s) found
DUnf-Boot2009> usb tree
Device Tree: 1 Hub (12MBit/s, 0mA) | OHCI Root Hub | |?-2 Mass Storage (12MBit/s, 100mA) TTI-MSA USB 2.0 Mobile Disk FF04091900068
DUnf-Boot2009> usb info
1: Hub, USB Revision 1.10
- OHCI 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: Mass Storage, USB Revision 2.0
- TTI-MSA USB 2.0 Mobile Disk FF04091900068
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x126f Product 0x1325 Version 1.0
Configuration: 1
- Interfaces: 1 Bus Powered 100mA
- ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
Interface: 0 - Alternate Setting 0, Endpoints: 3 - Class Mass Storage, Transp. SCSI, Bulk only - ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
- Endpoint 1 In Bulk MaxPacket 64 - Endpoint 2 Out Bulk MaxPacket 64 - Endpoint 3 In Interrupt MaxPacket 2 Interval 1msDUnf-Boot2009> usb storage Device 0: Vendor: Rev: Prod: Type: Removable Hard Disk Capacity: not available
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
I have testet a lot more and have found the following:
1. I tried an old USB 1.0 stick, but got the same bad result...
2. Then I took that USB 1.0 stick and deleted multiple partitions with linux fdisk and created a single bootable FAT32 partition. This variant worked without any problems in u-boot. (the multiple partitions seems to be typical from the vendors)
3. Then I took the USB 2.0 stick (from the trace in my first mail) and did the same repartioning with fdisk. But this stick still gives the same bad result :-(
So????
Are there any known limitations/requirements to the u-boot USB implementation? -USB1.0 vs USB2.0 -How to partition the stick (if the original partition can't be used) -Other
...and once more: the USB 2.0 stick works fine in linux....
Best regards Pål Bakken
From: Remy Bohmer [linux@bohmer.net] Sent: 2009-01-14 19:53:29 CET To: Paal Bakken [pabakken@online.no] Cc: u-boot@lists.denx.de, Stelian Pop [stelian@popies.net] Subject: Re: [U-Boot] Problems with USB mass storage on at91sam9263
Hello,
2009/1/14 Paal Bakken pabakken@online.no:
I have problems with usb mass storage in u-boot. We have our own at91sam9263 board, but I experience exactly the same problems on the standard at91sam9263ek. And the usb-port AND memory stick works fine in linux. I have tried both FAT and FAT32. Below follows an edited screendump of some usb commands with a u-boot snapshot version from 13.01.2009.
The current version should work, indeed a lot has been done in that area for these cores. However, IIRC there were some problems with the bootstrap code not initialising the PLLB correctly, which resulted in similar errors. I thought that Stelian got it to work finally on this particular core as well, so maybe he can confirm this. (I concentrated the patches on the sam9261)
Kind Regards,
Remy
(Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... ERROR: USB-error: STALL: TD was moved to the Done Queue because the endpoint returned a STALL PID (4) ERROR: USB-error: STALL: TD was moved to the Done Queue because the endpoint returned a STALL PID (4) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) : 225 more of the same error? :-) : ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) Device NOT ready Request Sense returned 00 00 00 1 Storage Device(s) found
DUnf-Boot2009> usb tree
Device Tree: 1 Hub (12MBit/s, 0mA) | OHCI Root Hub | |?-2 Mass Storage (12MBit/s, 100mA) TTI-MSA USB 2.0 Mobile Disk FF04091900068
DUnf-Boot2009> usb info
1: Hub, USB Revision 1.10
- OHCI 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: Mass Storage, USB Revision 2.0
- TTI-MSA USB 2.0 Mobile Disk FF04091900068
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x126f Product 0x1325 Version 1.0
Configuration: 1
- Interfaces: 1 Bus Powered 100mA
- ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
Interface: 0 - Alternate Setting 0, Endpoints: 3 - Class Mass Storage, Transp. SCSI, Bulk only - ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5)
- Endpoint 1 In Bulk MaxPacket 64 - Endpoint 2 Out Bulk MaxPacket 64 - Endpoint 3 In Interrupt MaxPacket 2 Interval 1msDUnf-Boot2009> usb storage Device 0: Vendor: Rev: Prod: Type: Removable Hard Disk Capacity: not available
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
On 22:30 Wed 14 Jan , Paal Bakken wrote:
I have testet a lot more and have found the following:
I tried an old USB 1.0 stick, but got the same bad result...
Then I took that USB 1.0 stick and deleted multiple partitions with linux fdisk and created a single bootable FAT32 partition. This variant worked without any problems in u-boot. (the multiple partitions seems to be typical from the vendors)
Then I took the USB 2.0 stick (from the trace in my first mail) and did the same repartioning with fdisk. But this stick still gives the same bad result :-(
So????
Are there any known limitations/requirements to the u-boot USB implementation? -USB1.0 vs USB2.0 -How to partition the stick (if the original partition can't be used) -Other
...and once more: the USB 2.0 stick works fine in linux....
I'll take a look on my 9263ek
but I've test recently a 4GB usb 2.0 key on the at91rm9200ek with any problem
btw please limit your mail at 80chars per line
Best Regards, J.
More testing....
It seems like I have one stick that generates the reported error. And this is of course THE one I have been testing with (Murphy is never resting...)
I have tried with four devices now USB 1.0 128MB : Had to repartition USB 2.0 512MB : Gives the reported problems (fine in linux and windows) USB 2.0 2GB : Works without partitioning USB 2.0 16GB: Works without partitioning
The response is the same on our own at91sam9263 board with 18.432MHz ocillator and the original at91sam9263ek with 16.36766MHz
So - I'm willing to rest my case :-) BUT there is something strange, since the "bad" stick works fine in Linux and Windows... -Any ideas about possible reasons for the difference? -Is there any specific known requirements for the sticks (except for FAT)
Best regards Pål Bakken
From: Jean-Christophe PLAGNIOL-VILLARD [plagnioj@jcrosoft.com] Sent: 2009-01-14 22:24:22 CET To: Paal Bakken [pabakken@online.no] Cc: Remy Bohmer [linux@bohmer.net], u-boot@lists.denx.de Subject: Re: [U-Boot] Problems with USB mass storage on at91sam9263
On 22:30 Wed 14 Jan , Paal Bakken wrote:
I have testet a lot more and have found the following:
I tried an old USB 1.0 stick, but got the same bad result...
Then I took that USB 1.0 stick and deleted multiple partitions with linux fdisk and created a single bootable FAT32 partition. This variant worked without any problems in u-boot. (the multiple partitions seems to be typical from the vendors)
Then I took the USB 2.0 stick (from the trace in my first mail) and did the same repartioning with fdisk. But this stick still gives the same bad result :-(
So????
Are there any known limitations/requirements to the u-boot USB implementation? -USB1.0 vs USB2.0 -How to partition the stick (if the original partition can't be used) -Other
...and once more: the USB 2.0 stick works fine in linux....
I'll take a look on my 9263ek
but I've test recently a 4GB usb 2.0 key on the at91rm9200ek with any problem
btw please limit your mail at 80chars per line
Best Regards, J.
Hello,
So - I'm willing to rest my case :-) BUT there is something strange, since the "bad" stick works fine in Linux and Windows... -Any ideas about possible reasons for the difference?
There has been many improvements to the USB stack lately that at least it works nowadays on these cores. However, there are still a number of bugs to solve, so we are not there yet. Besides, the USB stack only supports a single device at a time, and does not really support hotplug, it is a completely different USB stick than Linux is currently using. The FAT driver also only supports read-only.
So, you cannot really compare the U-boot USB stack with the Linux/Windows stack. It shows, however, that there are still bugs in the U-boot USB/FAT code.
-Is there any specific known requirements for the sticks (except for FAT)
FAT32 and VFAT should also work, but if I knew the exact 'requirements', I also knew how to solve the bugs...
Kind Regards,
Remy
I also found another non-working stick.... This one was also a first generation USB 2.0 stick.
But anyway - It seems like you guys has done a great job and made usb mass storage useful! A few non-working sticks is good enough for me :-)
Best regards
Pål Bakken
From: Remy Bohmer [linux@bohmer.net] Sent: 2009-01-15 13:03:20 CET To: Paal Bakken [pabakken@online.no] Cc: Jean-Christophe PLAGNIOL-VILLARD [plagnioj@jcrosoft.com], u-boot@lists.denx.de Subject: Re: [U-Boot] Problems with USB mass storage on at91sam9263
Hello,
So - I'm willing to rest my case :-) BUT there is something strange, since the "bad" stick works fine in Linux and Windows... -Any ideas about possible reasons for the difference?
There has been many improvements to the USB stack lately that at least it works nowadays on these cores. However, there are still a number of bugs to solve, so we are not there yet. Besides, the USB stack only supports a single device at a time, and does not really support hotplug, it is a completely different USB stick than Linux is currently using. The FAT driver also only supports read-only.
So, you cannot really compare the U-boot USB stack with the Linux/Windows stack. It shows, however, that there are still bugs in the U-boot USB/FAT code.
-Is there any specific known requirements for the sticks (except for FAT)
FAT32 and VFAT should also work, but if I knew the exact 'requirements', I also knew how to solve the bugs...
Kind Regards,
Remy
On Wed, Jan 14, 2009 at 07:53:29PM +0100, Remy Bohmer wrote:
Hello,
Hi,
2009/1/14 Paal Bakken pabakken@online.no:
I have problems with usb mass storage in u-boot. We have our own at91sam9263 board, but I experience exactly the same problems on the standard at91sam9263ek. And the usb-port AND memory stick works fine in linux. I have tried both FAT and FAT32. Below follows an edited screendump of some usb commands with a u-boot snapshot version from 13.01.2009.
The current version should work, indeed a lot has been done in that area for these cores. However, IIRC there were some problems with the bootstrap code not initialising the PLLB correctly, which resulted in similar errors. I thought that Stelian got it to work finally on this particular core as well, so maybe he can confirm this. (I concentrated the patches on the sam9261)
I do reproduce exactly the same kind of problems here. As I originally said in my October 9 mail (Message-Id: 1223564465.6130.20.camel@galileo), correcting the bootstrap PLLB settings made USB work, but USB storage did work only with one of my three USB sticks.
I suspect the rest of the issues to be USB specific and not hardware specific at this point, but I haven't looked closer into it.
Stelian.
participants (4)
-
Jean-Christophe PLAGNIOL-VILLARD -
Paal Bakken -
Remy Bohmer -
Stelian Pop