Install ubuntu 12.04 desktop to cubieboard in 5 minutes

[Matson Hall]

dear all,

 

I've make a ubuntu desktop image for cubieboard nand. The download url is http://pan.baidu.com/share/link?shareid=494017&uk=3426192474. this version of ubuntu is using linux-sunxi stage-3.4 kernel.

 

The instruction to install ubuntu desktop is,

1. download the prebuilt image from the link, and extract it

2. start livesuit, and flash to cubieboard

 

 

[Neal Peacock]

On 05/24/2013 11:45 AM, Matson Hall wrote:

dear all,

 

I've make a ubuntu desktop image for cubieboard nand. The download url is http://pan.baidu.com/share/link?shareid=494017&uk=3426192474. this version of ubuntu is using linux-sunxi stage-3.4 kernel.

How did you get around that error with large livesuit images?  Will this write without crashing livesuit?

 

The instruction to install ubuntu desktop is,

1. download the prebuilt image from the link, and extract it

2. start livesuit, and flash to cubieboard

 

 

--
You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

-- 
Neal Peacock
PengPod

[Dmitriy B.]

How did you get around that error with large livesuit images?  Will this write without crashing livesuit?

I'm also interested in this, I have 2GB max partiton right now. If you used sunxi-bsp, could you please show your changes/send patches.

Also you used to push stuff to https://github.com/matson-hall/allwinner-pack-tools, could you please update it if you automated the image generation with this?

Best Regards,

Dmitriy Beykun

[Matson Hall]

I just split the big partition to several smaller partitons. the have not fixed the 512MB limitation of single partiton issue of allwinner-tools. It's a bug  of some binary program in allwinner-tools which I don't have the source code. A good news is  the new packing enviroment of a20 have fixed such issue, and the bad news is it's a bit different from the old one.

 

2013/5/25 Dmitriy B. <rzk...@gmail.com>

--

[Matson Hall]

2013/5/25 Neal Peacock <kuliman...@gmail.com>

On 05/24/2013 11:45 AM, Matson Hall wrote:

dear all,

 

I've make a ubuntu desktop image for cubieboard nand. The download url is http://pan.baidu.com/share/link?shareid=494017&uk=3426192474. this version of ubuntu is using linux-sunxi stage-3.4 kernel.

 

How did you get around that error with large livesuit images?  Will this write without crashing livesuit?

The image won't have such issue with livesuit

[Matson Hall]

2013/5/25 Dmitriy B. <rzk...@gmail.com>

How did you get around that error with large livesuit images?  Will this write without crashing livesuit?

I'm also interested in this, I have 2GB max partiton right now. If you used sunxi-bsp, could you please show your changes/send patches.

Also you used to push stuff to https://github.com/matson-hall/allwinner-pack-tools, could you please update it if you automated the image generation with this

 I used the sunxi-bsp to generate the cubieboard_livesuit.img. The modification is a bit ugly right now, but anyway, I will try to push the patches to sunxi-bsp. 

 

 

Best Regards,

Dmitriy Beykun

[Neal Peacock]

On 05/24/2013 07:44 PM, Matson Hall wrote:

I just split the big partition to several smaller partitons. the have not fixed the 512MB limitation of single partiton issue of allwinner-tools. It's a bug  of some binary program in allwinner-tools which I don't have the source code. A good news is  the new packing enviroment of a20 have fixed such issue, and the bad news is it's a bit different from the old one.

I'm working on the A31 tools and I'm still seeing a problem if my partition is larger than 512mb.  So I tried creating another partition in the sys_partition.fex file with another ext4 file, from what I can tell dragon is just ignoring it when packing.  What else needs to be added so that next partition gets created?

 

2013/5/25 Dmitriy B. <rzk...@gmail.com>

How did you get around that error with large livesuit images?  Will this write without crashing livesuit?

I'm also interested in this, I have 2GB max partiton right now. If you used sunxi-bsp, could you please show your changes/send patches.

Also you used to push stuff to https://github.com/matson-hall/allwinner-pack-tools, could you please update it if you automated the image generation with this?

Best Regards,

Dmitriy Beykun

--
You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

-- 
Neal Peacock
PengPod

[Tom Cubie]

On Fri, Jun 21, 2013 at 8:48 AM, Neal Peacock <kuliman...@gmail.com> wrote:
>
> On 05/24/2013 07:44 PM, Matson Hall wrote:
>
> I just split the big partition to several smaller partitons. the have not
> fixed the 512MB limitation of single partiton issue of allwinner-tools. It's
> a bug of some binary program in allwinner-tools which I don't have the
> source code. A good news is the new packing enviroment of a20 have fixed
> such issue, and the bad news is it's a bit different from the old one.
>
> I'm working on the A31 tools and I'm still seeing a problem if my partition
> is larger than 512mb. So I tried creating another partition in the
> sys_partition.fex file with another ext4 file, from what I can tell dragon
> is just ignoring it when packing. What else needs to be added so that next
> partition gets created?

For A20 and A31, the problem is solved. There should be no issue when
packing, the problem happens when flashing with the old livesuite. Not
sure what A31 tools you are using.

Keep simple, stay foolish.

[Neal Peacock]

On 06/21/2013 01:53 AM, Tom Cubie wrote:
> On Fri, Jun 21, 2013 at 8:48 AM, Neal Peacock <kuliman...@gmail.com> wrote:
>> On 05/24/2013 07:44 PM, Matson Hall wrote:
>>
>> I just split the big partition to several smaller partitons. the have not
>> fixed the 512MB limitation of single partiton issue of allwinner-tools. It's
>> a bug of some binary program in allwinner-tools which I don't have the
>> source code. A good news is the new packing enviroment of a20 have fixed
>> such issue, and the bad news is it's a bit different from the old one.
>>
>> I'm working on the A31 tools and I'm still seeing a problem if my partition
>> is larger than 512mb. So I tried creating another partition in the
>> sys_partition.fex file with another ext4 file, from what I can tell dragon
>> is just ignoring it when packing. What else needs to be added so that next
>> partition gets created?
> For A20 and A31, the problem is solved. There should be no issue when
> packing, the problem happens when flashing with the old livesuite. Not
> sure what A31 tools you are using.

Yes, I can pack the image the problem is in flashing. I'm using
PhoenixSuit and its the newest one as far as I know. I attached a
picture of the error message, I'm not sure if it will come through. I've
tried using the Linux flashing tools but they always seem to freeze when
I try them.

Any thoughts about what to try would be appreciated.

Also here is the serial output on the device when the error happens.

PHY_PageReadSpare bad flag,bank 0x00000000 block 0x000003ff,page 0x00000000
plane 1: ch: 1, 0x0x40000000, 0x0x00008000
get mbr error
get mbr error, set 1 part as nanda
[ 31.489]Fed:nand_lgc_init, Nand cache open
[ 31.492]Fed:erase=1, hasPrivatePart=0.
[ 31.496]Fed:nand logic size [0x00000000, 0x00ec0000]Sec.
[ 31.502]Fed:-------------------------------------------------
[ 31.508]Fed: Byebye, Nand Register.
[ 31.514]Fed:-------------------------------------------------
[ 31.521]FES:INFO : run addr = 0x00000000 , type = 1437204482
[Read_single_page] NFC_ReadRetry 2 cycles, ch =1, chip = 0
[Read_single_page] block = 2044, page = 4, RetryCount = 0
[ 32.909]FES:---------------------------------------------------
[ 32.910]FES:fes_crc = 0x00000000
[ 32.914]FES:media_crc = 0xf6b6e4bf
[ 32.917]FES:---------------------------------------------------
[ 32.966]FES:---------------------------------------------------
[ 32.966]FES:fes_crc = 0x00000000
[ 32.970]FES:media_crc = 0xc47dc5c6
[ 32.974]FES:---------------------------------------------------
[ 35.633]FES:---------------------------------------------------
[ 35.633]FES:fes_crc = 0x00000000
[ 35.637]FES:media_crc = 0x2de174d4
[ 35.641]FES:---------------------------------------------------

Neal Peacock
PengPod

[Neal Peacock]

On 06/21/2013 01:53 AM, Tom Cubie wrote:

> On Fri, Jun 21, 2013 at 8:48 AM, Neal Peacock <kuliman...@gmail.com> wrote:
>> On 05/24/2013 07:44 PM, Matson Hall wrote:
>>
>> I just split the big partition to several smaller partitons. the have not
>> fixed the 512MB limitation of single partiton issue of allwinner-tools. It's
>> a bug of some binary program in allwinner-tools which I don't have the
>> source code. A good news is the new packing enviroment of a20 have fixed
>> such issue, and the bad news is it's a bit different from the old one.
>>
>> I'm working on the A31 tools and I'm still seeing a problem if my partition
>> is larger than 512mb. So I tried creating another partition in the
>> sys_partition.fex file with another ext4 file, from what I can tell dragon
>> is just ignoring it when packing. What else needs to be added so that next
>> partition gets created?
> For A20 and A31, the problem is solved. There should be no issue when
> packing, the problem happens when flashing with the old livesuite. Not
> sure what A31 tools you are using.

Alright trying from my Linux mint desktop (x64) the flashing program
always has an error, with any image, even those that work with my
Windows PhoenixSuit. Here is the error message

"Failed to flash firmware: Wait for Fes Device Timeout..."

Anyone seen this and know how to fix it? I creating a liveboot usb with
Fedora now so I can try a distro the flashing program likes.

Neal Peacock
PengPod

[npeacock]

On Friday, June 21, 2013 11:55:53 AM UTC-4, npeacock wrote:

On 06/21/2013 01:53 AM, Tom Cubie wrote:
> On Fri, Jun 21, 2013 at 8:48 AM, Neal Peacock <kuliman...@gmail.com> wrote:
>> On 05/24/2013 07:44 PM, Matson Hall wrote:
>>
>> I just split the big partition to several smaller partitons. the have not
>> fixed the 512MB limitation of single partiton issue of allwinner-tools. It's
>> a bug  of some binary program in allwinner-tools which I don't have the
>> source code. A good news is  the new packing enviroment of a20 have fixed
>> such issue, and the bad news is it's a bit different from the old one.
>>
>> I'm working on the A31 tools and I'm still seeing a problem if my partition
>> is larger than 512mb.  So I tried creating another partition in the
>> sys_partition.fex file with another ext4 file, from what I can tell dragon
>> is just ignoring it when packing.  What else needs to be added so that next
>> partition gets created?
> For A20 and A31, the problem is solved. There should be no issue when
> packing, the problem happens when flashing with the old livesuite. Not
> sure what A31 tools you are using.
Alright trying from my Linux mint desktop (x64) the flashing program
always has an error, with any image, even those that work with my
Windows PhoenixSuit.  Here is the error message

"Failed to flash firmware: Wait for Fes Device Timeout..."

Anyone seen this and know how to fix it?  I creating a liveboot usb with
Fedora now so I can try a distro the flashing program likes.

Well I guess I spoke too soon.  I finally figure out the Linux flash programs problem, I was using the USB 3.0 ports on the front.  I switched to a USB 2.0 on the back and now it will flash.

The small images still work but the larger images are still getting an error at the same place.  I can actually read the error message now, its

L296, Exception, returned value of Tools.entry_fes_thread is error.
./DeviceMessage/ASuitDeviceMessage.cpp 127 failed

 

>>
>>
>>
>>
>>
>> 2013/5/25 Dmitriy B. <rzk...@gmail.com>
>>>>
>>>> How did you get around that error with large livesuit images?  Will this
>>>> write without crashing livesuit?
>>>
>>> I'm also interested in this, I have 2GB max partiton right now. If you
>>> used sunxi-bsp, could you please show your changes/send patches.
>>> Also you used to push stuff to
>>> https://github.com/matson-hall/allwinner-pack-tools, could you please update
>>> it if you automated the image generation with this?
>>>
>>> Best Regards,
>>> Dmitriy Beykun
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "linux-sunxi" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an

>>> email to linux-sunxi+unsubscribe@googlegroups.com.

>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "linux-sunxi" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to linux-sunxi+unsubscribe@googlegroups.com.

>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>> --
>> Neal Peacock
>> PengPod
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "linux-sunxi" group.
>> To unsubscribe from this group and stop receiving emails from it, send an

>> email to linux-sunxi+unsubscribe@googlegroups.com.

[mtnm...@gmail.com]

W dniu piątek, 24 maja 2013 17:45:11 UTC+2 użytkownik Matson Hall napisał:  
> I've make a ubuntu desktop image for cubieboard nand. The download url is http://pan.baidu.com/share/link?shareid=494017&uk=3426192474. this version of ubuntu is using linux-sunxi stage-3.4 kernel.

Will be possible to make similar image with Debian armhf jessie/sid inside, and working ft5x_ts on any kernel? I tried to change kernel (I added /lib/modules/3.0.42-blahblah, and overwrote uImage), but tablet doesn't boot - I have only "MOM" logo, so I think that changing filesystem will also cause boot errors.

[Neal Peacock]

So I managed to figure out it.  All the values in the partition config file are half what I was thinking they meant.  I'm thinking this was probably explained in the comments I couldn't read.  I increased the size and everything seems to be find now. 

To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

-- 
Neal Peacock
PengPod

[dark...@gmail.com]

> >>> email to linux-sunxi...@googlegroups.com.

>
> >>> For more options, visit https://groups.google.com/groups/opt_out.
>
> >>>
>
> >>>
>
> >>
>
> >> --
>
> >> You received this message because you are subscribed to the Google Groups
>
> >> "linux-sunxi" group.
>
> >> To unsubscribe from this group and stop receiving emails from it, send an
>

> >> email to linux-sunxi...@googlegroups.com.

>
> >> For more options, visit https://groups.google.com/groups/opt_out.
>
> >>
>
> >>
>
> >>
>
> >>
>
> >> --
>
> >> Neal Peacock
>
> >> PengPod
>
> >>
>
> >> --
>
> >> You received this message because you are subscribed to the Google Groups
>
> >> "linux-sunxi" group.
>
> >> To unsubscribe from this group and stop receiving emails from it, send an
>

> >> email to linux-sunxi...@googlegroups.com.

>
> >> For more options, visit https://groups.google.com/groups/opt_out.
>
> >>
>
> >>
>
> >
>
> >
>
>
>
> --
>
> Neal Peacock
>
> PengPod

Thanks for this tip!

I was getting this error as well. I tried install from a USB 2.0 port on my laptop. No dice. But then I plugged it into my desktop USB 2.0 port and things went off without a hitch. Weird....

The laptop and desktop have almost identical OS setups: pretty fresh installs of Ubuntu 13.10.

[vinnichen...@gmail.com]

Cannot flash the board, I've tried a few things, but still end up getting the same error: