Add an example app for the EFR32

[sagar-apple]

Problem

No way to exercise the EFR32 platform specific code.

Summary of Changes

Add an example app for the EFR32 with instructions on how to build it.
Currently the CHIP stack is very limited but this app is able to launch with CHIP linked and use some of the features that are implemented for now.

We are working with the SDK authors on making this app easier to build.

[gerickson]

@pierredelisle and @suryanshup

[sagar-apple]

@pierredelisle and @suryanshup

This is based on the OW lock example. It does not depend on OpenThread right now so a lot of the Makefile differences between the OW example and this come from having to build the EFR32 platform since it's not being provided.

[woody-apple]

Approving pending comments, but LGTM

[woody-apple]

@pierredelisle & @suryanshup - any update?

[woody-apple]

@BroderickCarlin @jelderton can you take a peek please?

@gerickson - can we get eyes on this today so we can make progress?

[gerickson]

@BroderickCarlin @jelderton can you take a peek please?

@gerickson - can we get eyes on this today so we can make progress?

I pinged @suryanshup again.

[suryanshup]

Agreed. Other LEDs don't signal any runtime state yet (could be used in future). They do participate when the factory reset sequence is triggered.

…

On Mon, Apr 13, 2020 at 1:41 PM Sagar Dhawan ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In examples/lock-app/efr32/src/AppTask.cpp <#321 (comment)> : > + if (aEvent->Type != AppEvent::kEventType_Timer) + { + return; + } + + // If we reached here, the button was held past FACTORY_RESET_TRIGGER_TIMEOUT, initiate factory reset + if (sAppTask.mFunctionTimerActive && sAppTask.mFunction == kFunction_SoftwareUpdate) + { + EFR32_LOG("Factory Reset Triggered. Release button within %ums to cancel.", FACTORY_RESET_TRIGGER_TIMEOUT); + + // Start timer for FACTORY_RESET_CANCEL_WINDOW_TIMEOUT to allow user to cancel, if required. + sAppTask.StartTimer(FACTORY_RESET_CANCEL_WINDOW_TIMEOUT); + + sAppTask.mFunction = kFunction_FactoryReset; + + // Turn off all LEDs before starting blink to make sure blink is co-ordinated. Okay, sounds good. @suryanshup <https://github.com/suryanshup> looks like this code will have to handle both types of boards. The other LEDs don't signal any runtime state. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#321 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALZUJMETXZM2VJFHTQYXRZLRMN2GRANCNFSM4ME6FEEA> .

[suryanshup]

Thanks for confirming and updating the code.

…

On Mon, Apr 13, 2020 at 2:16 PM Sagar Dhawan ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In examples/lock-app/efr32/src/AppTask.cpp <#321 (comment)> : > + + sAppTask.mFunction = kFunction_SoftwareUpdate; + } + } + else + { + // If the button was released before factory reset got initiated, trigger a software update. + if (sAppTask.mFunctionTimerActive && sAppTask.mFunction == kFunction_SoftwareUpdate) + { + sAppTask.CancelTimer(); + EFR32_LOG("Software Update is not supported at this time"); + } + else if (sAppTask.mFunctionTimerActive && sAppTask.mFunction == kFunction_FactoryReset) + { + // Set lock status LED back to show state of lock. + sLockLED.Set(sLEDState); @suryanshup <https://github.com/suryanshup>, I just checked the SiLabs documentation and confirmed that the none of the EFR32 boards have more than 2 LEDs. I've updated the latest commit to reflect that by removing the spurious BSP_LED_X defines. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#321 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALZUJMBNULA2XM3LJPYY55DRMN6J7ANCNFSM4ME6FEEA> .