linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: lager - non-booting latest horms' devel branch
Date: Thu, 09 Jan 2014 12:30:57 +0000	[thread overview]
Message-ID: <52CE9681.3060700@codethink.co.uk> (raw)
In-Reply-To: <52CE8BC0.7060306@codethink.co.uk>

On 09/01/14 12:21, Geert Uytterhoeven wrote:
> Hi Ben,
>
> On Thu, Jan 9, 2014 at 12:45 PM, Ben Dooks <ben.dooks@codethink.co.uk> wrote:
>> I am using the devel branch from Simon Horms' git tree, SHA1
>> 3da593ea7d797d9f59bd6ed1ee629fab681d7a23 and not seeing a
>> boot when using the multi arch defconfig and device-tree.
>>
>> The board does not produce any console output so I am not
>> sure what is going on. Has anyone else had issues with using
>> the fdt-only boot?
>
> I'm using Koelsch (not Lager), but usually the non-reference version as I
> need Ethernet for NFS root.
> The DT-version does boot for me until mounting root.
>
> Are you using an initramfs? I noticed the kernel crashes early when using
> a non-trivial initramfs:

No, we're just tftping and then nfs-root.

>      Error: unrecognized/unsupported machine ID (r1 = 0x41915083).
>
>      Available machine support:
>
>      ID (hex)        NAME
>      ffffffff        Generic R8A7791 (Flattened Device Tree)
>      ffffffff        koelsch
>
>      Please check your kernel config and/or bootloader.
>
> Apparently the device tree gets overwritten in memory. I tried loading the
> DTB at a different address, but that didn't help. I didn't have more time
> to investigate, though.

I've managed to get it to boot with another boot method, however that 
has other limitations...

>
> FYI, I'm using the following patch to capture early kernel messages in RAM.
> After a reset, look up the addres of big_buffer[] in System.map, and
> inspect it from U-Boot to retrieve the messages (translate from 0xc0000000
> to 0x40000000).

Ta, that's a useful thing to have

i am considering it may be a dtc compiler bug or some other issue with
the device-tree.

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  parent reply	other threads:[~2014-01-09 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 11:45 lager - non-booting latest horms' devel branch Ben Dooks
2014-01-09 12:21 ` Geert Uytterhoeven
2014-01-09 12:30 ` Ben Dooks [this message]
2014-01-09 14:42 ` Ben Dooks
2014-01-09 16:01 ` Ben Dooks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52CE9681.3060700@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=linux-sh@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).