I have just returned to this project and I was wondering if 200 to 400 mS is to be expected?

I also notice that the release notes for EmberZnet SDK  6.6.5.0 have a fix for NVM3 - 
"  * Fixed an issue with Gecko Platform's NVM3"

Is this related?

That looks suspiciously like you are trying to compile a c file as c++.

Within the Project Build Settings under IAR Compiler I set the language from C to C++ manually, as this was not changed .

Only do this on files you actually want to compile as c++. What  I do is to do it on a folder by folder basis- i.e. create a folder for my c++ files and set this as c++. 

Also ensure that when you include c headers use extern "C" { #include "file.h" }

I also found that each time I regenerated the project, I had to convert back to C otherwise it wouldn't work. 

If you are using the IAR EW, you can select the language to be auto (extension based)

I think you will run into problems with your work around to redefine char16_t doesn't this then leave you with an undefined type? char16_redef_t
If you continue to have issues with this can I suggest you start a new thread as I think it is more likley to be seen by SiLabs

That looks suspiciously like you are trying to compile a c file as c++.

Within the Project Build Settings under IAR Compiler I set the language from C to C++ manually, as this was not changed .

Only do this on files you actually want to compile as c++. What  I do is to do it on a folder by folder basis- i.e. create a folder for my c++ files and set this as c++. 

I also found that each time I regenerated the project, I had to convert back to C otherwise it wouldn't work. 

If you are using the IAR EW, you can select the language to be auto (extension based)

I think you will run into problems with your work around to redefine char16_t doesn't this then leave you with an undefined type? char16_redef_t
If you continue to have issues with this can I suggest you start a new thread as I think it is more likley to be seen by SiLabs

Also, check the release notes for the version of stack you are using to see if it is qualified against the version of IAR compiler, the configuration I'm using is V8.30.

The other workarounds I had to do were,

• Add --enable_restrict to Options->C/C++ Compiler->Extra Options
• Define some missing sections in the linker file,

Also, check the release notes for the version of stack you are using to see if it is qualified against the version of IAR compiler, the configuration I'm using is V8.30.

The other workarounds I had to do were,

• Add --enable_restrict to Options->C/C++ Compiler->Extra Options
• Define some missing sections in the linker file,

Hi,

The EFR Connect doesn't incorporate any security features yet, that will come out on a later version.

Regards,

Tiago

Hi,

The EFR Connect doesn't incorporate any security features yet, that will come out on a later version.

Regards,

Tiago

We were relying on that. Is the old version still available?