BeagleboardxM rev. C - no network, missing smsc95xx

GoogleGroups
1

Which lines do I need to edit within a uEnv.txt file?

bootfile=zImage
address_image=``0x80300000 <<<<<<<<<<<<<<<< Do I change this to match system.sh?

bootinitrd=initrd.img
address_initrd=``0x81600000

console=ttyO2,115200n8

defaultdisplay=dvi
dvimode=1280x720MR-``16``@60

mmcroot=/dev/mmcblk0p2 ro <<<<<<<<<< Do I change this to /dev/sdb2

mmcrootfstype=ext4 rootwait fixrtc

optargs=console=tty0

mmc_load_image=fatload mmc ``0``:``1 ${address_image} ${bootfile}
mmc_load_initrd=fatload mmc ``0``:``1 ${address_initrd} ${bootinitrd}

#just zImage
xyz_mmcboot=run mmc_load_image; echo Booting from mmc ...

#zImage and initrd
#xyz_mmcboot=run mmc_load_image; run mmc_load_initrd; echo Booting from mmc ...

deviceargs=setenv device_args mpurate=${mpurate} buddy=${buddy} buddy2=${buddy2}

mmcargs=setenv bootargs console=${console} ${optargs} vram=${vram} omapfb.mode=${defaultdisplay}:${dvimode} omapdss.def_disp=${defaultdisplay} root=${mmcroot} rootfstype=${mmcrootfstype} ${device_args}

loaduimage=run xyz_mmcboot; run deviceargs; run mmcargs; bootz ${address_image}

#zImage and initrd
#loaduimage=run xyz_mmcboot; run deviceargs; run mmcargs; bootz ${address_image} ${address_initrd}:${filesize}

Additionally, do I need to "``sudo tar xfvp ./debian-*-minimal-armel-*/armel-rootfs-*.tar -C /media/rootfs/" or is the root file system completely create via the "install_image.sh"?

Thanks.

2

Which lines do I need to edit within a uEnv.txt file?

bootfile=zImage
address_image=0x80300000 <<<<<<<<<<<<<<<< Do I change this to match
system.sh?

Nope leave it as is.. it's a totally different number...

bootinitrd=initrd.img
address_initrd=0x81600000

console=ttyO2,115200n8

defaultdisplay=dvi
dvimode=1280x720MR-16@60

mmcroot=/dev/mmcblk0p2 ro <<<<<<<<<< Do I change this to /dev/sdb2

on your x86 it's /dev/sdb2, but on the beagle when it's booting
it's???... /dev/mmcblk0p2....

mmcrootfstype=ext4 rootwait fixrtc

Additionally, do I need to "sudo tar xfvp
./debian-*-minimal-armel-*/armel-rootfs-*.tar -C /media/rootfs/" or is the
root file system completely create via the "install_image.sh"?

That's the rootfs and a totaly different subject right up to this
point, we were just talking about u-boot and the kernel...

So, yes, if you want your kernel to boot into anything, you'll need a
rootfs, i have a couple listed on the eewiki that'll work just fine..

Regards,