Hey there, I'm using the FX2 on a Spartan-3 devel board. I'm going through the GPIF Primer, but I'm running into a problem in uVision2. The code that is being generated by the GPIF Designer (gpif.c) contains the following segment: // use dual autopointer feature... AUTOPTRSETUP = 0x07; // inc both pointers, // ...warning: this introduces pdata hole(s) // ...at E67B (XAUTODAT1) and E67C (XAUTODAT2) // source AUTOPTRH1 = MSB( &WaveData ); AUTOPTRL1 = LSB( &WaveData ); // destination AUTOPTRH2 = 0xE4; AUTOPTRL2 = 0x00; // transfer for ( i = 0x00; i < 128; i++ ) { EXTAUTODAT2 = EXTAUTODAT1; } The problem is that when this attempts to compile, I get the following errors: compiling gpif.c... GPIF.C(251): error C202: 'AUTOPTRH1': undefined identifier GPIF.C(252): error C202: 'AUTOPTRL1': undefined identifier Google's got nothing useful to say abuot this that I can find, and neither have I have been able to find anything on these forums so far. I seem to get this issue everywhere I turn (both in my own project, and in the example code), and can't seem to fix it. Any help? This is really driving me up the wall. Thanks
Error 202 is an undefined identifier. Find the definitions of AUTOPTRH1 and AUTOPTRL1 because the compiler can't, or just put two arbitrary defines for them in your source file and see if the error goes away.
Yeah, I've been searching everywhere that makes sense, even using general searches through all files (binary or otherwise) using find. All searching has been to no avail. I was worried that if I use a arbitrary define, that the register will not serve its purpose in this autopointer feature.
"I use a arbitrary define, that the register will not serve its purpose" Of course it won't! Doesn't the Datasheet give you the necessary information to create a correct definition??
View all questions in Keil forum