From: paul <paul.arssov@sbcglobal.net>
To: buildroot@busybox.net
Subject: [Buildroot] orange-pi build not working
Date: Thu, 19 Jan 2017 07:06:33 -0800 [thread overview]
Message-ID: <5880D5F9.8040403@sbcglobal.net> (raw)
In-Reply-To: <5877E30B.5050600@sbcglobal.net>
Hi ,
I did find a solution to the one time boot for 'orange pi' boards.
In order to keep booting I did change through the build-root config -
- select 'linux headers' as '4.7.x'
- select 'kernel' as '4.7'
I made a build and did test - successfully booting multiple times.
Why do the builds with newer 4.8 and 4.9 kernels boot only 1 time?
I did not find the exact reason but here are some hypotheses -
- u-boot documentation (pretty old-2007) mentions 'boot-count'
parameter, used in making u-boot, and passing it to kernel
- u-boot documentation provides a source of a kernel driver to modify
boot count through the '/proc' ;
Paul.
On 1/12/2017 12:11 PM, paul wrote:
> Hello Micha?l ,
>
> raspberry-pi and may be your imx7 board has a 'cmdline.txt' file in the
> first fat partition where you specify - 'console=...' parameter.
>
> However orange-pi does not have or use 'cmdline.txt' file in the first
> fat partition.
> There are 3 files -
> boot.scr, sun8i-orangepi-pc.dtb, zImage
>
> Besides, the orange-pi completes successfully the very first boot. Does
> your imx7 board completes the very first boot without 'console=...'
> parameter?
>
>
> Paul.
>
>
> On 1/12/2017 7:14 AM, Micha?l Zweers wrote:
>> Hi,
>>
>> Sorry if this is unhelpful but have you told your kernel to use console ?
>>
>> I can get the same results if i dont set the console=... to uart in
>> boot argument on my imx7 board.
>>
>> kind regards,
>> Micha?l
>>
>>
>> On 12-1-2017 09:36, Peter Korsgaard wrote:
>>> Hi,
>>>
>>> Please keep the buildroot list in CC so others can help as well.
>>>
>>>
>>>>> So no output at all after this? It sounds like your kernel image has
>>>>> somehow gotten corrupted. How did you reboot?
>>>>
>>>> I did multiple builds with 4.8 and 4.9 kernels - same result. The
>>>> original/initial kernel is not corrupted because it boots ok.
>>>> I did reboot by either -
>>>> # reboot
>>>> or, disconnect/connect power
>>>> While power off/on may corrupt the sd card, 'reboot' cmd should not.
>>>
>>> Funky, how are you powering the boards?
>>>
>>>> People did report on the list of functioning orange-pi-pc and
>>>> orange-pi-one
>>>> boards.
>>>> How did they find the boards working?
>>>
>>> I do have an orangepi-pc board stacked away here, and it did work in
>>> the past. I'll try to find time this weekend to retest.
>>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
next prev parent reply other threads:[~2017-01-19 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 21:57 [Buildroot] orange-pi build not working paul
2017-01-11 23:07 ` Peter Korsgaard
[not found] ` <5876E124.30603@sbcglobal.net>
2017-01-12 8:36 ` Peter Korsgaard
2017-01-12 15:14 ` Michaël Zweers
2017-01-12 20:11 ` paul
2017-01-19 15:06 ` paul [this message]
2017-01-12 18:57 ` paul
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=5880D5F9.8040403@sbcglobal.net \
--to=paul.arssov@sbcglobal.net \
--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.