System Workbench STM32 + CubeMX: cookbook

God have came from heaven and finally partially finished our BIG problem! What? What is a problem???
Yes, problem is called "IAR, KEIL - so ugly IDE's, and where is good open source IDE?":)
I always wants free, open source IDE for STM32, multi platform with blackjack and yohoho!
Why I said that solution is partial? Because now we have free open source IDE, and proposed IDE is Eclipse,frankly speaking it is not best from IDE's, but, as said "there's no choice among stinking fish" :)

Anyway, now we have new toolchain, which must work "from the box". It's name is "System Workbench for STM32", you can download it from http://www.openstm32.org site, you just need to register and spend a little time to find download link on the site.
Now, another good news is that CubeMX can generate project for this toolchain. But, currently(and I hope situation will change to the best), there are bugs in procedure of importing generated project to eclipse environment.
Up to today(May 21 2015), procedure is like this(from openstm32.org forum, I've just added some comments and images)

You should

  • Create a new workspace (empty folder named, for example, myWS)
  • Generate CubeMX code in a subdirectory of this folder (that is in myWS\myPROJECT)

  • Open System Workbench for STM32, using myWSas workspace. The project explorer will be empty
  • Import the CubeMX-generated project:
  • File >> Import...
  • General >> Existing Projects into Workspace >> Next
  • Browse (should automatically select myWS). It should show just one project, named "myPROJECT Configuration", automatically selected
  • Click "Finish"

Now you have a working project; however there is a small potential problem: Your project is called "myPROJECT Configuration", and a name with a space in it is, at least, a burden (especially on Linux but also on Windows). So you should probably:

    Rename the generated files
  • Right click on project >> Properties
  • C/C++ Build >> Settings >>; Build Artifact
  • Suppress " Configuration" from the artifact name

OK
    Do not rename your project 
Eclipse seems to break all linked resources pointing to project-relative paths when the project is renamed...

Then you should have a working project that can be compiled correctly. However, the CubeMX-generated project do not include a board description with debug connection information: kind of MCU, debug probe, debug link. You thus can't debug as simply as usually.

One solution may be to create a debug configuration then select your debug script manually by:
  • Debug As >> Debug Configurations...
  • Create a Ac6 STM32 Debugging configuration
  • Choose your project and executable (if needed)
  • Select the Debugger tab
  • If there is a NO SCRIPT FOUND red error message (most surely currently) select the "Use local script" redio button
  • Provide a debug script by one of three means:
    • Browse to your System Workbench install directory, then plugins\fr.ac6.mcu.debug_1.1.0.201503121050\resources\openocd\scripts\board and look for the script for your board (you may find also some st-specific scripts in st_board)This is usually the way to use for a standard ST board (eval, disco or nucleo)
    • Manually search for a close board in the directory above then manually copy it to your project main directory, then browse to it and select it. This is usually a good way to go for a custom board that is very close to an ST board (often an EVAL board), including the same debug interface.
    • Get a custom board debug script created when creating a project using your custom board (may be a no-firmware project with an empty main program). You just have to copy the System Workbench-generated debug script in your project and browse to it.    This is usually convenient if you define your own board, create a custom board in a System Workbench-generated test project and want to reuse it in your CubeMX-generated project

Once your configuration is working, you can launch it by using the small "bug" button in the top toolbar (either click it directly or use the small arrow on its right to see the last valid debug configurations used). 
Why everything is so complex? Actually, I do not know, but anyway, this is very buggy solution, and I hope, that ST's developers fix all this issues ASAP!

Comments

Post a Comment

Popular posts from this blog

u8g2 library usage with STM32 MCU

Image
Several years ago I wrote couple of articles about beautiful library u8glib in context of STM32 microcontrollers. Time moves on and author of this library released newer one, u8g2. u8glib is officially deprecated and not developed anymore. We cannot afford to lose code support for our libraries, time to move to newer library! Differences between these libraries are listed there, also there are a lot of helpful information about u8g2 library. It is not so hard to modify your old u8glib code for newer library. I'll show you how to use this library with Nucleo-F401 board and SSD1306 display, bought on Aliexpress. Display connection is SPI, pins are GND, VCC, SCL(the same as SPI clock), SDA(the same as MOSI), RES and DC. Wiring is: PA5 -> SCL PA7 -> SDA PA9 -> OLED_RES PC7 -> OLED_DC I use CubeMX code generation tool to initialize all the peripheral.  OLED_RES and OLED_DC is just GPIO output. SPI1 initialized with default parameters. u8g2 library has it
Read more

Use PCM5102 with STM32

Image
Use PCM5102 with STM32 PCM5102 and STM32 Here are my tiny notes about the connection of PCM5102 DAC to STM32F401 Nucleo board. I2S interface requires three wires to work: SCK is officially called as “continuous serial clock (SCK)”, but also you can found “bit clock” name. It is just the same clock as usual in the SPI interface. Word Select clock is used to select, which cannel is active now, 0 for left channel, 1 for right. It also called called “left-right clock (LRCLK)” or “frame sync (FS)”. Serial data - actual data. CubeMX settings Wiring diagram My board has such pins: | 3.3V | 3.3V on Nucleo board | | FLT | Filter select, grounded: select normal latency, grounded | | DMP | De-emphasis control, grounded(OFF) | | SCL | System clock input, in datasheet SCK pin. System clock is internally generated, it should not be wired anywhere | | BCK | Audio data bit clock input. In I2S terminology is equivalent to serial clock(SCK) I've connected i
Read more

RFFT in CMSIS DSP. Part 1.

Image
RFFT in CMSIS DSP. Part 1. RFFT in STM32 using CMSIS DSP. Part 1. Python warm-up for illustration I always wanted to use MCU for audio processing. And for my purposes, I need Discrete Fourier Transform(DFT), especially its fast version FFT. If you do not know what is this, read Wikipedia first:) FFT has a huge number examples of usage, for my case I want to build wavetable synthesizer. Let’s take some real example. We have an audio signal, which is just a set of amplitudes, which you will take from your ADC. Samples are taken with some sampling frequency Fs. For preliminary illustration, we’ll use Python. import numpy as np import matplotlib . pyplot as plt # Our wave settings N_samples = 32 amplitude = 10 # Here we'll generate our sine wave t = np . arange ( N_samples ) x = amplitude * np . sin ( 2 * np . pi * t / N_samples ) # Plotting fig , ax = plt . subplots ( ) ax . plot ( t , x , 'bo-' ) ax . set_xlabel ( 'N sa
Read more