Jump to content

Search the Community

Showing results for tags 'DriverLib'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • Announcements
    • Suggestions
    • New users say Hi!
  • Spotlight!
    • Sponsor Spotlight
    • Sponsor Giveaways
  • Energia
    • Energia - MSP
    • Energia - TivaC/CC3XXX
    • Energia - C2000
    • Energia Libraries
  • MSP Technical Forums
    • General
    • Compilers and IDEs
    • Development Kits
    • Programmers and Debuggers
    • Code vault
    • Projects
    • Booster Packs
    • Energia
  • Tiva-C, Hercules, CCXXXX ARM Technical Forums
    • General
    • SensorTag
    • Tiva-C, Hercules, CC3XXX Launchpad Booster Packs
    • Code Vault
    • Projects
    • Compilers and IDEs
    • Development Kits and Custom Boards
  • Beagle ARM Cortex A8 Technical Forums
    • General
    • Code Snippets and Scripts
    • Cases, Capes and Plugin Boards
    • Projects
  • General Electronics Forum
    • General Electronics
    • Other Microcontrollers
  • Connect
    • Embedded Systems/Test Equipment Deals
    • Buy, Trade and Sell
    • The 43oh Store
    • Community Projects
    • Fireside Chat
  • C2000 Technical Forums
    • General
    • Development Kits
    • Code Vault
    • Projects
    • BoosterPacks


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL





Found 9 results

  1. Hi, These after read this thread about how to use temperature calibration data, I tried to use TLV register to obtain the "real" voltage reference value and increase the ADC conversion by compensating the gain and offset. The test was performed in a Launchpad EXP430FR6989, but can be applied to other launchpads compatible with MSP430Ware driverlib. The increase in the accuracy is very interesting. in the table (sorry by the comma instead of point, brazilian notation). HP 3478A - value measured with DMM ADC_correct1 - value measured with MSP430 without any correc
  2. win10 - ccsv7 - energia 18 - msp432 launchpad I'm trying to use the crc32 library from driverlib to do a simple crc-16-ccitt calculation and stumbled across a weird problem. Just to give a quick background, the way the crc32 library works is the following: 1) initialize 2) add N bytes to be processed 3) request the computation to be done In order to get the routine to work correctly, I must slow down the code with some additional code in between steps 2 and 3. This can be operations, Serial.print, or even just a simple 1 us delay. If I do not do this, the answer I g
  3. Energia and Arduino users eventually get to the point where they need more direct access to the hardware if they take on more complicated projects. In addition to the direct access of registers using the provided header files, TI offers DriverLib which contains abstractions for accessing the peripherals. To better understand the peripherals, and to check out DriverLib, I recently created 20+ short examples for my own edification. All of them were written for the MSP430F5529 LaunchPad and most of the peripherals are covered. In some cases pushbuttons, LEDs, resistors, potentiometer, etc.
  4. For those who may not have seen it, the black LaunchPads with Rev B pre-release MCU are being phased out. New red LaunchPads with a revision C production device are replacing it. The announcement in e2e is located here. There is information on timing and compatibility with CCS located here. A quote from the second link: TI recommends that you update all hardware and software be updated to latest Revision C devices. Support for MSP432P401R on CCS cloud (dev.ti.com) and via MSP432Ware have been updated to match Revision C devices. Pre-production Revision C samples can be ordered online
  5. I am starting to use CCS and C more, Energia less. Currently I'm taking a TI workshop that tends to use driverlib rather than more more direct access to the registers. I notice that a lot (most I guess) code on 43oh accesses the registers directly. TI touts readability as the reason to use driverlib. It is bound to add some overhead. It is supposed to aid portability among TI products. I'm trying to develop good programming habits. How do others feel about using driverlib?
  6. Hello, I want to connect my MSP-EXP430F5529LP ("MSP430") LaunchPad to an external device via I2C. Which I2C port should I use? (1) The MSP430 Quick Start Guide (slau536.pdf) includes a diagram of the BoosterPack connector showing two sets of I2C ports: -set#1- I2C - SCL - PM_UCB1SOMI - PM_UCB1SCL - P4.2 I2C - SDA - PM_UCB1SIMO - PM_UCB1SDA - P4.1 -set#2- UCB0SDA - UCB0SIMO - P3.0 UCB0SCL - UCB0SOMI - P3.1 (2) I am using the sample project, usci_b_i2c_ex3_masterTxSingle.c. MSP430ware->Libraries->Driver Library->MSP430F5xx_6xx->Example Projects->USCI_B
  7. Hello, as I was studying the (extremely good written!) driverlib documentation, i noticed the SysCtlPeripheralReady function. Because it is not always clear which Timer (TIMER,WTIMER,WATCHDOG) is currently in use (many of them are used with PWM and other stuff), I wrote this little helper sketch for my Tiva C. The definitions for other peripheral can be read in "sysctl.h", I only used the timers to keep it short. I also included the SysCtlPeripheralPresent function, but I think it is meant, that a peripheral is physically available, so the "ready" function is the key. Try it out with some
  8. It was only after looking at some examples for the F5529 LaunchPad that I came across TI's DriverLib. Odd that I've never seen it mentioned before. Is anyone using it? Is it worth getting familiar with it or should I just stick with dealing with registers directly? I'm tempted to give it a go as there's a lot more to the F5529 with USB. Also at my skill level adapting sample code will get me going quicker that doing everything from scratch. However, I've so little free time that I don't want to waste it get to know yet another framework / library if it's not going to be that useful.
  9. During the workbook and some own created test I notice that I have an lib thats build in debug mode. Thanks to the answer there and collecting the reading stuff, I did read a little about the ROM_xxxx, MAP_xxxx. Anyway, I still would like to have the driverlib release build. Specialy during development, can allways later change the calls to ROM_functions. Is there a way, (a tut), to build this under window's. Knows a little about make and the makefiles under windows. Found some make stuff from arround 2003. Did found also at TI the BSD licened LM4 makefiles. Don't have linux but
  • Create New...