dCore Import Debian Packages to Mountable SCE extensions > dCore Armv7
Alwinner A20
Jason W:
Hi petrasl,
This is the dCore section, you would be better to ask in the PiCore section the link is below.
http://forum.tinycorelinux.net/index.php/board,57.0.html
jgrulich:
Hi All,
is there any progress in the Tiny Core implementation into the A20 Banana Pi?
roberts:
Here are my notes on such matter:
When trying to use an existing kernel from another Arm Linux device:
Requirements:
=============
The native kernel must support initrd.
Boot your vendor supplied arm device. Then check kernel by:
gunzip -c /proc/config.gz | grep INITRD
We are looking for the result of:
CONFIG_BLK_DEV_INITRD=y
If this is not the case then you will have to build a new kernel to support Tiny Core.
Note: Sometimes the kernel configuration file is located the /boot directory or may be available on the device support website.
Note: Sometimes an additional "recovery kernel" in included with initrd support and can be used.
Additionally:
=============
loopback block device as a module or in kernel.
squashfs file system as a module or in kernel.
are both required to use any Tiny Core extensions.
If included in the kernel great, if not the above modules can be packed into a .gz extension.
Since all .gz extensions are loaded before any other extensions this should be an easy task.
Optionally you could unpack the uCore and repack to include these modules.
Allwinner Configuration files.
==============================
Configuration file: boot.scr
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The "compiled" boot.scr file contains instructions to uboot for kernel and initrd.
To decrypt boot.scr use:
dd if=boot.scr of=boot.script bs=1 skip=72
The resulting boot.script is a plain text file that you can edit.
Add the initrd boot specifications and, as needed, typically change fatload to ext2load to match existing vendor supplied kernel boot specifications.
To "compile" back to a useable boot.scr do:
./mkimage -C none -A arm -T script -d boot.script boot.scr
Next copy this new boot.scr together with the uEnv.txt to target SDCARD.
Configuration file script.bin:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Often with Allwinner devices there is a script.bin file. This is a "compiled" configuration file of key=value pairs. It is typically placed alongside the kernel, i.e., same partition. The exact name of this file can vary and is specified via uboot.
To decrypt script.bin use: bin2fex
./bin2fex script.bin > script.fex
The resulting script.fex can now be edited with a simple text editor.
When finished convert back via fex2bin
./fex2bin script.fex > script.bin
Reboot to effect.
==================
After any changes to any configuration file a reboot is required.
If it does not boot to a prompt then kernel may not support initrd. In this case you must compile a kernel. Otherwise...
At the boot prompt (see readme 1st for further explanation):
$ tce-setdrive
For a trivial example try:
$ importsce sl
$ loadsce sl
$ sl
If sl fails to load then likely you need the squashfs and loopback modules. Look for it from the vendor supplied SDCARD. If vendor supplied such modules then make a cpio gz and place into the tce-dir and reboot.
As root:
# depmod -a
#exit
$ loadsce sl
$ sl
If successful then proceed with X desktop as explained in the readme files.
keksl22:
Hi!
Gents, two questions:
- do you plan to open a dCore HW section for Banana-PI or even a "banana-core"?
- is there a chance to get a BananaPi boot using e.g. a Cubietruck uImage - just for testing? As far as I read both run on Allwinner A20 ARMs, and the A20 should be able to run the A10 compiled code.
Well, reason for asking:
I'd like to run the B-Pi as a samba server (in parallel to a R-PI having a UMTS stick connected for internet access) using the SATA connector. Would be great if dCore or a piCore-variant ;) could do the OS job!
To get myself started I downloaded the cubieboard uImage, uCore etc.
I used the original Bananian uBoot and exchanged the uImage + edit the uEnv.txt.
Unfortunately the green LED remains on (no heartbeat) and in the /dev/ttyS0 I see it got stuck calibrating the delay loop...
So I updated and tried a uImage from the release candidate section. (/tinycorelinux/dCore/armv7/Allwinner-A10/release_candidates/)
What I see is:
U-Boot 2014.04-10694-g2ae8b32 (Sep 03 2014 - 20:53:14) Allwinner Technology
CPU: Allwinner A20 (SUN7I)
Board: Bananapi
I2C: ready
DRAM: 1 GiB
MMC: SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: dwmac.1c50000
[...]
Starting kernel ...
<5>Linux version 3.4.103 (root@box) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Thu Feb 26 11:30:43 PST 2015
CPU: ARMv7 Processor [410fc...] revision 4 (ARMv7), cr=10c53...
<6>sunxi: Allwinner A20 (AW1651/sun7i) detected.
[..]
<6>sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
<6>Calibrating delay loop...
no more ttyS0 output ... no HDMI screen, LEDs red + green are active
If you need the full log, please let me know. I just copied - as I think - the most interesting sections
Any ideas / updates on A20 dCore?
Thanks,
Axel.
vdelf:
I am now running dCore on a BananaPi using selfbuild mainline u-boot, mainline selfbuild zImage 4.0.5 and uCore from downloads section. HDMI, Framebuffer, USB, network works.
I can post/send kernel config and Boot.scr if someone wants to try.
Sent from my Nexus 4 using Forum Fiend v1.3.3.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version