Hi,

It is still not clear which one is the 'RF' and the 'non-RF' resistor and what is the difference between them. However, if this is not related to any Silicon Labs product, you should clarify this question with the radio chip manufacturer who recommended the RF front-end you mentioned. They should be able to answer what is the effect on the performance using one resistor type or another.

Daniel

AFAIK, there is no A03 revision schematic published.

https://www.silabs.com/documents/public/schematic-files/PCB4001-A03-assy-draw.pdf

https://www.silabs.com/documents/public/schematic-files/BRD4001A-A01-pkg.zip

Do you have reason behind to get A03, I suppose there is no big change between the revision.

I moved this topic to the more relevant MCU forum at https://www.silabs.com/community/mcu/32-bit/forum.topic.html/store_critical_dataintolockbitsregion-PnOb

(notification email contains the old url)

Hi Tamás, yes it's really great to be able to make use of these brilliant little radio chips.  I use the Microchip MCU's because I get on OK with their MPLabX IDE, and the Microchip Code Configurator feature makes setting up projects quite straightforward, though it does slightly restrict the range of MCU's available.  Anyway, the chip I'm currently using is a PIC 16F18345, and using MCC I have set it to be SPI Master, Mode 0, data sampled at middle.  Watch the clock frequency which will depend on the system clock, and obviously do not exceed the Si4455 maximum data rate. Hope this helps someone.

Regards,

John

Hi Team,

I am using  a EFR32FG12P231F1024GM48 (series 1 device). There is lockbit region size of 2 KB. As I read ug162-simplicity-commander-reference-guide doc in section 4.5 Memory Regions (LOCKBITSDATA), there is mentioned that the last 1.5 kB of this page is unused by the device itself. I also read in ug266-gecko-bootloader-user-guide doc, lockbits page is occupied for signing and encryption key. Can i use any free region in lockbits, if available, for storing my application critical data (size is 32 bytes)?  So, prevent the collisions with chip functionality.
All suggestion are welcome.

Thanks,
Pratik

Si4463 is far from EOL.

See https://www.silabs.com/wireless/longevity-commitment

Hi qihui you, I guess you chip doesn't have 1MB flash and you are using GCC. 

If that's true, it's a known issue. The workaround is to replace the linker file C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.7\platform\Device\SiliconLabs\EFR32MG21\Source\GCC\efr32mg21.ld with the attached one.

After that, clean and rebuild your project.

Please let me know if it works.

Hi Matteo,

Sorry for this lately reply, I just missed your previous post. 

Unfortunately, I do not have too much experience with Bluetooth, so I cannot compare it to the other protocols in your use-case. Yes, I know the basic attributes, regarding bandwidth, etc, but if you power the device from the line, then it should not matter. But you mentioned, for Bluetooth "but need royalties": as I know it is not 100% true. So if you make a Bluetooth device and if you would like to use the Bluetooth logo on this device, certified with Bluetooth SIG, then you have to pay royalties for the Bluetooth. If you use the Bluetooth protocol as "proprietary" protocol, so the PHY, the data format, and everything is same, just the device will not certified with Bluetooth SIG, then it is free. But you cannot sell it as Bluetooth compatible device, but my guess it is no problem in your case.

My guess, in this case, if you familiar with one of the available protocols, and you have idea how could you do with it, this protocol will be the fastest solution.

Externded star topology also achievable with: Zigbee, Connect protocols, (maybe with Bluetooth or Bluetooth MASH, but I am not familiar with BL protocols). Zigbee and Connect basing on 802.15.04 standard, so the lowest level of the communication should not be implemented. (this level implemented by the stack)

Hi Stefan,

Sorry, last time I didn't know that direct mode isn't supported on EFR32 Series 2 devices yet. Unfortunately the API documentation does not mention it, but it can be concluded by the fact that the part you have does not have PC10 and PC11 pins. Although, direct mode does not work on the target, synchronous MODEM.DOUT signal can be assigned to any GPIO on portA or portB (see datasheet) which puts the payload bits out on the selected pin in case of RX, and the whole packet (including preamble, sync word and CRC bits as well) on the transmitter; but I suspect, this isn't your goal.

Note that EXP_HEADER denotes pin header on WSTK not on the Thunderboard.

Best Regards,
Bence