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

I need some information about trustzone

Note: This was originally posted on 19th July 2013 at http://forums.arm.com

Hello there everyone,
Greetings!

I am Partho Paul, from India, Chennai. and I am here for some information. And this also happens to be my first post in the arm.com forums.
And my english is broken with loads and loads of grammar and spelling mistakes. kindly forgive me of those errors.

I will not try to beat around the bush, but this is what I am trying to do and this is my plan.
I am planning to port coreboot (www.coreboot.org) to blackberry playbook, which is omap4430 HS device. Which i plan to showcase in the GSOC14.
I have gathered most of the info regarding how to xloader and u-boot and etc etc.

Now I have a little confusion. First off I need some information about jtag and how do I proceed. I think, I have found the jtag pin outs and this Sunday I will give a try with jtag.
So now here is my real question. can I program the trusted zone?

If I understand correctly then the volatile SRAM holds the UUID and RSA metadata and SHA256 sum.

Can someone point me where am I making a blunder and help me from not doing a suicidal blunder. What should be my proper approach?

The arm documents says using proper tools i can modify the secure areas but i want to know which proper tools.
I got a wiggler jtag and buspirate to do the debugging and now how do i proceed. this will be my first question.

And my second question will be, how do i reprogram the efuse. Because the arm documents said i can reprogram the efuse. and there are loads of information there like SPIDEN and SPNIDEN and SUIDEN and SUNIDEN. and there is this secure_boot_lock can be set to 0 = low and 1 = high.

How do i do it in real life?

Because too much information got me a little lost.

I am not doing this for financial gain because i wish to be in the GSOC 2014, since all my proposals till date been rejected. Can someone please help me?

thanks!
-paul

partho paul over 11 years ago

Note: This was originally posted on 21st July 2013 at http://forums.arm.com

hi isogen74,
first off thanks for answering my questions.
i did contact TI all i got was 6000 pages of tonnes of information and no information on security at all.
debugging info was there but no debug info on hs registers.
those high security registers are safely stored in their vault i guess.

so this leaves me or forces me to ask the taboo question. may i?

how about reverse engineering. is reverse engineering talk/discussions allowed?
can i reverse engineer the process and then post in here and ask for help? and allowed?
this is strictly academic. and carries the GPL since its coreboot and also gsoc.
do i have the liberty and freedom to discuss those. especially the assembly code!
and if its allowed to post the assembly code its till how much.
since i find assembly and debugging information in the documents themselves.
does it mean that i have the liberty of doing it and posting the results and values and asking users their feedback?
thanks!
-paul
Cancel
Vote up 0 Vote down

Cancel
Peter Harris over 11 years ago

Note: This was originally posted on 20th July 2013 at http://forums.arm.com

There are many ways TrustZone can be used - it is really a pile of security building blocks which ARM's customers use to build custom security environments. The ARM documents you have found explain how the individual pieces work, and some possible configurations of them, but it is down to ARM's customers to build the production security environment.

If you have a particular chipset in mind such as OMAP, I would check on the vendor forums; they are likely to have more data about how their actual system is built and configured.

Sorry that's not more use!

Iso
Cancel
Vote up 0 Vote down

Cancel