|
| Re: Third party mcu develop tech [message #1861565 is a reply to message #1861529] |
Thu, 19 October 2023 06:05  |
 Charlotte Filemdar
Messages: 4
Registered: October 2023 |
Junior Member |
|
|
To use Eclipse to burn in to flash and on-chip debug a RISC-V MCU, you will need to install the Eclipse IDE and the OpenOCD debugger.
Once you have installed Eclipse and OpenOCD, you can create a new Eclipse debug configuration for your RISC-V MCU. To do this, follow these steps:
Open Eclipse and create a new project for your RISC-V MCU.
Right-click on the project and select "Debug As" > "Debug Configurations".
In the Debug Configurations dialog box, click on the "New" button.
Select the "GDB OpenOCD Debugging" debug configuration type.
In the Debug Configuration dialog box, enter the following information:
Name: A name for your debug configuration.
Main: The path to the GNU Debugger (GDB) executable.
Target: The name of your RISC-V MCU.
Configuration: The configuration file for your RISC-V MCU.
Click on the "Debug" button to start the debugging session.
Once the debugging session has started, you can use Eclipse to burn in to flash and on-chip debug your RISC-V MCU.
To burn in to flash, you can use the following steps:
In the Eclipse Debug view, click on the "Download" button.
In the Download dialog box, select the flash file that you want to burn in.
Click on the "Download" button to start the burning process.
To on-chip debug your RISC-V MCU, you can use the following steps:
In the Eclipse Debug view, click on the "Step Over" button to step through your code.
You can also use the other debug buttons, such as "Step Into", "Step Out", and "Run to Line", to debug your code.
You can code the protocol and command for the burning and debugging process in the OpenOCD configuration file. The OpenOCD configuration file is a text file that contains commands that tell OpenOCD how to communicate with your RISC-V MCU.
Here are some specific examples of how to code the protocol and command for the burning and debugging process in the OpenOCD configuration file:
# Burning to flash
transport select hla_swd
interface hla_swd
init
reset halt
flash write_image erase verify .hex
reset run
# On-chip debugging
transport select hla_swd
interface hla_swd
init
reset halt
target name riscv32
monitor reset halt
monitor stepi
You can modify these commands to meet your specific needs.
|
|
|
Powered by
FUDForum. Page generated in 0.03390 seconds
] 
Search
Help
Register
Login
Home
