Search the Community

Showing results for tags 'cc430'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • Community Calendar

Found 8 results

  1. Hello Folks, Here is Malkiat Singh from Punjab India.This forum has been doing a suberb job and lot of great topics enlighting various aspects on Low-power microcontrollers. I was reading " What's left for MSP430?" and decided to join a forum. Wonderful job by you guys. Currently, I am making various agro-based sensors and scratching web and 43oh.
  2. hi, i have also facing the ROM_OVERFLOW issue....: /msp430-elf/bin/ld: region `ROM' overflowed by 29894 bytes....... my .ld file contains like this.......... MEMORY { SFR : ORIGIN = 0x0000, LENGTH = 0x0010 /* END=0x0010, size 16 */ PERIPHERAL_8BIT : ORIGIN = 0x0010, LENGTH = 0x00F0 /* END=0x0100, size 240 */ PERIPHERAL_16BIT : ORIGIN = 0x0100, LENGTH = 0x0100 /* END=0x0200, size 256 */ RAM : ORIGIN = 0x1C00, LENGTH = 0x0FFE /* END=0x2BFD, size 4094 */ INFOMEM : ORIGIN = 0x1800, LENGTH = 0x0200 /* END=0x19FF, size 512 as 4 128-byte segments */ INFOA : ORIGIN = 0x1980, LENGTH = 0x0080 /* END=0x19FF, size 128 */ INFOB : ORIGIN = 0x1900, LENGTH = 0x0080 /* END=0x197F, size 128 */ INFOC : ORIGIN = 0x1880, LENGTH = 0x0080 /* END=0x18FF, size 128 */ INFOD : ORIGIN = 0x1800, LENGTH = 0x0080 /* END=0x187F, size 128 */ ROM (rx) : ORIGIN = 0x8000, LENGTH = 0x7F80 /* END=0xFF7F, size 32640 */ VECT1 : ORIGIN = 0xFF80, LENGTH = 0x0002 VECT2 : ORIGIN = 0xFF82, LENGTH = 0x0002 VECT3 : ORIGIN = 0xFF84, LENGTH = 0x0002 VECT4 : ORIGIN = 0xFF86, LENGTH = 0x0002 VECT5 : ORIGIN = 0xFF88, LENGTH = 0x0002 VECT6 : ORIGIN = 0xFF8A, LENGTH = 0x0002 VECT7 : ORIGIN = 0xFF8C, LENGTH = 0x0002 VECT8 : ORIGIN = 0xFF8E, LENGTH = 0x0002 VECT9 : ORIGIN = 0xFF90, LENGTH = 0x0002 VECT10 : ORIGIN = 0xFF92, LENGTH = 0x0002 VECT11 : ORIGIN = 0xFF94, LENGTH = 0x0002 VECT12 : ORIGIN = 0xFF96, LENGTH = 0x0002 VECT13 : ORIGIN = 0xFF98, LENGTH = 0x0002 VECT14 : ORIGIN = 0xFF9A, LENGTH = 0x0002 VECT15 : ORIGIN = 0xFF9C, LENGTH = 0x0002 VECT16 : ORIGIN = 0xFF9E, LENGTH = 0x0002 VECT17 : ORIGIN = 0xFFA0, LENGTH = 0x0002 VECT18 : ORIGIN = 0xFFA2, LENGTH = 0x0002 VECT19 : ORIGIN = 0xFFA4, LENGTH = 0x0002 VECT20 : ORIGIN = 0xFFA6, LENGTH = 0x0002 VECT21 : ORIGIN = 0xFFA8, LENGTH = 0x0002 VECT22 : ORIGIN = 0xFFAA, LENGTH = 0x0002 VECT23 : ORIGIN = 0xFFAC, LENGTH = 0x0002 VECT24 : ORIGIN = 0xFFAE, LENGTH = 0x0002 VECT25 : ORIGIN = 0xFFB0, LENGTH = 0x0002 VECT26 : ORIGIN = 0xFFB2, LENGTH = 0x0002 VECT27 : ORIGIN = 0xFFB4, LENGTH = 0x0002 VECT28 : ORIGIN = 0xFFB6, LENGTH = 0x0002 VECT29 : ORIGIN = 0xFFB8, LENGTH = 0x0002 VECT30 : ORIGIN = 0xFFBA, LENGTH = 0x0002 VECT31 : ORIGIN = 0xFFBC, LENGTH = 0x0002 VECT32 : ORIGIN = 0xFFBE, LENGTH = 0x0002 VECT33 : ORIGIN = 0xFFC0, LENGTH = 0x0002 VECT34 : ORIGIN = 0xFFC2, LENGTH = 0x0002 VECT35 : ORIGIN = 0xFFC4, LENGTH = 0x0002 VECT36 : ORIGIN = 0xFFC6, LENGTH = 0x0002 VECT37 : ORIGIN = 0xFFC8, LENGTH = 0x0002 VECT38 : ORIGIN = 0xFFCA, LENGTH = 0x0002 VECT39 : ORIGIN = 0xFFCC, LENGTH = 0x0002 VECT40 : ORIGIN = 0xFFCE, LENGTH = 0x0002 VECT41 : ORIGIN = 0xFFD0, LENGTH = 0x0002 VECT42 : ORIGIN = 0xFFD2, LENGTH = 0x0002 VECT43 : ORIGIN = 0xFFD4, LENGTH = 0x0002 VECT44 : ORIGIN = 0xFFD6, LENGTH = 0x0002 VECT45 : ORIGIN = 0xFFD8, LENGTH = 0x0002 VECT46 : ORIGIN = 0xFFDA, LENGTH = 0x0002 VECT47 : ORIGIN = 0xFFDC, LENGTH = 0x0002 VECT48 : ORIGIN = 0xFFDE, LENGTH = 0x0002 VECT49 : ORIGIN = 0xFFE0, LENGTH = 0x0002 VECT50 : ORIGIN = 0xFFE2, LENGTH = 0x0002 VECT51 : ORIGIN = 0xFFE4, LENGTH = 0x0002 VECT52 : ORIGIN = 0xFFE6, LENGTH = 0x0002 VECT53 : ORIGIN = 0xFFE8, LENGTH = 0x0002 VECT54 : ORIGIN = 0xFFEA, LENGTH = 0x0002 VECT55 : ORIGIN = 0xFFEC, LENGTH = 0x0002 VECT56 : ORIGIN = 0xFFEE, LENGTH = 0x0002 VECT57 : ORIGIN = 0xFFF0, LENGTH = 0x0002 VECT58 : ORIGIN = 0xFFF2, LENGTH = 0x0002 VECT59 : ORIGIN = 0xFFF4, LENGTH = 0x0002 VECT60 : ORIGIN = 0xFFF6, LENGTH = 0x0002 VECT61 : ORIGIN = 0xFFF8, LENGTH = 0x0002 VECT62 : ORIGIN = 0xFFFA, LENGTH = 0x0002 VECT63 : ORIGIN = 0xFFFC, LENGTH = 0x0002 RESETVEC : ORIGIN = 0xFFFE, LENGTH = 0x0002 BSL : ORIGIN = 0x1000, LENGTH = 0x0800 } so ,how should i add .far_rom regeion?....
  3. Does Energia support CC430 Devices? If yes Plz help me on this... Thanks in advance.
  4. Dear colleagues, I'm more than happy to announce the release of panStamp NRG, our new Wireless ISM (868/915 MHz) module based on the CC430F5137 MCU and programmable from the Arduino 1.5 IDE. panStamp NRG is pin, radio and software compatible with our classic AVR modules but entirely relies on a Texas Instruments CC430F5137 MCU instead of our old Atmega + CC1101 approach. As result, we are getting a more robust module providing more features, more speed and consuming less power. Wiki page Commercial website Webstore panStamp NRG can be programmed serially from the Arduino IDE or even wirelessly from our Python tools. All related to panStamp is open source, including hardware designs, cores, libraries and software tools so our users don't need to invest in development toolchains or configuration applications. We also provide sample applications, an open protocol called SWAP and software IP gateway to start deploying WSN (Wireless Sensor Networks) and developing IoT applications from the first day. Another nice feature of NRG is that it can host multiple sensors on-board. There is then no need to develop or buy additional boards for measuring temperature, humidity or 3-axis acceleration since all these sensors can be hosted by this tiny module. Simply grab your application, power the module from a 3V coin battery and display the readings from any of the software applications compatible with panStamp. panStamp NRG is already on sale and we are offering a 15% discount in all our products for the members of the 43oh community until 15 January 2015. You just have to fill your cart and send us an e-mail asking for the discount before completing the payment.
  5. Hi everyone, I'm working on Energia CC430 support. It's the first time I do this kind of work, it allowed me to understand a lot of things but not everything of course So I have a lot of questions ! So for now where I am : I'm working on a eZ430 - Chronos 433 mhz (==> CC430F6137). I program it with the ez430 USB stick (I will see later for upload using radio BSL). For now I just tried to get something working, I made a pin_energia.h creating a new MSP430 variant. I edited the board.h and I had to modify wiring.c to get the clock system working : Original line 168 : #if defined(__MSP430_HAS_UCS__) Modified to : #if defined(__MSP430_HAS_UCS__) || defined(__MSP430_HAS_UCS_RF__) I used some function from the eZChronos firmware provided by TI to test if the system was running, here is the code : Upload using Energia integrated in CCS v6 ==> IT WORKS the heart on the LCD is beating ! Now I am trying to understand if my modification of wiring.c is enought, and if other Energia features are OK. All files are here : Now my questions : 1) What is interesting me the most is the radio core. TI provides some interesting low level libraries I can re-use, but I don't know how to integrate it directly in the core. I plans to work on others features like LCD_B, AES ... I think it would be better to directly integrate it and to do not have to add a library each time. 2) I found some defines in msp430's pins_energia.h : #define TWISDA_SET_MODE (PORT_SELECTION0 | PORT_SELECTION1 /* | INPUT_PULLUP*/) /* do not enable the pull ups for this device */ #define TWISCL_SET_MODE (PORT_SELECTION0 | PORT_SELECTION1 /* | INPUT_PULLUP*/) #define DEBUG_UARTRXD_SET_MODE (PORT_SELECTION0 | PORT_SELECTION1 | INPUT) #define DEBUG_UARTTXD_SET_MODE (PORT_SELECTION0 | PORT_SELECTION1 | OUTPUT) #define SPISCK_SET_MODE (PORT_SELECTION0 | PORT_SELECTION1) #define SPIMOSI_SET_MODE (PORT_SELECTION0 | PORT_SELECTION1) #define SPIMISO_SET_MODE (PORT_SELECTION0 | PORT_SELECTION1) #define DEBUG_UART_MODULE_OFFSET 0x0 I don't really understand what they mean ... 3) How the PMAP is used in Energia ? I found a PMAP maping in fraunchpad pins_energia.h but I did not found where it's used. 4) I just need a confirmation : function "const uint8_t digital_pin_to_timer[]" is used to define pins PWM compatible ? 5) In wiring.c init() : /* Clear P2.6 and P2.7 bits to default to GPIO */ #ifdef P2SEL2 P2SEL &= ~(BIT6|BIT7); #endif Why this lines ? Thanks !
  6. Hi everybody, I find the Energia very very cool project, and i'm very new user of it, so bare with me if the questions sound stupid. I would like to know if anyone of you has some experience with Energia using MSP430-JTAG-TINY-V2 for program a CC430F513. If not which will be the most "compatible way for Energia" to communicate with the CC430. I do have also a ez430 usb programmer the i've got with the ez-chronos watch, would be that a better option? Which one whould you suggest? Thank you in advance
  7. I noticed that the users' guide was recently updated, so I took a look. About 14-18 months ago, I did some work on a 5509 + CC1101 USB stick that was a poorly-kept secret. It seems as though TI finally got the bugs out of the board and started replenishing their Chronos kits with it. In the users' guide, TI refers to the old kits as "BLACK" and new kits as "WHITE". Of course, it is the silkscreen they are talking about, but the boards are entirely different. Anyway, I would make sure to get the WHITE Chronos. The BLACK RF Gateway uses a CC1111, which is an 8051 core with an entirely different toolchain. The WHITE one can use the normal MSP430 toolchain. The 5509 is better than the CC1111 is terms of power (8051 is slow and has poor code density), but it is still a bit anemic (24KB/6KB). I can't really figure why they didn't use the 5503, considering that the ADC is unused, but I guess TI probably makes more 5509s, so it is easier for them to source (just guessing). Last year when I was working on this kit, I did manage to squeeze a full server build of OpenTag on it. I don't think other cool stacks (namely Contiki) can fit, but it might be worth a shot. In any case, it's a lot more hackable than the old kit was.
  8. I've been working on a Chronos altimeter app. But after some code changes suddenly my Chronos is not recognized by the FET. I got another, same story - programmed my code and it is bricked. I did not change the BSL address (so it should not be locked). The hex file of the code that kills the cc430f6137: Here is the session whewre I flash it and the part dies. It should not be a complier issue, since no opcode shoudl disable debugging, but in case it matters: mspgcc to compile&link, mspdebug to program the code. I verified that the FET is functional byt trying it with another chronos as well as this one before it bricked. I verified the chronos is bricked b y trying it with other FETs. Ideas? mspdebug rf2500 "prog ChronosAlt.hex" MSPDebug version 0.21 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 Daniel Beer <> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open interface 1 on 020 rf2500: warning: can't detach kernel driver: No data available Initializing FET... FET protocol version is 30001000 Set Vcc: 3000 mV Configured for Spy-Bi-Wire Device ID: 0x6137 Code start address: 0x8000 Code size : 32768 byte = 32 kb RAM start address: 0x1c00 RAM end address: 0x2bff RAM size : 4096 byte = 4 kb Device: CC430F6137 Number of breakpoints: 3 fet: FET returned NAK warning: device does not support power profiling Chip ID data: 61 37 12 Erasing... Programming... Writing 4096 bytes at c800... Writing 2576 bytes at d800... Writing 48 bytes at ffd0... Done, 6720 bytes total dmitrygr@vwm64:/mnt/hgfs/D/msp430/Chronos-Altimeter$ mspdebug You need to specify a driver. Try --help for a list. dmitrygr@vwm64:/mnt/hgfs/D/msp430/Chronos-Altimeter$ mspdebug rf2500 MSPDebug version 0.21 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 Daniel Beer <> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open interface 1 on 020 rf2500: warning: can't detach kernel driver: No data available Initializing FET... FET protocol version is 30001000 Set Vcc: 3000 mV Configured for Spy-Bi-Wire fet: FET returned error code 11 (Could not reset device) fet: command C_IDENT1 failed fet: identify failed Trying again... Initializing FET... FET protocol version is 30001000 Set Vcc: 3000 mV Configured for Spy-Bi-Wire Sending reset... fet: FET returned error code 11 (Could not reset device) warning: fet: reset failed fet: FET returned error code 11 (Could not reset device) fet: command C_IDENT1 failed fet: identify failed dmitrygr@vwm64:/mnt/hgfs/D/msp430/Chronos-Altimeter$