NeoTool/dfu-util bug - No such Alternate Setting: "rootfs"

Dale Maggee antisol at internode.on.net
Thu Nov 6 16:40:07 CET 2008


Hi,

Are you using the latest version of NeoTool? v1.1 and up should be able 
to detect and handle this situation by presenting you with a screen 
asking you which dfu-capable device you want to flash.

If you are using the latest version, please run 'dfu-util -l' and post 
the output here.

Regards,
-Dale

Mikko Ohtamaa wrote:
> Symptoms dfu-util/Neotool fails to flash Openmoko when using wiki.openmoko.org
> instructions:
>
> sudo ./dfu-util.1 -a rootfs -R -D Fat_and_Dirty_OM.200809_20081023.rootfs.jffs2 
> dfu-util - (C) 2007 by OpenMoko Inc.
> This program is Free Software and has ABSOLUTELY NO WARRANTY
>
> Opening USB Device 0x0000:0x0000...
> Claiming USB DFU Runtime Interface...
> Determining device status: state = dfuIDLE, status = 0
> WARNING: Runtime device already in DFU state ?!?
> No such Alternate Setting: "rootfs"
>
> Cause: 
>
> Neotool/dfu-util automatically picks wrong USB device - it must pick this one 
>
> Found DFU Runtime: [0x1457:0x5119] devnum=0, cfg=0, intf=2, alt=0, name="USB
> Device Firmware Upgrade"
>
> In my case, the wrong device was something built into my laptop:
>
> Bus 005 Device 003: ID 03f0:181d Hewlett-Packard 
>
> Workaround:
>
> Use dfu-util -d parameter to specify device id manually.
>
>
>
>
> _______________________________________________
> Openmoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>   





More information about the community mailing list