Bluetooth BLE product development strategy

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bluetooth BLE product development strategy

Jump to solution
1,333 Views
mjbcswitzerland
Specialist V

Hi NXP

I would like to ask about how best to implement a product using the KW30 for Bluetooth BLE operation.
As a starting point using the connectivity stack one can start development on the FRDM-KW41Z with its SDK but this contains libraries, including one that is named "lib_ble_kw41z_controller.a".

How is the move then made to a device that doesn't have its own SDK (like the KW30) since the above library doesn't sound to be suitable?

Specific questions:
- the SDK project import supplies the libraries. Where do these come from and is source code available?
- the library is suitable for MCUXpresso (and presumably generally GCC and I think that I saw that it is also available for IAR (?)) but what would be needed for Keil uVision (or others)?

Thanks in advance

Regards

Mark

Labels (1)
Tags (2)
0 Kudos
Reply
1 Solution
1,146 Views
Sebastian_Del_Rio
NXP Employee
NXP Employee

Hello Mark, I hope you're doing well!

 

I'm really sorry for the confusion, I might have not fully understood what you meant, but I believe I do now.

 

The only supported IDE for the KW30Z is IAR Embedded Workbench, and the only way to develop on it with our libraries should be using that IDE and the already precompiled libraries in the connectivity software, nonetheless, if you are just starting to develop I would recommend you to use the KW31Z as it is the newest version of our Bluetooth LE  and it is compliant with 2.4 Bluetooth Low Energy version 4.2and has a better RF performance than the KW30Z.

 

I'm aware that there is no library for the KW31Z available, but the KW41Z is compatible with the KW31Z, as long as you only use the available pins in the KW31Z and don't enable anything related to Thread, ZigBee or 802.15.4. If you only use the GFSK or the Bluetooth LE examples, you should be able to use the examples you create for the KW41Z in the KW31Z.

 

But, it is not possible to use the KW41Z code in the KW30Z code, as the precompiled libraries are not compatible between them.

 

The libraries are precompiled for delivery and those are not available to share and that it's the only way we provide them, I'm sorry for the inconveniences this might cause you.

 

Again, if you are just starting your project, I would recommend you use the KW31Z, as it supports Bluetooth LE 4.2, it's also being constantly updated with each maintenance release, and also, it has support for IAR and MCUXpresso.

 

Please let me know if you have any additional questions, and sorry for any inconveniences this might cause you. 

 

Best regards,

Sebastian

View solution in original post

0 Kudos
Reply
6 Replies
1,147 Views
Sebastian_Del_Rio
NXP Employee
NXP Employee

Hello Mark, I hope you're doing well!

 

I'm really sorry for the confusion, I might have not fully understood what you meant, but I believe I do now.

 

The only supported IDE for the KW30Z is IAR Embedded Workbench, and the only way to develop on it with our libraries should be using that IDE and the already precompiled libraries in the connectivity software, nonetheless, if you are just starting to develop I would recommend you to use the KW31Z as it is the newest version of our Bluetooth LE  and it is compliant with 2.4 Bluetooth Low Energy version 4.2and has a better RF performance than the KW30Z.

 

I'm aware that there is no library for the KW31Z available, but the KW41Z is compatible with the KW31Z, as long as you only use the available pins in the KW31Z and don't enable anything related to Thread, ZigBee or 802.15.4. If you only use the GFSK or the Bluetooth LE examples, you should be able to use the examples you create for the KW41Z in the KW31Z.

 

But, it is not possible to use the KW41Z code in the KW30Z code, as the precompiled libraries are not compatible between them.

 

The libraries are precompiled for delivery and those are not available to share and that it's the only way we provide them, I'm sorry for the inconveniences this might cause you.

 

Again, if you are just starting your project, I would recommend you use the KW31Z, as it supports Bluetooth LE 4.2, it's also being constantly updated with each maintenance release, and also, it has support for IAR and MCUXpresso.

 

Please let me know if you have any additional questions, and sorry for any inconveniences this might cause you. 

 

Best regards,

Sebastian

0 Kudos
Reply
1,146 Views
mjbcswitzerland
Specialist V

Many thanks Sebastian

That is exactly the answer that was being looked for.
The MKW31Z256VHT4 will be used in BLE mode based on the KW41 library as used in the MCUXpresso examples.

Regards

Mark

0 Kudos
Reply
1,146 Views
Sebastian_Del_Rio
NXP Employee
NXP Employee

Hello Mark, I hope you're doing well!

 

I'm really sorry to say, but it's not possible to share .a libraries because they're private and property of NXP. This is so we can guarantee that they're working correctly as the specification mentions.

 

I'm deeply sorry for any inconveniences this may cause.

 

Best regards,

Sebastian

0 Kudos
Reply
1,145 Views
mjbcswitzerland
Specialist V

Hello Sebastian

Can you tell me whether libraries (*.a files) are available for IAR and/or Keil users?

I have started with the SDK for the FRDM-KW41Z, with the final product based on a KW30. For the KW31 processor I can also build an SDK but there is no project to import to supply an appropriate BLE library (eg. lib_ble_kw31z_controller.a)

I note that there is neither an SDK for the FRDM-KW40Z nor the KW40Z processor, which is why I chose the FRDM-KW41F rather than the FRDM-KW40Z.

Once the application has been completed on the FRDM-KW41Z will I be able to use the same libraries for the KW30 and if not, where can they be obtained from since it is not possible to build them ourselves.

Thanks for the clarification.

Regards

Mark

0 Kudos
Reply
1,146 Views
Sebastian_Del_Rio
NXP Employee
NXP Employee

Hello Mark, I hope you're doing well!

 

I'm really sorry, but as I said before, *.a files are also not provided for Keil or IAR users, as they are private and property of NXP so we can guarantee that they're working as specified.

 

Again, I'm very sorry for any inconveniences this may cause.

 

Best regards,

Sebastian

0 Kudos
Reply
1,146 Views
mjbcswitzerland
Specialist V

Hi Sebastian

I understand that only *.a files are provided (not source) and now I understand that they are not provided for IAR or Keil users (although the KW40Z connectivity software V1.0.1 from Freescale, and used in HEXIWEAR, does include "ble_controller_lib.a" which is for IAR).

However the open question is still whether if one develops with the SDK BLE resources for KW41Z can one subsequently use these libraries on the KW30? And if not, where do the libraries come from? Presently the project is on hold until there is clarity that the KW30 can practically be used (i.e that it is really supported, and how).

I highlighted the missed question in the previous post too.

Thanks

Regards

Mark

0 Kudos
Reply