[Bug 899] New: U-boot seems to trash another partition on upload...?

bugzilla-daemon at bugzilla.openmoko.org bugzilla-daemon at bugzilla.openmoko.org
Sun Sep 30 04:48:53 CEST 2007


           Summary: U-boot seems to trash another partition on upload...?
           Product: OpenMoko
           Version: 2007.2
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dfu-util
        AssignedTo: laforge at openmoko.org
        ReportedBy: developer at linuxmontreal.com
                CC: buglog at lists.openmoko.org

I've got two GTA01Bv4 Neo's. One came as an Advanced kit the other as a Basic kit. 


Device 1 -> The basic kit came flashed with a 6 item boot menu, openmoko boot
splash image and whatever roofs.

Device 2 -> The advanced kit neo came with a two item boot menu and simply shows
fb penguin on boot.

Both devices successfully boot new-ish kernels, bootloaders and rootfs and
currently have U-boot 1.3.0-rc11.2.0+git20070917+svn2943 (Sept 17 2007 -
23:42:04) and uImage-


So instead of learning the uboot environ variables tonight (it's saturday night,
beer night) I just decided to use dfu-util to upload the uboot_env and splash
partitions from the first device to the second device.

1. After downloading (host->neo) the uboot_env partition data, which I uploaded
(neo->host) from device 1, device 2 now has 6 menu items but the kernel
partition now has bad magic suggesting that the download of the uboot_env
partition data has trashed the uImage partition.

Downloading the uImage again rectifies this situation.

2. After downloading (host->neo) the splash partition data onto device 2, which
I uploaded (neo->host) from device 1, device has backlit but blank screen. So I
ungziped (with trailing garbage) and then re-gziped the splash image and upload,
I now have a splash on device 2.

It does not seem that I need to re-download the rootfs after downloading the splash.

Granted, I have not done any boot prompt nand erasing... is this a bug or am I
just forgetting something?

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the buglog mailing list