BeagleBoard running arm debian etch from sd card

Hello,

Attached is a quick guide i put together for getting debian on the
beagleboard. I'm still in the process of building a native debian arm
kernel*, so this guide will build a debian root file system, but you
will still have to use one of the available uImage's.. (I'm currently
using uImage_OTG from the beagle board google code site..)

* Status: native compiling on beagle hardlocks at 'calibrate.o', i'm
currently attempting to build an image thru qemu.

Regards,

cat howto-mmc-uboot-ext3issue.txt
#GOAL boot debian linux with single sd card..
#Problem: ext2load doesn't work correctly, in current git u-boot /
test/
#Status:
#Debian boots, console on hdmi-dvi, usb keyboard, etc
#Issues:
#swap partition disabled, (change /dev/hda5 -> /dev/mmcblock0p5 in /
etc/fstab) artifact of qemu install /dev/hdaX
#Building kernel, gcc runs, but hard locks 10-15 files into make
uImage.. :wink: (swap/ram issue..)
#RTC/time hasn't really ever worked, add ntpdate to default install or
issue date MMDDHHMMSSYYYY
#Unknown/can't test:
#ethernet
#With the uImage_OTG image none of my usb-ethernet/usb-wifi adapters
work..

****2GB mmc/sd card***
fat 50MB
ext3 2GB-50MB

RobertCNelson wrote:

Hello,

Attached is a quick guide i put together for getting debian on the
beagleboard. I'm still in the process of building a native debian arm
kernel*, so this guide will build a debian root file system, but you
will still have to use one of the available uImage's.. (I'm currently
using uImage_OTG from the beagle board google code site..)

* Status: native compiling on beagle hardlocks at 'calibrate.o', i'm
currently attempting to build an image thru qemu.

Great!

Do you like to create a wiki page for this at

http://elinux.org/

e.g.

http://elinux.org/BeagleBoardDebian

?

Then we can add the link to

http://elinux.org/BeagleBoard

Thanks

Dirk

Great!

Do you like to create a wiki page for this at

http://elinux.org/

e.g.

BeagleBoardDebian - eLinux.org

Will do! Should be up shortly for a quick review, then publish...

I’d also suggest creating a project entry on http://beagleboard.org/project and having it point to the wiki page.

Dirk Behme:

Wiki page is up and ready for first review: http://elinux.org/BeagleBoardDebian

Jason Kridner

Submitted a project, the wording will need a little work, but it's
enough to get the idea..

Regards,

Attached is a quick guide i put together for getting debian on the
beagleboard.

Thanks!

##QEMU, arm, debian reference:Aurélien Jarno - New website, or kind of...
#packages we need to run qemu on arm..
wgethttp://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.18-6-vers…
wgethttp://people.debian.org/~aurel32/arm-versatile/initrd.img-2.6.18-6-v…
wgethttp://ftp.de.debian.org/debian/dists/etch/main/installer-arm/current…

Can you try with images from:

http://ftp.de.debian.org/debian/dists/lenny/main/installer-armel/current/images/versatile/netboot/

etch/arm is quite obsolete at this point, for the next release, lenny
Debian is going for armel.

Also, if you could report any issues you have with the lenny
installer:

http://d-i.alioth.debian.org/manual/en.arm/ch05s03.html#submit-bug

Attached is a quick guide i put together for getting debian on the
beagleboard.

Thanks!

##QEMU, arm, debian reference:Aurélien Jarno - New website, or kind of...
#packages we need to run qemu on arm..
wgethttp://people.debian.org/~aurel32/arm-versatile/vmlinuz-2.6.18-6-vers…
wgethttp://people.debian.org/~aurel32/arm-versatile/initrd.img-2.6.18-6-v…
wgethttp://ftp.de.debian.org/debian/dists/etch/main/installer-arm/current…

Can you try with images from:

http://ftp.de.debian.org/debian/dists/lenny/main/installer-armel/current/images/versatile/netboot/

etch/arm is quite obsolete at this point, for the next release, lenny
Debian is going for armel.

I agree!!! :wink:

At this point, i'm kinda stuck in the old non-eabi world. You
wouldn't happen to know where the current arm eabi patches for qemu
are hosted? (tried qemu trunk last night, with the lenny 'armel'
versatile netboot and the image wasn't able to detect the flash drive
(/dev/sdx, or hda.img)) and qemubuilder also failed.

At this point, I've got a method to build a native kernel non-eabi,
but I'm still tweaking the .config (framebuffer comes up corrupted, so
i don't have a console.. (rebuilding another native image as i
type..)).. Technique is listed here:
http://elinux.org/BeagleBoardDebian

I'm thinking once, we have a good working non-eabi kernel, (with
builtin usb-ethernet/wifi support). I want to load both the kernel
and the initrd.gz installer in ram, and do a standard netboot install.
Once that's successful, have a existing armel platform (i don't have
access to one of these at the moment) build a kernel with the same
.config, and completely bypass the qemu install method.. :wink:

Thank again!

Talk about one of those sundays. :wink:

I'm going to retract my previous statement, since qemu trunk decided
to detect my hda.img today. So i'm going to run with this, and get
lenny eabi guide setup..

Robert Nelson wrote:

Thank again!

Talk about one of those sundays. :wink:

I'm going to retract my previous statement, since qemu trunk decided
to detect my hda.img today. So i'm going to run with this, and get
lenny eabi guide setup..

Not being an expert of ARM Debian, I'm slightly confused looking at recent version of

http://elinux.org/BeagleBoardDebian

Is the note

"Note: This guide still uses the old etch arm 'non-eabi'. I'm currently modifying it for lenny armel eabi."

still correct? If yes, what is still missing for lenny armel eabi? Most sections seem to have a lenny 'armel' part. If no, should the etch 'arm' parts be removed? If both parts are still relevant, we should give the reader of the page a hint which configuration to use when.

And same with Native Built Debian Kernel section: We should give the reader a hint when to use the precompiled binaries and when to use build it your own section:

"You can use precompiled lenny armel eabi binaries if you want to ... or you can build everything at your own .... Building on your own has the advantage ..."

Sorry if I missed anything,

Dirk

Not being an expert of ARM Debian, I'm slightly confused looking at
recent version of

BeagleBoardDebian - eLinux.org

Is the note

"Note: This guide still uses the old etch arm 'non-eabi'. I'm
currently modifying it for lenny armel eabi."

still correct? If yes, what is still missing for lenny armel eabi?
Most sections seem to have a lenny 'armel' part. If no, should the
etch 'arm' parts be removed? If both parts are still relevant, we
should give the reader of the page a hint which configuration to use when.

Hi Dirk,
The page is messy at the moment, i'd like to remove all 'etch-arm'
material and only list 'lenny-armel'.. (armel, is slated to be an
official debian release to replace 'arm' for devices that support
it..) Except, I've been unable to finish building a native kernel in
'lenny-armel', i'm thinking it's a binutils issue, I'm rebuilding it
again at the moment, will post a full log shortly..

Reference: In the debian world there are two abi's for arm.. 'arm' =
original, 'armel' = arm eabi.
http://wiki.debian.org/ArmEabiPort

And same with Native Built Debian Kernel section: We should give the
reader a hint when to use the precompiled binaries and when to use
build it your own section:

"You can use precompiled lenny armel eabi binaries if you want to ...
or you can build everything at your own .... Building on your own has
the advantage ..."

I agree..

I'm thinking this document needs to be in two sections.

[1] Default install: partition your mmc card, run qemu and install
debian, reboot qemu and download these recompiled kernel deb's..
(basically a script based install)

[2] How to: Building a native Kernel (including build directions uboot
to get mkimage).

Sorry if I missed anything,

Dirk

Kernel log just finished, here's my current issue: (i'm thinking
CROSS_COMPILE snuck thru..)

/bin/sh: arm-linux-gnueabi-objdump: command not found
  HOSTCC scripts/mod/mk_elfconfig
  MKELF scripts/mod/elfconfig.h
  HOSTCC scripts/mod/file2alias.o
  HOSTCC scripts/mod/modpost.o
  HOSTCC scripts/mod/sumversion.o
  HOSTLD scripts/mod/modpost
  HOSTCC scripts/kallsyms
  HOSTCC scripts/pnmtologo
  HOSTCC scripts/conmakehash
  CC init/main.o
/tmp/ccHH14Zc.s: Assembler messages:
/tmp/ccHH14Zc.s:882: Error: selected processor does not support `cpsie i'
/tmp/ccHH14Zc.s:1357: Error: selected processor does not support `cpsid i'
/tmp/ccHH14Zc.s:1374: Error: selected processor does not support `cpsid i'
/tmp/ccHH14Zc.s:1401: Error: selected processor does not support `cpsid i'
/tmp/ccHH14Zc.s:1428: Error: selected processor does not support `cpsid i'
/tmp/ccHH14Zc.s:1540: Error: selected processor does not support `cpsid i'
/tmp/ccHH14Zc.s:1585: Error: selected processor does not support `cpsie i'

Thanks!