Skip to main content
Associate
March 17, 2025
Solved

WLC38RX F/W config setup problem

  • March 17, 2025
  • 2 replies
  • 631 views

I am making a board using your WLC38RX chip.
I had a problem during the experiment. When I applied a load and then disconnected it, the board rebooted.
So I found a solution. When I updated the Rx f/w, the reboot did not occur.
In order to find the parameter that affected it, I manually changed the config settings from the initial state without f/w update to the same as after the f/w update, but the board still rebooted.
I wonder why there is a difference when the Rx registers config settings are the same.
Is there an invisible setting value?

The f/w used is STEVAL-WLC38RX_config_1F46_EPP.memh.

Best answer by Didier HERROUIN

I assume that you use the GUI for FW upgrade and for parameters modifications.

All the parameters are not accessible by the GUI, it may explain why you see a difference.

When you remove suddenly a load from STWLC38 output, you probably trigger some protections, you can check it by reading the interrupts latches in the GUI .

Please contact your local representative to get the latest FWs.

 

2 replies

Didier HERROUIN
Didier HERROUINBest answer
Technical Moderator
March 18, 2025

I assume that you use the GUI for FW upgrade and for parameters modifications.

All the parameters are not accessible by the GUI, it may explain why you see a difference.

When you remove suddenly a load from STWLC38 output, you probably trigger some protections, you can check it by reading the interrupts latches in the GUI .

Please contact your local representative to get the latest FWs.

 

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
WisejetAuthor
Associate
March 18, 2025

Thanks for the reply. Thanks to you, I realized that not all parameters are configurable in the GUI.

Technical Moderator
March 23, 2025

Hi Sir 

The cause of this may be that the previous FW triggered some kind of protection, because RX dropped from heavy load to light load, which easily triggers VRECT OVP protection.
The new configuration file has already solved this problem.

Some configurations are internal and not open to customers.

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.