Ticket #604 (closed defect: wontfix)

Opened 11 years ago

Last modified 9 years ago

DFU at bootdelay conflicts with normal boot nand read

Reported by: elrond+bugzilla.openmoko.org@… Owned by: openmoko-kernel
Priority: normal Milestone:
Component: kernel Version: unspecified
Severity: minor Keywords: bootloader
Cc: buglog@…, werner@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:


I've set bootdelay to something like 7 or 8 seconds, so I don't have to use the
AUX button every time I want to get into u-boot.
This time also allows to fire up dfu and load a new kernel into RAM and boot it
there from u-boot.


  • power Neo on (or reboot)
  • Use dfu-util to download other kernel into RAM, while bootdelay...
  • picocom into u-boot to boot the kernel (will fail, as the memory is half overwirrten by the nand read)


  • power Neo on
  • picocom into u-boot to interrupt bootdelay
  • dfu-util
  • picocom again into u-boot
  • boot kernel

(1) gives the error as shown in the pic.
(2) works nicely.

Note1: this bug is a bit related to #207.
Note2: I set this bug to minor and lower prio, as a documented (in this bug)
workaround exists.

Change History

comment:1 Changed 11 years ago by werner@…

  • Cc werner@… added

As a workaround, you could just bring up the boot menu (by holding down
AUX while u-boot starts). That keeps the system from autobooting. DFU
subsequently disables the idle timeout of the boot menu itself.

comment:2 Changed 10 years ago by willie_chen@…

  • Owner changed from laforge@… to michael@…

comment:3 Changed 10 years ago by roh

  • Owner changed from michael@… to michael

comment:4 Changed 9 years ago by john_lee

  • Status changed from new to assigned
  • Owner changed from michael to openmoko-kernel
  • HasPatchForReview unset
  • Component changed from u-boot to System Software

Reassign to michael@… used to indicate we leave this to the community and we won't work on it. Obviously nothing is happening to these tickets, so I reassign this to openmoko-kernel for now. If we decided we won't do it, then resolve as 'community'.

comment:5 Changed 9 years ago by werner

I'd say that we bounce it back to the community. There's a good work-around
for the problem, fixing it properly would be hard (i.e., DFU and u-boot's
main "thread" would have to be synchronized, a task for which hardly any
infrastructure exists in u-boot) and may introduce new problems (i.e., if
interrupt latency is increased, USB may be unhappy), and we're moving away
from u-boot anyway.

comment:6 Changed 9 years ago by marek

  • Keywords bootloader added

comment:7 Changed 9 years ago by andy

  • Status changed from assigned to closed
  • Resolution set to wontfix

I think it only became less likely we address this guy since Werner's comment, and considering we move to Qi on GTA03: closing as WONTFIX.

Note: See TracTickets for help on using tickets.