beagle-xm rev C with 3.12 kernel + fdt

Hi,

If I remember well Rob Nelson got a 3.12 kernel running on the beagle-xm.

This is what I tried [1].

After applying all the patches the kernel does not build (for beagleboard):

CC kernel/irq/manage.o
LD drivers/base/built-in.o
CC kernel/power/console.o
drivers/base/platform.o: In function of_free_overlay_info': platform.c:(.text+0x2a4): multiple definition of of_free_overlay_info’
drivers/base/core.o:core.c:(.text+0x66c): first defined here
drivers/base/cpu.o: In function of_free_overlay_info': cpu.c:(.text+0x198): multiple definition of of_free_overlay_info’
drivers/base/core.o:core.c:(.text+0x66c): first defined here
make[4]: *** [drivers/base/built-in.o] Error 1
make[3]: *** [drivers/base] Error 2
make[3]: *** Waiting for unfinished jobs…
CC mm/mremap.o
CC fs/namespace.o
CC mm/msync.o
LD kernel/printk/built-in

So I removed a couple of patches to make it compile.

The next problem I got was that the device tree did not build:

DTC arch/arm/boot/dts/omap3-beagle-xm.dtb
ERROR (phandle_references): Reference to non-existent node or label “dpll1_ck”

Well there is only one patch, which defines “dpll1_ck” and without it kernel + device tree build.

I know this is very hacky. This is the patchset I currently use [2]

Does someone have a 3.12 or 3.13 kernel + patches for the beagle-xm which works with a flat device tree?

Maybe it works with stable and no patches in the meantime?

Regards,

Robert

[1] https://github.com/beagleboard/kernel/tree/3.12
[2] https://github.com/RobertBerger/meta-mainline/blob/dora-v3.12.x-max/beagle-xm-ml/recipes-kernel/linux/linux-yocto-custom/beagle-xm-ml-user-patches.scc

i would be *very* interested in seeing the (eventual?) solution to
this, as i am teaching an embedded linux course at the end of january
for a client that *specifically* wants it taught on the xM. so any
information i can start collecting for the xM (rev C) would be
terrific.

rday

Hi,

i would be very interested in seeing the (eventual?) solution to
this, as i am teaching an embedded linux course at the end of january
for a client that specifically wants it taught on the xM. so any
information i can start collecting for the xM (rev C) would be
terrific.

I do trainings myself and one of the boards I deploy for trainings is the beagle-xm.

What kernel and what functionality do you need?

Do you want it with yocto? If so which version?

rday

Regards,

Robert

we can take this offline if you prefer, either way works for me. i'm
after the most recent kernel i can get, and it would be great to have
a working yocto build for it. i know the poky distro already comes
with a machine definition for the beagleboard, and i'm going to test
that a bit later.

  all i want as a starting point is something i can build and boot.

rday

https://github.com/RobertCNelson/armv7-multiplatform

v3.13.x branch

for the xM:
device tree
1Ghz operation
fixed usb ehci (sprz319_erratum_v2.1)
omapdrm/kms video

Regards,

Hi All,

I’m trying to build 3.13.5 with FDT. On boot it hangs at “Starting kernel …” (see capture below). Robert Nelson’s reply seems to indicate he has some code on GitHib but there’s just a License and a Readme file. I can’t get anything to work since 3.10. Is Beagleboard still supported?

Regards,
Ralph

U-Boot SPL (Feb 28 2014 - 11:58:43)
reading u-boot.img
reading u-boot.img

U-Boot 2014.04-rc1-00190-geeb72e6 (Feb 28 2014 - 11:59:40)

OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In: serial
Out: serial
Err: serial
Beagle xM Rev C
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 1 are properly configured
No EEPROM on expansion board
Die ID #023200029ff80000016849a90301801c
Net: usb_ether
Hit any key to stop autoboot: 0
mmc0 is current device
gpio: pin 173 (gpio 173) value is 0
gpio: pin 4 (gpio 4) value is 0
SD/MMC found on device 0
reading uEnv.txt
106 bytes read in 3 ms (34.2 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
** File not found /boot/uImage **
Booting from nand …

no devices available
Wrong Image Format for bootm command
ERROR: can’t get kernel image!
2692216 bytes read in 212 ms (12.1 MiB/s)
15670 bytes read in 45 ms (339.8 KiB/s)
Booting with DT from mmc0 …
Kernel image @ 0x80200000 [ 0x000000 - 0x291478 ]

Flattened Device Tree blob at 80f80000

Booting using the fdt blob at 0x80f80000
Using Device Tree in place at 80f80000, end 80f86d35

Starting kernel …

Hi,

I have 3.13.5 booting and have resolved the phy issue so the network is once more usable. Would a patch for anyone else trying to use 3.13 be useful?

Regards,
Ralph

Hi Ralph,

I would like to try the 3.13 kernel. So, can you please upload the patch?

Regards,
Pradeep

Hi,