Chandler Blvd. As used in this Agreement, the following capitalized terms will have the meanings defined below:. Software License Grant. Microchip grants strictly to Licensee a non-exclusive, non-transferable, worldwide license:.
If source code is provided by Microchip to Licensee, to modify the Software for the sole purpose of rendering the Software operable with Licensee Products or Third Party Products, provided that Licensee clearly notifies Third Parties regarding the source of such modifications; and. To distribute the Software to Third Parties for use with or incorporation into Licensee Products or Third Party Products, provided that Licensee ensures that: i such Third Party agrees to be bound by this Agreement in writing or by "click to accept" , and ii this Agreement accompanies such distribution.
The procedure described in sub-clauses i and ii is not required when the Software is embedded in machine-readable object code form as firmware in Licensee Products or Third Party Products.
Further, the procedure described in sub-clauses i and ii is not required when modified versions of PC programs are re-distributed in machine-readable object code form, provided that Licensee notifies end users that: 1 the modified PC program is derived from a Microchip PC program and is governed by the terms of this Agreement including the requirement to use such program with Microchip Products, 2 a copy of this Agreement is available upon request, and 3 the Licensee supports the modified PC program.
Documentation License Grant. Microchip grants to Licensee a non-exclusive, non-transferable, worldwide license to use the Documentation in support of the authorized use of the Software as set forth in this Agreement. Third Party Requirements. This includes, by way of example but not as a limitation, any standards setting organizations requirements and, particularly with respect to Security Package Software, if any, local encryption laws and requirements.
Open Source Components. Notwithstanding the license grant in Section 2 above, Licensee further acknowledges that certain components of the Software may be covered by so-called "open source" software licenses "Open Source Components".
Open Source Components means any software licenses approved as open source licenses by the Open Source Initiative or any substantially similar licenses, including without limitation any license that, as a condition of distribution of the software licensed under such license, requires that the distributor make the software available in source code format. To the extent required by the licenses covering Open Source Components, the terms of such license will apply in lieu of the terms of this Agreement.
To the extent the terms of the licenses applicable to Open Source Components prohibit any of the restrictions in this Agreement with respect to such Open Source Components, such restrictions will not apply to such Open Source Component. Licensee Obligations. Licensee will not: a engage in unauthorized use, modification, disclosure or distribution of Software or Documentation, or its modifications or derivatives; b use all or any portion of the Software, Documentation, or its modifications or derivatives except in conjunction with Microchip Products, Licensee Products, or Third Party Products as set forth in this Agreement; or c reverse engineer by disassembly, decompilation or otherwise Software or any portion thereof.
Licensee may not remove or alter any Microchip copyright or other proprietary rights notice posted in any portion of the Software or Documentation. Licensee will defend, indemnify and hold Microchip and its subsidiaries harmless from and against any and all claims, costs, damages, expenses including reasonable attorney's fees , liabilities, and losses, including without limitation: x any claims directly or indirectly arising from or related to the use, modification, disclosure or distribution of the Software, Documentation, or any intellectual property rights related thereto; y the use, sale and distribution of Licensee Products or Third Party Products; and z breach of this Agreement.
Licensee agrees that the Software including but not limited to the source code, object code and library files and its modifications or derivatives, Documentation and underlying inventions, algorithms, know-how and ideas relating to the Software and the Documentation are proprietary information belonging to Microchip and its licensors "Proprietary Information". Except as expressly and unambiguously allowed herein, Licensee will hold in confidence and not use or disclose any Proprietary Information and will similarly bind its employees and Third Party ies in writing.
Proprietary Information will not include information that: i is in or enters the public domain without breach of this Agreement and through no fault of the receiving party; ii the receiving party was legally in possession of prior to receiving it; iii the receiving party can demonstrate was developed by the receiving party independently and without use of or reference to the disclosing party's Proprietary Information; or iv the receiving party receives from a third party without restriction on disclosure.
If Licensee is required to disclose Proprietary Information by law, court order, or government agency, License will give Microchip prompt notice of such requirement in order to allow Microchip to object or limit such disclosure. Licensee agrees that the provisions of this Agreement regarding unauthorized use and nondisclosure of the Software, Documentation and related Proprietary Rights are necessary to protect the legitimate business interests of Microchip and its licensors and that monetary damage alone cannot adequately compensate Microchip or its licensors if such provisions are violated.
Licensee, therefore, agrees that if Microchip alleges that Licensee or Third Party has breached or violated such provision then Microchip will have the right to injunctive relief, without the requirement for the posting of a bond, in addition to all other remedies at law or in equity.
OTG allows devices to also act as a host. This code is called the USB stack, and we will use this as the main library for communicating to PCs. The name of the root directory should be something like "Microchip Solutions v We will not be using any of those files for our purposes. Two additional header files and two additional source files specific to each application are required for the microcontroller to be fully USB functional. The file attached below is a zip containing examples of these four files.
For the pic32mx2xx series, the usb interrupts are not configured correctly in the Microchip stack, so the following changes need to be made. We've added a precompiler if statement to detect if a specific chip is being used. It's simple to change this for your specific chip though. It is important to use an external clock or oscillator in order to use the USB module.
A 48 MHz clock is required for proper operation. This timing can be faster than the minimum with no hitch, but slower causes failure in communication. This demo communicated with the processing demo explained below, using the DIP package for the pic32 and the following pinout. Documentation and downloads for this library can be found here. This is the Processing sketch used to interface with the demo board described above.
The code directory contains both the.
0コメント