Hi Robert,
I notice that your Debian Squeeze kernel is configured with OMAP4 Panda
support. I realize I'll need to pull down the Panda u-boot, etc. but I
suspect I should be able to use your initramfs on another armel board.
Have you tried running your Beagle bits on Panda?
Jon.
Hi Jon,
Yeap, it's configured for the OMAP4 Panda, but I've discovered with my
recently received "A1" the 2.6.35 kernel recipe doesn't work too well
on the Panda....
But I do have my 2.6.37-rc3 kernel working pretty great on the panda
(same kernel works just fine on my beagle's..) Right now only the
smp/dual core, uart, usb/ehci, usb/eth work.. I haven't figured out
the display stuff yet, sgx, dsp, audio, etc..
I've prebuilt x-load/u-boot based of ubuntu's repo's use ABI:2: (ABI:1
is beagle)
http://rcn-ee.net/deb/tools/latest/bootloader
Right now the NetInstall isn't ready for the panda.. But if you have
a preconfigured sd card for debian squeeze and beagle working..
First build and install this kernel: (it's in my build deb queue, but
way behind..)
https://code.launchpad.net/~beagleboard-kernel/+junk/2.6.37-devel
(2.6.37-rc3-d2 added working ehci support)
change your boot.scr from ttyS2 to ttyO2 (O for Omap), and edit
/etc/inittab "S:2345:respawn:/sbin/getty 115200 ttyO2"
then reboot, making sure it still works with the beagle.. (no dvi
video on omap4 yet in my kernel, so serial only)
Create a new sd card with the same partition layout, using the new
x-load and u-boot for the panda, then copy the uImage, uInird(if
used), boot.scr to the fat partition.. then copy the rootfs partion
data over.. It should boot just fine.. (it did on my panda and xM
today, same rootfs, same kernel build, just different MLO/u-boot..)
Regards,
But I do have my 2.6.37-rc3 kernel working pretty great on the panda
(same kernel works just fine on my beagle's..) Right now only the
smp/dual core, uart, usb/ehci, usb/eth work.. I haven't figured out
the display stuff yet, sgx, dsp, audio, etc..
Cool. btw, I can't boot the latest 2.6.37 RC kernel from your site on my
xM rev. A1 here. It's just hanging after uncompressing the kernel. It's
possible that it's pilot error due to being late in the evening (4am). I
would love to debug it, once I get a reply to my question on using the
Flyswatter with the Beagle. Do you use a debugger with yours? I suppose
you might even have your own BDI 
Ever since I stopped doing Embedded
for a day job and went into "Enterprise Linux" I lost that toy.
I've prebuilt x-load/u-boot based of ubuntu's repo's use ABI:2: (ABI:1
is beagle)
Yea. I saw those and guessed as much. Cool! I also see you've been busy
the last few days building some other panda bits. Awesome. I do so much
love same (E)ABIs that allow for this kind of fun.
Right now the NetInstall isn't ready for the panda.. But if you have
a preconfigured sd card for debian squeeze and beagle working..
Right. This is the plan. I just upgraded the SD card in my Beagle from 4
to 16GB using dd and an online resize, so I'll simply copy the same
userland bits over to a real SD card (non-micro) and boot on Panda.
Should work if I change over the uboot env and console settings. I see
you helpfully suggest just this in your reply. Thanks.
I'm away in California next week at a Yocto event but I'll look forward
to poking some more when I get back to Boston (I also might have to buy
another xM now that they're under $150). I took a slight detour earlier
setting up the Sheevaplug that came in the mail...finally. I think I
might even have more ARM devices than PPC at home now
Happy Thanksgiving!
Jon.
Hi Jon,
But I do have my 2.6.37-rc3 kernel working pretty great on the panda
(same kernel works just fine on my beagle's..) Right now only the
smp/dual core, uart, usb/ehci, usb/eth work.. I haven't figured out
the display stuff yet, sgx, dsp, audio, etc..Cool. btw, I can't boot the latest 2.6.37 RC kernel from your site on my
xM rev. A1 here. It's just hanging after uncompressing the kernel. It's
possible that it's pilot error due to being late in the evening (4am). I
would love to debug it, once I get a reply to my question on using the
Flyswatter with the Beagle. Do you use a debugger with yours? I suppose
you might even have your own BDI
for a day job and went into "Enterprise Linux" I lost that toy.
Double check your console=tty*2 setting in your bootargs..
Pre 2.6.37 is ttyS2, Post 2.6.37 is ttyO2 'O' as in Omap...
Nope, no debugger here, just using a serial port with all the builtin
kernel debugging tools..
I've prebuilt x-load/u-boot based of ubuntu's repo's use ABI:2: (ABI:1
is beagle)Yea. I saw those and guessed as much. Cool! I also see you've been busy
the last few days building some other panda bits. Awesome. I do so much
love same (E)ABIs that allow for this kind of fun.Right now the NetInstall isn't ready for the panda.. But if you have
a preconfigured sd card for debian squeeze and beagle working..Right. This is the plan. I just upgraded the SD card in my Beagle from 4
to 16GB using dd and an online resize, so I'll simply copy the same
userland bits over to a real SD card (non-micro) and boot on Panda.
Should work if I change over the uboot env and console settings. I see
you helpfully suggest just this in your reply. Thanks.I'm away in California next week at a Yocto event but I'll look forward
to poking some more when I get back to Boston (I also might have to buy
another xM now that they're under $150). I took a slight detour earlier
setting up the Sheevaplug that came in the mail...finally. I think I
might even have more ARM devices than PPC at home now
You can never have a enough of these boards, to conserve some power,
my Sheevaplug is running rcn-ee.homeip.net replaced an old x86.. 
Regards,
Hi Jon,
>
>> But I do have my 2.6.37-rc3 kernel working pretty great on the panda
>> (same kernel works just fine on my beagle's..) Right now only the
>> smp/dual core, uart, usb/ehci, usb/eth work.. I haven't figured out
>> the display stuff yet, sgx, dsp, audio, etc..
>
> Cool. btw, I can't boot the latest 2.6.37 RC kernel from your site on my
> xM rev. A1 here. It's just hanging after uncompressing the kernel. It's
> possible that it's pilot error due to being late in the evening (4am). I
> would love to debug it, once I get a reply to my question on using the
> Flyswatter with the Beagle. Do you use a debugger with yours? I suppose
> you might even have your own BDI
> for a day job and went into "Enterprise Linux" I lost that toy.Double check your console=tty*2 setting in your bootargs..
Pre 2.6.37 is ttyS2, Post 2.6.37 is ttyO2 'O' as in Omap...
Ouch. That's got to be it then. Thanks for that.
Nope, no debugger here, just using a serial port with all the builtin
kernel debugging tools..
I hope someone knows how to get the Flyswatter working because that'll
help with testing things like Flattened Device Tree migration.
> I'm away in California next week at a Yocto event but I'll look forward
> to poking some more when I get back to Boston (I also might have to buy
> another xM now that they're under $150). I took a slight detour earlier
> setting up the Sheevaplug that came in the mail...finally. I think I
> might even have more ARM devices than PPC at home nowYou can never have a enough of these boards, to conserve some power,
my Sheevaplug is running rcn-ee.homeip.net replaced an old x86..
Indeed. This one replaced an old ITX. Everything at home is on various
Masterswitches, and this one is kinda the emergency box that can be left
running even if everything else is shut down due to someone staying in
my home office/spare room not liking the noise of the machines
Jon.
Yup. That was it. Similarly, the USB network interfaces changed so that
the network port is now usb0.
Jon.