From Fedora Project Wiki
(Remove outdated f19 build pointer)
Line 146: Line 146:
  
 
The X-C1 will reboot. Without any defined boot options, it will attempt to PXE install. You will need a PXE server as described below.
 
The X-C1 will reboot. Without any defined boot options, it will attempt to PXE install. You will need a PXE server as described below.
 
= Download the Mustang Build =
 
{{admon/note|Note: These steps are obsolete.}}
 
The first step is to download the Mustang build. This can be found at the following location:
 
 
* [ftp://ftp.ges.redhat.com/private/jcm/apm/f19_remix/apm_f19_v5/apm_f19_v5.img.xz ftp://ftp.ges.redhat.com/private/jcm/apm/f19_remix/apm_f19_v5/apm_f19_v5.img.xz ]
 
 
= Extract the Mustang Build =
 
 
Once you have downloaded the Mustang build, you will need to extract the archive file. Use the following command from a Linux system:
 
 
$ tar xvfJ apm_f19_v5.tar.xz
 
 
This will extract the following files:
 
 
apm_f19_v5.img.xz
 
config_jcm15
 
mustang_linux_src_1.10.09-beta_rc.tar.xz
 
 
The first file is a compressed disk image that will be written to the hard disk installed within the Mustang board case. The other two files contain the Linux kernel configuration and source (should you - optionally - wish to rebuild the kernel that ships within this image).
 
 
Extract the disk image:
 
 
$ xz -dk apm_f19_v5.img.xz
 
 
This will extract the following files:
 
 
apm_f19_v5.img
 
 
= Copy the disk image to the Mustang board =
 
 
{{admon/warning|Warning: Be careful to choose the correct device name below since using the wrong device name could overwrite data on your Linux system instead of the removable disk drive.}}
 
 
The Mustang board ships in a case containing a 500GB hard disk. Carefully remove this disk drive from the case. Then install it into either a removable USB enclosure, or into a spare disk bay within your Linux system. Linux should detect this drive and assign a name, such as "/dev/sdc". You can determine the name using the "dmesg" or (preferably) "lsblk" commands.
 
 
Copy the disk image onto the hard disk:
 
 
$ dd if=apm_f19_v5.img of=/dev/sdX bs=1M
 
 
Replace "/dev/sdX" with the name of the device, for example "/dev/sdc".
 
 
Once this operation has completed, ensure that the drive is ejected safely from your Linux system:
 
 
$ sync
 
$ eject /dev/sdX
 
 
Replace "/dev/sdX" with the name of the device, for example "/dev/sdX".
 
 
= Configure the Mustang board to boot Fedora =
 
 
Reinstall the hard disk drive into the Mustang case. Next, power on the system and interrupt the boot sequence when the countdown begins. Type the following commands (do not type the "Mustang#" prompt the precedes each command as it is typed into U-Boot):
 
 
Mustang# setenv rh_load_kern_scsi 'ext4load scsi 0:1 ${kern_addr_r} /uImage'
 
Mustang# setenv rh_load_fdt_scsi 'ext4load scsi 0:1 ${fdt_addr_r} /mustang.dtb'
 
Mustang# setenv rh_local_load 'run rh_load_kern_scsi rh_load_fdt_scsi'
 
Mustang# setenv rh_local_args 'setenv bootargs root=/dev/sda2 rw panic=1 console=ttyS0,115200 earlyprintk=uart8250-32bit,0x1c020000 debug maxcpus=${num_cores}'
 
Mustang# setenv rh_local 'scsi init; run rh_local_load; run rh_local_args; bootm ${kern_addr_r} - ${fdt_addr_r}'
 
Mustang# setenv bootcmd 'run rh_local'
 
 
Save these settings into the Mustang's NOR flash memory with the following command:
 
 
Mustang# saveenv
 
 
The output should look similar to the image below:
 
 
[[File:Mustang_UBoot_Config.png]]
 
 
= Booting Fedora =
 
 
Once the board has been configured, you can type "reset" or power-cycle the board, and it should automatically boot into the Fedora engineering build. The default password for the "root" user is "fedora".
 
 
= Resizing the disk =
 
 
{{admon/note|Note: The Mustang Fedora build has been optimized for installation across a wide variety of disk sizes such that the amount of free space will be very limited initially. After booting, you may wish to resize the disk to utilize all of the free 500GB of disk space.}}
 
 
To do this, login to the Mustang, and type:
 
 
$ fdisk /dev/sda
 
 
Then delete the second partition (the root partition):
 
 
d
 
2
 
 
Next recreate the second partition, accepting all of the defaults:
 
 
n
 
p
 
2
 
1050624
 
PRESS ENTER
 
 
This will cause all of the available disk space to be used, as opposed to the very limited space in the default image. Exit from fdisk:
 
 
w
 
 
Then reboot the Mustang system. After rebooting, instruct the Mustang to use this new space:
 
 
$ resize2fs /dev/sda2
 
 
This will instruct the ext4 filesystem to resize itself to fill all of the remaining (e.g. 500GB in the example) free disk space.
 

Revision as of 19:51, 19 December 2014


Note.png
Note: Page needs cleanup and updating.


Applied Micro "Mustang" (X-C1) QuickStart Guide

Note.png
Note: An official release of Fedora is in preparation. That build has transitioned to an EFI-based boot and will shortly support ACPI for device enumeration. Consequently, the use of U-Boot and DeviceTree in this image should be considered transitory, deprecated, and due for replacement with the standardized ARM server boot architecture in the next release.

This page contains some Quickstart instructions for getting up and running with an early engineering build of Fedora 19 on the Applied Micro "Mustang" development board. This Mustang build is based upon the Fedora 19 AArch64 bootstrap software builds, with the addition of a kernel and DeviceTree from the interim Applied Micro 1.10.09 engineering software release, packaged together into a single downloadable image for easy installation onto a hard disk or SSD. Applied Micro are currently working on upstreaming support into the mainline Linux kernel. In due course this image will be deprecated in favor of a standard Fedora build.

Pre-requisites for downloading and installing the Mustang Build

Prior to downloading and installing the Mustang build, you will require access to the following equipment:

  • An existing Linux system, for example a laptop or desktop system
  • A USB hard disk enclosure, or a spare disk bay in a Linux system
  • A USB serial "null modem" cable (or USB serial adapter with "null modem" cable), or a serial port and a "null modem" cable
Note.png
Note: In the examples below, commands are often prefixed with a "$". This refers to the Linux shell prompt and should not be typed directly. Similarly the "Mustang#" prompt within U-Boot should not be typed but instead represents the output from the Mustang board prompt as each command is entered.

Hook up the Mustang board

Prior to installing Fedora, verify that the Mustang board is correctly hooked up and ready for use. To do this, perform the following:

  • Attach a USB serial cable to your Linux system (or use a serial port), along with a "null modem" cable.
  • Attach the other end of the serial cable to the DB9 connector on the rear of the Mustang system.
  • Attach an Ethernet cable into the first Ethernet port on the Mustang system, which is located furthest away from the DB9 connector, atop the two USB connectors. This is the port that Linux will recognize as "eth0" when booted.
  • Attach the power cable to the Mustang board.

Install the "minicom" package onto your Linux system:

$ sudo yum install minicom

Run the "minicom" command:

$ minicom -D /dev/ttyUSB0

Replace "/dev/ttyUSB0" with the name of the serial interface, which in the case of a single serial port is "ttyUSB0" or "ttyS0".

Configure minicom using the "Ctrl-A-O" key sequence. Then select "Modem and dialing". Select "A" and remove the "Init string". Do the same for the "Reset string". The result should look similar to the image below:

Mustang Modem And Dialing.png

Press escape to return to the previous menu. Next, select "Serial port setup" and ensure that option "E" (Bps/Par/Bits) is set to "115200 8N1", option "F" (Hardware Flow Control) is set to "No", and option "G" (Software Flow Control) is set to "No". The result should look similar to the image below:

Mustang Serial Port setup.png

Press escape to return to the previous menu, then select "Save setup as dfl" to make the configuration changes to minicom persistent. Press escape again to exit from the configuration menus.

Power on the Mustang board and watch for output from the serial interface. The output should look similar to the image below:

Mustang Minicom Output.png

Once you have confirmed that the Mustang board is hooked up correctly, power it off and continue with the following steps.

Upgrade to UEFI

For Mustang systems that are shipped with u-boot, Red Hat is providing a UEFI image and tools to upgrade the firmware to UEFI.

  • Host Linux system with the ability to write to an SDCard
  • SDCard with a size between 1GB and 8 GB.

Preparation

You will need an SDCard with the fat16 filesystem and the contents of the mustang/ and uefi/ directories on it. Follow these steps.

Insert the SDCard in the host computer

Use gparted (sudo if necessary)

  1. Select /dev/mmcblock0
  2. Create a new MSDOS partition table
  3. Format a new partition as fat16, taking up 2048 MB
  4. Commit the changes.

Mount /dev/mmcblock0

Copy the mustang/ and uefi/ directories from this package onto /dev/mmcblock0p1

Unmount /dev/mmcblock0 and remove the SDCard from the host computer.

Chain Loading UEFI from U-boot

The u-boot firmware provided by APM cannot update itself, but the UEFI firmware provided by Red Hat can update firmware. The first step to permanently replacing u-boot with UEFI is to convince u-boot to chain load the UEFI firmware.

Reboot the X-C1 server.

While u-boot is booting, it will print the message "Hit any key to stop autoboot". Hit any key within 5 seconds. You should see a prompt.

Put the SDCard in the X-C1 server.

Type the following command

 Mustang# printenv 

and record the system's MAC address. You will need to program it into UEFI later.

Type the following series of commands:

 Mustang# setenv rh_sd_tiano_sec_ubt fatload mmc 0:1 0x1d000000 /mustang/mustang_tianocore_sec_ubt.fd
 Mustang# setenv rh_sd_tiano_ubt fatload mmc 0:1 0x4002000000 /mustang/mustang_tianocore_ubt.fd
 Mustang# setenv rh_run_tiano_ubt go 0x1d000000
 Mustang# setenv bootcmd run rh_sd_tiano_ubt rh_sd_tiano_sec_ubt rh_run_tiano_ubt
 Mustang# saveenv

This will override the autoboot script to load the UEFI image from the SDCard and chain boot it.

Reboot the X-C1 server.

 Mustang# reset

u-boot will start the boot again, and after a few seconds, begin booting UEFI with messages like this:

9502720 bytes read in 823 ms (11 MiB/s)
    1. Starting application at 0x1D000000 ...
Boot firmware (version 1.1-rh-0.12 built at 08:20:41 on Jul 23 2014)
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3021001 I0

Eventually, the messages like this will be printed:

TianoCore 1.1-rh-0.12-beta2 UEFI 2.4.0 Jul 23 2014 08:20:16
CPU: APM ARM 64-bit Potenza 1600MHz PCP 1600MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Board: X-Gene Mustang Board
The default boot selection will start in 5 seconds

Hit any key to break into the UEFI boot sequence. A menu will be printed, and select "b" for the UEFI command shell.

Type fs1: and hit return to switch to the SDCard.

Type 'cd uefi' to enter the uefi folder.

Run the upgrade tool with UpgradeFirmware.efi upgrade.cmd. It will take a few minutes for the upgrade to complete. If you power off your machine at this point, you're intensely screwed, so don't do that.

At this point, the X-C1 will boot directly into UEFI in the future.

Reboot the machine with reset. You should remove the SDCard.

You will not see the u-boot messages, but instead the UEFI messages.

When this message appears,

The default boot selection will start in 5 seconds

hit a key to break into the boot sequence and again select option b to get the shell.

Set the MAC address by typing 'set RGMII_MAC0 aa:bb:cc:dd:ee:ff', replacing aa:bb:cc:dd:ee:ff with the MAC address you wrote down earlier.

Type reset to reboot the machine again.

The X-C1 will reboot. Without any defined boot options, it will attempt to PXE install. You will need a PXE server as described below.