Openmoko Bug #2348: dfu-util shows only one partition
Openmoko Public Trac
bugs at docs.openmoko.org
Fri Jul 30 17:23:56 CEST 2010
#2348: dfu-util shows only one partition
----------------------------+-----------------------------------------------
Reporter: gravis | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: host utilities | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
----------------------------+-----------------------------------------------
Comment(by gravis):
With the kernel 2.6.32-24 it started to working.. but differently?
Ok I know how all those things work now.
{{{
Found Runtime: [0x1d50:0x5119] devnum=1, cfg=0, intf=2, alt=0, name="USB
Device Firmware Upgrade"
}}}
See that intf=2 and cfg=0 ? Now compare this to my lsusb output.
This means that output was taken from first configuration
(bConfigurationValue 1), third interface (bInterfaceNumber 2), interface
is named "USB Device Firmware Upgrade"
But in fact, when OM is flashed it shows
{{{
Found Runtime: [0x1d50:0x5119] devnum=2, cfg=0, intf=0, alt=0,
name="rootfs"
}}}
Which is first configuration (bConfigurationValue 1), first interface
(bInterfaceNumber 0), which is AT-commands (v.25ter) Control Interface.
So different protocol is used to list partitions (UDF), and different one
to flash them (AT terminal upload (?)).
Once we force dfu-util to use interface 0 it will show all the partitions
(coming from AT query, rather than innacurate DFU).
so
{{{
dfu-util --intf 0 -l
}}}
should shows correct partitions and all flashing commands should have
--intf 0 option.
the problem is dfu-util ignores --intf 0 during listing..
but during flashing it works like a charm!
Conclusion:
always use --intf 0 when flashing with dfu-util.
[solved]
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2348#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the devel
mailing list