Difference between revisions of "Ezynq"

From ElphelWiki
Jump to: navigation, search
m
m
Line 44: Line 44:
 
* Add a new board record to the list in the ''boards.cfg'' (or leave as is if the item already exists).
 
* Add a new board record to the list in the ''boards.cfg'' (or leave as is if the item already exists).
 
* Create a configuration file for the new board - use ''include/configs/zynq_microzed.h'' as a reference
 
* Create a configuration file for the new board - use ''include/configs/zynq_microzed.h'' as a reference
* Edit according to the board configuration the following files:
+
* Edit (or create new for specific memory and chip) according to the board configuration the following files:
 
  include/configs/ezynq/ezynq_MT41K256M16RE125.h
 
  include/configs/ezynq/ezynq_MT41K256M16RE125.h
 
  include/configs/ezynq/ezynq_XC7Z010_1CLG400.h
 
  include/configs/ezynq/ezynq_XC7Z010_1CLG400.h

Revision as of 12:19, 4 October 2013

Decription

Ezynq project is started to create a bootloader for systems based on the Xilinx Zynq SoC without the inconvenience of the non-free tools and/or files. The goal is not just to "free" the code, but to provide users with the higher degree of flexibility in fine-tuning of the configuration parameters.

Supported boards

Output

  • boot.bin (fsbl is not required to boot)

Install meta-toolchain (Ubuntu 13.04)

sudo apt-get install texinfo chrpath
git clone -b dylan git://git.yoctoproject.org/poky
cd poky
. ./oe-init-build-env
bitbake meta-toolchain

  • Run installation script in build/tmp/deploy/

Install ezynq (Ubuntu 13.04)

git clone git://git.code.sf.net/p/elphel/ezynq ezynq
cd ezynq
./install_uboot.sh

Generate boot.bin

  • Edit initenv according to the built meta-toolchain

cd u-boot-xlnx
./makeuboot

  • The generated files are:
    • boot.bin - the bootloader image
    • u-boot.html - configuration settings overview
    • u-boot.map - the bootloader's memory map
    • u-boot - ELF file

Develop (add boards support)

  • Add a new board record to the list in the boards.cfg (or leave as is if the item already exists).
  • Create a configuration file for the new board - use include/configs/zynq_microzed.h as a reference
  • Edit (or create new for specific memory and chip) according to the board configuration the following files:
include/configs/ezynq/ezynq_MT41K256M16RE125.h
include/configs/ezynq/ezynq_XC7Z010_1CLG400.h
include/configs/ezynq/zed_ezynq.h
./makeuboot

IMPORTANT: Only 192KB of zynq's series on-chip memory are available at boot. It is the maximal size of u-boot.bin (not the final boot.bin)

Known issues

  • USB does not work yet.
  • Ethernet is not tested (on the board we have it does not work with provided images, so we suspect a hardware problem.
  • Bitstream loading is not tested, current code does not enable level shifters - it may be more appropriate to do just before loading of the bitstream.