Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] trying to use https://github.com/beagleboard/linux.git with buildroot
Date: Wed, 23 Dec 2015 18:47:51 +0100	[thread overview]
Message-ID: <20151223184751.12365336@free-electrons.com> (raw)
In-Reply-To: <1450890296.2355509.475056490.71128E4E@webmail.messagingengine.com>

Craig,

On Wed, 23 Dec 2015 09:04:56 -0800, Craig Swank wrote:

> [*] Linux Kernel
>       Kernel version (Custom Git repository)  --->
> (file:///home/craig/workspace/beaglebone/linux) URL of custom repository
> (4.1.4-ti-r9) Custom repository version
> ()    Custom kernel patches
>       Kernel configuration (Using an in-tree defconfig file)  --->
> (bb.org) Defconfig name
> ()    Additional configuration fragment files
>       Kernel binary format (zImage)  --->
>       Kernel compression format (gzip compression)  --->
> [*]   Build a Device Tree Blob (DTB)
>         Device tree source (Use a device tree present in the kernel.) 
>         --->
> (am335x-bone am335x-boneblack) Device Tree Source file names
> [ ]   Install kernel image to /boot in target
>       Linux Kernel Extensions  --->
>       Linux KernelTools?>

This looks good. It is somewhat odd to use "URL of custom repository"
when you have the sources locally. You could just as well use the
option BR2_LINUX_KERNEL_CUSTOM_LOCAL to point to a local directory. But
that definitely shouldn't prevent it from working.

> $ git checkout 4.1.4-ti-r9 -b tmp
> make ARCH=arm bb.org_defconfig
> so, following the pattern of the raspberry pi defconfig in buildroot,
> the defconfig name should be ?bb.org?

Correct.

> when I run ?make? in buildroot it all seems to build fine, but when I
> install the output to my sd card and start up my beaglebone I get:

Can you pastebin (on http://code.bulix.org or some other pastebin site)
the entire build output, so we can check that what happens is really
good?

> U-Boot SPL 2013.10 (Dec 23 2015 - 09:23:34)
> reading args
> spl: error reading image args, err - -1
> reading u-boot.img
> reading u-boot.img
> 
> 
> U-Boot 2013.10 (Dec 23 2015 - 09:23:34)
> 
> I2C:   ready
> DRAM:  512 MiB
> WARNING: Caches not enabled
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> *** Warning - readenv() failed, using default environment
> 
> Net:   <ethaddr> not set. Validating first E-fuse MAC
> cpsw, usb_ether
> Hit any key to stop autoboot:  0 
> mmc0 is current device
> SD/MMC found on device 0
> reading uEnv.txt
> 96 bytes read in 3 ms (31.3 KiB/s)
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Running uenvcmd ...
> reading /zImage
> 7416160 bytes read in 688 ms (10.3 MiB/s)
> reading ramdisk.gz
> ** Unable to read file ramdisk.gz **
> reading /am335x-boneblack.dtb
> 57860 bytes read in 12 ms (4.6 MiB/s)
> Booting from ramdisk ...
> Kernel image @ 0x80200000 [ 0x000000 - 0x712960 ]
> Wrong Ramdisk Image Format
> Ramdisk image is corrupt or invalid
> reading /zImage
> 7416160 bytes read in 689 ms (10.3 MiB/s)
> reading /am335x-boneblack.dtb
> 57860 bytes read in 11 ms (5 MiB/s)
> Kernel image @ 0x80200000 [ 0x000000 - 0x712960 ]
> ## Flattened Device Tree blob at 80f80000
>    Booting using the fdt blob at 0x80f80000
>    Using Device Tree in place at 80f80000, end 80f91203
> 
> Starting kernel ...
> 
> 
> After ?Starting kernel ?? there is no more output and no leds are
> flashing.  It just dies there.

Does it work with some other kernel? Do you have console= defined in
the bootargs to the proper value?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-23 17:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 17:04 [Buildroot] trying to use https://github.com/beagleboard/linux.git with buildroot Craig Swank
2015-12-23 17:47 ` Thomas Petazzoni [this message]
     [not found]   ` <1450893821.3034067.475093450.34890777@webmail.messagingengine.com>
2015-12-23 18:15     ` Craig Swank
2015-12-23 18:39       ` Thomas Petazzoni
2015-12-23 18:59         ` Craig Swank
2015-12-23 22:45         ` Craig Swank
2015-12-23 22:52           ` Thomas Petazzoni
2015-12-24  0:42             ` Craig Swank
2015-12-24 12:44               ` Chris LaRocque
2015-12-24 19:35                 ` Craig Swank
2015-12-26 16:00               ` Chris LaRocque
2015-12-26 16:31                 ` Craig Swank
2015-12-26 18:34                 ` Craig Swank
2015-12-26 23:02                   ` Frank Hunleth
2015-12-26 23:44                     ` Craig Swank
2015-12-27  0:09                       ` Chris LaRocque
2015-12-27 10:08                       ` Thomas Petazzoni
2015-12-27 13:34                         ` Craig Swank
2015-12-27 13:35                           ` Craig Swank
2015-12-27 16:28                           ` Chris LaRocque
2015-12-27 17:01                             ` Craig Swank
2015-12-27 18:36                               ` Chris LaRocque
2015-12-27 18:48                                 ` Craig Swank
2015-12-27 19:27                                   ` Craig Swank

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=20151223184751.12365336@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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