Hi,

First of all, which SDK version do you use?

The example in Flex 2.x has an additional node table in RAM that is cleared on restart - so, although the nodes are still associated the coordinator ignores the messages from the nodes. This behavior has been changed in Flex 3.x, in that case the coordinator accepts incoming messages from the previously associated children regardless of coordinator reset.

However, emberResetNetworkState() clears the table of the previously associated children and also de-configures the network. So, if you call that API function, you must configure the network ("form") and re-join all the previously associated children to be able to communicate (not only end-device <-> coordinator, but even end-device <-> end-device obviously as in case of Star mode network the coordinator does the routing).

The network parameters are stored in the NVM so, those are available after reboot but not automatically applied. You should call emberNetworkInit() to apply the previously stored values and configure the network.

BR,

/sza2

Hi,

So what I think the radio is busy swithing to BLE and right this time a proprietary message arrives, so it is lost. There isn't a mechanism to handle with this in DMP? Because if not, DMP by itself will always lose packets.

Since in the device there is only one radio HW, so, it is simply not possible to detect any incoming packet while the radio is not switched and setup on the proprietary frequency. Thus, it is obvious, that you will lose proprietary packets if the radio is operating on BLE and during the time it switches vice-versa.

I can implement an algorithm to resend the message is an acknowledgement is not receive back, so this PER of 4.5% can be reduced to zero. But is that the right way to go?

Yes, definitely.

Most time I need only proprietary communication, BLE is connected few times. So is there a way to BLE tasks do not use the radio?

I would ask this in the BLE forum, since that team has deeper knowledge on that. BLE is strict on timing, and there are multiple phases I'm not sure when / how it is possible to disable / turn off BLE.

BR,

/sza2

This question fits in the timing forum, so I am moving it to https://www.silabs.com/community/timing/forum.topic.html/reprogramming_a_pre-programmedsi5341-COxW from proprietary wireless.

If you’re planning to develop IoT applications for the EFM32 Giant Gecko or Pearl Gecko, you’re probably already thinking about using a real-time operating system.

It’s quite true that many embedded developers can get by with less sophisticated software based on a simple loop. But the latest EFM32 microcontrollers are packed with complex peripherals that require correspondingly complex application software. And designing IoT devices means dealing with both elevated user expectations and challenging design requirements. All this means that it’s become increasingly difficult for your projects to succeed without an operating system.

So how to get started? It can be daunting to make the sudden jump from bare-metal programming to kernel-based application development. So help you overcome that hurdle, we're producing a ten-episode video series to help smooth the way: Getting Started with Micrium OS.

The series is hosted by Matt Gordon, who has spent more than 10 years helping developers learn how to maximize the potential of the Micrium real-time operating system. He helped establish the Micrium training program, and is currently RTOS Product Manager at Silicon Labs.

The first episodes in the series starts with some basic information about what a kernel does and how kernel-based applications are structured. Matt covers initialization, how the kernel performs task scheduling, and how context switches pass control of the CPU from one task to another. Later in the series, Matt will discuss synchronization, resource protection, and inter-task communication. The series will leave you with a cohesive picture of real-time kernels and Micrium OS.

That’s not all: this series is supplemented with some of the best developer documentation ever produced for embedded systems programming. You can visit https://doc.micrium.com to learn much more about kernel-based application development and the networking and communication stacks that make up Micrium OS.

The Micrium OS kernel is available for free download through Simplicity Studio v4. To download and to find out more about Micrium OS, visit: https://www.silabs.com/support/getting-started/micrium-os

To find the series on YouTube, visit: https://goo.gl/JQ4UaV

And be sure to subscribe to the Silicon Labs YouTube channel to receive notifications of new episodes! https://www.youtube.com/user/ViralSilabs

Check out the first video in the series here:

Hi,

The GPIO wake up is not an interrupt, but a Power On Reset. It cannot be disabled.

To achieve something similar, you can

1) Go back to shutdown upon GPIO wake up, if the sleep timer is still running

or

2) For GPIO1, 2 and 3 you can set matrix mode that will prevent GPIO wake up on those pins only, but will actively pull them to ground when the chip is in shutdown state.

Regards,

Tamás

Hi Danil,

You can configure this IF mode in WDS. You can request the necessary WDS license for this in a support case at https://siliconlabs.force.com/s/contactsupport

Regards,

Tamás

Hi Vladimir,

I would suspect environmental effect, close to nodes id8 and id9. To make sure, you should repeat measurements and observe or control the environment as much as possible.

See useful article at https://www.silabs.com/community/wireless/proprietary/knowledge-base.entry.html/2019/01/11/efr32_rssi_measureme-wQiX and related topic at https://www.silabs.com/community/wireless/proprietary/forum.topic.html/efr32_rssi_stabilityandwindow-hov2

Regards,

Tamás

Hi,

While it is possible to implement your own Zigbee stack on top of RAIL, we don't recommend it. First, you need to comply with the Zigbee standard but there can be several difficulties like routing, security and so on - which probably requires a huge amount of work and detailed understanding of the Zigbee standard. On the other hand you will have to certify your product that it is Zigbee compatible (including the conformity of regulation  standards (at FCC, ETSI, etc.).

BR,

/sza2

Hi Danil,

You can configure this IF mode in WDS. You can request the necessary WDS license for this in a support case at https://siliconlabs.force.com/s/contactsupport

Regards,

Tamás