Error Messages

This problem was observed on a computer running a 64-bit version of Windows, in which virus protection software appeared to redirect an attempt to register the Visual Basic ActiveX controls file listed above in the SysWOW64 folder to the system32 folder instead, where there was no comctl32.ocx file. If you see this error while trying to install Mosaic IDE Plus, disable any running virus protection or security software, and attempt to run the installer again. You may wish to disconnect your computer from the Internet before disabling virus protection or security software.

If you are having problems resolving this error, please Contact Us.

When this error was observed, the Windows Event Viewer reported an application error on starting codeblocks.exe related to the DLL file mingwm10.dll, which is a runtime library used by programs compiled with the MinGW port of GCC for Windows. Codeblocks is itself compiled with MinGW, and this error was observed on a computer that had multiple installed programs that had been compiled with MinGW, and multiple different versions of mingwm10.dll. The solution is to rename the file C:\MosaicPlus\dev_tools\codeblocks\codeblocks.exe.manifest to codeblocks.exe.manifest-unused, or if you do not see the manifest extention, move the file of type MANIFEST in this folder to a different folder. This may affect visual styles of controls in the CodeBlocks editor on Windows XP.

If you are having problems resolving this error, please Contact Us.

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.

This error or crash 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.

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_ISR(name) if this error was generated by ATTACH().

If you receive this error, please save all your work and restart your computer.

This is a failure of the objalloc program which places blocks of code in the PDQ Board's paged flash storage. The fact that it crashes is a bug, but the root cause is that an individual function has grown too large to be allocated. In particular, this tends to happen when extensive calculations are performed using Double-precision_floating-point_format variables, the C double type. By default, floating point literals are interpreted as type double by GCC, and the basic standard library functions with headers in math.h such as log(), pow(), etc., accept arguments and return values of type double. This is unfortunate for the use of GCC in embedded systems, as the precision of the 32-bit float type is more than sufficient for measurement and control applications, and using the 64-bit double type balloons the code size.
If this problem is caused by complex calculations using the double type, switch to using the float type, add the f suffix to all numeric literals, and add the f suffix to math.h function calls, i.e.:
float a, b;
a = logf( 42.0f );
b = powf( a, 3.1415927f );
If you experience this error and your application does not use the double type, look for very long function definitions that may be broken into multiple shorter functions.

If you are having problems resolving this error, please Contact Us.

If you are having difficulty downloading a compiled application to the PDQ Board, first ensure in Mosaic Terminal, under the Settings menu →  Comm window, that Stop On Error is set to On. A code download for a project using web resources (web_resources subfolder is not empty), generally for the EtherSmart or WiFi Wildcard, may stop with the last few lines being similar to those shown above. This bug can be identified by noting that the last or second-last line contains C000 six characters from the start. This is an invalid address at which to load code for the PDQ Board, produced by a bug in the image converter program used to convert web resources into S-record data. All released versions of Mosaic IDE Plus as of October 2014 include a version of the image converter program containing this bug; if you encounter it, please contact Mosaic Industries for an updated image converter program.

When downloading compiled code to the PDQ Board, the code is first placed in paged RAM and then copied to shadow flash at the end of the download. This message indicates that the routine that saves the application code to shadow flash encountered some kind of error.

One reason this error may appear is a low power supply voltage. The PDQ Board requires a regulated 5 volt supply within a tolerance of ±5%, i.e. 4.75V to 5.25V. If the supply voltage is near the bottom of this range, the extra current drawn while writing to flash may cause the voltage to drop out of this range briefly and the flash write to fail. Check the power supply using a voltmeter by CAREFULLY measuring the voltage between pins 1 and 2 on either Wildcard Bus or Module Bus header, or the Digital I/O header. Do not touch the voltmeter probe to any two pins simultaneously; in particular, pin 4 adjacent to pin 2 carries the high V+RAW supply if the PDQ Board is mounted on a Docking Panel, and shorting pins 2 and 4 will permanently damage the PDQ Board.

If the power supply voltage is above 4.9V, the problem may be due to defective or worn-out flash memory cells, in which case the board needs to be replaced.

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.

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 Using Paged 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.

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.

If you receive this error, it most likely means that RAM on your PDQ Board is write protected. See this note.

This error means that you have defined the same name twice. See error-and-warning-messages for more information about Forth error messages.

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

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.