This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52832 Errata 78 , 182 , 204

3.19 [78] TIMER: High current consumption when using timer STOP task only

    I'm using app_timer_stop. But I do not know how to cope with this errata.
    Does the timer stop that this Errata says is pointing to function "ret_code_t app_timer_stop (app_timer_id_t timer_id)"?

3.48 [182] RADIO: Fixes for anomalies #102, #106, and #107 do not take effect

    I can not find the process that enabled the "register (0xFFC) POWER".
    Specifically, where should we add the processing of measures?

3.54 [204] RADIO: Switching beween TX and RX causes unwanted emissions

    I don't know where I'm switching between TX and RX.
    For example, sending BLE uses sd_ble_gatts_hvx (), which is a process in the SDK, so deeper nesting can not be seen.
    Also, there is a Define called "RADIO_STATE_STATE_RxDisable", which also seems to be unused.
    Please tell me how to respond.

Parents Reply Children
  • Implemented measures for Errata 182 in SDK 13.1, referring to SDK 15.3. Thank you.

    We apologize for the inconvenience, but I would like the 204 response method.

  • The SoftDevices are not affected by Errata 204 as they always transition radio states through the DISABLE task.

    Errata 204 is also only valid when using an external PA, and whether or not you need to take care of this unwanted emission depends on which kind of regulatory standard you are testing against. For your case, probably a close to worldwide certification, at least as far as the requirements go, you will probably run into the ETSI EN 300 328 which from what I understand is the most 'problematic' standard. In any case it is at least to some extent dependent on how you define the radio operation, personally I think it makes sense to consider the unwanted emission a part of the TX emission, and as such you should not need to worry about it as long as you do not use the channels at the bottom of the band (or transition through DISABLED for those). Also, there is no strict requirement for this, and it is not tested for, it is only found if you dig extra into the actual emissions and interpret the standard the most strict possible way.

  • Thanks for investigating.
    This thread close because it resolved.

Related