Jump to content

Install Nand on CubieBoard1 fail

glb29

By glb29
in Allwinner sunxi

 Share

Recommended Posts

glb29

glb29

Posted
Posted

Hi,

First of all: Thank you for all the great work that you're doing, Igor! I really appreciate it. And sorry for my english.

I try to install Armbian (debian jessie legacy kernel) on the NAND on cubieboard1, but I think that the installation doesn't go to the end.
Initially, a lubuntu was installed on NAND (http://docs.cubieboard.org/tutorials/a10-cubieboard_lubuntu_desktop_releases) and operated normally.

I booted with Sdcard "Armbian" (Armbian_4.5_Cubieboard_Debian_jessie_3.4.109) and I run ./nand-sata-install:

  • It will tell me, all data will be deleted on nand, and after a second or so it will inform me, should reload that script after   reboot

  • after reboot, I run ./nand-sata-install, and i have this message :

tar: A lone zero block at 964
[==============>                          ] 40%

and once at 100%, it happens nothing

 

I don't have the end of script as shown in this topic (http://forum.armbian.com/index.php/topic/228-debian-wheezy-34108-cubieboard2-nand-install/?hl=nand)

  • It will build the system while some minutes
  • After done, it informs to press a key, and after shutdown, remove the sd card
  • Do push a button, remove the sd card, power up cubieboard again":


If I reboot and run the script nand-sata-install, it will restart at the first opération : "all data will be deleted on nand...."

Do you know why ?
 

Link to comment
Share on other sites
Igor

Igor

Posted
Posted

It's possible that this is happening because of bad / missing sunxi tools. Check if you have a program called nand-part ?

 

Recently they were failing to compile.

 

We need those tools!

 

Try to compile by yourself and try again or wait for update.

Link to comment
Share on other sites
glb29

glb29

Posted
  • Author
Posted

Hi Igor,

Could you test the NAND installation on  your cubieboard1?
I  continue my tests to verify the proper functioning of my cubieboard and its NAND.

The instrallation Cubian of the NAND works well. But it is a Wheezy then I need a Jessie.

And it is a Armbian that I want to install !!

Link to comment
Share on other sites
glb29

glb29

Posted
  • Author
Posted

Hi Igor,

 

I can't try with the last version 4.7.

When i run "apt update", i have this error:

 

 

root@cubieboard:~# apt update

Get:1 http://security.debian.orgjessie/updates InRelease [2,578 B]                 

100% [1 InRelease gpgv 2,578 B] [Connecting to apt.armbian.com]Splitting up /var/lib/apt/lists/partial/security.debian.org_dists_jessie_updates_InRelease intoErr http://security.debian.orgjessie/updates InRelease       

 

Get:2 http://apt.armbian.comjessie InRelease [2,578 B]       

Err http://apt.armbian.comjessie InRelease /var/lib/apt/lists/partial/apt.armbian.com_dists_jessie_InRelease into data and signature failed

 

Fetched 2,578 B in 0s (9,858 B/s)

Reading package lists... Done

Building dependency tree      

Reading state information... Done

5 packages can be upgraded. Run 'apt list --upgradable' to see them.

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.debian.orgjessie/updates InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)

 

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://apt.armbian.comjessie InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)

 

W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease 

 

W: Failed to fetch http://apt.armbian.com/dists/jessie/InRelease 

 

W: Some index files failed to download. They have been ignored, or old ones used instead.

root@cubieboard:~#

 

I have the same error with 2 armbian image. Is it an armbian error?

 

Thanks.

Link to comment
Share on other sites
glb29

glb29

Posted
  • Author
Posted

Hi Igor,

 

I resolve the apt-update error: it was related to my router.

 

I could do the update (apt update && apt upgrade), and I retry the Nand Install.

I saw the new script  : a single step with just a reboot at the end.

 

Unfortunately, after the reboot, the CB1 does not start.

Link to comment
Share on other sites
masyan

masyan

Posted
Posted

Hi. I download last version of scrips from github. Run nand-sata-install.  Script executed without error, partitions created. But OS not boot from nand, after reboot Black screen (without sd). On boot partitions files exists (directory linux, *.ini files, etc). 
cubieboard 1 (ubuntu trusty).

Link to comment
Share on other sites
AvengerMoJo

AvengerMoJo

Posted
Posted

I can finish the write. But fail in boot.

 

 boot0 version : 1.5.0

dram size =1024
Succeed in opening nand flash.
Succeed in reading Boot1 file head.
The size of Boot1 is 0x00056000.
The file stored in 0X00000000 of block 2 is perfect.
Check is correct.
Ready to disable icache.
Succeed in loading Boot1.
Jump to Boot1.
[       0.178] boot1 version : 1.5.0
[       0.178] pmu type = 3
[       0.179] bat vol = 0
[       0.211] axi:ahb:apb=3:2:2
[       0.211] set dcdc2=1400, clock=1008 successed
[       0.213] key
[       0.226] no key found
[       0.226] flash init start
[       0.271] flash init finish
[       0.274] fs init fail
[       0.274] fs init fail, jump to fel
Link to comment
Share on other sites
AvengerMoJo

AvengerMoJo

Posted
Posted

 After I install one more time ... It fix the above issue but then 


 HELLO! BOOT0 is starting!boot0 version : 1.5.0
dram size =1024
Succeed in opening nand flash.
Succeed in reading Boot1 file head.
The size of Boot1 is 0x00056000.
The file stored in 0X00000000 of block 2 is perfect.
Check is correct.
Ready to disable icache.
Succeed in loading Boot1.
Jump to Boot1.
[       0.178] boot1 version : 1.5.0
[       0.178] pmu type = 3
[       0.179] bat vol = 0
[       0.210] axi:ahb:apb=3:2:2
[       0.210] set dcdc2=1400, clock=1008 successed
[       0.212] key
[       0.224] no key found
[       0.224] flash init start
[       0.270] flash init finish
[       0.273] fs init ok
[       0.275] fattype FAT16
[       0.275] fs mount ok
[       0.280] script finish
[       0.281] power finish
[       0.281] storage_type=0
[       0.291] BootMain start
[       0.291] 0
[       0.323] key value = 0
[       0.323] recovery key high 6, low 4
[       0.324] unable to find fastboot_key key_max value
[       0.331] test for multi os boot with display
[       0.333] logo name is invalid or dont need show logo
[       0.339] load kernel start
[       0.363] load kernel successed
[       0.363] start address = 0x4a000000
[       0.365] jump to




U-Boot 2013.10-rc2-08400-g0490093 (Oct 11 2013 - 00:40:21) Allwinner Technology


CPU:   Allwinner A10 (SUN4I)
Board: Cubieboard
I2C:   ready
DRAM:  1 GiB
NAND:  0 MiB
MMC:   SUNXI SD/MMC: 0
Card did not respond to voltage select!
MMC init failed
Using default environment


In:    serial
Out:   serial
Err:   serial
Net:   emac
Hit any key to stop autoboot:  0 
** Unrecognized filesystem type **
** File not found boot/uEnv.txt **
** File not found uEnv.txt **
** File not found /boot/script.bin **
** Unrecognized filesystem type **
** File not found /script.bin **

somehow the uboot is not what I'm expecting ... 

 

Since it get to uboot anyway, the installation is ok so I can still boot with the following 

 

setenv bootargs root=/dev/nand2 rootwait
fatload nand 0:0 0x43000000 script.bin
fatload nand 0:0 0x48000000 uImage
bootm 0x48000000

 

 

Any idea why I loaded with a old uboot and how should I go about to replace it

Link to comment
Share on other sites
Igor

Igor

Posted
Posted

Yes, it's possible to use this but it's not the proper way - upgrading will not work properly ...

 

Copy uEnv.txt, script.bin and uImage, located in /dev/nand1 to /boot , located in /dev/nand2 and reboot.

 

It will work.

 

I am searching for sources to fix this properly. I only found an working U-boot source for A20.

 

Current Uboot doesn't have support for NAND, that's why we need to use this prehistoric ;) Eventually this will change.

1
Link to comment
Share on other sites
AvengerMoJo

AvengerMoJo

Posted
Posted

Yes, it's possible to use this but it's not the proper way - upgrading will not work properly ...

 

Copy uEnv.txt, script.bin and uImage, located in /dev/nand1 to /boot , located in /dev/nand2 and reboot.

 

It will work.

 

I am searching for sources to fix this properly. I only found an working U-boot source for A20.

 

Current Uboot doesn't have support for NAND, that's why we need to use this prehistoric ;) Eventually this will change.

You are right :) making the files available in nand2 fix it. Thanks alot with your work. :) let me know if something I can help haha :) Thank for your effort to supporting this. 

Link to comment
Share on other sites
AvengerMoJo

AvengerMoJo

Posted
Posted

Help me find the correct source to fix this ;)

 

There are many u-boot sources around and will take some time to find the proper / working one.

 

Keep you updated, seem like the upstream still not accepting the NAND boot options. It is going to take me some time to test them out, one by one :) Working on it. Will post you. 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept