Search the Community

Showing results for tags 'JTAG'.

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


There are no results to display.

Found 9 results

  1. Hi Guys, I am a senior at an university. I am working on my senior design project which requires us to design our own PCB. I have decided to use MSP430FR2311 as our MCU and RC522(RFID) for our project. Does Energia support JTAG instead of microUSB? If we purchase MSP PROGRAMMER AND DEBUGGER, can we use Energia to program codes into the MCU? The main reason I want to use Energia because there are codes available to be used, so it would save me tons of time to design the codes for RFID RC522. Thank you so much!
  2. I am an absolute novice to all this but I have received a new firmware which I want to program into my electronic test instrument. I was told that this could be done by using a suitable software like FETPRO430 or UNIFLASH I bought the MSP-FET430UIF jtag interface and it has 4 connections GND, RST, VCC and TST , on the jtag layout on the circuit diagram for my device it has an 8 pin connector with 7 designated it has VCC and GND so they are self explanatory but it also has TDI, TDO, TNS, TCK and ANA_RST I would like to know how I interface the RST and TST on the jtag interface to the connections on the circuit board of my test instrument, i.e.which of the pins on the instrument do RST and TST connect too. The micro on the instrument is a MSP430F149 Thank you in advance for your help
  3. The CC1310 board option in Energia assumes that I am using the CC1310 Launchpad. The launchpad uses the CC1310F128RGZ, but I actually am using the CC1310F64RHBT. This means that the board is assuming it has more flash and RAM than it actually does. I want to edit the boards.txt file to match with the specs of my chip but I cannot find the correct numbers for my chip. There is also an issue with the pin mapping, because the F128RGZ has 48 pins while the F64RHBT has 32. Here the boards.txt for the CC1310 launchpad that needs to be adapted for the CC1310F64RHBT: menu.cpu=Processor LAUNCHXL_CC1310.vid.0=0x2341 w/ cc13xx EMT (48MHz) LAUNCHXL_CC1310.upload.maximum_size=16384 LAUNCHXL_CC1310.upload.maximum_ram_size=2560 LAUNCHXL_CC1310.upload.tool=dslite LAUNCHXL_CC1310.upload.protocol=dslite LAUNCHXL_CC1310.upload.maximum_size=131072 LAUNCHXL_CC1310.upload.maximum_data_size=8192 If anyone could help me adapt my boards.txt file or let me know where I can get these numbers, let me know. I have tried inputting 64kb for flash and the other appropriate values, but it didn't work because I assume the values have to line up perfectly with the chip's memory sectors and the memory map. Thanks, Cameron
  4. I'm trying to use a Launchpad 430 to program a board that has an MSP430G2553IRHB32R. I am doing this on a Windows 10 machine. I've removed the jumpers on the Launchpad and connected VCC and Ground to the other board. I've also connected RST and TEST pins. I created a simple blinky sketch which runs just fine with a stand alone Launchpad 430. However, when I attempt to program my custom board with the same code, I get the following error. MSP430_GetNumberOfUsbIfs MSP430_GetNameOfUsbIf Found FET: HID0003:COM5 MSP430_Initialize: HID0003:COM5 Firmware version is 20409001 MSP430_VCC: 3000 mV MSP430_OpenDevice tilib: MSP430_OpenDevice: Could not find device (or device not supported) (error = 4) tilib: device initialization failed the selected serial port tilib: device initialization failed does not exist or your board is not connected I have selected the MSP-EXP430G2553LP board and COM5. I cannot seem to get it to program my other board. I've tried several different USB cables. Used 2 different computers and 2 different Launchpads. I even attempted to program a different custom board that I had been able to program before. I'm using the latest version 18 of energia. Can somebody point me in the right direction as to how to solve this problem and be able to program my custom board? After that, does anybody know what I need to do to get the board.txt and pins file set up to work correctly with my 32 pin MSP430G2553... chip? Thanks for the help, Curtis
  5. Having a small collection of older F1xx and F4xx MSP430 devices, I've been looking for a convenient way to flash and debug them. The devices I have don't support Spy By Wire, so they require 4-wire JTAG. They also have their JTAG pins shared with other functions, so the test and reset pins have to be used to put them into JTAG mode. While I do have an Olimex parallel-port JTAG adapter, the computer I use most of the time has no parallel port. A Raspberry Pi running Debian Jessie and mspdebug with its gpio driver looked like a good option. Adding a patch to mspdebug so that the gpio driver supports the reset and test pins got it working. The patch is here: Now, I only need a Raspberry Pi Zero, Debian Jessie with the USB ethernet gadget configured on a micro SD card, a USB cable, and 7 jumper wires to flash and debug 4-wire JTAG MSP430 devices. The Pi Zero might be the lowest-cost 4-wire MSP430 JTAG debugger available! $ sudo ./mspdebug -j -d "tdi=3 tdo=2 tms=4 tck=17 rst=22 tst=27" gpio MSPDebug version 0.24 - debugging tool for MSP430 MCUs Copyright (C) 2009-2016 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. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. gpio tms= 4 gpio tdi= 3 gpio tdo= 2 gpio tck= 17 gpio rst= 22 gpio tst= 27 Starting JTAG JTAG_power on JTAG_connct led green JTAG ID: 0x89 Chip ID data: ver_id: 49f4 ver_sub_id: 0000 revision: 01 fab: 40 self: 0000 config: 00 Device: MSP430F44x Available commands: ! fill power setwatch_r = gdb prog setwatch_w alias help read simio blow_jtag_fuse hexout regs step break isearch reset sym blow_jtag_fuse hexout regs step break isearch reset sym cgraph load run verify delbreak load_raw save_raw verify_raw dis md set erase mw setbreak exit opt setwatch Available options: color gdb_default_port enable_bsl_access gdb_loop enable_fuse_blow gdbc_xfer_size enable_locked_flash_access iradix fet_block_size quiet Type "help <topic>" for more information. Use the "opt" command ("help opt") to set options. Press Ctrl+D to quit. (mspdebug) prog fet440_1.c.hex led green Erasing... led red led red Programming... Writing 74 bytes at 1100... led red led red Writing 32 bytes at ffe0... led red led red Done, 106 bytes total (mspdebug)
  6. Here's a heads-up for anyone that wants to use the external SPI flash memory on the SensorTag: it's not accessible while a debugger session is active. Unfortunately the pin on the SensorTag's CC2650 which outputs the SPI clock to the flash memory is also used as the JTAG TDI pin: While you're debugging using the Debug DevPack the CC2650 is unable to clock data out to the flash chip. That means the flash will just sit there doing nothing and the CC2650 will end up reading zeroes from the SPI bus. To use the flash you need to be certain that no JTAG communication is occurring during execution of your firmware. The easiest way to do this is just to disconnect the Debug DevPack and power the SensorTag from a coin cell or external power supply. Alternatively you can use the Debug DevPack to power the SensorTag, but then you have to follow this procedure: Load your updated firmware onto the SensorTag using the Debug DevPack (I just run it in the CCS debugger) Terminate the debug session once you reach the start of main() Disconnect the Debug DevPack from USB Detach the SensorTag from the DevPack Connect the Debug DevPack to USB Reattach the SensorTag to the Debug DevPack Be careful not to miss step 2, or the DevPack will resume JTAG communication when everything is connected up again. I found that out the hard way... Also, the order of the last two steps is to avoid an issue with powering up the Debug DevPack while it's connected to a SensorTag with no coin cell. The advantage of that is that you don't need a coin cell (I've drained two already...) This makes testing code that uses the flash really difficult, as there's no way to use the debugger. I've been using a combination of UART logging, LED flashes and beep codes from the onboard buzzer to keep track of where the code is up to. The other thing I'm doing is detecting whether the flash is available during startup and skipping the flash accesses if it's not there. That lets the rest of the code run in the debugger without problems. The command sequence I'm using to detect the flash is: Repeatedly send a Read Status Register command (0x05, 0x00) until the received BUSY flag is clear Send a Read Mode Reset command (0xFF, 0xFF) Send a Release From Power Down command sequence (0xAB, 0x00, 0x00, 0x00, 0x00) Flash is available if the device ID value 0x12 is received in the last byte of the Release From Power Down sequence This sequence is arranged to work irrespective of the state of the flash chip. If JTAG is active the code will immediately fall through step 1 (BUSY flag is zero), but the received device ID at step 4 will be zero too. Step 2 covers against any remote chance that the device has ended up in dual-SPI mode. Step 3 wakes the chip if it has been put in suspend, and returns the device ID regardless.
  7. Hi folks, I'm currently deciding on the layout of the debugging connectors. I have a couple of MSP430 controller boards, which I want to debug simultaneously, more or less. IEEE 1149.1 JTAG builds on a TDI-TDO daisy-chain from board to board to achive that. TI's CCS IDE supports that (I've heard so). The IEEE 1149.7 extension to this standard builds on a star-topology, where all the signals (TCK, TMS, TDI, TDO) are connected to all devices in parallel. Furthermore, the standard introduces a 2-wire variant (TI's spy bi-wire?), which I find quite attractive for this purpose. Here is the related document: Now the questions: Can I connect multiple controllers to the SBW-interface? Has anyone tried that before? Thanks in advance, Bass Mati
  8. Hi all I am new to TI environment, before this all of my projects were based on Arduino. I have developed one circuit with 5969 launchpad its working fine. Now I want to make it my own custom pcb for my application. I wanted to know by keeping two test pins for Spy Bi Wire on my pcb can I program my micro controller with help of my launch pad? And/Or which is best practice for ISP programming MSP430 micro controllers?
  9. 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