dCore Import Debian Packages to Mountable SCE extensions > Allwinner A10
Cubieboard Install
beerstein:
good point - never thought of that.
nand memory I call the built in memory in cubietruck.
sd memory I am calling the microSD cards, which fit into a slot on the cb3 board and act like a hard drive.
RaspberryPi f.i. has no nand - just an SD card slot
Peter Pudney:
I am not sure how necessary it is to write zeroes to the beginning of the SD card, but it is recommended on several forums. I have omitted this step a few times, without any problems.
Copy just the files, not the folders, from the hardware pack and TC distribution to the SD card. My SD card looks like this:
$ ls -l
total 12864
-rwxrwxrwx@ 1 pjp staff 304 17 Mar 2013 boot.scr
-rwxrwxrwx@ 1 pjp staff 45088 23 Jun 2013 script.bin
-rwxrwxrwx@ 1 pjp staff 2925169 2 Jan 06:10 uCore
-rwxrwxrwx@ 1 pjp staff 117 3 Sep 22:35 uEnv.txt
-rwxrwxrwx@ 1 pjp staff 3487576 23 Jun 2013 uImage
uImage and script.bin are from the kernel folder in the Cubie hardware pack; boot.scr, uCore and uEnv.txt are from the TC distribution.
I copied the files to the SD card using the Mac OS X GUI, which set the permissions as shown above. My SD card also contains a few hidden files that OS X uses for icons and trash, but these do not appear to effect anything.
You can monitor the boot process using a serial TTL to USB cable (supplied with my Cubieboard 2): http://linux-sunxi.org/Cubieboard/TTL
tinypoodle:
--- Quote from: beerstein on January 17, 2014, 10:21:54 AM ---Hi again: I followed your instructions - formatted the 2GB sd card FAT16 using gparted in Linux.
Which one of these files must executable? Could there be a problem with ownership?
--- End quote ---
msdos/fat filesystems do not provide for POSIX permissions at all ;)
beerstein:
Hi Peter Pudney:
Thanks for the info. I tried several approaches and - no luck. In one case I produced a microSD which boots my CT into the NAND android 4.2.2 -- wow this is strange. The other cards did not boot at all.
My ct is Allwinner A20 2x cortex A7. The CB2 is also A20 and 2x cortex A7. But I am still not sure whether I should use the files from:
http://dl.linux-sunxi.org/users/oliver/cubietruck_hwpack.tar.xz
or from:
http://dl.linux-sunxi.org/users/hramrach/cubieboard2-linux3.3_hwpack.tar.xz --> you used his one
Here is how my content of the cubietruck_hwpack.tar.xz file looks like:
cubietruck hwpack content:
/cubietruck_hwpack/bootloader
/cubietruck_hwpack/kernel
/cubietruck_hwpack/rootfs
in /cubietruck_hwpack/bootloader there are the following files:
/cubietruck_hwpack/bootloader/sunxi-spl.bin
/cubietruck_hwpack/bootloader/u-boot.bin
/cubietruck_hwpack/bootloader/u-boot.img
I discovered that I have an additional file here named:u-boot.img
I do not know what to do with this file?
Question: When you dd the two .bin files to your sd card, did that generate the two partitions needed for a bootable sd card?
A bootable sd card needs the boot loader at the beginning of the partition up to sector 2048. After that the "boot stuff" is looking for an ext2 partition. In an older http://linux-sunxi.org/index.php.. article "Bootable SD card" it is recommended that you format this separate /boot partition FAT and after the dd. This does not make sense because it overwrites the code in front of sector 2048 and in this case the FAT partition starts at sector 1. Which means no u-boot no boot at all.
I might be almost there if I would know which sunxi-spl.bin and which u-boot.bin I should use. The ones from cubieboard2 or from cubietruck. In addition I need to know what to with that u-boot.img from the cubietruck hwpack?
After that is done I could create a 64 MB ext2 partition starting at sector 2048 which would be the boot partition. Fies: uCore, uEnv.txt and boot.scr probably belong into this partition.
Behind the boot 64 MB boot partition the rext4 root partition could start at sector 133120. So now what belongs into this root partition?
I could put the content from the hw_pack /cubietruck_hwpack/rootfs folder into it?
If somebody could help me here I might be able to have a Core for cubietruck
Peter Pudney:
I suspect you should be using the cubietruck hardware pack.
The "Bootloader" section of the Bootable SD card article (http://linux-sunxi.org/Bootable_SD_card) has an example where u-boot.img is placed at sector 40 instead of placing u-boot.bin at sector 32.
When I partitioned my SD card, the single partition was placed at sector 8192. When I examine the SD card using fdisk I get:
Disk: /dev/disk2 geometry: 966/255/63 [15523840 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 0B 1023 254 63 - 1023 254 63 [ 8192 - 15515648] Win95 FAT-32
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
The "Starting" and "Ending" values do not look right, but my fdisk man page says most modern systems use the "start" and "size" fields instead.
The "Partitioning" section of the Bootable SD card article says you can use only one partition; it is an experimental feature, but it works for me.
When I dd the two bin files they are placed at sectors 8 and 32, well before the single partition.
I ignored the roofs folder from the Cubie hardware pack---TinyCore does not appear to need it.
What messages do you get from the serial port while booting?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version