Hi,
I am using s112_nrf52_7.2.0_softdevice with nRF5_SDK_17.1.0 and iar embedded workbench. I can flash and run the application without any problem but when i try to program secure_bootloader_ble_s112_pca10040e or secure_bootloader_ble_s112_pca10040e_debug I get harfault exception (A coprocessor access error has occurred (CFSR.NOCP) while i am using FLOAT_ABI_SOFT. Here is my linker configuration.
Could you try this address instead, 0x27fff
Did you select nRF52805 in the General Options?
Also note this from the SDK release notes:
*****
Note for IAR 8 users:
When using IAR 8, you must apply the following workaround in the MDK:
- Apply a patch to modules/nrfx/mdk/compiler_abstraction.h at line 140
(fix the '__ALIGN()' macro definition): use the argument 'n' in the macro expansion instead of 'x'.
-------------------
Libraries for IAR 8 require wchar_t to be of size 32 bits while IAR 7 requires 16 bits.
To run a project using IAR 8, follow these instructions:
1. Open the IAR project in IAR 8. The IAR workbench will automatically generate an IAR 8 compatible project file.
2. If the project contains one of the precompiled libraries listed below, replace it
with the IAR 8 compatible alternative (there are no projects targeting nRF51 in this SDK).
3. Save the project.
4. When building the project, you might get the warning: "The header file 'cmsis_iar.h' is obsolete and should not be used. [...]".
- The problem is described in DevZone post: https://devzone.nordicsemi.com/f/nordic-q-a/31123/iar-ewarm-8-22-1-complains-about-cmsis_iar-h
The solution is to remove all occurrences of #include <cmsis_iar.h>.
The affected libraries are:
- micro-ecc crypto:
- IAR7: Includes library located in the folder named “…_iar\…”.
- IAR8: Switch to using the library from the folder named “…_armgcc\…”.
- nrf_cc310, nrf_cc310_bl, and nrf_oberon:
- IAR7: Link to a library where “short_wchar” is part of the folder name.
- IAR8: Link to a library without “short_wchar” in the folder name.
- Gazell, NFC Tag, and 802.15.4:
- IAR7: Includes the library where the file name ends with “_iar”.
- IAR8: Switch to using the library with similar file name that ends with “_gcc”.
*****
Did you select nRF52805 in the General Options?
Also note this from the SDK release notes:
*****
Note for IAR 8 users:
When using IAR 8, you must apply the following workaround in the MDK:
- Apply a patch to modules/nrfx/mdk/compiler_abstraction.h at line 140
(fix the '__ALIGN()' macro definition): use the argument 'n' in the macro expansion instead of 'x'.
-------------------
Libraries for IAR 8 require wchar_t to be of size 32 bits while IAR 7 requires 16 bits.
To run a project using IAR 8, follow these instructions:
1. Open the IAR project in IAR 8. The IAR workbench will automatically generate an IAR 8 compatible project file.
2. If the project contains one of the precompiled libraries listed below, replace it
with the IAR 8 compatible alternative (there are no projects targeting nRF51 in this SDK).
3. Save the project.
4. When building the project, you might get the warning: "The header file 'cmsis_iar.h' is obsolete and should not be used. [...]".
- The problem is described in DevZone post: https://devzone.nordicsemi.com/f/nordic-q-a/31123/iar-ewarm-8-22-1-complains-about-cmsis_iar-h
The solution is to remove all occurrences of #include <cmsis_iar.h>.
The affected libraries are:
- micro-ecc crypto:
- IAR7: Includes library located in the folder named “…_iar\…”.
- IAR8: Switch to using the library from the folder named “…_armgcc\…”.
- nrf_cc310, nrf_cc310_bl, and nrf_oberon:
- IAR7: Link to a library where “short_wchar” is part of the folder name.
- IAR8: Link to a library without “short_wchar” in the folder name.
- Gazell, NFC Tag, and 802.15.4:
- IAR7: Includes the library where the file name ends with “_iar”.
- IAR8: Switch to using the library with similar file name that ends with “_gcc”.
*****