2019 STM32 Wish List

[Amel NASRI]

Dear Community Members & STM32 fans,

Let’s end 2018 thanking you for your involvement in our Community and wishing you all the best for 2019!

As already done in 2017 (https://community.st.com/s/feed/0D50X00009bLPmvSAG) and in 2018 (https://community.st.com/s/feed/0D50X00009bLSAKSA4), we open this space to hear from you.

This is an opportunity for us to evaluate what we deliver as offer and to know your expectations.

If we come back to the STM32 portfolio end of last year, it was like this:

Now the image is getting larger with new products as well as ecosystem components:

Compared to the wishes you shared previous years, we weren’t able to answer all proposals for sure, but may be some of our solutions met what you looked for. Like for example: delivering .ioc file in the STM32Cube package which we started with STM32G0...

Either you are a follower of the STM32 history as well as the Community updates, or a new member in this space, would you mind share with us your feedback answering the following 3 questions:

• What shouldn’t be done (don’t say migration to new Community platform or new CubeMX interface (because both of them will be improved)?
• What you appreciate the most as STM32 related offer?
• What do you expect/suggest related to the STM32 and its ecosystem?

All together, keep UP our STM32 Community!

[AVI-crak]

You will be surprised by the result after removing the pieces of paper from the chip.

Very surprised.

[thanks4opensource]

waclawek.jan and Dave Nadler:

These are old posts but I've just come online here and agree completely. You may want to check out my post in the "Share Your Activities" section. It's about my open-source project which I wrote partly to address these missing definitions in the CMSIS headers (also dissatisfaction with the design and inefficiencies of the LL and HAL libraries), but it does more than that. Maybe too much more "more" than what you're seeking, but that's for you to decide. If you're getting notifications of replies to your posts and look at my "Share" and/or the project it links to I'd be interested in your feedback and suggestions. Thanks!

[Stephen28]

I would like a M7 in a LQFP64 with 1MB Flash or larger.

[Dave Nadler]

That's an interesting library.

Can't use it for real work as it appears to have a polluting GPL.

Also needs to be complete and in my case F4 support, not F7.

Thanks anyway,

Best Regards, Dave

[flyer31]

Simple application demo examples (NOT STM32 Cube / HAL based).

Continued support for "slim compilers" as Keil / ARM-CC, also for new things like Wireless / KNX/ ... . (please be careful concentrating to much on this Attolic / STM IDE support - this is a mistake also Microchip did 10 years ago ... they were so fanatic about their "own IDE" / "own way", that they forgot the world around, and started 32 bit processors then in a completely wrong direction... for some people such an "integrated IDE approach" might be nice, but not for specialists, they usually prefer very much to check "slim and tiny code examples").

[gregstm]

As someone mentioned much earlier - more timers (ideally 32bit) that can be connected to the LSE - even if they are just simple timers that can be used to trigger DMA etc. ( I'm using the L4.)

I often wish that the Boot0 pin had an internal weak pulldown so I didn't have to place an external resistor near it.

I would like simple examples of how to get peripherals going using writes to registers - similar to what you would get if you did a "trace" of registers on working code.

[MikeDB]

Definitely a pulldown on Boot0.

Examples of register writes would also be most helpful - I always have to reduce the generated LL code to this in the end to save memory space.

[waclawek.jan]

Please give us back the "worst forum software ever" tag.

JW

[MikeDB]

And a new one for "Worst alpha tested IDE ever" :) (CubeIDE)

[S.Ma]

And how many times did you scroll this web page from the top to reach here?