Description

A prototype PSA API implementation was pushed into ‘feature-ipc’, which showcases PSA API usage. This implementation did not considerate real secure partition usage; and only partial PSA APIs were implemented.

An updated Full IPC implementation is required. In updated implementation:
• IPC secure partition has its own thread and call PSA APIs in thread entry.
• A scheduler and message buffer are implemented in SPM.
• IPC secure partition is generated from manifest (Partial with some handcraft, since still need deep modification within manifest part but ideas are not totally gathered).
• All PSA APIs implemented.

Event Timeline

KenLSoft triaged this task as High priority.Oct 11 2018, 2:14 AM

KenLSoft created this task.

KenLSoft created this object with edit policy "Administrators".

edison-ai added a comment.Oct 12 2018, 1:42 AM

This comment was removed by edison-ai.

KenLSoft added a comment.Oct 12 2018, 1:51 AM

This comment was removed by KenLSoft.

adrianlshaw added a subscriber: adrianlshaw.Oct 25 2018, 4:29 PM

KenLSoft updated the task description. (Show Details)Dec 19 2018, 1:56 AM

KenLSoft closed this task as Resolved.Feb 1 2019, 2:33 AM

spoonix changed the visibility from "All Users" to "Public (No Login Required)".Feb 1 2019, 3:49 PM

Thoroughly testing the IPC implementation to ensure its correctness, security, and compliance with PSA standards. This involves both functional testing and security validation to identify and suika game address any vulnerabilities.

It seems like a significant update, requiring a structured approach backpack battles

Thanks for up date @tiny fishing

Having sufficient unblocked access is of utmost importance, since USART requirements that comply with CMSIS might impede them. phrazle

Full IPC implementation for PSA APIs.Closed, ResolvedPublicActions

Description

Event Timeline

Full IPC implementation for PSA APIs.
Closed, ResolvedPublic
Actions