July 09, 2020, 04:37:10 am

News:

Have you visited the Allwinner Chipset wiki? - http://linux-sunxi.org/


Problem flashing cubietruck

Started by exander, January 18, 2014, 12:37:08 pm

Previous topic - Next topic

exander

January 18, 2014, 12:37:08 pm Last Edit: January 18, 2014, 12:43:37 pm by exander
Hi guys (and possibly girls), I am starting to feel like complete idiot.
Yesterday I got my cubietruck, it was loaded with Android.
Today, I got LiveSuit working and flashed it with Lubuntu Destop from the site. It booted, but then stuck, so I wanted to use different image, since then I got either:

--
You are running on Ubuntu

Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugin The Device Path is: /dev/aw_efex0
Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugin The Device Path is: /dev/aw_efex0
Fex_Send error: Invalid argument
Fex_transmit_receive Error: ./eFexCore.cpp, 288
Fex_command Error ./eFexCore.cpp 379
cmd_common_verify_dev 84
GetCurrentStage Failed 141 ./DeviceMessage/ASuitDeviceMessage.cpp
--

or

--
You are running on Ubuntu

Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugout The Device Path is: /dev/aw_efex0
Dev Plugin The Device Path is: /dev/aw_efex0
L225, Exception, returned value of Tools.entry_fel2fes is error.
FelThreadEntry g_Tools_if->Fel2Fes 227
--

depending on the image.

I tried SD images, but i won't boot either (or maybe i am doing something wrong).
I tried flasing different images.

Any help?

Note that commands are run as root.

maxx

Hi exander,

brand new cubietruck board? A20 chip is Rev. A or Rev. B ?

See here: http://docs.cubieboard.org/faq/faqs#a20_version_ab


Which version of Android is running? Android for Cubietruck(v1.01) ?

have a look: http://cubieboard.org/2014/01/13/upgrade-new-android-for-cubietruckv1-01/

Possible it's dram initializing error, so you can fix it with a firmware update? I don't know .. ?

Or your flash image is corrupt. MD5 hash checked? => http://www.cubieforums.com/index.php/topic,1275.msg9346.html#msg9346

cu
maxx

exander

Quote from: maxx on January 18, 2014, 01:24:30 pm
Hi exander,

brand new cubietruck board? A20 chip is Rev. A or Rev. B ?

See here: http://docs.cubieboard.org/faq/faqs#a20_version_ab


Which version of Android is running? Android for Cubietruck(v1.01) ?

have a look: http://cubieboard.org/2014/01/13/upgrade-new-android-for-cubietruckv1-01/

Possible it's dram initializing error, so you can fix it with a firmware update? I don't know .. ?

Or your flash image is corrupt. MD5 hash checked? => http://www.cubieforums.com/index.php/topic,1275.msg9346.html#msg9346

cu
maxx


Brand new, so I suppose new revision (Yes it is rev B according to images).
Somehow flashing started a few minutes ago, but failed at 90% (maybe my fault) and I am back with the same errors.

The device is really bahaving strange.

exander

My problem is that I can flash it, it does not boot from nand. So possible solutions are welcomed.

exander

Very strange, i somehow fixed it.
But some images can't be flashed.
I can flash ct-nand-v1.00-20130911.img, but can't ct-nand-v1.01-20140109.img and ct-nand-v1.01-20140110.img.

What is the best distribution with wifi and ethernet working and full hd video support?