http://docs.blackfin.uclinux.org/ 2010-09-08T20:53:43-04:00 http://docs.blackfin.uclinux.org/ http://docs.blackfin.uclinux.org/lib/images/favicon.ico text/html 2010-01-20T23:27:14-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:anomalies&rev=1264048034&do=diff Silicon anomalies can lead to erratic behaviors and consequently lead to instability in a hardware system. This document outlines all the silicon anomaly workarounds relevant to Das U-Boot, targeting the Blackfin processors. Please keep this list sorted numerically. text/html 2009-09-15T19:43:21-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:booting_methods&rev=1253058201&do=diff The Blackfin processor supports many different methods to load and execute U-Boot, depending on the specific processor variant. Whatever the on-chip Boot ROM supports, U-Boot supports. Consult the Boot ROM Boot Modes page for more information. Once U-Boot is up and running, other applications or operating systems can be booted from any peripheral/device that the Blackfin processor and U-Boot supports. This means U-Boot can load from a much larger variety of sources than the on-chip Boot ROM. text/html 2009-09-15T22:20:35-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:compiling&rev=1253067635&do=diff The latest release of Das U-Boot for the Blackfin processor can be found on the Blackfin Linux website in the U-Boot Project Files. There you can find tested precompiled images as well as the source archive. Unpack Once you've download the source code for the latest version, you can unpack the source archive by doing (replace u-boot-1.1.6.tar.bz2 with whatever filename you downloaded if it is not the same): text/html 2010-01-31T04:07:20-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:customizing&rev=1264928840&do=diff Every board port has its own board config file, and largely all customizable settings live there. You can usually find it at include/configs/<board>.h. Compiler related settings are placed in the board-specific config.mk which can usually be found at board/<board>/config.mk. text/html 2009-04-24T20:47:04-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:debugging&rev=1240620424&do=diff In the ideal world, everything should “just work”. In reality, porting to new boards is far from that. This page should help give direction in such situations. First thing to do is check the Hardware Design Checklist for the Blackfin® Processors. text/html 2007-11-16T22:21:46-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:dhcp&rev=1195269706&do=diff Das U-Boot includes a basic DHCP client that is pretty trivial to utilize. This allows you to get the board connected to the network quickly and dynamically so you can transfer files at high speeds or other such fun things. Setup If you don't have a DHCP server set up already, see the guide for setting up a DHCP server. text/html 2010-04-16T11:02:20-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:env&rev=1271430140&do=diff The power of U-Boot can come from it's ability for run time configuration. This flexibility is based on being able to easily change environment variables. These “environment variables” are set up be default in the board's ./include/configs/board_name.h file, and is kept in flash at a predefined location: text/html 2007-11-21T12:50:28-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:faq&rev=1195667428&do=diff This is a collection of some of the most frequently asked questions about running Das U-Boot on the Blackfin processor. U-Boot takes forever to write to flash! There was a bug in the flash driver in older versions of U-Boot (and thus the version found on many development shipped boards) that caused flash operations to take an inordinate amount of time, even with quite small files. If you install the latest release of U-Boot, the amount of time required to write to flash should return to norm… text/html 2009-01-23T05:45:23-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:features&rev=1232707523&do=diff U‑Boot is a boot loader program that is usually stored in flash memory on the embedded system. U‑Boot can load files from a variety of peripherals such as a serial connection, an ethernet network connection, or flash memories. Often times, U-Boot is the program that gets executed at system reset which will automatically load up another application (such as the Linux kernel). U-Boot can even parse many types of filesystems on many types of storage devices. text/html 2010-06-08T19:46:30-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:gpio&rev=1276040790&do=diff Like Linux, Das U-Boot has a GPIO/Portmux framework for managing pins. So if you wish to write code that works with specific pins, consult those pages. Additionally, Das U-Boot provides a gpio command that can be used from the console to tweak GPIOs on the fly. This page will cover that functionality. text/html 2010-06-09T01:26:46-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:i2c&rev=1276061206&do=diff Das U-Boot supports I2C busses and provides a simple C API to people developing code as well as a command line interface. Configuration For hardware I2C busses, you need the hard define as well as a specific driver: #define CONFIG_HARD_I2C /* Always defined for hardware I2C support */ #define CONFIG_BFIN_TWI_I2C /* Selects the Blackfin on-chip TWI peripheral driver */ #define CONFIG_SYS_I2C_SPEED /* default speed (in HZ) */ #define CONFIG_SYS_I2C_SLAVE 0 text/html 2010-04-28T18:41:48-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:jtagconsole&rev=1272494508&do=diff The Blackfin JTAG provides a method for passing data to and from the Blackfin core while it is still running. Basically, a gdbproxy process will listen via TCP/IP and take care of passing data via JTAG to/from the core. For more backend details, see this page. text/html 2010-07-02T12:53:50-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:loading&rev=1278089630&do=diff Flash memory on your development platform should come preloaded with a working U‑Boot. However, if you are either: * creating a new platform * have accidentally erased U-Boot * have created a bad U-Boot that does not boot and now have a bricked board * are unlucky and your platform did not come with U-Boot text/html 2007-11-30T23:14:20-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:loading_files&rev=1196482460&do=diff There are two ways you can transfer files to U-Boot. Due to drastic speed differences, using Ethernet is highly recommended over using the UART whenever possible. * Loading Files via Ethernet and TFTP * Loading Files via the Serial Port text/html 2009-05-06T21:43:46-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:maintenance&rev=1241660626&do=diff This page describes how the Blackfin port of Das U-Boot is maintained -- both on the blackfin.uclinux.org website and the upstream denx.de website. Version Control System Developers should familiar with several source code version control systems. For the Blackfin project, we use Subversion or SVN, but upstream uses git. text/html 2008-07-28T02:21:24-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:memory-layout&rev=1217226084&do=diff The default memory layout of the Blackfin port of U-Boot is similar to the other U-Boot ports. The common documentation though tends to be a bit PowerPC specific so we'll explicitly cover the Blackfin memory layout here. Default Layout Here we show a typical system that has 64 megs of external memory. The memory regions above the asynchronous memory will differ depending on your Blackfin variant, so consult the appropriate datasheet for exact addresses if you really want to know. text/html 2010-06-08T20:03:52-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:mii&rev=1276041832&do=diff Das U-Boot provides a command line option for banging directly on the wp>Media Independent Interface bus. This allows people to poke PHYs directly (presumably for debugging purposes) via supported Ethernet MACs. Note that not all Ethernet MAC drivers in U-Boot support the MDIO functions. The Blackfin EMAC driver does support it. text/html 2009-06-14T15:38:51-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:mmc&rev=1245008331&do=diff U-Boot supports MMC Cards with multiple paritions, with the FAT file system. For general information on MMC Cards - see the MMC Cards page. To initialize the mmc/sdio subsystem, use the mmcinit call: mmcinit To get the FAT info about the card, use the fatinfo command text/html 2010-01-29T10:44:02-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:nand-flash&rev=1264779842&do=diff U-Boot supports NAND flashes hooked up a variety of ways. It may be via the asynchronous memory bank (such as the CF/NAND card) or the on-chip NAND controller that exists on some Blackfins like the BF52x or BF54x. In terms of the command line interface, the nand command is the interface to all NAND flash operations. It allows you to read/write a sequential range of bytes as well as query the NAND flash. Bad block handling is optionally supported. text/html 2010-04-28T18:41:45-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:netconsole&rev=1272494505&do=diff If you are deploying a system, which has no UART connected to it, or is not practical to connect, you can use the network console. In U-Boot, the network console is implemented via the standard “devices” mechanism, which means that you can switch between the serial and network input/output devices by adjusting the 'stdin' and 'stdout' environment variables. To switch to the networked console, set either of these variables to nc. Input and output can be switched independently. text/html 2007-11-30T22:16:39-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:network-config&rev=1196478999&do=diff The network settings of U-Boot can be manually set or tweaked on the fly. All of the network settings are available as U-Boot environment variables which can be changed using the standard environment commands. The environment settings can then be saved into flash and restored automatically the next time U-Boot boots. text/html 2010-02-04T09:38:53-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:parallel-flash&rev=1265294333&do=diff U-Boot is able to utilize parallel NOR flash hooked up to the Blackfin processor's asynchronous memory banks. Commands are provided for common flash operations such as: * reading sectors * erasing sectors * writing sectors * sector protecting text/html 2010-08-02T01:59:17-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:plan&rev=1280728757&do=diff * uboot 2010R1 plan - 15 Apr. 2010 text/html 2009-09-15T18:23:41-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:platforms&rev=1253053421&do=diff Here are all the platforms that are officially supported by the Blackfin port of Das U-Boot. While 3rd parties may also have their boards merged into the official release, they provide support for the boards rather than ADI. Anything labeled with (!) means that support only exists in the latest development tree and not the last release. text/html 2010-01-31T04:09:05-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:porting&rev=1264928945&do=diff So you have a new custom Blackfin board and you want to get Das U-Boot up and running on it? Here's the document for you. Unfortunately, it isn't the only document you're going to need. You should also make sure to have the HRM for your Blackfin variant, as well as all the datasheets for all the main parts on your board (that you will be configuring in U-Boot). Since it is the job of U-Boot to initialize all the low-level hardware details, you're going to need to know the hardware settings. text/html 2010-06-08T18:18:33-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:release-notes&rev=1276035513&do=diff Choose thy version! * 2005r3 - 25 Aug 2005 - U-Boot 1.1.3 * 2005r4 - 25 Nov 2005 - U-Boot 1.1.3 * 2006r1 - 25 Mar 2006 - U-Boot 1.1.3 * 2006r2 - 31 Sep 2006 - U-Boot 1.1.3 * 2007r1 - 09 Apr 2007 - U-Boot 1.1.6 * 2008r1 - 13 Mar 2008 - U-Boot 1.1.6 * 2008r1.5 - 15 Aug 2008 - U-Boot 1.1.6 * 2009r1 - 25 Aug 2009 - U-Boot 2008.10 * 2009r1.1 - 25 Dec 2009 - U-Boot 2008.10 * 2010r1 - pending - U-Boot 2010.03 text/html 2008-12-11T07:24:01-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:serial-flash-eeprom&rev=1228998241&do=diff U-Boot supports serial EEPROM NOR flashes which hook up to the Blackfin processor via a 4 wire SPI-compatible interface. Commands are provided for reading/writing of the EEPROM device. Splitting up of requests across pages is handled transparently to the user as is erasing of sectors before writing. text/html 2010-07-22T13:25:48-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:serial-flash&rev=1279819548&do=diff U-Boot supports serial NOR flashes which hook up to the Blackfin processor via a 4 wire SPI-compatible interface. Commands are provided for reading/erasing/writing of the device. In terms of the command line interface, the sf command is the interface to all serial flash operations. It allows you to read/erase/write a sequential range of bytes as well as query the SPI flash. You can also select different flashes at runtime based on the SPI chip select. text/html 2007-11-08T01:56:28-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:serial_port_loading_files&rev=1194504988&do=diff When a network connection is not available, U-Boot can be load files via the serial port. U-Boot currently supports two protocols: kermit or y-modem. There are several terminal programs available and most likely your favorite one will work with at least one of these. Here we will cover three of the most common ones: C-Kermit and minicom in Linux and HyperTerminal in Windows. text/html 2010-06-09T01:38:06-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:spi&rev=1276061886&do=diff Das U-Boot supports SPI busses and provides a simple C API to people developing code as well as a command line interface. For working with SPI flashes, see the serial-flash page for more information. Configuration To enable support for the Blackfin on-chip SPI controller: text/html 2008-08-01T00:30:47-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:testing&rev=1217565047&do=diff Purpose The purpose of testing U-Boot is to ensure the release is stable and robust, which can be used to initialize the target board and boot it into the uClinux kernel. Overview To test the Das U-boot, a host system and Blackfin target are required. The host system is where the U-Boot source code is downloaded and built. The Blackfin target enables tests to be run on the processor ensuring that the U-Boot binary can initialize the board properly before the uClinux kernel has been booted u… text/html 2009-09-15T22:42:15-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:tftp_loading_files&rev=1253068935&do=diff With a network connection available, U-Boot can load files quickly and easily via TFTP. If you need information about how to even connect to the board initially for basic communication, please see the terminal programs document. If you need information about how to setup a TFTP server, please see the setting up a TFTP server document. text/html 2009-10-01T09:55:19-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:uimage&rev=1254405319&do=diff While U-Boot can boot a variety of file types (ldr files, elf files, binary files) and it includes support for its own special format - the U-Boot image format (or uImage). The format stores information about the operating system type, the load address, the entry point, basic integrity verification (via CRC), compression types, and free description text. Some common bootable U-Boot images you will encounter are files typically named uImage or vmImage. text/html 2008-09-08T02:20:45-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:upgrading&rev=1220854845&do=diff As described in the Compiling U-Boot section, when U-Boot is built, it generates some bootable images. Make sure you've selected the proper binary file for your target board and boot mode. U-Boot has the flexibility of upgrading itself on the fly by re-flashing the board without having to resort to a JTAG cable. text/html 2009-11-20T10:49:06-04:00 http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:usb&rev=1258732146&do=diff U-Boot supports USB Mass Storage Devices with multiple paritions, with the FAT file system. Everything is accessed via the usb command: help usb To initialize the usb subsystem, use the usb start call: usb start Yeah - you actually need to plug something in: