Differences in Revisions: Globalscale Dreamplug

fix code blocks
# Globalscale Dreamplug
 
## Technichal data
 
`CPU: Marvell Feroceon 1.2 GHz ARMv5te`
* CPU: Marvell Feroceon 1.2 GHz ARMv5te
`RAM: 512MB 16bit DDR2 @800`
* RAM: 512MB 16bit DDR2 @800
`Storage: 2 or 4GB internal µSD-Card + external SD-Card Slot`
* Storage: 2 or 4GB internal µSD-Card + external SD-Card Slot
`2x GigaBit LAN`
* 2x GigaBit LAN
`2x USB 2.0 HiSpeed`
* 2x USB 2.0 HiSpeed
`1x eSATA 2.0 (3Gbit)`
* 1x eSATA 2.0 (3Gbit)
`1x 802.11 b/g/n WLAN (not working with kernel 4.x - IPFire 2.21)`
* 1x 802.11 b/g/n WLAN (not working with kernel 4.x - IPFire 2.21)
`1x Bluetooth 2.1 EDR (not working with kernel 4.x - IPFire 2.21)`
* 1x Bluetooth 2.1 EDR (not working with kernel 4.x - IPFire 2.21)
`1x C-Media Audio Codec (Mic in/Line Out Analog+Digital Opt)`
* 1x C-Media Audio Codec (Mic in/Line Out Analog+Digital Opt)
 
http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
 
## Bluetooth & Wireless
 
With IPFire 2.21 bluetooth and wlan is not supported because the modul is not compatible with Kernel 4.x
 
## u-boot
The dreamplug uses u-boot as bootloader. IPFire 2.21 need a up-to-date u-boot that support flatted device tree (fdt) so you need to update it before using IPFire. It is best to flash the version that is shipped in the IPFire image in /usr/share/u-boot/dreamplug/. See [Debian - Flash Howto](https://wiki.debian.org/InstallingDebianOn/DreamPlug/U-bootUpgradeFromUSB)
 
The dreamplug uses u-boot as bootloader. IPFire 2.21 need a up-to-date u-boot that support flatted device tree (fdt)
so you need to update it before using IPFire. (best you flash the version that is shipped in the IPFire image in /usr/share/u-boot/dreamplug/)
[Debian - Flash Howto](https://wiki.debian.org/InstallingDebianOn/DreamPlug/U-bootUpgradeFromUSB)
 
Also you need some Environment entries to boot:
 
```
`boot_dev=usb`
boot_dev=usb
`boot_part=0:1`
boot_part=0:1
`bootcmd=${boot_dev} reset; fatload ${boot_dev} ${boot_part} 0x8000000 boot.scr; source 0x8000000;`
bootcmd=${boot_dev} reset; fatload ${boot_dev} ${boot_part} 0x8000000 boot.scr; source 0x8000000;
`console=console=ttyS0,115200 earlyprintk`
console=console=ttyS0,115200 earlyprintk
`fdt_addr_r=0x6300000`
fdt_addr_r=0x6300000
`fdtfile=kirkwood-dreamplug.dtb`
fdtfile=kirkwood-dreamplug.dtb
`kernel_addr_r=0x6400000`
kernel_addr_r=0x6400000
`ramdisk_addr_r=0x6900000`
ramdisk_addr_r=0x6900000
`root_dev=/dev/sda3`
root_dev=/dev/sda3
`soc=kirkwood`
soc=kirkwood
```
 
Depending on you config you have to change boot_part and root_dev if you not boot from the first detected device.
 
## Installation on the DreamPlug
 
##### Preparation
### Preparation
 
First, you need an SD or a USB drive. Plug it into your favorite computer. Download the image (see http://wiki.ipfire.org/en/hardware/arm/kirkwood at the bottom of the page) and then copy the image to your drive. IT WILL OVERWRITE ANYTHING ON THE DRIVE.
 
`xzcat ipfire-2.21.1gb-ext2.armv5tel-full-corexxx.img.gz > /dev/sd?`
 
where /dev/sd? is /dev/sda, sdb, whatever your SD or USB is.
It is possible to find out the correct designation with the following command.
 
It is possible to find out the correct designation with the following command:
`tail -f /var/log/messages`
 
Drop first the command and plug then the drive in, the screen should show then which sd[?] it is.
 
 
This puts a copy of the IPfire image on the SD/USB. However, the DreamPlug will not automatically boot from it. The following instructions tell you how to do that most easily.
 
Plug your JTag module into the DreamPlug. There are two wires, one marked "JTag", one marked "UART". Metal parts go up (there are plastic guides on the bottom side that fit into slots in the hole in the JTag and the DreamPlug). Also, plug the mini-usb into the JTag, but don't plug it into your computer yet.
 
You never know what port the JTag will come up as.
You never know what port the JTag will come up as:
 
`tail -f /var/log/messages`
 
(or syslog) will tell you. Do that and then plug the JTag module. You should see /dev/ttyUSBx, where x will be 0, 1, stuff like that. This is your port. The message will likely say something about "ftdi_sio", which is the Linux module that handles the JTag.