Hello there!
For our HW test I need to setup PHY_CAL_MODE to "normal mode".
What value shall I set? I do not see the value in swru455m.
Thanks for help!
Jiří
Hello,
Setting this to 0 should set the calibration mode to Normal.
Best,
Josh
Hey Jiri,
Apologies on the delay as I was looking into this for you. Yes, that table explains the calibration modes well and you are correct in your understanding of how each mode correlates to a value.
Unfortunately, we do not have a documentation that explicitly states "Normal Mode: 0", etc, but you are correct:
0 will set the calibration mode to Normal. 1 will set it to Triggered. And 2 will set it to Onetime.
After changing this to 0, be sure to reconfigure the project using the command lines shown under Section 7.1.10 of the Image Creator User's Guide.
Best,
Josh
I have one more question to this topic:
What is default Wi-Fi calibration mode value? According to documentation it is 1 = Triggered mode.
But why it was necessary in our project to implement this workaround? If default behavior would be consistent, it would not be needed.
https://e2e.ti.com/support/wireless-connectivity/wifi/f/wi-fi-forum/997365/cc3220sf-phy_cal_mode-settings-from-cli-imagecreator
JSON file that is generated holds value 0 = Normal mode. It looks like CLI application default behavior doesn't correspond to default behavior described in SWRU455m.
Can you confirm this inconsistency?
Jiří
Hi Jirko,
At SWRU455 is described this:
"15.4.2 PHY Calibration Mode: In normal mode, PHY is calibrated every time the networking subsystem is started and the device was either reset (using nShut pin), or 24 hours have passed since the last calibration. This mode is set by default..."
and this:
"4.9.1 2.4-GHz Wi-Fi Calibration Modes: The SimpleLink device performs calibration of the Wi-Fi physical layer. The system supports three different calibration modes to optimize this process for the required use case. The default calibration mode is triggered calibration."
I think default mode is normal. It looks that this is just another case of "gibberish" at SWRU455.
Jan
Hi Jiri,
Thanks for pointing this out. I have brought this back to our team and will work to make this more clear for customer use.
Best,
Josh