This example is for the 2681 DUART that LSI uses on most of its eval boards. The values shown here are for the BDMR4101 eval board.
PMON> fill . .+100 0 -- fill memory with nops.
PMON> m be000017 ff -- enable the 2681's interrupt mask.
PMON> m be000017 -- check the 2681's Interrupt status register.
be000017 09 . -- looks good. TXA, TXB, and Timer ints are asserted.
PMON> t -- single step. This causes PMON to reread
-- the CAUSE register.
PMON> r cause -- read the CAUSE value.
C0_CAUSE: BD CE IP SW EXCODE
0 0 000001 00 Bp -- Good. Int0 is asserted.
If you are suspicious about your cables, try using PMON's tr command to check out the connection. For example,
PMON> tr % edown < file.rec -- one line of data should appear in the PMON console window press cntrl-F in the console window -- another line of data should appear in the PMON console window press cntrl-K in the console window to return to the PMON prompt
If this is an ATMizer system. The problem is most likely caused by a lack of download protocol. When downloading to an ATMizerR/T platform, you must use a download protocol. See the User's Manual for a discussion of how to configure the download protocol.
If you experience this problem when using other processors in LSI's MIPS family, the problem is most likely caused by the caches not being enabled.
You can either change the value at the PMON prompt using the 'set etheraddr' command, or you can edit the file include/defines.h and build a new PROM. See also.
For example, to increase your heapspace by 64K bytes, perform the following steps.
pmcc -T 80030000 -o test1 test1.c PMON> set heaptop 80030000 PMON> load
objcopy -O srec [infile] [outfile]
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:1024 /pWhere C:\DOS is the directory that contains COMMAND.COM and other Win95/NT utilities.
path "%path%";c:\lsipkg\lib
If it stops with a strange error, you can usually continue by simply reissuing the nmake command again. Unfortunately the only way around the problem of not being able to open new apps, is to reboot your system. These problems should go away when Tasking starts shipping real 32-bit apps, rather than these 16-bit apps with DOS extenders.