Patching Flash Binary Files Using Platform Data File - Intel Quark SoC X1000 User Manual

Board support package bsp, build and software

Hide thumbs Also See for Quark SoC X1000:

Developer's manual (311 pages)

Design manual (186 pages)

Software user's manual (54 pages)

Table Of Contents

Table of Contents

Patching flash binary files

using platform data file

Note: This section is required for users who wish to update flash contents using flash

programmers, for example, during a manufacturing process. The platform data file

provides platform personality values such as platform type and board personality

values such as Ethernet MAC addresses that must be patched into the previously

mentioned Flash-missingPDAT.bin and Flash-EDKII-missingPDAT.bin files. This

section is NOT applicable to .cap / FVMAIN.fv files programmed by firmware running

on the target.

Platform data is part-specific, unique data placed in SPI flash. Every binary image

flashed to the board must be patched individually to use platform data. A data

patching script is provided in this release.

The platform data patching script (platform-data-patch.py) is stored in the

platform-data directory within the spi-flash-tools tarball in the Intel

BSP. The following text is written as if the user is executing the script on a Linux*

build machine, but the script may also be run on a Windows* build machine which has

Python 2.6 or Python 2.7 installed.

Before running the platform-data-patch.py script, open a new terminal session and

copy and edit the spi-flash-tools/platform-data/sample-platform-data.ini file

to include platform-specific data such as MAC address, platform type, and MRC

parameters.

On reference platforms, the MAC address to be programmed is printed on the product

label.

Note: The Intel

one address in the platform-data.ini file, even on boards (such as Galileo) that

have only one Ethernet port.

For Galileo, MAC 0 is the only MAC wired out. The default MAC 0 address value in the

platform-data.ini file is invalid and must be set to the value allocated to your

system, typically this is identified on a sticker.

MAC 1 must also have a valid UNICAST MAC address and the platform-data.ini file

contains a dummy but valid address for MAC 1.

If you do not set a valid MAC address, the following error message is returned:

HALT: Multicast Mac Address configured for Ioh MAC

Galileo / Kips Bay Fab D example is below, recommended values are shown in bold

text:

[Platform Type]

id=1

desc=PlatformID

data.type=hex.uint16

# ClantonPeak 2, KipsBay 3, CrossHill 4, ClantonHill 5, KipsBay-fabD 6

data.value=6

Intel

Quark™ SoC X1000

BSP Build and Software User Guide

Quark™ SoC X1000 contains two MACs and each must be configured with