Skip to content

Latest commit

 

History

History
75 lines (56 loc) · 7.93 KB

porting_guide_dev_apis.md

File metadata and controls

75 lines (56 loc) · 7.93 KB

Porting Guide: PSA Functional APIs Architecture Test Suite


Introduction

The architecture test suite contains the Platform Abstraction Layer (PAL) which abstracts platform-specific information from the tests. You must implement and port the PAL interface functions to your target platform. Create and update the target configuration file to match the details of this target platform.

This document provides the porting steps and the list of PAL APIs.

Porting steps

Target configuration

You must populate your system configuration and provide it as an input to the test suite. The system configuration is captured in a single static input configuration file called target.cfg, available at api-tests/platform/targets/<platform_name>/.

An example input configuration file is as shown.

// UART device info
uart.num=1;
uart.0.base = 0x40004000;
uart.0.size = 0xFFF;
uart.0.intr_id = 0xFF;
uart.0.permission = TYPE_READ_WRITE;

// Watchdog device info
watchdog.num = 1;
watchdog.0.base = 0x40008000;
watchdog.0.size = 0xFFF;
watchdog.0.intr_id = 0xFF;
watchdog.0.permission = TYPE_READ_WRITE;

For details on the structure of the input, refer to val/common/val_target.h.

Adding a new target

  1. Create a new directory in platform/targets/<platform_name>. For reference, see the existing platform tgt_dev_apis_tfm_an521 directory.
  2. Execute cp -rf platform/targets/tgt_dev_apis_tfm_an521/ platform/targets/<platform_name>/.
  3. Update platform/targets/<platform_name>/target.cfg with your platform details. Refer to val/common/val_target.h for structure details.
  4. Update platform/targets/<platform_name>/target.cmake appropriately to select the correct instances of PAL files for compilation.
  5. Refer to the List of PAL APIs section to view the list of PAL APIs that must be ported for your target platform. These API definitions are available in nspe/<suite_name>/pal_*_intf.c. These APIs are written for tgt_dev_apis_tfm_an521 platform. You can reuse the code if it works for your platform. Otherwise, you must port them for your platform-specific peripherals.
  6. Update Crypto configuration file nspe/crypto/pal_crypto_config.h to enable or disable Crypto features selectively for the Crypto test suite.

Note: The test suite requires access to the following peripherals:

  • One UART to print Test NSPE messages
  • One Watchdog timer to help recover from any fatal error conditions
  • Non-volatile memory support to preserve test status over watchdog timer reset. Each byte of this region must be initialised to FF at power on reset.

List of PAL APIs

Since the test suite is agnostic to various system targets, you must port the following PAL NSPE APIs before building the tests. Implement these functions for your target platform.

No Prototype Description Parameters
01 int pal_uart_init_ns(uint32_t uart_base_addr); Initializes the UART UART base address
02 int pal_print_ns(char *str, int32_t data); Parses the input string and writes bytes into UART TX FIFO str : Input String
data : Value for format specifier
03 int pal_wd_timer_init_ns(addr_t base_addr, uint32_t time_us, uint32_t timer_tick_us); Initializes a hardware watchdog timer base_addr : Base address of the watchdog module
time_us : Time in micro seconds
timer_tick_us : Number of ticks per micro second
04 int pal_wd_timer_enable_ns(addr_t base_addr); Enables a hardware watchdog timer base_addr : Base address of the watchdog module
05 int pal_wd_timer_disable_ns(addr_t base_addr); Disables a hardware watchdog timer base_addr : Base address of the watchdog module
06 int pal_nvmem_read_ns(addr_t base, uint32_t offset, void *buffer, int size); Reads from the given non-volatile address. base : Base address of nvmem
offset : Offset
buffer : Pointer to source address
size : Number of bytes
07 int pal_nvmem_write_ns(addr_t base, uint32_t offset, void *buffer, int size); Writes into given non-volatile address. base : Base address of nvmem
offset : Offset
buffer : Pointer to source address
size : Number of bytes
08 int32_t pal_crypto_function(int type, va_list valist); Calls the requested Crypto function type : Function code
valist : variable argument list
09 uint32_t pal_its_function(int type, va_list valist); Calls the requested Internal Trusted Storage function type : Function code
valist : Variable argument list
10 uint32_t pal_ps_function(int type, va_list valist); Calls the requested Protected Storage function type : Function code
valist : Variable argument list
11 int32_t pal_attestation_function(int type, va_list valist); Calls the requested Initial Attestation function type : Function code
valist : Variable argument list
12 uint32_t pal_compute_hash(int32_t cose_alg_id, struct q_useful_buf buffer_for_hash, struct q_useful_buf_c *hash, struct q_useful_buf_c protected_headers, struct q_useful_buf_c payload); Computes hash for the requested data cose_alg_id : Algorithm ID
buffer_for_hash : Temp buffer for calculating hash

hash : Pointer to store the hash
buffer_for_hash : Temp buffer for calculating hash
protected_headers : data to be hashed
payload : Payload data
13 uint32_t pal_crypto_pub_key_verify(int32_t cose_algorithm_id, struct q_useful_buf_c token_hash, struct q_useful_buf_c signature); Function call to verify the signature using the public key cose_algorithm_id : Algorithm ID
token_hash : Data that needs to be verified
signature : Signature to be verified against
14 int pal_system_reset(void) Resets the system None

License

Arm PSA test suite is distributed under Apache v2.0 License.


Copyright (c) 2019-2020, Arm Limited and Contributors. All rights reserved.