Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ashish_Kumar_Mishra <dgashu55@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel Panic with BB Black + buildroot-2016.11.1
Date: Wed, 4 Jan 2017 21:13:32 -0800 (PST)	[thread overview]
Message-ID: <1483593212540-153987.post@n4.nabble.com> (raw)
In-Reply-To: <87bmvm2303.fsf@dell.be.48ers.dk>

1) So how do you create your rootfs and filesystem image?
I have the directory structure of 
my_virtual_project/git_release_buildroot = Has the buildroot setup 
my_virtual_project/release_branch_v2    =  Its here that i have my $(O)
directory & the steps were 
        *make -C ../git_release_buildroot/buildroot-2016.11.1 O=$(pwd)
menuconfig
        make *
Then flashing the images from ~/my_virtual_project/release_branch_v2/images
                 

2) Does it work if you instead build out beaglebone_defconfig? (E.G. make
clean; make beaglebone_defconfig; make
Initially i had working setup of buildroot-2016.05 where i carried the build
in the same directory .
With buildroot-2016.11.1 , i am trying building externally as per step_1
above. 

3) As you pointed i will try to build the buildroot-2016.11.1 internally
today & share the result. 

Could you please let me know if i am doing any step wrong here or missing
some steps !!!!!




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Kernel-Panic-with-BB-Black-buildroot-2016-11-1-tp153942p153987.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

  reply	other threads:[~2017-01-05  5:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 13:31 [Buildroot] Kernel Panic with BB Black + buildroot-2016.11.1 Ashish_Kumar_Mishra
2017-01-04 16:39 ` Peter Korsgaard
2017-01-05  5:13   ` Ashish_Kumar_Mishra [this message]
2017-01-05  8:34     ` Ashish_Kumar_Mishra

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=1483593212540-153987.post@n4.nabble.com \
    --to=dgashu55@gmail.com \
    --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