MSP430F2011 and IAR workbench fails to debug because of energytrace

I am still searching for a solution. Does anyone knows, if I need an update on the eZ430-board, which I have connected to the application?

BR Bernd

Hello Bernd,

The eZ430 does not support ULP debugging, hence why the "Enable ULP" check box is disabled and Energy Trace is not supported for this project. I was able to build and run a simple ASM project using a MSP-EXP430G2 LaunchPad (which includes an on-board eZ430) with a MSP430F2012 device. What type of eZ430 board are you using? Has the correct target device and debugger tool been selected in the project options?

Regards,
Ryan

Dear Ryan,

Thanks for reply! We don't want to use ULP. We don't want to use EnergyTrace, we don't want to use EnergyTrace++. If this Comes within IAR, it is fine, but we just don't care about it.

Our different boards are as follows: The eZ430-F2013, which Comes in the Crystal USB-package and is a very fine device to teach students about the MSP430 device. Three wires from this Crystal clear device are connected to an outside placed device, in a very simple application just connected with the battery and an oscilloscope for visual explainations.

Than the MSP-EXP430G2 board which come with the pin rail left and right to the processor.

After updating the IAR workbench from the CD-Versions which came Long time before with the demo boards to the 6.30 or the 6.50 Software Revision, the demo boards are not longer usable.

Definitely, this also means all material for Student teaching/training does not work at the moment.

Please specify more questions for further discussions.

Best regards

Bernd

Hello Bernd,

As I stated previously, I am having trouble replicating this issue which makes it hard to produce a solution. I will try to loop in an IAR expert to provide further comments/suggestions, for the moment I recommend uninstalling all instances of the IAR Workbench from your computer and attempt to re-install the newest version again. Did you mention that the same error can be found when trying to connect a MSP-EXP430G2 LaunchPad? Have you tested for this problem on more than one computer station?

Regards,
Ryan

Dear Ryan,

Thanks for your Support concerning this issue! There are several questions and suggestions in your message above, which I try to answere one by one:

Trouble replicating:
>>>> code sample >>>
#include "msp430.h" ; #define controlled include file

NAME main ; module name

PUBLIC main ; make the main label vissible
; outside this module
ORG 0FFFEh
DC16 init ; set reset vector to 'init' label

RSEG CSTACK ; pre-declaration of segment
RSEG CODE ; place program in 'CODE' segment

init: MOV #SFE(CSTACK), SP ; set up stack

main: NOP ; main program
MOV.W #WDTPW+WDTHOLD,&WDTCTL ; Stop watchdog timer
JMP $ ; jump to current location '$'
; (endless loop)
END
<<< code sample end <<<<

IAR-expert: After first blocking, now I stand in contact with the IAR "FAE.EMEA" in Munich. He got a similar sample code and could confirm the error / warning. His comments were (by coding with MSP-EXP430G2 board)

- remove Projectoptions Debugger -> FET Debugger -> Breakpoints clickboxes on card System breakpoints (putchar, getchar) (remove/deactivate)

- deactivate clickboxes Tools -> Options -> Stack all clicks (this, I never deactivate in the past)

The comment from the FAE was

"Wed Jun 29, 2016 10:56:43: No state storage buffer implemented on connected device : (EnableEnergyTrace) "

is just an diagnosis issue, not an error at all - okay I understand.

At this point, I have done all what he explained, but: If you place a second breakpoint in code, this will be ignored and can not be deactivated in Debugger. To deactivate the breakpoint, this can be done in Editor only. I have tested several constallations, one time the Debugger stopped one line before the first breakpoint.

The very bad thing is, the second breakpoint is ignored and the user believes, this part of code will never be reached !

... No, I have not deinstalled and reinstalled the workbench. I am going with the package file "EW430-6501-Autorun.exe", which sets up the Version MSP430 6.50.1.

But I have installed this Version on a totally different PC-System with Win7 and 64bit hardware. All the behaviours are the same as on the WinXP System with the first ansatz.

Yes all tests described above are done with the board MSP-EXP430G2 and the processor G2231.

So, what I do not understand at the moment is, the SECOND breakpoint is not handled in the correct way. And the missing hints were related to "putchar", "getchar",and the stack control.

Now, I am expecting an answer from the FAE from Munich. I am interested, if you can confirm the misbehaviour and if the expert from IAR USA is Aware about These issues. Definitely, the use of the two breakpoint is unsatisfied.

(Sorry for misspelled text. Something on Internet page changes characters by itself.)

... awaiting Response, BR

Bernd

Bernd,

I was able to reproduce the breakpoint error with the code example provided, the debug log output:

Invalid parameter(s) : (SetNewEEMBreakpoint) , pwBpHandle=0x0
Failed to clear breakpoint: Driver error.

As this issue is strictly related to the IAR software your greatest support will come from the IAR team. My IAR USA contact has yet to respond to my email inquiry.

Regards,
Ryan

Dear Ryan,

Thanks for confirmation. As I understand you opened a ticket at IAR? That's fine. We should stay in contact and wait what they will answer from Munich and USA.

I'll Keep you informed.

BR

Bernd

Dear Ryan,

and "to whom it may concern"!

Meanwhile I have received a confirmation of the bug from IAR office Munich. They escalated this issue to their development team (in Sweden ?) and now, we have to wait for their response - bug fix.

But, this does not mean that the world stands still and is not able to turn. A first solution to overcome the bug is to disable the SW breakpoints and continue work with HW breakpoints at the moment.

---> open window for Workspace
- mouse right click on root of Project
- mouse left click on oprions...
- mouse left click on Debugger -> FET Debugger
- Card breakboints
- diasble "use Software breakpoints"
- here an extra info: "System breakpoints on - exit getchar putchar " all are disabled

These are my settings by now and I continue my work.

Do not feel too good, I have found another mystery with the FR5969 and come back soon - with a new thread.

BR

Bernd

Dear Ryan,

Thanks a lot. This morning I have talked to the FAE in Munich and suggested to update the template for new projects of workbench. Since the eZ430-F2013 kits are still sold in DE, mainly, I think, to students, hobbyists, and HAM radio amateurs, this might help them after updating from the CD-Version of the kit to the most recent released version. ... same with launchpad for G2331.

I really have my doubts, if the "however consequences" will be available within the next weeks.

But we will see...

So far I discoverd another bug after glueing the F2011 to the Launch pad MSP-EXP430F5969. This Story is filed under e2e.ti.com/.../525899

To me, it is okay to close this converstion at the moment and I will do the best for my projects from the current situation.

Best regards

Bernd

Dear Ryan 

we need F2011 MSU

how we can contact through mail

pls let me know mail

or replay 

my mail creeperpnp@gmail.com

Dear 

Thanks

I'm Located in India

I'm talked in your distributors at Coimbatore office

they told me only available MSP-FET FLASH EMULATOR, USB, MSP430

this is not available 

MCU and msp-ts430PW14 and MSP430F2011

we need F2011 MCU and that related Debugger and target and Samples MCU

we want read and re program it ( we made a new Products )

pls tell me how can i buy

or mail me 

creeperpnp@gmail.com

I am contacting Sales Support to address this matter.

Regards,
Ryan

Dear

My Address

Creeper Technologies
50, Nall Road , Erode , TN, INDIA

email : creeperpnp@gmail.com