[Gta04-owner] Trying to flash U-Boot led to a bricked device
andreas at kemnade.info
Mon Mar 12 22:35:25 CET 2018
On Sun, 11 Mar 2018 19:18:04 +0100
Andreas Kemnade <andreas at kemnade.info> wrote:
> On Sun, 11 Mar 2018 18:34:23 +0100
> cnut <cnut at posteo.de> wrote:
> > Hello Nikolaus,
> > Hello Andreas,
> > the good news: with the tutorial of Nikolaus, dmesg shows that the
> > device is alive...
> > [ 2895.846968] usb 1-4: new high-speed USB device number 4 using xhci_hcd
> > [ 2895.987845] usb 1-4: unable to get BOS descriptor
> > [ 2895.988919] usb 1-4: New USB device found, idVendor=0451, idProduct=d00e
> > [ 2895.988932] usb 1-4: New USB device strings: Mfr=33, Product=37,
> > SerialNumber=0
> > [ 2895.988941] usb 1-4: Product: OMAP3630
> > [ 2895.988949] usb 1-4: Manufacturer: Texas Instruments
> > [ 2898.990793] usb 1-4: USB disconnect, device number 4
> > usb-starts-uboot shows only:
> > # ./usb-start-uboot.sh
> > Power on you gta04 with aux button pressed
> > Waiting for USB device vendorID=0x451 and productID=0xD009:
> It has to be run *before* powering on the gta04 to start uboot
maybe I should have clearly mention that.
That step by step guide was really meant to be done step by step.
First thing is to get a running uboot. Transmission can only start in
the few seconds when the gta04 appears on the bus. But the script will
wait for it to appear.
> > dfu-util -l shows not a sign from the gta04 too (no "Found DFU ...").
> > usb-flash-uboot-gta04.sh does not run too:
> > # ./usb-flash-uboot-gta04.sh nand uboot_files/
And that would flash the uboot (and resets the environment).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Gta04-owner