To Do

The following is the list of the files generated. Files, where some additions or changes have to be made are in red, the others in blue.

ads1259_acquire.cpp:

• This file handles the data acquisition.
• Modify the acquire_adc_done() function to match the current implementation. In most cases, the given one will work, but you might need some extra code. 
• When to add extra code: 
  • Special cleanup is needed after a block is finished. Examples for that are: 
  • DMA needs to be stopped because of corrupted data at the end of a transfer. 
  • McBSP needs to be stopped or additional receive events will be propagated to the DMA controller. 
  • A new block depends on the block just finished (e.g. coming out of an idle loop) and you need to switch to the "real" data transfer instead of issuing another idle loop transfer. 
• Several other things you will have to find out for yourself.

ads1259_acquire.h:

• Nothing. This file is fine as it is.

ads1259_version.h:

• This file holds the version number for the firmware. 
• Nothing to change for the first run
• Please increment it each time a binary file leaves your PC.

ads1259evm-mmb0.cdb: 

• The DSP/BIOS configuration file for the project. 
• Insert the interrupt routine for the DMA. The interrupt number and the name of the routine depends on the DCP software. Look there for some hints what to use.

ads1259evm-mmb0.pjt:

• The project file itself 
• No changes are necessary

ads1259evm.h: 

• Include the prototypes for the callback functions. Failing to do so will result in some nasty compile errors. 

ads1259evm_files.c:

• The file holding the file system and the callback functions for the hardware configuration 
• Insert the files necessary to match your H/W: 
  • Each register and / or feature should be represented by a file, even if it is yet unsued by ADCPro. Some stuff might come up in the future and this avoids having to touch the code after some years. 
• Insert the callback-functions for the files (i.e. the getter and setter functions).
• Keep in mind that the DCP software for the low level interface provides already a dc_control() function with most of the commands necessary, so in most cases, the callback functions are reduced to a call to this API.
• Connect the pins from the DSP to the daughtercard as necessary. See the include file for the MMB0 for more details.
• Initialize the GPIOs to match the correct direction. By default, they are inputs 
• If there are I2C port expanders on the EVM, initialize them. 
• If the PLL of the MMB0 needs to be set prior to th initialization of the data converter, please set it in this file as well. The best position for that is marked in the file (it is close to the end of the source file. 

ads1259evm_mmb0-r.hexcmd

• The firmware conversion file for the release version of the code.
• Nothing to change here.

ads1259evm_mmb0.hexcmd

• The firmware conversion file for the debug version of the code. 
• Nothing to change here. 

FW-script.pl: 

• The script file itself. 
• Don't touch it, don't read it. 
• Don't even think about it! 

main.c:

• Entry point for the program. 
• No changes necessary. 

make.bat:

• Makes the debug version of the firmware.
• No changes necessary.

makebin-r.bat:

• Makes the release version of the firmware and copies it over to c:\Program Files\ADCPro\plugins\ads1259evm\fw. 
• Change the copy path if you want your firmware elsewhere

makebin.bat:

• Makes the debug version of the firmware and copies it over to c:\Program Files\ADCPro\plugins\.
• Change the copy path if you want your firmware elseware.

MMB0.gel:

• The GEL file for the MMB0. Include this file in your Code Composer Studio setup as the startup GEL file.
• Note: The load program function of the GEL just loads the debug version, not the release version.

What else to do:

• Use the data converter support tool to create the low level driver for the device or write your own driver.