d

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决
907 次查看
dungwang
Contributor I

e

0 项奖励
回复
1 解答
748 次查看
BlackNight
NXP Employee
NXP Employee

Hello Dung,

the reason is that on Kinetis K there are two memory controllers, one for each memory area. Because it can cause a hard fault if you are accessing the memory boundary with an unaligned access, the two memory areas are splitted. If you ensure that you do not have any misaligned access, you can combine the two areas. See the comments section of FreeRTOS Heap with Segmented Kinetis K SRAM | MCU on Eclipse  for a detailed discusson on that topic.

I hpe this helps,

Erich

在原帖中查看解决方案

1 回复
749 次查看
BlackNight
NXP Employee
NXP Employee

Hello Dung,

the reason is that on Kinetis K there are two memory controllers, one for each memory area. Because it can cause a hard fault if you are accessing the memory boundary with an unaligned access, the two memory areas are splitted. If you ensure that you do not have any misaligned access, you can combine the two areas. See the comments section of FreeRTOS Heap with Segmented Kinetis K SRAM | MCU on Eclipse  for a detailed discusson on that topic.

I hpe this helps,

Erich