Does STM32CubeIDE and Azure RTOS properly support Sprintf?

[GreenGuy]

I am having issues using sprintf in an application on a STM32H743 using Azure RTOS.  The function works correctly the first time it is used to convert a float to a string but after the first use, it inserts garbage characters where the decimal point should be while the digits are as expected.  The garbage characters continue to show up on subsequent calls to the routine where the sprintf is used and show up in other routines that use sprintf.  The garbage characters are always the same and only appear for float values that have digits to the right of the decimal point.  An example is when printing the conversion for the internal battery measurement which comes out as ...MCU Bat : 3.15 V on the first pass, then comes out as ...MCU Bat : 3"KOq@=xZ15 V on the second pass.  It is repeatable.  The format string is ...MCU Bat : %.2f V\r.  Changing the format string does not seem to effect the result.

I have gone over numerous posts regarding sprintf and RTOS but none seems to match with what I have implimented and what I am seeing.  There are no hard faults or crashing.  

Version info:

STM32CubeIDE - Version: 1.14.1 - Build: 20064_20240111_1413 (UTC)

STM32CubeMX - STM32 Device Configuration Tool - Version: 6.10.0-RC9 - Build: 20231120-2037 (UTC)

Linux LMint 21

[AScha.3]

I would set in debug a breakpoint at the sprintf line , to look , what is the float now ; + whats in the string, after sprintf ; then run ..and look.

+

what did you set : in project settings ->

[GreenGuy]

I guess I could uncheck the scanf option since it is not used.  But that does not make a difference.

I already did the break point on the sprintf line.  The float values are good and the string after the sprintf has the garbage characters in it.  I also tried stepping into the sprintf function but it simply steps over it.  The local string buffer is initialized to all 0 upon entering the routine containing the sprintf.

[AScha.3]

> I also tried stepping into the sprintf function but it simply steps over it.

Hm - whats your optimizer setting ?

+

Just for test: set D-cache off (or dont enable it ), to be sure its not just some ...cache effect.

[Tesla DeLorean]

Pull the full runtime, not the nano stuff.

[Pavel A.]

@GreenGuy  Please test before starting the RTOS scheduler. If that works, you'll need to fix the multi-threading locks in newlib for ThreadX.

[GreenGuy]

maximum(g3)

[GreenGuy]

Dcache disabled changes the inserted garbage but still garbage.

Also, applied cache maintenance (SCB calls) but no change in behavior and yet the garbage is different.

[GreenGuy]

that will take a good deal of rearranging since I use threading to send the messages.

But it is worth a try to understand what is wrong with sprintf.

Right now my work around is to reduce every thing to non decimal by doing:

bat_left = (UINT)battery;

bat_right = (UINT)((battery - bat_left)*100); //2 decimal places

and then just building the message with %d.%d - no problems!

[GreenGuy]

can you translate into steps relative to files and perhaps CubeMX?