phyCORE-i.MX 6 / phyBOARD-Mira Downloads

Hardware Manual

Yocto BSP Manual

Android BSP Manual

Software

Yocto-Linux

Android

WEC2013

Image Processing

Components Placement Diagrams

Dimensioned Drawing

Module Connector

PHYTEC Order Number: VM317
Samtec Order Number: REF-183457-03

FAQ

FAQ

phyCORE-i.MX 6

Linux

Creating a bootable SD card

Setting up SD Card Partitions for Bootloader and Linux RootFS

1. A new card must be setup with 2 partitions and 8 MB of free space at the beginning of the card. Use the following procedure with fdisk under Linux:

  • Create a new fat partition with partition id C. When creating the new partition you must leave 8 MB of free space at the beginning of the card. When you go through the process of creating a new partition, fdisk lets you specify where the first sector starts. During this process fdisk will tell you where the first sector on the disk begins. If the first sector begins at 1000 for example, and each sector is 512 bytes in size, then 8 MB / 512 bytes = 16384 sectors ==> your first sector should begin at 17384 to leave 8 MB of free space. The size of this fat partition only needs to be big enough to hold the zImage which is only a few megabytes. To be safe, make this partition 64 MB in size.
  • Create a new Linux partition with partition id 83. Make sure you start this partition after the last sector of partition 1! By default fdisk will try to use the first partition available on the disk, which in this example is 1000. However, this is our reserved space! You can use the remaining portion of the card for this partition. Write the new partitions to the SD card and exit fdisk.

 

2. Create filesystems on the partitions (you may need to remove and reinsert the card for Linux to recognize the new partitions created in the previous step and you need to replaxe sdx by the proper devices):

mkfs.vfat /dev/sdx1

mkfs.ext3 /dev/sdx2

 

3. Mount the partitions so that you can copy files to them:

mount -t auto /dev/sdx1 /mnt/sdx1

mount -t auto /dev/sdx2 /mnt/sdx2

 

4. Copy the images from the BSP to the card:

cp linuximage /mnt/sdx1/zImage

tar -xvzf root.tgz -C /mnt/sdx2

 

5. umount the partitions:

umount /dev/sdx1

umount /dev/sdx2

 

6. Copy barebox image and environment to the card using the script write_flash.sh:

./write_flash.sh /dev/sdx barebox.bin barebox_default_env

 

 

write_flash.sh

#!/bin/sh

DEV=$1

LOADER=$2

ENVIRONMENT=$3

err_exit () {

  echo -e "Error: $1\n";

  echo -e "\tUse this script with parms: Device BareboxImage bareboxEnvironmentImage"

  echo -e "\tEx: write_flash.sh /dev/sdb barebox.bin barebox_default_env"

  exit 1

}

[ -z "$DEV" ] && err_exit "device not found"

[ -b "$DEV" ] || err_exit "Device '$DEV' not a block device."

[ -f "$LOADER" ] || err_exit "barebox image not found"

[ -f "$ENVIRONMENT" ] || err_exit "barebox environment image not found"

 

echo "Writing bootloader '$LOADER' and environment '$ENVIRONMENT' to '$DEV'"

 

echo -ne "Writing loader: "

dd if="$LOADER" of="$DEV" bs=512 skip=2 seek=2 >/dev/null 2>&1 && echo "Ok" || echo "False"

 

echo -ne "Writing environment: "

dd if="$ENVIRONMENT" of="$DEV" bs=512 seek=4096 >/dev/null 2>&1 && echo "Ok" || echo "False"

sync

Activating and deactivating cores

To determine the number of active cores use:
grep '^processor*:*' /proc/cpuinfo | cut -d : -f 2 | wc -l

Turning off a core, i.e. core #1 (cpu0):
echo 0 > /sys/devices/system/cpu/cpu0/online

Reactivating core #1 (cpu0):
echo 1 > /sys/devices/system/cpu/cpu0/online

Use "cpu1" for core #2, "cpu2" for core #3, ...

But please note:

i.MX6 Solo and Dual Lite will behave differently to a Quad with only 1 or 2 activated cores, anyway! Amongst others this is due to different width and speed of the busses.

 

 

Windows Embedded Compact 2013

Fragen und Antworten zu ähnlichen Produkten

Setting boot mode DIP-switch

As being described within the manuals, for booting from SD card DIP-Switch S3 must be set to ON-ON-OFF-OFF. But in case that your baseboard is an OEM-board instead of that shipped within our RDKs, most probably this switch is not populated. In such a case you need to wire the according pads or close solder jumpers (see schematics of your OEM-board).

QNX BSP

Our partner BitCtrl created a QNX BSP for the phyFLEX-i.MX6. Please visit their pages for more information.


English: http://www.bitctrl.de/produkte/hw_qnx/bsp/phyFLEX-i.MX6/index_en.shtml

German: http://www.bitctrl.de/produkte/hw_qnx/bsp/phyFLEX-i.MX6/index.shtml

 

 

Back to product

Back to the product pages of phyCORE-i.MX 6 and phyBOARD-Mira.

*) discontinued, not recommended for new products / development