Hi Steve, Thanks for your reply, that was exactly what I needed, to include a file and then use my favorite Editor . The Absolute Path ended up being a bit complicated, but it worked #include "Z:\\Mega_2\\STM ILLUMINATI\\FlowCode Base\\Suplimentary_Code\\UART3_DMA.c" Thanks again Regards

Hello

Is there a way to make a C block function Global ( can be called from all Macros ), other than putting it in the supplementary code ?
or can we just add a C file to the supplementary code?

If not, I think it should be possible to create a component that lets us add a C file

Yes, I understand, it is not a big problem.

So maybe it could be a good idea if we could input the CLK manually for the interrupt Frq calculation.

Thanks

Hi LeighM, Thanks for your reply. That was exactly the issue — I had assumed it was the system clock, not the source clock. That’s why I thought the MCU was limited to a maximum of 26 MHz. Now the UARTs are working fine at 115200 bps. However, I’ve noticed another problem: the timer interrupt freque...

OK ,

So with the original FCDX and running at 16MHz using HSI default Settings, the problem is gone and the UART works fine @115200 .
But I need to use the External 8MHz crystal HSE mode and PLL to 96Mhz, which is half of what this MCU can do
is that possible?

I believe I’ve found the source of the problem. I had to set RCC_PLL_SRC to OFF, as this was the only way the delay timings correctly matched 96 MHz when verified on the oscilloscope. However, when I change the PLL source to HSE, the UART baud rate improves slightly, but it still doesn’t reach the c...

Hello, I’m encountering a strange issue with the UART baud rate, which I suspect might be a bug. Everything works correctly at lower baud rates, but when I select 115200, the UART output becomes extremely slow — roughly equivalent to 110 baud or less. I’ve modified the FCDX file to allow the MCU to ...

Hi Martin, Storing the data in a byte array worked perfectly for me. I can always convert it to a string when needed. To be honest, I was trying to avoid that at first, since it would require changing a lot of existing code—but in the end, this approach makes more sense, especially since I’m mostly ...

Hi Martin, After giving it some thought, I realized that many C functions stop processing a string once they encounter a null character. That’s likely the issue when trying to store the data in a string array. I’ll try storing the data in a byte array instead and see how that works out. I really app...

Hi Martin, Sorry can not share the FCFX file, > The additional setup is required to change non-standard baud rates during runtime. > Receiving a single character per interrupt is a good idea, I have not tried that . > For each unit & Brand, the expected byte count is known, but a timeout is also...