dCore Import Debian Packages to Mountable SCE extensions > dCore Armv7

Running TinyCore on Cortex-A9?

<< < (2/3) > >>

pioj:
Sorry I don't understand the process at all...


--- Quote ---... the tricky thing is to get u-boot to boot the board with the initial root file system containing tinycore -- rather than switching root to a filesystem as most linux distros do.
--- End quote ---

Isn't this supposed to be as 'easy' as tell u-boot what kernel and initrd to load, then let core.gz scripts to do the magic? Aren't they in charge of providing the way to load the system?


As an example, my device is supposed to boot it this way:

--- Code: ---set bootargs 'console=ttyS0,115200n8 vmalloc=384M \
              video=dovefb:lcd0:1280x720-32@60-edid'
ext2load mmc 0:1 0x2000000 /uImage
ext2load mmc 0:1 0x4000000 /uInitrd
bootm 0x2000000 0x4000000
--- End code ---
from: http://www.solid-run.com/mw/index.php/Initial_RAM_Disk

sihorton:
I am in no way an expert in this.

However distributions like ubuntu start up and load an initial root file system into memory, that contains enough to get started, then they switch the root filesystem to the disk and then boot the operating system from there.

Tinycore is different in that the initial root file system that is loaded directly into memory is the OS. It will then scan the disks and load extensions and startup the display manager etc. I remember reading that Roberts said that playing around with uboot to get it to load this initial root file system was a little tricky and was different for each board.

However I might be making mountains out of molehills, since I have not tried yet I do not know how tricky this step will be.

/Simon

sihorton:
Here is roberts reply to the question "Re: Porting between ARM platforms... How is it made?":
http://forum.tinycorelinux.net/index.php/topic,15126.msg86882.html#msg86882


--- Quote ---Having access to a working Debian/Ubuntu system is not too much of an advantage for Core.
Now for most typical traditional distros it is a huge advantage as one would only need to identify and recompile their binaries and swap in their rootfs. Use existing boot loader. Done. That is why shortly after Ubuntu was made available for Mele, you saw several distros become available.

Core is not traditional, it's rootfs is the initrd, so even existing Arm boot loaders need to be studied to accomodate our initrd rootfs.  Since the major work has already been done to create a minimal Core Arm based initrd, I would start with say the a10Core and try to see what adjustments would need to be made for your particular boot loader and hopefully pick a platform that supports Arm v7hf, else be prepared to identify and compile the binaries within a10Core.
--- End quote ---

/Simon

roberts:
If you have access to u-boot for your board then it could be very easy. I would start by using the a10Core image as it uses u-boot. My remarks are based on Allwinner, sunxi. Their git repository has a board specific section. I have compiled such for the boards and provided them here http://tinycorelinux.net/4.x/armv7/hardware/

sihorton:
Yes I have access to uboot and can compile it together with a kernel and then use build root to create a busybox system.

So if I understand correctly hopefully I can take the a10Core and then copy its initial root filesystem (I think its called uImage) and replace my busybox initial filesystem with it and hope that it starts up.

/Simon

Navigation

[0] Message Index

[#] Next page

[*] Previous page