Infineon Microcontrollers DISCUSSION

PSOC Edge E84: how should always-on detection be divided between its processing domains?

Started by sabari PSOC Edge E84always-on inferenceCortex-M33Cortex-M55energy budget
3 replies 248 views 4 participants
Latest activity · 27 Sep 2026

PSOC Edge E84: how should always-on detection be divided between its processing domains?

#1

Community replies 3

Re: PSOC Edge E84: how should always-on detection be divided between its processing domains?

#2

Start with the event rate and the simplest detector that can reliably decide when more processing is needed. The E84 architecture includes an M55 with Ethos-U55 and a low-power M33 path with NNLite. Confirm model support and peripheral routing for the proposed split rather than assuming either accelerator runs every network.

Re: PSOC Edge E84: how should always-on detection be divided between its processing domains?

#3

Measure standby detection energy, wakeup cost and the rate of false wakeups. Average power can be modeled as baseline power plus event rate multiplied by extra energy per event. A low-power first stage that wakes the larger workload too often can lose its expected advantage.

Re: PSOC Edge E84: how should always-on detection be divided between its processing domains?

#4

Evaluate missed events and false triggers using representative noise and operating conditions. Bound the delay from detection to a usable result and define ownership of shared sensor buffers. Optimize the full detection cycle, including transitions, instead of comparing accelerator execution times alone.

TEP COMMUNITY