Skip to content

Meshcore dev#2824#51

Merged
m0urs merged 3 commits into
v1.16.0mu5from
meshcore-dev#2824
Jul 6, 2026
Merged

Meshcore dev#2824#51
m0urs merged 3 commits into
v1.16.0mu5from
meshcore-dev#2824

Conversation

@m0urs

@m0urs m0urs commented Jul 6, 2026

Copy link
Copy Markdown
Owner

NickDunklee and others added 3 commits June 23, 2026 11:39
While working on some sensor code implementations, I ran into
some hard crashes that root-caused to the 4KB loop task stack
being exhausted.

Looking for various optimization schemes resulted in this relatively
low-lift fix. RAK3401 and RAK4631 both support hardware crypto.

Rather than loading in one of the two software crypto libs,
we can just use the onboard hardware. This is faster, should
consume less power, and in testing used a scant up to 700
bytes in the run loop vs 2.5-3KB per advert.

This change **only** affects advert verification processing, which
currently consumes a significant chunk of the 4KB run loop.

I figured such a change should likely be implemented in phases.

After soaking, this hardware crypto verification
process could be implemented across the entire MeshCore
cryptographic function on RAK nodes. Also possible other nodes
have available hardware crypto, however, I have not checked,
so future improvements may also exist there.

Tested on:
  - RAK3401 RAK 1W
  - RAK4631 19001
Tested Heltec t096 and Seeed t1000-e, both support this
hardware feature.
@m0urs m0urs merged commit 9adb9a4 into v1.16.0mu5 Jul 6, 2026
@m0urs m0urs deleted the meshcore-dev#2824 branch July 15, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants