LOCATION OF NR51_ERRATAS.H

RE: LOCATION OF NR51_ERRATAS.H

Simonr — Tue, 05 Oct 2021 07:41:33 GMT

a) You should also be able to flash the SoftDevice onto the board as long as you erase it between writes. Can you post what exactly the "download failed" error says?

b) Yes, erratas.h files should be included.

2. The erratas.h file won't be included in the SDK at all. It is part of the Device family pack in Keil, and not in the SDK.

b) The No such file or directory is caused by the nrf51_erratas.h header not being found for example. Any other errors you need an explanation for?

Best regards,

Simon

RE: LOCATION OF NR51_ERRATAS.H

Robin — Thu, 30 Sep 2021 18:41:22 GMT

Hello again Simonr,

It seems that I have confused you more than clarify my questions. So let me try again.

1a.) This problem began when I was trying to reprogram 10028 and 10040 boards that I had inadvertently corrupted with the wrong code. In the process of trying to correct, I was unable to download the SD to either board. Non-descriptive error messages stating that either the erase or the download failed occurred. Those messages ending in the phrases "... Cortex M0", or "... Cortex M4" depending, of course, on which board I was attempting to reprogram. I found I can download SD's, but only after an nrfjprog --recover. However, subsequent SD download attempt will fail if not proceeded by another nrfjprog --recover. So the fundamental questions;. Is this normal, is the SD protected from erasure on these boards? Or is there something wrong with my projects for these boards that is causing these errors?

1b.) ...protected from errant code generation when proceeding to newer Nordic devices and SDK's.

2.) Both the working and non-working SDK folders sit at the same directory level. The only difference is when they were downloaded and installed on my computer, and perhaps the version of Keil that was installed at those times. Why would one include the erratas, and one not? Why would one exhibit the error/warning posted above, and one not?

2a) Thank you for this I will run it by Arm/Keil support.

2b) ie what would be causing the above posted error and warning, missing files, or errant code in Arm provided files?

Thanks

Robin @ T L

RE: LOCATION OF NR51_ERRATAS.H

Simonr — Thu, 30 Sep 2021 08:00:49 GMT

a) Can you specify what you mean about erasure protection of the SoftDevice?

b) You should indeed include the erratas.h file in your project. Not sure what you refer to the project being protected from.

2. What is the difference between the "working" SDK path and the non-working one? If the non-working SDK is located further "down" the path than the working one, can you try moving it closer to the root (C:\ or D:\).

a) I guess the MDK will need to check that the system_nrfxx.c file is supported by the SDK version used.

b) This I'm not sure about unfortunately.

Best regards,

Simon

RE: LOCATION OF NR51_ERRATAS.H

Robin — Wed, 29 Sep 2021 16:00:31 GMT

Hello again Simonr,

First of all, I recognize where the blame lies here, but need Nordic info to help resolve the issue correctly. So, thank you again for your continued support. I have Keil support work things from there end as well. That said, let me rephrase, and reprioritize these questions a bit:

1.) I have an SDK that seem to be working fine, but for the issue of subsequent downloads of the SD. It does not call out the erratas.h file. So:

a.) Is the issue of failed subsequent SD downloads normal due to some such feature as erasure protection?

b.) Would my project be better protected if I were to update it to include the erratas?

2.) The error and warning are posted above in my original post. I believe the system_nrf51.c file in my "working" SDK path come from within that path, not the path you suggested.

a.) What can I suggest to Arm/Keil support to correct this bug in their MDK install?

b.) Is this just a pathing issue, or is there errant content in one or more of their provided source files?

I hope this helps clarify what I need to insure my project is best configured for our next upgrade to a later Nordic device and SDK.

Thanks again,

Robin @ TL

RE: LOCATION OF NR51_ERRATAS.H

Simonr — Tue, 28 Sep 2021 08:54:43 GMT

Yes, this should apply for the nRF51 as well, but you need to find the system_nrf51.c file instead of nrf52 for the device family pack you're using.

It is not an issue that we at Nordic can resolve I'm afraid, as it is a bug in the MDK, specific to newer MDKs in the Keil IDE.

What error/warning are you seeing with the SoftDevice? In Keil, you will need to flash the SoftDevice onto the board separately, and then the application onto the board afterwards.

Best regards,

Simon

RE: LOCATION OF NR51_ERRATAS.H

Robin — Mon, 27 Sep 2021 14:58:22 GMT

Hello Simon,

The device is an NRF51. Does the solution using the NRF52 pack still apply?

Interesting fact though, the my original project does not call for the erratas include file at all.

Can this be explained? Same SDK (12.3.0), bit no callout of that file in any project file, and it builds, loads and runs perfectly, with the exception of the failing subsequent load of the SD, which is another question I need answered. Is this normal operations Nordic Development Boards?

What about the above warning?

And finally, why all this only with a recently downloaded virgin SDK?

RE: LOCATION OF NR51_ERRATAS.H

Simonr — Mon, 27 Sep 2021 13:32:55 GMT

Hi Robin

The nrfxx_erratas.h files should be located in C:\Users\_USERNAME_\AppData\Local\Arm\Packs\NordicSemiconductor\nRF_DeviceFamilyPack\8.xx.x\Device\Include\. In the past, this error has been caused by a bug of MDK-ARM. The MDK always copies 'system_nrf5x.c' from the latest software pack, so even though you select the supported version it might try to use the newer one. One solution is to replace RTE\Device\nRF52832_xxAA\system_nrf52.c using the system_nrf52.c file from the Software pack (Devicefamily pack) that the SDK you're using supports.

Best regards,

Simon