Jump to content

Search the Community

Showing results for tags 'OUTPUT'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Sparkfun


Github

Found 4 results

  1. So, I'm using Energia and getting frustrated with Wire.h. I need to do some i2c communications and figured it would be fairly easy to write my own Bit-Bang implementation of i2c. I got started and things seem to be working pretty well. However, I discovered the concept of OpenCollector. It seems that OpenCollector means that the pin is set to High by default with a Pullup Resister and you just set it to LOW and then it goes back to high when you're not setting it to LOW. It also goes to low when a slave i2c device sets it to LOW. Question is how the heck do we do this with Energia?? Does pinMode(INPUT) set a pin to OpenCollector mode? Does pinMode(INPUT_PULLUP) set a pin to OpenCollector mode? If either of these do, what does digitalWrite(LOW) do on that pin? It sets it to LOW, but for how long? Do you have to set it back to HIGH, or does it get pulled back up to HIGH, or does setting it to HIGH, just release the LOW pull-down? This behavior doesn't seem to be documented anywhere that is easy to find. Perhaps it's not intended to be used that way, but I don't know how a person would implement i2c correctly without being able to set the SCL and the SDA to OpenCollector mode and to be able to pulse the clock. Speaking of pulsing the clock, how is that to be accomplished? Seems like you should be able to pull it LOW and then let it go, but I'm not sure how to 'let it go' back to its HIGH state without just calling digitalWrite(HIGH) on that pin.. But then aren't I holding it high? Anyway, if somebody has a good explanation around this, I would LOVE to hear it. I found some hints about it at the following location http://energia.nu/Constants.html But it didn't use the term OpenCollector anywhere...
  2. I'm getting very frustrated with this CC3200MOD, and the CC3200 in general. First it started with the A0 analog channel always reading 4096 but now on to some GPIO problems. This should be fairly straight forward but apparently they make everything difficult, so I don't know what to say. I have made a custom PCB for using the CC3200MOD. Its supposed to read the 4 ADCs, 3 for accelerometer, which is working great, 1 for an analog microphone, which isn't working at all, but I've given up on it and going to just mux with one of the 3 working ones. Now I have 3 LEDs on the board for general LED applications. These LEDs are on pins(pins of the MOD device) 6,7,8, which correspond to (according to PinMux Tool) GPIO 15,16,17. So ideally I should be able to just pinMode the pins to OUTPUT, and set them HIGH to have the LEDs working. I should mention right now that I have two populated boards both have issues in the same way. So if I was to do this in Energia it would just be: pinMode(15,OUTPUT); pinMode(16,OUTPUT); pinMode(17,OUTPUT); digitalWrite(15,HIGH); digitalWrite(16,HIGH); digitalWrite(17,HIGH); So this is where it gets strange, only 1 LED turns on, only GPIO16. But here is the kicker, GPIO16 turns on only when I enable GPIO15!! What the heck is going on, I think there is an issue with Energia incorrectly labelling pins but I cannot find the solution. I think this is also the issue with the analog pin, but I want to sort this out first. Does anyone know what is going on? Ill break it down: GPIO16 turns on when I digitalWrite(15,HIGH) GPIO15 and GPIO17 don't turn on at all and get some weird low voltage on them. Using Energia
  3. ClydeTombaugh

    Output Pins Don't Work

    Hi, I'm running Energia on Windows 7 x64. My Launch Pad model is the MSP-EXP430F5529LP (25Hz) My board's green LED will light up when connecting to the computer, the red LED will flash while compiling and all onboard LEDs and buttons function when programed. However, whenever I try to program output pins and connect the output in question to ground, I get no current out. I have plenty of experience with Arduino and all programs I write for the Launch Pad work for Arduino. The GND, 5V and 3.3V pins on the LaunchPad all work fine. I have also used a number of sample programs, all to no avail. Here is a schematic sheet for my model. http://energia.nu/img/LaunchPadMSP430F5529.jpg Here is a quick program that I have written to demonstrate one way that I have been testing it. const int led = 19; // LED is hooked to P2.0 aka 19 with at 220 Ohm resistor and then connected to ground. void setup() { pinMode(led, OUTPUT); } void loop() { digitalWrite(led, HIGH); //LED should turn on and quickly flash off and on again delay(1000); //I know for sure that the LED is not broken because I digitalWrite(led, LOW); // repeatedly test it with my Arduino between compiling delay(500); }
  4. dtour

    Driving BJT with MSP430G2553

    I'm trying to drive an NTE108 (BJT NPN) with an output pin on my MSP430G2553 and having trouble. The output (P2.4) of the MSP is connected to the base of the BJT through a 330 resistor and controlled via software on the MSP. I've attached a picture of the schematic (R1 is a recent addition). Pin P2.4 works as expected when connected to the LaunchPad. It can drive an LED and works when floating. I cannot test it with the BJT (NTE108) because I only have one and it is soldered down. I have moved the MSP over to a protoboard where it is supplied with a 3V regulator that can do 250mA. Now the problems start... P2.4 floats somewhere between 0.5V and 1.5V all the time. It has not been configured in software for pullup/pulldown resistors. It seems like there is some activity when the pin should change from the software, but the voltage variation is minimal. If the base resistor R10 is disconnected from P2.4 and connected directly to Vcc (3V), it turns on the transistor as expected and the motor runs. >> Maybe the MSP cannot supply the current to turn on the BJT... If the base resistor R10 is disconnected from the MSP430, the pin floats near 1.0V regardless of software control (should be 3 or zero). If R1 is disconnected, the same happens.>> Not a current supply problem. I have checked that the chip is properly grounded and receiving adequate power. I have moved the chip back to the LaunchPad and everything still works fine. Any thoughts on why the pin is floating and cannot be controlled? This is driving me crazy. I only have problems on the protoboard so it's probably something to do with connections, but I've tried to check what I can. Is there something I'm missing about moving the MSP430 from a LaunchPad to a protoboard? Thanks, Danny
×