Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] beaglebone: better support for starting and creating images
Date: Wed, 02 Jul 2014 09:01:03 +0200	[thread overview]
Message-ID: <53B3AE2F.1020607@relinux.de> (raw)
In-Reply-To: <5395B898.3090505@gmail.com>

Hello community,

is there really no interest in this patch?

I personally think it would be a great improvement for beaglebone
support, but do not feel suficiently familiar with buildrooot to apply
Acked-by.

Kind regards

Stephan

Am 09.06.2014 15:37, schrieb Marcin Jabrzyk:
> Tried it one more time and it works fine for master.
>
> Tested-by: Marcin Jabrzyk <marcin.jabrzyk@gmail.com>
>
> W dniu 26.05.2014 20:27, Stephan Hoffmann pisze:
>> Am 14.03.2014 13:13, schrieb Marcin Jabrzyk:
>>> - Added short readme file with description of first steps how to start.
>>> - Added uEnv.txt so the board can start from SDCard
>>> - Added post-image.sh script to copy included uEnv.txt to output/images
>>>
>>> Signed-off-by: Marcin Jabrzyk <marcin.jabrzyk@gmail.com>
>> Tested-by: Stephan Hoffmann <sho@relinux.de>
>>> ---
>> The patch still applies to the current HEAD. I tested it with both
>> BeagleBone and BeagleBoneBlack as described in the readme file.
>>>  board/beaglebone/post-image.sh |  6 ++++
>>>  board/beaglebone/readme.txt    | 62 ++++++++++++++++++++++++++++++++++++++++++
>>>  board/beaglebone/uEnv.txt      |  3 ++
>>>  configs/beaglebone_defconfig   |  1 +
>>>  4 files changed, 72 insertions(+)
>>>  create mode 100755 board/beaglebone/post-image.sh
>>>  create mode 100644 board/beaglebone/readme.txt
>>>  create mode 100644 board/beaglebone/uEnv.txt
>>>
>>> diff --git a/board/beaglebone/post-image.sh b/board/beaglebone/post-image.sh
>>> new file mode 100755
>>> index 0000000..7441d07
>>> --- /dev/null
>>> +++ b/board/beaglebone/post-image.sh
>>> @@ -0,0 +1,6 @@
>>> +#!/bin/sh
>>> +# post-image.sh for BeagleBone
>>> +# 2014, Marcin Jabrzyk <marcin.jabrzyk@gmail.com>
>>> +
>>> +# copy the uEnv.txt to the output/images directory
>>> +cp board/beaglebone/uEnv.txt $BINARIES_DIR/uEnv.txt
>>> diff --git a/board/beaglebone/readme.txt b/board/beaglebone/readme.txt
>>> new file mode 100644
>>> index 0000000..dc44751
>>> --- /dev/null
>>> +++ b/board/beaglebone/readme.txt
>>> @@ -0,0 +1,62 @@
>>> +BeagleBone
>>> +
>>> +Intro
>>> +=====
>>> +To be able to use BeagleBone board with the images generated by
>>> +Buildroot, you have prepare the SDCard.
>>> +
>>> +How to build it
>>> +===============
>>> +
>>> +  $ make beaglebone_defconfig
>>> +
>>> +Then you can edit the build options using
>>> +  
>>> +  $ make menuconfig
>>> +  
>>> +Compile all and build rootfs image:
>>> +  
>>> +  $ make
>>> +
>>> +Result of the build
>>> +-------------------
>>> +
>>> +After building, you should get a tree like this:
>>> +
>>> +  output/images/                                                                                                                                                                                   
>>> +  ??? am335x-boneblack.dtb                                                                                                                                                                         
>>> +  ??? am335x-bone.dtb
>>> +  ??? MLO
>>> +  ??? rootfs.ext2
>>> +  ??? u-boot.img
>>> +  ??? uEnv.txt
>>> +  ??? zImage
>>> +
>>> +
>>> +Prepare you SDCard
>>> +==================
>>> +
>>> +You need to prepare first partition in fat32 and marked as bootable,
>>> +and second where you will write rootfs.
>>> +
>>> +Copy the files to boot partition
>>> +
>>> +  $ cp MLO u-boot.img zImage uEnv.txt *.dtb /media/zzzzz
>>> +  
>>> +where /media/zzzzz is the mount point
>>> +Then you need to write the rootfs image onto SDCard:
>>> +
>>> +  # dd if=rootfs.ext2 of=/dev/xxxxx
>>> +  
>>> +where /dev/xxxxx is the second partition. Use:
>>> +  
>>> +  # fdisk -l 
>>> +  
>>> +to check for correct one.
>>> +
>>> +Finish
>>> +======
>>> +
>>> +Unmount all mounted SDCard partitions and insert the card to BeagleBone.
>>> +Hold the "BOOT" button and apply power. Then release the "BOOT" button. 
>>> +The output is available on the serial console.
>>> \ No newline at end of file
>>> diff --git a/board/beaglebone/uEnv.txt b/board/beaglebone/uEnv.txt
>>> new file mode 100644
>>> index 0000000..68d6e23
>>> --- /dev/null
>>> +++ b/board/beaglebone/uEnv.txt
>>> @@ -0,0 +1,3 @@
>>> +bootpart=0:1
>>> +bootdir=
>>> +uenvcmd=run loaduimage;run loadramdisk;run findfdt;run loadfdt;run ramboot 
>>> diff --git a/configs/beaglebone_defconfig b/configs/beaglebone_defconfig
>>> index 3181c66..b2052f4 100644
>>> --- a/configs/beaglebone_defconfig
>>> +++ b/configs/beaglebone_defconfig
>>> @@ -8,6 +8,7 @@ BR2_TARGET_GENERIC_HOSTNAME="beaglebone"
>>>  BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS=y
>>>  BR2_TARGET_GENERIC_GETTY_PORT="ttyO0"
>>>  # BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW is not set
>>> +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/beaglebone/post-image.sh"
>>>  
>>>  # filesystem
>>>  BR2_PACKAGE_AM33X_CM3=y
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2014-07-02  7:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 12:13 [Buildroot] [PATCH 1/1] beaglebone: better support for starting and creating images Marcin Jabrzyk
2014-05-26 18:27 ` Stephan Hoffmann
2014-06-09 13:37   ` Marcin Jabrzyk
2014-07-02  7:01     ` Stephan Hoffmann [this message]
2014-10-12 10:38 ` Arnout Vandecappelle
2014-10-12 16:28   ` Peter Korsgaard
2014-10-12 17:07     ` Marcin Jabrzyk
2014-10-12 17:21       ` Peter Korsgaard

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=53B3AE2F.1020607@relinux.de \
    --to=sho@relinux.de \
    --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