| Tool | Error Message |
|---|
| GCC Compiler |
make.exe: C:\Users\name\AppData\Local\Temp\cbmBAA8.tmp: No such file or directory
make.exe: * * * No rule to make target `C:\Users\name\AppData\Local\Temp\cbmBAA8.tmp'. Stop.
This means that your 'Temp' directory is getting too full. This directory can safely be cleaned out using the "Disk Cleanup" tool provided by Microsoft. Depending on your operating system, you can open the tool from here:
Windows XP: Start→ All Programs→ Accessories→ System Tools→ Disk Cleanup
Vista\7: Start, type "Disk Cleanup" into the search box.
After launching Disk Cleanup, make sure to check the box next to "Temporary files" ( not "Temporary Internet Files" ). Before clicking "OK" make sure that you review any additional files that will be deleted by this program. Mosaic recommends that you uncheck "Compress old files" because of the length of time that this operation takes.
|
| GCC Compiler |
C:\MosaicPlus\c\tools\ gcc\bin\m6811-elf-ld.exe: Warning: size of symbol `Balance_Function' changed from 1349 in .objs/main.o to 1439 in .objs/scale.o
This message means that the function 'Balance_Function()' was defined twice; Once in 'main.c' and once in 'scale.c'. Although this message specifically addresses the size change, it is really warning you that the function is defined two times. Simply rename one of the functions to resolve this error.
|
| GCC Compiler |
Error: Ran out of room allocating section .text.1 object C:/MosaicPlus/my_projects/big/big_prelink1.elf of size 5700
This error is generated when a function or file is too large. To resolve this error, create a new .C file in your project directory. Add this file to your project by clicking "Project→ Add files…" and choosing the file you just created.
You will need to break up extremely long functions into two or more parts. Do this by moving some code from the long function into a new function. Then just call your new function from the long function. Put your newly created function in the new .C file.
If you are having problems resolving this error, please Contact us.
|
| GCC Compiler |
timekeep.c:137: error: 'FunctionTimer_ISR_xaddr' undeclared (first use in this function)
This error means that the requested name is undeclared. In general this error is resolved by making sure you have defined the requested variable, and that there are no typos in your program.
This error is mentioned here specifically because of the '_xaddr' postfix. The "ATTACH(name)" macro requires that "name_xaddr" is defined before "ATTACH()" is called. This can be confusing because the "_xaddr" postfix is hidden, but still required.
You can resolve this error by calling "MAKE_XADDR(name)" if this error was generated by "ATTACH()". See attach-makes-it-simple.
|
| GCC Compiler |
C:\MosaicPlus\dev_tools\msys\1.0\bin\make.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0
If you receive this error, please save all your work and restart your computer.
|
| GCC Compiler |
or
C:\MosaicPlus\c\tools\gcc\bin\m6811-elf-ld.exe: cannot find -lbsp_pdq
If you receive this error, you should click "Tools→ Rebuild libraries" from the toolbar of the Mosaic IDE Plus. This will pop-up a box with the title "rebuild.sh", and messages will print. After the messages finish printing there should be the word "SUCCESS!" next to every kernel version listed. If this is not the case, you may need to re-install the Mosaic IDE Plus software. You can also contact Mosaic Industries in this situation.
Close the "rebuild.sh" window by pressing enter. Rebuild your application by clicking "Build→ Clean & Rebuild".
|
| GCC Compiler |
Error: Offset out of 5-bit range for movw/movb insn: 66
found in a file similar to
C:/Users/username/AppData/Local/Temp/ccsHbaaa.s:100
If you receive this error, your program may have an extern forward declaration of a global variable that is actually local. This can happen if you are moving variables from global to local, and have forgotten to remove references in the .h file. To resolve this issue, remove the offending "extern" statements and rebuild your application by clicking "Build→ Clean & Rebuild".
|
| Runtime Message |
C malloc heap has run out of space
This error will appear on the Mosaic Terminal when connected to serial1. This error can be generated for two reasons. Using malloc() and requesting too many bytes will result in this error. Calling the memory hungry printf() can also cause this error.
If a call to printf() emits this error, it means that your program has defined too many strings or variables in common memory. To resolve this problem, put some or all of your strings and variables in paged memory. See Making Effective Use of Memory for more information about paged memory. For sample code that uses arrays in paged memory, see using-lookup-tables.
Note: In general it is a bad idea to use malloc() or asprintf() with any embedded system because of memory limits.
|
| Runtime Message |
GUI communications buffer is corrupted!
These errors are emitted by the GUI Toolkit on the PDQScreen when the slave Freescale 9S12 (HCS12) microcontroller is not responding. These error messages do not apply to the PDQ Board. If either message is printed, it means that the GUI Toolkit driver is being mishandled in some way.
Most likely this message means that you are calling GUI routines from multiple tasks at once. You should only use one task to run your application’s user interface so that only one task interacts with the GUI Toolkit. If a task conflict is the issue, the errors will occur seemingly at random, and your program will experience intermittent crashes. To resolve this issue, double check your code to make sure that GUI routines are only called from one task.
These errors can also be caused by passing invalid arguments to GUI routines. If this is the cause, the message will print at the same place in your program. Try and track down exactly where the message is being generated and closely examine your usage of GUI routines.
If you are having problems resolving this error, please Contact us.
|
| Runtime Message |
Error! Program Compiled for Wrong Kernel Version!
This error is displayed at download time if your program has been compiled for the wrong Kernel Version.
To check your current kernel version, type:
VERSION COUNT.TYPE
To resolve this issue, click Project→ Project Compiler Options from the Mosaic IDE Plus. Click the dropdown box and choose the correct version. When you click close, the project will automatically clean. After the clean process has finished, click Build→ Build. Now load the newly created .DLF file to your board. This error will not appear and your program will load completely.
|
| QED-Forth |
Error at CMOVE Data stack underflow!
This error indicates that a word tried to remove an item from the stack, but the stack was empty. In this case, the "CMOVE" word requires 5 items on the stack to execute. See Forth v6 Function Summary for a list of all Forth words and their stack requirements.
See error-and-warning-messages for more information about Forth error messages.
|
| QED-Forth |
anew globals_section Error at GLOBALS_SECTION Can't compile–Not RAM!
If you receive this error, it most likely means that RAM on your PDQ Board is write protected. See this note.
|
| QED-Forth |
VARIABLE NEWVAR ↓ NEWVAR isn’t unique ok
This error means that you have defined the same name twice. See error-and-warning-messages for more information about Forth error messages.
|
| QED-Forth |
Can't compile deferred lib-to-lib call!
In compilation mode, an error occurs if <name> is in a different library or application segment than the segment that CFA.FOR is located in. To resolve this condition, simply define a colon definition synonym for <name> in the current library or application segment, and use the synonym as the argument of CFA.FOR.
This limitation and error message applies to:
→ CFA.FOR
→ '
→ <DBUILDS
→ <VBUILDS
|
| QED-Forth |
Error at VALLOT Page boundary was crossed!
When allocating variable space with VALLOT, or defining a word using a colon definition, a page boundary may not be crossed.
If this error was generated when allocating a variable, use this line to increment the page of the variable pointer:
0x8000 VHERE NIP 1+ VP X!
If this error was generated by a colon definition, place the following code before the definition to increment the page of the dictionary pointer:
0x8000 HERE NIP 1+ DP X!
The code for the colon definition will then be placed on the new page.
|
| QED-Forth |
Memory write failed during segment loading; try reloading all libraries.
Attempting to reload a segment whose definition is still in memory may produce this error message. To resolve this, do a COLD restart and reload the code.
|
