Arm Community
Site
Search
User
Site
Search
User
Groups
Education Hub
Distinguished Ambassadors
Open Source Software and Platforms
Research Collaboration and Enablement
Forums
AI and ML forum
Architectures and Processors forum
Arm Development Platforms forum
Arm Development Studio forum
Arm Virtual Hardware forum
Automotive forum
Compilers and Libraries forum
Graphics, Gaming, and VR forum
High Performance Computing (HPC) forum
Infrastructure Solutions forum
Internet of Things (IoT) forum
Keil forum
Morello forum
Operating Systems forum
SoC Design and Simulation forum
SystemReady Forum
Blogs
AI and ML blog
Announcements
Architectures and Processors blog
Automotive blog
Graphics, Gaming, and VR blog
High Performance Computing (HPC) blog
Infrastructure Solutions blog
Internet of Things (IoT) blog
Operating Systems 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
118 subscribers
Views
4358 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 10 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
Martin Weidmann
over 10 years ago
Note: This was originally posted on 5th January 2013 at
http://forums.arm.com
Your problem is that the two boards probably have different memory maps. So the Versatile has RAM at 0x80000000, I'm guessing the Xilinx board has it somewhere else.
The example will be making assumptions about where things like RAM are, for example to allocate stack memory. As the two boards are different it's falling over (looks like while trying to load)
When you're working with apps, the OS hides the differences between systems (true for ARM, x86, etc...). But when you have bare metal code you'll need to do some level of porting when moving code from one board to another. At the most basic, re-link to match the address of memory.
The example you're using is quiet simple. So I suspect it wouldn't take too much effort to port. Probably just need to change the scatter files and re-link.
Cancel
Up
0
Down
Cancel
Reply
Martin Weidmann
over 10 years ago
Note: This was originally posted on 5th January 2013 at
http://forums.arm.com
Your problem is that the two boards probably have different memory maps. So the Versatile has RAM at 0x80000000, I'm guessing the Xilinx board has it somewhere else.
The example will be making assumptions about where things like RAM are, for example to allocate stack memory. As the two boards are different it's falling over (looks like while trying to load)
When you're working with apps, the OS hides the differences between systems (true for ARM, x86, etc...). But when you have bare metal code you'll need to do some level of porting when moving code from one board to another. At the most basic, re-link to match the address of memory.
The example you're using is quiet simple. So I suspect it wouldn't take too much effort to port. Probably just need to change the scatter files and re-link.
Cancel
Up
0
Down
Cancel
Children
No data