|
因项目需要使用STM32F417的硬件浮点单元,但当时Micrium的官方移植µC/OS-III V3.03.01 (2013/01/23)不支持FPU,因此需要修改代码添加FPU支持。 首先,为了便于控制是否使用FPU,定义一个宏 USE_FPU。需要使用FPU时在MDK的工程选项中定义这个宏,要在”C/C++“和”Asm“选项卡中都定义,这样无论C代码还是汇编代码中都可以使用这个宏了。需要注意的是,预定义宏__TARGET_FPU_VFP只能在C文件中使用,汇编文件中不能使用。; o, I8 r: A* m1 L9 Y 然后,在CPU初始化代码中设置FPU。在官方移植中,设置代码已经有了,但被注释掉了,只要取消注释即可,然后再设置代码前后添加条件编译:# {- n6 }. Y: }1 D) a IF EF: USE_FPU8 C. u8 a7 j$ H ;Enable FPU ;Use reset settings: automatic lazy FPU state preservation LDR R0, =0xE000ED88 ; Enable CP10,CP11 LDR R1,[R0] C- A& Q/ X' P/ }8 w4 J6 x# B <span lang="EN-US" style="font-size: 9pt; font-family: Arial, sans-serif;"> ORR R1,R1,#(0xF |
【福利三:雨露均沾·逢7狂欢】之四:用一个定时器同步另外两个定时器输出PWM
【逢7发帖赢大礼】STM32开发之WIFI实时时钟
【逢7发帖赢大礼】STM32开发之指纹识别!
【逢7发帖赢大礼】STM32开发之环境空气质量监测
【逢7发帖赢大礼】STM32开发之人体实时运动信息监测!
【逢7发帖赢大礼】STM32开发之IC门禁卡UID读取方法!
【逢7发帖赢大礼】全网最简单的Arduino_STM32开发环境搭建教程!
STM32F4中文用户手册
STM32F400、STM32F402 Cortex-M4超值单片机
SPI 高温读错最后一位?STM32F42xx 官方根治方案
微信公众号
手机版
RE:【MCU实战经验】向μC/OS-III在STM32F4xx上的移植中添加FPU支持
CPU_STK *OSTaskStkInit (OS_TASK_PTR p_task,# w) k3 b8 P1 M' {" r4 e9 d
void *p_arg,
CPU_STK *p_stk_base,: h8 m7 C3 ~/ S: A
CPU_STK *p_stk_limit,6 g& B; R- i! [) ?+ o# x
CPU_STK_SIZE stk_size,
OS_OPT opt) d" Z- V' y5 g9 ?9 I8 p
{5 G+ W$ X- @) ^3 R. v6 W. p
CPU_STK *p_stk;( M! {2 c$ I7 H% F4 ^4 p6 M
(void)opt; /* Prevent compiler warning */; z q" P9 _" o# U: w/ z3 z2 M
p_stk = &p_stk_base[stk_size]; /* Load stack pointer */
/* Align the stack to 8-bytes. */
p_stk = (CPU_STK *)((CPU_STK)(p_stk) & 0xFFFFFFF8);# J% A0 _/ V9 N/ C! z4 u
/* Registers stacked as if auto-saved on exception */% g& f& c7 h! J6 q4 q
#ifdef USE_FPU3 P3 J3 m- X) G. I3 Y0 v: d
*--p_stk = (CPU_STK)0xABCD1234u; /* Reserved */
*--p_stk = (CPU_STK)0x00000000u; /* FPSCR */8 q+ x# a' ~+ k
*--p_stk = (CPU_STK)0x7FC01515u; /* S15 */
*--p_stk = (CPU_STK)0x7FC01414u; /* S14 */. \% @* e# b* `: b9 _
*--p_stk = (CPU_STK)0x7FC01313u; /* S13 */
*--p_stk = (CPU_STK)0x7FC01212u; /* S12 */
*--p_stk = (CPU_STK)0x7FC01111u; /* S11 */
*--p_stk = (CPU_STK)0x7FC01010u; /* S10 */' ~' {/ a& ^0 g
*--p_stk = (CPU_STK)0x7FC00909u; /* S9 */
*--p_stk = (CPU_STK)0x7FC00808u; /* S8 */- O8 H; Y: F; W: n* b s& ]9 V; n& v
*--p_stk = (CPU_STK)0x7FC00707u; /* S7 */" d R( a( ^& v8 n
*--p_stk = (CPU_STK)0x7FC00606u; /* S6 */3 O( I3 M; ]! P$ q9 S7 t
*--p_stk = (CPU_STK)0x7FC00505u; /* S5 */* _, R% \, `3 D' b
*--p_stk = (CPU_STK)0x7FC00404u; /* S4 */ s- G3 c7 M' o j" V
*--p_stk = (CPU_STK)0x7FC00303u; /* S3 */
*--p_stk = (CPU_STK)0x7FC00202u; /* S2 */
*--p_stk = (CPU_STK)0x7FC00101u; /* S1 */
*--p_stk = (CPU_STK)0x7FC00000u; /* S0 */2 _; d1 ]) I8 G, `4 w6 X
#endif /* USE_FPU */) B' a+ T# n0 b# p4 F$ l
*--p_stk = (CPU_STK)0x01000000u; /* xPSR */0 c6 j$ v, j5 [- t, ^
*--p_stk = (CPU_STK)p_task; /* Entry Point */+ j; |3 U( }+ v0 Y t. Z
*--p_stk = (CPU_STK)OS_TaskReturn; /* R14 (LR) */1 A7 w% U6 U$ Z3 f* {1 t4 X$ ?
*--p_stk = (CPU_STK)0x12121212u; /* R12 */
*--p_stk = (CPU_STK)0x03030303u; /* R3 */' C! i: u" ~: K
*--p_stk = (CPU_STK)0x02020202u; /* R2 */$ h ]8 v# \ [& x; N; ]+ P9 m! Y/ D
*--p_stk = (CPU_STK)p_stk_limit; /* R1 */- r; d( o3 K3 m9 [' n% g8 m
*--p_stk = (CPU_STK)p_arg; /* R0 : argument */: w0 F! k! L4 J
/* Remaining registers saved on process stack */
#ifdef USE_FPU: A$ O- y$ n" R" y0 L8 f& E. e- @1 M# F
*--p_stk = (CPU_STK)0x7FC03131u; /* S31 */
*--p_stk = (CPU_STK)0x7FC03030u; /* S30 */
*--p_stk = (CPU_STK)0x7FC02929u; /* S29 */! J; s' y7 f+ C6 Y7 o' R( v6 k
*--p_stk = (CPU_STK)0x7FC02828u; /* S28 */
*--p_stk = (CPU_STK)0x7FC02727u; /* S27 */
*--p_stk = (CPU_STK)0x7FC02626u; /* S26 */
*--p_stk = (CPU_STK)0x7FC02525u; /* S25 */
*--p_stk = (CPU_STK)0x7FC02424u; /* S24 */' F& q0 O) ~ \0 l
*--p_stk = (CPU_STK)0x7FC02323u; /* S23 */- ~' F4 @7 }) O
*--p_stk = (CPU_STK)0x7FC02222u; /* S22 */
*--p_stk = (CPU_STK)0x7FC02121u; /* S21 */
*--p_stk = (CPU_STK)0x7FC02020u; /* S20 *// ?' f' m9 Q2 `, c8 {4 N- H
*--p_stk = (CPU_STK)0x7FC01919u; /* S19 */+ ]5 c9 T3 N% k5 {4 C# B/ t2 L
*--p_stk = (CPU_STK)0x7FC01818u; /* S18 */, n3 E- D* X2 B( B9 ?
*--p_stk = (CPU_STK)0x7FC01717u; /* S17 */
*--p_stk = (CPU_STK)0x7FC01616u; /* S16 */
#endif /* USE_FPU */
*--p_stk = (CPU_STK)0x11111111u; /* R11 */
*--p_stk = (CPU_STK)0x10101010u; /* R10 */3 M$ x# G3 S/ g" f5 i+ x! B
*--p_stk = (CPU_STK)0x09090909u; /* R9 */
*--p_stk = (CPU_STK)0x08080808u; /* R8 */
*--p_stk = (CPU_STK)0x07070707u; /* R7 */
*--p_stk = (CPU_STK)0x06060606u; /* R6 */4 o @/ u* S( h# c) e" d
*--p_stk = (CPU_STK)0x05050505u; /* R5 */
*--p_stk = (CPU_STK)0x04040404u; /* R4 */1 |3 }' ` |- k5 U2 S6 z
return (p_stk);
}
其中红色代码是新添加的处理浮点寄存器的代码。特别注意注释为Reserved的第2行红字,在任务栈中保存这个保留的32位字是必须的,其值没有特别要求,请参考ARMv7-M Architecture Reference Manual (DDI0403D)。
回复:【MCU实战经验】向μC/OS-III在STM32F4xx上的移植中添加FPU支持
OS_CPU_PendSVHandler
CPSID I ; Prevent interruption during context switch- f. G* n+ R7 {
MRS R0, PSP ; PSP is process stack pointer
CBZ R0, OS_CPU_PendSVHandler_nosave ; Skip register save the first time
3 l3 o3 g/ l4 |; j- ~8 \
IF
. J; @( T; T+ U% K9 y0 T2 a- A
VMRS R1, FPSCR ; Dummy read access to force FPU state preservation and FPSCR clear* G; _+ w( m, f- H, ], N% q
SUBS R0, R0, #0x40 ; Save remaining FP regs s16-s31 on process stack3 ~9 Q! t: r7 v, ~2 \# I7 B/ w
VSTM R0, {D8-D15}6 A7 }2 h% ]3 k
ENDIF
( l% E- M' |3 F# W* d) L
SUBS R0, R0, #0x20 ; Save remaining regs r4-11 on process stack! l' c5 V. ~7 `/ S
STM R0, {R4-R11}' \6 Q( ^9 Y, ~' E
LDR R1, =OSTCBCurPtr ; OSTCBCurPtr->OSTCBStkPtr = SP;
LDR R1, [R1]
STR R0, [R1] ; R0 is SP of process being switched out. R+ |- e L! V8 L6 [' M
8 a# `( O& q3 X9 l& w1 `7 U
; At this point, entire context of process has been saved- m. K) |6 o" m5 ^: C/ J& C7 D6 j$ L
OS_CPU_PendSVHandler_nosave
PUSH {R14} ; Save LR exc_return value
LDR R0, =OSTaskSwHook ; OSTaskSwHook();# p" w8 {# r! E$ q% w, _6 \3 S7 U
BLX R0
POP {R14}1 j7 w) w- N7 Z7 F2 m
LDR R0, =OSPrioCur ; OSPrioCur = OSPrioHighRdy;
LDR R1, =OSPrioHighRdy
LDRB R2, [R1]
STRB R2, [R0]
$ {" k2 m0 I& j. i2 h. ]3 ?9 W
LDR R0, =OSTCBCurPtr ; OSTCBCurPtr = OSTCBHighRdyPtr;0 g# l/ R& h8 b+ R, z; Z
LDR R1, =OSTCBHighRdyPtr
LDR R2, [R1]
STR R2, [R0]
' a) C9 ~# V, ~6 M: l. g
LDR R0, [R2] ; R0 is new process SP; SP = OSTCBHighRdyPtr->StkPtr;
LDM R0, {R4-R11} ; Restore r4-11 from new process stack/ G0 ?( b: x% p9 A4 w) F
ADDS R0, R0, #0x20
/ D9 K7 P' x# z0 {$ g) N6 R6 ~1 |' d
IF
VLDM R0, {D8-D15} ; Restore s16-s31 from new process stack( d" a" l v Y7 l- U/ J. }7 C
ADDS R0, R0, #0x40
; S1 W6 _5 V \$ e
ENDIF
MSR PSP, R0 ; Load PSP with new process SP/ m7 d) `9 q. A* C7 ~6 t! e4 v
ORR LR, LR, #0x04 ; Ensure exception return uses process stack
9 B, P( y5 \( g' M) H7 t1 {" W1 H
IF
5 f/ y' U% \5 `" J! U
AND LR, LR, #0xFFFFFFEF ; Clear LR to ensure FPU state restore
LDR R0, =0xE000EF34 ; Clear FPCCR (LSPACT) to ensure FPU state restore# I( x( i8 Y+ w
LDR R1, [R0]
AND R1, R1, #0xFFFFFFFE$ F/ K* {' \3 F+ u. ]: A- [
STR R1, [R0], q. \+ C1 ] X2 W
ENDIF
CPSIE I
BX LR ; Exception return will restore remaining context
其中红色代码是新添加的处理浮点寄存器的代码。几点说明:
1)根据FPCCR的设置值(就是复位值ASPEN=1, LSPEN=1),如果发生PendSV异常时CONTROL.FPCA=1,在进入PendSV异常处理函数时,硬件会自动在任务栈保留浮点寄存器占用的空间,首先通过读FPSCR寄存器让硬件自动保存浮点寄存器S0~S15和浮点状态寄存器FPSCR到任务栈,然后手动保存其余的浮点寄存器S16~S31。
2)在退出PendSV异常处理函数前,清除LR第4位并清除FPCCR寄存器第0位(LSPACT),目的是让硬件在退出PendSV异常处理函数时自动从任务栈恢复浮点寄存器S0~S15和浮点状态寄存器FPSCR。这样如果新任务是第一次运行,则可实现从任务栈加载浮点寄存器初值,否则是从任务栈加载以前保存的值,并且可以保证每个任务运行时都有CONTROL.FPCA=1。/ R0 ?' w1 r: c0 B; L" Z7 D q6 |
3)虽然使能了延迟保存浮点状态功能,但因为总是有CONTROL.FPCA=1,因此无论旧任务是否执行过浮点指令,在进入PendSV异常处理函数执行任务切换时,都会保存旧任务的浮点寄存器,加载新任务的浮点寄存器,没有利用延迟保存浮点状态功能可减小中断延迟的优势。
RE:【MCU实战经验】向μC/OS-III在STM32F4xx上的移植中添加FPU支持
回复:【MCU实战经验】向μC/OS-III在STM32F4xx上的移植中添加FPU支持
回复:【MCU实战经验】向μC/OS-III在STM32F4xx上的移植中添加FPU支持
谢谢,在F407VG上通过
RE:【MCU实战经验】向μC/OS-III在STM32F4xx上的移植中添加FPU支持