Error 102/106/107 in Engineering C Errata

RE: Error 102/106/107 in Engineering C Errata

Ralph — Fri, 25 May 2018 07:48:51 GMT

Hi Sigurd,

Excellent.

Thanks for your explanation .

RE: Error 102/106/107 in Engineering C Errata

Sigurd — Fri, 25 May 2018 07:45:38 GMT

Hi Ralph,

[quote userid="52712" url="~/f/nordic-q-a/33360/error-102-106-107-in-engineering-c-errata/133325"]So S132 v4 or v5 works around issues #102, #106, #107 for revision 1 chip and revision 2 chip.[/quote]

Correct.

[quote userid="52712" url="~/f/nordic-q-a/33360/error-102-106-107-in-engineering-c-errata/133325"]S132 v6 uses HW fix by setting a register only for revision 2 devices? What if we use it for revision 1 chip, the issues won't be fixed? [/quote]

S132 v6 will automatically detect if it’s being used on a rev1 or rev2 chip.

If it detect a rev 1 device, it will apply the workaround for #102,#106 and #107

If it detect a rev 2 device, it will instead enable the HW fix(#182)

RE: Error 102/106/107 in Engineering C Errata

Ralph — Fri, 25 May 2018 02:48:30 GMT

Hi, Sigurd

"In the case you want erratums #102, #106, #107 fixed, on either revision 1 or revision 2, you need to use one of these softdevices:

S132 v4 or v5
S132 v6 (applies #182 for revision 2 devices, which enables a hardware fix for #102/106/107)

So S132 v4 or v5 works around issues #102, #106, #107 for revision 1 chip and revision 2 chip.

S132 v6 uses HW fix by setting a register only for revision 2 devices? What if we use it for revision 1 chip, the issues won't be fixed?

Is that correct?

Thanks.

RE: Error 102/106/107 in Engineering C Errata

Sigurd — Thu, 19 Apr 2018 12:11:10 GMT

Hi,

[quote userid="52712" url="~/f/nordic-q-a/33360/error-102-106-107-in-engineering-c-errata/128875"]Are the results of using SR3v1.1 on both Rev.1 and Rev. 2 chips the same?[/quote]

Yes, they will behave the same.

[quote userid="52712" url="~/f/nordic-q-a/33360/error-102-106-107-in-engineering-c-errata/128875"]Are the errors 102/106/107 corrected in old SR3v1.1with Rev 1 chip or not?[/quote]

They are not corrected in SR3v1.1, because SRv1.1 uses S132 v3.(fix was first added in S132 v4)

Some comments on the erratas:

102: The frequency at which this occurs is low (<0.1% of packets).

106: 1 in 1600 (<0.07%) randomly generated BLE addresses are affected.

107: BLE addresses are not affected.

RE: Error 102/106/107 in Engineering C Errata

Ralph — Thu, 19 Apr 2018 02:21:15 GMT

Hi,

Thanks for your clear answer.

We'd like to confirm something.

As you mentioned above, using old SoftDevice with new chip(Rev. 2) the chip will behave equal to a Rev. 1 chip. We have questions in this:

Are the results of using SR3v1.1 on both Rev.1 and Rev. 2 chips the same?
Are the errors 102/106/107 corrected in old SR3v1.1with Rev 1 chip or not?

RE: Error 102/106/107 in Engineering C Errata

Sigurd — Wed, 18 Apr 2018 13:08:56 GMT

Hi,

[quote userid="52712" url="~/f/nordic-q-a/33360/error-102-106-107-in-engineering-c-errata/128373"]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?[/quote]

No. If you use an old softdevice(older than v.6.0) with the new chip(revision 2), the chip will behave equal to a revision 1 chip.

In order for the fix that is implemented in revision 2 chip to take effect, the register described in Errata 182 will need to be written when you enable the RADIO peripheral. This will need to be handled by the SoftDevice(starting from S132 v.6.0).

Summarized:

In the case you want erratums #102, #106, #107 fixed, on either revision 1 or revision 2, you need to use one of these softdevices:

S132 v4 or v5
S132 v6 (applies #182 for revision 2 devices, which enables a hardware fix for #102/106/107)

In the case of using S132 v3 or older, you cannot workaround issues #102, #106, #107, and you cannot apply erratum #182 on revision 2 devices to enable the HW fix.

RE: Error 102/106/107 in Engineering C Errata

Ralph — Wed, 18 Apr 2018 09:40:44 GMT

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!

RE: Error 102/106/107 in Engineering C Errata

Ralph — Tue, 17 Apr 2018 07:07:34 GMT

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!

RE: Error 102/106/107 in Engineering C Errata

Sigurd — Mon, 16 Apr 2018 15:09:40 GMT

Hi,

[quote userid="52712" url="~/f/nordic-q-a/33360/error-102-106-107-in-engineering-c-errata/128373"]Or, Can I use SoftDevice 4.0.2 or later in SR3 v1.1?[/quote]

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.

[quote userid="52712" url="~/f/nordic-q-a/33360/error-102-106-107-in-engineering-c-errata/128373"]. 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? [/quote]

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.

RE: Error 102/106/107 in Engineering C Errata

Ralph — Mon, 16 Apr 2018 01:10:36 GMT

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!

RE: Error 102/106/107 in Engineering C Errata

Sigurd — Fri, 13 Apr 2018 13:21:45 GMT

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)