Known Venom Problems
This page documents known problems and bugs in the current version of
Venom. Workarounds are shown where applicable.
When bugs are fixed in newer software releases, they are
listed in the Release Note
|
Description
|
Workaround/Fix
|
|
ROMing: Protect(2) - Report the application area
statistics to the serial port
- will only work if it is called after Protect(1) and before
the next Reset.
|
|
|
Protect(0): Leaves macro names in the symbol table.
|
If you use #DEFINE in your programs, then after calling
Protect(0) to
clear out the contents of the application flash memory, you may
find you have to
reset the controller and clear all the memory to clear out old
macros.
|
No Error Navigation in Rommed applications:
When you 'ROM' an application using Protect(1), the
information that locates each procedure in it's source
file is lost, so Error Navigation from within VenomIDE
can't work.
|
You can still find the source of errors as the error report line
numbers will refer to lines within a procedure.
|
|
PulseCounter: Sometimes (infrequently) the PulseCounter
object can start with a count
of 65536 rather than zero.
|
Reset the counter after making it.
|
FileSystem: An empty file vanishes after the system
is restarted.
Affects all versions of FAT file system.
|
Impact Not likely to be a problem as opening the
missing file will recreate it empty anyway. Applications
should be designed to recover gracefully from the
non-existence of any file. A program which uses the
time and date of an empty file would get an unexpected
result.
Workaround: Don't rely on empty files. Writing
anything (even a single byte)
to an empty file is enough to prevent this from happening.
Fix: fixed for the next release.
|
|
|
|
|
