Cubieboard anyone?

[WarheadsSE]

My apologies, I've been busy with day job. I'll do my best to get to it this weekend.

[WarheadsSE]

http://archlinuxarm.org/platforms/armv7/cubieboard

[ezyclie]

Seems the image compatible with Marsboard http://www.marsboard.com/

[WarheadsSE]

The root filesystem is identical for all a10 boards. Only u-boot & fex file are different.

That said:
'GUN' Linux? And wrote that looks really, really similar to the cubieboard

[gerits]

My system seems to fail when I put the uEnv.txt file. Without this file I can boot it, but it doesn't use the settings from the script.bin.

This file seems a necessary requirement to use the script.bin file. My fixed mac address is not taken into account without the uEnv.txt. Am I doing something wrong?

Content of uEnv.txt:
$this->bbcode_second_pass_code('', 'boot_mmc=fatload mmc 0 0x43000000 ${fexfile}; fatload mmc 0 0x48000000 ${kernel}; bootm 0x48000000
extraargs=rootwait
fexfile=script.bin')

[WarheadsSE]

Pay close attention to the uEnv.txt I provide, and the one you are presenting here. There is a minor, but key difference.

[maribu]

Hi, there!

Has anyone updated to xorg 1.14? Since I did the X-Server crashes randomly on my cubieboard. Most of the time my display server (lxdm) restarts immediately and I have to login again. But sometimes X completely freezes and I have to reboot the cubieboard via ssh.

X crashes mostly after a few seconds and only once lasted about 5 mins before crashing. I'm using xf86-video-fbdev driver (the xf86-video-mali driver is not compatible with the new xorg version) and I guess that there is the problem.

I get a lot of "(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument" on startup of X on the xorg.log

Has someone found a solution for this problem?

Regards,
maribu

[WarheadsSE]

Looks similar to the raspberry pi problem with fbdev

[ambrosa]

Hi guys.
2 hours ago I've received my CubieBoard 1GB RAM. This is my first ARM device so I'm a newbie about this.
My goal is a small server reacheable using SSH. No media center so I'm not interested in hires video output (no X or VLC...)

Without microSD card inserted, the board boot correctly with its Android preinstalled in internal flash. Ok, the board looks to work fine. Red and green LED stay on.
With Android I see video connected with HDMI->HDMI to my Panasonic TV and with HDMI->DVI-D to my Samsung PC monitor (it has only DVI-D input, no HDMI). All looks to work fine.

Now I've installed ArchLinux ARM reading the guide http://archlinuxarm.org/platforms/armv7/cubieboard into a 4GB microSD card but the system doesn't boot. When I power on the board the red LED is on, green LED flash shortly (about 100 mS ?) and then ... nothing. No boot. In my router I don't see any IP leased by DHCPD, no video signal.

I've configured my microSD as follow (all command made using 'root' in my LinuxMint PC)
1) I've inserted the card into an USB adapter. My card is device /dev/sdc
2) Using fdisk I've deleted all previous partition and the I''ve created 2 new primary partitions.
The first type "6 FAT16" and the second type "83 Linux"
$this->bbcode_second_pass_code('', 'tiger ~ # fdisk /dev/sdc
Disco /dev/sdc: 3963 MB, 3963617280 byte
64 testine, 32 settori/tracce, 3780 cilindri, totale 7741440 settori
Unità = settori di 1 * 512 = 512 byte
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Identificativo disco: 0x00000000

Dispositivo Boot Start End Blocks Id System
/dev/sdc1 * 2048 34815 16384 6 FAT16
/dev/sdc2 34816 7741439 3853312 83 Linux
')
The strange thing is that first partition can start only at sect 2048. I don't know how but it looks that first 2048 sect are not available (??)
I've made the first partition bootable.
Formatted with mkdosfs -n BOOT -F 16 /dev/sdc1

This is the content of BOOT partition:
$this->bbcode_second_pass_code('', 'ambrosa@tiger ~ $ ls -la /media/ambrosa/BOOT
totale 3442
drwx------ 2 ambrosa ambrosa 16384 gen 1 1970 .
drwxr-x---+ 4 root root 4096 apr 4 19:05 ..
-rw-r--r-- 1 ambrosa ambrosa 43628 apr 2 19:32 cubieboard_512.bin
-rw-r--r-- 1 ambrosa ambrosa 43628 apr 2 19:32 cubieboard.bin
-rw-r--r-- 1 ambrosa ambrosa 168 apr 4 18:41 uEnv.txt
-rw-r--r-- 1 ambrosa ambrosa 3410548 apr 2 19:32 uImage

')this is uEnv.txt
$this->bbcode_second_pass_code('', 'ambrosa@tiger ~ $ cat /media/ambrosa/BOOT/uEnv.txt
boot_mmc=fatload mmc 0 0x43000000 ${fexfile}; fatload mmc 0 0x48000000 ${kernel}; bootm 0x48000000
extraargs=rootwait ethaddr=00:CE:39:B7:74:4E
fexfile=cubieboard.bin
')
and this is the ROOT partition (formatted with mkfs.ext4 -L ROOT /dev/sdc2 )
$this->bbcode_second_pass_code('', 'ambrosa@tiger ~ $ ls -la /media/ambrosa/ROOT/
totale 88
drwxr-xr-x 19 root root 4096 gen 29 01:24 .
drwxr-x---+ 4 root root 4096 apr 4 19:05 ..
drwxr-xr-x 2 root root 4096 gen 17 00:30 bin
drwxr-xr-x 2 root root 4096 gen 29 01:51 boot
drwxr-xr-x 2 root root 4096 lug 10 2011 dev
drwxr-xr-x 44 root root 4096 gen 29 01:53 etc
drwxr-xr-x 2 root root 4096 dic 6 17:52 home
lrwxrwxrwx 1 root root 7 dic 31 03:47 lib -> usr/lib
drwx------ 2 root root 16384 gen 29 01:23 lost+found
drwxr-xr-x 2 root root 4096 dic 6 17:52 mnt
drwxr-xr-x 2 root root 4096 dic 6 17:52 opt
dr-xr-xr-x 2 root root 4096 dic 6 17:52 proc
drwxr-x--- 2 root root 4096 gen 29 01:51 root
drwxr-xr-x 4 root root 4096 gen 13 01:08 run
drwxr-xr-x 2 root root 4096 gen 17 00:31 sbin
drwxr-xr-x 4 root root 4096 dic 6 17:52 srv
dr-xr-xr-x 2 root root 4096 dic 6 17:52 sys
drwxrwxrwt 2 root root 4096 gen 17 00:30 tmp
drwxr-xr-x 9 root root 4096 gen 13 01:30 usr
drwxr-xr-x 12 root root 4096 gen 13 01:09 var
')

Obviously I've made 'dd' commands as explained in guide section (2).


Any idea ?

[WarheadsSE]

1) you are assuming video out of the box. Wrong
2) do you have a 3.3v serial adapter?
3) do you have the 512MB or 1GB model?