Example application overrides EUIs while using LR11xx crypto

[adriansmares]

The example application overrides the DevEUI/JoinEUI and AppKey always on reset:

SWL2001/utilities/user_app/main_examples/main_exti.c

Lines 200 to 211 in 0979db3

	case SMTC_MODEM_EVENT_RESET:
	SMTC_HAL_TRACE_INFO( "Event received: RESET\n" );
	// Set user credentials
	smtc_modem_set_deveui( stack_id, user_dev_eui );
	smtc_modem_set_joineui( stack_id, user_join_eui );
	smtc_modem_set_nwkkey( stack_id, user_app_key );
	// Set user region
	smtc_modem_set_region( stack_id, MODEM_EXAMPLE_REGION );
	// Schedule a Join LoRaWAN network
	smtc_modem_join_network( stack_id );
	break;

This should be a bit more nuanced, since if the example is compiled with CRYPTO=LR11XX_WITH_CREDENTIALS, one may expect that the EUIs are really the ones 'on the board'. Maybe the overrides should be guarded by a ifdef for USE_PRE_PROVISIONED_FEATURES ?

[smtc-bot]

Thank you for your inquiry.

Customers are encouraged to submit technical questions via our dedicated support portal at https://semtech.force.com/ldp/ldp_support.

We invite all users to visit the LoRa Developer Portal Forum at https://forum.lora-developers.semtech.com and to join the thriving LoRa development community!

[matthieuantoine]

Thanks @adriansmares - I'll report that internally to update it for the next release.

FYI - examples in the LoRa Basics Modem SDK already have it implemented this way.

[lbm-team]

Hi @adriansmares !
Thanks for your report.
We will update the basic example to take in count internal credentials in case CRYPTO=LR11XX_WITH_CREDENTIALS is used at makefile level.
It can also make sense to print current CHIP EUI and CHIP PIN to ease claiming process.
It will be updated as well for the next release

[lbm-team]

Hi @adriansmares !

We add this feature in the new v3.3.0 release.
You can find the updates line in main example here