Electronic Components Datasheet Search
  English  ▼
ALLDATASHEET.NET

X  

OL2385SWUG Datasheet(PDF) 22 Page - NXP Semiconductors

Part # OL2385SWUG
Description  SIGFOX software driver
PDF  64 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  NXP [NXP Semiconductors]
Direct Link  http://www.nxp.com
Logo NXP - NXP Semiconductors

OL2385SWUG Datasheet(HTML) 22 Page - NXP Semiconductors

Back Button OL2385SWUG Datasheet HTML 18Page - NXP Semiconductors OL2385SWUG Datasheet HTML 19Page - NXP Semiconductors OL2385SWUG Datasheet HTML 20Page - NXP Semiconductors OL2385SWUG Datasheet HTML 21Page - NXP Semiconductors OL2385SWUG Datasheet HTML 22Page - NXP Semiconductors OL2385SWUG Datasheet HTML 23Page - NXP Semiconductors OL2385SWUG Datasheet HTML 24Page - NXP Semiconductors OL2385SWUG Datasheet HTML 25Page - NXP Semiconductors OL2385SWUG Datasheet HTML 26Page - NXP Semiconductors Next Button
Zoom Inzoom in Zoom Outzoom out
 22 / 64 page
background image
NXP Semiconductors
OL2385SWUG
SIGFOX software driver
OL2385SWUG
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2018. All rights reserved.
User guide
Rev. 2.1 — 6 April 2018
22 / 64
the board. There is no external MCU required, thereby saving the customer additional
cost. Because each application from customer to customer is different, this version
will be provided as a skeleton with a combined library (NXP radio plus SIGFOX stack).
The customer can modify the skeleton for customizing the behavior of the buttons
and LEDs. A basic version of the software exists and can be enabled by a macro
(BUTTON_PRESS_MODE) in project settings. The creation of a combined library
still has to be done, therefore it is not ready to be provided. Additionally, the program
memory does not have a lot of space and therefore, the application has to be very
small and simple.
• UART based firmware (under investigation): This version needs a UART interface
to the OL2385. This interface can also be to an external MCU or to a terminal program.
From a business point of view, it makes sense to not have an external MCU required,
thus saving the customer additional cost. A basic version of the software exists and
can be enabled by a macro in project settings (SIGFOX_UART_MODE). However, the
driver for UART is not robust and needs to be rewritten completely. The AT commands
need to be updated and bugs have to be fixed.
Note: A SIGFOX based module might go through a P1 certification process at
SIGFOX, depending on if there is a hardware change from an NXP reference design
or modification of certified NXP software. NXP has only standard product – SPI based
firmware certified at SIGFOX for all regions. Even if the radio parts of the software
remain unchanged, any small change in software will still be considered a change. And
therefore, if a customer decides to use Button press based or UART based firmware,
they will have to get their devices recertified. In order to do the certification, SIGFOX
will require activation of various test sequences on the OL2385 device. This will be
very difficult for Button press based firmware, because OL2385 has only three buttons.
Therefore, a SPI or UART based interface to OL2385, where we can control these test
sequences, is needed.
Similarly, a UART based firmware without an MCU is good for evaluation using a terminal
program. But for end product, customers will use either an MCU to connect to UART
interface or use buttons again to write application on the device. In case of using an
external MCU, it is highly recommended to use SPI based firmware, because it is
certified and readily available. In case of no MCU usage and using buttons as a final
interface to the user, UART will just be used as a certification interface. Again, in such
a scenario it is easier to use a SPI based interface for certification purposes, because
button applications will vary from customer to customer. It will again be our strategy to
provide the code to customers with a combined library.
Proposed solution: For the applications where buttons are the interface to users and
an interface is required only for evaluation and certification, it makes sense to provide
the code to customers with a combined library and skeleton source files. A macro can be
used by customers to enable/disable the SPI interface, which then will be used for one
time certification. This means that customers do not have to use the MCU permanently
on all products, but only externally to get certification. Therefore, there is no need for
UART based firmware. Also, UART would have required an additional FTDI cable to
interface OL2385 for certification. Now, it will just be an MCU based device controlling
OL2385 externally for certification.
6.2 Kinetis MCU based application
This chapter is relevant for writing the code for an application on Kinetis MCUs. If your
KL43Z is preflashed, you can skip to Section 7.1 "Testing on SIGFOX Base Station".



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64


Datasheet Download

Go To PDF Page


Link URL



Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link to Datasheet    |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com