Re: Freescale Linux kernel 3.10.17_1.0.0_beta

[John Weber <rjohnweber@gmail.com>]

Hi Fabio -

On 12/30/13 11:17 AM, Fabio Estevam wrote:
> On Mon, Dec 30, 2013 at 2:46 PM, John Weber <rjohnweber@gmail.com> wrote:
>> Testing this now.  Looks like it boots and talks to the network, USB, and
>> serial ports on Wandboard Dual, but changes might be needed for U-boot to
>> use a zImage by default, as well as changing the default fdt load address.
>> I had problems booting with the DTB using a uImage.
> Can you try with fdt_addr=0x18000000 ?
I had problems with uImage when the DTB is loaded at 0x18000000.  It would give 
me errors like the following (note this was yesterday using 3.10.9):

reading uImage
4565936 bytes read in 238 ms (18.3 MiB/s)
Booting from mmc ...
reading imx6dl-wandboard.dtb
34153 bytes read in 19 ms (1.7 MiB/s)
## Booting kernel from Legacy Image at 10008000 ...
    Image Name:   Linux-3.10.9+
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    4565872 Bytes = 4.4 MiB
    Load Address: 10008000
    Entry Point:  10008000
    Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
    Booting using the fdt blob at 0x18000000
    XIP Kernel Image ... OK
    Using Device Tree in place at 18000000, end 1800b568

Starting kernel ...

undefined instruction
pc : [<10008028>]          lr : [<4ff7ffe8>]
sp : 4f57c8c8  ip : ffffffff     fp : 4ffb9bd4
r10: 4ffba2a4  r9 : 4f57cf38     r8 : 4f57e2fc
r7 : 00000000  r6 : 10008000     r5 : 4ffba2a4  r4 : 00002c8d
r3 : 00008569  r2 : 18000000     r1 : 0000113c  r0 : 18000000
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

Loading the zImage in the same place and using bootz worked.  I'm not sure if I 
have made a mistake somewhere else.

>
>> Also, do not use imx_v6_v7_defconfig.  Here, I believe that v6 and v7 refer
>> to the ARM instruction set.  The new kernel seems to include some
>> v7-specific instructions in some assembly code (specifically some lpddr2
>> code).  I'm using imx_v7_defconfig instead, which actually has more
>> i.MX6-specific options included by default.
>>
>> As an side question - is there an issue with defaulting to using zImage
>> instead of uImage for Yocto/u-boot?
> No, I also think we should switch to zImage format. We only need to
> update the script to call 'bootz' instead of 'bootm'.
OK, is this something that we should stage for v1.6?
>
> Regards,
>
> Fabio Estevam