You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3
+
4
+
# MPLAB® Harmony 3 MiWi
5
+
6
+
MPLAB® Harmony 3 is an extension of the MPLAB® ecosystem for creating embedded firmware solutions for Microchip 32-bit SAM and PIC® microcontroller and microprocessor devices. Refer to the following links for more information.
This repository contains the MPLAB® Harmony 3 MiWi for PIC32CX-BZ2 platform devices.
15
+
The MiWi protocol stack supports MiWi's own proprietary application(MiApp) & mac layer(MiMAC) and IEEE 802.15.4 Standalone PHY Layer of devices like WBZ451, RF233 and RF212B.
16
+
Refer to the following links for release notes, training materials, and interface reference information.
17
+
18
+
As a first step, the [MiWi](https://github.com/MicrochipTech/MiWi) repo must be cloned to the User's Local Harmony repo folder location and follow the steps mentioned in the follwoing [link](https://github.com/MicrochipTech/MiWi/blob/main/docs/GUID-32628D58-8B41-490F-8DA4-520C34856980.md) to generate the harmony project application.
19
+
User must have atleast a Standalone PHY component that supports [WBZ451](https://github.com/Microchip-MPLAB-Harmony/wireless_15_4_phy) or Standalone Transceivers like [RF233](https://github.com/MicrochipTech/wireless_15_4_phy_trx) / [RF212B](https://github.com/MicrochipTech/wireless_15_4_phy_trx).
[](https://www.youtube.com/user/MicrochipTechnology)
45
+
[](https://www.linkedin.com/company/microchip-technology)
46
+
[](https://www.facebook.com/microchiptechnology/)
47
+
[](https://twitter.com/MicrochipTech)
The MiWi Development Environment \(MiWi DE\) was developed by Microchip to<br /> support a wide range of wireless applications. The backbone of MiWi DE is MiMAC and<br /> MiApp interfaces, which links the support of multiple RF transceivers and wireless<br /> communication protocols together as a well-defined, simple but robust Microchip<br /> proprietary wireless development environment.
4
+
5
+
Within MiWi DE, application developers can switch between RF transceivers and<br /> wireless protocols with little or no modification in the application layer. Such<br /> migration capability in MiWi DE reduces the firmware development risk to a very minimum<br /> level. MiWi DE is defined by three layers:
6
+
7
+
- Application layer
8
+
- Protocol layer
9
+
- RF transceiver layer
10
+
11
+
The three layers are linked together by MiMAC and MiApp interfaces. The<br /> Application layer uses MiApp interfaces to communicate to the protocol layer. In the<br /> protocol layer, there are implementations of MiWi P2P, MiWi Star, and MiWi Mesh wireless<br /> communication protocols. The drivers for Microchip RF transceivers \(AT86RF233,<br /> AT86RF212B\) are called by protocol layers via MiMAC interfaces. Configuration files are<br /> also presented in each layer.
The MiWi stack offers a significantly smaller footprint relative to the open<br /> standard based ZigBee® compliant protocol stack. This enables operation in<br /> microcontrollers with smaller memory/lower cost.
16
+
17
+
- MiWi P2P/Star – Simple Peer-to-Peer or Star network requiring minimal code size.
18
+
- MiWi Mesh – A True Routing Mesh network topology. This can be used for a department store HVAC, alarm application or a large smart home application.
|Description|This is the primary user interface function for the application layer to start communication with an existing PAN. For P2P protocol, this function call can establish one or more connections. For network protocol, this function can be used to join the network, or establish a virtual socket connection with a node out of the radio range.|
5
+
|Pre-Condition|Protocol initialization is done. If only to establish connection with a predefined device, an active scan must be performed before and valid active scan result must be saved.|
6
+
|Parameters|• uint8\_t channel – selected channel to invoke join procedure.• uint8\_t addr\_len – address length• uint8\_t \*addr – address of the parent• uint8\_t Capability\_info – capability information of the device• connectionConf\_callback\_t ConfCallback – callback routine which will be called upon the initiated connection procedure is performed|
7
+
|Returns|The index of the peer device on the connection table.|
8
+
|Example|<code\>// Establish one or more connections with any devicePeerIndex = MiApp\_EstablishConnection\(14, 8, 0x12345678901234567,0x80,callback\);</code\>|
9
+
|Remarks|If more than one connections is established through this function call, the return value points to the index of one of the peer devices.|
10
+
11
+
**Parent topic:**[MiApp API Description](GUID-A47B6424-A497-498C-8B1E-044F12F201A6.md)
Information contained in this publication is provided for the sole<br /> purpose of designing with and using Microchip products.<br /> Information regarding device applications and the like is<br /> provided only for your convenience and may be superseded by<br /> updates. It is your responsibility to ensure that your<br /> application meets with your specifications.
4
+
5
+
THIS INFORMATION IS PROVIDED BY MICROCHIP “AS IS�. MICROCHIP MAKES NO<br /> REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR<br /> IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE<br /> INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES<br /> OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A<br /> PARTICULAR PURPOSE OR WARRANTIES RELATED TO ITS CONDITION,<br /> QUALITY, OR PERFORMANCE.
6
+
7
+
IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE,<br /> INCIDENTAL OR CONSEQUENTIAL LOSS, DAMAGE, COST OR EXPENSE OF ANY<br /> KIND WHATSOEVER RELATED TO THE INFORMATION OR ITS USE, HOWEVER<br /> CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR<br /> THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY<br /> LAW, MICROCHIP'S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY<br /> RELATED TO THE INFORMATION OR ITS USE WILL NOT EXCEED THE AMOUNT<br /> OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR<br /> THE INFORMATION. Use of Microchip devices in life support and/or<br /> safety applications is entirely at the buyer’s risk, and the<br /> buyer agrees to defend, indemnify and hold harmless Microchip<br /> from any and all damages, claims, suits, or expenses resulting<br /> from such use. No licenses are conveyed, implicitly or<br /> otherwise, under any Microchip intellectual property rights<br /> unless otherwise stated.
0 commit comments