Search the Community

Showing results for tags 'firmware'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Calendars

There are no results to display.


Found 9 results

  1. Good morning (or good evening)! First of all, if these questions are stupid, don't spare my feelings. I know better than anyone that I'm still new at this and I have thick skin. I've had a great deal of success writing my own sketches with Energia. It's fun, simple-to-use, and easy to explain to others, but I have a few questions: 1) is Energia suitable for firmware in a small commercial product or is it intended more as a rapid prototyping framework, with "permanent" firmware written in CC7? 2) When working with a PCB using the CC3200MOD, how would I flash my Energia sketch onto the modules flash? 3) If I were to have a few hundred PCBs produced for a task at my day job, would each PCB (using the CC3200MOD) have to be individually flashed by hand or is there a way to have this done during the assembly process? For a small project like this, I don't feel that having a PCB designer work out a PCB trace antenna would be cost effective - plus my boss would want to avoid FCC issues at all costs - so the MOD version would clearly be better. I just don't know enough (yet) to know if the MOD version can be used in mass production, even on a small scale. Again, as I said, I've had SO much fun with Energia! I would like to thank Robert Wessels for making this experience possible. I feel like I could make every device and every toy that I've ever thought would be cool, by using Energia with the TI CC3200 platform. This is so cool!
  2. I've been searching for the Wi-Fi SensorTag firmware. Has anyone see it on TI's wiki or tool site? I just received mine. It works seamlessly, but I wanted to play around with the firmware a little.
  3. Hello , my problem is , energia msp432 pin mapping allows 2 serial ports. Serial and Serial1. and msp432 have a 4 hardware serial ports. so i want to add one more serial port to the msp432 energia firmware. i open a topic e2e.ti.com but they didn't answer yet. so maybe somebody help me here. https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/444248 in energia ide , msp432 hardware serial pins are p1_2,p1_3 and p3_2,p3_3. but msp432p401r also have a two more hardware serial ports. p2_2,p2_3 and p9_6,p9_7. if we look at the hardwareSerial.cpp file , last 2 lines HardwareSerial Serial(0); HardwareSerial Serial1(1); and if we look hardware\msp432\variants\MSP_EXP432P401R\board_init.c file there is just 2 uart implemented with ti driverlib. but if we write Board_init.c: Board_initUART function like /* Set P1.2 & P1.3 in UART mode */ MAP_GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P1, GPIO_PIN2 | GPIO_PIN3, GPIO_PRIMARY_MODULE_FUNCTION); /* Set P3.2 & P3.3 in UART mode */ MAP_GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P3, GPIO_PIN2 | GPIO_PIN3, GPIO_PRIMARY_MODULE_FUNCTION); /* Set P2.2 & P2.3 in UART mode */ MAP_GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P2, GPIO_PIN2 | GPIO_PIN3, GPIO_PRIMARY_MODULE_FUNCTION); and i also add other uart definations to above the Board_initUART function. but thats not working. so i discovery something. if we just delete something in board_init.c file , purpose of syntax error. like i am deleting ";' charecter one line of code , energia still compile the sketch. so energia doesn't compile board_init.c file. and i don't know how to compile it. there is makefile file but its not working for me. and i am bad compiling things. so how i can edit energia msp432 hardware/firmware ? do you have a any idea ? thanks cevat Cevat Bostancioglu
  4. Hello! I recently bought a MetaWatch FRAME, with the intention of messing around with it as an inexpensive, portable MSP development platform. Meta open-sourced the watch's firmware and *used* to sell JTAG programming clips for the watch. Now, however, they've discontinued both my model of watch and its programming clips, and I'm out some cash on a less-than-fully-functional smartwatch. The watch uses an MSP430F5438A microcontroller and is programmable using the Spy-Bi-Wire protocol, according to this SparkFun teardown. I found the sticky post about programming MSPs with Launchpads, but I was wondering if anyone had tried programming a F5438A (or a complete MetaWatch, for that matter) with one. I'm new to the MSP chips, so if anyone had any suggestions I'd greatly appreciate it. Thanks, John
  5. Hi there! I wanted to do a temperature logger with my chronos ez-430. Everything worked fine, and I installed the DataLog firmware (correct frequency). After that I wasn't able to communicate with the watch anymore. Wireless update still works, but on the normal firmware i can't sync, yust like with datalog firmware. do you have any suggestions on how to solve this? thanks, Jonas Otto
  6. Updated Firmware 1.26 for CC3000 SimpleLinkWiFi Boosterpack Warning!!! You do this on your own risk! If you brick your CC3000 its not my fault! This file replaces the fw_patch.h in <energia_install_folder>\hardware\msp430\libraries\SimplelinkWifi\utility - Load the Simplelinkwifi Example: CC3000FirwareUpdate - you might need to Edit the Pins for the Boosterpack in the Sketch if you are using a different platform. - and start the Sketch. Warning!!! You do this on your own risk! If you brick your CC3000 its not my fault! This worked for me on Tiva-C Launchpad with CC3000 Boosterpack. Changes i've noticed yet: mdnsAdvertiser(...) - correctly advertises the Servicename instead of "target.local" regards, Nick fw_patch.h
  7. I'm developping some codes with Energia or TI CCS for the TI LaunchPad MSP-EXP430G2, v1.4 and v1.5, with G2553 and G2452 chips. I organize DIY workshops. I'm playing with various computers, I enumarate them: 1x W7Pro32, 1x W7Starter, 1x W8.1x64, 1x TP-Link TL-MR3020+OpenWrt, 1x TP-Link WR710N+OpenWrt. Nothing is going right with serial, only my old W7Pro32 can read/write thru the USB serial ! Even my 2 OpenWrt TP-Link can't communicate ! If I play with some Arduino in place of TI LaunchPad, all USB serial is working fine (except the known reset problem of Arduino USB serial). Yesterday evening, I played a lot with a TI LaunchPad and my W8.1x64. I discovered that sometimes, the serial USB could communicate ! That's after a lot of stress of the serial settings. I used PuTTY to receive something. The G2553 program was continualy sending 1 character every second. After changing the "Flow control" in PuTTY/Settings/Connection/Serial a lot of times, changing from XON/XOFF to RTS/CTS to /DTR/DSR, in any order, and typing a lot of ^S,^Q,... sentences, the TI Launchpad would finally communicate ! As soon as the USB serial communicates, I can deselect the "Flow control" (can be any) to "none". But never unplug the USB else... What is wrong in the firmware ?
  8. When the Launchpad was quite new, TI published an Launchpad update program that would make it work with new (at the time) microcontrollers. But sometimes, the update failed, leaving me and others with a useless launchpad. http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update (BEWARE!) This has been discussed here (43oh.com) and elsewhere http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/p/97931/346074.aspx#346074 and someone in that thread was kind enough to backup his/her Launchpad's firmware: http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/166/3060.LP100901938.zip Today I stumbled across my defunct launchpad and looked into MSP430 parallel port JTAG adapters (it seems, only the level conversion is required) and others (Versaloon may be portable to STM32_F4_Discovery), bit banging with FT2xxx, etc., but ended up looking for the effort required using the integrated serial bootloader (BSL): http://www.mike-stirling.com/2013/06/turn-a-ti-launchpad-into-a-goodfet-with-just-a-serial-cable/ This is really quite simple (you'll have to decide if your time is worth it, if you haven't thrown it away already..): the process only requires a 3.3 V serial interface, soldering of 5 wires, pushing a few buttons.. Since he's actually replacing the F1612's firmware with another one, I'll just qoute the BSL info for posterity:
  9. I'm new to 43oh, but I've read threads here a number of times and it has been a great reference. I wanted my own application board with a built-in programmer, so I designed the application board, and used the launchpad schematics (v1.4, I believe) as the programmer. I have printed the board and populated it. I've been looking around, and I am not actually sure how to program the firmware onto the board. I know that TI has its "firmware updater," but I think this requires that the board already has firmware loaded onto it. The programming portion of the launchpads have a programmer MSP430 and an EEPROM. I would be more or less comfortable programming the MSP430 (at the very worst, by using a pre-built Launchpad), but I'm not sure if there is anything special I need to do to program the EEPROM. I see that some people have made their own launchpads (links below), but they make no mention of loading the firmware. Is there a guide to how to load the firmware onto the Launchpad from scratch, or could someone give me some pointers? Any help would be appreciated. Thanks! http://forum.43oh.com/topic/1605-diy-proto-launchpad/ http://forum.43oh.com/topic/1599-diy-mini-launchpad/