Knowledge Database

phyBOARD-Wega

phyBOARD-Wega

Setting boot mode DIP-switch

For booting from SD using PCM-953 baseboard card DIP-Switch S5 must be set to ON-ON-ON-ON-OFF-ON-OFF-OFF.

Booting from USB

Datasheet of the prozessor shows in chapter 26.1.8.6 "USB Boot Procedure", that the processor's boot sequence uses USB in order to establish an IP-connection to a tftp-server. So it's not intended for booting from an USB-Stick.

Furthermore Barebox is not able to boot from USB. Some related coding it contains will not run.

Linux

Creating a bootable SD card

Setting up SD Card Partitions for Bootloader and Linux RootFS

You can use the following script in order to format an SD-card from that an AM335x can boot:

#!/bin/bash
if [ ! "$1" = "/dev/sda" ] ; then
    unset LANG
    DRIVE=$1
        umount $DRIVE"1"
        umount $DRIVE"2"
    if [ -b "$DRIVE" ] ; then
        dd if=/dev/zero of=$DRIVE bs=1024 count=1024
        SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`
        echo DISK SIZE - $SIZE bytes
        CYLINDERS=`echo $SIZE/255/63/512 | bc`
        echo CYLINDERS - $CYLINDERS
        {
        echo ,9,0x0C,*
        echo ,,,-
        } | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE
        mkfs.vfat -F 32 -n "boot" ${DRIVE}1
        mke2fs -j -L "rootfs" ${DRIVE}2
    fi
fi

 

The following script copies all files onto the SD-card:

if [ ! "$1" = "/dev/sda" ] ; then
  DRIVE=$1
  SRC=$2

  sudo mount $DRIVE"1" /mnt
  sudo cp $SRC/MLO /mnt
  sudo cp $SRC/barebox.img /mnt
  sudo cp $SRC/uImage-pcm051 /mnt
  sudo umount $DRIVE"1"

  sudo mount $DRIVE"2" /mnt
  sudo tar zxf $SRC/root.tgz -C /mnt
  sudo umount $DRIVE"2"
  sync
fi

Choosing the right Linux-BSP version

The essential question for deciding which Linux BSP version is the right one for your Wega board are the version numbers of the printed circuit boards of Wega and AV adapter. You'll find them when you dismount the AV adapter from the Wega.

Wega and TTL-RGB adapter (PEB-AV-02)
1405.1 or 1405.2 (Wega) + 1415.1 (PEB-AV-02): BSP PD14.1.0
1405.0 (Wega) + 1415.0 (PEB-AV-02): BSP PD13.1.0_CR1

Wega and HDMI adapter (PEB-AV-01)
1405.0 or 1405.1 or 1405.2 (Wega) + 1406.0 or 1406.1 (PEB-AV-01): BSP PD13.0.0

For instructions of how to flash BSPs see Wega's Application Guide (download link L-792e.pdf aside), chapter 4.4 "Updating the software".

Status of HDMI driver

Status of HDMI driver

The BSP Linux PD13.0.0 (alpha) Release supports HDMI in experimental state, which means it's not production quality.
The limitations concern coding quality as well as test depth.
Supported Resolutions are only 720p and XGA.
No EDID recognition of monitors.


The first BSP release of production quality (PD13.1.0) will have HDMI deactivitaed due to these restrictions.
Implementation of good HDMI driver will take some more time, but will also be done.

 

 

Accessing GPIO inputs as interrupt from userspace

The Linux kernel offers an UIO-driver for this purpose. For usage see Linux-kernel-documentation within "DocBook/uio-howto.tmpl" or online this link:
www.kernel.org

Decreasing amount of available RAM

In order to change the amount of available RAM for example to 512 MB, you need to add "mem=512M" parameter within Barebox's environment.

For current BSP versions this means to add "mem=512M" within "/env/config-board" at the end of the line:

global.linux.bootargs.base="console=ttymxc3,115200 enable_wait_mode=off vt.global_cursor_default=0 consoleblank=0 mem=512M"

Out of 512MB RAM, 128MB will be allocated to GPU and 384MB for general uses. Depending upon your requirement you can change GPU memory size. In order to modify the GPU memory size you need to make modification in kernel
board config file.

Verwendung eines Nameserver anmelden

Damit auch bei fix eingestellten IP-Adressen ein Nameserver verwendet wird, sind die folgenden Einstellungen vorzunehmen:

In die /etc/resolv.conf gehört ein Eintrag der Art:
nameserver 192.168.1.19

In der /etc/nsswitch.conf muß der Eintrag "hosts: files" erweitert werden zu "hosts:files dns".

Ein gültiger Default-Gateway sollte eingestellt sein, erkennbar daran, daß die Anweisung "route" eine Zeile "default" mit ausgibt.

Wo finde ich die Linux-Sourcen und sind diese schon an die PHYTEC-Module angepaßt?

Auf unserem FTP-Server finden Sie unter ftp://ftp.phytec.de/pub/Products/ eine Auswahl unserer Module. Das darunter befindliche Verzeichnis "Linux/" beinhaltet die letzte(n) aktuelle(n) BSP-Version(en). Diese bestehen aus den fertig flashbaren Binary-Images sowie einem OSELAS-Tarball und der PTXdist-Toolchain.

Der OSELAS-Tarball enthält außer den letzten PHYTEC-Patches selber kaum Sourcen. Vielmehr ist es ein Regelwerk, mit dem PTXdist die Binary-Images erstellen kann. Dazu ist eine Verbindung zum Internet erforderlich, denn fast sämtliche Sourcen werden von dem Regelwerk aufgrund fest hinterlegter Links von dort geladen. Die Sourcen befinden sich also erst nach der Erstellung der Binaries auf Ihrer Festplatte und enthalten dann in der Tat auch sämtliche Anpassungen an Ihr PHYTEC-Modul.

Windows Embedded Compact 7

Fragen und Antworten zu ähnlichen Produkten

Booting from SD card

The essential question for deciding how it's possible to force boot from SD card instead of from NAND is the version number of the printed circuit board of the Wega. You'll find it when you dismount the AV adapter from the Wega.

 

Wega 1405.0

After having dismounted the AV adapter you need to connect X_LCD_D2 (pin 8 at X70) to a high-level (e.g. VCC3V3 – pin 13 at X71) during the power-up sequence. For orientation of the connectors please refer to ftp://ftp.phytec.de/pub/Products/phyBOARD-WEGA-AM335x/Layout/PL1405_0/1405-0-BS-ref.pdf

Wega 1405.1

After having dismounted the AV adapter you'll see a DIP switch which toggles boot sequence between NAND and SD card.

 

 

Using UART2 and UART3

In order to use UART2 and UART3, pinmuxing of AM335x's balls L18, K18, L16 and L17 must be changed within Linux kernel source "arch/arm/mach-omap2/board-phyboard-wega.c" as follows:

 

1.) Add the following structs:

/* Pin mux for uart2 */
static struct pinmux_config uart2_pin_mux [] = {
  {"mii1_rxclk.uart2_txd_mux0", OMAP_MUX_MODE1 | AM33XX_PULL_ENBL},
  {"mii1_txclk.uart2_rxd_mux0", OMAP_MUX_MODE1 | AM33XX_PIN_INPUT_PULLUP},
  {NULL, 0},
};

/* Pin mux for uart3 */
static struct pinmux_config uart3_pin_mux [] = {
  {"mii1_rxd2.uart3_txd_mux0", OMAP_MUX_MODE1 | AM33XX_PULL_ENBL},
  {"mii1_rxd3.uart3_rxd_mux0", OMAP_MUX_MODE1 | AM33XX_PIN_INPUT_PULLUP},
  {NULL, 0},
};

 

2.) Within init function "wega_board" add the appropriate calls:

  setup_pin_mux (uart2_pin_mux);
  setup_pin_mux (uart3_pin_mux);

 

3.) Comment out the lines that want to have these balls as GPIOs for user LEDs and user buttons within struct "static struct pinmux_config btn_pin_mux []" and function "peb_eval_01_init":

//     {"mii1_rxclk.gpio3_10", OMAP_MUX_MODE7 | AM33XX_PIN_INPUT_PULLUP},

//     setup_pin_mux(led_pin_mux);

 

4.) Because no GPIOs are left over now for user LEDs, the whole LED logic can be deactivated by commenting it out within function "peb_eval_01_init":

//     platform_device_register (&leds_gpio);

Boot sequence remains in an endless loop

Problem:

Shortly after beginning of booting Linux kernel the board unexpectedly resets and restarts booting. This will repeatedly be done in an endless loop.

 

Solution:

Most probably your power supply is too weak. Please use a stronger one, because at the beginning of the boot sequence the AM335x needs more power than later on during regular work.

Booting from USB

Datasheet of the prozessor shows in chapter 26.1.8.6 "USB Boot Procedure", that the processor's boot sequence uses USB in order to establish an IP-connection to a tftp-server. So it's not intended for booting from an USB-Stick.

Furthermore Barebox is not able to boot from USB. Some related coding it contains will not run.

LVDS display power supply

When you're using an LVDS display together with PEB-AV-02, it's power supply will completely be done over its flat flex cable (FFC). There's no necessity for separate backlight supply.