topic Re: LPC55S69 : Core1 and TrustZone in LPC Microcontrollers

LPC55S69 : Core1 and TrustZone

EugeneHiihtaja — Tue, 15 Oct 2019 12:30:27 GMT

Hello !

It is not so clear from user/ds documents about some dependencies between some peripherals.

1. Can Core1 and their peripherals to be allocated in secure part and be fully protected from Core 0.

So Core 0 shouln't able to access to Core 1 code/data/peripherals at all ?

So like Core 1 running under Trustzone protection at secure part ?

If Core 1 generate some interrupts, Core 0 can call some secure API and read status if need ?

Looks like Core 1 should be able to access areas what is protected by Core0's Trustzone.

Or Core0 is able to exclude Core1 areas by using own MPU only ?

2. What if Core0 stay in Deepsleep mode and can Core 1 continue to to switch between Run and DeepSleep modes

and Core1 should use some GPIO lines for wakeup from DeepSleep ?

Basically I need if both Cores can switch between Run and DeepSleep freely by using own set of GPIO lines and peripherals. And able to wakeup up each other when need.

But all Core1 peripherals/memory should be at secure world.

Does this kind of configuration is possible ?

Regards,

Eugene

Re: LPC55S69 : Core1 and TrustZone

Sabina_Bruce — Wed, 16 Oct 2019 20:54:39 GMT

Hello Eugene,

Here are the answers to your questions:

1. Can Core1 and their peripherals to be allocated in secure part and be fully protected from Core 0.
So Core 0 shouln't able to access to Core 1 code/data/peripherals at all ?
So like Core 1 running under Trustzone protection at secure part ?
If Core 1 generate some interrupts, Core 0 can call some secure API and read status if need ?

The LPC55S66 and LPC55S69 have implemented core 0 as a Cortex-M33 with full TEE and TrustZone® support enabled. The LPC55S69 has a second Cortex-M33 (core 1) that does not implement the secure environment with TZ. In this case Core 0 is the secure part and Core 1 shouldn't be able to access Core 0, unless through secure gateways.

TrustZone® technology divides the system into two states, safe (S) and non-secure (NS), and can switch between the two states through corresponding commands. The CPU states can be secure privilege, secure non-privilege, privilege (Handler), or non-privilege (Thread).

What if Core0 stay in Deepsleep mode and can Core 1 continue to to switch between Run and DeepSleep modes
and Core1 should use some GPIO lines for wakeup from DeepSleep ?

Only Core 0 is able to enter deep sleep mode. core 1 is able to enter normal sleep mode. Please refere to chapter 14 for the power profiles available in the LPC55s69.You can however enter sleep mode for either CPU 0 or CPU1.

Please let me know if you have additional questions.

Best Regards,

Sabina

Re: LPC55S69 : Core1 and TrustZone

EugeneHiihtaja — Thu, 17 Oct 2019 08:36:40 GMT

Hello Sabina !

So basically Core1 can be always ON and used like this :

- it can have own Core clock and use 32kHz or 1Mhz internal oscillators as clock source and for Systick timer.

And only switch between RUN and Sleep (_ WFI()) modes.

In this case it can consume some mkA but exact digits is not visible in DS.

- Secure gateways can be configured in ways that Core1 always and Core0 in Secure mode access some part of SRAM memory.

But Core0 in Non-Secure mode can't access it.

Is this true ?

Thank you !

Regards,

Eugene

Re: LPC55S69 : Core1 and TrustZone

Sabina_Bruce — Tue, 22 Oct 2019 14:45:16 GMT

Hello Eugene,

1. The System Tick timer for CPU1 has three options.

The datasheet shows the current consumption when CPU1 is in sleep mode or off.

The second question I did not understand what you mean. Here is the basic functionality if the CPU is in secure or non-secure states.

Here are some really great videos that explain in detail, how the trustzone feature works with our LPC55S6x Family.

If you have more questions let me know.

Best Regards,

Sabina