Site Index
   Home
   File Upload
Google

Transfer Site
Main Site

EVM5509 FAQ


Board Specific Issues


Board Specific Issues

1.1 Daughtercard McBSP Signals
The McBSP signals on the 5509 EVM follow a slightly different layout than boards that follow the standard expansion connector format such as a 5510 DSK. This is done to maintain compatability with the Skywalker Internet Audio board. The following chart shows the pin differences between the two formats, you can map one to another by swapping the DX and CLKX pins.

 
    Pin       5509EVM     5509EVM    5510DSK
              Schematic   Function   Function
    33        MMC2.CLK    DX2 -----> CLKX1
    35        MMC2.DAT3   FSX2       FSX1
    39        MMC2.CMD    CLKR2      CLKR1
    41        MMC2.DAT2   FSR2       FSR1
    36        MMC2.DAT0   CLKX2 ---> DX1
    42        MMC2.DAT1   DR2        DR1

1.2 Booting code from Flash
The preferred way to boot code from Flash on a 5509 EVM is to convert the program into a bootloader format hex file using TI's hex55 conversion utility (included with Code Composer), then use the FlashBurn Code Composer plug-in to program the hex file into Flash. FlashBurn itself is available for registered users of Code Composer through the online Update Advisor. A port of the FlashBurn programming algorithms that allow FlashBurn to work specifically with the 5509 EVM can be found on the site: http://c5000.spectrumdigital.com/evm5509( in the EVM5509 Multi-stage boot utility section )

The 5509 EVM in its current form uses the 5509 in the PGE low-profile quad flatpack package which only has 14 address lines. The implication of small number of address lines is that only 16 Kwords of the Flash can be seen at any given time. The on-board FPGA supplies the upper address bits to the Flash via a user programmable register (see the 5509 EVM Technical Reference that ships with the EVM) to create a paged memory view where each page is 16Kwords long. Programs too large to fit in the first Flash page must boot a small bootloader stub first that loads the rest of the code using the paged view specific to the 5509 EVM. An example of this process is given in the FlashBurn 5509 EVM port referenced in the previous paragraph.

1.3 Core voltage is set to 1.5V
The 5509 EVM was designed with a DSP core voltage of 1.5V which was based on the 5509 specification at the time the board was designed. The current specification is for 1.6V with 5% tolerance for a range of 1.52V to 1.68V. The 5509 EVM is fully tested at 1.5V and we believe that there are no issues with running the 5509 at 1.5V under normal operating temperatures. However, users designing their own hardware should aim for 1.6V to stay within the letter of the current specification.

1.4 SPI EEPROM conflicts with AIC23 codec
The AIC23 codec and SPI EEPROM share a common data output which is connected to the data input of McBSP0. However, the AIC23 always drives its data output which renders the SPI EEPROM unusable. For this reason, the SPI EEPROM is unpopulated when shipped. It is possible to use a SPI EEPROM by populating it and either lifting the AIC23 data output pin or removing the AIC23 entirely. It is impossible to use both devices at the same time although you can use one at a time by building an external multiplexor circuit.

©Copyright 2002-2011 Spectrum Digital, Inc. All Rights Reserved.