I am working with Dm6435 target. My Out file works as per expectation. the bin file converted from same out file is not working properly. Its getting booted properly but input capture buffer is blank. any light on this? any one faced similar issue?
Do need any changes in code before converting it to BIN?
The most common problem I have seen in this case is forgetting to include code that was automatically executed in your gel file when running the 'out' file through code composer. Step through your gel file and make sure you all the configuration is duplicated in your code. Sometimes you have to connect to the target without a gel file while it is running and examine the registers to make sure you have duplicated all the gel setup properly.
thanks a lot, I tried removing gel file in Out mode , I could reproduce issue of Bin mode. I observed that it has startup() and on TagetConnect() calls in GEL file. I need to impelement startup(), in which they are setting up memory map with few gel file APIs. Can you please guide me by providing any link, doc, example which explains how to implement gel file functionality in C code or similar if possible.
spraa74 is an old document talking about GEL file use
spraag0 talks about the bootloader for the dm643x family, you may already be using the AIS script in your generated bin file
In general, the memory map portion of the gel file does nothing more than tell the debug environment what sections of the full device memory range exist, so that it doesn't try to access memory that isn't there. If you are using AIS boot, then your pll, pinmux, external memory, and DDR2 are probably being set up by the AIS script. If you are not using AIS boot (you should be for a production device, its much faster), you will have to perform those settings in code. You should confirm the settings match what you expect. Beyond that, you will have to parse your gel file for other random bits like video port settings. Most of the gel file is just duplicating register write functionality.
If you have the dvsdk, spectrum digital included c-versions of the gel file initialization in that software, including handy include files that define all the device register locations.
Thanks Matt, that was really helpful.
We observed that we are getting -10 as return value on "FVID_Exchange()". from IOM.h we understood that
#define IOM_EBADARGS -10 /* Illegal arguments specified */ , same code works ok for Out mode. what does this mean? when it returns -10?
Can anyone guide on this?
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.