Jump to content

Alan

Members
  • Content Count

    56
  • Joined

  • Last visited

  1. I was looking at the 32L152CDISCOVERY board (order code STM32L152C-DISCO) which handily comes with an LCD, and I seen a few similarly priced F versions as well after your suggestion (STM32F3DISCOVERY,STM32F4DISCOVERY ) . I know that you praise them pretty highly in your post: http://forum.43oh.com/topic/3416-stm32l-vs-msp430f5-whats-left-for-msp430/. I would be curious to hear what your (and others) thoughts on using these chips were? While they seem to pack more punch that the MSP430F5529, my concerns would be the ease of development (datasheets, header files, example code etc) and community support. I hear the latter, at least in terms of forums etc isn't particularly great (http://forum.43oh.com/topic/1039-web-site-blog-like-43oh-for-stm32/) I guess it may be good to have some ARM experience on the old CV ;-)
  2. I believe at the moment, WiFi is more or less a requirement. Not too sure what you are referring to though with your suggestion. Use a simple protocol for the sensors and potentially have a controlling "base station" to put them onto the internet? Out of curiosity how does the USB gateway fit in? The base station communicates to PC over USB? I had considered Bluetooth LE, as its a relatively new technology and Ive seen some pretty low power transceivers, but as I said previously I believe it has to be WiFi currently.
  3. I was considering even a value line 2553 launchpad, but I think Id need more memory - I'd like room to expand the project the project if needs be. Thinking perhaps porting arduino twitter libraries at the moment.
  4. Ideally, but I'm not sure I have the time available to become familiar enough with both to then make a decision. I guess when I choose one, I could attempt to abstract from the HW enough to try and make swapping out the MCU an option should something crop up, but that's easier said than done.
  5. Yea, I have done some rough calculations, and the ~250 mA of the CC3000 will likely dwarf the MCU current. So as long as the MCU supports a decent low power mode a few mA here or there when active should not be a concern. The device will likely wake from sleep periodically to report data, and perhaps poll a server for instructions to keep current consumption low (rather than always be in an rx mode). I considered the Tiva C LP for this as well but glancing over current consumptions I thought they were perhaps a bit too high and its improved processing / instruction set perhaps doesn't compensate in this application as I do not imagine it will be processing large amounts of data.
  6. Hi guys, For my final year project I'm going to be doing some embedded development related to "the internet of things". The specs aren't fully formed yet but it'll be mcu+sensors+wifi+maybe some actuators. At the moment I've been doing some research on components, and was wondering if I could get some of your input? So for wifi connectivity I'm looking at the CC3000 and RN-171, and currently favouring the CC3000. I was wondering if anyone worked with either of these chips, and what they thought about them? My big question involves choosing a microcontroller (ideally a development board initially). The final application will likely be battery powered, so low power is a must. Sensors etc need some a/d, and since it is wifi enabled I would like a reasonable amount of RAM/Flash to experiment with. Currently, since I have some experience with the value line series, I'm considering the MSP430F5529 board since it seems to have ample resources. I was wondering if anyone could weigh in with thoughts/ ideas/ suggestions? I've also been looking into the STM32LVDISCOVERY board, but have seen a few complaints with about the quality of resources (libraries etc) available for it. I know this forum might be biased towards the MSP430 but I'm posting in other micros hoping to get the opinions of those who have worked with other brands, but all feedback is welcomed :grin: (Its not a major issue for me, but when it comes to development I tend to prefer working in Linux and avoiding the use of an IDE, so any chips with compilers that support Linux would be a bonus )
  7. CCS for GNU/Linux does support MSP430 to my knowledge. Last time I installed it, it unfortunately didn't. You could give msp-gcc a go. You can get it from the Ubuntu Software Center (though there are a few small issues) and works well for me. Alternatively you can always get the newest version from source. I find it a better environment for programming. It has by default some pretty good command line tools for dealing with text and documents - grep, sed,find. I am also a fan of Git. Though a lot of this I am sure is available with an IDE such as Eclipse I tend not to be a huge fan of them. I have never properly used Cygwin for programing (I tend to use Xubuntu more than Windows anyways so haven't taken the time to test it out) but from what I hear it probably covers all of the above assuming msp-gcc can work through it.
  8. Sorry I have never went through the debian site before, I'm happy apt-get'ing from the command line. Did you install all the packages on the debian page? including http://packages.debian.org/sid/zlib1g for example?. The only thing I can think of is you missed a dependency which ubunutu bundled into the install for me. Also I am not too sure what msp430mcu-config is as I don't seem to have a binary for it - at least in my PATH.
  9. Alan

    MSP430G2553 I2C

    That is decimal 12 not hex (0x12) so its 1 Mhz / 12 which is slightly less than 100 Khz. This code is stolen from the TI example in fairness but looking at the datasheet: " Clock prescaler setting of the Baud rate generator. The 16-bit value of (UCAxBR0 + UCAxBR1
  10. Sounds like your linker is having some issues. If you look for "msp430" in the ubuntu software centre, or in the link you previous posted and make sure you install all the packages. The linker is in binutils which can be installed with a sudo apt-get install binutils-msp430 you should also install sudo apt-get install msp430-libc sudo apt-get install gcc-msp430 sudo apt-get install msp430mcu sudo apt-get install gdb-msp430 sudo apt get install mspdebug However I have some issues with gdb - haven't successfully got it working with the launchpad. GDB isn't too necessary but if you have used it before it allows debugging through C code. mspdebug allows for flashing and debugging but its in assembly.
  11. When I copied the makefile source from the page it left a single space at the start of every line. Makefiles use tabs to distinguish a block of code under a target so its complaining about this. You'll have to remove all them spaces to get it going. (The link is here is anyone is curious http://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Example:Makefile) If you are new to makefiles that example might be a bit too convoluted to start with. Here is a simpler example if you prefer. Its not as universal as the example provided but hopefully shows just enough to give you a basic overview. https://github.com/alanbarr/msp430-launchpad/blob/master/examples/switchLeds/makefile https://github.com/alanbarr/msp430-launchpad/blob/master/examples/switchLeds/main.c
  12. Alan

    MSP430G2553 I2C

    Hmm I actually just noticed a potential issue with my code. I still have the clock freq hardcoded: UCB0BR0 = 12; // fSCL = SMCLK/12 = ~100kHz So as long as your clock is 1MHz this will be ok and give you ~100 kHz. So my I2C code doesn't actually use time430.h. - just my example. Its something I'll change in the future. The point of this header file is to globally define the clock speed in a macro which can be used in some calibration and delay macros which are defined in this header file. If you are looking at my example and you have used TIME430_CALIBRATE_CLOCK() you can switch this for the standard DCO macros to calibrate 1Mhz. If you have used TIME430_DELAY_MS() you will have to replace it with an appropriate _delay_cycles call. If you use my header you need to #define TIME430_CLOCK_FREQ to 1 before you #include the header - either in your makefile OR right before you include it e.g. #define TIME430_CLOCK_FREQ 1 #include "time430.h" If you look at the file https://github.com/alanbarr/msp430-launchpad/blob/master/common/inc/time430.h you can see whats going on
  13. Alan

    MSP430G2553 I2C

    I've modified TIs code and split it into functions. Its been a while since I have looked at it admittedly but hopefully the following files might be useful to you. I wrote it for mspgcc there might be some issues with using it with CSS / IAR mainly the interrupts will need changed. The register setups will be the same though. I2C: https://github.com/alanbarr/msp430-launchpad/blob/master/common/src/i2c.c https://github.com/alanbarr/msp430-launchpad/blob/master/common/inc/i2c.h Example: https://github.com/alanbarr/msp430-launchpad/blob/master/examples/i2cBitExp4Leds/main.c
  14. Ah PWM will be a problem. I hope someone will correct me if I am wrong since it has been a while since I looked at Timer A in detail but I think TA0.0 is only compare register 0, which is generally what sets the period of the PWM wave. For PWM you need both compare 0 and 1
  15. You need to consult the port schematics section (page 41 onwards) of the msp430g2553 datasheet. Pin 1.5 has TA0.0 functionality when P1DIR and P1SEL bits high. Pin 1.4 doesn't have any Timer A functionality.
×
×
  • Create New...