First, you want to verify that your serial cable is connected to SIO-1 on the development board. This is the default hardware configuration. There are alternate configurations that load in internal or external memory, and use the SIO-0 or SIO-1 ports. Please view the readme.txt file in the C:\Cypress\USB\Target\Monitor directory for information on how to use alternate configurations.
In Keil, check for the following settings by selecting "Project" from the top menu and then "Options for Target 'Target 1'" from the drop down menu:
- 1. In the Debug tab ensure the "Use Keil Monitor-51 Driver" is selected.
2. Click the Settings button and ensure you have the correct COM port selected
3. Ensure that you have the baud rate set to 19200
1. In the Target tab,ensure that you set the Xtal (MHz) setting to 48
2. In the Debug tab ensure that you select "Use Keil Monitor-51 Driver"
3. Click the Settings button and ensure you have the correct COM port selected
4. Ensure that you have the baud rate set to 38,400 IMPORTANT NOTE: The EZ-USB board is always set to run at 24 Mhz, so the baud rate should be set to 19200. The EZ-USB FX board may also be set to run at 24 MHz. In this case, the baud rate should be set to 19200.
For EZ-USB FX and FX2:
The last thing to verify is that after the board completes the power on sequence that the green LED (BKPT/Monitor) illuminates, indicating that the 8051 Keil monitor code loaded and is running.
The default, 64K monitor for the Keil debugger loads automatically at startup for EZ-USB, EZ-USB FX, and EZ-USB FX2 and allows you to use the Keil debugger without explicitly loading the monitor yourself. Alternate configurations may require the monitor to be manually downloaded using the control panel. Please view the readme.txt file in the C:\Cypress\USB\Target\Monitor directory for more information on using alternate configurations.
The SX2 reference desgin uses an EZ-USB FX Development Board as an external master. All monitoring, therefore, occurs on the FX, not the SX2 board. See the documentation for the particular SX2 example you are using for details on how to set up the monitor.
Occasionally, even if you've configured your development environment correctly, you may still get the "Connection to Target" dialog box when you start the debugger. Clicking on "Try Again" two or even three times often will establish the connection.