All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Sergio Borgonovo <mail@webthatworks.it>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: imx28evk based board moving from fido to jethro stopped to fully boot
Date: Mon, 14 Dec 2015 10:34:16 +0100	[thread overview]
Message-ID: <566E8D18.8080005@webthatworks.it> (raw)

I've a board that just need a couple of patches to device tree compared 
to the imx28evk board:
- configuration of serial ports
- display timing

It was fully booting with fido (linux-fsl) and I was able to see the 
login prompt on the screen.

Now I see the penguin logo and no more login prompt.

While I wait to have a cable to connect a serial console this is the 
only information I can provide.

I was reading
http://www.yoctoproject.org/docs/2.0/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.0-release

http://freescale.github.io/doc/release-notes/2.0/#known-issues

but nothing seems relevant unless the gcc problem is relevant for the 
current status of linux-fsl kernel (4.1).

Since my only changes to the imx28evk are related to dt and the screen 
does seem to work I'd be tempted to say the problem is elsewhere.
I had to adjust local.conf just to cope with a couple of changes in qt5 
and gstreamer, but software that shouldn't have any impact on boot.

Any clue that may help me to fix this while I wait for cable?
Has anyone tested imx28evk with jethro?


thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it



             reply	other threads:[~2015-12-14  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14  9:34 Ivan Sergio Borgonovo [this message]
2015-12-14 14:08 ` imx28evk based board moving from fido to jethro stopped to fully boot justin chaise
2015-12-14 14:13   ` Ivan Sergio Borgonovo
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=566E8D18.8080005@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.