• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 41 subscribers
  • Views 119 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: CC33Conf Tool and CC33XX INI Parameter issues

CC33XX-SOFTWARE: is cc33xx-conf.bin / AntGain_2_4GHz issue fixed in FW release 1.0.0.7?

Kaisa_K
Prodigy 175 points
Part Number: CC33XX-SOFTWARE

Tool/software:

Hi TI team,

we have noticed that there is a new CC33xx FW release 1.0.0.7, but do you have any update related to the cc33xx-conf.bin and AntGain_2_4GHz issue mentioned in the previous thread? At least I couldn't find any mention about it in the CC33xx Linux Package release notes.

Thanks & best regards,
Kaisa

  • 0
    TI__Mastermind 25970 points

    Hi Kaisa,

    Just to confirm on the ask, you would like some clarity on the ability to change parameter 'AntGain_2_4GHz'? Are you looking for it to be configurable through cc33conf or INI Composer?

  • 0 in reply to Sabeeh Khan1
    Prodigy 175 points

    Hi Sabeeh,

    as reported in the original thread: If we change "AntGain_2_4GHz" value in cc33xx-conf.bin file, it doesn't affect to TX power at all with the Wireless firmware version 1.7.0.185 (CC33xx Linux Package 1.0.0.6). Earlier "AntGain_2_4GHz" tuning worked fine with the Wireless firmware version 1.7.0.120, meaning that the TX power was actually reduced accordingly.
    So the problem is not changing the "AntGain_2_4GHz" value, but the fact that it doesn't seem to affect to TX power anymore. And now the question is, should it be effective with the latest available FW 1.7.0.188 (CC33xx Linux Package 1.0.0.7)?

    Br,
    Kaisa

  • 0 in reply to Kaisa_K
    TI__Mastermind 25970 points

    Hi Kaisa,

    Understood, let me check with the team and I will report back by the end of this week.

  • +1 in reply to Sabeeh Khan1
    TI__Mastermind 25970 points

    Hi Kaisa,

    I got confirmation that there was an issue in the firmware with this field. It has been addressed in our upcoming release, which is planned to be publicly available by the end of this month. 

  • 0 in reply to Sabeeh Khan1
    Prodigy 175 points

    Hi Sabeeh,

    thank you for the confirmation, we shall then wait for the next release.

    Br,
    Kaisa