STMicroelectronics? As usual :-(

Almost two years ago now, I decided to leave STMicroelectronics processors to try other suppliers.

The reason? I don't really like the GUI of the STM32CubeIDE. And then also, the update system was starting to crash. And I don't like it at all.

I, 'unfortunately', intend to use a product from STmicro again for an extended version of my MSX-USB cartridge. Certain characteristics of ST microprocessors are interesting for this project.

So I downloaded and installed the latest version of the software for Windows, namely, Version: 1.14.1. The software installed without problem. : 

Obviously, the problems arose immediately, when I wanted to try a 'Hello World' on a processor from the ST32F722X range.

And yes, the system wants to install the latest version of the package specific to this processor. Obviously, this doesn't go well:

Well, as I think it is preferable, when embarking on a new project, to start with up-to-date resources. I used this legitimacy to attempt the upgrade in 'do it yourself' mode, like lets him suggest the message.

And there, welcome to the world of inconsistencies of all kinds with stupid messages, incoherent since emanating from automatic procedures which do not know what you are doing, given that you are leaving the world step by step programmed, and, as you are a human and you have no idea how this automatic procedure works, you do not know in what precise order to carry out the operations and you therefore do anything.

As a result, with each operation, the 'automatic' procedure makes progress, when something has been presented to it at the right time, without telling you, obviously, but the result still crashes. But, you have moved forward without knowing it. So, you try something you've already tried and this time, it works.

In short, all this because of update files or patches that the automatic procedure does not find when downloading, telling you tersely 'network error', while these files can easily be downloaded 'by hand' from the site of ST.

All, of course, with the crappy ergonomics of Eclipse!

ST: borring as desired.

After a... certain time..., in my case, more than two hours, I finally managed to configure two pins of a processor and start generating the source.

Another stupid thing: you can't generate the source from the processor's graphical configuration interface . 

There's no button for that. No, this is done when you save your configuration. As a result, and as all the source is conditioned by tag type comments where you must insert your code under penalty of future inconsistency between the source and the processor configurator (MX), and if after an error you wish to regenerate the source , well you need to modify a pin to make the backup possible and therefore, at the same time, the regeneration of the source.

Potentially understandable in certain conditions, but in reality, it's completely stupid and annoying.

In short: STmicro!