Hi Martin. I'm sure that will help - thank you, though I found the 'Auto Version Identifier' component under Storage >> Utility. File versions are usually embedded in file names (so that we can recover them in a name search), so ability to reference and report the source project filename (also refle...
When creating many different projects and products, building them and programming to micros, it is invariably useful to know exactly which software version is programmed to the micro by report (UART/USB/display, etc). This can be achieved manually by creating a string constant, copying-in the source...
Many amongst us will be using timer interrupts on devices that clock such timers from internal busses (i.e. not the input clock frequency always assumed by Flowcode), rendering the otherwise-useful interrupt frequency calculations quite wrong. Ordinarily, it is most useful to play around with pre-sc...
Whilst I've responded to a former thread on the subject, more appropriate to request here support for STM32 USB Vcom, obviously requiring that pre/post-scalers are first configured appropriately. I'm professionally committed to mostly STM32 these days, now using such micros to stream/log high-speed ...
A huge +1 for USB Vcom support for STM32 devices, with the obvious caveat that clock prescale/postscale registers must first be set correctly - per STM32 CubeMX. I'm streaming high-speed data to host from ADCs, but limited by wired UART. USB Vcom would expand available bandwidth and leverage the hig...
I believe there are fundamental issues with STM32F4.. UART, particularly when RxD hangs for no apparent reason, and erratically so. I have a program on an STM32F407 running TxD+RxD (no flow control) on two hardware UART channels running at 9600bps. In both cases the UARTS are serviced by ISRs that m...
Quite often it can be somewhat frustrating getting to the bottom of build errors, whether they be embedded in macros, conflicts in var types, interrupts, etc. It's certainly possible to copy the project to a new file, deleting macros and variables (etc) until a successful exploratory build points at...
Hi Ben. Thank you so very much for investigating further, and for your valued time to reply. I really do appreciate this. I will take this back to the team early next week in order that we can now arrive at well-informed decisions going forwards, hoping that scope remains for Flowcode-based integrat...