• State Not Answered
  • Replies 1 reply
  • Subscribers 88 subscribers
  • Views 438 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 282447
Options

use of OSS

yk112

Hello,

I use nRF52810 in commercial product. I modify examples (ble_app_hids_keyborard_pca10040e_s112 and ble_app_uart_pca10040e_s112) a bit. If softdevice S112 or the examples use open source softwares like linux, I think I have to write about license information (GPL、BSD、etc) to our product's document. Do S112 and the examples include open source softwares?

Parents
  • 0

    Hi,

    Both open source and proprietary licences may or may not include clauses requiring inclusion of licence information with distributions.

    The SoftDevice is proprietary software developed by Nordic Semiconductor. You find the licence in the <SDK root folder>/components/softdevice/s112/doc/ folder. No attribution or redistribution of the SoftDevice licence is needed for use on Nordic Semiconductor ICs and/or distributed through use of such devices.

    The nRF5 SDK comes with licence texts for the licences used. An overview is found in the file <SDK root folder>/license.txt.

    Most of the SDK is covered by our proprietary licence (<SDK root folder>/documentation/nRF5_Nordic_license.txt.) It is similar to that of the SoftDevice. For most practical situations there is no need of attribution or to distribute the licence with the product.

    Various files under <SDK root folder>/components/toolchain, which comes from e.g. ARM, use other licenses (such as ARM 3-clause, Apache 2.0, etc.) Source files are equipped with license texts at the beginning of the files, stating which license covers the source file. Some of those files are included in your project, so you should read their associated licences and act accordingly.

    Various files under <SDK root folder>/external come from third party sources, each with their own licenses. The subfolders contain license texts and/or information about the licenses used. Some of the example projects in the SDK may use one or more of those third party libraries. The applicable licenses therefore depend on which example is used, and what functionality has been added to or removed from that example.

    Regards,
    Terje

Reply
  • 0

    Hi,

    Both open source and proprietary licences may or may not include clauses requiring inclusion of licence information with distributions.

    The SoftDevice is proprietary software developed by Nordic Semiconductor. You find the licence in the <SDK root folder>/components/softdevice/s112/doc/ folder. No attribution or redistribution of the SoftDevice licence is needed for use on Nordic Semiconductor ICs and/or distributed through use of such devices.

    The nRF5 SDK comes with licence texts for the licences used. An overview is found in the file <SDK root folder>/license.txt.

    Most of the SDK is covered by our proprietary licence (<SDK root folder>/documentation/nRF5_Nordic_license.txt.) It is similar to that of the SoftDevice. For most practical situations there is no need of attribution or to distribute the licence with the product.

    Various files under <SDK root folder>/components/toolchain, which comes from e.g. ARM, use other licenses (such as ARM 3-clause, Apache 2.0, etc.) Source files are equipped with license texts at the beginning of the files, stating which license covers the source file. Some of those files are included in your project, so you should read their associated licences and act accordingly.

    Various files under <SDK root folder>/external come from third party sources, each with their own licenses. The subfolders contain license texts and/or information about the licenses used. Some of the example projects in the SDK may use one or more of those third party libraries. The applicable licenses therefore depend on which example is used, and what functionality has been added to or removed from that example.

    Regards,
    Terje

Children
No Data
Related