RF Driver: fsmSetupState is changing the rate word in the setup command in proprietary mode

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • TI Device Drivers
    • TIDRIVERS-1217
    • 3.30.00
    • 3.40.00
    • Hide
      When an application uses common to set bNoFsPowerUp, it actually ends up zeroing the 3rd bit of the rate word in the CMD_PROP_RADIO_DIV_SETUP object. We noticed this issue when running our CC1101 (low rate tx/rx) experiments. Our original rate was 0x5BC, after executing this line it was 0x5B8; this change in rate caused packets over a certain length to be incorrectly received, i.e. a CRC error.
      Show
      When an application uses common to set bNoFsPowerUp, it actually ends up zeroing the 3rd bit of the rate word in the CMD_PROP_RADIO_DIV_SETUP object. We noticed this issue when running our CC1101 (low rate tx/rx) experiments. Our original rate was 0x5BC, after executing this line it was 0x5B8; this change in rate caused packets over a certain length to be incorrectly received, i.e. a CRC error.

      RF Driver: fsmSetupState is changing the rate word in the setup command in proprietary mode

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-1003 - RF Driver: fsmSetupState is changin...
                SYNCHRONIZED
                • Last Sync Date: