what
an
es
or
=20
Excuse me, but it isn't ME being obtuse, it's IAR's method of=20 versioning, which makes it quite difficult to document what toolchain=20 "version" was/should be used to build a particular "version" of an=20 application.
The choice is to either archive the entire IAR environment used to=20 produce the executable, or never/rarely "upgrade".
=20
Ooh, touchy, aren't we? Of course, it also ignores the fact that not=20 all "releases" of the various components work with earlier release=20 components of the same major version.
=20
Right, my point exactly.
--Gene