• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 43 subscribers
  • Views 345 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

CC33XX-SOFTWARE: AntGain_2_4GHz / cc33xx-conf.bin still not working in FW release 1.0.0.8

CC33XX-SOFTWARE: cc33xx-conf.bin issue in FW release 1.0.0.9: AntGain_2_4GHz not working

Kaisa_K
Prodigy 185 points

Part Number: CC33XX-SOFTWARE
Other Parts Discussed in Thread: CC3300

Tool/software:

Dear TI experts,

we are using CC3300 chip and have been evaluating that for quite some time. During the summer we updated CC33xx FW to release 1.0.0.9, and after that we noticed that WLAN TX Power was much higher than earlier. After some tests it's clear to me that the AntGain_2_4GHz setting in cc33xx-conf.bin configuration file doesn’t work anymore. It just doesn't affect to WLAN TX Power at all. Earlier we learned that RegDomain parameter needs to be 1 (FCC) or 2 (ETSI) in order to get AntGain_2_4GHz parameter to work, but now it doesn't work with any of the RegDomain settings anymore.

Is this a known bug and is it already fixed in the latest FW release 1.0.2.10?


Thanks & best regards,
Kaisa

  • 0
    TI__Genius 15001 points

    Hi Kaisa,

    Thanks for bringing this to my attention. I will try to replicate the behavior and follow up with my findings and next steps.

    Thanks,

    Rogelio

  • 0 in reply to RogelioD
    Prodigy 185 points

    Hi Rogelio,

    do you have any feedback regarding this issue?

    Best regards,

    Kaisa

  • +1 in reply to Kaisa_K
    TI__Mastermind 46675 points

    Hey Kaisa,

    Sorry for the late reply here, I was digging up some of the release notes for the year. This is not a bug, the PHY FW was adjusted to interpret this value differently. It will no longer adjust TX power with any RegDomain setting (matching the WW setting). This should simplify the implementations of the Power limit array - if migrating to the new FW you will need to reduce the Power limit accordingly. Now if you are generating a conf for multiple regions, they can now have aligning Power limit arrays even with differing RegDomain settings.

  • 0 in reply to Dylan Hubbard
    Expert 1561 points

    Hey Dylan,

    Is this change documented anywhere? I don't recall seeing it.

    Are there any other power related parameters that changed their behavior with regard to the RegDomain setting?

    Thanks,

    Dean

  • 0 in reply to Dylan Hubbard
    Prodigy 185 points

    Hi Dylan,

    thank you for the explanation. It's really not an issue that RegDomain doesn't affect to AntGain_2_4GHz anymore, but the issue is that AntGain_2_4GHz doesn't affect to TX Power at all and this is not aligned with your documentation, which still explains how AntGain_2_4GHz should affect. If there are such changes made in the behavior of the configuration settings, then these should be explained in the documentation as well. Otherwise it's really impossible for the users to know how to use these configurations.

    Best regards,
    Kaisa

  • +1 in reply to Kaisa_K
    TI__Mastermind 46675 points

    Hey Kaisa,

    Yes, fully aligned on the feedback here. We will make sure we get this rectified as soon as possible.

    Dean -  this also in response to your statement on the documentation, we are taking action to ensure our release notes that have critical implications to our customers are more clearly indicated in the release notes.