Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: paul <paul.arssov@sbcglobal.net>
To: buildroot@busybox.net
Subject: [Buildroot] orange-pi build not working
Date: Thu, 12 Jan 2017 10:57:48 -0800	[thread overview]
Message-ID: <5877D1AC.6060808@sbcglobal.net> (raw)
In-Reply-To: <CACXmViYRiyOME4qytV0puMhMewe1A-J-24MEnkPaVKh9-=C72g@mail.gmail.com>

Hello Peter ,

Regarding -
 > Funky, how are you powering the boards?
I use a cable - usb to power jack. This way is ok for powering and 
booting with  images from the oragngepi.org - ubuntu,debian...
The vendor of the boards recommends using 5v/2a power supply.
Just to be sure it is not a powering issue I did use 5v/2a adapter but 
the result is the same - stops after starting kernel.

Let me know the results of your test with orangepi .


Thanks, Paul.

On 1/12/2017 12:36 AM, 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.
>

      parent reply	other threads:[~2017-01-12 18:57 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
2017-01-12 18:57       ` paul [this message]

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=5877D1AC.6060808@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox