C8051F Simulation Debugging Quick Start (Silicon IDE)

Note: Silicon IDE and Keil software must be installed before downloading the program

Keil installation:
　　Please go to Keil official website:  https://www.keil.com/c51/demo/eval/c51.htm to download and install.

·Silicon IDE installation:
　　Please go to the Silabs official website:  http://www.silabs.com/products/mcu/Pages/SoftwareDownloads.aspx?cm_sp=-_--_- to download and install.

1. Integrate Keil software in Silicon IDE ( click to view )

2. As shown in the figure below, click "Options -> Connection Options" to enter the download mode settings

3. Set the download mode as shown in the figure below. The following figure shows the download/simulation using the C2 interface.

4. As shown in the figure below, click "Debug -> Connect" in the menu bar or press the button in the red circle to connect the software and hardware:

5. Click the button in the red circle as shown below to download the program

Then a progress bar will pop up

6. When the progress bar is completed, it means that the program download is complete, and then it enters the simulation interface, as shown in the figure below

The following is a brief introduction to using Silicon IDE for simulation debugging

Debug Control Bar
The debug control bar can control the execution status of the program. All debug controls can be implemented by menus, shortcut keys and debug toolbar.

1. Connect/Disconnect software and hardware devices (Connect or Disconnect)
This command will start or stop the debugging mode. When in the starting state, all debugging control commands are valid and enter the debugging platform; when in the stopping state, all debugging control commands are invalid and exit the debugging platform.

2. Download code (ALT + F5)
This command will download the program to the microcontroller.

3. Start/Stop Full Speed ​​(Go or Stop) (F5)
The Run command in the debug menu will start (restart) the program. The program will continue to run until it is stopped by the user or a breakpoint is encountered. This command can only be executed when the program is in the stopped state.

4. Step (F11)
The Step command in the debug menu executes only one instruction. If this instruction contains a function call/subroutine call, the function/subroutine will also be executed at the same time. If a user-set breakpoint is encountered in the Step command, the program will be suspended. After the Step command is executed, the information in all windows will be updated.

5. The Multiple
Step command in the debug menu executes multiple instructions. The actual number of instructions is set by the user. If a breakpoint set by the user is encountered in the Multiple Step command, the program will be suspended. After the Multiple Step command is executed, the information in all windows will be updated.

6. Step Over (F10)
The step over command in the debug menu will cause the program to run without entering the subroutine until the current function ends. If a breakpoint set by the user is encountered, the program will be suspended. When the program is in the outermost layer (such as the main function), the step over command is executed at this time, and the program will continue to run until a breakpoint is encountered or it is stopped by the user. After the command is executed, the information in all windows will be updated.

7. Run to breakpoint/cursor (Run To Cursor) (F8)
The Run to breakpoint or cursor command in the debug menu will cause the program to run to the breakpoint in the source code window or the statement indicated by the cursor and stop. If the program never reaches the statement indicated by the cursor, the program will continue to run until it is stopped by the user. When this command ends, the information in all windows will be updated. Since this command is related to the breakpoint or cursor position, it is only valid when the source code window is activated.

8. Insert or Remove Breakpoint (F9)

9. Remove All Breakpoints

a. Enable or Disable Breakpoint

b. Enable or Disable All Breakpoints

c. Open the internal watchpoints dialog box (Watchpoints)

d. Force write data (Refresh Values) (Alt + R)
Write the modified value to the emulator, the register window will reread the emulator, the window will be refreshed, so the changed value will be displayed in red. Note that the register value can only be modified when the debugger is in the stopped state. When the target processor is executing user program code, it is not allowed to be written.

e. Reset (Ctrl + R) 
This command can reset the target program. This command cannot be executed when the program is running. If the user is in source mode, the program will jump back to the first user source code statement after the reset is completed. After the reset command is executed, the information in all windows will be updated.

f. Next bookmark

g. Toggle Bookmark

h. Previous bookmark

i. Delete all bookmarks (Remove bookmark)