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.?

>
> http://pastebin.com/LdiemVK3
>
>> ## Booting kernel from Legacy Image at 80007fc0 ...
>>    Image Name:   Linux-3.12.0
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    34759808 Bytes = 33.1 MiB
>>    Load Address: 80008000
>>    Entry Point:  80008000
>>    Verifying Checksum ... OK
>> ## Flattened Device Tree blob at 82ff8000
>>    Booting using the fdt blob at 0x82ff8000
>>    XIP Kernel Image ... OK
>>    Using Device Tree in place at 82ff8000, end 82fff820
>>
>> Starting kernel ...
>>
>>
>> Error: unrecognized/unsupported machine ID (r1 = 0x00000e05).
>>
>> Available machine support:
>>
>> ID (hex)        NAME
>> ffffffff        Generic DT based system
>> ffffffff        Generic OMAP4 (Flattened Device Tree)
>> ffffffff        Generic AM33XX (Flattened Device Tree)
>> ffffffff        Generic OMAP3-GP (Flattened Device Tree)
>> ffffffff        Generic OMAP36xx (Flattened Device Tree)
>> ffffffff        Generic OMAP3 (Flattened Device Tree)
>> 0000060a        OMAP3 Beagle Board
>> 00000a9d        IGEP OMAP3 module
>> 00000928        IGEP v2 board
>>
>>
>> Any idea why my .dtb isn't getting picked up?
>
> 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.

Reply via email to