10.07.2015 Views

Carbon Cortex-A15 Model User Guide for SoC Designer

Carbon Cortex-A15 Model User Guide for SoC Designer

Carbon Cortex-A15 Model User Guide for SoC Designer

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1-2 Using the <strong>Model</strong> Kit Component in <strong>SoC</strong> <strong>Designer</strong> PlusThis section provides a summary of the functionality of the model compared to that of thehardware, and the per<strong>for</strong>mance and accuracy of the model.• Implemented Hardware Features• Hardware Features not Implemented• Features Additional to the Hardware1.1.1 Implemented Hardware FeaturesMost hardware features have been implemented. Some functionality and register pin differencesare listed in the next section.Note that when using semihosting you must use the semihost component from <strong>Carbon</strong>.This “<strong>Carbon</strong>Semihost” component is included in the <strong>Carbon</strong> <strong>SoC</strong> <strong>Designer</strong> Plus Standard<strong>Model</strong> Library, version 3.0 or greater. The ARM RVML semihost component will notwork with the <strong>Carbon</strong> <strong>Model</strong>.See the ARM <strong>Cortex</strong>-<strong>A15</strong> Technical Reference Manual <strong>for</strong> more in<strong>for</strong>mation.1.1.2 Hardware Features not ImplementedThe following features of the <strong>Cortex</strong>-<strong>A15</strong> hardware are not implemented in the <strong>Carbon</strong>izedmodel:• Debug access to virtual memory does not currently handle TLB lockdown.• Debug transactions do not fully support cache coherence. This means that the debugtransaction could read or write data without realizing that it is accessing data thatresides in the other cores’ caches. Debug transactions are needed by RVD accesses tomemory, as well as by semihosting. If you see a different memory value from RVDthan what you see by opening the Memory view in the processor and memory, thenyour design may have encountered this limitation.• Some registers are read-only. See the section “Register In<strong>for</strong>mation” on page 1-12 <strong>for</strong>more in<strong>for</strong>mation.• The registers in Table 1-1 on page 1-3 are not available to be read/written via debugtransactions — <strong>for</strong> example, in the <strong>SoC</strong> <strong>Designer</strong> Plus Registers window, or byaccessing them directly from RealView Debugger.The functionality of these registers, however, does exist and can be accessed by softwarerunning on the virtual plat<strong>for</strong>m.<strong>Carbon</strong> Design Systems, Inc. Confidential

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!