Hi,
i had a first trial with embOS using
- embOS V502a
- Cortex-M
- STM32F051_STM32F051R8_SK example from the embOS BoardSupport Folder
- Segger Embedded Studio for ARM V4.12 (64Bit)
and realized the following problem:
/* CODE INSIDE A TASK */
unsigned long long SerialNumber = 123456789012345;
char buffer[50];
sprintf(buffer, "%llu", SerialNumber);
/**********/
produces - while using embOS - the result : buffer[0] => u (only the character "u") ??
and without embOS the result is correct : buffer content == 123456789012345
What could be the reason for that behavior?
The stack is big enough to handle the sprintf without crashing the RTOS.
The flags inside solution OPTIONS / CODE for the Printf/Scanf are always set to:
Printf Integer Support = Long Long
Printf Width/Precision Supported = Yes
Wide Characters Supported = Yes
Thank you for your support!
Marco Seitter
i had a first trial with embOS using
- embOS V502a
- Cortex-M
- STM32F051_STM32F051R8_SK example from the embOS BoardSupport Folder
- Segger Embedded Studio for ARM V4.12 (64Bit)
and realized the following problem:
/* CODE INSIDE A TASK */
unsigned long long SerialNumber = 123456789012345;
char buffer[50];
sprintf(buffer, "%llu", SerialNumber);
/**********/
produces - while using embOS - the result : buffer[0] => u (only the character "u") ??
and without embOS the result is correct : buffer content == 123456789012345
What could be the reason for that behavior?
The stack is big enough to handle the sprintf without crashing the RTOS.
The flags inside solution OPTIONS / CODE for the Printf/Scanf are always set to:
Printf Integer Support = Long Long
Printf Width/Precision Supported = Yes
Wide Characters Supported = Yes
Thank you for your support!
Marco Seitter