Hi,

Some clarification on Connect maximum device number. Connect supports the so-called "Simple Star" network which supports 64 connected devices, in this case, the end devices directly connected to the coordinator. Connect also support the so-called "Extended Star" network, where extenders connected to the coordinator and the end devices connected to the extenders. In this case, the maximum number of the end devices is 2048 (64 * 32) - but extenders must be "always-on" devices to forward messages from end devices to other devices on the network, while end devices can be sleepy nodes (which sleeps in low power mode in most of the time).

connect stack can implement 4 extenders and 32 end devices for each so total end devices at network is 128 end devices ?

Correct, so for 250 end devices you need 8 extenders.

Connect also support "Direct Mode" in which case the number of devices is not limited, but you have to implement the routing if you need routing and you must ensure that the device addresses are unique (in "Star Mode" the coordinator allocates the addresses for every joining nodes and forward messages between nodes). If your nodes only have to communicate with one central node, you don't have to implement any routing, though.

EFR32FG devices support RAIL library based and Connect stack applications only (Flex SDK). If you need extended capabilities (BLE) then you need to switch to EFR32BG or EFR32MG (Zigbee, Thread, etc.) devices. If you need more information on the applicable stack for different device families, please contact your local Silicon Labs sales offices.

BR,

/sza2

Hi,

The issue seems Zigbee related, I moved the topic to the appropriate forum.

BR,

/sza2

I'm using EmberZNet 6.7.3.0 and GNU ARM 7.2.1. Most of the project was generated by AppBuilder. I only added callbacks and extended attributes. I'm using ZCL Occupency sensing. I communicate with the sensor using UART.

I used SLWSTK6102A board and SLWRB4308A to build the project.

Everything worked fine.

Now I have created my own pcb and I'm using MGM210P032JIA2R he has a pre-programmed bootloader with XMODEM.
I'm trying to upload my application correctly.

XMODEM connects via a USB-UART converter. It will show that it has uploaded correctly, but after starting the application it falls into the reset loop.

[ASSERT:librail.a:49]
Thread mode using main stack (20001140 to 20001AA0), SP = 200019C0
664 bytes used (28%) in main stack (out of 2400 bytes total)
No interrupts active
Reset cause: Assert librail.a:49
R0 = 000318E9, R1 = 00000031, R2 = 20001E68, R3 = 20003370
R4 = 00000000, R5 = 00000001, R6 = 0003365C, R7 = 20001FCC
R8 = 00000001, R9 = 00031CA4, R10 = 20003111, R11 = 200030FC
R12 = 000310C8, R13(LR) = FFFFFFF9, MSP = 200019C0, PSP = 20001AA0
PC = 000061E8, xPSR = 69000000, MSP used = 00000298, PSP used = 00000000
CSTACK bottom = 20001140, ICSR = 00000806, SHCSR = 00070008, INT_ACTIVE0 = 00000000
INT_ACTIVE1 = 00000000, CFSR = 00010000, HFSR = 00000000, DFSR = 00000000
MMAR/BFAR = E000ED34, AFSR = 00000000, Ret0 = 000285D1, Ret1 = 00028219
Ret2 = 0000AB75, Ret3 = 00029DBB, Ret4 = 0000AB7B, Ret5 = 000146BF
Dat0 = 000318E9, Dat1 = 00000031

I used the same converter to upload via xmodem to the module on the SLWSTK6102A board and the application started correctly.

I pulled the module (SLWRB4308A) out of the board and connected it directly to the converter. I uploaded again using XMODEM and started correctly.

Unfortunately I didn't have space on the PCB to make a Jlink connector I need to upload it via XMODEM.

I only have the option as shown in the diagram

Hi,

Basically, the workflow is that first the project needs to be configured once (with AppBuilder) then if that's read, clicking on 'Generate' and then develop the code.

Obviously, that does not always work and sometimes it is necessary to make modifications in the AppBuilder and re-generate the project files - although, in normal workflow it usually happens rarely.

Currently, the generation will overwrite the setting you made on the project, there's no way to change this behavior.

A semi-workaround could be to physically copy the rtcdriver.c to your project directory - this way it will be part of the project and will be compiled every time.

Additionally, you can add files to the project (even from outside of the project) by the AppBuilder:

Although, you still have to manually remove (or exclude from build) those files the generation adds to the project and you don't need.

BR,

/sza2

Hi

I assume you have to add em_eusart.c manually to your project. In case of default installation path it should be located here: C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.7\platform\emlib\src\

There are two ways to do this (both ways, right click on the project's emlib directory, then New -> File).

1. Link the file

Click on Advanced >>, check the checkbox then apply the location

2. Copy the file

Simple navigate to the above mentioned path and copy the file to the project's emlib directory.

I recommend the first one, as in that case the project will use the updated file automatically when you update the SDK.

BR,

/sza2

Hi,

What kind of project is this (example in the SDK)?

Which SDK (+version) do you use?

Is it RAIL or Connect maybe?

Additionally, what are error messages?

BR,

/sza2

Hi,

What kind of project is this (example in the SDK)?

Which SDK (+version) do you use?

Is it RAIL or Connect maybe?

BR,

/sza2

Hi,

I moved your case to the 32-bit MCU forum as the current question is rather MCU related.

MCU team, could you please handle this case, thanks.

BR,

/sza2

Hi,

My requirement is to create a bootloader which should support the functionalities of Standalone Bootloader as well as the Application Bootloader for EFR32MG13 chipset with 512kB Flash.

To achieve this, I took EFR32MG13P732F512GM32 Gecko Bootloader example "Internal Storage Bootloader (single image on 512kB device)" and enabled all the Plugins that are required for a Standalone Bootloader.

But I am getting compilation issue:  "FLASH memory overflowed !",  Please refer the attached image.

Is there any way to optimize the bootloader code, for example by removing any unnecessary Plugins ?

Regards,
Ashish