after Qi no USB in Nor questions - solved

C R McClenaghan chris at mcclenaghan.com
Tue Feb 17 00:13:22 CET 2009


On Feb 16, 2009, at 9:56 AM, C R McClenaghan wrote:

> All,
>
> I have a Neo Freerunner GTA02V5 to which I apparently flashed Qi  
> some weeks ago. I'm not sure which version of FSO is flashed to  
> memory, but I think it is milestone 3. In installing Qi, I think I  
> may have been trying to recover from modifications made to uboot for  
> Debian and probably ran the devirginator process to flash uboot  
> before I went ahead and flashed Qi. I no longer recall why I did  
> either.
>
> And now, I'm a little confused as to how to proceed as I can no  
> longer flash with dfu-util. When I boot to Nor and plug in the USB  
> cable, I get a series of errors on my host and cannot use dfu-util.  
> The errors are these:
>
> [   87.928631] usb 1-1: new full speed USB device using uhci_hcd and  
> address 3
> [   88.540254] usb 1-1: unable to read config index 0 descriptor/ 
> start: -71
> [   88.540437] usb 1-1: chopping to 0 config(s)
> [   88.695904] usb 1-1: string descriptor 0 read error: -71
> [   88.698093] usb 1-1: string descriptor 0 read error: -71
> [   88.700419] usb 1-1: string descriptor 0 read error: -71
> [   88.734000] usb 1-1: no configuration chosen from 0 choices
> [   88.736092] usb 1-1: USB disconnect, address 3
> [   89.084376] usb 1-1: new full speed USB device using uhci_hcd and  
> address 4
> [   89.692859] usb 1-1: invalid descriptor for config index 1: type  
> = 0x2, length = 0
> [   89.692909] usb 1-1: can't read configurations, error -22
> [   89.912237] usb 1-1: new full speed USB device using uhci_hcd and  
> address 5
> [   90.420975] usb 1-1: invalid descriptor for config index 1: type  
> = 0x2, length = 0
> [   90.421000] usb 1-1: can't read configurations, error -22
> [   90.641355] usb 1-1: new full speed USB device using uhci_hcd and  
> address 6
> [   90.676829] usb 1-1: invalid descriptor for config index 1: type  
> = 0x2, length = 0
> [   90.676850] usb 1-1: can't read configurations, error -22
> [   90.900242] usb 1-1: new full speed USB device using uhci_hcd and  
> address 7
> [   90.939088] usb 1-1: invalid descriptor for config index 1: type  
> = 0x2, length = 0
> [   90.939111] usb 1-1: can't read configurations, error -22
> [   90.940610] hub 1-0:1.0: unable to enumerate USB device on port 1
>
> This occurs whether the Freerunner is attached to the host first or  
> not.
>
> Note: when booted into installed image, USB networking is fine and  
> the above errors do not occur. Is this a host side problem or Neo  
> Freerunner problem?
>
> I notice in the Qi documentation that there is no dfu-util support.  
> Would that effect dfu-util in Nor?
>
> When I do attempt to boot into Nand, I end up with a Nor boot menu  
> that is the same as when I boot into Nor - apparently either why the  
> AUX/Power button are selected I boot to Nor. Is that correct  
> behavior with Qi?
>
> BTW - my Nor boot menu seems slightly different than what I see on  
> the wiki - rather than a Reset option in the fifth position I have  
> Reboot.
>
> Are there any log or configuration files I should post to help  
> diagnosis?
>
> I would like to be able to upgrade the release in memory or for that  
> matter Qi - which I think I'm now blocked from doing.
>
> Is there an alternative to the "devirginator" process to restore the  
> Freerunner to "factory" state?
>
> Thanks,
>
> Chris
>

All,

Seems my problem may be VMWare Fusion. My host for Openmoko work is  
Ubuntu (currently 8.10) as a vm on my MacBook Pro running Leopard  
10.5.6. Returning to the pure Leopard environment I'm able to use  
OpenMoko Flasher and it dfu-util to access the USB port. I'm guessing  
either something in Ubuntu 8.10 and/or VMWare is causing the DFU  
capability to be corrupted and therefore not work, although as late as  
December it seemed to work just fine.

So, I've upgrade both my distributions and bootloader and seem to have  
no problem at this point other than the slowness of flashing.

Thanks to all who read this far,

Chris





More information about the community mailing list