Arm Community
Site
Search
User
Site
Search
User
Arm Developer
Documentation
Learning Paths
On-Demand Videos
Groups
Arm Ambassadors
Education Hub
Open Source Software and Platforms
Research Collaboration and Enablement
Forums
AI forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Automotive forum
Compilers and Libraries forum
Embedded and Microcontrollers forum
High Performance Computing (HPC) forum
Internet of Things (IoT) forum
Keil forum
Laptops and Desktops forum
Mobile, Graphics, and Gaming forum
Morello forum
Operating Systems forum
Servers and Cloud Computing forum
SoC Design and Simulation forum
SystemReady Forum
Blogs
AI blog
Announcements
Architectures and Processors blog
Automotive blog
Embedded and Microcontrollers blog
Internet of Things (IoT) blog
Laptops and Desktops blog
Mobile, Graphics, and Gaming blog
Operating Systems blog
Servers and Cloud Computing blog
SoC Design and Simulation blog
Tools, Software and IDEs blog
Support
Arm Support Services
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Support forums
Arm Development Studio forum
Running TrustZone
Jump...
Cancel
Locked
Locked
Replies
3 replies
Subscribers
120 subscribers
Views
4588 views
Users
0 members are here
Options
Share
More actions
Cancel
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
Running TrustZone
Andreas Lauber
over 11 years ago
Note: This was originally posted on 4th January 2013 at
http://forums.arm.com
Hallo,
I'm trying to run the TrustZone example from DS-5. And it's working with the RTSM-VE-A9x4. But this is just a simulation, isn't it. Because I do not have to power up DSTREAM and my board.
So I tried some more to run the example on the Xilinx Zynq board which has a ARM Cortex A9 DualCore.
BUT: If I'm using "Debug Cortex_A9_0 via DSTREAM/RVI" from Xilinx-Zynq-7000 EEP ZC702 its not working anymore. I used the connection with a hello world program before so it's defiantly the right connection. I also added
add-symbol-file "${workspace_loc:/TrustZone/normal.axf}" N:0
in execute debugger commands like it is in the RTSM version.
Nevertheless I get the following error if I want to debug the software on the ARM.
ERROR(CMD16-TAD11-NAL22):
! Failed to load "TrustZone-versatile.axf"
! Failed to write 4.872 bytes to address S:0x80000000
! General error on memory or register access.
I know the example was written for versatile express, but its also just a Cortex A9. So where is the difference? What did I forgot to change? I would be happy about some ideas.
Parents
Andreas Lauber
over 11 years ago
Note: This was originally posted on 7th January 2013 at
http://forums.arm.com
Hey ttfn,
thanks for your help. I know moved the software to the OCM and it looked like it's going to work.
I could also run the code in the secure mode.
But unfortunately as soon as I'm swithing in the non-secure mode the software crashs. As far as I see its because the regin of the non-secure software is still marked as secure. So for example I copied the code with the scatter file to 0x18000 and its there but if I have a look at the memory it says S:0x18000. This means I cannot access it from normal world.
So here comes the question: How can I make the memory from 0x18000 to 0x30000 as non-secure. I don't see any point in the scatter files and startup files.
But I guess there has to be a way...
Thx
Cancel
Vote up
0
Vote down
Cancel
Reply
Andreas Lauber
over 11 years ago
Note: This was originally posted on 7th January 2013 at
http://forums.arm.com
Hey ttfn,
thanks for your help. I know moved the software to the OCM and it looked like it's going to work.
I could also run the code in the secure mode.
But unfortunately as soon as I'm swithing in the non-secure mode the software crashs. As far as I see its because the regin of the non-secure software is still marked as secure. So for example I copied the code with the scatter file to 0x18000 and its there but if I have a look at the memory it says S:0x18000. This means I cannot access it from normal world.
So here comes the question: How can I make the memory from 0x18000 to 0x30000 as non-secure. I don't see any point in the scatter files and startup files.
But I guess there has to be a way...
Thx
Cancel
Vote up
0
Vote down
Cancel
Children
No data