Problem programming MSP430G2452 with Launchpad

Aye, I got two today and was happy... did some work and end up with this... Tried two launchpads and both chips, nothing... :(

You are not alone. See

http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/t/93751.aspx

Hi Markus,

as already mentioned by old cow yellow you're not the only one who's having problems with the MSP430G2452 samples on the launchpad! But, you were the first one who's given details on the launchpad revision!

I have some of them, took a Rev 1.4 (new out of the box!) and tried programming the G2452. As you, I was unable to program the device:

MSP430: Trouble Writing Memory Block at 0xfa7c on Page 0 of Length 0x32: Could not write device memory
Cannot write to target

I removed the sample from the Rev 1.4 launchpad and mounted it on my Rev. 1.3 ones (the one I've used so far). After clicking DEBUG in CCS the download (and the app) works like a charm!

CONCLUSION:

All you guys out there facing problems in programming your MSP430G2452 parts, pls check your launchpad revision (printed under MSP-EXP430G2). 

To the guys at TI: Pls tell us about the difference of Rev 1.3 and Rev 1.4 launchpads! The users manual still shows Rev 1.3 (http://focus.ti.com/lit/ug/slau318/slau318.pdf) and has no details on 1.4!

Rgds
aBUGSworstnightmare 

old cow: Yes, I saw that posting.

 I'm in the exact same boat as Markus, CCS with all the latest updates, all 5 of my launchpads are 1.4.  I did try IAR also and it acts like it works to some degree.  I was going to give mspgcc a shot later today since it has support for the G2452's. I did send TI a mail through the online form, would be nice to get some actual information about this problems origin or resolution.

Tried just launching the debugger without debugging the active project and when you connect to the target it gives:

"The target setup (F20x2_G2x2x_G2x3x) does not match the actual target type (MSP430G2xx2)"

So I'm guessing the debugger doesn't even know about these chips yet.  Update?

@ Abugsworstnightmare, i think the difference between Launch pad Rev 1.3 and Rev 1.4 is the change in values of caps and resistors as shown below (taken from launchpad user guide). Apart from this i don't know if there is any  firmware change in these versions

Regards,

Nischay

Same problem here. I have Launchpads at V 1.4. Cannot load FW to G2452. Any feedback from TI ?

Hi

as Nischay pointed out, the only change between Rev1.3 and Rev1.4 is the slightly increased Programming Voltage and different Capacitors at the Oscillator of the emulator. This was changed to improve the startup characteristics and decrease yield loss in production.

We are currently investigating this issue and let you know any outcome.

Best Regards

Eric

I have also the same problem can flash some time but not debug.  The code is running soo the program is there in the G2452

Will follow this ....

//Jonas

Same problem here rev 1.4 launchpad. Very instable. Able to load executable once in a while. 

Eric Loeffler said:

... the only change between Rev1.3 and Rev1.4 is the slightly increased Programming Voltage and different Capacitors at the Oscillator of the emulator. ..

The 6k8 and 3k3 of Rev1.3 resulted 3.62V regulated output. The 61k5 and 30k1 of Rev1.4 resulted 3.60V. Not an increase, but an insignificant decrease.

Eric Loeffler said:

We are currently investigating this issue and let you know any outcome.

We are all waiting for that! Thanks.

Hi

Yes, old_cow_yellow you are absolutly rigth, its in fact a slight decrease, but this is not the issue. And i would really wonder if there is a difference between the LaunchPad revisions in programming the G2452.

We just discovered an issue with the MSP430.dll, which makes debugging impossible on CCS. The Mass Erase of only the main memory fails due to some missalignment between UIF/ez/LaunchPad FW and the DLL. We have discovered this issue with only the 8kB Flash ip on the G2452, the DLL version 2.4.7.1 on CCS 4.2.1.000004. The simplest fix is to just select Erase main and information memory on your CCS Debug Target setting.

We will incooperate a fix within the next DLL and IDE releases. But we still need some feedback from you guys, if this is really fixing your issue and under what circumstances you discovered this issue. We need Tool Revision, DLL and IDE version if you still experiencing a problem. We tried to get IAR to show this error, but IAR seems somehow resistent to this because they are using another DLL API.If someone is facing problems with IAR please let us know.

Best Regards

Eric

I running IAR Embedded Workbench Kickstart for MSP430 5.20  and debug is not working  .

Can not step the program and run tu curser.

/Jonas

Hello Eric,

Here is a snippet from one of my earlier posts in another thread:

"I have had some limited success by starting fresh with a brand new project, using the <MSP430G2452.h> include. Program is a microcrystal test program and is 86 bytes. Approximately 50% of the time I can flash the 2452 successfully and about the same percentage of the time I can initiate the Run command from CCS successfully. However, rarely can I single step the program without an error. 

I have tried it with USB supplied power and a separate power supply for the MSP target device and it doesn't seem to affect the results one way or the other.  However, there is tangible comfort in that I now have a flashing LED.  :)"

I am using CCS 4.2.1.00004 and the MSP430.dll version is 2.4.7.1.  I have also tried using IAR unsuccessfully.  I checked the settings in your screen shot and the only box checked in my case is "Erase Main and Information Memory". 

Hope this helps.....

Hi Eric,

sad to say: I'm not with you!

Yes, your're right when saying 'ERASE MAIN MEMORY ONLY' causes an error. I've did some testing (on a REV1.4 boards) which always results in the errors shown below when'ERASE MAIN MEMORY ONLY' is selected:

Selecting 'ERASE MAIN AND INFO MEMORY' gives you:

So, still impossible to debug the MSP430G2452 on Rev1.4 launchpad! 

I've had a look at the DLL-Version I'm using (it's 2.4.7.1), (just to be shure) CCS 4.2.1.00004 (it's the Microcontroller Edition with GRACE installed) before I un-mounted the MSP430 from the Rev1.4 Launchpad and re-mounted it on my Rev1.3.

Re-doing the same tests again resulted in the same error when selecting 'ERASE MAIN MEMORY ONLY' on the Rev1.3 too. Erasing main and info works without problems!

CONCLUSION:
REV1.4 will not allow debugging! REV1.3 does, but only if one selects 'ERASE MAIN AND INFO MEMORY'!

Rgds
aBUGSworstnightmare 

Here is the IAR environment specs for which the 430G2452 fails on Launchpad rev 1.4

-Andrea

=== Install subdirectory: 430 ===
 
IAR Assembler for MSP430
  5.20.1 (5.20.1.50215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\a430.exe
  12/1/2010 12:36:52 PM, 2081280 bytes
 
IAR C/C++ Compiler for MSP430
  5.20.1 [Kickstart LMS] (5.20.1.40215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\icc430.exe
  12/1/2010 12:54:50 PM, 16784384 bytes
 
IAR Library Builder
  5.0.2.5 (5.0.2.5)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\xar.exe
  11/5/2010 5:48:26 PM, 148992 bytes
 
IAR XLIB
  5.0.2.5 (5.0.2.5)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\xlib.exe
  11/5/2010 5:48:26 PM, 538112 bytes
 
IAR Universal Linker
  5.0.2.5 (5.0.2.5)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\xlink.exe
  11/5/2010 5:48:26 PM, 2316288 bytes
 
IAR C-SPY Batch Simulator Driver for MSP430
  5.20.1 (5.20.1.50215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\430bat.dll
  12/1/2010 12:15:14 PM, 505344 bytes
 
IAR C-SPY Emulator Driver for MSP430
  5.20.1 [Kickstart LMS] (5.20.1.40215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\430fet.dll
  12/1/2010 12:35:10 PM, 2469888 bytes
 
IAR C-SPY Library Support Plug-in for MSP430
  5.20.1 (5.20.1.50215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\430libsupport.dll
  12/1/2010 12:14:54 PM, 588288 bytes
 
IAR LibSupport Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\430LibSupport.ENU.dll
  11/23/2010 5:05:32 AM, 10240 bytes
 
IAR LibSupport Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\430LibSupport.JPN.dll
  11/23/2010 5:05:32 AM, 9216 bytes
 
IAR C-SPY Processor Descriptor for MSP430
  5.20.1 (5.20.1.50215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\430proc.dll
  12/1/2010 12:17:12 PM, 1895936 bytes
 
IAR C-SPY Simulator Driver for MSP430
  5.20.1 [Kickstart LMS] (5.20.1.40215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\430sim.dll
  12/1/2010 12:36:16 PM, 4061696 bytes
 
CP210x
  1.2 (1.2.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\CP210xManufacturing.dll
  1/14/2010 5:19:52 PM, 69632 bytes
 
IAR Project File Converter for MSP430
  V3.21A/W32 (3.21.1.9)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\cwtd430.dll
  1/14/2010 5:21:20 PM, 352256 bytes
 
FTD2XX library
  3.01.06 (3.1.6.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\FTD2XX.dll
  1/14/2010 5:19:52 PM, 81920 bytes
 
HIL
  1, 2, 6, 0 (1.2.6.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\hil.dll
  11/3/2010 2:36:22 PM, 32768 bytes
 
SEGGER J-Link MSP430 interface DLL
  2.1.1.0 (2.1.1.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\JLink430.dll
  1/14/2010 5:19:52 PM, 114688 bytes
 
MSP430.dll for USB-MSP430-FPA 4v61 based on TI's ver.2.4.6.1
  2, 4, 6, 1 (2.4.6.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\MSP430-FPA.dll
  11/26/2010 5:19:50 PM, 585728 bytes
 
MSP430 JTAG Interface Driver
  2.4.7.001 (2.4.7.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\msp430.dll
  11/8/2010 9:51:12 AM, 352256 bytes
 
MSP430
  1, 0, 4, 0 (1.0.4.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\olimex.dll
  11/29/2010 9:44:14 AM, 1138688 bytes
 
SBMSP430_DLL DLL
  2, 3, 3, 3 (2.3.3.3)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\sbmsp430.dll
  1/14/2010 5:19:52 PM, 262144 bytes
 
SiUSBXp
  3.1 (3.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\SiUSBXp.dll
  11/18/2010 10:26:50 AM, 90112 bytes
 
MSP430
  Version (2.3.3.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\SoftBaugh.dll
  1/14/2010 5:19:52 PM, 32768 bytes
 
IAR Workbench Target Descriptor for MSP430
  5.20.1 (5.20.1.50215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\swtd430.dll
  12/1/2010 12:15:48 PM, 1005056 bytes
 
IAR Workbench Target Descriptor, Emulator, for MSP430
  5.20.1 (5.20.1.50215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\swtd430fet.dll
  12/1/2010 12:14:42 PM, 587264 bytes
 
IAR Workbench Target Descriptor, Simulator, for MSP430
  5.20.1 (5.20.1.50215)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\bin\swtd430sim.dll
  12/1/2010 12:14:48 PM, 540672 bytes
 
Driver Installation Utility
  2.1 (2.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\USBXpressInstaller.exe
  9/9/2009 4:49:02 AM, 290816 bytes
 
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\InstallDriver32.exe
  1/14/2010 5:21:40 PM, 61440 bytes
 
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\InstallDriver64.exe
  1/14/2010 5:21:40 PM, 61440 bytes
 
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\eZ430-UART\preinstalCDC.exe
  1/14/2010 5:19:36 PM, 49152 bytes
 
Driver Package Installer
  2.1 (2.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Vista32\DPinst.exe
  1/14/2010 5:20:08 PM, 552528 bytes
 
Driver Package Installer
  2.1 (2.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Vista64\DPinst64.exe
  1/14/2010 5:20:08 PM, 1047632 bytes
 
Driver Package Installer
  2.1 (2.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Win7-32\DPinst.exe
  1/14/2010 5:20:08 PM, 552528 bytes
 
Driver Package Installer
  2.1 (2.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Win7-64\DPinst64.exe
  1/14/2010 5:20:08 PM, 1047632 bytes
 
Driver Package Installer
  2.1 (2.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\XP32\DPinst.exe
  1/14/2010 5:20:08 PM, 552528 bytes
 
Driver Package Installer
  2.1 (2.1.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\XP64\DPinst64.exe
  1/14/2010 5:20:08 PM, 1047632 bytes
 
FTD2XX Dynamic Link Library
  3.02.02 (3.2.2.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\FTD2XX.dll
  11/16/2010 8:54:24 AM, 199048 bytes
 
FTDI USB Serial Converter Property Page Provider
  1.2.0.1 (1.2.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\amd64\ftbusui.dll
  10/22/2009 2:17:04 PM, 143688 bytes
 
FT2232 VCP CoInstaller
  2.00.00.1 (2.0.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\amd64\ftcserco.dll
  10/22/2009 2:11:20 PM, 51528 bytes
 
FTD2XX library
  3.01.19 (3.1.19.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\amd64\ftd2xx64.dll
  10/22/2009 2:17:18 PM, 330056 bytes
 
FTDI Multi-Lingual Property Page Text Library
  1, 4, 0, 1 (1.4.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\amd64\ftlang.dll
  10/22/2009 2:16:52 PM, 284992 bytes
 
FTDI Virtual COM Port Property Page Provider
  2.06.00.1  built by: WinDDK (2.6.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\amd64\ftserui2.dll
  10/22/2009 2:08:36 PM, 55112 bytes
 
FTDI USB Serial Converter Property Page Provider
  1.2.0.1 (1.2.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\i386\ftbusui.dll
  10/22/2009 2:17:10 PM, 120136 bytes
 
FT2232 VCP CoInstaller
  2.00.00.1 (2.0.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\i386\ftcserco.dll
  10/22/2009 2:11:26 PM, 54088 bytes
 
FTD2XX library
  3.01.19 (3.1.19.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\i386\ftd2xx.dll
  10/22/2009 2:17:26 PM, 206144 bytes
 
FTDI Multi-Lingual Property Page Text Library
  1, 4, 0, 1 (1.4.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\i386\ftlang.dll
  10/22/2009 2:16:56 PM, 197952 bytes
 
FTDI Virtual COM Port Property Page Provider
  2.06.00.1  built by: WinDDK (2.6.0.1)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\Olimex\i386\ftserui2.dll
  10/22/2009 2:08:46 PM, 52552 bytes
 
WDF Coinstaller
  1.9.7600.16385 (win7_rtm.090713-1255) (1.9.7600.16385)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Vista32\WdfCoInstaller01009.dll
  1/14/2010 5:20:08 PM, 1461992 bytes
 
WDF Coinstaller
  1.9.7600.16385 (win7_rtm.090713-1255) (1.9.7600.16385)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Vista64\WdfCoInstaller01009.dll
  1/14/2010 5:20:06 PM, 1721576 bytes
 
WDF Coinstaller
  1.9.7600.16385 (win7_rtm.090713-1255) (1.9.7600.16385)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Win7-32\WdfCoInstaller01009.dll
  1/14/2010 5:20:06 PM, 1461992 bytes
 
WDF Coinstaller
  1.9.7600.16385 (win7_rtm.090713-1255) (1.9.7600.16385)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\Win7-64\WdfCoInstaller01009.dll
  1/14/2010 5:20:08 PM, 1721576 bytes
 
WDF Coinstaller
  1.9.7600.16385 (win7_rtm.090713-1255) (1.9.7600.16385)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\XP32\WdfCoInstaller01009.dll
  1/14/2010 5:20:08 PM, 1461992 bytes
 
WDF Coinstaller
  1.9.7600.16385 (win7_rtm.090713-1255) (1.9.7600.16385)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\drivers\TIUSBFET\XP64\WdfCoInstaller01009.dll
  1/14/2010 5:20:06 PM, 1721576 bytes
 
LCD Plugin for EW430
  3.42A (3.42.1.9)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\plugins\Lcd\lcd.dll
  12/1/2010 12:15:48 PM, 413696 bytes
 
SEGGER embOS IAR-Plugin
  6, 0, 6, 0 (6.0.6.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\plugins\rtos\embOS\embOSPlugin.dll
  11/4/2010 2:23:26 PM, 572416 bytes
 
PowerPac RTOS Plugin
  6, 0, 6, 0 (6.0.6.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\plugins\rtos\PowerPac\PowerPacRTOSPlugin.dll
  11/2/2010 9:40:42 PM, 594944 bytes
 
µC/OS-II <= 2.86 KA Plug-in for C-SPY DLL
  2.5.0 (2.5.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\plugins\rtos\uCOS-II\uCOS-II-286-KA-CSpy.dll
  11/3/2010 8:25:58 PM, 659456 bytes
 
µC/OS-II >= 2.87 KA Plug-in for C-SPY DLL
  2.5.1 (2.5.1.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\plugins\rtos\uCOS-II\uCOS-II-KA-CSpy.dll
  11/3/2010 8:25:58 PM, 664576 bytes
 
PspUtil1Plugin DLL
  2.0 (2.0.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\plugins\simulation\PspPort1LED.psp.dll
  3/12/2010 11:18:04 AM, 464384 bytes
 
CSPY PspWatchdogPlugin DLL
  2.0 (2.0.0.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\plugins\simulation\PspWatchdogPlugin.psp.dll
  3/12/2010 11:16:56 AM, 452096 bytes
 
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\PowerPac\USB\Windows\Bulk\Example\Exe\Echo1.exe
  12/1/2010 1:44:18 PM, 49152 bytes
 
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\PowerPac\USB\Windows\Bulk\Example\Exe\EchoFast.exe
  12/1/2010 1:44:18 PM, 45056 bytes
 
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\PowerPac\USB\Windows\Bulk\Example\Exe\Test.exe
  12/1/2010 1:44:18 PM, 45056 bytes
 
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\430\PowerPac\USB\Windows\HID\Example\Exe\HIDEcho1.exe
  12/1/2010 1:44:16 PM, 53248 bytes
 
=== Install subdirectory: common ===
 
IAR CSpyBat
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\CSpyBat.exe
  11/23/2010 5:06:30 AM, 735232 bytes
 
IAR Build Utility
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IarBuild.exe
  11/23/2010 5:08:22 AM, 97280 bytes
 
IAR Embedded Workbench IDE
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IarIdePm.exe
  11/23/2010 5:07:30 AM, 504320 bytes
 
IAR CSpyBat Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\CSpyBat.ENU.dll
  11/23/2010 5:04:30 AM, 5632 bytes
 
IAR CSpyBat Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\CSpyBat.JPN.dll
  11/23/2010 5:04:34 AM, 4096 bytes
 
IAR C-SPY Debugger GUI
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\DebuggerGui.dll
  11/23/2010 5:08:30 AM, 1877504 bytes
 
IAR C-SPY Debugger GUI Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\DebuggerGui.ENU.dll
  11/23/2010 5:07:46 AM, 65536 bytes
 
IAR C-SPY Debugger GUI Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\DebuggerGui.JPN.dll
  11/23/2010 5:07:44 AM, 56832 bytes
 
IAR Find In Files
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\FindInFiles.dll
  11/23/2010 5:07:24 AM, 302080 bytes
 
IAR Find In Files Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\FindInFiles.ENU.dll
  11/23/2010 5:05:56 AM, 4608 bytes
 
IAR Find In Files Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\FindInFiles.JPN.dll
  11/23/2010 5:05:50 AM, 4096 bytes
 
IAR Build Utility Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IarBuild.ENU.dll
  11/23/2010 5:05:46 AM, 3072 bytes
 
IAR Build Utility Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IarBuild.JPN.dll
  11/23/2010 5:05:46 AM, 3072 bytes
 
IAR Embedded Workbench IDE Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IarIdePm.ENU.dll
  11/23/2010 5:05:46 AM, 472064 bytes
 
IAR Embedded Workbench IDE Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IarIdePm.JPN.dll
  11/23/2010 5:05:46 AM, 467456 bytes
 
IAR IDE Framework
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IdeFramework.dll
  11/23/2010 5:05:48 AM, 1022976 bytes
 
IAR IDE Framework Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IdeFramework.ENU.dll
  11/23/2010 5:05:38 AM, 4608 bytes
 
IAR IDE Framework Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\IdeFramework.JPN.dll
  11/23/2010 5:05:38 AM, 3584 bytes
 
IAR C-SPY Debugger Kernel
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\kernel.dll
  11/23/2010 5:08:52 AM, 2305024 bytes
 
IAR C-SPY Debugger Kernel Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\kernel.ENU.dll
  11/23/2010 5:08:00 AM, 14336 bytes
 
IAR C-SPY Debugger Kernel Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\kernel.JPN.dll
  11/23/2010 5:08:00 AM, 10240 bytes
 
IAR Log Window
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\LogWindow.dll
  11/23/2010 5:06:42 AM, 254464 bytes
 
IAR Log Window Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\LogWindow.ENU.dll
  11/23/2010 5:05:04 AM, 9728 bytes
 
IAR Log Window Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\LogWindow.JPN.dll
  11/23/2010 5:05:04 AM, 9728 bytes
 
IAR Project Manager Engine
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\ProjectManagerEngine.dll
  11/23/2010 5:08:00 AM, 1216512 bytes
 
IAR Project Manager Engine Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\ProjectManagerEngine.ENU.dll
  11/23/2010 5:04:50 AM, 13312 bytes
 
IAR Project Manager Engine Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\ProjectManagerEngine.JPN.dll
  11/23/2010 5:04:48 AM, 9216 bytes
 
IAR Project Manager Gui
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\ProjectManagerGui.dll
  11/27/2010 12:10:06 AM, 807424 bytes
 
IAR Project Manager Gui Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\ProjectManagerGui.ENU.dll
  11/23/2010 5:04:44 AM, 156672 bytes
 
IAR Project Manager Gui Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\ProjectManagerGui.JPN.dll
  11/23/2010 5:04:40 AM, 147968 bytes
 
IAR Text Editor
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\TextEditor.dll
  11/23/2010 5:07:56 AM, 745984 bytes
 
IAR Text Editor Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\TextEditor.ENU.dll
  11/23/2010 5:04:28 AM, 25600 bytes
 
IAR Text Editor Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\TextEditor.JPN.dll
  11/23/2010 5:05:48 AM, 23552 bytes
 
Shared Library for Xerces-C Version 1.5.1
  1, 5, 1 (1.5.1.0)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\xerces-c_1_5_1.dll
  11/1/2010 8:16:26 PM, 1197056 bytes
 
IAR XmlLib
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\bin\XmlLib.dll
  11/23/2010 5:04:06 AM, 87040 bytes
 
IAR Code Coverage Plug-in
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\CodeCoverage\CodeCoverage.dll
  11/23/2010 5:08:26 AM, 451584 bytes
 
IAR Code Coverage Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\CodeCoverage\CodeCoverage.ENU.dll
  11/23/2010 5:08:22 AM, 10752 bytes
 
IAR Code Coverage Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\CodeCoverage\CodeCoverage.JPN.dll
  11/23/2010 5:08:12 AM, 10240 bytes
 
IAR ORTI RTOS Plug-in
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\Orti\Orti.dll
  11/23/2010 5:07:00 AM, 563200 bytes
 
IAR ORTI RTOS Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\Orti\Orti.ENU.dll
  11/23/2010 5:05:02 AM, 8704 bytes
 
IAR ORTI RTOS Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\Orti\Orti.JPN.dll
  11/23/2010 5:05:02 AM, 7680 bytes
 
IAR Stack Plug-in
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\Stack\Stack.dll
  11/23/2010 5:06:08 AM, 486400 bytes
 
IAR Stack Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\Stack\Stack.ENU.dll
  11/23/2010 5:04:24 AM, 7168 bytes
 
IAR Stack Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\Stack\Stack.JPN.dll
  11/23/2010 5:04:52 AM, 6144 bytes
 
IAR Symbols Plug-in
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\SymList\SymList.dll
  11/23/2010 5:06:16 AM, 431616 bytes
 
IAR Symbols Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\SymList\SymList.ENU.dll
  11/23/2010 5:05:00 AM, 3072 bytes
 
IAR Symbols Plug-in Language Specific Resources
  6.1.2.1748 (6.1.2.1748)
  C:\Program Files\IAR Systems\Embedded Workbench 6.0 Kickstart_0\common\plugins\SymList\SymList.JPN.dll
  11/23/2010 5:05:00 AM, 2560 bytes

Thank you all for your feedback!

It seems that the error within our tool chain is not the only problem with the new G2452 silicon. Sadly we are still not able to reproduce an error on our setup other than the issue with the main memory erase. We have different production lots of LaunchPads, devices and different IDE versions, but all are working fine.

@Andrea: I am working with the same IAR and dll here and it's working fine. Did you also use the LaunchPad Rev1.4 as well?

@aBUGSworstnightmare: Is it somehow possible to get hold on your failing setup or can you give any more details on the failing LaunchPad. (VCC, SerialNr. on the back, Crystal used, ...) Is there any way to get in contact with you?

We are really sorry about this issue and what you see here in the forum is only the tip of the iceberg.

Regards

Eric

Hi Eric,

I can give you the details on the Launchpads in the eving (MEZ).

Where are your located? I'm living in Munich, so Freising wouldn't be the farest way to go.

 You should be able to get my email address (since I will not post it in the forum) to get in touch with me. If you have problems in obtaining it you can ask David Friedland or Andreas Dannenberg for it (or posts yours and I will email you).

CU
Joerg (aBUGSworstnightmare)

Eric, correct the test has been done on a ver. 1.4 LaunchPad.

-Andrea

I was hoping a different batch of chips would be available.  I ordered a new sample and it came immediately, it had painted lettering this time.  Same problem found using Rev 1.4  SN101001479, using crystal supplied with launchpad kit, different usb cables, and CCS with Grace removed.

Its Funny ! , Ti Engineers have no clue about this problem. how can Ti  launch these chips without proper testing,  what is the use of having these chips if they cannot be programmed using Ti's own IDE and H/W.

Ti sold ( and is selling) Launch pads saying that these boards can be used for all value line series MSP430s for programming and debugging which includes the 14 pin and 20 pin PDIP packages.

i bet ,we all bought more than 3 boards and are complaining that theses boards are useless with these chips. We all have been Fooled ! thats's as simple as that.

I think we in the forum are going very soft with TI, if this would have happened in a commercial setup, then i think Ti would  be facing  hundreds( or even thousands) of Law suits against them.

Ti correct your mistake - announce a total Recall of these chips or the Launchpad boards and end this mess. Don't try to shake off this problem by saying

"We are not able to replicate the problem with our in house setup"

Earlier it was the "never ending" waiting time for Launchpad boards and now this problem - TI give us a Break

Nischay

Well put Nischay.  I am heartbroken about these latest occurrences.  The medical device I have been developing could probably be built with any other MCU, but I picked up on the LP because of TI's marketing of the MSP430 chips.  I have wasted my time and energy with this betting on the 20PIN chips, only to languish with four inputs and outputs.  Someone else will probably patent my idea while I rework my plan.

KB

Sigh, I cannot hear all this lamenting anymore.
The LaunchPad is a cheap adertising product. For <$5 including a programmer and an USB cable that alone costs more in an average supermarket.

Considering an ultra-low-cost device for medical devices is ... well ... I really don't want to put my life on such a product.

Yes, there seems to be a problem. And it seems to not show up in the lab. So there must be something different between lab and end users. And it must be sorted out somehow.

But there's really no point in crying 'lawsuits' (while typing this word, you almost wasted more energy that the LaunchPad did cost you!) or 'I use a different processor' (which one? the ten or hiundred times more costly ones from this or the incapacitated and still mroe expensive and power wasting ones from that competitor? Why did you chose the LaunchPad in first place?)

In most cases it turned out that the problem is a certain combination of (maybe common) hardware or software on the user side that was not used in the TI labs.

There's a golden rule about any prduct or work:

"Things can be good, fast and cheap.
fast and cheap is not good.
good and cheap is not fast.
fast and good is not cheap."

So if you choose to go for cheap and want it good, you cannot expect it fast. Give the folks at the TI labs time to find the reason (if things are workign for them, they are working for them. So just saying 'it won't work for me' won't help to find the reason).
If you want to have the result ASAP, you'll have to pay an engineer to dedicate all of his time to this job. For $100 an hour or more. Then you get it fast - but it isn't cheap anymore.

Be patient, make your own investigations or move along and look for a different product. But please stop crying like a baby that dropped its lollypop.

Sorry, but this 'I want it all and I want it now and I want it for free' attitude is really bugging me.

I was thinking along the same lines. Silicon and the tools to work with it are incredibly complex and glitches are inevitable, especially when rolling out new products.

Count me among the group waiting patiently for the root cause to be found and the issue ultimately resolved.

Nice attitude.  The best thing that could happen to the medical device industry would be to have cheaper options which improve or outperform what is available now.  Disposable device are commonplace, and the price tags are astounding.  Of course, nobody would use a component that was in any way dangerous or unreliable to save a buck, this could be the lesson of the day......

Ken Bueltmann said:

The best thing that could happen to the medical device industry would be to have cheaper options which improve or outperform what is available now

Ken Bueltmann said:

Of course, nobody would use a component that was in any way dangerous or unreliable to save a buck

That's why the NASA still uses processors with 20 years + age. They are thoroughly tested, all bugs are known or removed.

Ina cirital or production environment, you shouldn't even update your flash player just because the update notification offers you to do so. (and I know from my lady, who is working in the field of medical studies) that they have even more restrictive regulations for their equipment. Everything that's not been tested for soem tiem in the IT department won't be allowed for the working stations. This includes even the paper supply for the printers :)

The problem processor in the new LaunchPads is so new on the marked, teh ink on the blueprints is still wet. It's nice to play with it and it is cheap, But I don't consider it a mature product yet. Nothing for critical environemnts or mass production. And everyone working on projects with this market should know this.

Well put JMG.  I hope these chips make the cut. in the long run......The premise is exciting

.. Microsoft Windows [Version 6.1.7600] (Windows 7, fully patched) 64 bit.  Both CCS and IAR are fully patched and neither work.  I've had "random" luck with launching the debugger in CCS and then connecting to the device, reloading program, reset/reset, and I was able to get the DCO flash to work... once.  The chip behaves more like it's just not running the program as I can reset it with just battery power and it will not blink leds with a led blinking test program.  Program Counter takes me to random addresses and I can almost never flash the reset (0xfffe). I'll post board/chip rev's when I get home... From an IT job in a hospital. 

Yes, the software restrictions are tight, but I'll tell ya... It's not as bad as you folks are painting it.  Not at all.

I am having the same problem.   I am using a LaunchPad, rev 1.4.   And my CCS is 4.21.00004.  This is the message I see when trying to write to my MSP430G2452PW sample:

I also see this error:

Both chips are OCDYRKKA / M430G2452.

Oops, here is that error.

1122.CCSError.tiff

BTW, I just tried a program with the MPS430G2452 sample under IAR and it works.  So the problem is definitely not with the part but with CCS.

Regards, Jeff

Hi Jeff ,

In IAR, which option did you use : 1) Erase Main memory or 2) Erase main Mem + info Mem  ?

Also, what was your success rate, did you get to program the chip in first go or you made several attempts ?

@ JMG

I know you are a very die hard fan of MSP430 (or Ti), many times you have said that LP is a cheap tool and one should not expect too much from it, well, i am not expecting "MIRACLES" from LP but it should at least be able to program the chips for which it was designed and promoted. i am not expecting LP to program a AVR or a PIC. i never knew about the new value line series (14 pin and 20 pin) until i came across LP in a write up.

Why should i pay $100/hr for a Ti engineer if this mess was created by Ti ? Also  nobody forced TI to launch the 20 pin chips without proper testing, they were or are in a hurry to catch the hobby bandwagon. Because i paid $4.3 do i have to live up with this annoyance and keep telling my self that " because this is a cheap tool, expect this sought of things to happen".

Also i have read in your other threads, you asked the user/thread starter  "So, who asked you to choose the MSP430 ? ". Just because people  chose MSP430 do they have to "suffer" ?

Regards,

Nischay

I have tried a fresh Windows XP Pro 32 bit  install with CCS, both updates, and IAR.  And.....

CCS:

MSP430: Trouble Writing Memory Block at 0xfffe on Page 0 of Length 0x2: Could not write device memory
Cannot write to target

IAR:

Wed Feb 23 19:28:23 2011: Target reset
Wed Feb 23 19:28:25 2011: Could not write device memory

and when I stop it (break)...

Wed Feb 23 19:29:14 2011: The stack 'Stack' is filled to 98% (79 bytes used out of 80). The warning threshold is set to 90.%

Though IAR will actually reset the PC when CCS won't and the program will run, once.  They both fail to write the reset vector still :(

IAR has worked repeatedly for me..   It has never not worked since I first tried it.  I think it is the latest version, I downloaded it last week.  The about screen has way too many version numbers in it, so I am not going to list them all here. Of note:

I am using the default erase main and info mem option. 

It has worked several times in a row with my MSP430G2452 which I received from TI yesterday.  I whipped up a home made single sided etched .032 PCB TSSOP to DIP adapter.  I can solder the .65 mm pad pitch, so it worked great.   This was my solution for the lack of availability on the DIP packages.  

My LaunchPad is rev 1.4 received a couple weeks ago.    

The whole thing is running in a VMware virtualized Win 7 32 bit machine on my MacBook Pro and it works fine.  So I don't think there's really anything wrong with the timing, USB, LaunchPad, Hardware, etc.  I think it is just a CCS library.   

I don't think it is worth an overreaction.  These are samples, not 1000 unit productions quantities, and I've seen these new releases many times.  It takes a little time to work out all the bugs.  TI will fix it shortly and all will be well.   

If anybody has tried out the PinOsc Capacitive Touch on the new 2xx2 parts, please post your experiences.   I am going to try it tonight.

Hello Markus,

I have exactly the same problem.

MSP430G2452 seem to be not supported by CCS.

Regards

Hi nabil,

well, MSP430G2452 IS supported by CCS! I have a setup (launchpad + silicon) on my desk which NEVER failed!

In addition, I have launchpads/devices which always fail when I attempt programming/debugging the device and I have some which sometimes fail!

So, stop 'which-hunting' because this is a far more complex problem than it looks like on first view! It's a combination of problems caused by the silicon, launchpad hardware (since my samples are working when I debug them by using the MSP-FET430UIF WITH CCS) and software (since CCS AND IAR have problems).

Rgds
aBUGSworstnightmare 

Just chiming in with a "me too".

I have a Launchpad rev 1.4, MSP430G2452 with a date code OCDYRKKA.

Running CCS on Windows XP.

voltage measured on the pins of the MSP430G2452 is 3.55V

9 out of 10 times (very roughly) I get the error: "MSP430: Trouble Writing Memory Block at 0xfffe on Page 0 of Length 0x2: Could not write device memory"
"Cannot write to target"

Once in a while it successfully programs, but doesn't run in the debugger:

with the error: "MSP430: Can't Run Target CPU: Could not run device (to breakpoint)"

On unplugging the launchpad usb connector and plugging it back in, it runs (program blinks an LED so I know it runs).

(it has once run in the debugger)

Incidentally, pressing S1 doesn't have any effect while the program is running. Shouldn't it hard reset the CPU ? (the switch and the board are fine. reset has been confirmed electrically on pin 16.)

Wish you guys luck debugging!

Please let me know if there's any more information I can provide, or any tests you would like me to run.

Ok so this is really strange: I have 3 Launchpads. All 3 are Rev1.4

But what seems important isn't the Rev, it's what's written on the bottom side of the pad. I have 2 Launchpad which have written 1033 the at the bottom side, with them programming only works 1 out of 6 times. With the other Launchpad with the code 1030 at the bottom side programming and debugging always works!

Can someone verify this?

I attached a photo, with the code highlighted.

Greetings

Markus

Markus, its probably a coincidence. I know of someone who has a 1033 that works fine.

I have a 1043 that works intermittently.

The code is probably YYWW (2 digit year, 2 digit week)

I'd like to explore another possibility: The clock on the MSP430F1612.

Can you take photos of the crystal Q1 on the top right hand corner of both your boards ?

M<something> Bhungy said:

Can you take photos of the crystal Q1 on the top right hand corner of both your boards ?

There's a difference there too, between the working and the 2 not-working Launchpads:

Working: 

12.000

B 032F

Not working:

12.000

B 046F

Mr.Nischay Kumar V said:

I know you are a very die hard fan of MSP430 (or Ti)

I just have learned not to pick the latest product on the market, expect it to work flawlessly like a years old tested and refined product and then stomp with the foot if it doesn't.

Mr.Nischay Kumar V said:

it should at least be able to program the chips for which it was designed and promoted.

Mr.Nischay Kumar V said:

Why should i pay $100/hr for a Ti engineer if this mess was created by Ti ?

Mr.Nischay Kumar V said:

"So, who asked you to choose the MSP430 ? ". Just because people  chose MSP430 do they have to "suffer" ?

Luckily there are some people who rather try to find a solution than to bug us with pointless laments. Thanks to Markus and M Bhungy for their investigations. Maybe it leads into the right direction. Since it seems to be a timing problem, teh crystal on the programming side could be a cause.

Just wanted to add my experience...

My version 1.4 launchpad works just great with the microcontrollers supplied with it, but I too cannot get a MSP430G2452 to work. This is using the latest IAR Workbench. There are numerous errors when downloading a program and breakpoints do not work. The program usually seems to run, however.

It's too bad because I need the extra I/O on the 20-pin package. I am also now worried that the Launchpad will have trouble with other Spy-Bi-Wire devices...

Dan

Eric Loeffler said:

It seems that the error within our tool chain is not the only problem with the new G2452 silicon. Sadly we are still not able to reproduce an error on our setup other than the issue with the main memory erase. We have different production lots of LaunchPads, devices and different IDE versions, but all are working fine.

Hi Eric,

I would be happy to provide you with my launchpad and failing G2452 if that would help you out.

Dan

Last post was in march, are there any updates or am I missing something?

The problem can be solved by updating the Launchpad firmware.

The last available firmware in this link http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update allow Launchpad to support many new G2XXX members.

Regards

Now my launchpad is working like a charm :-) with the G2452. Updated from my laptop running W7 64bit.

Thank's TI...

Would you like to help me solve error 

Error connecting to the target:
The target setup (F20x2_G2x2x_G2x3x) does not match the actual target type (MSP430G2xx3)

Thanks

Hi Leminh,

you have to select another device in your IDE project setting. You selected a device which is not matching the one you have put into the LaunchPad socket. Select the MSP430G2553 if you are trying to access the device supplied with the LaunchPad.

Regards

Eric

This link:

http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update

helped me
Thanks!