You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@teaclave.apache.org by ms...@apache.org on 2021/10/19 20:19:26 UTC
[incubator-teaclave-trustzone-sdk] branch rww-doc created (now
7d4a1f2)
This is an automated email from the ASF dual-hosted git repository.
mssun pushed a change to branch rww-doc
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git.
at 7d4a1f2 Delete trailing whitespaces
This branch includes the following new commits:
new 966c4fa add debug-optee-ta.md
new d63d53a modify according to comments
new 961eb8d modify docs/README.md
new 7d4a1f2 Delete trailing whitespaces
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@teaclave.apache.org
For additional commands, e-mail: commits-help@teaclave.apache.org
[incubator-teaclave-trustzone-sdk] 03/04: modify docs/README.md
Posted by ms...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mssun pushed a commit to branch rww-doc
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git
commit 961eb8d7f4cd78d142cabbfd8f56cc2345713fdc
Author: rmheng <29...@qq.com>
AuthorDate: Tue Oct 19 03:45:00 2021 +0000
modify docs/README.md
---
docs/README.md | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/docs/README.md b/docs/README.md
index 869c82f..cf8bcfa 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -4,12 +4,6 @@ permalink: /trustzone-sdk-docs
# Teaclave TrustZone SDK Documentation
-<<<<<<< HEAD
* [Getting Started with OPTEE for QEMU ARMv8](getting-started-with-optee-for-qemu-armv8.md)
* [Overview of OP-TEE Rust Examples](overview-of-optee-rust-examples.md)
-* [Debug OP-TEE TA](debug-optee-ta.md)
-=======
-* [Getting Started with OPTEE for QEMU ARMv8](/trustzone-sdk-docs/getting-started-with-optee-for-qemu-armv8)
-* [Overview of OP-TEE Rust Examples](/trustzone-sdk-docs/overview-of-optee-rust-examples)
-* [Debug OP-TEE TA](debugging-optee-ta.md)
->>>>>>> modify according to comments
+* [Debugging OP-TEE TA](debugging-optee-ta.md)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@teaclave.apache.org
For additional commands, e-mail: commits-help@teaclave.apache.org
[incubator-teaclave-trustzone-sdk] 04/04: Delete trailing
whitespaces
Posted by ms...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mssun pushed a commit to branch rww-doc
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git
commit 7d4a1f2f47b18ad935a0c900e182cd6cfd3408f1
Author: Mingshen Sun <bo...@mssun.me>
AuthorDate: Tue Oct 19 13:18:52 2021 -0700
Delete trailing whitespaces
---
docs/debugging-optee-ta.md | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/docs/debugging-optee-ta.md b/docs/debugging-optee-ta.md
index 54ebba8..7425428 100644
--- a/docs/debugging-optee-ta.md
+++ b/docs/debugging-optee-ta.md
@@ -2,26 +2,26 @@
permalink: /trustzone-sdk-docs/debugging-optee-ta.md
---
-# Debugging OP-TEE TA
+# Debugging OP-TEE TA
-When developing applications, it is inevitable that there will be a need for
-debugging. This tutorial introduces how to configure the debug environment in
-OP-TEE enabled QEMU environment. You may also check
-[OP-TEE documentation](https://optee.readthedocs.io/en/latest/building/devices/qemu.html)
+When developing applications, it is inevitable that there will be a need for
+debugging. This tutorial introduces how to configure the debug environment in
+OP-TEE enabled QEMU environment. You may also check
+[OP-TEE documentation](https://optee.readthedocs.io/en/latest/building/devices/qemu.html)
for more information about running QEMU for Arm v8.
-To debug TEE core running QEMU with GDB, it is necessary to disable TEE ASLR with
-`CFG_CORE_ASLR ?= n` in `OP-TEE/optee_os/mk/config.mk`. Note that you need to
-recompile QEMU with `make run` again. You can also choose to add the compilation
+To debug TEE core running QEMU with GDB, it is necessary to disable TEE ASLR with
+`CFG_CORE_ASLR ?= n` in `OP-TEE/optee_os/mk/config.mk`. Note that you need to
+recompile QEMU with `make run` again. You can also choose to add the compilation
information directly at compile time.
```sh
$ make run CFG_CORE_ASLR=n
```
-Since we will debug the TA remotely with a `gdb` server, please also add the
+Since we will debug the TA remotely with a `gdb` server, please also add the
`GDBSERVER=y` flag when compiling QEMU.
-To debug a TA, you need to first start a gdb on the host machine. Then run
+To debug a TA, you need to first start a gdb on the host machine. Then run
`target remote :1234` to connect to the remote QEMU GDB server.
```sh
@@ -37,7 +37,7 @@ Next, in the GDB console, load the symbol table of the TEE core library.
```sh
(gdb) symbol-file /path/to/qemu-v8-project/optee_os/out/arm/core/tee.elf
```
-Taking `hello_world-rs` as an example, you can get the start address of the text
+Taking `hello_world-rs` as an example, you can get the start address of the text
section from the log in the secure world console, which is 0x40014000.
```sh
@@ -48,13 +48,13 @@ Then, you can load symbols from TA file (in debug build) to the address.
```sh
(gdb) add-symbol-file /path/to/examples/hello_world-rs/ta/target/aarch64-unknown-optee-trustzone/debug/ta 0x40014000
```
-Now, you can add breakpoints according to your own needs in the corresponding
+Now, you can add breakpoints according to your own needs in the corresponding
functions or addresses.
```sh
(gdb) b invoke_command
Breakpoint 2 at 0xe11bb08: invoke_command. (6 locations)
```
-Last, initiate the boot. You can execute `hello_world-rs` in the normal world
+Last, initiate the boot. You can execute `hello_world-rs` in the normal world
console, and will see that the breakpoint we set was hit.
```sh
(gdb) c
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@teaclave.apache.org
For additional commands, e-mail: commits-help@teaclave.apache.org
[incubator-teaclave-trustzone-sdk] 02/04: modify according to
comments
Posted by ms...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mssun pushed a commit to branch rww-doc
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git
commit d63d53a463c0e8238b71215435e43745411a5ab7
Author: rmheng <29...@qq.com>
AuthorDate: Tue Oct 19 03:40:43 2021 +0000
modify according to comments
---
docs/README.md | 6 +++++
docs/debug-optee-ta.md | 57 ---------------------------------------
docs/debugging-optee-ta.md | 66 ++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 72 insertions(+), 57 deletions(-)
diff --git a/docs/README.md b/docs/README.md
index 792a7d7..869c82f 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -4,6 +4,12 @@ permalink: /trustzone-sdk-docs
# Teaclave TrustZone SDK Documentation
+<<<<<<< HEAD
* [Getting Started with OPTEE for QEMU ARMv8](getting-started-with-optee-for-qemu-armv8.md)
* [Overview of OP-TEE Rust Examples](overview-of-optee-rust-examples.md)
* [Debug OP-TEE TA](debug-optee-ta.md)
+=======
+* [Getting Started with OPTEE for QEMU ARMv8](/trustzone-sdk-docs/getting-started-with-optee-for-qemu-armv8)
+* [Overview of OP-TEE Rust Examples](/trustzone-sdk-docs/overview-of-optee-rust-examples)
+* [Debug OP-TEE TA](debugging-optee-ta.md)
+>>>>>>> modify according to comments
diff --git a/docs/debug-optee-ta.md b/docs/debug-optee-ta.md
deleted file mode 100644
index e5b5630..0000000
--- a/docs/debug-optee-ta.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-permalink: /trustzone-sdk-docs/debug-optee-ta.md
----
-
-# Debug OP-TEE TA
-
-When developing applications, it is inevitable that there will be a need for debugging. This tutorial introduces how to configure debug environment in OP-TEE enabled QEMU environment. You may also check [OP-TEE documentation](https://optee.readthedocs.io/en/latest/building/devices/qemu.html) for more information about running QEMU for Arm v8.
-
-To debug TEE core running QEMU with GDB, it is necessary to disable TEE ASLR with `CFG_CORE_ASLR ?= n` in `OP-TEE/optee_os/mk/config.mk`. Note that then recompile with `make run`. You can also choose to add compilation information directly at compile time.
-```sh
-$ make run CFG_CORE_ASLR=n
-```
-
-Since the program is debugged on your PC, while the program being debugged runs in the QEMU environment, this should be added at compile time: `GDBSERVER=y`.
-
-After starting GDB, executing `target remote :1234` in the normal world console to connect to QEMU GDB server.
-
-```sh
-$ ./path/to/qemu-v8-project/out-br/host/bin/aarch64-buildroot-linux-gnu-gdb
-(gdb) target remote :1234
-Remote debugging using :1234
-warning: No executable has been specified and target does not support
-determining executable automatically. Try using the "file" command.
-0xffffb30b00ea12b4 in ?? ()
-```
-Next, in the GDB console, load the symbol table for TEE.
-
-```sh
-(gdb) symbol-file /path/to/qemu-v8-project/optee_os/out/arm/core/tee.elf
-```
-Taking `hello_world-rs` as an example, you can know as prompted in the secure world console, the start address of TA text is 0x40014000.
-
-```sh
-D/LD: ldelf:168 ELF (133af0ca-bdab-11eb-9130-43bf7873bf67) at 0x40014000
-```
-
-Then, you can load TA symbol table from the address.
-```sh
-(gdb) add-symbol-file /path/to/examples/hello_world-rs/ta/target/aarch64-unknown-optee-trustzone/debug/ta 0x40014000
-```
-Now, you can add breakpoints according to your own needs in the corresponding functions or addresses.
-```sh
-(gdb) b invoke_command
-Breakpoint 2 at 0xe11bb08: invoke_command. (6 locations)
-```
-Last, initiate the boot. You can execute `hello_world-rs` in the normal world console, and will see that the breakpoint we set was hit.
-```sh
-(gdb) c
-Continuing.
-[Switching to Thread 1.2]
-
-Thread 2 hit Breakpoint 2, ta::invoke_command (cmd_id=0, params=0x4010ff00) at src/main.rs:50
-50 trace_println!("[+] TA invoke command");
-```
-
-
-
diff --git a/docs/debugging-optee-ta.md b/docs/debugging-optee-ta.md
new file mode 100644
index 0000000..54ebba8
--- /dev/null
+++ b/docs/debugging-optee-ta.md
@@ -0,0 +1,66 @@
+---
+permalink: /trustzone-sdk-docs/debugging-optee-ta.md
+---
+
+# Debugging OP-TEE TA
+
+When developing applications, it is inevitable that there will be a need for
+debugging. This tutorial introduces how to configure the debug environment in
+OP-TEE enabled QEMU environment. You may also check
+[OP-TEE documentation](https://optee.readthedocs.io/en/latest/building/devices/qemu.html)
+for more information about running QEMU for Arm v8.
+
+To debug TEE core running QEMU with GDB, it is necessary to disable TEE ASLR with
+`CFG_CORE_ASLR ?= n` in `OP-TEE/optee_os/mk/config.mk`. Note that you need to
+recompile QEMU with `make run` again. You can also choose to add the compilation
+information directly at compile time.
+```sh
+$ make run CFG_CORE_ASLR=n
+```
+
+Since we will debug the TA remotely with a `gdb` server, please also add the
+`GDBSERVER=y` flag when compiling QEMU.
+
+To debug a TA, you need to first start a gdb on the host machine. Then run
+`target remote :1234` to connect to the remote QEMU GDB server.
+
+```sh
+$ ./path/to/qemu-v8-project/out-br/host/bin/aarch64-buildroot-linux-gnu-gdb
+(gdb) target remote :1234
+Remote debugging using :1234
+warning: No executable has been specified and target does not support
+determining executable automatically. Try using the "file" command.
+0xffffb30b00ea12b4 in ?? ()
+```
+Next, in the GDB console, load the symbol table of the TEE core library.
+
+```sh
+(gdb) symbol-file /path/to/qemu-v8-project/optee_os/out/arm/core/tee.elf
+```
+Taking `hello_world-rs` as an example, you can get the start address of the text
+section from the log in the secure world console, which is 0x40014000.
+
+```sh
+D/LD: ldelf:168 ELF (133af0ca-bdab-11eb-9130-43bf7873bf67) at 0x40014000
+```
+
+Then, you can load symbols from TA file (in debug build) to the address.
+```sh
+(gdb) add-symbol-file /path/to/examples/hello_world-rs/ta/target/aarch64-unknown-optee-trustzone/debug/ta 0x40014000
+```
+Now, you can add breakpoints according to your own needs in the corresponding
+functions or addresses.
+```sh
+(gdb) b invoke_command
+Breakpoint 2 at 0xe11bb08: invoke_command. (6 locations)
+```
+Last, initiate the boot. You can execute `hello_world-rs` in the normal world
+console, and will see that the breakpoint we set was hit.
+```sh
+(gdb) c
+Continuing.
+[Switching to Thread 1.2]
+
+Thread 2 hit Breakpoint 2, ta::invoke_command (cmd_id=0, params=0x4010ff00) at src/main.rs:50
+50 trace_println!("[+] TA invoke command");
+```
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@teaclave.apache.org
For additional commands, e-mail: commits-help@teaclave.apache.org
[incubator-teaclave-trustzone-sdk] 01/04: add debug-optee-ta.md
Posted by ms...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mssun pushed a commit to branch rww-doc
in repository https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git
commit 966c4fa84a7fbf24b48f9fce72fa4c3cf643c9dc
Author: rmheng <29...@qq.com>
AuthorDate: Sat Oct 16 06:31:02 2021 +0000
add debug-optee-ta.md
---
docs/README.md | 1 +
docs/debug-optee-ta.md | 57 ++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 58 insertions(+)
diff --git a/docs/README.md b/docs/README.md
index 81bf4a9..792a7d7 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -6,3 +6,4 @@ permalink: /trustzone-sdk-docs
* [Getting Started with OPTEE for QEMU ARMv8](getting-started-with-optee-for-qemu-armv8.md)
* [Overview of OP-TEE Rust Examples](overview-of-optee-rust-examples.md)
+* [Debug OP-TEE TA](debug-optee-ta.md)
diff --git a/docs/debug-optee-ta.md b/docs/debug-optee-ta.md
new file mode 100644
index 0000000..e5b5630
--- /dev/null
+++ b/docs/debug-optee-ta.md
@@ -0,0 +1,57 @@
+---
+permalink: /trustzone-sdk-docs/debug-optee-ta.md
+---
+
+# Debug OP-TEE TA
+
+When developing applications, it is inevitable that there will be a need for debugging. This tutorial introduces how to configure debug environment in OP-TEE enabled QEMU environment. You may also check [OP-TEE documentation](https://optee.readthedocs.io/en/latest/building/devices/qemu.html) for more information about running QEMU for Arm v8.
+
+To debug TEE core running QEMU with GDB, it is necessary to disable TEE ASLR with `CFG_CORE_ASLR ?= n` in `OP-TEE/optee_os/mk/config.mk`. Note that then recompile with `make run`. You can also choose to add compilation information directly at compile time.
+```sh
+$ make run CFG_CORE_ASLR=n
+```
+
+Since the program is debugged on your PC, while the program being debugged runs in the QEMU environment, this should be added at compile time: `GDBSERVER=y`.
+
+After starting GDB, executing `target remote :1234` in the normal world console to connect to QEMU GDB server.
+
+```sh
+$ ./path/to/qemu-v8-project/out-br/host/bin/aarch64-buildroot-linux-gnu-gdb
+(gdb) target remote :1234
+Remote debugging using :1234
+warning: No executable has been specified and target does not support
+determining executable automatically. Try using the "file" command.
+0xffffb30b00ea12b4 in ?? ()
+```
+Next, in the GDB console, load the symbol table for TEE.
+
+```sh
+(gdb) symbol-file /path/to/qemu-v8-project/optee_os/out/arm/core/tee.elf
+```
+Taking `hello_world-rs` as an example, you can know as prompted in the secure world console, the start address of TA text is 0x40014000.
+
+```sh
+D/LD: ldelf:168 ELF (133af0ca-bdab-11eb-9130-43bf7873bf67) at 0x40014000
+```
+
+Then, you can load TA symbol table from the address.
+```sh
+(gdb) add-symbol-file /path/to/examples/hello_world-rs/ta/target/aarch64-unknown-optee-trustzone/debug/ta 0x40014000
+```
+Now, you can add breakpoints according to your own needs in the corresponding functions or addresses.
+```sh
+(gdb) b invoke_command
+Breakpoint 2 at 0xe11bb08: invoke_command. (6 locations)
+```
+Last, initiate the boot. You can execute `hello_world-rs` in the normal world console, and will see that the breakpoint we set was hit.
+```sh
+(gdb) c
+Continuing.
+[Switching to Thread 1.2]
+
+Thread 2 hit Breakpoint 2, ta::invoke_command (cmd_id=0, params=0x4010ff00) at src/main.rs:50
+50 trace_println!("[+] TA invoke command");
+```
+
+
+
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@teaclave.apache.org
For additional commands, e-mail: commits-help@teaclave.apache.org