Differences

This shows you the differences between two versions of the page.

--- tutorials:ct1:installation:cb3_lubuntu-12.10-desktop_nand_installation_v1.00 [2013/10/31 12:35]
benn created
+++ tutorials:ct1:installation:cb3_lubuntu-12.10-desktop_nand_installation_v1.00 [2014/05/04 11:22] (current)
allen [Download Images]
@@ Line 15: / Line 15: @@
 The Cubie team have ported cubietruck to lubuntu-12.10-desktop, here is a guide for installing lubuntu-12.10-desktop to cubietruck nandflash.
+<note tip>The latest version is v1.02 ([[http://dl.cubieboard.org/software/a20-cubietruck/lubuntu/ct-lubuntu-nand-v1.02/|download]]) </note>
@@ Line 23: / Line 25: @@
   gzip -d lubuntu-desktop-nand.img.gz
+<note tip>This firmware default HDMI output, for default VGA output please use this [[http://dl.cubieboard.org/software/a20-cubietruck/lubuntu/ct-lubuntu-nand-v1.00/VGA/|firmware]] \\ login/password:	linaro/linaro </note>
 ==== PhoenixSuit ====
 To flash the image to cubietruck board, you need to install phoenixsuit on your labtop. Please refer to the [[http://docs.cubieboard.org/tutorials/common/livesuit_installation_guide|Installation Guide]]
@@ Line 56: / Line 59: @@
 {{:tutorials:ct1:installation:livesuit-enter-fel-mode.png?700|LiveSuit GUI}}
-  - Press FEL key, and holding it
+  - Press FEL key and while holding it
-  - Plug in mini usb cable, and wait the following prombt
+  - Plug in mini usb cable, and wait the following prompt
   - Release FEL key
 {{:tutorials:ct1:installation:lubuntu-livesuit-3.png?700|LiveSuit GUI}}
+<note tip>Some USB Ports do not provide enough current for the board. If this happen, please plug in power adaptor before click 'Yes'</note>
 ==== Flash to Board ====
-When seeing the prombt, you have enter the FEL mode. Select Yes to continue
+When seeing the prompt, you have enter FEL mode. Select Yes to continue
 {{:tutorials:ct1:installation:lubuntu-livesuit-4.png?700|LiveSuit GUI}}
@@ Line 72: / Line 77: @@
 Congratulations! You have finished the installation process. Enjoy your Cubie and Lubuntu Desktop!
-When you first start up the system, It will take about 2 minutes to initialize the system. Also we suggest you have the ethernet cable connected when booting, to avoid waiting DHCP timeout.
+When you first start up the system, It will take about 2 minutes to initialize the system. Also we suggest you have the ethernet cable connected when booting, to avoid waiting for DHCP timeout.
@@ Line 143: / Line 148: @@
   brw-rw---- 1 root disk 93, 2 Oct 15 08:46 /dev/nandb
   brw-rw---- 1 root disk 93, 3 Oct 15 08:46 /dev/nandc
-  brw-rw---- 1 root disk 93, 4 Oct 15 08:46 /dev/nandd
-  brw-rw---- 1 root disk 93, 5 Oct 15 08:46 /dev/nande
   * /dev/nanda
-Contains the bootlogo, script.bin, and so on
-  root@cubietruck:~# ls /mnt/nanda/
+Contains the bootlogo, script.bin, uEnv.txt, uImage and so on
-  boot.axf  drv_de.drv    font24.sft  linux      os_show   script.bin
-  boot.ini  drv_hdmi.drv  font32.sft  magic.bin  prvt.axf  sprite.axf
   * /dev/nandb
-Contains the u-boot boot parameters. The origin is showed below,
-  bootdelay=1
+rootfs
-  #default bootcmd, will change at runtime according to key press
-  bootcmd=run setargs_nand boot_normal#default nand boot
-  #kernel command arguments
-  console=ttyS0,115200
-  nand_root=/dev/system
-  mmc_root=/dev/mmcblk0p7
-  init=/init
-  loglevel=5
-  #set kernel cmdline if boot.img or recovery.img has no cmdline we will use this
-  setargs_nand=setenv bootargs console=${console} init=${init} loglevel=${loglevel}
-  setargs_mmc=setenv bootargs console=${console} init=${init} loglevel=${loglevel}
-  #nand command syntax: sunxi_flash read address partition_name read_bytes
-  #0x40007800 = 0x40008000(kernel entry) - 0x800(boot.img header 2k)
-  boot_normal=boota 40007800
-  #boot_normal=sunxi_flash read 40007800 boot;boota 40007800
-  boot_recovery=sunxi_flash read 40007800 recovery;boota 40007800
-  boot_fastboot=fastboot
-  #recovery key
-  recovery_key_value_max=0x13
-  recovery_key_value_min=0x10
-  #fastboot key
-  fastboot_key_value_max=0x8
-  fastboot_key_value_min=0x2
-If you want to change your own kernel parameter, you can:
+====Wifi====
-  - Save above text to a file, e.g. env.cfg
+  * Loading Module
-  - Use u_boot_env_gen tool to convert the file to a image
-  - dd the image to /dev/nandb
-If you are using Ubuntu 12.04 X86_64, there is a simple script help you do that
+  #modprobe bcmdhd
-  $wget http://dl.cubieboard.org/software/a20-common/mk_env_fex.tar
-  $tar -xf mk_env_fex.tar
+Hint: add "bcmdhd" at the end of file /etc/modules to activate WiFi during boot.
-  $cd mk_env_fex
-  $vim env.cfg  -- and change the content as you want
-  $./mk_env_fex.sh
+  * Using Wifi
+e.g.
+  #iwlist scan
+  #iwconfig wlan0 essid "ssid" key xxxx
+  #iwconfig wlan0
+  #ifconfig wlan0 up
+  #dhclient wlan0
+Hint: iwconfig key does not support password phrase. One has to generate xxxx.
+Hint: it is easier to use wpa_supplicant for wifi configuration with WPA2 and password phrase.

CubieBoard Docs

User Tools

Site Tools

Differences

Page Tools