ARMmbed
/
mbed-os
mirror of https://github.com/ARMmbed/mbed-os.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Copy edit REAMDE.md 

Copy edit file, mostly for active voice and consistent spelling.
pull/8479/head
Amanda Butler 2018-10-04 16:55:36 -05:00 committed by adbridge
parent ab3fb4357e
commit 2cd2292451
1 changed files with 18 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
targets/TARGET_NUVOTON/TARGET_M2351/TARGET_NUMAKER_PFM_M2351/TARGET_M23_NS/README.md
View File

@ -1,36 +1,30 @@
# Default secure code for M2351
M2351 is a TrustZone target which requires two codes: secure and non-secure.
Secure code would run first to set up secure environment and then bring up non-secure code.
`NuMaker-mbed-TZ-secure-example.hex` is the default secure code and `cmse_lib.o` is its accompanying
secure gateway library which exports secure functions to non-secure code. It is built from
[secure code template](https://github.com/OpenNuvoton/NuMaker-mbed-TZ-secure-example).
With secure/non-secure code possibly not starting at address `0x0`, `.hex` rather than `.bin` is
chosen as output format.
The M2351 is a TrustZone target that requires two codes: secure and nonsecure. Secure code runs first to set up the secure environment and then brings up the nonsecure code. `NuMaker-mbed-TZ-secure-example.hex` is the default secure code, and `cmse_lib.o` is its accompanying
secure gateway library, which exports secure functions to nonsecure code. It is built from the [secure code template](https://github.com/OpenNuvoton/NuMaker-mbed-TZ-secure-example). Because secure and nonsecure code may start at an address other than `0x0`, we have chosen `.hex` rather than `.bin` as the output format.
## Hardware partition
On TrustZone targets, it is necessary to partition the hardware first for secure/non-secure code
to run on secure/non-secure worlds respectively.
On TrustZone targets, you need to partition the hardware first for secure code to run on secure worlds and nonsecure code to run on nonsecure worlds.
The default secure code has the following hardware partition:
- Flash (512KiB in total): 256KiB/256KiB to secure/non-secure respectively
- SRAM (96KiB in total): 32KiB/64KiB to secure/non-secure respectively
- Peripherals: most are configured to non-secure except the following which are hardwired or reserved:
- **SYS/CLK** hardwired to secure. Accessible to non-secure through secure gateway
- **FMC** hardwired to secure. Accessible to non-secure through secure gateway
- **WDT** hardwired to secure. Accessible to non-secure through secure gateway
- **RTC** configured to secure. Accessible to non-secure through secure gateway
- **TMR0/1** hardwired to secure. Implement secure `us_ticker`/`lp_ticker` respectively
- **TMR2/3** configured to non-secure. Implement non-secure `us_ticker`/`lp_ticker` respectively
- **PDMA0** hardwired to secure. Implement secure asynchronous transfer
- **PDMA1** configured to non-secure. Implement non-secure asynchronous transfer
## Flash secure/non-secure code
- Flash (512KiB in total): 256KiB for secure and 256KiB for nonsecure.
- SRAM (96KiB in total): 32KiB for secure and 64KiB for nonsecure.
- Peripherals: Most are configured to nonsecure except the following, which are hardwired or reserved:
- **SYS/CLK** hardwired to secure. Accessible to nonsecure through a secure gateway.
- **FMC** hardwired to secure. Accessible to nonsecure through a secure gateway.
- **WDT** hardwired to secure. Accessible to nonsecure through a secure gateway.
- **RTC** configured to secure. Accessible to nonsecure through a secure gateway.
- **TMR0/1** hardwired to secure. TMR0 implements secure `us_ticker`, and TMR1 implements secure `lp_ticker`.
- **TMR2/3** configured to nonsecure. TMR2 implements nonsecure `us_ticker`, and TMR3 implements nonsecure `lp_ticker`.
- **PDMA0** hardwired to secure. Implements secure asynchronous transfer.
- **PDMA1** configured to nonsecure. Implements nonsecure asynchronous transfer.
To flash secure/non-secure code on M2351, drag-n-drop `NuMaker-mbed-TZ-secure-example.hex`
first and then built user program e.g. [mbed-os-example-blinky.hex](https://github.com/ARMmbed/mbed-os-example-blinky).
## Flash secure and nonsecure code
To flash secure and nonsecure code on the M2351, drag-and-drop `NuMaker-mbed-TZ-secure-example.hex` first, and then build the user program, for example, [mbed-os-example-blinky.hex](https://github.com/ARMmbed/mbed-os-example-blinky).
## Reference
Refer to [secure code template](https://github.com/OpenNuvoton/NuMaker-mbed-TZ-secure-example) for details.
Please refer to the [secure code template](https://github.com/OpenNuvoton/NuMaker-mbed-TZ-secure-example) for details.