- Msp432p401r wire library serial#
- Msp432p401r wire library driver#
- Msp432p401r wire library portable#
- Msp432p401r wire library code#
- Msp432p401r wire library series#
For the GNU tools, separate header files are included in the inc directory of the root installation of DriverLib.
Msp432p401r wire library code#
Vector table definitions that are compatible with the GCC compiler are also provided for code examples in the startup_gcc.c file for each individual code example. While no IDE in specific is supported, Makefiles are provided for both the library and all of the code examples.
Msp432p401r wire library series#
The GNU compiler tools for ARM are fully supported by the MSP432 Series DriverLib. All of the include paths and compiler options are set up to allow the user to seamlessly start development on their MSP432 DriverLib application. A user can import this project in CCS using the TI Resource Explorer, or open the workspace with IAR Embedded Workbench for ARM or KEIL uVision 5. This project includes links to the DriverLib library as well as everything that is needed for the programmer to immediately start writing a DriverLib application. Getting started using DriverLib for MSP432 Series is very simple regardless of the chosen development environment.Īn empty "skeleton" project is provided in the examples directory of the MSPWare release. While each module will still have individual status (IFG), enable/disable, and clear bits, interrupt service routines now have to be associated with the ARM NVIC before usage. Interrupts, for example, are a bit difference on MSP432 compared to MSP430 due to integration with ARM's interrupt controller (the NVIC).
Msp432p401r wire library driver#
Note that while many Driver Library APIs are shared between MSP430 and MSP432, there are a few underlying differences between the two architectures. With a rich set of analog, timing, and communications peripherals, they cater to a large number of application scenarios.
They feature an ARM Cortex-M4 processor in a wide configuration of device options.
Both sets of code set MCLK to be sourced from VLO with a divider of four: Texas Instruments MSP432 Microcontrollers are the latest addition of efficient ultra-low-power mixed-signal MCUs. For example, examine the following pair of code snippets. Writing code in DriverLib will make user code more legible and easier to share among a group.
Msp432p401r wire library portable#
By using the high level software APIs provided by DriverLib, users can create powerful and intuitive code which is highly portable between not only devices within the MSP432 platform, but between different families in the MSP430/MSP432 platforms. Nearly every aspect of a MSP432 device can be configured and driven using the DriverLib APIs. The DriverLib is meant to provide a "software" layer to the programmer in order to facilitate higher level of programming compared to direct register accesses. Texas Instruments Code Composer Studio 6.1 Below is a list that contains the supported toolchain and corresponding hardware debugger used. Subsequently, for each toolchain a specific debugger was used for testing validation.
Msp432p401r wire library serial#
In addition to being able to control the MSP432 peripherals, DriverLib also gives the user the ability to use common ARM peripherals such as the Interrupt (NVIC) and Memory Protection Unit (MPU) as well as MSP430 peripherals such as the eUSCI Serial peripherals and Watchdog Timer (WDT).ĭriverLib for MSP432 Series has been tested and compiled under a variety of different toolchains. PS.The Texas Instruments MSP432 Driver Library (DriverLib) is a set of fully functional APIs used to configure, control, and manipulate the hardware peripherals of the MSP432 platform. Thank you for your assistance in advance. (In arduino, it doesn't occur even when i2c device is disconnected - just the data is fixed to '0') (Edit * This I2C device is IMU Digital Combo Board - 6 Degrees of Freedom ITG3200/ADX元45 ) This appears to occur with and without the i2c device connected I had tried several solutions, such as reinstalling Energia, using most recent build of the MSP432's Wire.h library, and even using external pull-up as suggested in. *Hang means that it doesn't execute next operations, and stuck in the state until it is manually reset. While trying to connect a slave i2c device(IMU) to the board, I discovered that MSP432P401R hangs (specifically, goes to 'sleep mode'(according to CCS Cloud debugging) then 'idle mode' when Wire.endTransmission() is executed. I am a user who uses MSP432P401R, with Energia 0101E0017 (and TI CCS Cloud)