Such as: UCOSIII stm32cubeIDE transplant, STemwin, stm32407 chip, float variables into the hardware error after
Is Keil5 before transplantation also encountered this problem, and then is in the boot file to add a piece of code solves the,
This time because of the startup file is different also, don't know how to change

CodePudding user response:

See what is the specific hardware error, then try to analysis

CodePudding user response:

Feel like precision problem, you add a f when float variables;
Such as float a=0.5 f;

CodePudding user response:

If the CPU with floating point registers, at the time of transplantation is put into the inside of the task stack as R0 - R3

CodePudding user response:

reference Jacky_Lu reply: 3/f

if the CPU with floating point register, at the time of transplantation is put into the inside of the task stack as R0 - R3

I readjusted, because I have been the UCOS_III and STemwin, later found to be as long as add touch cannot use float, haven't find out why

CodePudding user response:

F4 series many have FPU core, need to focus on whether open, open, RTOS will automatically protect the scene, otherwise there will be a chance in the operation of the floating point Numbers of abnormal call level (register) lead to errors, so need to focus on two points:
1. The single chip microcomputer of FPU whether open,
2. RTOS to the requirement of FPU how, whether to need to change?