• Locked Locked
  • Replies 11 replies
  • Subscribers 119 subscribers
  • Views 6740 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARM FastModels for TrustZone Development

Earlence Fernandes
Note: This was originally posted on 22nd August 2013 at http://forums.arm.com

I am trying to learn about TrustZone and I've downloaded the FastModels 8.1 simulator.
The license I can obtain is only for the Cortex A8 Eval Board, and The ref manual for FastModels implies that
no trust zone is built in.

Which fast model I can use to experiment with trust zone?
How do I get the required evaluation license? I am a student and have a .edu email address?
Anyone else with similar experience? My first step is to boot a linux kernel in secure world.

-Earlence
Parents
  • Arm Employee Badge
    Note: This was originally posted on 27th August 2013 at http://forums.arm.com


    Are these the 2 secure ranges?

    0x0000000000..0x0007FFFFFF (128MB))
    0x007E000000..0x007FFFFFFF (32MB)

    I'm wondering why did they split it up like this?


    Also, lower down in the lisa file, it seems that if a secure access is made on a non-secure region, then an abort occurs.
    This means that the normal and secure worlds are completely isolated? Even secure cannot see all memory?

    -Earlence



    At a quick look, those 2 regions are configured to allow secure accesses and deny NS access. Assuming you have set the secure_memory parameter to TRUE.

    For this configuration, yes the TZSwitch does appear to deny S access to a NS region. That is just a configuration of VE - it is easily changed to let you have all memory accessible to S and only some accessible to NS access.

    As to why this configuration was chosen for the VE platform, I would have to ask the designer.

    Chris


Reply
  • Arm Employee Badge
    Note: This was originally posted on 27th August 2013 at http://forums.arm.com


    Are these the 2 secure ranges?

    0x0000000000..0x0007FFFFFF (128MB))
    0x007E000000..0x007FFFFFFF (32MB)

    I'm wondering why did they split it up like this?


    Also, lower down in the lisa file, it seems that if a secure access is made on a non-secure region, then an abort occurs.
    This means that the normal and secure worlds are completely isolated? Even secure cannot see all memory?

    -Earlence



    At a quick look, those 2 regions are configured to allow secure accesses and deny NS access. Assuming you have set the secure_memory parameter to TRUE.

    For this configuration, yes the TZSwitch does appear to deny S access to a NS region. That is just a configuration of VE - it is easily changed to let you have all memory accessible to S and only some accessible to NS access.

    As to why this configuration was chosen for the VE platform, I would have to ask the designer.

    Chris


Children
No data