Filter
Top Products
Writing a Loader File to Flash Memory
7-6 Getting Started with ADSP-BF548 EZ-KIT Lite
ing a boot stream on an ADSP-BF548 EZ-KIT Lite is the 32 MB, 16-bit
wide burst flash memory. VisualDSP++ includes a Flash Programmer util-
ity to program the loader file into flash memory ready for booting.
From the Tools menu, click Flash Programmer to open a three-page dia-
log box. Figure 7-2 shows the Driver page, the initial setup page of the
dialog box. The Flash Programmer manages the overall flash program-
ming process but relies on a driver, running on the ADSP-BF548
processor, to issue the appropriate commands to erase and write flash sec-
tors or blocks. VisualDSP++ provides drivers for the EZ-KIT Lite flash
memories. You specify the driver file on the Driver page of the Flash Pro-
grammer dialog box. For the burst flash memory, use the Browse
command to navigate to
<install_path>\Blackfin\Examples\ADSP-BF548 EZ-KIT Lite\Flash
Programmer\Burst\BF548EzFlashDriver_PC28f128.dxe
, then click Load
Driver. After a few seconds, the message “Success: Driver loaded.” will
appear in the Message center text box.
Now move to the next page by clicking the Programming tab of the dia-
log box (Figure 7-3). Flash memory must be erased before it can be
re-programmed. The Pre-program erase options control the erasing pro-
cess and specify flash memory sectors to erase. You can erase only sectors
required to hold the new loader file, the entire flash memory, sectors listed
on the right-hand side of the page, or none at all. Erase affected is the
appropriate choice for simple flash programming tasks.
The middle panel of Figure 7-3 is where you specify the format of the file
holding the data to be programmed into flash memory. This should match
the format you direct the loader utility to create, with Intel Hex being the
most commonly used format.
Now use the Browse command under the Data file text box to select the
loader file created by your VisualDSP++ project. You can instruct the flash
driver to check that the loader file data is being programmed correctly, on
a sector-by-sector basis, by clicking the Verify while programming check
box. Or, you can use the Compare command once programming is com-