5 creating a flash image, 1 how to create an image, 6 creating a flash image -15 – Cirrus Logic CS4970x4 User Manual

Page 125: 1 how to create an image -15

Advertising
background image

8-15

Copyright 2013 Cirrus Logic, Inc.

DS810UM6

Creating a Flash Image
CS4953x4/CS4970x4 System Designer’s Guide

Click on Build->Create Flash Image

The build log window will open displaying all the files (*.uld, *.cfg etc) listed in the project (underlying xml
file) and also display if the image creation process was successful or not.. If there is a failure, scrolling
through this log will give the error messages. The log will mention any missing uld or .cfg files.

8.5 Creating a Flash Image

8.5.1 How to create an image

To create a flash image for testing or final deployment, use the Build/Create flash image command in the
Condenser wizard. This command runs a makefile that will:

Determine the size of the flash image.

Run a utility to actually create a hex ASCII flash image file which includes all specified DSP firmware
and configuration files.

Run a utility to create a .wav update file, if the project specifies to create one.

When creating a flash image, it is important that the target flash type be properly specified. If you are
creating the flash image for testing on the Cirrus Logic evaluation board, the flash type should be
SST25VF. If you are creating the flash image for deployment on your own board, this setting should be
appropriate for the flash type used in your design.

After the flash image is created, you can use the Build/Explore build outputs command to see the results
of the build. In the outputs folder are the following important files:

egg.img — The startup DSP code that is programmed into flash at location zero

flash.img — The main flash image that contains all other DSP firmware components and
configuration files

flash_update.wav — The flash.img file in .wav format, if you specified to create a .wav update file

flash.h — A C .h file that contains information about the flash.img file which must be used by the
micro-controller code as it uses the high-level DSP Manager API. Specifically, it contains a mapping
of symbolic names for the various firmware components and modes defined in the condenser
project to integer values used in host-to-DSP communication.

The other files in the outputs folder are intermediate output files that are not necessary for actual
deployment or debugging.

Advertising
This manual is related to the following products: