MM2.2 SDK with AP powersave features for 8108

Software Embedded
1

Hi,
Can we get early release or beta of MM2.2 SDK with AP powersave features for 8108 (using AP duty-cycled radio TWT).

Regards
Arun

2

I also have additional questions for you
Is there a way to put the MM8108 into a retained-state sleep while in AP mode in SDK 2.11.2? If so, what is the API and what state is retained vs. lost?
Does the chip support beacon offload (autonomous TBTT TX while host is sleeping)? If yes, is it surfaced in 2.11.2 or planned for 2.12+?
Is the PMKSA cache for AP-mode authentication held in chip RAM or host RAM (i.e. in morselib state)? Can we inject entries before mmwlan_ap_enable?
Is broadcast TWT supported on the AP side in 2.11.2? STA side?
Is WNM-Deep Sleep supported on the AP side (does the AP retain the parked-STA association)?
What is the typical cold-start time from PWR_EN high to first beacon on air, with calibration cached and not cached?

6

Morse Micro team:
Kindly respond to this thread.
Regards
Arun

7

Is there a timeline for the release of these features, otherwise can we get source code of morsedriver under NDA?

8

Hi @arun.v.emqos

I can answer some of the questions, but not all of them yet.

Is there a way to put the MM8108 into a retained-state sleep while in AP mode in SDK 2.11.2? If so, what is the API and what state is retained vs. lost?

Not for the MM-IoT-SDK. AP mode on MM-IoT-SDK is a beta feature.
The 1.17.8 Linux driver for the MM6108 supports AP sleep between beacons as a beta feature. This sounds similar to what you want.

Does the chip support beacon offload (autonomous TBTT TX while host is sleeping)? If yes, is it surfaced in 2.11.2 or planned for 2.12+?

Once again this is a feature available in the Linux driver, but not in the MM-IoT-SDK.

Is the PMKSA cache for AP-mode authentication held in chip RAM or host RAM (i.e. in morselib state)? Can we inject entries before mmwlan_ap_enable?

Supplicant holds this key, so this is stored in host ram. Injection is not something we have an API for.

Is broadcast TWT supported on the AP side in 2.11.2? STA side?

No. Only individual TWT is supported.

Is WNM-Deep Sleep supported on the AP side (does the AP retain the parked-STA association)?

Not for the MM-IoT-SDK.

What is the typical cold-start time from PWR_EN high to first beacon on air, with calibration cached and not cached?

I’m still chasing this number.

Is there a timeline for the release of these features, otherwise can we get source code of morsedriver under NDA?

libmorse (our MM-IoT-SDK driver and upper mac implementation) is already open source.

9

Hi, Pls confirm. If i set BUILD_MORSELIB_FROM_SOURCE it will compile morsedriver from source instead of using the library from ~/mm-iot-sdk-2.11.2/framework/morselib/lib

Regards
Arun

10

Can you please share code for morsemicro driver 2.9.7

11

Yes that is correct.

It is not possible for us to share the 2.9.7 libmorse source. Please update to 2.10 or 2.11 instead.

12

Just to extend what @ajudge said, AP mode entering power save is not on the roadmap for MM-IoT-SDK.

MM-IoT SDK AP mode is alpha and it is expected many basic (and non-basic) features like WNM sleep, TWT etc are not working/implemented. Being alpha also means we are light on specific performance characteristics such as for your question:

What is the typical cold-start time from PWR_EN high to first beacon on air, with calibration cached and not cached?

As you may have noticed, from the quick turn around between 2.10 and 2.11, we are now targeting faster release cadence, so you can expect rolling improvements particularly around AP mode over the coming months