I believe you should first try with the basic approach, the one in here .

Then if this doesn't work, try the solution that kuleszdl posted changing the boot.scr..
It is indeed a bit pesky, you need to understand the uboot boot process, and its a bit difficult for someone starting..

basically you have a text file called 'boot.cmd', and you need to generate a binary file from that one called 'boot.scr'.
every change that you make to 'boot.cmd' and you need to compile it in binary format 'boot.scr', it will substitute previous 'boot.scr' with the new one..

But I believe you should first go with the default option
So forget for now the 'boot.scr'

The serial connection,
Is very important to connect the pins in a correct way..

You should only connect Ground, TX,RX..

How to connect:
The Board has:
1)GND
2)TX
3)RX

The usb-serial adapter has( at least):
1)GND
2)TX
3)RX

So you conect:
1) Insert adapter in your computer

2)
The ground from adapter with ground from the board
The TX from adapter with RX from the board
The RX from adapter with TX from the board

3) Use a serial adapter application like picocom, for example, or other and start it

4) Only then, you apply power to the SBC board

After this you should see the output in the serial console output, and later a text based installer

After some days the USB - serial adapter arrived. But it had to stay in the envelope.

I tried to mount the written flash card and alter boot.scr
The truck booted up und continously tried to boot from network.
But i changed converted the boot.cfg right on the mounted SD card.
This may have been not the right war, because it didn't work.
After some attempts i did quit this.

Then i moved to read about extlinux.conf
I'm could not try this, there are too many questions:

It says, it's about booting from ext filesystem.
After putting firmware and partition archives to SD card, there's only one vfat partition.
Others reported they had two partitions with using extlinux method.
First guess was formatting the card to ext filesystem, but then i still didn't
have an idea about the second partition i was missing.

So i will wait and gather some information about this before i will have a next try.
It looks too promising not to try it.

Instead i opened the usb <-> uart adapter envelope and installed it this afternoon.

The information about using the right connectors came from here:
https://andre.blaatschaap.be/2013/01/cu … onnection/

https://lists.denx.de/pipermail/u-boot/ … 00162.html

Anyways, you should now have quite a few approaches to try. ;-) Good luck!

You can try however to test the changes kuleszdl, proposed..
Have you tried the image here ?
http://deb.devuan.org/devuan/dists/beow … rd-images/

After the zcat process..
You can mount the image with:

apt-get install u-boot-tools
mkdir /mnt/iso
mount -t vfat -o loop,offset=$((2048 * 512)) /path/to/Cubietruck.img /mnt/iso
cd /mnt/iso
# To see the boot.scr code..
strings boot.scr

create a boot.cmd file with the content you want..then generate the new boot.scr with:

mkimage -C none -A arm -T script -d boot.cmd boot.scr
sync
cd /
umount /mnt/iso

then try the changed boot script within  the changed Cubietruck.img..
burn Cubietruck.img to sdcard, and test if you can access, otherwise you will need the adapter..

The problem of install via normal procedure, is that you need display working, and keyboard, and ethernet..
ethernet is the easy part, display is the most difficult one( and sometimes keyboard too )
Because of this factors, we choose the serial install that works always

You are right about the USB issue, I completely forgot that. The boot.scr has some kind of binary format that is generated from boot.cmd. This can be done using the mkimage command as described in the sunxi wiki:

https://linux-sunxi.org/U-Boot

As an alternative, you could try to boot using extlinux.conf instead of boot.scr. I prefer this over the boot.scr method used by Debian.

Alternatively, you could also try to set the parameters using uEnv.txt.

Good luck, and maybe you get it working before your usb-serial-adapter arrives. :-)

Moin,

I've read somewhere that a USB hub in between could possibly make a difference,
but it didn't.

Hello,
In the README section, in the end, the method specified to install is via serial connection..
Using a usb-to-serial converter, exactly because it prevents that problem with displays

Thank you a lot !

I'm sorry ... Happy new year !!

I'd love to be able to go to the boot prompt and i tried two different keyboards
but neither of them worked. It looks like they'are simply not recognized at the
stage where one could interrupt the boot process.
I've read somewhere that a USB hub in between could possibly make a difference,
but it didn't.
Is it possible to change the - is it the boot.scr file ? - boot process somehow ?

afaik this is a cubietruck-specific issue. Try the following in u-boot:

setenv bootargs console=tty1 fb=false
saveenv 
boot

Btw.: Welcome to the forums!

I'm not able to even start the installer armhf version on a Cubietruck.
I've tried ASCII as well as beowulf version. For both of them the pinned
instructions do not work at all.

The system boots up.
Beowulf reports starting the kernel. But the screen just goes black.
ASCII shows two tux symbols after starting the kernel. But it goes
black as well.
LEDs do not show any activity at all. Just the green led.

For beowulf i did:
zcat firmware.Cubietruck.beowulf.img.gz partition.img.gz > /dev/sdj

For ascii:
xzcat devuan_ascii_2.0.0_armhf_sunxi.img.xz | sudo dd of=/dev/sdj bs=2M
dd if=Cubietruck_defconfig.bin of=/dev/sdj bs=1024 seek=8 && sync

Am i missing something ?

Thanks,
    Sascha