[Gta04-owner] successful boot from usb

Andreas Kemnade andreas at kemnade.info
Thu Nov 23 22:41:16 CET 2017


Hi,

now I managed to drill through the more thick wall of going this way:
- start pusb
- power on gta04 with aux pressed
- pusb loads SPL
- load uboot using dfu-util

- load kernel and stuff using dfu-utils (well, you could also load
  commands here to initialize nand, etc).

U-Boot SPL 2016.11-01300-gc2af91d548-dirty (Nov 23 2017 - 22:27:26)
Trying to boot from USB DFU
Using default environment

ERROR: "dfu_alt_info" env variable not defined!

at common/spl/spl_dfu.c:45/spl_dfu_cmd()
got dfu_alt_info uboot ram 0x83000000 0x800000
musb-hdrc: peripheral reset irq lost!
####DOWNLOAD ... OK
Ctrl+C to exit ...
Unknown command 'run' - try 'help'
Legacy image
spl: payload image: load addr: 0x800fffc0 size: 409808
Jumping to U-Boot
loaded - jumping to U-Boot...

U-Boot 2016.11-01300-gc2af91d548-dirty (Nov 23 2017 - 22:27:26 +0100)

OMAP3630/3730-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
GTA04 + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0
Using default environment

OMAP die ID: 144200229ff800000163810c1901301f
Found GTA04A4
Device Tree: omap3-gta04a4.dtb
Net:   usb_ether
Error: usb_ether address not set.

Hit any key to stop autoboot:  0 
got dfu_alt_info kernel ram 0x82000000 0x800000;fdt ram 0x81c00000 0x40000;rd ram 0x83000000 0x4000000;script ram 0x80800000 0x40000;bootscript ram 0x81800000 0x40000
musb-hdrc: peripheral reset irq lost!
#DOWNLOAD ... OK
Ctrl+C to exit ...
#DOWNLOAD ... OK
Ctrl+C to exit ...
#DOWNLOAD ... OK
Ctrl+C to exit ...
## Executing script at 80800000
## Error: "mmcargs" not defined
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-4.14.0-letux+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4662336 Bytes = 4.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 81c00000
   Booting using the fdt blob at 0x81c00000
   Loading Kernel Image ... OK
   Loading Device Tree to 8ffea000, end 8ffff435 ... OK

Starting kernel ...

... (no further output here because I set console=tty0)

Next step: cleaning up patches, etc.

Regards,
Andreas

On Mon, 20 Nov 2017 22:30:53 +0100
Andreas Kemnade <andreas at kemnade.info> wrote:

> On Mon, 20 Nov 2017 12:40:07 +0100
> Andreas Kemnade <andreas at kemnade.info> wrote:
> [...]
> > > > 
> > > > After I changed that base address, I could load a recent spl from usb.
> > > > I managed to load uboot via ymodem (not that strange kermit anymore) via rs232.
> > > > Next step would be to enable dfu in spl. There is an option in uboot for that.
> > > > But I do not manage to compile u-boot that way.
> > > > 
> > > > But what can be more easily managed: Compile dfu into main uboot (well,
> > > > you have to first enable the dfu command, then you can open the dfu menu in uboot menuconfig),
> > > > so it can be enabled on a button in the menu.
> > > > Access to mmc and to ram seems to work, access to onenand cannot be enabled.
> > > > But with dfu to ram, you can e.g. load kernel, fdt and a ramdisk and a script to ram.
> > > > Or load other things to ram and flash it to nand using that script.
> > > > So with that you can basically do a lot of things.      
> > > 
> > > Wow, cool work!
> > > 
> > > If you have patches for our u-boot git (that do not break OMAP4 & OMAP5), we can integrate them.
> > >     
> > For the dfu in main u-boot it should be not critical,
> > dfu in uboot is only started via a command, so if not used, it will not harm.
> > 
> > I'll put them in separate branches.
> >   
> In
> work/kemnade/dfu_in_main_uboot
> there is now everything need for the main uboot to work properly with
> dfu.
> 
> dfu to ram mode is activated by button 7
> You can use it like this:
> dfu-util -a kernel -D uImage
> dfu-util -a fdt -D omap3-gta04a4.dtb
> dfu-util -a rd -D initrd.img
> dfu-util -a script -D bootkernel.scr -R
> 
> The script can contain things like:
> setenv bootargs ...
> bootm ${loadaddr} ${loadaddrinitrd} ${loadaddrfdt}
> 
> initrd.img might be something like
> cat hw-tester.cpio modules.cpio | gzip >initrd
> and then a mkimage run to create initrd.img from that.
>  
> There is a mmc mode on button 8 (well, it is not that useful)
> 
> nand is not activated because the dfu nand seems not to work with
> onenand, so it is easier to load stuff to ram and execute a script then.
> 
> Regards,
> Andreas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.goldelico.com/pipermail/gta04-owner/attachments/20171123/0e14d721/attachment.asc>


More information about the Gta04-owner mailing list