[RISC-V MCU CH32V103 Evaluation] 2. Compilation Environment and Routine Import

ddllxxrr

[RISC-V MCU CH32V103 Evaluation] 2. Compilation Environment and Routine Import [Copy link]

 

RISC-V has several advantages over ARM, but the most important one is that it is open source, which means it is free. This is a huge difference from ARM, which charges a licensing fee.

So, why not use MDK to develop RISC-V? The reason is simple: MDK is used to develop ARM architecture. In other words, RISC-V can only be an open source compilation environment.

I am used to MDK, but in order to evaluate RISC-V, I have no choice but to use MOUNRiver Studio. The translation is quite interesting, Shanhe Studio.

In my future evaluation, I will call this environment mountains and rivers.

I also downloaded the sample program, and thought that I could edit the project file by clicking twice. But it didn't work, it was all in the form of a file.

I looked at the PDF file, and there is a section that talks about the steps to start these routines. I combined my own experience and summarized it as follows:

1. Create a new project and remember the path of the project.

2. Open the routine path to be compiled, and copy all the things in USER to USER in the new project. (Completely copy, replace all the previous ones)

3. Select Refresh in the original project, and then open MAIN.c. (I think it is OK not to refresh, after all, the file has changed) and then compile the routine.

I opened the first example of ADC.

The above method is used to compile and download successfully, and then press the key. The following is the running result:

During the download process, it was very fast. I think this development environment is good. I like it.

freebsder

Magic Eclipse, the big guys play with IAR

shzps

I like it, but there are too few chips. I hope Qinheng can develop more chips, which will be a powerful force in China.

zxopenljx

Thanks for sharing