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.
OMG, I let the cat out of the bag! It was supposed to be a secret as Belgium is now on our Enemies of the State list.
The V1 rocket, is old-school. Origionally we were going to called it a "Buzz-Bomb," but some National Socialist Commander-in-Chief said nO, Bambin' way.
"BrusselsV1" happens to be the code-name (aka I made it up) for a widget that I should not discuss.
When I posted it, I thought "oh boy, I need to change the name to something stupid like 'Brussels version 1' instead of the real name." (also so I can hide the real embarrasing "Version 31.9c")
Usually I go with PaceMaker2000 or Systol-Snubber, but since I was doing some geography with the kids, I chose "Brussels." [Those Evil People in Belgium shall get their comeuppance!]
FYI... I'm working two projects and both of them resulted in the same error during link time: ONLY if I use the RTX kernel/tasks. Once I stub out, errr, remove the __task references and functions, the widget compiles and links just fine here at work.
The second project --non 'Brussels'-- is well below the 32k boundary (and that includes the data-space too). Whereas 'Brussels' is a huge program (as it takes a lot to take out a single city and not the entire country of Belgium).
Remember my OP said:
Works at home using the full version of uVision3. Doesn't work at work using the Demo version of uVision4. So, is it a change in Version4, or is it a change in Demo vs Full?
P.S. Yes, the V1 was analog.
as Belgium is now on our Enemies of the State list. [Those Evil People in Belgium shall get their comeuppance!]
Belgian women are often hot. You should try the West-Flemish ones in particular!
Belgian women are often hot.
BrusselsV2 shall be the one deployed... it targets only the male population in that area. So you should enjoy the sudden *need* for eligable men.
I personally 'own' a hot wife: http://i.imgur.com/jLnsn.jpg (uhm, she actually 'owns' me)
P.S. Thank God she doesn't read these forums!
"P.S. Thank God she doesn't read these forums!"
Can of course be corrected ;)
I realize that I might not have given enough information on my OP, but does anybody have a clue to why I'm getting linker problems once I use any _task in the RTX environment?
I am really interesed in knowing if I *need* to put in a requesition for the full $4,995 version of Keil.
We most likely will buy it anyway, I just need an excuse to say, "well, I'm stuck now, and I need to get it asap."
[The main problem is management hasn't decided if we're going to go with an 800MHz++ Ti DSP or an ARM flavor for the master controller.]
So, please---with sugar on top---help me out with this uVision4 vs. Demo vs Full version issue. Or shall I ask Keil directly?
FYI... it is the uVision3 VS. uVision4's difference. (Of which I have yet to resolve).
RFQ is in, REQ is in.
MDK-ARM due in next week. ULINK2 (another one) due in next week too.
http://www.keil.com/support/man/docs/rlarm/rlarm_ar_cfgfifosz.htm
FIFO Queue Buffer
Home » RL-RTX » Configuring RTX Kernel » Basic RTX Configuration » FIFO Queue Buffer
FYI. (might be useless to you, Captain.) http://www.keil.com/update/relnotes/RLARMV405.HTM
RL-ARM Version 4.05
Release Date: 28 January 2010
* [RTX Enhancements] Added: configurable FIFO Queue size for ISR requests in RTX_Config.c configuration file. * [RTX Enhancements] Added: runtime error function os_error() to RTX_Config.c file. The runtime error codes are defined in RTL.h * [RTX Problems solved] Corrected: a problem in Round Robin task switching. This failed if a robin task was suspended by a higher priority task. * [RTX Problems solved] Corrected: Stack checking did not work on system tick timer interrupt, only on preemptive task switches. * [RTX Problems solved] Corrected: task switch monitoring in RT Agent did not work for Round Robin task switching. * [RTX Problems solved] Corrected: incorrect event flag clearing in os_evt_wait_and() function if event flags were set separately. The following example shows the problem.
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.