world leader in high performance signal processing
Trace: » bf537-ezkit

BF537 EZKit


Normally, the BF537-EZkit should have the same setup as the bf537-stamp, however, there are a few additional switches/settings. Normally, if you ignore these pieces, you can treat the BF537-EZKit as a BF537-STAMP. There are a few population differences, and not all add-on cards are tested on the BF537-EZKIT. There are known issues with boards that work on the STAMP version, but not on the EZKIT version.

On-board audio

The On Board Audio codecs are not supported in Linux and make the SPORT0 unusable.

The two codecs are:

  • AD1854 - audio output
  • AD1871 - audio input

You may be able to get limited audio output by using the AD1836 driver in I2S mode.

On-Board JTAG

The USB connector on the BF537-EZKIT, is for built in In Circuit Emulator (ICE) for VDSP++ only. This ICE is not gdb friendly, and can not be used with gdb. It can be used if you just want to load something for testing - you can do it over JTAG and VDSP++. Things get stuffed into memory directly, and the PC is set to the start of the program.

National Instruments Elvis Connector

Using VDSP++

After loading U-Boot into Flash, you can still use the board for VDSP++ development (if you want). There is no 2nd stage boot loader required by VDSP applications, so there are no specific flash requirements.

The VDSP++ Tools can create either a bin file (execute in place at the start of flash), or an “LDR”, which is a made up container format for a file which needs to be relocated (put this section into xxxx address, run this code, load a second section into yyyy address - that type of thing). The loader that does this is in the BOOT-ROM of the device. You can erase flash, and the BOOT-ROM will search (depending on what the BMODE pins are set to), either parallel flash, serial flash, or UART for an LDR.

You don't need anything in flash to run a VDSP LDR. If you are using the USBJTAG ICE, then the file is loaded directly into SRAM or SDRAM, and again nothing specific is needed in the flash.

Loading U-Boot

With Linux - we use a compressed image format, so we need something that can load the image over the Ethernet / decompress the image / relocate the image, and then boot it. These are functions that the on-chip bootrom doesn't have, so, we use a second stage bootloader (U-Boot). U-Boot does not come preloaded on the EZKit, (after all, blinking lights are so much more useful ;-) ) so, U-Boot must be loaded via hand. See the loading U-Boot document for more information.