• State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 67 subscribers
  • Views 4678 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 103677
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to develop open source software for nRF51 series?

d00616

Hello,

i want to develop open source software for nRF51 but i think the SDK licensing is to restrictive. I cannot use any of provided example code because its permits redistribution. So i must waste many hours to create own examples using available documentation. Why? Why its not possible to license all example code under an open source compatible license?

For me it's o.k. to sell an evaluation or development kit to get access to the SDK and softdevices but i want to share my code.

I'm sure making nRF51 SDK more compatible to open source software helps to sell much more MCU's and development kits. I think there is a big market for small and power efficient MCU's with BLE/ANT+ and open source compatibility. The question is what vendor provides this MCU first.

Parents
  • 0

    I am also interested in open sourcing some work based on NRF51. I have been experimenting with the mbed API: mbed.org/.../ and that's starting to be usable.

    I think mbed is supposed to be open source (Apache 2 license?), the Nordic code published on the mbed repositories so far has a mix of copyright headers though, some still claiming the code to be confidential, which is a little farcical when it was released by Nordic to a public repository, I presume that's an oversight but would be good to have clarity.

    I would still love to see a more open release of the NRF51 SDK though... the mbed libraries are great for more easy-to-understand examples but not as flexible and currently don't feel quite "production ready". It would also help with the great annoyance that occurs every time Nordic release a new version of the SDK and I have to figure out what changed compared to the previous one, rather than just being able to look at the commits.

Reply
  • 0

    I am also interested in open sourcing some work based on NRF51. I have been experimenting with the mbed API: mbed.org/.../ and that's starting to be usable.

    I think mbed is supposed to be open source (Apache 2 license?), the Nordic code published on the mbed repositories so far has a mix of copyright headers though, some still claiming the code to be confidential, which is a little farcical when it was released by Nordic to a public repository, I presume that's an oversight but would be good to have clarity.

    I would still love to see a more open release of the NRF51 SDK though... the mbed libraries are great for more easy-to-understand examples but not as flexible and currently don't feel quite "production ready". It would also help with the great annoyance that occurs every time Nordic release a new version of the SDK and I have to figure out what changed compared to the previous one, rather than just being able to look at the commits.

Children
No Data
Related