We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I get this when I compile/link a project that DOES work on my system at home. At home, I have the full uVision3 system, where as at work we are [still] using the 'new' Demo version. My question is 'simple'... are these linker errors due to the EVAL/Demo version or the 'new' uVision V4.03q?
linking... BrusselsV1.axf: Error: L6218E: Undefined symbol os_fifo (referred from p1120-3). BrusselsV1.axf: Error: L6218E: Undefined symbol os_fifo_size (referred from p1120-3). BrusselsV1.axf: Not enough information to produce a FEEDBACK file. BrusselsV1.axf: Not enough information to list image symbols. BrusselsV1.axf: Not enough information to list the image map. BrusselsV1.axf: Finished: 3 information, 0 warning and 2 error messages. Target not created
Or is it that the Demo version won't allow the RTX support?
--Cpt. Vince Foster 2nd Cannon Place Fort Marcy Park, VA
P.S. I tried tacking this onto: http://www.keil.com/forum/docs/thread17370.asp but it doesn't seem to show up.
I guess that, the below page shows the major differences.
www.keil.com/.../rlarm_ar_your_first_app.htm
Great sluething Mr. Linq.
I was working with tech support on this issue, and since the Cortex M3 uses the RTX_Config_CM.C file, I had to add in a snippet of code into that file I was using:
#ifndef OS_FIFOSZ #define OS_FIFOSZ 16 #endif /* Fifo Queue buffer for ISR requests.*/ U32 os_fifo[ OS_FIFOSZ*2 +1 ]; U8 const os_fifo_size = OS_FIFOSZ;
Once this was in place, everything worked.
I was going to post this, but was going to wait for tech support to either explain it, or post an errata.
So once again, thanks for being hot on the trail on my issue.