Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Rickta59

  1. You could the launchpad with mspdebug and msp430-gdb for true hardware debugging. However, that isn't supported directly from the Energia environment. You would have to use the command line tools to get at that capability. Unfortunately it doesn't solve your other requirement of using two ports in the future. What you want to do is possible. However, it would be best accomplished using native code to program the peripherals using a lower level access than the Energia API provides. You can look in the projects section of this forum for serial code that uses cycle counting and bit bangin
  2. The TBA remark was in reference to TimerSerial and it has been implemented. Energia isn't really setup to use 2 serial ports. TimerSerial isn't meant to multiplex between various serial devices. Its purpose is to provide a simple implementation to talk to the host. To do what you are asking would require that you use the UART for one device and a either a custom timer serial or custom cycle counting serial. Neither of the secondary alternates are part of Energia. This doesn't seem to be a good fit for Energia. What are you actually trying to do?
  3. Did you want a SoftwareSerial so you can use any port? Or did you just want a Serial implementation that works with a g2231/g2452?
  4. Not without a deeper understanding of the hardware. The easiest solution is to get an msp430g2553 chip if you want to use simple code.
  5. Your Servo.h and TImerSerial both want to use the same Timer interrupt. Which chip are you using? I'm guessing the g2452 or g2231. You will have to use the g2553 if you want to use both Serial and something that uses the Timer interrupt.
  6. These images are great. Nice job. ... My only concern is that people with a version 1.4 board or older will fry their chips. On those boards the first two jumpers are are VCC (3.5volts) and TX. Turning those jumpers sideways could potentially cook the pin. Maybe a disclaimer is in order. If you have a 1.4 board, don't ever turn your first two jumpers 90 degrees.
  7. I don't think you have found a bug, delayMicroseconds expects an unsigned int. void delayMicroseconds(unsigned int us) That means the maximum value you can pass is 65535. You might want to use the delay() function for longer delays.
  8. Note: MOSI and MISO are flipped on the USI chips. (g2231/g2452)
  9. #if defined(__MSP430_HAS_USCI__) static const uint8_t SS = 8; /* P2.0 */ static const uint8_t SCK = 7; /* P1.5 */ static const uint8_t MOSI = 15; /* P1.7 */ static const uint8_t MISO = 14; /* P1.6 */ #endif #if defined(__MSP430_HAS_USI__) static const uint8_t SS = 8; /* P2.0 */ static const uint8_t SCK = 7; /* P1.5 */ static const uint8_t MOSI = 14; /* P1.6 */ static const uint8_t MISO = 15; /* P1.7 */ #endif
  10. At this time, with Energia 101E0008, the most power chip supported is the msp430g2553. In the works are the msp430fr5739 you find in the fraunchpad board. This chip has 16K of FRAM and 1K of RAM. However because it is FRAM you can use it like RAM allowing you a lot more flexibility. The code to make it work with Energia is in the "fraunchpad" branch and should be part of the master soon. After we get the frauchpad in the master branch and tested, we will start looking at the msp430f5510 you find in the recent Olimex board. http://www.mouser.com/olimex-olimexino5510/ The problem
  11. Glad you got it working. Version 0101e006 was feature incomplete. Version 101E008 is much better. Hopefully each new version will be better than the last.
  12. Says you. I'd prefer that the hardware have some sense of the software that will use it. Designing the pins so the software can take advantage of the hardware would be my preference.
  13. All booster packs that use SPI are going to have a problem depending on which chip it was targeting. The MOSI and MISO pins are the opposite on boards with USI vs USCI. If you design your board for the g2452 it won't work with a g2553 chip if you want to use hardware SPI. So no, just because you can physically jam one socket into the other doesn't really mean they are compatible. The booster pack designer has to make sure they provide some form of jumper to allow you to select the proper socket to pin mapping. -rick
  14. You get that because you hadn't posted three times. Now that you have made three posts you should be able to post a link to the correct url. I did look before I asked. I didn't find anything marked specifically Keypad_I2C. That is why I asked. When I search the Arduino playground for "Keypad_I2C". I get 3 hits, none of which are actually "Keypad_I2C". http://arduino.cc/playground/Main/I2CPortExpanderAndKeypads http://www.arduino.cc/playground/code/Keypad http://arduino.cc/playground/Main/I2CPortExpanderAndDecoders I also found some posts in the forum that allude to problems with
  15. Could you provide a link to where you got your "Keypad_I2C"?
  16. I don't think any of us have a raspberry PI. Paired with the msp430 it would create a useful networking and data sampling duo.
  17. Some parts should port fairly easily. The problem would be in using the various time sources. TimerSerial should work. TimerGPS less so as we don't have a NewSoftSerial library. You would have to write one of those yourself. The TimeNTP time source uses networking so it isn't going to port without a lot of effort. There really isn't a standard networking card for the launchpad. So there isn't any networking code to use. Other than the time sources, some of the code is very AVR specific. It uses the avr-gcc macro PROGMEM which isn't valid for the msp430. char monthStr1[] PROGMEM = "Jan
  18. When you say converting .. what does that actually mean. Are you going to delete all the existing posts? -rick
  19. When you use a calculator to multiply, all the secrets about how to multiple are hidden in the firmware of the calculator. When you use Energia to read and write the serial port, all the secrets of how that is done is available for you to look and learn from.
  20. It doesn't hide anything. It doesn't limit you. There is nothing stopping you from typing in straight 'C' code and skipping all the provided API calls. Energia isn't a language. It is a pre-configured build system with examples using a object oriented API for some of the common peripherals. It uses C++ classes, C code and some msp430 asm. Users of Energia have the ability to use all or none of those features to get to any part of the processor. It isn't dumbed down. Energia has a predefined way it works, but there is nothing stopping you from completely ignoring all of the provided framew
  21. $ msp430-objdump -S /tmp/buildxxxx/somfile.elf | less That will show you the generated asm and the c code mixed together in a listing.
  22. This might work http://askubuntu.com/questions/95081/ca ... ng-haskell
  23. That link is the binary distribution. Probably won't be another till we add some more features. -rick
  24. There aren't any wrappers for the Comparator as of yet. You could look at the TI code samples for the msp430g2553 and use that as a starting point. http://www.ti.com/litv/zip/slac485a code samples there. Check out the ones with *_ca_* in the name of the file. -rick
  25. Maybe you could give our latest binary release a try: https://github.com/downloads/energia/Energia/energia-0101E0008-linux.tgz This one includes 32 bit binaries for msp430-gcc 4.6.3 and mspdebug I compiled on Ubuntu 11.04. -rick
  • Create New...