At Silicon Labs, “doing the right thing” is a corporate value we live by. Ever since our company was founded in 1996, we’ve made it a priority to give back to communities where we operate. In 2016, our Austin site embarked on a new philanthropic partnership with Code2College. Code2College’s mission is to dramatically increase the number of minority and low-income high school students who enter and excel in STEM (Science, Technology, Engineering, and Math) undergraduate majors and careers, and their work aligns perfectly with our goal to promote the advancement of STEM education. Together, we’ve built a mutually beneficial relationship that helps serve the community. In addition to providing volunteers for Code2College activities, we’ve hosted numerous student workshops and events onsite and hired Code2College high school summer interns, giving them a preview of what it’s like to work in STEM.  

Code2College Executive Director, Matt Stephenson, shared his views of Silicon Labs’ involvement with Code2College: “Our relationship with Silicon Labs has grown exponentially over the years because of the many things that the company is doing for and with us. With Silicon Labs’ engineers, our students are learning not just the actual technical skills in software development but also numerous soft skills that are valuable in the workplace, like working with a team, effective communication, and project management. It’s a great value proposition from a successful semiconductor organization like Silicon Labs, and we are so thankful for this partnership.”

Don’t just take our word for it – hear from some of our Code2College volunteers.

We’re proud to partner with Code2College on the important work they’re doing every day in our community. For more information about their services, visit code2college.org.

No problem. I believe you will solve this issue also with the edge triggered interrupt.

Tamás

Hi dingyg99,

My answer about NIRQ typical use case was from radio standpoint. You have to take into account the interrupt capabilities on the MCU side. If you need help with that, our MCU forum is a better place for that. (I can confirm I don't see level sensitive GPIO interrupt option in the EZR32LG ref manual.)

Tamás

Hi,

In Studio (v5) click on the Launcher button, select your device and click on Create New Project. In the next window from Technology Type select Bootloader and choose UART XMODEM Bootloader, create the project. The Appbuilder will appear, select the Plugins tab and click on the UART item.

Click on USART0. Here you can setup the pins corresponding your custom board.

BR,

/sza2

Use the Direct TX project, that also contains the RX config for the same RF parameters. You may have to change only the GPIO config if you want to use the same GPIOs for RX and TX. After that you can change state between RX and TX.

Tamás

Regardless of how well is your application working, generally it is advised to regularly reinitialize the radio with a cycle time allowed by the use case, to prevent any unexpected external disturbance.

Tamás

Do you see the sensitivity loss on both ICs on both frequencies?

Do you see it every day at the same time?

If you don't do it now, try to control the chips to READY before resending START_RX.

Generally it is advised to regularly reinitialize the radios to prevent any unexpected external disturbance, with a cycle time allowed by the use case.

Regards,

Tamás

Yes, right. For LDC+DSA the RX_TIMEOUT_STATE should be SLEEP.

My previous recommendation of NOCHANGE was for LDC without DSA. 

If you want the radio to go back to sleep in every case and not wait in READY or RX state for the MCU to react, you should set also the RXINVALID_STATE to SLEEP state. This way the WUT will wake up the radio regularly but it will always go back to sleep.

I recommended to use the status signals to observe and debug what is happening in the radio and not to replace NIRQ with them. If you understand how NIRQ works, you can use it reliably. NIRQ is LOW when any of the PEND bits of the enabled interrupts are active. It is advised to handle in the MCU the NIRQ as level sensitive interrupt, so it will generate interrupt in the MCU again and again until the MCU clears all the enabled PEND bits.

Tamás

Yes, right. For LDC+DSA the RX_TIMEOUT_STATE should be SLEEP.

Tamás

Yes, right. For LDC+DSA the RX_TIMEOUT_STATE should be SLEEP.

My previous recommendation of NOCHANGE was for LDC without DSA. 

Tamás