From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] state of olimex_imx233_olinuxino_defconfig
Date: Sun, 21 Feb 2016 09:21:24 -0300 [thread overview]
Message-ID: <56C9ABC4.1070506@zacarias.com.ar> (raw)
In-Reply-To: <87egc7c7y8.fsf@dell.be.48ers.dk>
On 20/02/16 19:50, Peter Korsgaard wrote:
>>>>>> "Phil" == Phil Eichinger <phil.eichinger@gmail.com> writes:
>
> > Hello
> > I recently tried olimex_imx233_olinuxino_defconfig and created the SD
> > card according to the readme.txt. It failed to boot with:
> > "
> > PowerPrep start initialize power...
> > Battery Voltage = 0.74V
> > No battery or bad battery
> > detected!!!.Disabling battery
> > voltage measurements./r/nLLCFeb 16 201616:01:38
> > EMI_CTRL 0x1C084040
> > FRAC 0x92926192
> > init_ddr_mt46v32m16_133Mhz
> > power 0x00820710
> > Frac 0x92926192
> > start change cpu freq
> > hbus 0x00000003
> > cpu 0x00010001
> > LLLLLLLFCLJ
> > "
> > Looks like the handover to the kernel is somehow broken, as it is not starting.
>
> Sorry, no experience with imx233 / mxs-bootlets. Gustavoz, you've done
> various updates to the defconfig. Does it work for you? Any hints?
>
> > I am however not sure if I should submit an updated defconfig or a new
> > one like olimex_imx233_olinuxino_uboot_defconfig and extend the
> > readme.txt to cover both use cases?
>
> Lets see what Gustavoz says.
Hi All.
Unfortunately i don't have an olinuxino in my hands any more.
It's very likely bootlets isn't happy with newer toolchain components -
it's known to be somewhat fragile in that aspect, so if someone wants to
update the defconfig to use uboot that would be great.
That wasn't a viable option when i added it since it didn't work vanilla.
Regards.
next prev parent reply other threads:[~2016-02-21 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 22:15 [Buildroot] state of olimex_imx233_olinuxino_defconfig Phil Eichinger
2016-02-20 22:50 ` Peter Korsgaard
2016-02-21 12:21 ` Gustavo Zacarias [this message]
2016-02-21 12:45 ` Phil Eichinger
2016-02-21 13:25 ` Peter Korsgaard
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=56C9ABC4.1070506@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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.