Jump to content
43oh

New MSP430F5529 USB Launchpad Released


Recommended Posts

G'Day,

How can I get my hands on this device. Have tried the TI site  http://www.ti.com/tool/MSP-EXP430F5529LP#buy but  "Buy from TI" button takes me nowhere, plus the "Buy from distributor" has the additional expense of fed-ex postage.

Does this mean I have to wait awhile due to availability, or is it because am placing an order from Australia?

Tks

 

 

Link to post
Share on other sites
  • Replies 119
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Alright so, I had to keep a zip on it til now but since it's released... I had early access to one of these (thanks to the TI folks!) and got to play with it a little ahead of time.  I'm going to dump

Did you guys notice TI's selling their new MSP430F5529 USB Launchpad board? I found an old announcement back in 2012 on 43oh main page that TI's working on it but haven't seen any on it being sold. I

If anyone is planning a CC1200 (or CC11xx) booster pack for this, let me know. I'll support it. I've already done considerable work with the EXP-5529 board + CC110x, and I'll happily port to 5529-LP.

Posted Images

Hi guys. Here are my first experiences with MSP-EXP430F5529LP:

 

1.

I tested it only as an external programmer to program an MSP430G2553 (located in  MSP-EXP430G2 launchpad) with  CCS5.5.

 

I connected the two boards with: GND, VCC(3V3), SBW_RST, SBW_TST wires. 

 

At the beginnig CCS warned me that the eZ-FET lite emulator firmware was outdated and need to be updated. I pressed the update button. The update took less than one minute. After the update CCS programmed the MSPG2553 with the eZ-FET lite emulator. It seemed that the uploading was faster than with the emulator of the MSP-EXP430G2 launchpad.

 

 

2.

I tried to use FET-Pro430 Lite (latest verison I found: 3.10) to read the memory content of the MSP430G2553 with the eZ-FET lite emulator. It didn't work me with default settings. (I think the msp430.dll comes with the FET-Pro430 Lite software was too old). In the "Setup->Connection/Device Reset" menu I browsed path of a fresh (3.3.1.4) msp430.dll. (the eZ-FET lite requires 3.3.0.6 or higher). Then everything was OK. Reading the memory content took 1.9 sec.

 

I did the same with the emulator of the MSP-EXP430G2 launchpad: reading took 5.9 sec.

Link to post
Share on other sites
I tried to use FET-Pro430 Lite (latest verison I found: 3.10) to read the memory content of the MSP430G2553 with the eZ-FET lite emulator. It didn't work me with default settings. (I think the msp430.dll comes with the FET-Pro430 Lite software was too old). In the "Setup->Connection/Device Reset" menu I browsed path of a fresh (3.3.1.4) msp430.dll. (the eZ-FET lite requires 3.3.0.6 or higher). Then everything was OK. Reading the memory content took 1.9 sec.

 

I did the same with the emulator of the MSP-EXP430G2 launchpad: reading took 5.9 sec.

 

If you was reading full 56 KB flash, than it's slower than my standard SBW quick read, that is about 46 KB/s.

 

http://forum.43oh.com/topic/2972-sbw-msp430f550x-based-programmer/?p=31159

Link to post
Share on other sites

If you was reading full 56 KB flash, than it's slower than my standard SBW quick read, that is about 46 KB/s.

 

http://forum.43oh.com/topic/2972-sbw-msp430f550x-based-programmer/?p=31159

 

Sorry, I was wrong, because FET-Pro430 displayed  "run time" and not "reading time". I think "run time" > "reading time".

Here is an another test: eZ-FEt lite MSP430F5529 128 KB flash memory reading "run time" : 10.9 sec

post-30759-0-29204600-1382185737_thumb.png

Link to post
Share on other sites

Sorry, I was wrong, because FET-Pro430 displayed  "run time" and not "reading time". I think "run time" > "reading time".

Here is an another test: eZ-FEt lite MSP430F5529 128 KB flash memory reading "run time" : 10.9 sec

 

There is no big difference between run/reading time, especially on big interval like 10 seconds. Reading 128 KB in 10 seconds (for me) is very slow. My standard 2-wire SBW quick read for 192 KB will take 5 seconds. And this is for reading from 8 target devices at once. Reading just from 1 target device will be much faster.

Quick Read
Address: 05C00  Words: 98304
Size: 196608 bytes  Time: 5000 ms  Speed: 38,40 KB/s
Link to post
Share on other sites

Finally uncrated my MSP430F5529LP, rebuilt MSPDebugStack from SLAC460F, updated mspdebug.

 

It takes seventeen seconds from typing "mspdebug ezfet" before I get a prompt, while it resets this and that, checks these and those, reads the other, and finally configures itself.

 

Really?  17 seconds?  Did I build something wrong in the mspdebug toolchain, or is this how it's going to be with the ezfet?  The rf2500 to the Fraunchpad takes under one second to figure itself out.  The FET-430UIF under tilib to a F5438A board takes about three seconds.

 

I may have to change my workflow to keep mspdebug running permanently.

Link to post
Share on other sites

I have only used mspdebug tilib with the new LP and it takes about 3 seconds like you said.

 

Thanks.  I'd tried tilib earlier but it wanted to do a firmware update, and I thought I saw somebody say they'd bricked their device that way.  But I tried it, and so did I: update failed, and the USB device ID changed from:

Bus 002 Device 014: ID 2047:03fe Texas Instruments
Bus 002 Device 015: ID 2047:0013 Texas Instruments
Bus 002 Device 013: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub

to:

Bus 002 Device 042: ID 2047:03fe Texas Instruments
Bus 002 Device 043: ID 2047:0203 Texas Instruments
Bus 002 Device 041: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub

However, I tried again as root (my udev rules grant write permission to 2047:0013, not 2047:0203), and after doing it twice it took and now it works with both ezfet (17 seconds) and tilib (3-4 seconds).

Link to post
Share on other sites

Thanks.  I'd tried tilib earlier but it wanted to do a firmware update, and I thought I saw somebody say they'd bricked their device that way.  But I tried it, and so did I: update failed, and the USB device ID changed from:

Bus 002 Device 014: ID 2047:03fe Texas Instruments
Bus 002 Device 015: ID 2047:0013 Texas Instruments
Bus 002 Device 013: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub

to:

Bus 002 Device 042: ID 2047:03fe Texas Instruments
Bus 002 Device 043: ID 2047:0203 Texas Instruments
Bus 002 Device 041: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub

However, I tried again as root (my udev rules grant write permission to 2047:0013, not 2047:0203), and after doing it twice it took and now it works with both ezfet (17 seconds) and tilib (3-4 seconds).

Yep, I did those from my Windows machine and it took 3 attempts but finally worked as described.

Link to post
Share on other sites

This is the biggest minus of LP approach, that all pins of target device are not accesable, only prepared for BP connection.

 

Yeah, and this mostly kills the usability of the EXP430F5529LP for me since I don't care about USB.  There's this neat SENSHUB booster pack with temperature, humidity, pressure, light, accelerometer, and other stuff.  It also has an RFEM header for a radio.  The sensors work, but the MSP430F5529 pins the RF header is connected to don't support SPI which is what's needed for the radio.

 

The EM Adapter booster pack doesn't have the sensors, but it does provide an EM header, and it's stackable with the SENSHUB.  Of the five GPIO lines from the radio, only one is routed to an interrupt-capable port on the EXP430F5529LP.  It's not the one connected to the CC3000 EM's SPI_IRQ line.

 

So much for using this as an off-the-shelf IoT device.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...