Trying to find compute resources (RAM, CPU utilization) needed to support EAP-TTLS security in WICED.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
TiCu_2020706
Level 1
Level 1
5 sign-ins Welcome!

Running EAP-TTLS security on 1LD module (STM32F412 + CYW43438) and getting less Wi-Fi throughput than expected. Has any testing been done that can provide the RAM and CPU utilization? Would like to know if I'm resource constrained or if there is room for improvement.

0 Likes
1 Solution
GauravS_31
Moderator
Moderator
Moderator
10 questions asked 250 solutions authored 250 sign-ins

The join_ent process with EAP-TTLS using freeradius consumes ~18kB memory before data packets could be exchanged. You can use the command malloc_info in test.console before and after calling join_ent to verify the same. The processor should have sufficient memory available for data transmission. In the test.console app (used for testing EAP-TTLS), you can consider disabling features in console.mk not needed such as P2P, TraceX, Iperf (enabled if used for throughput testing), etc. to free up memory. You can also adjust the TX and RX packet pool size as explained in the Enterprise security user guide. If all these checks fail, we would need further details such as throughput test performed (TCP or UDP), radius server details and version, throughput numbers, method used for testing throughput (iperf/WICED TCP library).

View solution in original post

3 Replies
GauravS_31
Moderator
Moderator
Moderator
10 questions asked 250 solutions authored 250 sign-ins

The join_ent process with EAP-TTLS using freeradius consumes ~18kB memory before data packets could be exchanged. You can use the command malloc_info in test.console before and after calling join_ent to verify the same. The processor should have sufficient memory available for data transmission. In the test.console app (used for testing EAP-TTLS), you can consider disabling features in console.mk not needed such as P2P, TraceX, Iperf (enabled if used for throughput testing), etc. to free up memory. You can also adjust the TX and RX packet pool size as explained in the Enterprise security user guide. If all these checks fail, we would need further details such as throughput test performed (TCP or UDP), radius server details and version, throughput numbers, method used for testing throughput (iperf/WICED TCP library).