That's the old image builder or the old hwpack.

Yep that's what I was looking for ... thanks for testing. Obviously this issue is not just limited to my tablet. I'll see if I can get that to work. Maybe I can mix up the old boot loader with the new kernels and have a better success (actually that's what's running on my tablet 3.4.75 kernel on the old boot loader) ... I'll haveto do something.

Cubieboard 2 from the new hwpack or from the old hwpack ? just to know if on some boards the new bootloader is working.
Also are you usning 14.0 or 14.1 miniroot for userland on the booting setup ?

You can have a go at building a custom kernel to try support all you need.

You should be passing and environmement variable to uboot like this (your root may be on mmcblk0p1 oe something like that since you have a single partition scheme)
I write that to uEnv.txt

Or does that happen only on the very first boot ?

1 members found this post helpful.

Hi,

Yes, I did! But it does not boot.
I just tried it again, here what I did:
Deflate the downloaded file:
Putting the card into the slot, switching power on:
Nothing appears. The blue LED is glowing (not flashing). The other LEDs are dark.
My Screen (HDMI) is dark.
No boot, sorry.
But cubietruck is NOT booting the preinstalled Android (nand), like when no SD card is inserted. It freezes at the SC card. You know, what I mean.

I am not an beginner in Linux, I used Linux (Slackware) over 10 years. But I am a beginner in programming, there is no specialized knowledge.
So I think, I don't made something wrong.

Sincerely,
Arnim!

Arnim000: can you pleas checkout my questions @ post #16 ... it will help be debug what's wrong with the new image creator/hwpack.

Hello,

Of course, I will answer your questions!!
But you posted while I was answering the other post.
Writing english takes some time;-)

With the old hwpack, I used the old miniroot 14.0.
With the new hwpack, I used the new minitoot 14.1.
I don't mixed new and old.

I tested your new Scripts.
New hwpack, custom_hwpack_3.4.61.tar.xz + minitoot 14.1 + Kernel 3.4.61
With option "cubietruck", there is no boot.
With option cubieboard2, my cubietruck is booting.
Booting with miniroot 14.1 + new hwpack + option "cubieboard2"

This is the reason, while I am waiting for someone, who collates a slackware image for cubietruck ;-)

Sincerely,
Arnim!

I noticed that my image creator script does not ckean up the /tmp/hwpack directory in which the hwpack is exploded.
If you did not clean it up manually I think you have a mixed up thing anway. I'm changing the script to clean up before extracting is a previous /tmp/hwpack is found.

Could you pleas remove /tmp/hwpack and try again with the new hwpack ?

Good to know that the 14.1 userland is booting fine on my image creator (I've not got round to testing it).

happens on all boots unless you patch rc.S to comment the 'read junk' line that stops the boot sequence

I'll try the ro rootwait

EDIT: it worked, thanks

try with
If it doesn't work I'll upload a new image later today

I got round to doing a bit of testing on the new script and it seems to be working fine.
I tried also the new script.bin with the old boot stuff and is seems to work fine.
I removed boot.cmd: after having a closer look at how uboot loads the various environment settings it turnes out that boot.cmd is ignored.

If Arnim000 can boot his cubietruck by using the new hwpack and selecting cuibieboard2 (and after having cleaned up /tmp/hwpack) then there is something wrong only with some boards boot stuff. If he cannot thenn I'll assume that all the boot stuff is bust in the new hwpack.

Good ... please go to the post where I told you this and hit "yes" beside "Did you find this post helpful?"

I used to do this but it turns out that it has no better success then doing the cat thing but it has a really bad side effect: it writes the flash in 1K blocks while the internal flash erase block is pprobabbly much bigger then that (128k)... this could turn out equivalent to erasing the blocks several times.

1 members found this post helpful.

@cycojesus:
It does not work, same result as writing to SD card with cat.

@louigi600:
First test:
I deleted /tmp/hwpack.
Then calling create_raw_image script,
with new hwpack + miniroot 14.1 and option cubietruck

RESULT: No boot. Same result as without deleting /tmp/hwpack

Second test:
Again, I deleted /tmp/hwpack.
Then calling create_raw_image script,
with new hwpack + miniroot 14.1 and option cubieboard2

RESULT: Cubietruck is booting preinstalled Android from nand.
What is that? No stop at the SD card?

I have done this test a second time. Again, Android is booting:-(

After deleting /tmp/hwpack before creating an new image, nothing is working.
So, you are right, there is something mixed up in /tmp/hwpack, if it is not deleted before creating a new image.


Sincerely, Arnim!

I'm uploading a new image updated with all the updates I made on my script. I've tested it and it boots fine after writing it to sd using cat. Default root password is 'password'
A major change (although it should be transparent) is the use of the 'official' linux-sunxi kernel instead of patwood's. I know little about patwood's patches and as a slacker I tend to prefer vanilla upstream (next stop is trying kernel.org latest stable kernel if possible.)

@louigi600:
interesting info about dd and cat. I've changed the README accordingly

To get you going with something again:
clean up /tmp/hwpack (or download the new script that does that for you) and create an image with the old hwpack. If you like you can use 14.1 miniroot as I've tested that it does boot but I've not got round to adding in there the pits and pieces I did to the 14.0.

If you need a newer kernel then you can mouunt the SD cart root and boot and copy over by hand from the new hwpack:
/tmp/hwpack/kernel/3.4.61_uImage.sun7i to the sd boot/uImage
/tmp/hwpack/modules/3.4.61.sun7i+ to sd lib/modules/

this should get you booting with the old bootloader but the new kernel.

I realized there is a naming convention error in the newhwpack that will fail to copy over the modules ... this may accounf for the keyboard not working at some of the test you did.
I'll fix that asap along with something to get both hwpacks booting right.

Hello,

@cycojesus:
Your new image v0.3 is booting.
I can't modprobe module bcmdhd for wlan, because of an error.
modprobe bcmdhd
ERROR: could not insert bcmdhd: No such device

Amazing, I know, there is such a device;-)


@luigi600:
Creating an image with old hwpack and new 14.1-rootfs is working.
I can boot with it.

But booting old hwpack and old 14.0 rootfs, I have no keyboard, same as yesterday.
I have mounted SD card for changing the kernel and modules. This is working too.


Old hwpack + old 14.0-rootfs, after writing the SD card, mount the second partition from SD card, and have a look at /lib/modules!!
There are no modules! This directory is empty.
The empty directory on SD card is named /lib/modules/3.4.43.sun7i+
But the directory inside the old hwpack is named 3.4.43.sun7i
(Without ending "+"!)
No modules on SD Card --> no keyboard.

Inside the new hwpack, the modules directorys are ending with "+".
Here the modules directory on the SD card is not empty. My keyboard is working.

You mean the old hwpack, I think....

Bye,
Arnim!

I fixed the script for the new names and broke on the old hwpack, now it should work with both.
You can have the new merged hwpack with new kernel, new boards and old boot environment.
I tested it on my tablet ant it's booting ... but I'd appreciate if you had a go at it too.

Don't hesitate in mixing miniroots with new and old ... the new stuff was not to support the new 14.1 version but rather to support more boards, get newer kernel and a few other minor fixes in the script itself.

I'm not using wifi so I didn't notice this before. Indeed it's not working and after a bit of research it seems I can blame the kernel for that -- http://linux-sunxi.org/A20-Cubietruck#Wifi

I tried building a vanilla linux-3.14-rc4 but it didn't boot. Maybe I'll have better luck with sunxi