• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 76 subscribers
  • Views 3331 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 205251
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Error 102/106/107 in Engineering C Errata

Ralph

Hi,

We're using SR3 v1.1 for several BLE R/C.

Early this month, we received information of Engineering C Errata.

It suggests that we upgrade to SR3 v1.2 for fixing some errors relative to RADIO issues (error 102/106/107).

After comparing these two version of codes, we think it is not possible for us to complete the upgrade and verification before the date of  mass-production.

Instead of upgrading to SR3 v1.2, we think that we could fix these errors only  in current code based on SR3 v1.1.

Studying the errata, we still no clue about how to fix them.

We are in a hurry to catch the mass-production date!

Can anyone tell how to fix these errors clearly?

Thanks!

  • 0

    Hi,

    What revision of the nRF52832 are you going into production with?

    As you have seen from the errata workaround section, there are 2 workaround options for revision 1.

    1 ) Update to SoftDevice s132_nrf52_4.0.2 or later.

    2) Apply the errata workaround-code before triggering the RXEN task.

    Option 2 only applies to solutions that don’t use the SoftDevice.

    You are therefore left with option 1

    Note that SR3 v1.1 uses S132 v.3.0.0 (no fix), and that SR3 v1.2 uses S132 v.5.1.0 (with fix)

  • 0

    Hi,

    Thanks for your replay. Below are answers and questions for you.

    1. I don't know what reversion of nRF52832 will be used in production. Got no answer when I asked people who are in charge of purchase and sales the chip. So no matter what reversion will be used in production, we have to make sure it will be OK.

    2. Is it OK for using SoftDevice reversion other than 3.0.0 in SR3 v1.1?

       Or, Can I use SoftDevice 4.0.2 or later in SR3 v1.1?

    3. In the errata workaround sections, it mentions using ESB and Gazell libraries of SDK 14.0.0 or later. Does it mean that I need copy them from SDK14 and paste onto SR3 v1.1? 

    Thanks!

  • 0 in reply to Ralph

    Hi,

    Ralph said:
    Or, Can I use SoftDevice 4.0.2 or later in SR3 v1.1?

    Yes, you can migrate the SR v1.1 code to use SoftDevice v.4.0.2 or later. But it will require work. We have migration documents in the SoftDevice .zip, found here. Depending on how you have structured your application, it could be easier to port your application to the SR3 v1.2 code-base. But it could also easier to migrate to SD v.4.0.2 from your SR v1.1 application project.

    Ralph said:
    . In the errata workaround sections, it mentions using ESB and Gazell libraries of SDK 14.0.0 or later. Does it mean that I need copy them from SDK14 and paste onto SR3 v1.1? 

    ESB and Gazell are Nordic proprietary radio protocols. SR3 uses Bluetooth low energy. ESB and Gazell are not used in SR3. So if you are not using ESB and Gazell in your application, you can ignore that section, and you don't need to copy anything.

  • 0 in reply to Sigurd

    Hi,

    Thanks for your information.

    I've checked the SoftDevice migration document.

    It seems that the effort of migration of SoftDevice is no less than of migrating to SR3 V1.2.

    We had a meeting and decided to migrate to SR3 V1.2.

    We'll check the amount of the older chip that can be used for production to figure out the schedule of this migration.

    Thank you anyway!

  • 0 in reply to Ralph

    Hi,

    I'd like to ask one thing: what will happen if we  using old softdevice on new chip?

    Does the error 102/106/107 will be corrected?

    If so, we can keep using SR3v1.1.

    Thanks!

Related
Terms of service