Associate III

Solved

Programming STM32 only with CMSIS.

Forum|Forum|6 years ago
May 18, 2020
14 replies
5149 views

Hi,

I would like to start using my discovery board STM32F0308 without HAL library.

Where should I start?

Now I use CubeMX to generate Makefile but I would like to write this on my own, linker script and startup too.

Shall I ask another question about programming only with using CMSIS?

I'm tired of reading this tones of lines without understanding, I prefer bare-metal programming with registers.

tl dr section;

I want to just use text editor and command line to program and debug STM32s.

STM32F0 series

This topic has been closed for replies.

Best answer by waclawek.jan

> I want to just use text editor and command line to program and debug STM32s.

You'll need also a PDF reader. And I strongly recommend Total Commander or equivalent.

I have some barebones progamming examples on efton.sk/STM32 . You probably have some gcc binary from the Cube bundles or the eclipsoids, or get one from ARM. For simple projects, I avoid using make as it's an added hassle which pays off only with moderately large to huge projects - I simply call gcc from a batch file.

Then you have to download your code to target. There's many ways to skin the cat - you can avoid the debugger "pods" like STLink or JLink and use the built-in bootloader in some form, but I'm not sure about the details. Or use e.g. STLink, it comes with the STLink Utilities (or its Cube form) both in windowy and command-line form.

You can then debug using oldfashioned (but in no way unusable) methods - LED blinking, wiggling a pin observed by oscilloscope or LA, using debug printouts (and I'd recommend you to avoid printf() and family for the barebones experience, alleviating you from the associated problems - write your own simple print routines) through some serial channel or any other means.

Or, if you want to use the on-chip debug interface, you probably go for gdb with some suitable server (usually openocd) attaching to the debugging "pod" (e.g. STLink). I'm not very versed in this - I can get this going for myself, but won't offer guidance.

Which one from these items you'd want to elaborate on further? (I'm not offering more help, but knowing your exact standpoint may help others who'd want to help you).

JW

PS. Oh, and what TDK said above... Absolutely yes, you should start with the simplest loopdelay blinky and evolve from that.

TDK

Start with a simple task, and try to do that. Change clock settings. Blink an LED. Whatever. Get used to reading the reference manual and understanding what the various registers do.

Hard to answer "How do I X?" when X is undefined. Don't want to use HAL? Simple, just don't #include any HAL files. CubeMX is going to generate code with HAL/LL. That's what it does. You will need to generate your own code.

"If you feel a post has answered your question, please click ""Accept as Solution""."

dnjAuthor

Associate III

Then to not to dive in deep water at first I make CubeMX project and just don't use HAL library. I only let MX do linker, startup etc. stuff.

Thanks

waclawek.janBest answer

Super User

> I want to just use text editor and command line to program and debug STM32s.

You'll need also a PDF reader. And I strongly recommend Total Commander or equivalent.

I have some barebones progamming examples on efton.sk/STM32 . You probably have some gcc binary from the Cube bundles or the eclipsoids, or get one from ARM. For simple projects, I avoid using make as it's an added hassle which pays off only with moderately large to huge projects - I simply call gcc from a batch file.

Then you have to download your code to target. There's many ways to skin the cat - you can avoid the debugger "pods" like STLink or JLink and use the built-in bootloader in some form, but I'm not sure about the details. Or use e.g. STLink, it comes with the STLink Utilities (or its Cube form) both in windowy and command-line form.

You can then debug using oldfashioned (but in no way unusable) methods - LED blinking, wiggling a pin observed by oscilloscope or LA, using debug printouts (and I'd recommend you to avoid printf() and family for the barebones experience, alleviating you from the associated problems - write your own simple print routines) through some serial channel or any other means.

Or, if you want to use the on-chip debug interface, you probably go for gdb with some suitable server (usually openocd) attaching to the debugging "pod" (e.g. STLink). I'm not very versed in this - I can get this going for myself, but won't offer guidance.

Which one from these items you'd want to elaborate on further? (I'm not offering more help, but knowing your exact standpoint may help others who'd want to help you).

JW

PS. Oh, and what TDK said above... Absolutely yes, you should start with the simplest loopdelay blinky and evolve from that.

dnjAuthor

Associate III

I think I introduced myself wrong. I'm embedded dev but I always use HAL or prepared by someone project in other IDE and then I'm frustrated I don't know how it works... but guys I'll take your advice and try to separate from "automagic" tools step by step.;)

waclawek.jan

Super User

> As I see you generated linker and startup file with Attolic (I mean blinky at your site EFTON).

Generated? No, I've simply stolen them from the templates in SPL or Cube (depending on the age of that example).

JW

waclawek.jan

Super User

i.e. from places like

https://github.com/STMicroelectronics/STM32CubeF0/tree/master/Drivers/CMSIS/Device/ST/STM32F0xx/Source/Templates/gcc

and

https://github.com/STMicroelectronics/STM32CubeF0/blob/master/Projects/STM32F030R8-Nucleo/Examples/GPIO/GPIO_IOToggle/SW4STM32/STM32F030R8-Nucleo/STM32F030R8Tx_FLASH.ld

I never had CubeMX installed (I had MicroXplorer installed, though - that was the predecessor of CubeMX).

JW

dnjAuthor

Associate III

> For simple projects, I avoid using make as it's an added hassle which pays off only with moderately large to huge projects - I simply call gcc from a batch file

Ok then, how you know how to enquire above files (startup and linker script) in compilation.

I think I can take them from Makefile prepared from CubeMX, but I'm curious how you did it.

Could you show me your batch file for compilation? Maybe there are some usefull comments.

dnjAuthor

Associate III

Ouch i see those .bat files =)

Could you tell me what does it mean in c.bat file?

%2 %3 %4 %5 %6 %7 %8 %9

waclawek.jan

Super User

Well, MSDOS education is not widespread these days, I reckon... =)

%1..%9 replicate the input parameters given to the.bat file. In this way, I can add additional command-line ad-hoc, by writing them as parameter to the bat file when running it from command line (the first parameter is the .c source file name, without the .c extension)

No magic there, and zero sophistication.

JW

dnjAuthor

Associate III

Yeah I check this just now, sorry.

I'm curious how you debug this code?

Do you use this .lss file?

waclawek.jan

Super User

That, too.

I also do staring at the code. And I explain it to the teddy bear.

I spend a lot of paper making various drawings, remarks, diagrams...

Debugging is a multi-facet process, the more tools you have at hand the better. The on-chip debugger makes life a lot, A LOT easier, but relying on it as the ultimate debugging tool is extremely short-sighted.

See my first post above.

JW

dnjAuthor

Associate III

I did it. Well I wrote few simple functions only with linker script and startup file. Thank you :)

dnjAuthor

Associate III

Is there a way to close/mark as resolved?

Sign up

Click below to sign in

Login to the community

Click below to sign in