Tiny Core Base > Raspberry Pi
Towards Core (microcore) on Raspberry Pi
bmarkus:
Tested with different QEMU versions on WINDOWS.
1.0.x - kernel panic, same as on TC
1.1.x - OK
1.2.x - OK
Would be good a QEMU 1.2 update
curaga:
I'm really short on time nowadays. Feel free to post an update, the configure arguments are in the usual place:
ftp://ftp.nluug.nl/pub/metalab/distributions/tinycorelinux/4.x/x86/tcz/src/qemu
bmarkus:
--- Quote from: curaga on September 12, 2012, 12:13:57 PM ---I'm really short on time nowadays. Feel free to post an update, the configure arguments are in the usual place:
ftp://ftp.nluug.nl/pub/metalab/distributions/tinycorelinux/4.x/x86/tcz/src/qemu
--- End quote ---
Thanks for the link.
Now I have QEMU-1.2.0 built on TC. It looks OK, Raspbian qemu-kernel works like on the WINDOWS version, piCore 4.6.1 starts. I will submit it after some testing and fine tuning.
bmarkus:
Status after more testing. piCore using qemu-kernel from the Raspbian emulator for Windows works on TC 4.6.1 except kernel modules due to the mismatch of kernel versions. Raspbian 2012-07-15 works fine in console mode. Starting X it continously restarts (telinit 5), startx seems to be freezing after the raspberry image, don't know why. Same setup is OK on Windows.
Anyhow, it can be a usable starting for piCore and QEMU variant of piCore kernel.
There are 'pflash write unimplemented command sequence...' errors during boot. There is a patch, applying it this goes away and replaced with more flash related errors, so I didn't apply the patch. Do not know is it related to X problem or not.
Anyhow, it is not for the first version.
roberts:
The posted http://distro.ibiblio.org/tinycorelinux/4.x/arm/armv6/rpiCore-20120907.img.gz
seems to be testing quite well.
I am using a pendrive for my backup and extensions. It is recognized and is easily available via
the standard mount /mnt/sda1. You can backup and restore from it, you can tce-setdrive it.
You can tce-load -i links and it will use the link /etc/sysconfig/tcedir. All that seems to be working.
You can easily specify the usual boot commands by editing cmdline.txt, e.g., waitusb=5:LABEL=mypi tce=LABEL=mypi
onboot works as expected!.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version