From mboxrd@z Thu Jan 1 00:00:00 1970 From: Remy Bohmer Date: Sat, 14 Mar 2009 09:51:28 +0100 Subject: [U-Boot] At91 mass storage device In-Reply-To: <3972542e0903131200w4b0834d2i55729923e5fb823a@mail.gmail.com> References: <3972542e0903121003g64829f70j4e0a6a3a2db2a89b@mail.gmail.com> <3efb10970903121349x23cfd84k8059e98ba04c7029@mail.gmail.com> <3972542e0903121445k60c4d2b2t4a3cf7f7505039fd@mail.gmail.com> <3efb10970903121550q5ef9a8b5ge589f7605c4a423a@mail.gmail.com> <3972542e0903130919h2eaa9d2dge30b78a9fb6421c3@mail.gmail.com> <3972542e0903131200w4b0834d2i55729923e5fb823a@mail.gmail.com> Message-ID: <3efb10970903140151n486fe667qc54a65a2f7aa4f5f@mail.gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello, > I decided to do some digging and I see the not responding error reported below. > I added a wait of 2ms to the ?*dl_reverse_done_list(ohci_t *ohci) > loop. I'm not sure > how this affects everything else. > However, although I did not get the no response error, I did get the > STALL PID error. The device not responding error is one of the weird things I talked about. Some USB-sticks happen to do that, have you tried a different stick? This is a workaround, but if you find out what really goes wrong here, I would be happy to hear it. The stall state of the device not handled in U-boot at all, the USB-stack of U-boot does not recover from this, it has to be implemented. Once the device returns the stall state, the only thing that can be done is to restart all over. (reset) Kind Regards, Remy