CubeMX under linux in couple with System Workbench for Stm32

Yes, it really happened! During update of CubeMX, I've glanced on list of changes, and not believed to my eyes: ST released linux version. Time to try this stuff and get opinion on it.
First of all, CubeMX under linux:


Nothing extremely special, for the first glance everything works fine. Finally, they added support of codegeneration of generic GCC environment. I've generated test project for my F3Discovery board for SystemWorkbench for stm32 IDE.

And if CubeMX have not shown any issues for this time, IDE showed a lot of them:( As always on linux... Really, I LOVE LINUX, but I hate these crude solutions in contrast of windows. (Actually, system workbench on windows also is buggy too, and this compelled me currently work in IAR which is ugliest IDE in the world. But IAR works PREDICTABLE and it is key factor).

Step 1. 
Ok, what I get when I run IDE at the first time and tried to debug my board. Error...

Could not determine GDB version using command:
/home/artsin/bin/SystemWorkbench/plugins/fr.ac6.mcu.externaltools.arm-none.linux64_1.3.0.201507241112/tools/compiler/bin/arm-none-eabi-gdb
--version

/home/artsin/bin/SystemWorkbench/plugins/fr.ac6.mcu.externaltools.arm-none.linux64_1.3.0.201507241112/tools/compiler/bin/arm-none-eabi-gdb:
error while loading shared libraries: libncurses.so.5: cannot open
shared object file: No such file or directory
What was wrong? libncurses, but not just it, and 64-bit version. Solution:


sudo apt-get install lib32ncurses5
Step 2.
Ok, move forvard. Next iteration - next error. Now when we tried to debug on 
our board. We got window with error like this:

Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: timed out
localhost:3333: timed out

I cannot remember full error, but it is concerned to openocd debugger. Really,attempt to run manually it showed this:

artsin@artsin-K53SJ:~$
/home/artsin/bin/SystemWorkbench/plugins/fr.ac6.mcu.externaltools.openocd.linux64_1.7.0.201602121841/tools/openocd/bin/openocd
-f stm32f3discovery.cfg -s
/home/artsin/bin/SystemWorkbench/plugins/fr.ac6.mcu.debug_1.7.0.201602121829/resources/openocd/scripts/st_board
-s
/home/artsin/bin/SystemWorkbench/plugins/fr.ac6.mcu.debug_1.7.0.201602121829/resources/openocd/scripts
-c gdb_port 3333

Open
On-Chip Debugger 0.9.0-dev-dirty (2015-11-13-11:40)

Licensed under GNU GPL
v2

For
bug reports, read

   
http://openocd.org/doc/doxygen/bugs.html

Info : auto-selecting first
available session transport "hla_swd". To override
use 'transport select <transport>'.

adapter speed: 1000
kHz

adapter_nsrst_delay: 100

Info : The selected transport
took over low-level target control. The results might differ compared
to plain JTAG/SWD

srst_only separate srst_nogate srst_open_drain
connect_assert_srst

srst_only separate srst_nogate srst_open_drain
connect_assert_srst

3333

Info : Unable to match requested speed 1000 kHz,
using 950 kHz

Info : Unable to match requested speed 1000 kHz,
using 950 kHz

Info : clock speed 950 kHz

Error: libusb_open() failed with
LIBUSB_ERROR_ACCESS

Error: open failed

in procedure 'init'


in
procedure 'ocd_bouncer'
Solution I've found here:

 
“For the JTAG probes implemented as USB devices (actually most of them), the last installation step on GNU/Linux is to configure the UDEV subsystem. OpenOCD provides an UDEV rules file defining all the supported IDs; to install it, just copy the file to /etc/udev/rules.d and eventually notify the daemon:


$ sudo cp /opt/gnuarmeclipse/openocd/0.10.0-201510281129-dev/contrib/99-openocd.rules \
 /etc/udev/rules.d/
$ sudo udevadm control --reload-rules
Note: If you previously installed the J-Link binaries, the USB IDs were already added to UDEV. The above OpenOCD rules file also defines the J-Link ID. Apparently UDEV does not complain; if you encounter problems, just comment out the definition in the OpenOCD file.
“
 But for cp command I've used path to file 
99-openocd.rules located in SystemWorkbench directory (just search it in 
your installation path)

After this magic I've got first complete test debugging. And what bugs waiting for me again - I do not know:)

Comments

  1. BernardFebruary 14, 2016 at 4:19 PM

    Hi,

    Thanks for the heads up about libncurses5 for 32 bit executables; this is due to the fact that several utilities we do not want to recompile (for reliability reasons, especially the compiler itself that is heavily tested by Linaro) are only available as 32-bit executables.

    I thought the warning was present in the installation instructions, but discover it was missing and I just correct them.

    As far as the udev rules are concerned, if you install System Workbench using th einstaller, these rules are automatically installed (after asking for your password through gksudo if installing as a normal user). If you install manually in an existing Eclipse platform the procedure to install the rules file is described (and the proper rules file is provided as a tarball).

    Thanks for your posts about System Workbench,

    Bernard (Ac6)

    ReplyDelete
    Replies
    1. Artyom SinitsinFebruary 15, 2016 at 3:59 AM

      Hello, Bernard! Thank you for your attention to my little blog:) One clarification about your udev rules. stuarte83 and Antony(and me too) at OpenStm32 forum faced with problem with udev. I do not remember my error during installation, but Stuarte wrote his issue:
      Starting process Loading STLink/V2 udev rules (3/3)
      cp: cannot stat ‘49-stlinkv2.rules’: No such file or directory
      I fix my issue by copying 99-openocd.rules, not 49-stlinkv2.rules file. Is this file present in your installation script? Unfortunately, I cannot check your installation script now, but it is possible, that reason is in availability and path to udev rules file.

      Delete

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