No 2020 STM32 wishlist

[waclawek.jan]

This is probably the promised replacement.

[Edit 2023] Link above lead to Ideas, a section mostly ignored by ST (TouchFX crew being exception) and ultimately removed together with content i.e. user wishes when migrating to Khoros [/EDIT]

Pity. It's been a nice tradition.

JW

PS. Following is my 2020 STM32 wishlist. I'm not going to dump it to that new place. Anybody feel free to cherry-pick and post there, if you feel so.

• renew STM32 Technical Updates https://community.st.com/s/question/0D50X00009Xkba4SAB/stm32-technical-updates
• normal forum software
• make a static snapshot of the forum, especially since older posts are closed
• revert ST main web to pre-2019 (practically every "improvement" made in 2019 is a regression in usability) - this would also return full linkability
• more technical staff presence in the forum
• in documentation, better module-interconnections description (these chapters are often incomplete or missing), links from RM to AN where the interconnections are described "externally"
• in new chips, more interconnections, especially timer-related, e.g. SPI (and other modules') baudrate generated by timer, SPI NSS/framing generated by timer in counter mode (i.e. timer fed from SPI), USART IDLE timer, etc.
• as an upgrade to TIM module, add a shift register to facilitate non-standard shiftregister-based communication protocols
• add a simple counter to RTC (while done in RTCv3, present only in 'WL, see AN4759)
• document variants of IPs used in the various STM32 models
• extensive examples based on normal C code (Snippets)
• dozens of appnotes (https://community.st.com/s/feed/0D50X00009XkVvLSAV)
• update ES timely (errata often don't make it from the particular model where they've been "discovered" into other models where the same erratum applies, or it takes inordinate amount of time when this happens, and often such "migrated" erratum misses some key part e.g. https://community.st.com/s/question/0D50X0000BufujjSQA/es0388-l452-errata-rev5-comment-about-mco-in-spurious-brownout-reset-after-short-run-sequence-erratum-does-not-make-sense-without-the-accompanying-figure )
• remove "modern feel and look" in technical texts (appnotes, errata, devboards UM)
• reduce unnecessarily big images in devboards UM, reducing file size to sane values
• include schematics in the devboard UMs, even if its more work for you, it's then less work for us
• reconsider DISCO boards - make them to be perks, break out all pins and make ways to disable onboard features, make examples, make the stlink to be usable (e.g. make appnote how to use it with low-voltage target, how to use galvanic decoupling, how to use swo?)
• remove obsolete devboards (e.g. STM32VLDISCOVERY with the V1 STLink which is not supported anymore) - and by that I mean purge them also from the distributors -- OTOH, make available documentation also for discontinued devboards
• provide binaries of ALL the demos which come preprogrammed in ALL the DISCO, NUCLEO and EVAL board
• provide sources for MFX on Disco boards
• stlinkv2-1 in the lower-end devboards rather than the unnecessarily expensive stlinkv3 (which btw. can't provide the 8MHz clock precisely)
• stlinkv2-1 sold as a chip (preprogrammed 'F103)
• STLinkV3 implement complete FS functionality, so that it can be used with USB isolators https://community.st.com/s/question/0D53W000005qNEzSAM/how-can-isolate-the-usb-port-for-stm32g474-nucleo-64-board https://community.st.com/s/question/0D53W000003Kqb3SAC/failed-to-connect-to-stlink-v3-using-a-usb-isolator
• crypto-less 'F7x0/'H7x0 https://community.st.com/s/question/0D50X0000ALv1isSQB/not-really-a-technical-questionproblem-purchasing-stm32h750vb
• direct sales distributor in Europe (yes I'm selfish)
• built-in JVM in the java-based software (including the installers) https://community.st.com/s/question/0D70X00000763nW/oracle-jre-license-impact
• bitfield values in the CMSIS-mandated device headers https://community.st.com/s/feed/0D50X00009XkVsDSAV
• restore pin compatibility across families (G0/G4 are not compatible, not even with each other)
• consider API to USB library portions in bootROM (see NXP's LPC)

Others have asked for:

• more 32-bit timers
• chips with smaller and/or more prototyping-friendly packages
• better GPIO/AF matrix
• use the wide ADC MUX also as input MUX to OPAMP/PGA
• more transparent software update process (public bug tracker), maybe even open (parts of ) it to external contributions
• more chips with integrated HS USB PHY
• shared address/data bus (i.e. stripped-down pin requirement, possibly fitting into 100-pin devices) for SDRAM, as Tiva do https://community.st.com/s/question/0D53W000003xcVSSAY/how-to-configure-sdram-on-100-pin-h7

[re.wolff9]

> DTCM-SRAM working with DMA.

The way I understand things, the "tightly coupled" RAMs are faster because they don't have that many connections. So the idea of the TCM is that it doesn't have DMA capability and therefore has higher performance for the CPU alone.

[Asantos]

STM32H7 is the only cortex-m7 on the market where DTCM does not work with DMA. For example, the I.MX RT from NXP runs at 600MHZ and the DTCM works with DMA. The DTCM of the STM32F7 also works with DMA.