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

RTE\Device\nRF52832_xxAA\system_nrf52.c(29): error: #5: cannot open source input file "nrf_erratas.h": No such file or directory

I am using nRF52832, And SDK 15.3, the ble_app_blinky project,

   a.   if i have installed only the latest version of Device family 8.29.0 ,  when i try to build the project, it asks for permission to install 8.24.1 also.as shown in below fig

b. If I install version 8.24.1 in the pack installer as shown below, I get an error with erratas.h file



I have tried the solution given in other thread, to delete a file in module folder. But the error still persists. 

Can anyone kindly guide me?

Parents Reply Children
  • Hi,

    I had exactly the same problem but finally I've sorted this issue:

    1. Remove nRF_DeviceFamilyPack version 8.29 because it looks like automatically add to system_nrf_528xx #include "nrf_erratas.h" which makes a problem.

    I am using 8.24.1 

    2. Close Keil

    2. Unzip once again the SDK and open blinky project (just to clear)

    3. Compile and should work.

  • i have uploaded sdk 15 BLE blinky example, s132 soft device

    The nrf connect reads as below,

    2019-11-11T07:50:18.248Z INFO Application data folder: C:\Users\bjnag\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
    2019-11-11T07:50:19.780Z DEBUG App pc-nrfconnect-programmer v1.2.3 official
    2019-11-11T07:50:19.781Z DEBUG App path: C:\Users\bjnag\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
    2019-11-11T07:50:19.781Z DEBUG nRFConnect 3.2.0 is supported by the app (^3.2.0)
    2019-11-11T07:50:19.781Z DEBUG nRFConnect path: C:\Users\bjnag\AppData\Local\Programs\nrfconnect\resources\app.asar
    2019-11-11T07:50:19.782Z DEBUG HomeDir: C:\Users\bjnag
    2019-11-11T07:50:19.782Z DEBUG TmpDir: C:\Users\bjnag\AppData\Local\Temp
    2019-11-11T07:50:19.847Z INFO Using nrfjprog library 10.3.0, pc-nrfjprog-js 1.5.8
    2019-11-11T07:50:28.933Z INFO Using nrfjprog to communicate with target
    2019-11-11T07:51:22.259Z INFO Target device closed.
    2019-11-11T07:51:24.473Z INFO Using nrfjprog to communicate with target
    2019-11-11T07:51:26.998Z INFO Using J-Link Software version 6.50
    2019-11-11T07:51:32.641Z INFO Segger serial:  519001316
    2019-11-11T07:51:32.642Z INFO Segger speed:  2000  kHz
    2019-11-11T07:51:32.643Z INFO Segger version:  J-Link Lite-Cortex-M V9 compiled May 17 2019 09:50:01
    2019-11-11T07:51:32.683Z INFO Probed: 519001316.
    2019-11-11T07:51:32.684Z INFO Model: NRF52832_xxAA_REV1.
    2019-11-11T07:51:32.685Z INFO RAM: 64KiB.
    2019-11-11T07:51:32.685Z INFO Flash: 512KiB in pages of 4KiB.
    2019-11-11T07:51:36.112Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T07:51:41.098Z INFO Non-volatile memory has been read. 5 non-empty memory blocks identified.
    2019-11-11T07:51:41.259Z INFO SoftDevice detected, id 0x81 (S132 v2.0.0)
    2019-11-11T07:53:32.606Z INFO Using nrfjprog to communicate with target
    2019-11-11T07:53:35.425Z INFO Using J-Link Software version 6.50
    2019-11-11T07:53:38.350Z INFO Segger serial:  519001316
    2019-11-11T07:53:38.351Z INFO Segger speed:  2000  kHz
    2019-11-11T07:53:38.351Z INFO Segger version:  J-Link Lite-Cortex-M V9 compiled May 17 2019 09:50:01
    2019-11-11T07:53:38.370Z INFO Probed: 519001316.
    2019-11-11T07:53:38.371Z INFO Model: NRF52832_xxAA_REV1.
    2019-11-11T07:53:38.371Z INFO RAM: 64KiB.
    2019-11-11T07:53:38.371Z INFO Flash: 512KiB in pages of 4KiB.
    2019-11-11T07:53:40.198Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T07:53:44.902Z INFO Non-volatile memory has been read. 6 non-empty memory blocks identified.
    2019-11-11T07:53:45.102Z INFO SoftDevice detected, id 0x81 (S132 v2.0.0)
    2019-11-11T07:54:01.696Z INFO Recovery procedure finished
    2019-11-11T07:54:01.711Z INFO Using nrfjprog to communicate with target
    2019-11-11T07:54:03.836Z INFO Using J-Link Software version 6.50
    2019-11-11T07:54:06.367Z INFO Segger serial:  519001316
    2019-11-11T07:54:06.367Z INFO Segger speed:  2000  kHz
    2019-11-11T07:54:06.367Z INFO Segger version:  J-Link Lite-Cortex-M V9 compiled May 17 2019 09:50:01
    2019-11-11T07:54:06.385Z INFO Probed: 519001316.
    2019-11-11T07:54:06.386Z INFO Model: NRF52832_xxAA_REV1.
    2019-11-11T07:54:06.386Z INFO RAM: 64KiB.
    2019-11-11T07:54:06.386Z INFO Flash: 512KiB in pages of 4KiB.
    2019-11-11T07:54:08.501Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T07:54:13.145Z INFO Non-volatile memory has been read. 1 non-empty memory blocks identified.
    2019-11-11T07:54:15.223Z INFO Parsing HEX file:  C:\Users\bjnag\Desktop\Softwares\s132_nrf52_7.0.1_softdevice.hex
    2019-11-11T07:54:15.435Z INFO File was last modified at  8/29/2019, 10:57:45 AM
    2019-11-11T07:54:15.600Z INFO Data block: 0x00000000-0x00000B00 (0x00000B00  bytes long)
    2019-11-11T07:54:15.601Z INFO Data block: 0x00001000-0x000258C0 (0x000248C0  bytes long)
    2019-11-11T07:54:15.603Z INFO SoftDevice detected, id 0xCB (S132 v7.0.1)
    2019-11-11T07:54:22.910Z INFO Writing procedure starts
    2019-11-11T07:54:32.305Z INFO Write procedure finished
    2019-11-11T07:54:32.311Z INFO Using nrfjprog to communicate with target
    2019-11-11T07:54:34.588Z INFO Using J-Link Software version 6.50
    2019-11-11T07:54:37.345Z INFO Segger serial:  519001316
    2019-11-11T07:54:37.346Z INFO Segger speed:  2000  kHz
    2019-11-11T07:54:37.346Z INFO Segger version:  J-Link Lite-Cortex-M V9 compiled May 17 2019 09:50:01
    2019-11-11T07:54:37.368Z INFO Probed: 519001316.
    2019-11-11T07:54:37.369Z INFO Model: NRF52832_xxAA_REV1.
    2019-11-11T07:54:37.369Z INFO RAM: 64KiB.
    2019-11-11T07:54:37.369Z INFO Flash: 512KiB in pages of 4KiB.
    2019-11-11T07:54:39.286Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T07:54:44.197Z INFO Non-volatile memory has been read. 3 non-empty memory blocks identified.
    2019-11-11T07:54:44.334Z INFO SoftDevice detected, id 0xCB (S132 v7.0.1)
    2019-11-11T07:54:44.336Z INFO SoftDevice detected, id 0xCB (S132 v7.0.1)
    2019-11-11T07:54:54.820Z INFO Using nrfjprog to communicate with target
    2019-11-11T07:54:57.112Z INFO Using J-Link Software version 6.50
    2019-11-11T07:54:59.873Z INFO Segger serial:  519001316
    2019-11-11T07:54:59.873Z INFO Segger speed:  2000  kHz
    2019-11-11T07:54:59.873Z INFO Segger version:  J-Link Lite-Cortex-M V9 compiled May 17 2019 09:50:01
    2019-11-11T07:54:59.893Z INFO Probed: 519001316.
    2019-11-11T07:54:59.894Z INFO Model: NRF52832_xxAA_REV1.
    2019-11-11T07:54:59.894Z INFO RAM: 64KiB.
    2019-11-11T07:54:59.896Z INFO Flash: 512KiB in pages of 4KiB.
    2019-11-11T07:55:02.055Z INFO Reading device non-volatile memory. This may take a few seconds.
    2019-11-11T07:55:06.762Z INFO Non-volatile memory has been read. 4 non-empty memory blocks identified.
    2019-11-11T07:55:06.899Z INFO SoftDevice detected, id 0xCB (S132 v7.0.1)
    2019-11-11T07:55:06.901Z INFO SoftDevice detected, id 0xCB (S132 v7.0.1)
    





    But, when i open BLE of nRF COnnect, i get the following error
    08:55:11.147	Application data folder: C:\Users\bjnag\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
    08:55:15.499	Validating connectivity firmware for device with serial number 000519001316...
    08:55:18.629	Error while setting up device 000519001316: No serial port available for device with serial number 000519001316
    08:55:18.636	Device closed.
    08:55:57.585	Validating connectivity firmware for device with serial number 000519001316...
    08:55:59.726	Error while setting up device 000519001316: No serial port available for device with serial number 000519001316
    08:55:59.730	Device closed.
    09:02:04.763	Validating connectivity firmware for device with serial number 000519001316...
    09:02:07.461	Error while setting up device 000519001316: No serial port available for device with serial number 000519001316
    09:02:07.467	Device closed.

    ANd i cant view the device in App either

  • Hi,

    Problem is not related to the previous one. Something silly with com port. 

    If you use win10 try to go to the device manager and disable this specific com port and enable it once again. then restart nrf connect and try. 

Related