Skip to contentSkip to conversation

configs/acmesystems_aria_g25: new configs

PATCH Superseded Gustavo Zacarias 4 participants 7 messages Jun 29, 2015 – Jun 30, 2015 Arm/Microchip (AT91) SoC support

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 configs/acmesystems_aria_g25: new configs

Add new basic configurations for ACME Systems ARIA G25 SOM. There are two different variants, a 128MB and a 256MB RAM model.

---
 .../aria-g25/at91bootstrap_aria_g25_128mb.config   |  9 ++++
 .../aria-g25/at91bootstrap_aria_g25_256mb.config   |  9 ++++
 board/acmesystems/aria-g25/readme.txt              | 48 ++++++++++++++++++++++
 configs/acmesystems_aria_g25_128mb_defconfig       | 24 +++++++++++
 configs/acmesystems_aria_g25_256mb_defconfig       | 24 +++++++++++
 5 files changed, 114 insertions(+)
 create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config
 create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config
 create mode 100644 board/acmesystems/aria-g25/readme.txt
 create mode 100644 configs/acmesystems_aria_g25_128mb_defconfig
 create mode 100644 configs/acmesystems_aria_g25_256mb_defconfig
board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config new file +9 -0
new file mode 100644
index 0000000..9be0545
@@ -0,0 +1,9 @@
+CONFIG_AT91SAM9X5_ARIA=y
+CONFIG_BUS_SPEED_100MHZ=y
+CONFIG_RAM_128MB=y
+CONFIG_SDCARD=y
+CONFIG_LOAD_LINUX=y
+CONFIG_LINUX_ZIMAGE=y
+CONFIG_LINUX_KERNEL_ARG_STRING="mem=128M console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
+CONFIG_DEBUG=y
+CONFIG_THUMB=y
board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config new file +9 -0
new file mode 100644
index 0000000..546c62c
@@ -0,0 +1,9 @@
+CONFIG_AT91SAM9X5_ARIA=y
+CONFIG_BUS_SPEED_100MHZ=y
+CONFIG_RAM_256MB=y
+CONFIG_SDCARD=y
+CONFIG_LOAD_LINUX=y
+CONFIG_LINUX_ZIMAGE=y
+CONFIG_LINUX_KERNEL_ARG_STRING="mem=256M console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
+CONFIG_DEBUG=y
+CONFIG_THUMB=y
board/acmesystems/aria-g25/readme.txt new file +48 -0

48 lines not on this page · raw message

configs/acmesystems_aria_g25_128mb_defconfig new file +24 -0
new file mode 100644
index 0000000..76ccbe1
@@ -0,0 +1,24 @@
+# Architecture
+BR2_arm=y
+
+# Toolchain
+BR2_KERNEL_HEADERS_VERSION=y
+BR2_DEFAULT_KERNEL_VERSION="4.1"
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
+
+# Kernel
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.1"
+BR2_LINUX_KERNEL_DEFCONFIG="at91_dt"
+BR2_LINUX_KERNEL_ZIMAGE=y
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91-ariag25"
+
+# Bootloader
+BR2_TARGET_AT91BOOTSTRAP3=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL="git://github.com/tanzilli/at91bootstrap.git"
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION="3f957cec253abc80fd10c733e5e596f46e1aef56"
+BR2_TARGET_AT91BOOTSTRAP3_USE_CUSTOM_CONFIG=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_CONFIG_FILE="board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config"
configs/acmesystems_aria_g25_256mb_defconfig new file +24 -0
new file mode 100644
index 0000000..320abc3
@@ -0,0 +1,24 @@
+# Architecture
+BR2_arm=y
+
+# Toolchain
+BR2_KERNEL_HEADERS_VERSION=y
+BR2_DEFAULT_KERNEL_VERSION="4.1"
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
+
+# Kernel
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.1"
+BR2_LINUX_KERNEL_DEFCONFIG="at91_dt"
+BR2_LINUX_KERNEL_ZIMAGE=y
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91-ariag25"
+
+# Bootloader
+BR2_TARGET_AT91BOOTSTRAP3=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL="git://github.com/tanzilli/at91bootstrap.git"
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION="3f957cec253abc80fd10c733e5e596f46e1aef56"
+BR2_TARGET_AT91BOOTSTRAP3_USE_CUSTOM_CONFIG=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_CONFIG_FILE="board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config"
Signature · 1 line
2.3.6
#1 lore raw

PATCH v2 1/1 configs/acmesystems_aria_g25: new configs

Hi Gustavo,

Quoted 16 lines · Gustavo Zacarias

Add new basic configurations for ACME Systems ARIA G25 SOM. There are two different variants, a 128MB and a 256MB RAM model.

---
 .../aria-g25/at91bootstrap_aria_g25_128mb.config   |  9 ++++
 .../aria-g25/at91bootstrap_aria_g25_256mb.config   |  9 ++++
 board/acmesystems/aria-g25/readme.txt              | 48 ++++++++++++++++++++++
 configs/acmesystems_aria_g25_128mb_defconfig       | 24 +++++++++++
 configs/acmesystems_aria_g25_256mb_defconfig       | 24 +++++++++++
 5 files changed, 114 insertions(+)
 create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config
 create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config
 create mode 100644 board/acmesystems/aria-g25/readme.txt
 create mode 100644 configs/acmesystems_aria_g25_128mb_defconfig
 create mode 100644 configs/acmesystems_aria_g25_256mb_defconfig

[snip]

board/acmesystems/aria-g25/readme.txt line 6

Quoted 6 lines
board/acmesystems/aria-g25/readme.txt new file +6 -0
+Build instructions
+==================
+
+As a regular user configure and then build:
+
+$ make acmesystems_aria_g25_defconfig

No such defconfig anymore.

baruch

Signature · 3 lines
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
#2 lore raw

PATCH v2 1/1 configs/acmesystems_aria_g25: new configs

Quoted 10 lines · Baruch Siach

Hi Gustavo,

board/acmesystems/aria-g25/readme.txt line 6

Quoted 6 lines
board/acmesystems/aria-g25/readme.txt new file +6 -0
+Build instructions
+==================
+
+As a regular user configure and then build:
+
+$ make acmesystems_aria_g25_defconfig

No such defconfig anymore.

Hi Baruch.
Oh yes, v3 coming :)
Regards.

#3 lore raw

PATCH v2 1/1 configs/acmesystems_aria_g25: new configs

In reply to Gustavo Zacarias

Hi Gustavo,

2015-06-29 23:38 GMT+02:00 Gustavo Zacarias <[email protected]>:

Quoted 4 lines

Add new basic configurations for ACME Systems ARIA G25 SOM. There are two different variants, a 128MB and a 256MB RAM model.

Quoted 12 lines
---
 .../aria-g25/at91bootstrap_aria_g25_128mb.config   |  9 ++++
 .../aria-g25/at91bootstrap_aria_g25_256mb.config   |  9 ++++
 board/acmesystems/aria-g25/readme.txt              | 48 ++++++++++++++++++++++
 configs/acmesystems_aria_g25_128mb_defconfig       | 24 +++++++++++
 configs/acmesystems_aria_g25_256mb_defconfig       | 24 +++++++++++
 5 files changed, 114 insertions(+)
 create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config
 create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config
 create mode 100644 board/acmesystems/aria-g25/readme.txt
 create mode 100644 configs/acmesystems_aria_g25_128mb_defconfig
 create mode 100644 configs/acmesystems_aria_g25_256mb_defconfig

Can we agree on the configs name format? Sergio usually uses the format "acme-BOARD-MEMORY", I used acme-arietta-128m_defconfig for example. I really prefer to have a standard name format!

Quoted 52 lines
board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config new file +9 -0
new file mode 100644
index 0000000..9be0545
@@ -0,0 +1,9 @@
+CONFIG_AT91SAM9X5_ARIA=y
+CONFIG_BUS_SPEED_100MHZ=y
+CONFIG_RAM_128MB=y
+CONFIG_SDCARD=y
+CONFIG_LOAD_LINUX=y
+CONFIG_LINUX_ZIMAGE=y
+CONFIG_LINUX_KERNEL_ARG_STRING="mem=128M console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
+CONFIG_DEBUG=y
+CONFIG_THUMB=y
board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config new file +9 -0
new file mode 100644
index 0000000..546c62c
@@ -0,0 +1,9 @@
+CONFIG_AT91SAM9X5_ARIA=y
+CONFIG_BUS_SPEED_100MHZ=y
+CONFIG_RAM_256MB=y
+CONFIG_SDCARD=y
+CONFIG_LOAD_LINUX=y
+CONFIG_LINUX_ZIMAGE=y
+CONFIG_LINUX_KERNEL_ARG_STRING="mem=256M console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait"
+CONFIG_DEBUG=y
+CONFIG_THUMB=y
board/acmesystems/aria-g25/readme.txt new file +16 -0
new file mode 100644
index 0000000..374cf1c
@@ -0,0 +1,48 @@
+Build instructions
+==================
+
+As a regular user configure and then build:
+
+$ make acmesystems_aria_g25_defconfig
+$ make
+
+Writing to the MicroSD card
+===========================
+
+Assuming your Aria G25 baseboard has a MicroSD socket, for example with
+the Terra baseboard, you'll need a blank MicroSD (obviously) initialized
+in a particular way to be able to boot from it.
+
+Assuming the card is seen as /dev/sdb in your PC/laptop/other device

board/acmesystems/aria-g25/readme.txt line 26

Quoted 10 lines
board/acmesystems/aria-g25/readme.txt new file +10 -0
+you'll need to run the following commands as root or via sudo.
+
+Make sure all of the card partitions are unmounted before starting.
+
+First we'll need to create two partitions:
+
+# sfdisk -uM /dev/sdb <<EOF
+,32,6
+;
+EOF

This is better:

echo ',32,6\n;' | sfdisk -uM /dev/sdX

Quoted 42 lines
board/acmesystems/aria-g25/readme.txt new file +22 -0
+
+Then we'll need to create the empty filesystems:
+
+# mkdosfs -n SD_BOOT /dev/sdb1
+# mkfs.ext4 -L SD_ROOT /dev/sdb2
+
+We'll populate the first partition (boot) with the relevant files:
+
+# mount /dev/sdb1 /mnt
+# cp output/images/at91bootstrap.bin /mnt/BOOT.BIN
+# cp output/images/zImage /mnt
+# cp output/images/at91-ariag25.dtb /mnt
+# umount /mnt
+
+And the root filesystem afterwards:
+
+# mount /dev/sdb2 /mnt
+# tar -C /mnt output/images/rootfs.tar
+# umount /mnt
+
+You're done, insert the MicroSD card in the slot and enjoy.
+
configs/acmesystems_aria_g25_128mb_defconfig new file +14 -0
new file mode 100644
index 0000000..76ccbe1
@@ -0,0 +1,24 @@
+# Architecture
+BR2_arm=y
+
+# Toolchain
+BR2_KERNEL_HEADERS_VERSION=y
+BR2_DEFAULT_KERNEL_VERSION="4.1"
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
+
+# Kernel
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.1"
+BR2_LINUX_KERNEL_DEFCONFIG="at91_dt"
+BR2_LINUX_KERNEL_ZIMAGE=y

configs/acmesystems_aria_g25_128mb_defconfig line 24

Quoted 10 lines
configs/acmesystems_aria_g25_128mb_defconfig new file +10 -0
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91-ariag25"
+
+# Bootloader
+BR2_TARGET_AT91BOOTSTRAP3=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL="git://github.com/tanzilli/at91bootstrap.git"
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION="3f957cec253abc80fd10c733e5e596f46e1aef56"
+BR2_TARGET_AT91BOOTSTRAP3_USE_CUSTOM_CONFIG=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_CONFIG_FILE="board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config"

Config files for at91bootstrap are not really needed cause Sergio shipped them in it's own at91bootstrap fork, so you should simply use something like this in your bootstrap defconfig:

BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG="aria-128m"

Quoted 20 lines
configs/acmesystems_aria_g25_256mb_defconfig new file +14 -0
new file mode 100644
index 0000000..320abc3
@@ -0,0 +1,24 @@
+# Architecture
+BR2_arm=y
+
+# Toolchain
+BR2_KERNEL_HEADERS_VERSION=y
+BR2_DEFAULT_KERNEL_VERSION="4.1"
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
+
+# Kernel
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.1"
+BR2_LINUX_KERNEL_DEFCONFIG="at91_dt"
+BR2_LINUX_KERNEL_ZIMAGE=y

configs/acmesystems_aria_g25_256mb_defconfig line 24

Quoted 10 lines
configs/acmesystems_aria_g25_256mb_defconfig new file +10 -0
+BR2_LINUX_KERNEL_DTS_SUPPORT=y
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="at91-ariag25"
+
+# Bootloader
+BR2_TARGET_AT91BOOTSTRAP3=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL="git://github.com/tanzilli/at91bootstrap.git"
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION="3f957cec253abc80fd10c733e5e596f46e1aef56"
+BR2_TARGET_AT91BOOTSTRAP3_USE_CUSTOM_CONFIG=y
+BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_CONFIG_FILE="board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config"

No need for custom config, should be:

BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG="aria-256m"

Sincerely, Angelo

Quoted 7 lines

--
2.3.6

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

Signature · 1 line
Profile: http://it.linkedin.com/in/compagnucciangelo
#4 lore raw

PATCH v2 1/1 configs/acmesystems_aria_g25: new configs

Quoted 1 line · Angelo Compagnucci

Hi Gustavo,

Hi Angelo.

Quoted 9 lines
Quoted 5 lines

create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config create mode 100644 board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config create mode 100644 board/acmesystems/aria-g25/readme.txt
create mode 100644 configs/acmesystems_aria_g25_128mb_defconfig create mode 100644 configs/acmesystems_aria_g25_256mb_defconfig

Can we agree on the configs name format? Sergio usually uses the format "acme-BOARD-MEMORY", I used acme-arietta-128m_defconfig for example. I really prefer to have a standard name format!

Of course, though i don't know who Sergio is :)
But you must follow the rule as well, is it acme (configs/) or acmesystems (board/) ?
It's not consistent for them to differ.

Quoted 3 lines

This is better:

echo ',32,6\n;' | sfdisk -uM /dev/sdX

I've used the xplained readme as basis.
Ideally we should script this thing up, probably making a somewhat generic one that takes parameters from an image file defined in the BR config.

Quoted 5 lines

Config files for at91bootstrap are not really needed cause Sergio shipped them in it's own at91bootstrap fork, so you should simply use something like this in your bootstrap defconfig:

BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG="aria-128m"

I've missed the fact that the kernel command line is specified in the dts, so yes it seems reasonable.

Regards.

#5 lore raw

PATCH v2 1/1 configs/acmesystems_aria_g25: new configs

Hi Gustavo,

2015-06-30 13:24 GMT+02:00 Gustavo Zacarias <[email protected]>:

Quoted 18 lines · Angelo Compagnucci
Quoted 2 lines

Hi Gustavo,

Hi Angelo.

Quoted 9 lines
Quoted 7 lines

create mode 100644
board/acmesystems/aria-g25/at91bootstrap_aria_g25_128mb.config
create mode 100644
board/acmesystems/aria-g25/at91bootstrap_aria_g25_256mb.config
create mode 100644 board/acmesystems/aria-g25/readme.txt create mode 100644 configs/acmesystems_aria_g25_128mb_defconfig create mode 100644 configs/acmesystems_aria_g25_256mb_defconfig

Quoted 6 lines
Quoted 3 lines

Can we agree on the configs name format? Sergio usually uses the format "acme-BOARD-MEMORY", I used acme-arietta-128m_defconfig for example. I really prefer to have a standard name format!

Of course, though i don't know who Sergio is :)

Ah sorry! Usually who comes from acmesystems products knows Sergio very well! He is the mastermind behind Acmesystems products!

Quoted 3 lines

But you must follow the rule as well, is it acme (configs/) or acmesystems (board/) ?
It's not consistent for them to differ.

Ok, go for acmesystem then! I'll update my patches.

Quoted 8 lines
Quoted 3 lines

This is better:

echo ',32,6\n;' | sfdisk -uM /dev/sdX

I've used the xplained readme as basis.
Ideally we should script this thing up, probably making a somewhat generic one that takes parameters from an image file defined in the BR config.

Yes right, but I think the one liner is better for a novice that tries buildroot for the first time. Up to you!

Quoted 8 lines
Quoted 5 lines

Config files for at91bootstrap are not really needed cause Sergio shipped them in it's own at91bootstrap fork, so you should simply use something like this in your bootstrap defconfig:

BR2_TARGET_AT91BOOTSTRAP3_DEFCONFIG="aria-128m"

I've missed the fact that the kernel command line is specified in the dts, so yes it seems reasonable.

Yes, DTS command line takes precedence over the at91bootstrap one.

Quoted 2 lines

Regards.

Signature · 1 line
Profile: http://it.linkedin.com/in/compagnucciangelo
#6 lore raw

PATCH v2 1/1 configs/acmesystems_aria_g25: new configs

In reply to Gustavo Zacarias

Dear Gustavo Zacarias,

Quoted 6 lines · Gustavo Zacarias
Quoted 1 line

echo ',32,6\n;' | sfdisk -uM /dev/sdX

I've used the xplained readme as basis.
Ideally we should script this thing up, probably making a somewhat generic one that takes parameters from an image file defined in the BR config.

No, we should use genimage:

http://patchwork.ozlabs.org/patch/462195/

But that's longer term. For now, I'm fine with a script.

Thanks,

Thomas

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