From: Mark Jackson <mpfj-list@mimc.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Booting 3.9.0-rc2 on Beaglebone ?
Date: Tue, 12 Mar 2013 20:44:04 +0000 [thread overview]
Message-ID: <513F9394.6010306@mimc.co.uk> (raw)
I'm struggling to get the latest kernel git to load on my beaglebone.
My build process is:-
$ make -j 8 ARCH=arm CROSS_COMPILE=arm-linux- distclean
$ make -j 8 ARCH=arm CROSS_COMPILE=arm-linux- omap2plus_defconfig
CONFIG_DEBUG_LL=y
CONFIG_DEBUG_OMAP2PLUS_UART=y
CONFIG_DEBUG_AM33XXUART1=y
CONFIG_EARLY_PRINTK=y
CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y
$ make -j 8 ARCH=arm CROSS_COMPILE=arm-linux-
$ cat arch/arm/boot/zImage arch/arm/boot/am335x-bone.dtb >
arch/arm/boot/zImage-dtb.am335x-bone
$ scripts/mkuboot.sh -A arm -O linux -C none -T kernel -a 0x80008000 -e
0x80008000 -n 'Linux' -d arch/arm/boot/zImage-dtb.am335x-bone
arch/arm/boot/uImage-dtb.am335x-bone
But this produces the following when booting:-
## Booting kernel from Legacy Image at 80000000 ...
Image Name: Linux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3995640 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Error: unrecognized/unsupported machine ID (r1 = 0x00000e05).
Available machine support:
ID (hex) NAME
ffffffff Generic OMAP5 (Flattened Device Tree)
ffffffff Generic OMAP4 (Flattened Device Tree)
ffffffff Generic AM33XX (Flattened Device Tree)
ffffffff Generic OMAP3-GP (Flattened Device Tree)
ffffffff Generic OMAP3 (Flattened Device Tree)
ffffffff Generic OMAP2430 (Flattened Device Tree)
ffffffff Generic OMAP2420 (Flattened Device Tree)
000001fe OMAP2420 H4 board
00000384 OMAP2430 sdp2430 board
0000060a OMAP3 Beagle Board
0000091a OMAP3 Devkit8000
00000667 OMAP LDP board
000006ed OMAP Logic 3530 LV SOM board
00000882 Logic OMAP3 Torpedo board
00000706 Gumstix Overo
000005ff OMAP3 EVM
000006e1 Pandora Handheld Console
00000472 OMAP3430 3430SDP board
000006bf Nokia N810 WiMAX
0000060c Nokia N810
000004f7 Nokia N800
00000dc2 Nokia RM-696 board
00000c94 Nokia RM-680 board
000007a3 Nokia RX-51 board
000009a0 OMAP Zoom3 board
000007af OMAP Zoom2 board
000009a1 OMAP 3630SDP board
00000cda Compulab CM-T3730
00000925 Compulab CM-T35
00000abe Compulab CM-T3517
00000a9d IGEP OMAP3 module
00000928 IGEP v2 board
00000959 OMAP3 touchbook Board
00000870 OMAP4430 4430SDP board
00000ae7 OMAP4 Panda board
00000898 OMAP3517/AM3517 EVM
00000aa2 OMAP3 STALKER
00000bbc ti8148evm
00000af0 ti8168evm
ffffffff ARM-Versatile Express
000008e0 ARM-Versatile Express
Please check your kernel config and/or bootloader.
I guess I'm missing some vital step ?
Thanks for any help
Mark J.
next reply other threads:[~2013-03-12 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 20:44 Mark Jackson [this message]
2013-03-19 18:33 ` Booting 3.9.0-rc2 on Beaglebone ? Tony Lindgren
2013-03-20 8:35 ` Hiremath, Vaibhav
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=513F9394.6010306@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--cc=linux-omap@vger.kernel.org \
/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