Skip to contentSkip to conversation

configs/udoo_quad_defconfig: new defconfig

PATCH New Ivo Slanina 4 participants 8 messages Jan 17, 2015 – Feb 2, 2015

lore
Share & tools
lore

Ivo Slanina

author
#0 lore raw

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

Added defconfig for UDOO Quad board. Used official kernel 3.0.35. Kernel is patched in order to use gcc version 4.8 and above, according to mailing list at
https://lists.yoctoproject.org/pipermail/meta-freescale/2013-July/003531.html

Bootloader is also downloaded from official repository.

Signed-off-by Ivo Slanina <[email protected]>
---
 configs/udoo_quad_defconfig |   25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 configs/udoo_quad_defconfig
configs/udoo_quad_defconfig new file +25 -0
new file mode 100644
index 0000000..32e9a61
@@ -0,0 +1,25 @@
+BR2_arm=y
+BR2_cortex_a9=y
+BR2_ARM_EABIHF=y
+BR2_ARM_FPU_VFPV3=y
+BR2_KERNEL_HEADERS_VERSION=y
+BR2_DEFAULT_KERNEL_VERSION="3.0.35"
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_0=y
+BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
+BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
+BR2_TARGET_GENERIC_GETTY_PORT="ttymxc1"
+BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_GIT=y
+BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/UDOOboard/Kernel_Unico"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="master"
+BR2_LINUX_KERNEL_PATCH="https://github.com/torvalds/linux/commit/455bd4c430b0c0a361f38e8658a0d6cb469942b5.patch https://github.com/torvalds/linux/commit/418df63adac56841ef6b0f1fcf435bc64d4ed177.patch"
+BR2_LINUX_KERNEL_DEFCONFIG="UDOO"
+BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x10008000"
+BR2_LINUX_KERNEL_INSTALL_TARGET=y
+BR2_TARGET_UBOOT=y
+BR2_TARGET_UBOOT_BOARDNAME="udoo_quad"
+BR2_TARGET_UBOOT_CUSTOM_GIT=y
+BR2_TARGET_UBOOT_CUSTOM_REPO_URL="https://github.com/UDOOboard/U-Boot_Unico-2013"
+BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION="master"
+BR2_TARGET_UBOOT_FORMAT_IMX=y
Signature · 1 line
1.7.10.4
#1 lore raw

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

Hi Ivo,

Quoted 4 lines · Ivo Slanina

Added defconfig for UDOO Quad board. Used official kernel 3.0.35. Kernel is patched in order to use gcc version 4.8 and above, according to mailing list at
https://lists.yoctoproject.org/pipermail/meta-freescale/2013-July/003531.html

Why can't you use mainline kernel for this board?

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 -
author
#2 lore raw

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

Hi baruch,

Quoted 12 lines · Baruch Siach

Hi Ivo,

Quoted 4 lines · Ivo Slanina

Added defconfig for UDOO Quad board. Used official kernel 3.0.35. Kernel is patched in order to use gcc version 4.8 and above, according to mailing list at
https://lists.yoctoproject.org/pipermail/meta-freescale/2013-July/003531.html

Why can't you use mainline kernel for this board?

baruch

I tried to used mainline kernel, but board doesn't boot up. I get only following output:

U-Boot 2013.10-rc3 (Jan 18 2015 - 12:03:56)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: UDOO
DRAM:  1 GiB
MMC:   FSL_SDHC: 0

*** Warning - bad CRC, using default environment

No panel detected: default to LDB-WVGA
Display: LDB-WVGA (800x480)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6

FEC [PRIME]
Hit any key to stop autoboot: 0
mmc0 is current device
** File not found boot.scr **
5489632 bytes read in 391 ms (13.4 MiB/s) Booting from mmc ...
** File not found imx6q-udoo.dtb **
## Booting kernel from Legacy Image at 12000000 ...

    Image Name:   Linux-3.18.3
    Image Type:   ARM Linux Kernel Image (uncompressed)
    Data Size:    5489568 Bytes = 5.2 MiB

Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

After this, board stuck. I also encountered this issue with another i.MX6 based board but I didn't fix that yet. Kernel from UDOO repository works fine.

I'm new in embedded Linux development. I still have a lot to learn, so I would be grateful if someone points me to how to use mainline kernel.

Regards,
Ivo Slanina

#3 lore raw

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

Hi Ivo,

Quoted 21 lines · Ivo Slanina
Quoted 1 line · Baruch Siach

Why can't you use mainline kernel for this board?

I tried to used mainline kernel, but board doesn't boot up. I get only following output:

U-Boot 2013.10-rc3 (Jan 18 2015 - 12:03:56)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: UDOO
DRAM:  1 GiB
MMC:   FSL_SDHC: 0

*** Warning - bad CRC, using default environment

No panel detected: default to LDB-WVGA
Display: LDB-WVGA (800x480)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6
Quoted 7 lines

FEC [PRIME]
Hit any key to stop autoboot: 0
mmc0 is current device
** File not found boot.scr **
5489632 bytes read in 391 ms (13.4 MiB/s)
Booting from mmc ...
** File not found imx6q-udoo.dtb **

Here is a clue. You can generate imx6q-udoo.dtb from the Linux sources by enabling CONFIG_ARCH_MXC, and running

make dtbs

Then copy arch/arm/boot/dts/imx6q-udoo.dtb to your MMC partition.

Quoted 9 lines

## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.18.3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5489568 Bytes = 5.2 MiB

Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Quoted 8 lines

Starting kernel ...

After this, board stuck. I also encountered this issue with another i.MX6 based board but I didn't fix that yet. Kernel from UDOO repository works fine.

I'm new in embedded Linux development. I still have a lot to learn, so I would be grateful if someone points me to how to use mainline kernel.

Hope this helps.

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 -
author
#4 lore raw

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

Hello Baruch,

Quoted 52 lines · Baruch Siach
Quoted 21 lines · Ivo Slanina
Quoted 1 line · Baruch Siach

Why can't you use mainline kernel for this board?

I tried to used mainline kernel, but board doesn't boot up. I get only following output:

U-Boot 2013.10-rc3 (Jan 18 2015 - 12:03:56)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: UDOO
DRAM:  1 GiB
MMC:   FSL_SDHC: 0

*** Warning - bad CRC, using default environment

No panel detected: default to LDB-WVGA
Display: LDB-WVGA (800x480)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6
Quoted 7 lines

FEC [PRIME]
Hit any key to stop autoboot: 0
mmc0 is current device
** File not found boot.scr **
5489632 bytes read in 391 ms (13.4 MiB/s)
Booting from mmc ...
** File not found imx6q-udoo.dtb **

Here is a clue. You can generate imx6q-udoo.dtb from the Linux sources by enabling CONFIG_ARCH_MXC, and running

make dtbs

Then copy arch/arm/boot/dts/imx6q-udoo.dtb to your MMC partition.

Quoted 15 lines

## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.18.3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5489568 Bytes = 5.2 MiB

Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

After this, board stuck. I also encountered this issue with another i.MX6 based board but I didn't fix that yet. Kernel from UDOO repository works fine.

Quoted 7 lines
Quoted 2 lines

I'm new in embedded Linux development. I still have a lot to learn, so I would be grateful if someone points me to how to use mainline kernel.

Hope this helps.

baruch

Thanks for help, I didn't notice device tree source file for UDOO in Linux sources. But after copying .dtb file into SD card, board still doesn't boot up.

Here is output, what I get:

U-Boot 2013.10-rc3 (Jan 18 2015 - 17:53:27)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: UDOO
DRAM:  1 GiB
MMC:   FSL_SDHC: 0

*** Warning - bad CRC, using default environment

No panel detected: default to LDB-WVGA
Display: LDB-WVGA (800x480)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6

FEC [PRIME]
Hit any key to stop autoboot: 0
mmc0 is current device
** File not found boot.scr **
5489632 bytes read in 361 ms (14.5 MiB/s) Booting from mmc ...
27547 bytes read in 129 ms (208 KiB/s)
## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.18.3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5489568 Bytes = 5.2 MiB

Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 11000000
Booting using the fdt blob at 0x11000000 Loading Kernel Image ... OK
Using Device Tree in place at 11000000, end 11009b9a

Starting kernel ...

It seems to be some trivial problem to me, but I can't fix this by myself. I not really understand uImage load address. I know that at 0x1000000 address starts MMC zone, but I'm not sure what is 0x8000 offset from that address. I took the value from freescale_imx6qsabresd_defconfig.

Please, can you give me some other clue?

Thanks,
Ivo Slanina

#5 lore raw

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

Hi Ivo,

Quoted 40 lines · Ivo Slanina

Thanks for help, I didn't notice device tree source file for UDOO in Linux sources.
But after copying .dtb file into SD card, board still doesn't boot up.

Here is output, what I get:

U-Boot 2013.10-rc3 (Jan 18 2015 - 17:53:27)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: UDOO
DRAM:  1 GiB
MMC:   FSL_SDHC: 0

*** Warning - bad CRC, using default environment

No panel detected: default to LDB-WVGA
Display: LDB-WVGA (800x480)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6

FEC [PRIME]
Hit any key to stop autoboot: 0
mmc0 is current device
** File not found boot.scr **
5489632 bytes read in 361 ms (14.5 MiB/s) Booting from mmc ...
27547 bytes read in 129 ms (208 KiB/s)
## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.18.3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5489568 Bytes = 5.2 MiB

Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 11000000
Booting using the fdt blob at 0x11000000 Loading Kernel Image ... OK
Using Device Tree in place at 11000000, end 11009b9a

Quoted 8 lines

Starting kernel ...

It seems to be some trivial problem to me, but I can't fix this by myself. I not really understand uImage load address. I know that at 0x1000000 address starts MMC zone, but I'm not sure what is 0x8000 offset from that address. I took the value from freescale_imx6qsabresd_defconfig.

Please, can you give me some other clue?

This is really quite off topic for this list. I agree with Thomas that if mainline kernel does not work for you for whatever reason, then you should stick with a kernel that works. Yet I think that the reason for choosing something other then mainline kernel should at least appear in the commit log. That is the reason I asked you about it.

I will only say that your next debugging step is called "earlyprintk". See the links below for some more details.

http://nishanthmenon.blogspot.co.il/2010/09/my-kernel-doesnt-boot-magic-of.html
http://nothingtechnicalaboutit.blogspot.co.il/2012/02/linux-early-boot-debug.html

If you have any further questions on kernel bring-up, please direct them to the linux-arm-kernel mailing list
(http://lists.infradead.org/mailman/listinfo/linux-arm-kernel).

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 -
#6 lore raw

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

In reply to Baruch Siach

Dear Baruch Siach,

Quoted 9 lines · Baruch Siach

Hi Ivo,

Quoted 4 lines · Ivo Slanina

Added defconfig for UDOO Quad board. Used official kernel 3.0.35. Kernel is patched in order to use gcc version 4.8 and above, according to mailing list at
https://lists.yoctoproject.org/pipermail/meta-freescale/2013-July/003531.html

Why can't you use mainline kernel for this board?

Well, on i.MX6, as far as know, you can't get OpenGL support with a mainline kernel. So even though I definitely support and encourage people to use mainline kernels, I believe for Buildroot defconfigs, it sometimes makes sense to use the vendor kernel when it is absolutely necessary to enable certain important features, like 3D acceleration.

Best regards,

Thomas

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

PATCH 1/1 configs/udoo_quad_defconfig: new defconfig

In reply to Ivo Slanina

Hi Ivo,

Quoted 5 lines · Ivo Slanina

Added defconfig for UDOO Quad board. Used official kernel 3.0.35. Kernel is patched in order to use gcc version 4.8 and above, according to mailing list at
https://lists.yoctoproject.org/pipermail/meta-freescale/2013-July/003531.html

Quoted 7 lines

Bootloader is also downloaded from official repository.

Signed-off-by Ivo Slanina <[email protected]>
---
 configs/udoo_quad_defconfig |   25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 configs/udoo_quad_defconfig

Thanks for your contribution!
I resubmitted your patch with two minor changes: use explicit commit numbers instead of a branch name like 'master'.

Best regards,
Thomas