To the kind attention of Nordic support team,
We are very interested indeed in using your nRF52840 and nRF52810 devices in our projects. We also would like to use your gazell protocol for them to communicate, in particular gazell with dynamic pairing, because of the built in security features it offers. Nevertheless, we have an urgent need at this stage to know and evaluate what is the software toolchain environment (Keil, IAR, Segger Embedded Studio), if any, that truly guarantees an out of the box working for the gazell dynamic pairing with encryption software examples that you kindly provide in SDK 16.0.0. Hope my asking is not inappropriate, but it is really important for us to understand the current state of the porting in various environments, so that we can experience at this stage an out of the box functioning, and should the need arise, make a conscious decision about the porting problems that we could have to address. Really hope that this is not an inconvenient question, and it is not much trouble for you to reply. It seems that IAR projects are experiencing some compilation issues when using IAR version 8, and Segger Embedded Studio projects are not provided for what we need in our projects. Please, correct me if I'm wrong. Should I conclude that actual Keil porting offers an out of the box working for host and device gazell dynamic pairing? I couldn't give a try to that environment, yet. In every case, let me thank you for all your valuable work and attention that you have for all your customers. Let me excuse in advance should my question be a little bit out of the scope.
Both IAR and Keil should work out-of-the-box. Can you tell me more about what compiling issues you have? Keep in mind that the projects are set up for the nRF52840 and nRF52832 devices, so to get it to work on an nRF52810, you'll have to follow the Transferring the project to nRF52810 hardware guide on the Infocenter.
Hi, thank you for replying us. I just downloaded sdk16.0.0 and opened the iar project gzll_dynamic_pairing_device.eww.
As I said we are in evaluation, right now. I don't want to say that we will be using IAR toolchain in the future, and I have not access to keil toolchain right now. We would like also to use Segger Embedded Studio, still we want to be sure that there are no known issues with precompiled libraries. Thank you
I found something about this issue in:
Still, not having at our disposal Keil, having troubles with IAR and not having the Segger project, as you see the evaluation becomes a little difficult. Having said that, we are really great estimators of Nordic hardware products and tools. Maybe you can give me the best advise possible in order to quickly evaluate these gazell pairing libraries that are very interesting for us. Hope you can understand. Best regards
This compiler issue should be easily fixed by switching to the IAR 8 compatible libraries as stated in the SDK release notes.
To run a project using IAR 8, follow these instructions:
- Open the IAR project in IAR8. 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.-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 solution to this is to remove all occurrences of #include <cmsis_iar.h>.
The library you need to switch out, in this case, is the library(ies) where the file name ends with _iar, and switch it with the file name ending with _gcc. Alternatively, you can use IAR 7 if you want it to work right away.
As for the missing SES project, this seems to be missing for some reason, and I've reported it internally. Hopefully, we will get this into our next SDK release, but I can't make any guarantees. In the meantime, you can import the Keil project to SES by following our guide here. Sorry about any inconvenience this may cause.
That is clear. Thank you