Open main menu

CDOT Wiki β

Changes

Winter 2010 Posters/SheevaPlug Configuration

304 bytes added, 23:39, 16 April 2010
no edit summary
= The Goal =
The goal of this project was to successfully run Fedora 12 on the SheevaPlug. The operating system that came loaded on the device is Debian. The purpose behind installing Fedora 12 on this device is to test the operating system's performance on the ARM architecture. = The Connection = Since the SheevaPlug doesn't have a display adapter, it comes integrated with a built in "serial console to mini USB" connection. The connection can Further tests will be made performed in the future to either a Windows or Linux machine. For determine if the purpose of this project, I connected it to SheevaPlug is a Windows machine. Once connecting it with good choice for the "mini USB Fedora Arm Secondary Architecture Project to regular USB" cable, I installed the Windows drivers that came with the CD and using PuTTy I used use a serial connection to COM 1 using 115200 stack of these devices as the connection speed. This is important to know because if you can't live without a GUI, I suggest avoiding this devicebuilders. :)
= Challenges =
2. The plug does not have a BIOS, instead it has a bootloader (U-boot) however this needed to be updated.
3. No Video video card (serial console to USB) instead.
4. Some network configuration had to be made when plugged into my network. This network configuration was required in order to download "wget".
1. In order to run Fedora 12 on the SheevaPlug I had to install the operating system on an SD card (although it can also be installed on a USB drive).
2. The bootloader was easily upgradable by accessing the newer version via TFTP or USB from a web source (http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html) 3. Since there is no BIOS the SheevaPlug doesn't have a display adapter, it comes integrated with a built in "serial console to select which device gets bootedmini USB" connection. The connection can be made to either a Windows or Linux machine. For the purpose of this project, the SheevaPlug has I connected it to a bootloader called U-bootWindows machine.
34. The bootloader default gateway had was easily upgradable by accessing configured and the newer version via TFTP or USB from a web source (http://www.cyriusname server was added to the resolv.com/debian/kirkwood/sheevaplug/uboot-upgradeconf file.html)
= Results =
1. Fedora 12 was successfully installed on an SD card and booted from the SheevaPlug. The boot up time was quick as well, with minimal extra configuration required once booted it up (i.e. networking).
2. Following the HOW-TO page for upgrading U-boot (located in the Links section) was pretty simple, however making sure the uboot.bin file copies over to the USB drive is important for the device to actually read it and copy it over. To configure U-boot, about 7 configuration commands were required, as soon as this was done and the device rebooted, the device selected the SD card and booted Fedora 12. 3. Once I connected the SheevaPlug with the "mini USB to regular USB" cable, I installed the Windows drivers that came with the CD and using PuTTy I used a serial connection to COM 1 using 115200 as the connection speed in order to connect to the device.
34. To configure U Configuring the name server enabled the connection to the Internet and I was able to use apt-boot, about 7 configuration commands were get to install "wget". Wget was required, as soon as this was done to download the Distro and the device rebooted, the device selected Kernel for when I had to install Fedora 12 on the SD card and booted Fedora 12.
= Acknowledgements =