I am evaluating uVision3. I have problems when trying to use GNU toolchain. I first created a new folder which includes the defautl startup.s file. I copied and pasted the pot.c file from C:ADuC_Beta702x\Code\...ADC\pot.c. I have already installed the GNU(GCCARM331.EXE from CD). When I hit the "translate" icon, I get: compiling pot.c... arm-uclibc-gcc: cannot specify -o with -c or -S and multiple compilations pot.c - 0 Error(s), 0 Warning(s). I can not do build or do anything from here. Can anyone help? Thank you
GNU tools, like most Unix tools of these days, can deal with spaces in filenames quite fine --- if you pass them in correctly, so blanks inside arguments can be distinguished from blanks separating arguments. The onus is on uVision, here: it should have either quoted this -I argument, or generated a message at installation time that blanks in filenames had better be avoided. OK. So, I installed the Keil tools as the previous poster described (under the Program Tools folder) and I compiled each and every GNU example program we provide. They each compiled with no errors and no warnings. There were many spaces in the path to the tools and in the path to the examples. Then I started looking for a POT.C file. I couldn't find one. So, I think a little more information is required to solve this issue. 1. Where did the POT.C file come from? 2. Is it part of the Analog Device's CD-ROM or was it obtained from a Keil CD? 3. What version of uVision3 are you using (click help-about)? The answers to these questions will help to resolve this issue. Jon
OK. So, I installed the Keil tools as the previous poster described (under the Program Tools folder) and I compiled each and every GNU example program we provide. They each compiled with no errors and no warnings. There were many spaces in the path to the tools and in the path to the examples. Then I started looking for a POT.C file. I couldn't find one. So, I think a little more information is required to solve this issue. 1. POT.C came from KEIL code examples that was included in my ADuC7026 eval board. C:\ADuC_Beta702x\Code\Keil Code Examples\ADC\Pot.c 2. I initially installed uV3 from a KEIL CD. But I also encountered the same problem from the Analog Device CD-ROM as well. 3. I used two versions. the Analog Device KEIL had a release 7.2004 (V3.05b), and the KEIL CD had a release 10.2004(do i really have to reinstall?). Both versions encountered the same problem until I moved the KEIL directory from C:\Program Files\KEIL... to C:\KEIL...