Hardware Reference
In-Depth Information
Figure D.2
■
AsmIDE terminal window after pressing the reset button
You can then enter D-Bug12 commands in the terminal window to display registers and
memory contents, modify memory and register contents, set breakpoints, trace instruction
execution, and download the program onto the demo board for execution.
If the D-Bug12 command prompt does not appear on the screen, the most likely three
causes are as follows:
1. The demo board is not powered up.
2. The RS232 cable connection is wrong.
3. The baud rate of the terminal program does not match that of the demo board.
One should make sure that the demo board has been powered up and also make sure that
the RS232 cable is connected to the right connector (if the demo board has two RS232 con-
nectors). If the D-Bug12 prompt still does not appear, then check the baud rate setting. Select
View
from the IDE menu and click on
Options.
Then click on
COM
port and the screen should
change to that shown in Figure D.3. To set COM port options, click on
Set COM Options
and a
dialog box will appear. Make sure the settings of the terminal program are identical to those in
Figure D.4. Another option that the user needs to set is
assembler
. Click on
Assembler
in the
dialog box and make sure the settings are the same as those in Figure D.5.
The user can learn the D-Bug12 monitor commands by walking through the Section 3.6.3.
After getting familiar with the D-Bug12 monitor commands, the user can continue to walk
through the following sections.
D.4 Entering an Assembly Program
When a program is first created, we need to open a new file to hold it. To do that, we press
the
File
menu from the AsmIDE window and select
New,
as shown in Figure D.6. After the
New
command is selected from the menu, a popup confirm box as shown in Figure D.7 appears
and asks the user to confirm the request. The user simply clicks on
Yes
to get rid of the popup
confirm box and start to enter a new program.
Search WWH ::
Custom Search