On Wed, Nov 6, 2013 at 3:55 PM, Robert Nelson <[email protected]> wrote: > On Wed, Nov 6, 2013 at 12:06 PM, Robert Nelson <[email protected]> > wrote: >> On Wed, Nov 6, 2013 at 11:55 AM, Jason Kridner <[email protected]> >> wrote: >>> On Wed, Nov 6, 2013 at 11:39 AM, Robert Nelson <[email protected]> >>> wrote: >>>> On Wed, Nov 6, 2013 at 9:29 AM, Jason Kridner <[email protected]> >>>> wrote: >>>>> Robert, >>>>> >>>>> I'm starting with the kernel at >>>>> http://github.com/beagleboard/kernel/tree/3.12. I've pushed a patched >>>>> version of the tree to http://github.com/beagleboard/linux/tree/3.12. >>>>> >>>>> To build the kernel, I'm using buildroot via >>>>> http://github.com/jadonk/buildroot/tree/latest. >>>>> >>>>> make beaglebone_config >>>>> make >>>>> >>>>> I'm booting the MLO and u-boot.img that are in the buildroot >>>>> output/images. I then try the following: >>>>> >>>>> U-Boot SPL 2013.07 (Oct 30 2013 - 09:44:19) >>>>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, >>>>> SoftConn) >>>>> musb-hdrc: MHDRC RTL version 2.0 >>>>> musb-hdrc: setup fifo_mode 4 >>>>> musb-hdrc: 28/31 max ep, 16384/16384 memory >>>>> USB Peripheral mode controller at 47401000 using PIO, IRQ 0 >>>>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, >>>>> SoftConn) >>>>> musb-hdrc: MHDRC RTL version 2.0 >>>>> musb-hdrc: setup fifo_mode 4 >>>>> musb-hdrc: 28/31 max ep, 16384/16384 memory >>>>> USB Host mode controller at 47401800 using PIO, IRQ 0 >>>>> OMAP SD/MMC: 0 >>>>> reading args >>>>> spl: error reading image args, err - -1 >>>>> reading u-boot.img >>>>> reading u-boot.img >>>>> >>>>> >>>>> U-Boot 2013.07 (Oct 30 2013 - 09:44:19) >>>>> >>>>> I2C: ready >>>>> DRAM: 512 MiB >>>>> WARNING: Caches not enabled >>>>> NAND: 0 MiB >>>>> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 >>>>> *** Warning - readenv() failed, using default environment >>>>> >>>>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, >>>>> SoftConn) >>>>> musb-hdrc: MHDRC RTL version 2.0 >>>>> musb-hdrc: setup fifo_mode 4 >>>>> musb-hdrc: 28/31 max ep, 16384/16384 memory >>>>> USB Peripheral mode controller at 47401000 using PIO, IRQ 0 >>>>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, >>>>> SoftConn) >>>>> musb-hdrc: MHDRC RTL version 2.0 >>>>> musb-hdrc: setup fifo_mode 4 >>>>> musb-hdrc: 28/31 max ep, 16384/16384 memory >>>>> USB Host mode controller at 47401800 using PIO, IRQ 0 >>>>> Net: <ethaddr> not set. Validating first E-fuse MAC >>>>> cpsw, usb_ether >>>>> Hit any key to stop autoboot: 0 >>>>> U-Boot# >>>>> U-Boot# run findfdt >>>>> U-Boot# setenv bootargs console=${console} >>>>> U-Boot# load mmc 0 0x80007fc0 uImage >>>>> reading uImage >>>>> 34759872 bytes read in 3941 ms (8.4 MiB/s) >>>>> U-Boot# load mmc 0 0x82ff8000 ${fdtfile} >>>>> reading am335x-boneblack.dtb >>>>> 18465 bytes read in 9 ms (2 MiB/s) >>>>> U-Boot# bootm 0x80007fc0 - 0x82ff8000 >>>> >>>> Hum, I actually haven't tested "bootm" in some time, I'll test it right >>>> now... >>>> >>>> Here's what i'm seeing with "bootz 0x80200000 >>>> 0x81000000:${initrd_size} 0x815f0000" (intrd is basically ignored as >>>> it's 3.8.x based..) >>> >>> What's the reasoning behind moving to bootz? I'm just looking for >>> something that is simple and works. I can see some advantage to >>> skipping the mkimage step, but if the build infrastructure is already >>> there, why should I go to an extra step to remove it and break some >>> compatibility with existing scripts, etc.? >> >> bootz/zImage is easier for multi-arch, plus you never have to remember >> the mkimage syntax or address. (Luckly TI has for the most part always >> used 0x80008000) Some 'other' vendors like to change the address >> randomly.. >> >> Anywho, it looks to not be a uImage/zImage issue.. I'm just waiting >> for buildroot to finish.. > > Weird, it works for me.. > > git clone https://github.com/jadonk/buildroot.git buildroot-jadonk > cd buildroot-jadonk/ > git checkout origin/latest -b latest > make beaglebone_defconfig > make > > http://pastebin.com/mLu6Ak5A > > maybe it's the load address of 0x80007fc0????
Interesting. I tried 0x82000000 as a the load address. I'll take a look at your pastebin for more ideas. BTW, I posted a build here: http://beagle.s3.amazonaws.com/buildroot/2013-11-06-19:49:50/index.html > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
