nrf52 Bootloader_secure_ble

RE: nrf52 Bootloader_secure_ble

Marco V. — Thu, 10 Jan 2019 15:00:35 GMT

Hello Howard,

I had the same problem, then the SDK v15.2.0 Release Notes helped me:

" Note for IAR 8 users: (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 intructions:

- Open the IAR project in IAR 8. The IAR workbench will automatically generate an IAR 8 compatible project file.

- 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).

- Save the project.

- 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: devzone.nordicsemi.com/.../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\…”

I've simply cross-compiled "_armgcc\" and switched the library and all seems to work correctly.

RE: nrf52 Bootloader_secure_ble

howard n2wx — Fri, 10 Aug 2018 19:34:17 GMT

Thank you Bjørn

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Thu, 09 Aug 2018 07:11:48 GMT

HI Howard, please refer this section of the SDK v15.0.0 Release Notes

Note for IAR 8 users:
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 intructions:
- Open the IAR project in IAR 8. The IAR workbench will automatically generate an IAR 8 compatible project file.
- 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).
- Save the project.
- 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: devzone.nordicsemi.com/.../iar-ewarm-8-22-1-complains-about-cmsis_iar-h
   The solution is to remove all occurrences of #include <cmsis_iar.h>.

RE: nrf52 Bootloader_secure_ble

howard n2wx — Fri, 03 Aug 2018 20:25:59 GMT

Bjørn, I'm on SDK15 but with IAR 8.20.2. IAR 8 has taken me from simple examples to adding multiple instances of ble_nus and single instance ble_nus_c to the hrscs_relay example and but for DFU I have an MVP. I'd like to report that 8.20.2 works well with SDK15.

Does the internal report system have any additional notes on IAR 8.20 and the need to remove -short-wchar from the micro-ecc Makefile? I have the same issue as Chris does if I don't remove -short-wchar, that is, a fatal link error complaining about micro-ecc's 16 bit wchar_t and IAR's 32 bit wchar_t.

Thank you, Howard

RE: nrf52 Bootloader_secure_ble

Chris — Tue, 16 Jan 2018 14:08:24 GMT

Perfect, thank you

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Tue, 16 Jan 2018 13:54:32 GMT

You should only have to clone the micro-ecc library to the folder specified in the Install micro-ecc section. SES uses GCC as its compiler so it should be able to compile the micro-ecc source together with the rest of the project.

RE: nrf52 Bootloader_secure_ble

Chris — Tue, 16 Jan 2018 13:26:53 GMT

Bjorn- Thanks, I am using v14.2.0. As far as I can tell, I still need micro-ecc:

infocenter.nordicsemi.com/.../sdk_app_serial_dfu_bootloader.html

Should I re-make the library using armgcc when using SES?

-Chris

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Tue, 16 Jan 2018 07:10:15 GMT

@cphelan( chris) : SES is fully supported in SDK v14.2.0, i.e. SES projects are generated for all examples so the bootloader example should compile and function out of the box. I suggest you move to the latest version of the SDK.

RE: nrf52 Bootloader_secure_ble

Chris — Mon, 15 Jan 2018 21:45:01 GMT

Bjorn -

I've started working with SES but potentially hit a roadblock with DFU and uECC. Is there a SES option for compiling this library? If not, is there a workaround?

-Chris

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Mon, 08 Jan 2018 09:40:34 GMT

I am not that familiar with IAR, as I've mostly been using Keil and now SES. Hence, my opinion might be a bit biased, but I would say that the main advantages are:

the free perpetual license for SES for development on Nordic ICs.
SES is cross-platform, i.e. runson Windows, Linux and macOS.
SES allows you to view logging information sent using Seggers RTT( one of the two logging backends we support in our SDK) directly in the SES IDE, rather than having to open a RTT terminal window.
Integrated Debugger with advanced debug information windows and direct J-Link integration.
Project converter for KEIL/IAR projects to SES.

As for testing, we've signed a licensing agreement with Segger so any issues that are reported with the IDE are reported back to SEGGER by us so that they are fixed as soon as possible.

RE: nrf52 Bootloader_secure_ble

Chris — Sat, 06 Jan 2018 01:13:24 GMT

Bjorn - One last question on this topic - would you recommend segger embedded studio over IAR? I know SES is now supported, but I don't know how thoroughly it has been tested.

RE: nrf52 Bootloader_secure_ble

Chris — Fri, 05 Jan 2018 21:51:51 GMT

Thanks. Looks like 7.8.4 still works with our license server - fingers crossed that this continues.

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Fri, 05 Jan 2018 09:30:30 GMT

Unfortunately, we do not have any documentation other than the cases reported here on DevZone. We're working on updating our build system to a newer version of IAR, but I cannot give you any ETA on this. So, my suggestion would be to try to downgrade the IAR version, if that is not possible then try searching for solutions on DevZone. If you cant find the solution for a issue here on DevZOne then you can contact us through our MyPage system and then we'll try to look through our internal support system.

RE: nrf52 Bootloader_secure_ble

Chris — Thu, 04 Jan 2018 18:53:44 GMT

Thanks. Unfortunately IARv7.x versions are fairly old at this point, and I suspect we are going to have issues with our IAR license server supporting these older versions (but we are going to try nonetheless). I know this isn't really your problem, but it would be good to know if there is any documentation covering the issues I might run in to if I do proceed with an up-to-date version of IAR. Is there anything like this available?

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Thu, 04 Jan 2018 07:36:26 GMT

Yes, we're still using IAR v7.80.4 for test and verfication of the latest SDK version, i.e. v14.2.0. THus, my recommendation would be to use IAR v7.x.x.

RE: nrf52 Bootloader_secure_ble

Chris — Thu, 04 Jan 2018 02:12:44 GMT

Bjørn - are your comments above regarding IAR v8.x still valid? I am running IAR 8.11.3, to date no IAR-related issues, but I've also just been using the nrf52832 as a MCU. I am now beginning to add in DFU and soon BLE as well, and I'd rather not have to debug IAR while debugging my code as well!

Note that I arrived at this post because I received the same error as hhuseyin. Please let me know if I should make the correction you recommend in the makefile, or if I need to move to an older version of IAR.

-Chris

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Tue, 06 Jun 2017 13:35:40 GMT

@hhuseyin: Just discussed this with one of our SW developers and according to him you need to use IAR v7.x as there are many changes, described here, that are not compatible with our SDK yet, i.e. will be in a future release. So, for now, stay with IAR v7.x and disregard my previous comment. Removing the -fshort-wchar flag may remove the linker errors, but we cant guarantee that the rest of the SDK source will behave as it is intended to with v8.x.

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Tue, 06 Jun 2017 13:06:30 GMT

@hhuseyin: I apologize for my late reply, I was out of office on travel last week. Are you using the IAR v8.10 or v8.11? If so you need to modify the Makefile in external\micro-ecc\nrf52_iar\armgcc to not use the -fshort-wchar flag, i.e. line 32 in the Makefile should look like this

CFLAGS += -fno-builtin --short-enums

This is because IAR v7.x set wchar_t size 2 bytes(16bits), but v8.x sets it to 4 bytes(32bits) so by removing the -fshort-wchar flag you set the size to 4 bytes.

RE: nrf52 Bootloader_secure_ble

hhuseyin — Mon, 29 May 2017 11:57:58 GMT

I'm waiting for your answer

RE: nrf52 Bootloader_secure_ble

hhuseyin — Sat, 27 May 2017 09:02:56 GMT

I am using IAR. After I create public_key.c, I copy it to dfu_public_key.c in the dfu_req_handling folder. I get this error

RE: nrf52 Bootloader_secure_ble

bjorn-spockeli — Fri, 26 May 2017 11:27:30 GMT

How are you compiling the bootloader project? Are you using Keil, GCC, IAR? Have you followed the compile instructions stated in the Cryptographic Library documentation?