d

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 
614件の閲覧回数
dungwang
Contributor I
0 件の賞賛
返信
1 解決策
455件の閲覧回数
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 返信
456件の閲覧回数
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