UM1657 STMICROELECTRONICS | Alldatasheet
Document overview
- Manufacturer or author: Provided By ALLDATASHEET.COM(FREE DATASHEET DOWNLOAD SITE)
- PDF pages: 48
Technical content
Datasheet sections
- 1 Hardware description
- 1.1 STEVAL-IKR002Vx
- 1.1.1 STEVAL-IKR002Vx (RF motherboard)
- 1.1.2 Microcontroller and connections
- 1.1.3 Power
- 1.1.4 Sensors
- 1.1.5 Extension connector
- 1.1.6 Daughter board test point
- 1.1.7 Push buttons and joystick
- 1.1.8 JTAG connector
- 1.1.9 LEDs
- 1.2 STEVAL-IKR002Vx (RF module)
- 1.2.1 Boost mode
- 1.3 STEVAL-IKR001V7D (with SPIRI T1 RF module with external
- 1.4 STEVAL-IKR001V8D (with SPIRI T1 RF module with external
- 1.5 STEVAL-IDS001Vx (SPIRIT1 USB dongle)
- 1.5.1 Microcontroller and connections
- 1.5.2 Extension connector
- 1.5.3 SWD interface
- 1.5.4 Band
- 1.5.5 RF connector
- 1.5.6 Push buttons
- 1.5.7 LEDs
- 1.6 STEVAL-IKR001Vx
- 1.6.1 STEVAL-IKR001Vx (RF motherboard)
- 1.6.2 STEVAL-IKR001Vx (RF module)
- 2 Software installation
- 3 SPIRIT1 DK - GUI description
- 3.1 Firmware installation
- 3.2 Detailed description
The SPIRIT1 DK is a complete software package to support SPIRIT1 RF evaluation and development. It contains a SPIRIT1 DK GRAPHICAL USER INTERFACE (SPIRIT1 DK - GUI) which allows checking the SPIRIT1 main performance and easily measure parameters such as sensitivity, output power and main features of the SPIRIT1. It also contains SPIRIT1 firmware libraries for STM32L and STM8L to allow development of SPIRIT1 applications. In addition, it contains a Wireless M-BUS library with documentation and example applications to allow development of Wireless M-BUS application based on the SPIRIT1.
3.2.2 Supply voltage panel (supported only in STEVAL-IKR001Vx -
Hardware description UM1657
1 Hardware description
The software SPIRIT1 DK - GUI supports all the hardware available as demo kit. The hardware includes: STEVAL-IKR002Vx (with x = 1, 2, 3, 4, 5), STEVAL-IKR001V7D, STEVAL-IKR001V8D, STEVAL-IKR001Vx (with x = 1, 2, 3, 4, 5) and STEVAL-IDS001Vx
1.1 STEVAL-IKR002Vx
The SPIRIT1 DK is made up of two units connected to one PC or two PCs with USB cables. Each unit is composed of an antenna for the selected band and two PCBs: RF motherboard RF module
1.1.1 STEVAL-IKR002Vx (RF motherboard)
The RF motherboard has an STM32L microcontroller used for driving the SPIRIT1 transceiver and to communicate to a PC via USB. A connector on the motherboard (Figure 1) allows accessing the JTAG interface for programming and debugging. The board can be powered through a mini-USB connector that can also be used for I/O interaction with a USB Host. The board has also a user button, a joystick and RESET button for user interaction. Temperature sensor and accelerometer are included in the board. The RF module can be easily connected through a dedicated interface. This is the list of some of the features that are available on the boards: – STM32L151RBT6 64-pin microcontroller. – Mini USB connector for power supply and I/O. – JTAG connector. – RF daughterboard interface. – One RESET button a nd one USER button. – One LIS3DH accelerometer. – One STLM75 temperature sensor. – One joystick. –5 L E D s . –O n e P W R L E D . – One battery holder for 2 AAA batteries. – One row of test points on the interface with the RF daughterboard
Figure 1. STEVAL-IKR002Vx (RF motherboard)
1.1.2 Microcontroll er and connections
128 KB of flash memory, 16 KB of RAM, 32-bit core ARM cortex-M3, 4 KB of data
EEPROM, RTC, LCD, timers, USART, I²C, SPI, ADC, DAC and comparators. Table 1. MCU pin description versus board function
Table 1. MCU pin description versus board function (continued)
1.1.3 Power
- These lines are also available on the test point row.
Hardware description UM1657 battery holder in the rear of the board and the jumper JP1 must be set in position 2-3. When the board is powered, the green LED DL6 is ON, Figure 1 (C). If needed, the board can be powered by an external DC power supply. Connect the positive output of the power supply to the central pin of JP1 (pin 2) and the ground to one of the four test point connectors on the motherboard.
1.1.4 Sensors
Two sensors are available on the motherboard: – LIS3DH, an ultra-low power high performance three axes linear accelerometer (D in Figure 1). The sensor is connected to the STM32L through the SPI interface. Two lines for interrupts are also connected. – STLM75, a high precision digital CMOS temperature sensor, with I²C interface (E in Figure 1). The pin for the alarm function is connected to one of the STM32L GPIOs.
1.1.5 Extension connector
There is the possibility to solder a connector on the motherboard to extend its functionality (F in Figure 1). 16 pins of the microcontroller are connected to this expansion slot (Table 1).
1.1.6 Daughter board test point
In M Figure 1, a row of test point is available to the user for debugging and testing. The list of signals available is: 1. GND 2. VDD 3. GPIO SDN (the pin to drive in SHUTDOWN the SPIRIT1) 4. SPI CSn 5. SPI MISO 6. SPI MOSI 7. SPI SCKL 8. SPIRIT1 GPIO2 9. SPIRIT1 GPIO3 10. SPIRIT1 GPIO1 11. SPIRIT1 GPIO0 12. GND.
1.1.7 Push buttons and joystick
For user interaction the board has two buttons and a joystick. One is to reset the microcontroller; the other one is available to the application. There is also a digital joystick with 4 possible positions (left, right, up, down) (G in Figure 1).
1.1.8 JTAG connector
A JTAG connector on the board (H in Figure 1) allows programming and debugging of the STM32L microcontroller on board, using an in-circuit debugger and programmer like the ST- LINK/V2.
UM1657 Hardware description
1.1.9 LEDs
Five LEDs are available (I in Figure 1). – DL1: green. – DL2: orange. – DL3: red. – DL4: blue – DL5: yellow.
1.2 STEVAL-IKR002Vx (RF module)
The RF module includes 5 different possible BOM lists, on the same layout PCB. Each one optimized for different RF band as follow: 169 MHz 315 MHz 433 MHz 868 MHz 915 MHz The band indication is reported with a dummy resistor on the board, in A Figure 2. A SMA connector on the RF module, in B Figure 2, allows connection with RF instruments as spectrum analyzer and signal generator to the SPIRIT1 by RF cable or also connect an antenna as the one included in the demo kit. The board is powered through the RF daughterboard connector, in D Figure 2, by the RF motherboard and communicates through this connector by SPI and some GPIOs with the microcontroller. The VCC_RF pin of the RF daughterboard connector is linked to the Vbat of the SPIRIT1 through a jumper that can be also removed to measure the current consumption, in C Figure 2 The RF module includes a memory EEPROM in which some information on the RF module at manufactory time are stored. The information is stored in the first pages of the EEPROM. The memory is not intended to be changed by user.
Figure 2. STEVAL-IKR002Vx (RF module)
1.2.1 Boost mode
The SPIRIT1 can be configured to increase the output power in transmission mode. connector via the reference design.
Figure 3. STEVAL-IKR002Vx (RF module) boost mode configuration power, available on the SPIRIT1 web site or in the document folder of this release.
1.3 STEVAL-IKR001V7D (with SPIR IT1 RF module with external
at manufactory time are stored. The information is stored in the first pages of the EEPROM. The memory is not intended to be changed by user. Figure 4. STEVAL-IKR001V7D (RF module)
1.4 STEVAL-IKR001V8D (with SPIR IT1 RF module with external
at manufactory time are stored. The information is stored in the first pages of the EEPROM. The memory is not intended to be changed by user. Figure 5. STEVAL-IKR001V8D (RF module)
1.5 STEVAL-IDS001Vx (S PIRIT1 USB dongle)
with a USB Host. The board has also two user buttons for user interaction, in G Figure 6. SPIRIT1 radio transceiver, in D Figure 6. STM32L151CBU6 48-pin microcontroller, in C Figure 6. USB connector for power supply and I/O, in A Figure 6. One row of pins with SWD interface and SPIRIT1's GPIOs, in B Figure 6. Two user buttons, in G Figure 6. Figure 6. STEVAL-IDS001Vx
1.5.1 Microcontroll er and connections
EEPROM, RTC, timers, USART, I²C, SPI, ADC, DAC and comparators.
Table 2. MCU pin description versus board function LEDs SPIRIT1 Buttons USB SWD Ext.
1.5.2 Extension connector
1.5.3 SWD interface
connect the ST-LINK/V2 with the board pins is showed. LEDs SPIRIT1 Buttons USB SWD Ext. Table 2. MCU pin description versus board function (continued)
Figure 7. SWD connection scheme with ST-LINK/V2 Table 3. SWD connection
1.5.4 Band
The chip antenna used supports all these four bands of frequency.
1.5.5 RF connector
Figure 8. RF connector scheme
1.5.6 Push buttons
UM1657 Hardware description
1.5.7 LEDs
Two LEDs are available (H in Figure 6). – D1: yellow. – D2: green.
1.6 STEVAL-IKR001Vx
The SPIRIT1 DK is made up of two units connected to one PC or two PCs with USB cables. Each unit is composed of an antenna for the selected band and two PCBs: RF motherboard RF module
1.6.1 STEVAL-IKR001Vx (RF motherboard)
The previous version of the motherboard is supported. The supply voltage is provided or by USB cable or by external power supply. The switch S1 turns on or off the SPIRIT1 DK - MB. Figure 9 highlights some features of the board as follow:
Hardware description UM1657 1. The power supply sources: USB connector and jack connector for external power supply. USB connector is used also for I/O with the microcontroller with a virtual COM port exposed to the PC. 2. Switch to turn ON or OFF the board. 3. JTAG/SWD connector. 4. Three button and a joystick: a) SCM_PS, not used b) RESET, for resetting the MB board c) Push_Button, used to enter in DFU mode d) Joystick, not used. 5. Test point (TP), to probe the SPI signals, the 4 GPIOs of the SPIRIT1, the shutdown of the SPIRIT1 (SDN), the supply voltage of the SPIRIT1 (VCCRF). The list of signals available is: a) GND b) VCC_RF c) GPIO SDN (the pin to dr ive in SHUTDOWN the SPIRIT1) d) SPI CSn e) SPI MISO f) SPI MOSI g) SPI SCKL h) SPIRIT1 GPIO2 i) SPIRIT1 GPIO3 j) SPIRIT1 GPIO1 k) SPIRIT1 GPIO0 l) GND 6. Five LEDs 7. SMA connector
Figure 9. STEVAL-IKR001Vx
1.6.2 STEVAL-IKR001Vx (RF module)
The band indication is reported with a dummy resistor on the board, in A Figure 10. through this connector by SPI and some GPIOs with the microcontroller.
Figure 10. STEVAL-IKR001Vx (RF module)
2 Software installation
necessary files in the user PC. Figure 11. SPIRIT DK - GUI installation window
Figure 12. SPIRIT DK - driver installation window the user is required to select the proper driver. At the end of installation the user can run the SPIRIT1 DK - GUI.
3 SPIRIT1 DK - GUI description
This section describes how to use the Spirit1 DK-GUI.
3.1 Firmware installation
3.2 Detailed description
typical connections with one or two. Figure 13. CONNECTION SETUP 1 - 1 PC WITH 2 SPIRIT DK - GUI Figure 14. CONNECTION SETUP 2 - 2 PC WITH 1 SPIRIT DK - GUI EACH device, and change dynamically this selection before running a test.
Figure 15. Spirit1 DK GUI Main Window
3.2.1 Connection panel
GUI. Click to open the COM list makes also a refresh of the COM port available. Figure 16. Serial port selection
3.2.2 Supply voltage panel (suppor ted only in STEVAL-IKR001Vx - RF
DB. This voltage can be also read by the pin VCCRF on the SPIRIT1 DK - MB. Figure 17. Supply voltage display This function is available only for STEVAL-IKR001Vx - RF motherboard.
3.2.3 Radio setting panel
Data rate in the interval: [99 - 500000] bps. Frequency deviation in the interval: [793 - 761718] Hz. Channel filter in the interval: [1100 - 800100] Hz.
correct XTAL frequency value. then read and dis-played for the user. Figure 18. Radio setting panel
3.2.4 RF test mode
Figure 19. RF test mode buttons Both tests require only one device connected to PC.
3.2.5 TX CW test
- Select the desired radio settings and load it by pressing the "Configure radio" button
- Pressing the "TX CW START" button.
frequency and with the selected output power. The SPIRIT1 DK - DB stays in TX state until the "TX CW STOP" button is pressed.
3.2.6 TX PN9 test
- Select the desired radio setting and th en pressed the "Configure radio" button
- Pressing the "TX PN9 START" button.
The SPIRIT1 DK - DB stays in state TX until the "TX PN9 STOP" button is pressed. frequency or output power or modulation scheme during step 1.
3.2.7 Packet setting
Each packet format gives different packet setting options. Figure 20. Packet setting panel (Basic packet view)
SPIRIT1 DK - GUI description UM1657
3.2.8 Packet setting - BASIC
As shown in Figure 21, selecting BASIC (default configuration), SPIRIT1 DK - DB uses the packet format BASIC described in the datasheet. The options for the packet are: Preamble length Sync length Sync value CRC FEC Data whitening These entire fields can be changed according to these limits: Preamble length in the interval: [1 - 32] bytes. Sync length in the interval: [1 - 4] bytes. CRC: – NO CRC. – Poly 0x07 (1 byte). – Poly 0x8005 (2 bytes). – Poly 0x1021 (2 bytes). – Poly 0x864CFE (3 bytes). The "FEC" and the "Data whitening" can be checked or not according to the desired setting. In particular, if the "FEC" is checked, this feature is used during the transmission; the same apply for "Data whitening".
3.2.9 Packet setting - WMBUS
As shown in Figure 22, selecting MBUS, SPIRIT1 DK - DB uses the packet format MBUS described in the datasheet. The options for the packet are: MBUS submode. Preamble length. Postamble length. FEC. Data whitening. These entire fields can be changed according to these limits: Preamble length in the interval: [0 - 255] chip sequence (01). Postamble length in the interval: [0 - 255] chip sequence (01). MBUS submode: – S1, S2, long header. – S1m, S2, T2 other to meter. – T1, T2, meter to other. – R2 short header. –N 1 a - f , N 2 a - f The "FEC" and the "Data whitening" can be checked or not according to the desired setting. In particular, if the "FEC" is checked, this feature is used during the transmission; the same apply for "Data whitening".
length field and the CRC field for each data blocks. Figure 21. Packet setting panel (MBUS Packet view)
3.3 Transmission test
Figure 22. Transmission test panel
SPIRIT1 DK - GUI description UM1657 On the left corner it is possible to set the device main role during the transmission: RX and TX, in "Device role" panel. The panel "Data to send" has the value expressed in hexadecimal or in characters that a transmitter sends. The max length of this field is 255 bytes (GUI arbitrary limitation, not device limitation), and represents the effective payload sent. If the HEX check box is checked, the value must be added in this way: 07 08 09 0A and so on, if the ASCII check box is checked, characters are accepted. There is also the possible to generate a random set of values checking RAND and write how many bytes send in Payload length box. In "RX timeout" box the RX timeout in milliseconds should be set: this value has to be set large enough to receive completely the SYNC word and have to be set according to the data rate, the preamble length and the sync length. The GUI computes automatically a value, but it can be changed. This period is necessary only during the RX state to allow the SPIRIT1 find correctly a SYNC word. If the value is 0, then the RX timeout is infinite and the SPIRIT1 stays in RX state until it found a correct SYNC word. The SPIRIT1 has two mode of packet length: fix mode length and variable mode length. The former is used in this GUI and needs the receiver to know the length of the expected packet, in the latter instead the receiver find out the length of the packet from the packet itself, because the transmitter has filled a field of the frame with this information. The data received can be displayed in HEX or in ASCII. The panel "test indicator" shows all the results about the transmission/reception operations: the number of packet received correctly; the packet lost (also the packet lost for RX timeout that means the SPIRIT1 does not receive a packet within the RX timeout period; the RSSI value of the last packet; the PER from the start of the communication up to now. Just below the panel "Device role", there are two controls: "Total packets" and "Packet rate". The former set how many packets the transmitter will send or how many packets are expected by the receiver, an infinite number of packets can be send if the value is 0; the latter set the period of time in which a packet is sent. The test implemented in the firmware of the GUI defines a cycle in which the SPIRIT1 configured as transmitter send a packet (the duration of this operation depends by the data rate and the approximate value is reported in the packet duration box) then the SPIRIT1 goes in the low power consumption state named STANDBY until the period set in the packet rate box expires; then cycle is repeated. From the receiver side, the test work slightly the same: the SPIRIT1 goes in RX state a couple of milliseconds before the transmitter goes in TX state, then wait for the SYNC of the packet for the time write in RX timeout box, then if the packet is received or the rx timeout expires the SPIRIT1 goes in a low power consumption state (STANDBY) until the period set in the packet rate box expires. Also, during first communication the SPIRIT1 goes automatically in RX state waiting for the first packet (synchronization packet) with infinite RX timeout. It is really important to set the value of the packet rate greater than the value indicated in "packet duration [ms]" field. Otherwise, to the received packet can be truncated. Also the packet rate must be the same for both devices. The "START" button makes the test run. Once the test is started, the "START" button label is changed in "STOP" button. If this button is pressed while the test runs, the test is stopped. In the bottom of the Transmission test panel, there is a box in which it is possible to write the name of a file in which the GUI will save a log of the current test. This operation is made during the test, so it is important to write the filename before the test starts.
RF noise in the environment.
3.3.1 AES
supported by the SPIRIT1 hardware.
- Select "Encryption" in AES operation
- Type the clear text composed of 128 bits (i.e. 32 hex chars) in the Data input field
- Type the encryption key composed of 128 bits (i.e. 32 hex chars) in the Key field
- Push "START AES OPERATION" button
- The encrypted text is provided as 32 hex chars in Data output
Figure 23. AES Encryption operation
- Select "Derive decryption key" in AES operation
- Type the encryption key composed of 128 bits (i.e. 32 hex chars) in the Key field
- Push "START AES OPERATION" button
- The derived decryption text is provided as 32 hex chars in Data output
- Select "Decryption using a given decryption key" in AES operation
- Type the encrypted text composed of 128 bits (i.e. 32 hex chars) in the Data input field
- Type the decryption key composed of 128 bits (i.e. 32 hex chars) in the key field
- Push "START AES OPERATION" button
- The clear text is provided as 32 hex chars in Data output
- Select "Decryption from an encr yption key" in AES operation
- Type the encrypted text composed of 128 bits (i.e. 32 hex chars) in the Data input field
- Type the encryption key composed of 128 bits (i.e. 32 hex chars) in the key field
- Push "START AES OPERATION" button
- The clear text is provided as 32 hex chars in Data output
3.3.2 Low level commands
Figure 24. Low level commands panel
UM1657 SPIRIT1 DK - GUI description Five panels are available: Read registers. Write registers. Save register values. SPIRIT1 information. VCC_RF regulator. To read the registers of the SPIRIT1 is necessary to write the address of the first register from which starts the read operation. Then, it is necessary to write the number of registers to read starting from that address. To write a register of the SPIRIT1 is necessary to write the address of the register to modify and the new value of the register. All the registers of the SPIRIT1 can be read and saved in a text file by clicking the Save button of the "Save register value" panel. The SPIRIT1 status can be read by pressing the "SPIRIT1 state" button. Also the version of the SPIRIT1 can be read. Only for STEVAL-IKR001Vx - RF motherboard, the VCC_RF supply voltage for the SPIRIT1 can be changed be-tween 1.8 and 3.6 V. Only for STEVAL-IKR002Vx - RF module and STEVAL-IKR001V8D, the offset of frequency measured during production can be readout by the button Freq. offset. The three buttons allow setting some particular test modes: RX Data on GPIO Send Data from GPIO RX Data on GPIO No Packet The RX Data on GPIO configures the GPIO_0 and the GPIO_1 of the SPIRIT1 to send respectively the RX data received and the clock signal. In this way, when the SPIRIT1 goes in RX state it is possible to see the packet received. The Send Data from GPIO configures the GPIO_0 and the GPIO_1 of the SPIRIT1 to send respectively the data to transmit and the clock to sample the data. In this way, when the SPIRIT1 goes in TX state it is possible to send data loaded through the GPIO (and not through the FIFO as usual). The RX Data on GPIO No Packet is equals to the RX Data on GPIO with the only difference that the packet handler embedded in the SPIRIT1 is by-passed.
3.3.3 How run a BER test using signal generator
Through the low level commands tab is possible to put the SPIRIT1 in RX direct more through GPIOs. In this mode, the packet handler is totally bypassed and the demodulated data plus associated clock signal is available on two GPIOs. This mode can be enabled by the button "RX Data on GPIO No Packet". The two signals then can be used as in Figure LL in a signal generator with BER option to allow measuring the Bit Error Rate according to that particular radio configuration. The data must be sampled on falling edge of clock signal.
Figure 25. BER test using SPIRIT1 DK - GUI
3.4 Tools
Figure 26. Tools list and also to load and save radio configurations.
3.4.1 Firmware version
The firmware version format is x.y.z with option "BETA" to identify beta release.
3.4.2 Firmware upgrade
- Activate the DFU software manually, by pr essing and releasing "RESET" button while
flashing to confirm that DFU boot loader is running.
- Launch the SPIRIT1 DK GUI and from Tools->Firmware Upgrade select the firmware
- After clicking OK the firmwar e will be programmed into the board.
The firmware images present in the folder are described in Table 4.
3.4.3 Save and load configurations
file, in order to make easy to restore it at later time. The Load option allows loading the stored radio and packet configurations from a file. Path>\\Spirit_GUI_Configuration. Table 4. SPIRIT DK firmware images SPIRIT1-wmbus-meter-169.hex SPIRIT1 WM-BUS meter demo 169 MHz firmware image. SPIRIT1-wmbus-meter-868.hex SPIRIT1 WM-BUS meter demo 868 MHz firmware image. DFU boot loader has been deleted by mistake.
3.4.4 Help
Figure 27. Help with user manual Opening the Help list a link to the user manual is available.
UM1657 SPIRIT1 WM-BUS GUI description
4 SPIRIT1 WM-BUS GUI description
This section describes how to use the Spirit1 Wireless M-BUS-GUI.
4.1 Firmware installation
The boards come preprogrammed with firmware suitable to run Spirit1 DK-GUI, in order to operate the WM-BUS GUI, it is necessary to reprogram the appropriate firmware. In order to program the correct firmware, you need to know in which band you would like to operate. The bands supported are 169 MHz and 868 MHz. Based on your choice, please follow the instructions in section 4.2.9.2 and load the firmware image …\\Firmware\\Binary\\SPIRIT1- wmbus-gui-<band>.hex in the board to be used in conjunction with the GUI (concentrator) and load the firmware image …\\Firmware\\Bin ary\\SPIRIT1-wmbus-meter-<band>.hex in the board to be used as a meter.
4.2 Detailed description
The SPIRIT1 Wireless M-BUS - GUI requires only the concentrator to be connected with the PC, the meter is operated through joystick and buttons and it needs USB connection just for power. After the boards are prepared as described in section 5.1, the user can run the GUI. After running the GUI, the fol-lowing steps needs to be performed: 1. Connect the concentrator board to the PC. 2. Click the connect button, you should get the message "Connection Successful" (see Figure 30 and Figure 31) 3. Select the "Configuration" tab and click on receive all (see Figure 32) 4. Please check the parameters and in partic ular that "Device type" is concentrator and WM-Bus mode is S1m if you are using 868 MHz band or N1 if you are using 169 MHz band and that the "Device mode" is "Install mode". (see Figure 32) 5. Power the meter board and move the joystick down (or press the button SW1 for STEVAL-IDS001Vx). The yellow LED DL5 should be on in the concentrator board (or green LED D2 for STEVAL-IDS001Vx). 6. The meter should be now registered in the concentrator database 7. Go to the "Meters" tab and click Refresh 8. On the concentrator and meter, push the "Push_Button" button. Red LED DL3 should be now ON on both boards (press the button SW2 for STEVAL-IDS001Vx and the yellow LED D1 will turn ON). 9. Go to "Monitoring tab" and click "Auto Refresh" 10. On the meter, do the following: a) Push joystick up to increase the gas consumption. b) Push joystick right to send data to concentrator (press the button SW2 on STEVAL-IDS001Vx). 11. The data is automatically disp layed in the "Monitoring" tab
Figure 32. WM-BUS GUI step 9, 11
UM1657 SPIRIT1 driver and example programs
5 SPIRIT1 driver and example programs
The installed software package contains also support for SPIRIT1 firmware development. The directory tree includes: SPIRIT1 driver in source form for STM32L Example IAR projects for STM32L in: – ...\\Firmware\\SPIRIT1_Library_Projec t\\IAR\\Spirit_Library_Project.eww Associated documentation in: – ...\\Documents In order to use or modify the example project, it is required to have installed IAR Embedded Workbench for ARM v6.40 and a JTAG interface like: ST-LINK Or IAR JLink
SPIRIT1 wireless M-BUS library and example programs UM1657
6 SPIRIT1 wireless M-BUS library and example
The installed software package contains also support for SPIRIT1 Wireless M-BUS firmware development. The directory tree includes: SPIRIT1 Wireless M-BUS library driver in binary form for STM32L Example IAR projects for STM32L in: – ...\\Firmware\\WMBUS_Example\\IAR\\wmbus.eww Associated documentation in: – ...\\Documents In order to use or modify the example project, it is required to have installed IAR Embedded Workbench for ARM v6.40 and a JTAG interface like: ST-LINKv2 Or IAR JLink
7 Revision history
Table 5. Document revision history 28-Nov-2013 1 Initial release.