Tiny Core on the Beaglebone

[tinycorelinuxrocks]

Would it be very difficult to add ALSA and jackd support to Tiny Core or Micro Core on a BeagleBone?

[curaga]

You'll need to build your own kernel to support that board, we don't target the beagle family currently.

Besides that, those are "just" extensions, so you could build them. The ARM repos aren't quite full yet.

[tinycorelinuxrocks]

BeagleBone doesn't work from a vanilla kernel yet anyway.  Compiling my own kernel is no problem.

Copy Mode looks like the right choice for me so I can run everything including application extensions in RAM.

It looks like the ARM application extensions are very limited.  Can I compile jack in order to use it as an application extension?

[curaga]

The members on ARM will have to answer the specifics, I'm not currently involved there. But in general, if jack runs on ARM, why couldn't you compile it?

Certainly you may need to also build dependencies.

[tinycorelinuxrocks]

I have Gentoo running on the Beaglebone and I'm trying to get Tiny Core working.  Should I need script.bin for this?  I have uEnv.txt, MLO, and uImage from Gentoo so I don't think I need the Tiny Core uImage or boot.scr.  I'm not sure where script.bin comes into play.  I don't use one with Gentoo.  If I start with my Gentoo boot stuff, should I only need uCore from Tiny Core?

[roberts]

Script.bin, I believe, is an Allwinner specific, configuration file. It happens to be "compiled". Typically used to set devices, e.g., vga or hdmi, and screen resolutions, etc. I am not familiar with beagelboard.
Which version of arm does it support? Perhaps, I should consider posting a tarball of our rootfs then likely with your existing beagleboard kernel and modules you might have a starting point.

[tinycorelinuxrocks]

The Beaglebone is ARMv7.  I would love to get access to that rootfs.  I'm having a hard time getting uCore to load.  I tried adding the following to uEnv.txt:

fatload mmc 0 0x43100000 uCore

and changing:

bootm 0x80200000

to:

bootm 0x80200000 0x43100000

but I get the following "data abort":

## Booting kernel from Legacy Image at 80200000 ...
Image Name:   Linux-3.6.0-rc7-00219-g35e0f42
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2878667 Bytes = 2.7 MiB
Load Address: 80008000
Entry Point:  80008000
Verifying Checksum ... OK
data abort
pc : [<8ff99480>]          lr : [<8ff996ac>]
sp : 8fe6abd0  ip : 8fe6d163     fp : 00000001
r10: 00000002  r9 : 00000000     r8 : 8fe6af68
r7 : 8ffbaebc  r6 : 43100000     r5 : 8ffbaec0  r4 : 43100000
r3 : 00000000  r2 : 00000010     r1 : 00000000  r0 : 43100000
Flags: nZCv  IRQs off  FIQs on  Mode SVC_32
Resetting CPU ...

I have the uCore file at /uCore.  How can I get uCore to load so init will work?

[tinycorelinuxrocks]

I've gotten farther along, but I get one of these two errors when loading the ramdisk:

RAMDISK: Couldn't find valid RAM disk image starting at 0.

Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid

Is it possible that the provided uCore doesn't work on the Beaglebone?

[roberts]

I have posted the rootfs for armv7 used in the allwinner build.
Hope that will be helpful.
See: http://distro.ibiblio.org/tinycorelinux/4.x/armv7/

[tinycorelinuxrocks]

Thanks roberts.  I wasn't able to get a shell prompt until I added rdinit=/bin/sh to my bootloader config.  Should that be necessary?

May I ask why proc is unmounted by /init?

[tinycorelinuxrocks]

I've installed jack and its dependencies by extracting archives I created on a Gentoo system.  I'm hoping to install stuff this way instead of via the Tiny Core application management system.  I have:

# ls -l /usr/bin/jackd
-rwxr-xr-x    1 root     root         22148 Nov  4  2012 /usr/bin/jackd

But I get:

# /usr/bin/jackd
sh: /usr/bin/jackd: not found

Does anyone know what happened?

[tinypoodle]

dynamically or statically linked?

[tinycorelinuxrocks]

I believe my Gentoo install is dynamically linked.  What can I do to put together archives for jack and its dependencies that will work on Tiny Core?  I would rather not use the Tiny Core application management system.

[tinypoodle]

You could install compile.tcz and some other dev extensions and compile by yourself.

For details on how to create extensions consult wiki.

BTW, prefix for post-install stuff (incl. tcz extensions) should be /usr/local rather than /usr

[tinycorelinuxrocks]

I'm on ARM and compile.tcz doesn't seem to be available yet:

http://distro.ibiblio.org/tinycorelinux/4.x/armv7/tcz/

Are there any other options?