Mustang

Differences between revisions 64 and 65
Revision 64 as of 2013-10-15 13:25:50
Size: 8006
Editor: c-24-147-74-79
Comment: 13.10 ARM updates
Revision 65 as of 2013-10-15 13:44:44
Size: 8010
Editor: james-page
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
= Installing Ubuntu Precise (12.04.2), Quantal (12.10), Raring (13.04) Saucy (13.10) using netboot for Calxeda ECX-1000 (Highbank) and ECX-2000 (Midway) = = Installing Ubuntu Precise (12.04.2), Quantal (12.10), Raring (13.04) and Saucy (13.10) using netboot for Calxeda ECX-1000 (Highbank) and ECX-2000 (Midway) =

Installing Ubuntu Precise (12.04.2), Quantal (12.10), Raring (13.04) and Saucy (13.10) using netboot for Calxeda ECX-1000 (Highbank) and ECX-2000 (Midway)

Before You Begin

You will need the following:

  1. A management device for console access
  2. DHCP available which will provide Internet access (to access the Ubuntu package archive)
  3. A TFTP Server accessible from the system

Downloading the Installer

Download the Calxeda Highbank kernel and installer initrd and place them on an available TFTP Server.

For Precise, use this kernel and initrd.

For Quantal, use this kernel and initrd.

For Raring, use this kernel and initrd.

For Saucy, use this kernel and initrd.

Booting the Installer

Power on the chassis and access the console via IPMI (e.g. "ipmitool -H 10.0.0.101 -U admin -P admin -I lanplus sol activate").

Power on the system processor (e.g. "ipmitool -U admin -P admin -H 10.0.0.101 chassis power on").

Interrupt U-Boot by pressing Enter when prompted to stop autoboot.

Type the following at the U-Boot prompt, replacing the IP address with the IP address of your TFTP Server:

dhcp
tftpboot ${kernel_addr_r} 10.0.0.10:/vmlinuz
tftpboot ${ramdisk_addr_r} 10.0.0.10:/initrd.gz
setenv bootargs "console=ttyAMA0"
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr}

Note: insert "setenv initrd_high 0xffffffff" after "dhcp" for early u-boot releases.

This will boot into the installer, follow the default partitioning scheme suggested.

Booting into the Installed System

Your system should now boot into the installed system.

Installing Precise (12.04.2) using netboot onto a Marvell ArmadaXP Development Board

Before You Begin

You will need the following:

  1. A management device for serial access to the board.
  2. DHCP available for the board which will provide Internet access (to access the Ubuntu package archive).
  3. A TFTP Server accessible from the board and optionally a PXE Server setup for PXE boot emulation.

Downloading the Installer

Download the Marvell ArmadaXP uImage and uInitrd and place them on an available TFTP Server.

Booting the Installer

Access the Marvell ArmadaXP serial console, for example with "screen /dev/ttyUSB0 115200" on a management machine with a USB serial adaptor attached to it.

Power on the board.

Interrupt U-Boot by pressing Enter when prompted.

TFTP Boot

Type the following at the U-Boot prompt, replacing the IP address with the IP address of your TFTP Server:

dhcp
tftpboot 0x2000000 10.0.0.10:/uImage
tftpboot 0x1100000 10.0.0.10:/uInitrd
setenv bootargs "console=ttyS0,115200 earlyprintk=ttyS0 pm_disable"
bootm 0x2000000 0x1100000

This will boot into the installer. Follow the default partitioning scheme suggested.

PXE Boot

Type the following at the U-Boot prompt to boot using PXE boot emulation:

dhcp
pxe get
pxe boot

This will boot into the installer. Follow the default partitioning scheme suggested.

Note: you may need to "set pxefile_addr_r 0x7000000", "set kernel_addr_r 0x2000000", and "set ramdisk_addr_r 0x1100000" before this will work (don't forget to "save" those values).

Here's a sample PXE configuration file: pxelinux.cfg/01-00-50-43-aa-bb-cc

default armadaxp-precise
prompt 0
timeout 1

label armadaxp-precise
   kernel /uImage
   initrd /uInitrd
   append console=ttyS0,115200 earlyprintk=ttyS0 pm_disable

Booting into the Installed System

When the installer finishes and reboots, interrupt U-Boot again and type the following. If you used a different partitioning scheme, adjust the ext2load and root parameters accordingly.

setenv bootcmd "ide reset; ext2load ide 0:1 0x2000000 uImage; ext2load ide 0:1 0x1100000 uInitrd; setenv bootargs console=ttyS0,115200 earlyprintk=ttyS0 root=/dev/sda2 ro pm_disable; bootm 0x2000000 0x1100000"
save
reset

Your system should now boot into the installed system, with U-Boot configured and verified to continue doing so on future reboots.

Installing pre-installed OMAP4 Precise (12.04.2) Server Images

Follow these steps;

Download

Download the compressed image from the cdimage server.

Warning /!\ Check the md5sum to verify the image Warning /!\

Copy the image to SD card

You should write the raw image to a blank SD card. Make sure you're using at least a 2 Gig SD card so that you have enough room for the image.

Steps:

  1. Insert the SD card in your host computer's SD card reader.
  2. Make sure the SD card is not mounted (just umount it if needed).
  3. Identify the correct device name (like /dev/mmcblk0 or /dev/sdb).

  4. Run the following command to write it:

gunzip -c ubuntu-12.04-preinstalled-server-armhf+<omap or omap4>.img.gz | sudo dd bs=1M of=/dev/<device name>
sync

or

sudo sh -c 'zcat ubuntu-12.04-preinstalled-server-armhf+<omap or omap4>.img.gz > /dev/<device name>'
sync

(note: replace <omap image> with omap4 for panda/blaze/other omap4 based system and the raw block device for <device name> - not a partition. i.e. /dev/mmcblk0 )

Booting the image

  1. Attach a serial cable to the serial port on the board. (note: The board is already wired for a straight serial cable - no null modem needed)

  2. Open a terminal on your host system and launch a serial console monitor with the port set for 115200,n,8,1
    • Screen: screen /dev/ttyUSB0 115200

      • * you can end the screen session by pressing Ctrl-A and then K

    • Minicom: TERM=vt100 minicom

      • * the TERM=vt100 setting is needed for proper output formatting

        * you can end the minicom session by pressing Ctrl-A and then X or Q

  3. Insert the SD card in the system and switch on the board.

The system should start booting with output shown on your serial terminal. After the board resizes the image to fill the SD card, it will reboot and start oem-config to prompt for localization and user info.

ARM/Server/Install/Mustang (last edited 2016-02-17 16:57:00 by rkota)