From: Ivan Sergio Borgonovo <mail@webthatworks.it>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: imx28evk based board moving from fido to jethro stopped to fully boot
Date: Mon, 14 Dec 2015 15:13:40 +0100 [thread overview]
Message-ID: <566ECE94.9060504@webthatworks.it> (raw)
In-Reply-To: <CAJrHVV4VRG7G+50v+3iEbYHL7d=GkOcYt2a5qZdqJs9SVx+mbg@mail.gmail.com>
On 12/14/2015 03:08 PM, justin chaise wrote:
> Hi, I am working with a board that is almost the same as the imx23evk,
> the imx28evk sibling.
> It seems that not all of our, MXS family, drivers were ported to the
> newer kernels.
> If fido booted and you saw a login on the lcd you may be in good shape.
>
> When you see the penguin logo that is the bootloader, u-boot,
> initializing the hardware.
> If the screen goes away after that; linux is not using or initializing
> the lcd. It may be using the serial port.
> First I would check the linux kernel command line switches in your
> device tree under chosen --> bootargs.
> Compare that to the settings you used with fido (linux-fslc 3.18?)
> Second check the boot arguments in u-boot. These settings will overwrite
> the command line switches from your device tree.
> I you can not type at the command line in u-boot, you can change the
> boot arguments in the code then recompile u-boot
> see (include/configs/mx28evk.h)
> I hope this starts you in the right direction.
It is definitively a good starting but it is even more puzzling:
- if uboot version changed from fido to jethro... it seems it is still
working since I can see the penguin logo
- the kernel didn't change. I'm using 4.1 in fido and jethro.
Anyway... I'll check in the direction you pointed.
thanks
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
next prev parent reply other threads:[~2015-12-14 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 9:34 imx28evk based board moving from fido to jethro stopped to fully boot Ivan Sergio Borgonovo
2015-12-14 14:08 ` justin chaise
2015-12-14 14:13 ` Ivan Sergio Borgonovo [this message]
2015-12-14 14:14 ` justin chaise
2015-12-14 23:23 ` Ivan Sergio Borgonovo
2015-12-15 1:45 ` Fabio Estevam
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=566ECE94.9060504@webthatworks.it \
--to=mail@webthatworks.it \
--cc=meta-freescale@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.