Jump to content
43oh

Leaderboard

Popular Content

Showing content with the highest reputation since 01/22/2020 in all areas

  1. bluehash

    Forum flooded with spam

    Hi All, I cleaned up the site last week. This year has not been the greatest for me(and for alot). Pardon the neglect. True that the blog has not been update, but I have not seen much content on the MSP430/432. Also TI's E2E has been vastly popular. There was no "commercial" side. I still pay for server and forum licenses out of pocket. I've kept it up since there is alot of useful info and people benefit from it.
    2 points
  2. And with J7 removed, everything works just fine. Note to the future: if trying to do I2C on EXP430G2ET, remove J7. It probably says that somewhere in the user guide.
    1 point
  3. I locked myself out by incorrectly programming GPIO reg C. I used the LMflashprogrammer to unlock it.
    1 point
  4. As far as I can remember, the G2553 has a very small serial buffer. Just try to reduce the number of byte to send, e.g. AT: Instead of Enter AT commands:
    1 point
  5. G2553 has a Hardware Serial Interface, so do not use the Software implementation. Serial BTSerial..... Should work
    1 point
  6. Which MSP430 are you using? I recently tested it on an MSP430F5529 and that worked. One thing to note though is that pins 3 and 4 are already used by Hardware Serial which you use in your Sketch (Serial.xyz()). Try changing to different pins. I would suggest you try pins 11 and 12 if you are not using those for anything else. Robert
    1 point
  7. Yes, of course you can do that. Just for the Launchpad the numbering is always done on the boarder of the PCB = Pin Headers of the board, as this is the point where a typical user would connect something. If you prefer for your own board to have the device pin numbers used - you can do that. Doing the updates as you mentioned above should do that 🙂 To get the board in the GUI you need to - add a device in the variants folder - as just discussed with the update of the pins_energia.h file - add a section into the boards.txt file (located in the folder above) in a s
    1 point
  8. I'v solved this issue installing previous version of Energia. It's works. Release version 1.8.7E21 (10/17/2018) upload correctly.
    1 point
  9. zeke

    MSP430 Nixie Clock

    I have a zip file of @RobG's Nixie Clock V3. @RobG, I hope you are okay with me posting this? @bluehash, please delete this if there is a problem.
    1 point
  10. Thanks, for the feedback. I have already implemented the fixes based on your findings and planning for an update release of this package.
    1 point
  11. Rei Vilo

    BME280

    @Abdul400 There is no need to post the same question multiple times, as already at Please refer to: Netiquette for Newbies Porting an Arduino library to Energia
    1 point
  12. It looks like that the compiler setting for the large memory model is not set correct. can you open the platform.txt file in c:/users/johnw/appdata/local/energia15/packages/energia/hardware/msp430elf/2.0.7/platform.txt and change line 21 from compiler.mlarge_flag=-mlarge -mcode-region=upper to compiler.mlarge_flag=-mlarge -mcode-region=either
    1 point
  13. You could use a library designed for Arduino. See Porting an Arduino library to Energia
    1 point
  14. >energia also has in its software serial library error Well, no. The 5529 has hardware serial. Don't use software serial. FWIW, it's not an error in Energia, but a limitation of the software serial library that it can't run with the faster clock. HTH
    1 point
  15. You can use a library for Arduino and adapt it to the MSP430. Porting an Arduino library to Energia
    1 point
  16. The first line in the error log says it all: java.io.IOException: Cannot run program "{runtime.tools.dslite-9.2.0.1793-e1.path}/DebugServer/bin/DSLite": CreateProcess error=2, The system cannot find the file specified It's not about the launchpad but your Energia/system configuration. In short, a "file not found" error for the compiler. So, an environment/path setting? On my system the compiler is found @ C:\ti\Energia\energia-1.8.10E23\hardware\tools\DSLite\DebugServer\bin if you search for dslite under your Energia installation is it found?
    1 point
  17. enl

    MMA8452Q / MSP-EXP430G2ET

    To follow up with @Rei Vilo the actual errors are important here, as is the processor (though I would presume G2553 given where you put the question). Also, the interface module you are trying to use (I2C I would hope, since the MMA8452Q only communicates with I2C), what header files you included, what processor you selected in CCS project setup, and so on.
    1 point
  18. Please have a look at Information to Provide When Asking for Help I²C Check-List I guess you're using the MMA8452 on I²C.
    1 point
  19. The RAM of an MCU can’t be expanded. Go for another LaunchPad with a more capable MCU.
    1 point
  20. Yes, this is the right file (- as the energia-1.8.10E23 did not got a update on the MSP430 tool chain - then it would be in c:\Users\USERNAME\AppData\Local\Energia15\packages\energia\hardware\msp430 - just for completeness) Yes, update both lines
    1 point
  21. The goal of this project is to utilize an MSP430 to allow existing remote-controlled outlets to by controlled over Wi-Fi. As purchased, the outlets can be controlled with a provided remote control which uses 434 MHz radio signals. By programing the MSP430 to replicate the signals from this remote and hosting a web page with controls on the MSP430, the outlets can be able to be controlled from anywhere on the same Wi-Fi network. The completed project provides a web page that can both control each of three outlets individually or all three at once. This is done using an MSP430 as a controller wi
    1 point
  22. Sorry being a newbie to 430oh.com if this is a no-no posting to old threads. But did get the Neopixel Library working with an MSP432 Launchpad (some tweaking of the Cortex-Mx assembly required. Much thanks to the WS2811 driver mentioned here: Only problem is I am not the greatest C++ programmer and had to hardcode the GPIO somewhat in Adafruit_NeoPixel.cpp : //jg 12/5/17 P1.0 is pin 78. 0x40004C02 YELLOW_LED //jg 12/5/17 P2.0 is pin 75. 0x40004C03 RED_LED //jg 1/3/18 P3.0 is pin 18. 0x40004C03 - Gets Neopixel off LED jumper on MSP432 LP But hooks are in Adafruit_NeoPi
    1 point
  23. EMT low power unfortunately is not well documented but quite simple. How low of a power the device goes into depends on what interfaces are open and what device the Sketch runs on. The quick reference: If all Sketches are in delay() the idle loop is entered. The idle loop is a TI-RTOS task that consults the power manager and then determines what level of low power it can go to. Make sure that all unused pins are in the appropriate state according to the datasheet. Usually this is output high. Make sure that sensors that are connected are put into sleep mode if you intend to go to low p
    1 point
  24. Here are 2 graphics libraries that can be used with my Color LCD BoosterPacks as well as some other LCDs ugl8tiva works with: 1.8" JD-T1800 ST7735 2.2" ILI9225 (with touch panel or without, but touch is not implemented yet.) ugl8tiva.zip ugl16tiva works with: 2.2" 320x240 ILI9341 2.4" 320x240 ILI9341 ugl16tiva.zip (updated 4/27/15, new pinout) MSP430 versions are here
    1 point
×
×
  • Create New...