Re: [Gta04-owner] successful boot from usb
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 0x8300 0x80 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: 144200229ff80163810c1901301f 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 0x8200 0x80;fdt ram 0x81c0 0x4;rd ram 0x8300 0x400;script ram 0x8080 0x4;bootscript ram 0x8180 0x4 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 8080 ## Error: "mmcargs" not defined ## Booting kernel from Legacy Image at 8200 ... 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 81c0 Booting using the fdt blob at 0x81c0 Loading Kernel Image ... OK Loading Device Tree to 8ffea000, end 8435 ... 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 Kemnadewrote: > On Mon, 20 Nov 2017 12:40:07 +0100 > Andreas Kemnade 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 pgp8bdUvTMXtx.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] successful boot from usb
On Mon, 20 Nov 2017 12:40:07 +0100 Andreas Kemnadewrote: [...] > > > > > > 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 pgp4C83IqcvX6.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] successful boot from usb
> Am 20.11.2017 um 07:40 schrieb Andreas Kemnade: > > On Sun, 19 Nov 2017 13:28:34 +0100 > Andreas Kemnade wrote: > >> On Sat, 18 Nov 2017 23:29:32 +0100 >> Andreas Kemnade wrote: >> >>> Hi, >>> >>> I have hacked the pusb tool a bit so that I could use it to boot the >>> gta04. The original pusb tool seems to work only at the right moon >>> phase, the gta04 oriented exactly in north-south direction ;-) >>> >>> Now I am a quit independant of that. >> >> The results are here: >> https://github.com/akemnade/omap-u-boot-utils/ >> >> Now I just have to find out why I can only boot the old SLO that way >> (on A4). > > > Well, I found the reason. > 1. There is MLO and spl/u-boot-spl.bin > The further has a CHSETTINGS header which can configure things like > image start address. This header cannot be used for peripheral boots like > serial or usb, only for flash/mmc boots. So the image start address has to > stick > to the standard. Ok, this means that MLO is a special variant only. But did I understand it correctly, we have to strip the headers from spl/u-boot-spl.bin to make it an image for serial/usb boot? If we understand that and have a script that does it, we can automatically add such images to: http://download.goldelico.com/letux-u-boot/GTA04-OneNAND/latest/ > > 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. BR, Nikolaus signature.asc Description: Message signed with OpenPGP using GPGMail ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] successful boot from usb
On Sat, 18 Nov 2017 23:29:32 +0100 Andreas Kemnadewrote: > Hi, > > I have hacked the pusb tool a bit so that I could use it to boot the > gta04. The original pusb tool seems to work only at the right moon > phase, the gta04 oriented exactly in north-south direction ;-) > > Now I am a quit independant of that. The results are here: https://github.com/akemnade/omap-u-boot-utils/ Now I just have to find out why I can only boot the old SLO that way (on A4). The new SPL does for some reason not spit out anything on rs232 console (even when I load it using p_serial) , although it seems to be successfully transferred to the device. To use it: make usb cp omap-usb-boot.rules /etc/udev/rules.d/ ./pusb -f s-load.bin power on gta04 with aux pressed Regards, Andreas pgpDVNWIcE44k.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
[Gta04-owner] successful boot from usb
Hi, I have hacked the pusb tool a bit so that I could use it to boot the gta04. The original pusb tool seems to work only at the right moon phase, the gta04 oriented exactly in north-south direction ;-) Now I am a quit independant of that. That means: I could transfer the old SLO via usb, then uboot via ukermit (unfortunately via rs232) ... and then I can talk to uboot. What I am interested in: loading everything via usb and load e.g. the debian installer, your favourite test scripts, whatever. What I am wondering now: I can successfully transfer the new SPL to the gta04 that way. But it does not display anything. I am not sure yet, what is going on. And then of course, a uboot configuration allowing further usb actions is needed. Regards, Andreas pgpQG29m17Fnl.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner