IPC@CHIP DK41 / DK51
Getting Started V2.2
© 2000-2004 Beck IPC GmbH Page 59 of 61
For example, in the Sleep procedure we can see that register BX is safely set with the 'how_long'
value read from off the input parameter stack, with no subsequent writes to BX by the compiler prior to
the interrupt API call.
An alternative to inspecting code is to use the compiler's int86 or int86x procedures. While these
procedures are certainly safe, they are costly in terms of execution time. For real-time programs you
may want to do some code inspecting.
For more detailed information, see the documentation of DEBUG@CHIP. You will find this
documentation after installation at the subdirectory ‘Doc’ of the Debugger’s installation path.
3.3.5 Stripping debug information from executables prior to download
The Borland debug info can require a lot of space and serves no purpose in the target system. It is
enough to have a copy of the executable with debug info on the Windows PC where the Debug@Chip
is located. The 'tdstrip' program provided by Borland will remove the debug information from an
executable file. This operation is recommended prior to downloading programs to the target
IPC@CHIP to conserve Flash disk space.
To Next Page
Loading...
