STM32 Roadmap?

[harerod]

I have been designing solutions around STM32 for over 15 years, right from the F103 days. The most complex projects have been with F4, simpler applications with F1, F0, Lx, Gx, etc..
As a result of the ongoing Chipageddon situation, most silicon manufacturers have lost my faith. Since my clients and I have put a huge investment into the STM32 family, I am really concerned about how ST is going to proceed with that family. A quick online search for "STM32 roadmap" didn't bring any enlightenment. The "10 year guarantee" is of not much use, when it comes to a F407. At this point and being a simple freelance engineer, I don't expect a useful answer from ST, should I address them directly.

https://www.st.com/en/microcontrollers-microprocessors/stm32-32-bit-arm-cortex-mcus.html

Question: is there any information out there, regarding which way ST is going to develop the STM32 family? What devices should one use for the next redesign?
At the moment the F407 from the "High Performance"-range would be my biggest concern, simple because of the code complexity. At the same time I am also interested in "Mainstream"-range items. During Chipageddon we already did several redesigns to keep things going with the devices that we could procure. E.g. replacing F407 with smaller FLASH versions, or replacing F1 with any small, slow and buggy A-revision Gx's that we could scratch from the bottom of the barrel.

I am aware of STM32 clones and other ARM MCU's. Let's stick to genuine ST in this thread, please.

[Sacodepatatas]

I expect them answering to this question on tomorrow's event.

https://content.st.com/stm32-innovation-live.html

[mark03]

So the deadline is past, and although I don't have time to sit through a 1.5-hour video, I did take a look at the STM32 product page and tried a google news search for "stm32" and I don't see much in the way of new MCU development.  (The new MPUs are interesting to some, I guess.)

Still no Cortex M55 or M85 parts with the Helium SIMD.  Nothing with neural coprocess (Ethos).  Nothing exciting on the process front either (anyone remember FDSOI?).  No foray into RISC-V either.  I would need at least one of those to pique my interest.

Everyone knows there is a long lag time between ARM's announcement of new cores and real silicon, but if
you compare with Cortex M7, this has already been a longer wait than normal---the M55 was unveiled more than three years ago, and there are still not even vaporware new-product announcements from ST.

That being said, they promised an update on the supply situation... Did anyone tune in to hear what they had to say?  Just being able to buy parts from their current product line would be fantastic in the near term.  But IMO a lack of new products in the pipeline bodes ill for the future.

[peter-h]

Looking at chips I have used over past 30 years, I reckon the 32F407/417 will be in production for another 15-20 years.

ST is in a similar ballpark to Hitachi (now Renesas). Once they get loads of design-ins they tend to keep making the parts. H8/3xx had a 25 year production run and I'd say the 32F4 has had more design-ins. Even in the heyday of sales engineers, Hitachi offered almost no help at all. Painfully, one could extract information on stuff not in the data books.

And then ST will chop some package options, narrowing it down to some tiny BGA package.

These 168MHz-180MHz chips deliver 10x the power of previous generations, which is nice, and necessary for stuff like USB and ETH. The later ones might do 500MHz internally but they risk getting too far ahead of market demand. The applications that need that are far fewer, and you have to charge more for the chips to maintain product spectrum differentiation; this is a key marketing requirement even if it is completely bogus in terms of production costs.

And at the same time you don't want to drop prices on the older chips because nowadays that is a real no-no. The name of the game is shafting everybody who is not big enough to not get shafted. That in turn limits how much you can charge for the later chips.

IMHO the most important thing is to avoid brands which drop parts faster than a whore's knickers - like Atmel

[AVI-crak]

In Russia, everything is very simple - there are simply no ST products.
We use everything that can be used, even very strange and scary solutions. The main purchase opportunity.

[SiliconWizard]

In Russia, everything is very simple - there are simply no ST products.
We use everything that can be used, even very strange and scary solutions. The main purchase opportunity.

What kind of MCUs do you use?
I have seen some russian MCUs, but mostly hardened/stuff for aerospace applications.
I guess you otherwise have access to chinese MCUs with not much difficulties.

[peter-h]

Building cruise missiles and such, you don't need anything beyond a chinese ripoff of a 32F407 The challenges are inertial nav (for where GPS is being messed with) and hi res IR (thermal) sensors, and all that stuff is ITAR.

[Boscoe]

I am too keen to understand where ST is going and id love to be a fly on their wall when it comes to addressing how their company will move forward considering the dent in their reputation - their fault or not.

I moved over to ESP32 for a couple of reasons however sourceability being the main one. The IDF tool chain is light years ahead of the ST offering.

I personally think that MCU companies should drastically reduce their product lines and invest that RnD into tool chain and support. If you had ~15 key products with differing cores, speeds, memories and packages and epic tooling you’d have a winning offering IMHO.

[uer166]

The most interesting series on roadmap are the Stellar MCUs, the first engineering samples are hard to come by though. 6 Cortex-R cores, where you can run different combination of lockstep, checker cores, etc. NEON and all the bells and whistles as well.
https://www.st.com/en/automotive-microcontrollers/sr6g7c4.html

I don't understand the "they don't have anything on the roadmap", these are probably the most complex, feature packed, and FMEA'd CPU/MCUs they've ever made, and are well tailored to power electronics and all kinds of automotive stuff.

[AVI-crak]

What kind of MCUs do you use?

Everything that can swing its paws, well, except for very ancient solutions. Direction - industrial automation. Many products have become inaccessible and too expensive, even Chinese ones. You have to invent your own.

[Sacodepatatas]

I expect them answering to this question on tomorrow's event.

https://content.st.com/stm32-innovation-live.html

Summarizing...

-They Will focus on two families, the entry level STM32C0 for replacing the legacy STM8S designs, something weird as these aren't pin compatible with the later  (and, in my opinion, it's a horrible nomenclature change, the "C" reminds me the time when regular 8-bit MCUs and EPROMs were OTP or Factory masked. A "Z" series would have rocked instead). And they'll stick developing for the STM32H5 family. For STM32F0/1/2/3/4, no dead line in a short term, but no further development of these cores. For entry level, they promote switching among C0 and G0 families depending upon the need of features (quite obvious though).

-For high end MPUs of the STM32MP1 family the're strongly focusing on hardening IP security and trust level so their top MPUs have obtained several certifications (I don't remember which ones).

-They keep holding the 10yr commitment for new design lines.

-They are releasing a new ST-Link V3 extended with power metering and analyzing capabilities.

-They might have reach some agreement with Microsoft because they are going to follow the line of development integrating their ecosystem with VScode and AzureRTOS. They will continue developing the STM32CubeIDE, but this is not their priority right now.

-And that's what I have got in clear from the yesterday's meeting. Oh, one more thing left: they are very happy to anounce that they have reached agreements with their foundry parners (I guess that they refer to TSMC) so they consider the chip shortage something from the past, but It looks more like a promise than a matter of fact.

[harerod]

@Sacodepatatas (ger. Kartoffelsack),
thank you for the write-up. The part regarding the F-family fits my misgivings pretty well.
Instead of giving dates, we hear that a foundry is actually signalling willingness to manufacture devices in the future. We have also heard that ST got new major customers that require huge amounts of silicon. We can assume that the first production runs will go towards those.
Without further input, my recommendation to clients who require long time availability:
- for existing products: keep checking the distribution channels for eventual availability of STM32 devices. Move F4-designs to feature compatible devices
- keep in mind who gave the best support to small clients during Chipageddon. In my personal experience, Microchip sales/support made outstanding efforts to keep us supplied. ADI, ST, TI, only to name a few, have a lot of image reconstruction work ahead of them   
- in the past we used weaker STM32 to replace 8-bitters, simply to use one IDE for all projects. Now I can see us moving back to AVR/PIC, just to reduce the dependence on ST

[Debugging]

The Webinar was interesting because it kicked off talking about the expansion of capacity. the availability of STM MCU has been a pain for very long.
It was like apologizing for the shortages to keep the cold heart of (small) consumers warm that supply is coming....  It may be just a little too late.... We all know the big consumer have
booked all the supply from the fabs keeping no allocations left for retail . This is easy to see as in retail you find that if order K's of MCU's you get reduced leadtimes from 6 months to a year or more. that is not the strategy of Mouser, Digikey, That is the attitude of STM, NXP and all the big MCU brands and that may have backfired for smaller companies that are now switching or have already switched over to other MCU's. some brands have chosen ther priorities and are killing SMB's, some smart brands are focusing  to take their place in that market segment.

Low lights:

- No STM32MP15 with 4 lanes MIPI  display interface
- The STMH5 series is based on single core M33 and not M55. It misses out on DSP instructions and graphics like the H7 has.  Memory is limited to 640K.
   Hopefully they will release a higher end H5 with those features. it seems something between an F/G and the H7 but with higher clock speed.
   A good reason to stay with the H7. M33 is already 7 years old.
- No mention if the the improvement made for MP13 (see below) will also apply for MP15.
- Select speakers with better English.

Here are my notes:

- Supply :  300mm expansion on site (France?), Italy 300mm fan ramp facility, Plans for 400m plans (if I did hear correctly), Capacity increase will happen from now till 2025
- STM32MP13(5) < $4.  Tj=125C, Cortex A7  1Ghz, Low power standby, 4 layer TH templates, Yocto Real time OS as alt to embedded Linux, LinuxRT Factory automation
  AzureRTOS , Bare metal control, Side channel., Root Of Trust, Armz trustzone,  Obtain SESIP level 3,
- STM32H5 adds I3C interface, 2MB Dual Flash , 640KB MAX
- Integration with VSCODE (NXP announced the same for IMXRT)
- WB1MMC BLE  FCC/CE/Anatel precertified. can use Internal antenna and  external antenna
- Cube.AI Developer Cloud
- STM32WBA  BTLE100mhz 407 stone marks BLE 5.3 SESIP 3 + 10dBA gain. Support isochronous mode transmission and LC3 codec
- Several product support SESIP Security Evaluation Standard for IoT Platforms）
- CubeIDE SecureManager - iROT / PSA SESIP 3, PSA API with  SMDK Secure Management Development Kit

Hopefully they don't go into too deep in the love boat with Microsoft because  Micorsoft is dropping Linux support everwhere due to their new GUI engine. Teams is also victim of that and when that continues the STM IDE may loose Linux support ? Hope not.

P.S: A 10 years guarantee does not mean much when parts have soon been 5 years out of stock and with the forecast we may only see there whole situation recovered by 2025..

[MT]

and F429 are 12 years later still manufactured but sold at silly high prices and errata sheet at Rev19 and counting.

[harerod]

...
Hopefully they don't go into too deep in the love boat with Microsoft because  Micorsoft is dropping Linux support everwhere due to their new GUI engine. Teams is also victim of that and when that continues the STM IDE may loose Linux support ? Hope not.
...

Dropping Eclipse and replacing it by anything Microsoft would be serious bad news for all of us who are dedicated to long time support. I'd rather go through yet another "refactoring" of the libs than seeing that happen.

The availability issue extents to other ST products, which also require fab capacity.   
Heck, it seems that ST are hell-bent on killing all arguments in favor of sticking with them. Maybe it is time to accept that small businesses are not their target audience.

[peter-h]

They will continue developing the STM32CubeIDE, but this is not their priority right now.

I have not noticed "development" over past 2 years, other than adding support for new chips.

Maybe it is time to accept that small businesses are not their target audience.

They never were anybody's target audience. Not since I started in this business in 1978.

Select speakers with better English.

I gave up on their videos partly due to this. What country are they made in? There are a couple of places where not speaking English is "culturally mandatory"

[SiliconWizard]

The newer STM32U5 series looks also pretty cool.

Not very fond of the love affair with MS. But we know how MS can be extremely commercially agressive, so "resisting" MS is probably tough shit, especially if you want to expand your IoT market.

[peter-h]

I know nothing about MS VC++ (I pay people on freelancer.com to write apps in it) but I understand that some people have used that IDE for STM chips. Cube IDE is after all not much more than an editor and a makefile generator. How one runs a debugger under VC++ I have no idea but perhaps the clunky Segger ones with the 1970s user interface will run OK.

Obviously as "Cube IDE" only, not Cube MX (which all seasoned programmers seem to hate anyway, but is handy for getting the ST devkit to flash an LED).

Cube IDE getting killed off would not worry programmers working for themselves but it would be a hassle if more than one person is generating code for a project, especially over a long time.

[Sacodepatatas]

Select speakers with better English.

I can't talk with much authority about that, but, the french lady looked too much hot for me to become aware of her speech fluency...

If I can recall properly, when in the Q/A section, somebody asked if there was any H5 (or U5, don't remember exactly) with GPU capabilities, and the answer was  "no" because such family was oriented for industrial environment and not for graphics...

[peter-h]

Where is this video?

Looking back to electronics engineers I knew since univ, all the univ dropouts ended up being sales engineers. But they were way more successful with "night life" than us real engineers

New ST products will be driven largely by large OEM requirements.

[hans]

To be honest I'm a bit confused by ST's new MCUs.

The STM32F103, STM32F207 and STM32F407 were classics that made pavement for a lot of the other MCU models. The F42x series added SDRAM and LCD support, the F446 had QuadSPI memory expansion, and then later the F7 and H7 models were introduced with Cortex-m7, more memory, SDMMC, etc. Some of these chips (in particular F7) had very similar peripherals to the F446 chips. Then ST has sort-of aa 2nd gen of MCUs in the H7 family that introduced a new memory controller e.g. OctoSPI, which follows up on quad SPI so you can utilize dual-bank FLASH and/or even HyperRAM. The U5 MCU also has this memory controller, and it's great if you want to run code from external memory. The QuadSPI FLASH controller can have a random read latency of up to 430ns on a L1 cache miss, which is an eternity (93 cycles @ 216MHz)

That's all great: but meanwhile, they were also able to maintain other useful peripherals of the F4 family. For example, the F4 family has USB OTG FS+Phy and OTG HS+ULPI, which can be useful for high bandwidth PC applications. The U575, G4 and H5 series seem to have left these peripherals out and only includes a "USB FS host and device" peripheral. So I wonder: why a step backwards?
All these chips are on a better level of speed/memory as the original F207/407 chip, so I don't see why these chips wouldn't be able to carry USB HS data. Maybe it's an IP licensing issue, maybe a low customer demand issue, but I find it confusing that they have omitted this peripheral for 3-ish new generations in a row. I do see they list USB HS on the newer U59x chips, which is great, but still makes me wonder why they fragment their U5 lineup with only USB FS on the U575.. If anything I'd make a guess it makes more sense to consolidate several variants to the same die design, so they can be sold from the same wafers.

Ah well, can't complain and probably will never know. I never viewed ST's MCU as especially focused on 1 area, such as industrial, which IMO is a key ingredient to their widespread adoption. I think that with their mainstream line-up listing "ALL" option boxes was a great strategy. E.g. I once tried to design with a Microchip/Atmel Cortex-m7 chip, and was purely shocked that a 300MHz 100QFP device would only have 2 SPI interfaces

[5U4GB]

Building cruise missiles and such, you don't need anything beyond a chinese ripoff of a 32F407

Friend of mine has done some analysis of various STM32 clones/fakes.  Trust me, you really don't ever need one of those.

Your competitors OTOH...

[GromBeestje]

Building cruise missiles and such, you don't need anything beyond a chinese ripoff of a 32F407

Friend of mine has done some analysis of various STM32 clones/fakes.  Trust me, you really don't ever need one of those.

Your competitors OTOH...

I looked into F103 clones myself, back in 2019, and I am about to have another look.
Does your friend have a blog or somewhere they share their analysis?

[5U4GB]

Does your friend have a blog or somewhere they share their analysis?

No, sorry, just an occasional IM'd "WTF, look a this!" :-).  However there's a ton of pages around that cover these things, "stm32 fake" should turn up a good set of results.

[janoc]

I know nothing about MS VC++ (I pay people on freelancer.com to write apps in it) but I understand that some people have used that IDE for STM chips. Cube IDE is after all not much more than an editor and a makefile generator. How one runs a debugger under VC++ I have no idea but perhaps the clunky Segger ones with the 1970s user interface will run OK.

Obviously as "Cube IDE" only, not Cube MX (which all seasoned programmers seem to hate anyway, but is handy for getting the ST devkit to flash an LED).

Cube IDE getting killed off would not worry programmers working for themselves but it would be a hassle if more than one person is generating code for a project, especially over a long time.

Visual Studio Code is not Visual Studio, those are two completely different products, with unfortunate naming (yay, Microsoft!). VS Code is originally built on Atom, an open source editor project and is mostly open source, with support for languages and what not in form of extensions. Some paid, some free (both as in beer and freedom).

I can understand that they would want to drop Eclipse which was slow and clunky in the best of times, VS Code is lot better in that regard, with modern tooling support for developers. Its support for C/C++ (but also Python, Javascript/Typescript and a lot of other things) is very good, even first class. It is also cross-platform (unlike the "big" Visual Studio) - and doesn't need Java, which is another bonus. There is also a huge community behind it, unlike Eclipse these days.

PlatformIO uses VS Code if you want a taste of what it is like.

So in this case I would consider moving to VS Code from an Eclipse-based IDE as a straight upgrade, IMO. The code generators and projects should be convertible if they do it properly - VS Code doesn't have a "native" project format, like Eclipse or the Visual Studio, it completely depends on what tooling you install in it. E.g. C/C++ work is usually done using CMake-based projects but nothing prevents you from using hand-written Makefiles, if you want. The IDE will work either way.

[MT]

Building cruise missiles and such, you don't need anything beyond a chinese ripoff of a 32F407

Friend of mine has done some analysis of various STM32 clones/fakes.  Trust me, you really don't ever need one of those.
Your competitors OTOH...

As long you dont provide evidence you will sound like a used car salesman. Clones is all right, fakes not.

[Debugging]

IYDM, Taking this thread a bit back on track.

Check out Charbax Embedded world W2023 live with 45 minutes of STM coverage with Roman as the presenter (in excellent English :-))



They are giving out free C0 boards.

1. C0 line (follow up on G)
2. H5 series fully pin to pin compatible with F4 line. Secure boot/TEE, Azure & AWS IoT previsioning with a key and certificate at STM Factory level
3. U5 now scalable to 4MB flash and 2.5MB SRAM for graphics framebuffer and NeoChrome GPU accelerator (upgrade from ChromArt)
4. STM32WB Matter demo
5. Contactless USB2 using 60GHZ ST60
6. STM32MP13 single core Ethercat demo's. ST will release realtime OS later this year
7. Overview  of GUI solution for STM products
8.Developer packages now on github STM32 MCU developers zone.
https://www.st.com/content/st_com/en/stm32-mcu-developer-zone.html
https://www.st.com/content/st_com/en/stm32-mcu-developer-zone/embedded-software.html
9. STLINKV3PWR
10. AI Demo (NanoEdgeAIStudio) TOF STM32F4 CubeAI
11. TSC1614 I3C H5 demo
12. IMU motion sensor LSM16OIS (RISC) LS6VS16X game controller (could have the numbers wrong here)
13. Motor anomaly behavior detection demo

Note: Renesas showed off the first board with the M85 + Helium. STM had nothing of this, even the N6 was announced last year.
Hope the N6 will have Dual USB HIGH SPEED OTG or high speed dual role USB-C (like on the H5),  no external ULPI, Ethernet and RGB LCD and larger SDRAM than U5
See M85 versus older MCU's: https://developer.arm.com/documentation/102787/latest
https://www.eenewseurope.com/en/st-to-launch-its-first-neural-microcontroller-with-npu/

P.S I am not affiliated with ST, just got nothing better to do than writing a summary.

and oh yeah, can sign up for free C0 course and get a board (Guess that only applies in Europe and USA, leaving out the poor chip consumer  elsewhere as usual)

[JPortici]

5. Contactless USB2 using 60GHZ ST60

Woah. Reminding myself to put money in ST stocks
now i'm regretting not ditching work to go to EW

[coppice]

5. Contactless USB2 using 60GHZ ST60

Woah. Reminding myself to put money in ST stocks
now i'm regretting not ditching work to go to EW

People have had working demos of that for maybe 15 years, but it never seems to reach the market.

[harerod]

@Debugging, thanks for your post.

One of my clients has pilfered the stash of F407's, which we bought at horrendous cost from some Chinese purveyer of rare merchandise. It was their call, of course - and the other project was importanter at that time.
Anticipating the next production run of the product that stash was for, I look for "STM32 ethernet" at Digikey. No other restrictions. I don't see much that could replace an F407 with 1MB FLASH.
So it is great to hear about all those new plans from ST. However, the indicator most germane to me is availability at distros, like Digikey or Farnell.

Well, the show must go on. The other day I sent a new product into production, replacing STM32/M0 with ATtiny. That being said - a bunch of M0's seem to have become readily available, in the meantime, for the moment. Worse than the stockmarket.

[peter-h]

What is the value of HS USB?

Unless you are building a hard disk type of product, and then (if on ETH) you will want to run linux on it. Maybe USB-only drives can use that.

The 407 is a great chip for all-round stuff.

There is a real skill (and luck) in picking a good long term bet. LM358, anybody? I got 25 years (plus 5-10 more from shady dealers, until the chinese fakes started) with the H8/323. ST will probably run the 407 for a similar total time, and there are pin and software compatible others e.g. 417 437 etc. And then there are chinese ripoffs, knockoffs, fakes, counterfeits... I reckon the 407 will be like the Z80.

[coppice]

What is the value of HS USB?

The full speed of USB2 may be overkill for most MCU applications, but the full speed of USB1 can be quite limiting. Especially during debug, where you might want to stream a lot of data to a PC for analysis. I think a lot of people have need for something with room to breath.

[JPortici]

What is the value of HS USB?

usb High speed? USB Audio with more than 2x2 i/o channels

In the early days USB audio was limited to 16 bits/48 kHz max.
Today 32 bit / 768 kHz is supported.

A common source of confusion is the version of the bus (USB 1,2 or 3) and the USB audio standard (1 or 2).
USB Audio Class 1 standard (1998)

This standard allows for 24 bits/96 kHz max.
The standard itself doesn't impose any limitation on sample rate.
Class 1 is tied to USB 1 Full Speed = 12 MHz


Every millisecond a package is send.
Maximum package size is 1024 bytes.

2 channel * 24 bit * 96000 Hz sample rate= 4608000 bits/s or 576 Byte/ms
This fits in the 1024 byte limit.
Any higher popular sample rate e.g. 176 kHz needs 1056 bytes so in excess of the maximum package size.

 

All popularr operating systems support USB Audio Class 1 natively.
This means you don’t need to install drivers, it is plug&play.
All support 2 channel audio with 24 bit words and 96 kHz sample rate
USB Audio Class 2 standard (2009)

USB Audio Class 2 additionally supports 32 bit and all common sample rates > 96 kHz
Class 2 uses High Speed (480 MHz). This requires USB 2 or 3.
As the data rate of High Speed is 40 X Full speed, recording a 60 channel using 24 bits at 96 kHz  (132 Mbit/s) is not a problem.

Using High Speed USB for playback  there are no limits in resolution.

It is downwards compatible with class 1.

[peter-h]

where you might want to stream a lot of data to a PC for analysis

You can get ~ 1 megabyte per second with FS USB (CDC - a virtual COM port on the PC).

With the amount of time it takes to get the ST port of FS USB running properly (CDC and MSC in my case) I would not bet on HS USB being easier

Also the PC app is limiting. If you are receiving debugs with say Teraterm, it loses data (or you need to implement the handshake) if you feed it too fast.

usb High speed? USB Audio with more than 2x2 i/o channels

Fair enough - not my area. But maybe quite a narrow application?

[coppice]

where you might want to stream a lot of data to a PC for analysis

You can get ~ 1 megabyte per second with FS USB (CDC - a virtual COM port on the PC).

With the amount of time it takes to get the ST port of FS USB running properly (CDC and MSC in my case) I would not bet on HS USB being easier

Also the PC app is limiting. If you are receiving debugs with say Teraterm, it loses data (or you need to implement the handshake) if you feed it too fast.

Wow, that's really narrow thinking. On the PC side its trivial to get reliable rapid data with tools like libusb to make development easy. On the MCU side there are certainly some performance limitations, but the cores we are talking about are not that slow.

[Debugging]

Regarding the roadmap at the high end MCU line and MPU's in general, I guess STM now faces an up hill battle with NXP. On the MCU side the iMX RT M7 versus the STM32H7437 (no USB-HS w/ PHY) and for MPU the STM32MP (2xA7+ 1xM4 800MHz) versus IMX93 2xA55/1xM33+1xU65 AI @ 1.7GHZ... and there was the Renesas Demo with the M85+Helium-AI

[JPortici]

where you might want to stream a lot of data to a PC for analysis

You can get ~ 1 megabyte per second with FS USB (CDC - a virtual COM port on the PC).

With the amount of time it takes to get the ST port of FS USB running properly (CDC and MSC in my case) I would not bet on HS USB being easier

Also the PC app is limiting. If you are receiving debugs with say Teraterm, it loses data (or you need to implement the handshake) if you feed it too fast.

Then don't do that? It's almost never wroth the hassle to use CDC. When i have lots of data i use raw Bulk endpoints, as I've finally managed how to make windows recognize my device so it gets enumared as a WinUSB device, no driver needed (the application uses libusb, but that's another story)
Raw bulk endpoints: Copy raw memory to endpoint, arm endpoint. let the controller and pc figure out the rest. couldn't be simpler for the MCU. CDC devices instead, at least on the OS side, have to behave as real COM ports with all the delays and buffering

[Sacodepatatas]

and oh yeah, can sign up for free C0 course and get a board (Guess that only applies in Europe and USA, leaving out the poor chip consumer  elsewhere as usual)

ST hates freelancers 😞

[SiliconWizard]

You can be a freelancer and have a business email address.
They don't do that to hate anyone, they do it mostly to avoid spam, which otherwise would be absolutely gigantic. Spam has gotten completely out of control, and even when it's well filtered (which is becoming harder and harder), it still takes the majority of the mail traffic on most exposed servers, that's horrific. So I don't blame too much.

As a freelancer, I would highly suggest buying a domain name anyway, that will help a lot. For about $20/yr you can have a domain name and an email address with your own domain. For a bit more, you can host your website, but even without a website, having an email address with your own domain is a big plus.

[Sacodepatatas]

I have "buyed" a corporate domain (well, I payed 0€ because it was a promo offer), anyway after sending the registering form, ST has to review my registration request, and confirm or deny it in the next days.

I've signed up for several ST events before, just by using my gmail address, and this uncertainty hasn't happened to me before.

[JPortici]

5. Contactless USB2 using 60GHZ ST60

Woah. Reminding myself to put money in ST stocks
now i'm regretting not ditching work to go to EW

People have had working demos of that for maybe 15 years, but it never seems to reach the market.

however in the near future we are going to have gadgets with mmwave antennas in our pocket. I wondered if they were going to remove the charging port too, wireless charging AND wireless data only (brr)

[Debugging]

It's not about freelancer. Tried to access with business account.

Not sure they use some kind of  process to only allow  preference based methods based on location, company name etc..
They probably ran out of free sample C0 stock.

Perhaps they could consider having separate sessions for different regions in the world... 
Would not mind the loss of opportunity to get a C0 board that we probably never would be able to get anyhow, but the course would be interesting.


We appreciate your interest in our workshop on STM32C0: Your next generation 8-bit MCU is a 32-bit, taking place on Thursday, March 23, 2023.
As you may be aware, this is a complimentary workshop with limited seating. Registrations are based on space availability. Due to an overwhelming response, our capacity has been reached and, unfortunately, we are unable to confirm your registration.

... for mmWave, they say it is for automotive, but actually Google, Amazon and the likes don't want your address, they want know if you are in the kitchen, toilet or bedroom to make your life easier and solve all the problems you don't have... Take a look at what Nordic has been working on as well for WIFI to help those big companies...

And

As a freelancer, I would highly suggest buying a domain name anyway, that will help a lot. For about $20/yr you can have a domain name and an email address with your own domain. For a bit more, you can host your website, but even without a website, having an email address with your own domain is a big plus.


Yes do that, some companies already refuse g-mail addresses.. in the end, it won't help those companies much to limit the number the total of  number  requests much because those that really want support, are serious folks that will  or may have their own domain anyhow

[harerod]

pssst - sacodepatatas.es was still available a minute ago...

As others have mentioned - your own domain plus email plus some gigabytes of webspace, with PHP and databases, should be available for less than 50 tax-deductable Euros per year. (just one example, and most certainly not the best: strato.de, who also hosts .com-addresses, should Spanish providers be overly expensive)
Forget Facebook or Twitter or whatever - your own internet domain is the backbone of your online presence.

[Sacodepatatas]

It's not about freelancer. Tried to access with business account.

Not sure they use some kind of  process to only allow  preference based methods based on location, company name etc..
They probably ran out of free sample C0 stock.

Believe or not, after some days of waiting, I have received a confirmation email, hence, i'm in. However I did not choose the yesterday's session but the one of april 20th, because yesterday I had to be aware of the surgery procedure that my mom was undergoing (all went fine).

pssst - sacodepatatas.es was still available a minute ago...

I wouldn't like to kidnap such domain name that is very suitable for the spanish fandom of Marilyn Monroe 😂

[paulca]

Building cruise missiles and such, you don't need anything beyond a chinese ripoff of a 32F407

Friend of mine has done some analysis of various STM32 clones/fakes.  Trust me, you really don't ever need one of those.

Your competitors OTOH...

I looked into F103 clones myself, back in 2019, and I am about to have another look.
Does your friend have a blog or somewhere they share their analysis?

It's a space I am actively trying to avoid as it looks like a massive money pit

I was in that space back when you couldn't buy "drones", the closest thing would have been a DIY tri-copter.  The big thing then was "FPV", using a 12V CCTV camera and 2.4Ghz video transmitter.  There was a thread where someone brought up the various regulations in the US.  For example, selling a product which amounts of a "guidance system", especially if you are exporting it, could get you into some hot legal water.  They ever produced the US government policy documentation/references stating that an airborne navigation system capable of following multiple waypoints to a destination was "restricted".  This was while 13 yo. kids where doing exactly that using micro-controllers and GPS navigation units!

[Smokey]

...
I moved over to ESP32 for a couple of reasons however sourceability being the main one. The IDF tool chain is light years ahead of the ST offering.

...

Can you maybe post over here and let me know what you mean?
https://www.eevblog.com/forum/projects/professional-docs-and-toolchain-for-esp32-in-commercial-product/

[tooki]

What is the value of HS USB?

The full speed of USB2 may be overkill for most MCU applications, but the full speed of USB1 can be quite limiting. Especially during debug, where you might want to stream a lot of data to a PC for analysis. I think a lot of people have need for something with room to breath.

FYI, “Full Speed” in the context of USB doesn’t mean “the entire possible speed” as a description, but rather specifically means the 12Mbps mode. Subsequent USB versions don’t redefine the speeds, just add on more, so for example, USB 1.1 Full Speed is 12Mbps, and USB 2.0 Full Speed is also 12Mbps.

Low speed: 1.5Mbps
Full speed: 12Mbps
High speed: 480Mbps

And then I can’t keep track of the official nomenclature in USB 3.0 and later, since it was always confusing, and keeps changing…

[coppice]

What is the value of HS USB?

The full speed of USB2 may be overkill for most MCU applications, but the full speed of USB1 can be quite limiting. Especially during debug, where you might want to stream a lot of data to a PC for analysis. I think a lot of people have need for something with room to breath.

FYI, “Full Speed” in the context of USB doesn’t mean “the entire possible speed” as a description, but rather specifically means the 12Mbps mode. Subsequent USB versions don’t redefine the speeds, just add on more, so for example, USB 1.1 Full Speed is 12Mbps, and USB 2.0 Full Speed is also 12Mbps.

Low speed: 1.5Mbps
Full speed: 12Mbps
High speed: 480Mbps

And then I can’t keep track of the official nomenclature in USB 3.0 and later, since it was always confusing, and keeps changing…

I did say "the full speed off USB2", not "full speed USB". Because of funky terminology in the USB specs those are quite different things. They love funky terms in USB specs. Can USB2 send data at anything like 12Mbps (FS) or 480Mbps (HS)? That's also funky terminology.

[tooki]

Can USB2 send data at anything like 12Mbps (FS) or 480Mbps (HS)? That's also funky terminology.

What are you asking exactly?

[westfw]

can USB2 send data at anything like 12Mbps (FS) or 480Mbps (HS)?

USB2 added the 480Mbps "High Speed."

USB3 adds "Super Speed" (5Gbps)
USB3.2 adds "SuperSpeed+" (10Gbps, or 20Gbps using multiple lanes.)  https://en.wikipedia.org/wiki/USB_3.0#USB_3.2

[SiliconWizard]

What is the value of HS USB?

The full speed of USB2 may be overkill for most MCU applications, but the full speed of USB1 can be quite limiting. Especially during debug, where you might want to stream a lot of data to a PC for analysis. I think a lot of people have need for something with room to breath.

FYI, “Full Speed” in the context of USB doesn’t mean “the entire possible speed” as a description, but rather specifically means the 12Mbps mode. Subsequent USB versions don’t redefine the speeds, just add on more, so for example, USB 1.1 Full Speed is 12Mbps, and USB 2.0 Full Speed is also 12Mbps.

Low speed: 1.5Mbps
Full speed: 12Mbps
High speed: 480Mbps

And then I can’t keep track of the official nomenclature in USB 3.0 and later, since it was always confusing, and keeps changing…

I did say "the full speed off USB2", not "full speed USB". Because of funky terminology in the USB specs those are quite different things. They love funky terms in USB specs. Can USB2 send data at anything like 12Mbps (FS) or 480Mbps (HS)? That's also funky terminology.

Terminology is just terminology. Everything has history. USB has a long one already.
The missing link here is the low speed, without which we can't understand why they chose 'Full Speed' in the first place.

USB initially allowed two speeds: low-speed (1.5Mbps) and full-speed (12Mbps). The "full" was obviously to signify the full (max) bandwidth possible on then USB.

Then USB 2.0 introduced high-speed (480Mbps) while still being backwards compatible.

Then USB 3.0... as westfw said.

It's not funky, it's just that it has bagage, like everything else. But if you don't use the standard terminology, people are likely not to understand what you mean.

[harerod]

Speaking of terminology: I still remember a cover page of the German computer magazine "c't" calling that new interface: "Useless Serial Bus". I have used that term ever since.
At that time developers had to upgrade their machines to Win98 to get USB support. We had just started selling our new medical device (dozens of EEG channels), when Intel decided to drop out of the USB device chip game and we had to redesign the hardware and rewrite the firmware around the Cypress EZ-USB. Nobody cared for another USB device implementation in 8051 assembly, which led so the firmware being rewritten in Keil C. Windows driver development for that beast was even worse, blue screens galore. During that development we saw Win98, then ME and finally the rather decent XP.
Since then USB development has matured considerably.

[coppice]

Speaking of terminology: I still remember a cover page of the German computer magazine "c't" calling that new interface: "Useless Serial Bus". I have used that term ever since.
At that time developers had to upgrade their machines to Win98 to get USB support. We had just started selling our new medical device (dozens of EEG channels), when Intel decided to drop out of the USB device chip game and we had to redesign the hardware and rewrite the firmware around the Cypress EZ-USB. Nobody cared for another USB device implementation in 8051 assembly, which led so the firmware being rewritten in Keil C. Windows driver development for that beast was even worse, blue screens galore. During that development we saw Win98, then ME and finally the rather decent XP.
Since then USB development has matured considerably.

I think it got the name Useless Serial Bus because for several years it was entirely useless. Numerous peripheral  products, like mice and scanners, were developed, manufactured and died in the market because there was no way to use them. Peripheral makers must have lost a fortune on this. I used to see so many nice polished products in the computer malls in HK, being test marketed to a public that couldn't make use of them. Millions of PCs had that socket on the back that "was for the future", but definitely not for the present. Intel eventually joked that the US beat the Japanese in WW2 faster than the computer industry got USB into a marketable shape.

The original USB specs were very interesting in what they defined and did not define. Standardised serial ports? Nope. For that legacy reason we still have a bunch of incompatible drivers for those. Standardised ways to take a telecoms E1 or T1 carrying ISDN, and terminate it into a PC, with full plesiochronous support. Yep, 100% defined for the handful of people who might ever use it..

[harerod]

Well, USB-2-Serial became much simpler when FTDI issued their first FT232's. All we had to do was connect a serial EEPROM to host our VID/PID. Brings back memories of FTDI's minuscule stall at Electronica(?), staffed with actual Scottish technical expertise (Andrew?, Steward?).

[coppice]

Well, USB-2-Serial became much simpler when FTDI issued their first FT232's. All we had to do was connect a serial EEPROM to host our VID/PID. Brings back memories of FTDI's minuscule stall at Electronica(?), staffed with actual Scottish technical expertise (Andrew?, Steward?).

My experience was Prolific USB serial ports suddenly became.....er..... prolific, and their driver was already on most machines when you plugged into them.

[SiliconWizard]

I forgot to add USB 4.0.
They have changed the naming convention and that goes: USB4 20 Gbps and USB4 40 Gbps. More explicit.

[SiliconWizard]

Well, USB-2-Serial became much simpler when FTDI issued their first FT232's. All we had to do was connect a serial EEPROM to host our VID/PID. Brings back memories of FTDI's minuscule stall at Electronica(?), staffed with actual Scottish technical expertise (Andrew?, Steward?).

What do you again mean by "USB 2". FTDI's first chips were compatible with USB 1.1 only AFAIR.
And yes, that made adding USB to a device much easier. They had also released  a parallel FIFO version at about the same time (FT245), which allowed nearly the full bandwidth in USB FS, about 1 MBytes/s.
You could do the same with Cypress EZ-USB MCUs at the time which were pretty much the only other "simple" solution available, although it was more involved and didn't come with usable drivers.

FTDI's first USB 2.0 HS (high speed) came much later, around 2007 IIRC. Of course to get the benefit of HS you would need to use a parallel FIFO mode. Even on their latest chips, the UART <-> USB function tops at 3 Mbits/s, for which the bandwidth of FS is enough.

And then they released USB 3.0 SS chips (FT6xx). At this point, alternatives (such as Cypress FX3) are much more expensive actually. I think there are some chinese interface chips supporting USB SS, but I don't have references in mind.

I don't know if they'll ever release chips allowing the new speeds of USB 4. That's freaking fast.

[tooki]

Well, USB-2-Serial became much simpler when FTDI issued their first FT232's. All we had to do was connect a serial EEPROM to host our VID/PID. Brings back memories of FTDI's minuscule stall at Electronica(?), staffed with actual Scottish technical expertise (Andrew?, Steward?).

What do you again mean by "USB 2". FTDI's first chips were compatible with USB 1.1 only AFAIR.

I suspect that by “USB-2-Serial”, they meant “USB-to-serial”. Just a very unwise choice of spelling, methinks.

[SiliconWizard]

Well, USB-2-Serial became much simpler when FTDI issued their first FT232's. All we had to do was connect a serial EEPROM to host our VID/PID. Brings back memories of FTDI's minuscule stall at Electronica(?), staffed with actual Scottish technical expertise (Andrew?, Steward?).

What do you again mean by "USB 2". FTDI's first chips were compatible with USB 1.1 only AFAIR.

I suspect that by “USB-2-Serial”, they meant “USB-to-serial”. Just a very unwise choice of spelling, methinks.

Ouch
But at least maybe the history I gave helped some remember/or be aware of the offering.

[harerod]

... they ...

Don't do that to me, please. 

[alm]

... they ...

Don't do that to me, please. 

You can list your preferred pronoun in your profile / signature if you care that much

[tooki]

... they ...

Don't do that to me, please. 

So… don’t use English to you?!?
In English, the singular ”they” is a standard way of referring to someone whose gender you do not know. That usage is well-documented, going back to at least the 14th century.

(This is, incidentally, precisely the reason “they” has also become the dominant gender-neutral pronoun, beating all the invented ones like “ze”: it’s only a minor extension to a familiar usage. But that doesn’t mean it’s lost its original meaning!)

[harerod]

Tooki, I simply love our occasional exchanges about linguistics.
Sure, a lazy "they" is one viable device, in case you couldn't possibly know the referee's sex and wanted to churn out another quick post. However, one might venture that in a forum like this, the oldfangled "generic he" might be an even better bet.

Since I signed our private exchanges with my given name and having set my  gender in my forum profile, I permit myself to politely ask you to do this old grumpy engineer the courtesy of using that information.

https://en.wikipedia.org/wiki/Gender_in_English
https://en.wikipedia.org/wiki/Singular_they
https://en.wikipedia.org/wiki/Gender_neutrality_in_languages_with_gendered_third-person_pronouns#Generic_he

[tooki]

Tooki, I simply love our occasional exchanges about linguistics.
Sure, a lazy "they" is one viable device, in case you couldn't possibly know the referee's sex and wanted to churn out another quick post. However, one might venture that in a forum like this, the oldfangled "generic he" might be an even better bet.

Since I signed our private exchanges with my given name and having set my  gender in my forum profile, I permit myself to politely ask you to do this old grumpy engineer the courtesy of using that information.

As a native English speaker, I respectfully decline to strike a correct, valid usage of generic English terminology from my vocabulary (even if just for one person). I’m happy to use “he” referring to you in the future, but can’t guarantee I will remember the username and make the association.

Honestly, I didn’t remember your username or name, and I’m not going to check someone’s profile to see if they happen to have set their gender. It simply doesn’t matter that much when a perfectly serviceable solution has been in continuous use for 700 years.

[paulca]

I had a meeting with a local manager today and relevant SMEs, they were epic.
I had a meeting with a local manager today and relevant SMEs, he/she was epic.
It matters.  Plurality.

[tooki]

I had a meeting with a local manager today and relevant SMEs, they were epic.
I had a meeting with a local manager today and relevant SMEs, he/she was epic.
It matters.  Plurality.

Irrelevant to the issue at hand, it’s the well established singular they.

[gmb42]

Can all the pronoun discussion be moved to the appropriate place (or even better deleted) and then we can get back to discussing the STM32 roadmap?

[Sacodepatatas]

It's not about freelancer. Tried to access with business account.

Not sure they use some kind of  process to only allow  preference based methods based on location, company name etc..
They probably ran out of free sample C0 stock.

Perhaps they could consider having separate sessions for different regions in the world... 
Would not mind the loss of opportunity to get a C0 board that we probably never would be able to get anyhow, but the course would be interesting.

I've followed the course in English the past 20th of this month although i couldn't pay so much attention because of personal matters, so i wanted to watch the course again once being more relaxed). During the course we were told that the 3h recording would be available in a brochure sent to our emails besides the link for ordering the Nucleo Board samples. That was 4 days back. Still no news from ST Micro besides some email advertisements regarding more courses. I'm starting to think that i've been mocked. But, let's wait some more days...

[peter-h]

Well, USB-2-Serial became much simpler when FTDI issued their first FT232's. All we had to do was connect a serial EEPROM to host our VID/PID. Brings back memories of FTDI's minuscule stall at Electronica(?), staffed with actual Scottish technical expertise (Andrew?, Steward?).

At least one of these is still sitting somewhere in Scotland, and replying to emails.

The commercial side of FTDI is long gone, to Taiwan I believe.

I still use these chips but the FT232 was replaced by the much cheaper FT231. FTDI are today a really opportunistic outfit and are gauging people with FT232 pricing. Mouser have got stuck with vast stocks of FT232 when the chip shortage bubble blew up; they will probably flog them off to the 2nd tier disti cowboys in the US and elsewhere. Off topic anyway.

32F4 USB works OK, with the ST Cube IDE supplied code and with lots of patches (found on google) added. I have a pretty solid CDC and MSC running. I would have never even dreamt of doing USB without that code. It's horrible.

It's almost never wroth the hassle to use CDC. When i have lots of data i use raw Bulk endpoints, as I've finally managed how to make windows recognize my device so it gets enumared as a WinUSB device, no driver needed (the application uses libusb, but that's another story)
Raw bulk endpoints: Copy raw memory to endpoint, arm endpoint. let the controller and pc figure out the rest. couldn't be simpler for the MCU. CDC devices instead, at least on the OS side, have to behave as real COM ports with all the delays and buffering

What if you actually want a VCP under windoze? It's a very simple API for apps to use. The delays probably don't matter in most real applications.

[SiliconWizard]

Definitely use a FT230X or FT231X these days. They're cheaper, support more, draw less power and have not been cloned whatsoever (yet at least) that I know of, so you're relatively safe.

[westfw]

USB-2-Serial became much simpler when FTDI issued their first FT232's

Well, aside from the fact that they were pretty hard to get; not carried by the usual distributors...

[harerod]

Quote

USB-2-Serial became much simpler when FTDI issued their first FT232's

Well, aside from the fact that they were pretty hard to get; not carried by the usual distributors...

Well, I guess we (a medical devices outfit with a couple of hundred employees) got them either directly from FTDI or via our standard distributor Spoerle. Fascinating how stories a quarter century old stick in the memory.

STM32 availability seems to be improving. Only yesterday ST's website told me that 2000 units of a certain component were available from Future. After clicking on the provided link, I was told that Future is sold out and awaits new stock by end of this year. Really smooth database links...

[Sacodepatatas]

I've followed the course in English the past 20th of this month although i couldn't pay so much attention because of personal matters, so i wanted to watch the course again once being more relaxed). During the course we were told that the 3h recording would be available in a brochure sent to our emails besides the link for ordering the Nucleo Board samples. That was 4 days back. Still no news from ST Micro besides some email advertisements regarding more courses. I'm starting to think that i've been mocked. But, let's wait some more days...

After 8 days, the e-mail message with the aforementioned  links eventually arrived to my e-mail box. The recording of the workshop has been uploaded to Youtube by ST, but the link has not been published for listing (although it's publicly accesible). I'll respect the ST's will and won't put a link here in this post, but I might reply to any PM asking for it, with a reply containing the link.

[grantb5]

IYDM, Taking this thread a bit back on track.

2. H5 series fully pin to pin compatible with F4 line. Secure boot/TEE, Azure & AWS IoT previsioning with a key and certificate at STM Factory level
3. U5 now scalable to 4MB flash and 2.5MB SRAM for graphics framebuffer and NeoChrome GPU accelerator (upgrade from ChromArt)

Thank you! 

I'm in the opposite camp as the OP. I'm just starting with STM32 but did one learning project with F103 because of the plethora of resources for it. I'm actually looking for a fairly cheap *new* STM32, like $5-ish in quantity. The U575 looks good price-wise compared to the older parts, BUT I need a pretty large TFT LCD. I don't see any STM32's that I can afford that would have enough memory for an 800x480 TFT compared to say, ESP32, but I don't want to go the ESP32 route. The H563 also looks good and is a bit cheaper. Most of the gee whiz stuff on those micros I don't need (I do need USB Device, full speed).

[langwadt]

FTDI's first USB 2.0 HS (high speed) came much later, around 2007 IIRC. Of course to get the benefit of HS you would need to use a parallel FIFO mode. Even on their latest chips, the UART <-> USB function tops at 3 Mbits/s, for which the bandwidth of FS is enough.

the HS chips can do 12MBaud

[Debugging]

More information related to the title of this topic:

https://live.vhall.com/v3/special/detail?id=744067034

You can view the ST Event in China last week, There is English translation for the key note, click on "English" after selecting the video
Unfortunately, no PDF slides.(yet?)

ST seems to to a better marketing job with much more detail for the folks in China than for those elsewhere. Perhaps there are more product design house customers there than anywhere else ?

Hard to find, but there is the STM32MP2 series announcement with 2x GB, USB 3.0 and 4 lane MIPI (at least that is what Yahoo news said about MIPI and  it is not in the ST flyer, so Yahoo seem to know more than what is on the ST website)
Personally, don't prefer such marketing practices with very limited detail. Why not just get over it, announce the whole feature spec at once with a roadmap of availability  instead of a half baked flyer.

https://finance.yahoo.com/news/stmicroelectronics-introduces-second-generation-industry-070000434.html

[Debugging]

AND AS USUAL  THE SAME ANSWER.

This is becoming a systemic issue. ST changed to use a BOT  that checks IP or bases to auto-reject  ?


We appreciate your interest in our workshop on STM32H5: Ultimate combination of performance, integration and affordability, taking place on Tuesday, May 23, 2023.

As you may be aware, this is a complimentary workshop with limited seating. Registrations are based on space availability. Due to an overwhelming response, our capacity has been reached and, unfortunately, we are unable to confirm your registration.

If you have any questions, please contact us on the dedicated ST Community.

[Eternauta]

The peripherals of the new microprocessor family are truly complete. There is also PCIe and LVDS

https://www.st.com/content/st_com/en/campaigns/microprocessor-stm32mp2.html?icmp=tt32627_gl_pron_may2023

[Debugging]

Per the ST "Event" this week, MP2's will now become (more) available in 2025. It seems only some customer have some on hand. So that will be 2 years from announcement to actual availability, whatever this "availability" may actually mean. (retail ?). and still no USB 3.0... These two slides are everything that seems available now regarding MP2.

[mark03]

Wow, is the event over now?  I was just on the STM32 product page and I see the new STM32U0 series listed, but nothing else.  That could be interesting.

OTOH, none of the cutting edge stuff that I listed last year (see below) is even in vaporware phase, except for STM32N6 which has now been in "pre-launch" for TWO YEARS without even a data brief to summarize what is inside.  This suggests they are having real problems getting new silicon out the door.

I will continue to use STM32 for the foreseeable future because I can't stomach having to reverse-engineer undocumented MCUs from China just to make them work.  I am starting to suspect, however, that ST made a strategic decision to cede the MCU market to others, and is just milking their current portfolio for as long as they can.  The future is bleak

ARM must also be worried.  For anyone keeping track, it has now been more than *four* years since Cortex M55 was announced and there is still no silicon from the big players, not even pre-release announcements, unless you count coprocessors on Cortex A's.  We do have M85 from Renesas but no hint of competition from anyone else.  This is a much longer product cycle than M7 which makes you wonder if the new cores with Helium will ever see the light of day.

So the deadline is past, and although I don't have time to sit through a 1.5-hour video, I did take a look at the STM32 product page and tried a google news search for "stm32" and I don't see much in the way of new MCU development.  (The new MPUs are interesting to some, I guess.)

Still no Cortex M55 or M85 parts with the Helium SIMD.  Nothing with neural coprocess (Ethos).  Nothing exciting on the process front either (anyone remember FDSOI?).  No foray into RISC-V either.  I would need at least one of those to pique my interest.

Everyone knows there is a long lag time between ARM's announcement of new cores and real silicon, but if you compare with Cortex M7, this has already been a longer wait than normal---the M55 was unveiled more than three years ago, and there are still not even vaporware new-product announcements from ST.

That being said, they promised an update on the supply situation... Did anyone tune in to hear what they had to say?  Just being able to buy parts from their current product line would be fantastic in the near term.  But IMO a lack of new products in the pipeline bodes ill for the future.

[IOsetting]

STM32F103 and STM32F407 still work perfectly in most applications, with plenty of alternative chips in the market, I don't see a reason to move to new product lines. As for Arm and ST, their biggest challenge comes from RISC-V. The market has been quite different in China mainland after the pandemic.

[grantb5]

STM32F103 and STM32F407 still work perfectly in most applications, with plenty of alternative chips in the market, I don't see a reason to move to new product lines. As for Arm and ST, their biggest challenge comes from RISC-V. The market has been quite different in China mainland after the pandemic.

Entering this STM32 MCU game late, I was taught on the F103, but realize that's very old now. I really like the U5 series, but it's just way too big a leap for me at this point. What was the roadmap after the F4?  I get the impression it was F1 -> F4 but then what? I'd like to make a couple of generational leaps from the F1 without going too crazy. My primary usage is basic USB peripheral, but I have a LOT of stuff hanging off of GPIOs, so I appreciate things like BSRR and bit-banding (the latter of which seems to have disappeared somewhere along the line).

[SiliconWizard]

STM32F103 and STM32F407 still work perfectly in most applications, with plenty of alternative chips in the market, I don't see a reason to move to new product lines.

I don't know what "most applications" mean. This kind of assertion is always odd. What is the definition of "most applications"?
STM32 MCUs have made big gaps in terms of performance and, particularly, power consumption in more recent series than the venerable F1 and F4. If low-power is a requirement, then the F1 and F4 are certainly out of the equation, so in itself is a good reason for considering more recent series.

There are alternatives for sure, but again, when it comes to low-power and the L4/L5/U5 series, not that many either. Very few actually that come even close.

I somehow would translate your above assertion to "STM32F103 and STM32F407 can be had dirt cheap in China and we don't see any reason to use any more recent STM products, as they are much more costly for us. And we don't particularly care for low power anyway."

And with that said, with anything that doesn't require ultra-low power, I now like the WCH RISC-V-based products, but their peripherals tend not to be as flexible as what we get on STM32 MCUs in general, at least the more recent ones, as WCH tends to "clone" STM32 peripherals from older generations.

[IOsetting]

If low-power is a requirement, then the F1 and F4 are certainly out of the equation, so in itself is a good reason for considering more recent series.
There are alternatives for sure, but again, when it comes to low-power and the L4/L5/U5 series, not that many either. Very few actually that come even close.

You are right, low-power is a con of old series.

I somehow would translate your above assertion to "STM32F103 and STM32F407 can be had dirt cheap in China and we don't see any reason to use any more recent STM products, as they are much more costly for us. And we don't particularly care for low power anyway."

It's not quite true that, in addition to price, we also need to consider the stability of the supplier's delivery as well as alternative options in extreme cases.  If we put our bets on ST's new product line, there will be a significant risk.