Make core functionality work in no-std environment #2

Closed
opened 2023-01-17 01:58:50 +00:00 by zachary · 1 comment
Owner

The biggest current issue is with async APIs like channels. We may end up picking out a RTOS like Embassy as the only no-std target.

The biggest current issue is with async APIs like channels. We may end up picking out a RTOS like Embassy as the only no-std target.
zachary added the
enhancement
accepted
label 2023-01-17 01:58:50 +00:00
Author
Owner

We are targetting Embassy and no-std for nodes, master devices based on std will come later.

We are targetting Embassy and no-std for nodes, master devices based on std will come later.
zachary added the
implementation
complete
label 2023-04-09 15:08:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: BFPOWER/physical#2