Jump to content

dubnet

Members
  • Content count

    560
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by dubnet

  1. error message not shown

    First of all, welcome to the forum. in order for someone to help you, you will need to provide more information. Please see this link for guidance.
  2. Sounds like noise. How is the ADC input physically connected to ground? If it is a long jumper wire you may want to shorten it as much as possible. A long jumper wire will act as an antenna, picking up noise from the digital clocks on your board. Another thing you can try is placing a small capacitor right at the ADC pin to ground.
  3. Hi from dannyf

    Welcome to the forum!
  4. Welcome to the forum. It is best to start a new topic rather than post to a topic that is a year old. To the best of my knowledge, Energia only supports two of the four serial ports available on the msp432. In order to use the other two ports you would need to use CCS (TI's development environment for their MCUs).
  5. MSP430F149 Board

    @Fmilburn Thanks for the feedback. I did a little bit of research on the tradeoffs between the two methods, both from a readability standpoint and a performance standpoint. It wins on the readability and can be faster executing in many cases than the if/then approach. I will "switch" the code the next time I work on it.
  6. MSP430F149 Board

    A while back @omnicron generously offered up some surplus boards sporting a MSP430F149 and a good mix of conditioned I/O on the board including a couple of 5.8psi pressure transducers. I feel that this, along with the programming header on the board, makes it a good all-around board for general purpose projects. The board also supports a standby NiMH battery (6v, 1800mAh) with charging/discharging capability and voltage monitoring all controlled by the MCU. The battery switches in via a relay upon primary power loss. One of the pushbuttons is configured in hardware to be used as a soft power on/off and requires just a little bit of code to work. One of the concerns upon getting the board is that, even though it has a programming header, the fuse may have been blown to protect the original code. With the fuse setup on the MSP430F149 that would be a show stopper and the board would have been a paper weight. Thankfully, when I connected my MSP-FET I was able to talk to the MCU as well as program it. So what does one do when presented with a new piece of hardware? Write code to flash LEDs and exercise the hardware, of course. Since I wanted to make this a general purpose, “throw it at a project” kind of board, I wanted to write some functions to simplify the main program code. So far I have routines for digital I/O, analog in, chip temperature and a function to display a binary result on the eight LEDs on the board. One downside to the way this particular board was designed is the lack of easily accessible serial ports. One way around this is to solder directly to the MCU pins to utilize the secondary serial ports , but that wasn't very attractive. Looking at the schematic I found that by removing three passives from each of the two serial lines, I could repurpose what were originally a couple of digital outputs and have a serial port (UART only, no I2C on this MCU). SPI is also possible using the same technique, but a little more cumbersome to implement. I haven't written the functions for serial yet and will probably wait until I actually need serial I/O. The video demonstrates my demo code that utilizes soft power using the switch shown at the bottom left. Default power up behavior is the 8 LEDs chasing up and down. The next switch to the right of the power switch toggles the beeper which, when activated, sounds every time the LED furthest to the left (LSB) lights up. The next switch to the right toggles the speed of the LEDs and the final button displays the chip temp in binary (75 degrees in this case), pauses to allow it to be read and then resumes the LED chasing. There… hardware reasonably exercised. J I have included pictures of the front and back of the board as well as a PDF schematic. If you have the inclination I welcome feedback on the code and the resulting opportunity to learn to code more efficiently. // Since I used portions of TI’s MSP430ware examples in two functions (chiptemp and analogIN) I am //including the TI copyright notice below: /* --COPYRIGHT--,BSD_EX * Copyright (c) 2012, Texas Instruments Incorporated * All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * * Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * * Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * * * Neither the name of Texas Instruments Incorporated nor the names of * its contributors may be used to endorse or promote products derived * from this software without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * ******************************************************************************* * * MSP430 CODE EXAMPLE DISCLAIMER * * MSP430 code examples are self-contained low-level programs that typically * demonstrate a single peripheral function or device feature in a highly * concise manner. For this the code may rely on the device's power-on default * register values and settings such as the clock configuration and care must * be taken when combining code from several examples to avoid potential side * effects. Also see www.ti.com/grace for a GUI- and www.ti.com/msp430ware * for an API functional library-approach to peripheral configuration. * * --/COPYRIGHT--*/ #include <msp430.h> #define ana_ch_a 0x01 // Port 6.0, A0 #define ana_ch_b 0x02 // Port 6.1, A1 #define ana_batt 0x03 // Port 6.2, A2 #define ana_9v 0x04 // Port 6.3, A3 #define ON 0x01 #define OFF 0x00 #define LED_1 0x01 // Port 2.0 #define LED_2 0x02 // Port 2.1 #define LED_3 0x03 // Port 2.2 #define LED_4 0x04 // Port 2.3 #define LED_5 0x05 // Port 2.4 #define LED_6 0x06 // Port 2.5 #define LED_7 0x07 // Port 2.6 #define LED_8 0x08 // Port 2.7 #define LED_9 0x09 // Port 3.0 #define LED_10 0x0A // Port 3.1 #define valve_a 0x0B // Port 3.2 #define valve_b 0x0C // Port 3.3 #define pump_a 0x0D // Port 3.4 #define pump_b 0x0E // Port 3.5 #define charge 0x0F // Port 3.6 #define discharge 0x10 // Port 3.7 #define beep 0x11 // Port 4.0 #define chkbatt 0x12 // Port 4.1 #define VCCEN 0x13 // Port 4.2 //array and variables to support functions const int BitValue[8] = {0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0x80}; unsigned int var1; unsigned int var2; unsigned int var3; unsigned int var4; unsigned int a; unsigned int b; unsigned int c; unsigned int ADCvalue; int long IntDegF; void PostLEDValue (unsigned int Var4); void chiptemp(int long degree_f); void analogIN(unsigned int var3); // values= ana_ch_a/b, ana_batt, ana_9v void digitalWrite(unsigned int var1, unsigned int var2); // values = LED_1-10, valve_a/b, pump_a/b, beep, charge, discharge, chkbatt, VCCEN, and var2 = ON, OFF volatile unsigned int i=0; unsigned int led_count; volatile unsigned int j; unsigned int l=2; unsigned int sw_press = 0; unsigned int beep_status = 0; unsigned int speed = 6000; int long temp; void main() { WDTCTL = WDTPW + WDTHOLD; DCOCTL = DCO0 + DCO1; BCSCTL1 = RSEL0 + RSEL1 + RSEL2; P1DIR |= 0x00; P4DIR |= BIT0 + BIT1 + BIT2; P4OUT |= 0x00; P4OUT |= 0x04; // Set P4.4 to 1 (VCCEN) P2DIR |= BIT0 + BIT1 + BIT2 + BIT3 + BIT4 + BIT5 + BIT6 + BIT7; P2OUT &=~(BIT0+BIT1+BIT2+BIT3+BIT4+BIT5+BIT6+BIT7); P2OUT |= (BIT0+BIT1+BIT2+BIT3+BIT4+BIT5+BIT6+BIT7)& 0xFF; P3DIR |= BIT0 + BIT1 + BIT2 + BIT3 + BIT4 + BIT5 + BIT6 + BIT7; P3OUT &=~(BIT0+BIT1+BIT2+BIT3+BIT4+BIT5+BIT6+BIT7); P3OUT |= (BIT0 + BIT1) & 0xF; P1IES |= 0x00; P1IFG |= 0x00; P1IE |= (BIT0 + BIT1 + BIT2 + BIT3 + BIT4 + BIT5 + BIT6 + BIT7); _enable_interrupt(); // MAIN CODE STARTS HERE ---------------------------------------------------------- l=2; do { led_count = 11; do { led_count--; j = speed; // Delay 6000 or 1500 do (j--); while (j != 0); if (led_count == 9){ led_count = 8;} if (led_count == 7){ led_count = 6;} digitalWrite(led_count, ON); } while (led_count != 1); i = 45000; do (i--); while (i != 0); if (sw_press == 3) { // Toggle beep at LSB transistion beep_status ^= 0x01; sw_press = 0; } digitalWrite(beep, beep_status); i = 5000; do (i--); while (i != 0); // Delay 5000 digitalWrite(beep, OFF); if(sw_press == 1) { // Soft Power Down P4OUT ^= 0x04; sw_press = 0;} if (sw_press == 4 && speed == 6000) { //Toggle LED chase speed speed = 1500; sw_press = 0;} if (sw_press == 4 && speed == 1500) { speed = 6000; sw_press = 0;} if (sw_press == 5) { sw_press = 0; chiptemp(0);} led_count = 0; do { led_count++; j = speed; // Delay 6000 or 1500 do (j--); while (j != 0); if (led_count == 7){ led_count = 8;} if (led_count == 9){ led_count = 10;} digitalWrite(led_count, OFF); } while (led_count != 10); i = 50000; do (i--); while (i != 0); // Delay 50000 } while (l != 0); } // MAIN CODE ENDS HERE ------------------------------------------------------------------------------------ #pragma vector=PORT1_VECTOR __interrupt void PORT1_ISR(void){ _disable_interrupt(); if(P1IFG & BIT0) { sw_press = 1; P1IFG &= ~BIT0; } if(P1IFG & BIT1) { sw_press = 2; P1IFG &= ~BIT1; } if(P1IFG & BIT2) { sw_press = 3; P1IFG &= ~BIT2; } if(P1IFG & BIT3) { sw_press = 4; P1IFG &= ~BIT3; } if(P1IFG & BIT4) { sw_press = 5; P1IFG &= ~BIT4;} if(P1IFG & BIT5) { sw_press = 6; P1IFG &= ~BIT5; } if(P1IFG & BIT6) { sw_press = 7; P1IFG &= ~BIT6; } if(P1IFG & BIT7) { sw_press = 8; P1IFG &= ~BIT7; } _enable_interrupt(); } #pragma vector=ADC12_VECTOR __interrupt void ADC12ISR (void) { _disable_interrupt(); temp = ADC12MEM0; _enable_interrupt(); } // FUNCTIONS BEGIN HERE -------------------------------------------------------------------------------------------- void digitalWrite(unsigned int var1, unsigned int var2){ a=0; b=0; c=0; if (var1 <= 0x0A){ //Flip ON/OFF on LED outputs since they are active low. var2 ^= 0x01;} if (var1 >= 0x10 && var1 <= 0x13){ c = (var1-17); if (var2==1){ a=P4OUT; a=a|(BitValue[c]); P4OUT=a;} if (var2==0){ a=P4OUT; b=~(BitValue[c]); P4OUT = (a&b);} } if (var1 >= 0x09 && var1 <= 0x10){ c = (var1-9); if (var2==1){ a=P3OUT; a=a|(BitValue[c]); P3OUT=a;} if (var2==0){ a=P3OUT; b=~(BitValue[c]); P3OUT = (a&b);} } if (var1 >= 0x01 && var1 <= 0x08){ c = (var1-1); if (var2==1){ a=P2OUT; a=a|(BitValue[c]); P2OUT=a;} if (var2==0){ a=P2OUT; b=~(BitValue[c]); P2OUT = (a&b);} } } void chiptemp (long int degree_f) { ADC12CTL0 = SHT0_8 + REFON + ADC12ON; ADC12CTL1 = SHP; ADC12MCTL0 = SREF_1 + INCH_10; ADC12IE = 0x001; ADC12CTL0 |= ENC; ADC12CTL0 |= ADC12SC; i = 5000; do (i--); while (i != 0); IntDegF = (temp - 2519) * 761; IntDegF = IntDegF / 4096; temp = 0; degree_f = IntDegF; PostLEDValue (degree_f); } void PostLEDValue (unsigned int var4){ led_count = 0; do { led_count++; j = 250; do (j--); while (j != 0); // turn off LEDs if (led_count == 7){ led_count = 8;} if (led_count == 9){ led_count = 10;} digitalWrite(led_count, OFF); } while (led_count != 10); if (var4 > 64){ var4 = var4 - 64; digitalWrite(LED_8, ON); } if (var4 > 32) { var4 = var4 - 32; digitalWrite(LED_6, ON); } if (var4 > 16) { var4 = var4 - 16; digitalWrite(LED_5, ON); } if (var4 > 8) { var4 = var4 - 8; digitalWrite(LED_4, ON); } if (var4 > 4) { var4 = var4 - 4; digitalWrite(LED_3, ON); } if (var4 > 2) { var4 = var4 - 2; digitalWrite(LED_2, ON); } if (var4 == 1) { digitalWrite(LED_1, ON); } j = 20; //delay to allow reading of LEDs do { i = 50000; do (i--); while (i != 0); j--; } while (j != 0); } void analogIN (unsigned int var3){ ADC12CTL0 = SHT0_8 + REFON + ADC12ON; ADC12CTL1 = SHP; if (var3==1){ ADC12MCTL0 = SREF_1 + INCH_0; } if (var3==2){ ADC12MCTL0 = SREF_1 + INCH_1; } if (var3==3){ ADC12MCTL0 = SREF_1 + INCH_2; } if (var3==4){ ADC12MCTL0 = SREF_1 + INCH_3; } ADC12MCTL0 = SREF_1 + INCH_10; ADC12IE = 0x001; ADC12CTL0 |= ENC; ADC12CTL0 |= ADC12SC; i = 5000; do (i--); while (i != 0); ADCvalue = (temp/16); PostLEDValue (ADCvalue); } - Circuit Diagram.pdf Demo_Program_Video.MOV
  7. MSP430F5529 and RFM12b used together

    What your professor should have said is: "A logic analyzer is your best friend". Seriously though, if you can borrow a logic analyzer to monitor what is happening on your communication lines that would allow you to see what is really happening. It is very difficult to troubleshoot communication issues between devices without one since you can't tell if you have a hardware issue, a software issue or a combination of the two. If you can't get a hold of a logic analyzer then a four channel memory scope, although not ideal, could help shed some light on the situation as well.
  8. My apologies. I did see that you had mentioned the fact that you are using the 5529. I didn't connect the dots very well between your hardware and the MSP430G2 Launchpad as it pertains to the CC110 Booster Pack. When I tested the CC110 I did use the MSP430G2 so disregard my comments on everything except the actual results of my distance test. Perhaps @energia could jump in and shed some light on the Energia implementation as it pertains to the CC110 Booster Pack and the issue you are experiencing. Wish I could have been more help.
  9. Have you tried to use the demo software included with the CC110 Booster Pack to verify performance? It allows you to set the various parameters of the CC110 from a GUI. The default program for the Launchpad itself is preprogrammed in the MSP430G2553's included with the CC110 Booster Pack. I was able to achieve reliable communications between two modules at a distance of 300 feet or more between two floors inside a concrete/metal commercial building.
  10. Msp430 software serial error

    With the 5529 you don't want to use software serial. It isn't necessary as the 5529 has 2 hardware serial ports. if you are doing an include of the software serial library in your code you will want to remove it. Also, please only post once. You may also want to post your code with your request for help. It allows folks to better help you.
  11. energia software serial with msp430f5529

    My understanding is that the software serial is only supported in the value line MCUs under energia. However, the 5529 has two hardware serial ports available under energia. I have used both ports on the 5529 with energia in past projects.
  12. GPS interfacing

    Since the board is not a TI product, I am not sure how compatible it is with Energia. You may want to check with the manufacturer to verify that it is. Regarding software serial, you will need to change the references to software serial in the sketch to one of the available hardware serial ports.
  13. GPS interfacing

    You didn't mention which specific launchpad you were using. Software serial, IIRC, is only supported on the valueline MSP430G series MCUs without hardware serial built in. So unless you are using one of these, you will need to modify your code to use the hardware serial port on the MCU you are currently using (instead of software serial).
  14. MSPDebug can't connect to MSP-EXP430G2 under Linux

    The G2553 is a current product and you should be able to work with it under CCS or Energia. It does look like a driver issue to me as well. However, I'm not a Linux expert so you may want to wait for someone here more versed in Linux to chime in. You may also want to post your question on the TI E2E forum.
  15. MSP430F5529 LPM Questions

    it would appear to be so. If you have the 5529 Launchpad it would easy to confirm.
  16. MSP430F5529 LPM Questions

    You would need to take a look at the documentation for the F5529 to verify that it can be awakened with a GPIO interrupt. In a very deep sleep, IIRC, the list of available interrupt sources gets shorter. So if LPM4.5 supports a GPIO transition as a wakeup source you should be good to go.
  17. Upload error

    Are you using the 432 Launchpad black PCB or the red PCB? If you are using the black there are issues with the now obsolete black board. By using an earlier version of Energia (e.g. V16 or V17), it may solve the issue.
  18. MSP430F5529LP

    First of all, welcome to the forum. If I remember correctly, the software serial library isn't supported on the F5529, only on the lower end G2 parts without built in hardware serial. However, it shouldn't be needed as the 5529 has two hardware serial ports. The second serial port would be referred to as Serial1 (e.g. "Serial1.begin" as opposed to the first serial port "Serial.begin"). Refer to the pin outs on energia.nu for the correct pins for each port.
  19. Current too high in LPM3; what am I missing?

    @NurseBob Not familiar with that one, but they do have an infinite bag of tricks. A memorable experience was when I was young.... I stayed over at friend's house in Southern California and slept on a pull out couch sofa bed. They had a cat with a bell on it's collar. The room was fairly dark but I could hear the cat moving about the room, and then silence. The cat would then launch from his perch on the back of the couch and land on my head or body. I would shoo him off and the process would repeat, until I determined he was having far more fun than I was and wouldn't quit this game any time soon, At that point I prevailed upon my friend to put the cat on lockdown for the night.
  20. New from Buffalo, NY

    Welcome to the forum!
  21. Current too high in LPM3; what am I missing?

    @NurseBob Happy to hear that you are all ok. Given the hurricanes, earthquakes and wildfires it has been a tough year for lots of folk. Your cats may seem to have forgiven you but they are just waiting for the right opportunity.....
  22. Current too high in LPM3; what am I missing?

    @NurseBob Was saddened to see the destruction and loss of life due to the wildfires. Hopefully you won't be affected but please evacuate without a moments hesitation if it even starts to move toward you. In the big picture stuff is truly meaningless and life is precious.
  23. Current too high in LPM3; what am I missing?

    When I have utilized EnergyTrace in the past I have found that I had to disconnect all FET data lines in order to get a measurement that was close to the calculated current consumption. You could try disconnecting the TDIO and TCK lines, leaving just 3.3V and ground connected between your target and the FET to see if that improves the measurement.
  24. Kentec Library (BOOSTXL-K350QVG)

    I vaguely remember something a while back on the E2E forums with regard to the Kentec driver/library not being right on the 432. If I recall correctly, there was an updated version referred to which sped up the display significantly and made the original poster happy. A well worded search should find that thread. EDIT: Did a few searches and couldn't find it. Perhaps it was not the 432 but a Tiva issue. That's the trouble with vague memories.... You may want to try posting on E2E if you can't find it by searching. If it is indeed the issue I seem to remember, then perhaps one of the TI guys might recall and be able to help out.
  25. msp430-g++ File Not Found! HELP!!

    No problem. Happy to hear you got it resolved.
×