Splitter Output Files In Ascii Format; Debugger Files - Analog Devices VisualDSP++ 3.5 Manual

Table A-4. End-of-File Record Example (Cont'd)
Field
01
FF

Splitter Output Files in ASCII Format

When the loader is invoked as a splitter, its output can be an ASCII-for-
mat file with the
representations of ROM memory images that can be post-processed by
users. For more information, refer to the chapter in this manual that is
appropriate for your target processor.

Debugger Files

Debugger files provide input to the debugger to define support for simula-
tion or emulation of your program. The debugger supports all the
executable file types produced by the linker (
I/O, the debugger also supports the assembler's data file format (
the loader's loadable file formats (.
The standard hexadecimal format for a SPORT data file is one integer
value per line. Hexadecimal numbers do not require an
can have any number of digits but is read into the SPORT register as
follows:
• The hexadecimal number is converted to binary.
• The number of binary bits read in matches the word size set for the
SPORT register, which starts reading from the LSB. The SPORT
register then fills with zero values shorter than the word size or
conversely truncates bits beyond the word size on the MSB end.
VisualDSP++ Loader Manual
for 16-Bit Processors
Purpose
Record type
Checksum
extension. ASCII-format files are text
.LDR
LDR
, ,
.DXE .SM .OVL
).
0x
File Formats
). To simulate
) and
.DAT
prefix. A value
A-9