A new version of U-Boot is provided with each Vivado version, the current version is v2015.1.
There are several patches for U-Boot:
-
Increased PHY autonegotiation timeout from 4 to 10s.
include/phy.h -
Added support for Lantiq PHY11G.
include/phy.h drivers/net/phy/phy.c drivers/net/phy/lantiq.c drivers/net/phy/Makefile include/linux/mii.h -
Red Pitaya board added to U-Boot configuration.
arch/arm/cpu/armv7/zynq/Kconfig arch/arm/dts/zynq-red-pitaya.dts configs/zynq_red_pitaya_defconfig include/configs/zynq_red_pitaya.h -
Boot options for Ubuntu/Debian SD card images.
TODO
There are three possible sources for the U-Boot environment: configuration header file, persistent storage (EEPROM) and scripts. If the environment is taken from persistent storage (CONFIG_ENV_IS_IN_EEPROM macro is defined), then the contents of the CONFIG_EXTRA_ENV_SETTINGS macro are ignored. So EEPROM becomes the only source for the environment. Scripts can only be called from the previously described environment sources, so currently they are not used.
modeboot is internaly set to sdboot, this makes sdboot the default boot sequence.
Currently the environment is stored inside the EEPROM:
bootcmd=run $modeboot
bootdelay=3
baudrate=115200
ipaddr=10.10.70.102
serverip=10.10.70.101
prod_date=12/22/13
kernel_image=uImage
ramdisk_image=uramdisk.image.gz
devicetree_image=devicetree.dtb
bitstream_image=system.bit.bin
loadbit_addr=0x100000
kernel_size=0x500000
devicetree_size=0x20000
ramdisk_size=0x5E0000
fdt_high=0x20000000
initrd_high=0x20000000
sdboot=echo Copying Linux from SD to RAM... && mmcinfo && fatload mmc 0 0x3000000 ${kernel_image} && fatload mmc 0 0x2A00000 ${devicetree_image} && fatload mmc 0 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000
ethaddr=00:26:32:F0:03:21
nav_code=4651
hw_rev=1.0
serial=140900801
The Linux boot parameters are not appropriate for running Ubuntu images, since a different filesystem configuration is more appropriate. Pavel Demin solved this issue by patching a U-Boot source file, where some variables from the environment contained in the EEPROM are overwritten.
A new version of the Linux kernel is provided with each Vivado version, the current version is v2015.1.
arch/arm/configs/xilinx_zynq_defconfig
Kernel configuration update based on a generic configuration for Xilinx Zynq devices.
drivers/misc/eeprom/at24.c
Modifies the EEPROM driver to use a 32 Byte page size for 24c64 instead of the default 8 Bytes. This patch might improve speed and reduce EEPROM wear. There are no related changes upstream. TODO, check if the same can be achieved using runtime configuration options.
drivers/net/phy/Kconfig
drivers/net/phy/Makefile
drivers/net/phy/lantiq.c
A driver for Lantiq PHY11G is provided here. I checked the manfacturers website for an official driver, but could not find one.
drivers/net/wireless/Kconfig
drivers/net/wireless/Makefile
drivers/net/wireless/rtl8192cu/*
This patch adds the out of tree driver for Broadcom rtl8192cu chip, since there are many issues with the in kernel version (even latest kernels). The provided code was copied from the Raspberry PI kernel repository https://github.com/raspberrypi/linux/tree/rpi-3.18.y/drivers/net/wireless/rtl8192cu.
Linux kernel configuration is based on arch/arm/configs/xilinx_zynq_defconfig, which is patched to add support for RT2X00 and RTL8192CU wireless drivers. Aditional networking features are also enabled so Red Pitaya can behave like an access point routing travic from the wireless adapter to the wired port connected to the internet.
OS costumization can be split between generic components (file system mounting, network configuration, wireless access point) and Red Pitaya specific components (starting Nginx and SCPI servers).
Configuration file patches/fw_env.config should be copied to the OS image:
/etc/fw_env.config
The next scripts are installed inside /opt/redpitaya/sbin. lantiq_mdio provides access low level access to the MDIO interface, but it is not used. bazaar is a script used in application instalation, scripts ro (read only) and rw (read write) are used by bazaar or can be run by the user.
OS/filesystem/sbin/lantiq_mdio
OS/filesystem/sbin/bazaar
OS/filesystem/sbin/ro
OS/filesystem/sbin/rw