Errata on Vybrid Reference Manual Rev 7, 06/2014

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Errata on Vybrid Reference Manual Rev 7, 06/2014

ソリューションへジャンプ
813件の閲覧回数
hmyoong
Contributor III

Page 186 of "Vybrid Reference Manual" Rev 7, 06/2014, the size of the memory is not 0.448 but 0.4375.

errata.jpg

Is the address range from 0x40070000 to 0x4007BFFFF allocated?

タグ(2)
0 件の賞賛
1 解決策
618件の閲覧回数
CommunityBot
Community Manager
This an automatic process.

We are marking this post as solved, due to the either low activity or any reply marked as correct.

If you have additional questions, please create a new post and reference to this closed post.

NXP Community!

元の投稿で解決策を見る

0 件の賞賛
4 返答(返信)
619件の閲覧回数
CommunityBot
Community Manager
This an automatic process.

We are marking this post as solved, due to the either low activity or any reply marked as correct.

If you have additional questions, please create a new post and reference to this closed post.

NXP Community!
0 件の賞賛
619件の閲覧回数
hmyoong
Contributor III

errata2.jpg

I think there is also an error in the image above.

0 件の賞賛
619件の閲覧回数
billpringlemeir
Contributor V

I think this one makes sense.  0xe0000000-0xffffffff is the CM4 PPB on the M4.  For the A5, this is an alias to the DDR.  Each CPU sees a different peripheral in this case.  Most of the time, the peripheral addresses are the same, so it seems odd until you divine what they are talking about.  I think the manual might be clearer to show common peripheral addresses followed by the CPU private addresses.  Then the column with mostly repeated information wouldn't be needed.  Thank goodness they don't have the same peripheral at different addresses on each CPU.

0 件の賞賛
619件の閲覧回数
jiri-b36968
NXP Employee
NXP Employee

Hi Yoong,

yes correct it would be:

0xE000_0000 - 0xE00F_FFFF     CM4 Private Peripheral Bus (PPB)

0xE010_0000 - 0xFFFF_FFFF     Reserved

You are right 0x70000 bytes are 458,752 bytes, 458,752 / 1024 is 448kB - this would be correct. 0.xxx MB generally is not correct. If used then 0.4375 is less wrong. Will make note in shared review.

regarding 0x40070000 please look in secure RM.

/Jiri