Cubieboard 2 green system board light

[Robert Moskowitz]

What is the meaning of this light?

It start flashing shortly after power up and seems to flash a lot. And
perhaps there are 2 of these lights.

What do (they) indicate?

I am trying to build a F21 alpha SD boot and nothing is happening. The
red power light comes on, but not the green lights, and of course no
firstboot screen info. I don't have my UART connector, so not until
friday (when I get home) will I be able to see if there are any console
messages...

[Henrik Nordström]

ons 2014-07-23 klockan 22:13 -0400 skrev Robert Moskowitz:
> What is the meaning of this light?
>
> It start flashing shortly after power up and seems to flash a lot. And
> perhaps there are 2 of these lights.
>
> What do (they) indicate?

The two green lights are both software controlled, meaning they indicate
whatever the software/operating system you boot on the board uses them
for.

> I am trying to build a F21 alpha SD boot and nothing is happening. The
> red power light comes on, but not the green lights, and of course no
> firstboot screen info.

If it doesn't come on at all during boot then that suggest you have not
got u-boot properly installed on the SD card. u-boot lights one of the
green lights to indicate it has started.

The kernel then takes over the lights when started and uses then for
whatever the kernel is told to use them for. Often one is bound to MMC
I/O indication.

Regards
Henrik

[Robert Moskowitz]

I am following:

https://fedoraproject.org/wiki/Architectures/ARM/Rawhide/Installation

With

https://kojipkgs.fedoraproject.org//work/tasks/4206/7184206/Fedora-Xfce-armhfp-21-20140723-sda.raw.xz

Scroll down to manual install and see the Cubietruck uboot instructions.

Of course the question is should it be /dev/sdb or /dev/sdb1 ???

I used /dev/sdb

[Henrik Nordström]

tor 2014-07-24 klockan 07:48 -0400 skrev Robert Moskowitz:

> https://fedoraproject.org/wiki/Architectures/ARM/Rawhide/Installation

> Scroll down to manual install and see the Cubietruck uboot instructions.

Not sure if Cubietruck SPL works on Cubieboard 2.

Try the one from
http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi/u-boot-sunxi-latest/u-boot-sunxi-cubieboard2.tar.xz

> Of course the question is should it be /dev/sdb or /dev/sdb1 ???

The SPL goes to /dev/sdb.

Regards
Henrik

[Robert Moskowitz]

Thanks! I can't test anymore today (last day at IETF and checked out of
my room). I will try this tomorrow.

Looks like I would use:

dd
if=/home/rgm/u-boot-sunxi-cubieboard2-20140713T154223-2e4c692/u-boot-sunxi-with-spl.bin
of=/dev/sdb bs=1024 seek=8 conv=fsync,notrunc

to install uboot.

[Robert Moskowitz]

On 07/24/2014 10:38 AM, Henrik Nordström wrote:

Well this does not work. And actually the supplied Cubietruck uboot is
booting. there are other problems.

with this uboot I am seeing on the console:

U-Boot SPL 2014.04-10690-g2e4c692 (Jul 13 2014 - 15:47:12)
Board: Cubieboard2
DRAM: 1024 MiB
CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
spl: not an uImage at 1600


U-Boot 2014.04-10690-g2e4c692 (Jul 13 2014 - 15:47:12) Allwinner Technology

CPU: Allwinner A20 (SUN7I)
Board: Cubieboard2
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
Hit any key to stop autoboot: 0
** Unrecognized filesystem type **
** File not found boot/uEnv.txt **
** File not found uEnv.txt **
** Unrecognized filesystem type **
** File not found boot/boot.scr **
22486 bytes read in 218 ms (100.6 KiB/s)
Jumping to boot.scr
## Executing script at 44000000
Welcome to a-b-c 0.63.

Could not successfully auto-detect system type.
You may need to set u_k_addr, u_ramfs_addr, u_dtb_addr, and u_dtb
Will scan for kernels on mmc usb scsi sata ide, using ext2 fat
filesystems with bootm

Starting menu init....

Failed to auto-boot
No value for u_dtb. Use klist and dtblist to select.

a-b-c main menu
---------------
run clist: for a list of known board configurations.
run klist: for a list of kernels.
run dtblist: for a list of dtbs.
run single: for single user target on boot.
run rescue: for rescue target on boot.
run graphical: for graphical target on boot.
run debug: for verbose debug boot.
run normal: for default systemd boot target (default).
run showdefs: for current defaults.
boot or run bootcmd: boot with currently configured parameters.

Enter command from the above list.

** File not found /boot/script.bin **
** Unrecognized filesystem type **
** File not found /script.bin **
sun7i#

=====================================================

And, no there is no /boot/script.bin.