Usually. I chose the complete solution, the one that helps me get the most of it. As is the case with STM32CubeMX + OpenSTM32 IDE + HAL drivers. But HAL does not give me the level of control I was used to, so Low Layer drivers are a very good addition. Unfortunately, OpenSTM32 does not offer … Continue reading Crossroads without signs…
Stories
A new morning shines at the horizon
Finally, the STM32CubeMX can generate Low Layer code for all STM32 microcontrollers! Thank you ST Microelectronics!I have taken an active pause, continuing with PIC18F microcontrollers, SDCC and XC8 compilers. Translating the library and examples for the DS18B20 temperature sensor, but these are yet to be committed in their repositories. I also tried to make an … Continue reading A new morning shines at the horizon
Your map may be old and you’ll get lost
The actual version of the HAL drivers in OpenSTM32 IDE for my board is 1.6.0 and the last official ST version is 1.7.0. So, I thought I may update it myself, how hard may be that (I had to do it anyway, as I did the upgrade also for STM32CubeMX)? And I did it, replacing … Continue reading Your map may be old and you’ll get lost
Preparing the trap for time…
Update May 12, 2017: The HAL libraries regarding I2C peripheral are just stupid! Their unneeded "simplification" gives me headaches. I'm not a newbie, you know? Well, more likely I'll use the HAL Low Layer drivers for this one...It seems that the mixed use is allowed (Chapter 4 of "Description of STM32L1 HAL and Low-layer drivers")Original … Continue reading Preparing the trap for time…
The wire has fever!
Yep! The onewire and DS18B20 libraries are ready. Built on top of the HAL layer, I was afraid that the timing won't be right... my tiredness added to that and I didn't observed that the bus is connected to a wrong wire on Nucleo board, making me to do some major changes in the source. … Continue reading The wire has fever!
Standard is better…
Code size wise, using only the Standard Libraries, you get an advantage of around 3Kb in size, compared with the HAL Libraries. Disadvantages? You lose the fast prototyping features (and the sense of security) offered by the STM32CubeMX.Well, that is not a problem for the advanced programmer, but I, as a beginner, I will work … Continue reading Standard is better…
Staring at the display
After adding a conversion library and porting the LCD library from c18lib project, and adjusting the microseconds delay, I have a functional example. When you set the pins as outputs on the STM32CubeMX graphic configurator, you must rename them as follows: LCD_D7, LCD_D6, LCD_D5, LCD_D4, LCD_E, LCD_RS. Otherwise, the library will set her own default … Continue reading Staring at the display
One char after another…
I started the work to onewire library, to test the DS18B20 temperature sensor but realized that I don't know yet how to work with the serial transmission :(. So, I opened the STM32CubeMX for the configuration of a new project that will use the main serial port of the Arduino socket (on my Nucleo board, … Continue reading One char after another…
Without microseconds, you’re just an outsider
As it is, the HAL library comes with a tick at every 1 millisecond, like a "millis" in an Arduino library. It is your application's timer, allowing you to plan timed, non-blocking tasks, like in a real-time operating system. But no microsecond delay function provided 😦 . And you know, many initialization procedures or protocols … Continue reading Without microseconds, you’re just an outsider
In the blink of an … LED
I strongly desired to enter 32bit arm microcontroller world with Atmels' SAM-D21 (Cortex-M0+) microcontroller, but the Arduino Zero board came very late and expensive... then Atmel was acquired and... And STM32 it was! In form of the Nucleo board which I see it much over Arduino Zero in terms of features, and four times cheaper!So, … Continue reading In the blink of an … LED
VPC - Visual Pin Configurator 