Initially, VPC application provide the following pin functionality (source code in pascal):
Stories
Perversity
This is such a perversity, that is beyond outrageous! I mean, there is only one way to set the registers and correctly "start the engine" of the controller! That is part of the user manual or documentation that comes with the microcontroller! To declare that foundation code generated by CubeMX to be unarguably their property … Continue reading Perversity
Storing the project
I use XML format for program settings, but for an entire project is too much of a hassle. Typhoon Relational Database System would have been excellent for this job and can be linked "statically" (embedded), but I have it only as a C library and I don't want to pay the price of translating it … Continue reading Storing the project
Moving…
As Github.com is acquired by Microsoft (man, nothing is set in stone these days), I'm moving to Gitlab.com. Which Gitlab is very slow, but it might be because there are many others that move as well. I will keep both locations for awhile, but there is no going back (don't ask, I have my reasons). … Continue reading Moving…
Lazarus versus Qt Creator
Yesterday I took a pause from working to vpc project and fired up Qt Creator to see the progress. It is much easier today to create modal dialog windows than it was when we had only the Qt Designer. It still lacks the features and versatility of pascal visual components but is to be expected, … Continue reading Lazarus versus Qt Creator
Author name – a little bit of dilema…
As every sane IDE and code generator on the face of the Earth, my generator allows the specification of an author and the license of the generated code. Now, this "author field" must be included in the general settings of the application (set once and forget), or must be something you specify on every generated … Continue reading Author name – a little bit of dilema…
Testing tool modified to support SPL
And published to github.com. The tool creates the project's folder structure, copies the SPL driver inside and creates the required files for the Visual Studio Code editor. In general it had the role to clean the rust from my pascal language knowledge. Part of the code will be implemented in my Visual Pin Configurator. Here … Continue reading Testing tool modified to support SPL
Nucleo L152RE Visual Configurator… maybe
Hmm, this should be ok as a name for my code generator and as name says, it will address only one microcontroller and one specific board (maybe Visual Configurator for Nucleo L152RE board?). It will work with the SPL v.1.3.1 from ST Microelectronics for STM32L1xx family in the limits of the license provided with the … Continue reading Nucleo L152RE Visual Configurator… maybe
ll_designer update
I'm switching to SPL libraries and the name of the designer will change in the end. Unfortunately, this means also that the development will slow down. This being said, is time for a little rant:[Rant]You won't see me programming in LL (I dropped HAL once I found LL) anymore. At the date of this article, … Continue reading ll_designer update
Low Layer Designer for Nucleo L152RE
Update 29 March, 2018: Started working at the pinout configuration for the Morpho connector, and clock configuration windows (dialogs). It goes slowly, as there are lots of controls that must be distinctly named and configured (the two right images from the pinout configuration window are just for reference, and will be removed later, and the clock … Continue reading Low Layer Designer for Nucleo L152RE
VPC - Visual Pin Configurator 