This is extensively documented in section 184.108.40.206 of the FX3 Programmer's Manual. Read that and see if you can successfully debug project.
Thanks for your reply
yes I have made all the settings suggested by programmers manual
after I start executing step by step that is when I am debugging when it is at the step
it gives the error
sorry I mean to say resume executing as similiar to step "220.127.116.11 page no 164".
The source of APIs are not available. So while step-by-step debuggin when you try to enter an API, it throws that error that the source is not available. Ignore that and Click on 'resume' or 'step-over' button.
CyU3PDeviceInit() is implemented in a file called cyu3device.c in the SDK. But we don't release the source code and so you can't jump into the function.
So, you can use 'Step Into' only for your functions or the ones already there in the firmware. For SDK functions, use 'Step Over'.
Thanks for the help NIKL and MANU
I am already working on it.
Can some one explain me what does this way of gpio settings mean
gpioSimpleEn = (1 << (FPGA_DONE-32)) | (1 << (FPGA_INIT_N-32))
| (1 << (DQ16-32))| (1 << (DQ17-32))| (1 << (DQ18-32))| (1 << (DQ19-32))| (1 << (DQ20-32))
| (1 << (DQ21-32))| (1 << (DQ22-32))| (1 << (DQ23-32)) | (1 << (DQ24-32))| (1 << (DQ25-32))
| (1 << (DQ26-32))| (1 << (DQ27-32));
io_cfg.gpioSimpleEn = 1<<SOME_PIN means that SOME_PIN is being used as a Simple GPIO. gpioSimpleEn is a bitmapped variable where a '1' at bit 'x' means that pin GPIO[x] is being used for that purpose (simple GPIO). Since there are >32 pins, gpioSimpleEn is an array of 2 uint32s.
Thanks for the information you made things very clear
I am presently programming a firmware to perform slavefifo sync interface with FPGA.
So should I also initialize using the gpiosimpleen the clock signal from fpga, slcs,slrd etc etc...??
No. These signals are control lines that are used by the GPIF hardware. If you initialize them in gpioSimpleEn, they will be used as GPIO and not control lines for GPIF.