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: Wed, 11 Jan 2017 13:57:48 -0800	[thread overview]
Message-ID: <5876AA5C.2010904@sbcglobal.net> (raw)

Hi ,

I did pull the current 'buildroot' from git, and did a build with the 2 
configs provided for orange pi boards -
orangepi_pc_defcongfig
orangepi_one_defcongfig

Here are the results of testing for both types of builds -
1. The hdmi supports is not enabled - nothing comes on screen
2. The 'orange-pi' boards have dedicated serial port for boot logging; 
the very first boot completes successfully - through the serial port I 
am able to log-in as root, and run commands; for ex. 'uname -a' returns 
'4.9.0' kernel;
3. After first reboot, and any other boot the board reaches to the point 
of starting the kernel but does not go any further.

Here is the output from the serial port logging -
------------
	..........
Scanning mmc 0:1...

Found U-Boot script /boot.scr

reading /boot.scr

300 bytes read in 14 ms (20.5 KiB/s)

## Executing script at 43100000

reading zImage

3545792 bytes read in 189 ms (17.9 MiB/s)

reading sun8i-h3-orangepi-pc.dtb

13056 bytes read in 24 ms (531.3 KiB/s)

## Flattened Device Tree blob at 43000000

    Booting using the fdt blob at 0x43000000

    Using Device Tree in place at 43000000, end 430062ff



Starting kernel ...
----------------

Questions -
1. Why is the hdmi port not enabled?
2. Why does it boot completely only time, and then stops at 'Starting 
kernel ...' ?


Thanks,
Paul.

             reply	other threads:[~2017-01-11 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 21:57 paul [this message]
2017-01-11 23:07 ` [Buildroot] orange-pi build not working 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

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=5876AA5C.2010904@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