I am finding that as soon as you bring out a smaller logger someone comes
along and wants it smaller still. I just did one that is 0.51 gms with
battery and encapsulation. Two mounting tubes add another 0.05gms to it. The
trouble is that it is not only weight that concerns these scientists, but
the size as well. The piezo devices I have seen are too bulky to consider. I
would like to see something like this in a MEMS scale size. I had an idea
about doing something like this but the funds were not available to pursue
it. I finally found someone who has a higher tolerance for weight and it is
a maximum of 125 grams. I have not had the luxury of something like this for
some time.
Cheers
Peter
-----Original Message-----
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Monday, 10 March 2014 7:30 PM
To: m...
Subject: [msp430] MAY BE OF INTEREST
Hi Peter, I was looking through Popular Science today, an old one, since I
stopped buying it when it became Australian authored. there was an article
on self powered light weight data loggers, which I know is your area of
interest. Basically they are trying to develop a piezo generator to power a
data logger. Their test version develops 300uW, so very low, and it's
bulky
having two discrete sections with the bendable piezo element as the link.
They are figuring the weight will be down to 12gm.
This got me to thinking. I have something I call LOQATOR. It has a 9 axis
sensor, 64Mb memory (although just 32Mb on the proto) temp and
altitude/pressure sensing and a GPS. The thing measures 0.9 x 0.9" or
<23 x 23mm and weighs just 4gm, the battery for it weighs 4gm, but is a
200+mAh device, and the RF circuit I designed to mate with it would
weigh just 0.5gm, although I don't know if this type of device would use
low
power ISM, or the old 70MHz beacon style. Do you want to data dump or simply
find the device? I don't know.
Hi Peter, I was looking through Popular Science today, an old one, since
I stopped buying it when it became Australian authored. there was an
article on self powered light weight data loggers, which I know is your
area of interest. Basically they are trying to develop a piezo generator
to power a data logger. Their test version develops 300uW, so very low,
and it's bulky having two discrete sections with the bendable piezo
element as the link. They are figuring the weight will be down to 12gm.
This got me to thinking. I have something I call LOQATOR. It has a 9
axis sensor, 64Mb memory (although just 32Mb on the proto) temp and
altitude/pressure sensing and a GPS. The thing measures 0.9 x 0.9" or
<23 x 23mm and weighs just 4gm, the battery for it weighs 4gm, but is a
200+mAh device, and the RF circuit I designed to mate with it would
weigh just 0.5gm, although I don't know if this type of device would use
low power ISM, or the old 70MHz beacon style. Do you want to data dump
or simply find the device? I don't know.
Al
Reply by Hugo Brunert●February 11, 20142014-02-11
If the C line of code which you want to put the breakpoint on was optimized out,
you will see that the breakpoint moves automatically to the next executable C
code line.
From: m... [mailto:m...] On Behalf Of Al Bowers
Sent: Tuesday, February 11, 2014 8:59 AM
To: m...
Subject: RE: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
Hi folks – one thing I have noticed is the optimization level –
the breakpoint can be set in the C source,
but the disassembly window shows this would not ever get called.
Not sure this is pertinent as some folks work solely in asm…
Thanks, Al
From: m... [m ailto:m...] On Behalf Of Onestone
Sent: Tuesday, February 11, 2014 6:27 AM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
Sure do, been there too many times.
Al
On 11/02/2014 3:00 PM, Peter Grey wrote:
Al,
One thing I did was upgrade the firmware on the FET. At one stage a year or so
ago I thought I had blown 2 FETs but it was going between 3 different computers
and moving FETs about. I then decided to keep each FET to their own computer.
When I upgraded IAR, I found it would not work and so upgraded the firmware and
it was OK. I have now been doing this on each PC. So far I have not lost a
single FET. There is something odd going on but I never seem to have the time to
track it down. It is usually once I get everything going that I am late with a
project and this takes priority. I am sure you know the situation!
Peter
From: m... [mailto:m...] On Behalf Of Onestone
Sent: Tuesday, 11 February 2014 11:25 AM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
HERE WE GO AGAIN, GOT THE LICENCE SORTED. So finally got on to 5.60 and what do
I find? Well it now recognsies 2 hardware breakpoints on the 149, and gives the
third as emulated. I could live with 2 breakpoints very comfortably, but what
the heck damn thing doesn't even recognise the second. Good thing though is
that it doesn't crash, it just blows right through it. however it does give
up and roll over if your in the debugger and try to set the third breakpoint.
Enough already. bed time.
Al
On 11/02/2014 12 :50 PM, Steve Mayfield wrote:
I've had issues with the V3 FET software too...so I keep copies of the
older HIL.DLL and MSP430.DLL files and then locate and replace the new versions
after installing compilier updates.
----- Original Message -----
From: Onestone
To: m...@yahoogroups.co m
Sent: Monday, February 10, 2014 18:11
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I would pay for a decent assembler, but not the high costs for a compiler I
don't want. I could go the Ti home tools route, but for unfathomable
reasons their assembler syntax doesn't appear to be compatible with IARs,
which is what I am more familiar with. I know the 149 should have 3 breakpoints
but IAR is giving 1 + 2 emulated, which it took me a while to figure were
causing the crashes. The trouble is that there are also other issues. The new
versions want to update the FET debugger, then do n't always complete
succesfully. I've lost 2 FET debuggers in a weekend. I'm loathe to
move to another piece of software which you already say is buggy, and lose my
last debugger. I will be totally screwed if that happens.
Al
On 11/02/2014 12:09 PM, Peter Grey wrote:
Al,
It has 3 breakpoints with a 149. I was getting odd behaviour with
breakpoints at one stage and ended up downloading the latest version to get over
it. I know the software if free so should not complain. I would not mind paying
something for a more reliable version, but I guess there is no choice.
Good luck
Peter
From: m... [mailto:m...] On Behalf Of Onestone
Sent: Monday, 10 February 2014 3:36 PM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
Thanks Peter, can you recall how many breakpoints it allows with a 149, and
what type they are? I'm kind of at a point where every time the program
stops at the only working breakpoint I have to reset and reload the software so
it is almost impossible to progress.
Al
On 10/02/2014 6:01 PM, Peter Grey wrote:
Al
I also downloaded the latest version from IAR, which needed a few back and
forth comms with them. This was although I did this from the TI site. The
version I downloaded was SLAC050at.zip. I have been using it fot some of the
newer micros and also the older ones like the F149. The system gives a lot more
errors than a few years ago. It is hard to define what is going on. I find that
I have to have an external power supply or it fails. Like you I am using Windows
XP. I have tried to run earlier versions but have never been able to do so. If I
get to many crashes I get the latest version and it seems OK for a time. I have
not had any issues with breakpoints.
Cheers
Peter
From: m... [mailto:m...] On Behalf Of Onestone
Sent: Monday, 10 February 2014 3:11 PM
To: m...
Subject: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I've gone back to an older design to upgrade the software. The design
uses an MSP430F149. A couple of months ago I upgraded Kickstarter to slac050aq,
or version 5.52. It seemed to be OK for the newer micros I was working with, but
now it seems to be behaving strangely. It won't revert to compiler mode
from debug mode, it crashes. It doesn't seem to recognise or a ct on most
breakpoints, if I try to modify a breakpoint it disappears upo its own butt, and
hangs the system.
Checking through I discover that it lists only the first breakpoint as
hardware, and all others as emulated, and it can't hgandle the emulated
breakpoints since the 149 doesn't have the advanced EEM module required.
I tried to backstep to an older version (both slac050r and slac050x) but it
bombed declaring it couldn't find a xerces-c dll file, which a search
reveals is in common/bin. I'm running XP because I hate the options. Any
ideas on how I can backstep or force the new version to recognise all 3 hardware
breakpoints?
Thanks
Al
< /div>
Reply by Al Bowers●February 11, 20142014-02-11
Hi folks - one thing I have noticed is the optimization level -
the breakpoint can be set in the C source,
but the disassembly window shows this would not ever get called.
Not sure this is pertinent as some folks work solely in asm.
Thanks, Al
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Tuesday, February 11, 2014 6:27 AM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
Sure do, been there too many times.
Al
On 11/02/2014 3:00 PM, Peter Grey wrote:
Al,
One thing I did was upgrade the firmware on the FET. At one stage a year or
so ago I thought I had blown 2 FETs but it was going between 3 different
computers and moving FETs about. I then decided to keep each FET to their
own computer. When I upgraded IAR, I found it would not work and so upgraded
the firmware and it was OK. I have now been doing this on each PC. So far I
have not lost a single FET. There is something odd going on but I never seem
to have the time to track it down. It is usually once I get everything going
that I am late with a project and this takes priority. I am sure you know
the situation!
Peter
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Tuesday, 11 February 2014 11:25 AM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
HERE WE GO AGAIN, GOT THE LICENCE SORTED. So finally got on to 5.60 and what
do I find? Well it now recognsies 2 hardware breakpoints on the 149, and
gives the third as emulated. I could live with 2 breakpoints very
comfortably, but what the heck damn thing doesn't even recognise the
second.
Good thing though is that it doesn't crash, it just blows right through
it.
however it does give up and roll over if your in the debugger and try to set
the third breakpoint.
Enough already. bed time.
Al
On 11/02/2014 12:50 PM, Steve Mayfield wrote:
I've had issues with the V3 FET software too...so I keep copies of the
older
HIL.DLL and MSP430.DLL files and then locate and replace the new versions
after installing compilier updates.
----- Original Message -----
From: Onestone
To: m...
Sent: Monday, February 10, 2014 18:11
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I would pay for a decent assembler, but not the high costs for a compiler I
don't want. I could go the Ti home tools route, but for unfathomable
reasons
their assembler syntax doesn't appear to be compatible with IARs, which
is
what I am more familiar with. I know the 149 should have 3 breakpoints but
IAR is giving 1 + 2 emulated, which it took me a while to figure were
causing the crashes. The trouble is that there are also other issues. The
new versions want to update the FET debugger, then don't always complete
succesfully. I've lost 2 FET debuggers in a weekend. I'm loathe to
move to
another piece of software which you already say is buggy, and lose my last
debugger. I will be totally screwed if that happens.
Al
On 11/02/2014 12:09 PM, Peter Grey wrote:
Al,
It has 3 breakpoints with a 149. I was getting odd behaviour with
breakpoints at one stage and ended up downloading the latest version to get
over it. I know the software if free so should not complain. I would not
mind paying something for a more reliable version, but I guess there is no
choice.
Good luck
Peter
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Monday, 10 February 2014 3:36 PM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
Thanks Peter, can you recall how many breakpoints it allows with a 149, and
what type they are? I'm kind of at a point where every time the program
stops at the only working breakpoint I have to reset and reload the software
so it is almost impossible to progress.
Al
On 10/02/2014 6:01 PM, Peter Grey wrote:
Al
I also downloaded the latest version from IAR, which needed a few back and
forth comms with them. This was although I did this from the TI site. The
version I downloaded was SLAC050at.zip. I have been using it fot some of the
newer micros and also the older ones like the F149. The system gives a lot
more errors than a few years ago. It is hard to define what is going on. I
find that I have to have an external power supply or it fails. Like you I am
using Windows XP. I have tried to run earlier versions but have never been
able to do so. If I get to many crashes I get the latest version and it
seems OK for a time. I have not had any issues with breakpoints.
Cheers
Peter
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Monday, 10 February 2014 3:11 PM
To: m...
Subject: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I've gone back to an older design to upgrade the software. The design
uses
an MSP430F149. A couple of months ago I upgraded Kickstarter to slac050aq,
or version 5.52. It seemed to be OK for the newer micros I was working with,
but now it seems to be behaving strangely. It won't revert to compiler
mode
from debug mode, it crashes. It doesn't seem to recognise or act on most
breakpoints, if I try to modify a breakpoint it disappears upo its own butt,
and hangs the system.
Checking through I discover that it lists only the first breakpoint as
hardware, and all others as emulated, and it can't hgandle the emulated
breakpoints since the 149 doesn't have the advanced EEM module required.
I tried to backstep to an older version (both slac050r and slac050x) but it
bombed declaring it couldn't find a xerces-c dll file, which a search
reveals is in common/bin. I'm running XP because I hate the options. Any
ideas on how I can backstep or force the new version to recognise all 3
hardware breakpoints?
Thanks
Al
Reply by Onestone●February 11, 20142014-02-11
None are connected Matthias. Another thing I discovered after upgrading
to the latest slac050aV version earlier.
It now shows 2 hardware breakpoints instead of the earlier 1 or the
actual 3. But only acts on one of them. however it does allow an
emulated one without crashing as it was before, and it will stop on it,
but if I add a second it ignores that. Perhaps it is only recognising
every second breakpoint of any kind, I don't know, and I can't waste
more time trying to make it work properly so I'm going to just carry on
running a single hardware breakpoint, since I don't trust it to select
the critical one.
Al
On 11/02/2014 7:22 PM, Matthias Weingart wrote: too. > Another hint to USB-FET's that solved some of my
weired problems: remove all
> usb-serial adapters from your system. It seems that there is a driver
> confusion when some of these are connected (FTDI).
>
> Matthias
>
> "Peter Grey" :
>
>> Al,
>>
>>
>>
>> One thing I did was upgrade the firmware on the FET. At one stage a year
>> or so ago I thought I had blown 2 FETs but it was going between 3
>> different computers and moving FETs about. I then decided to keep each
>> FET to their own computer. When I upgraded IAR, I found it would not
>> work and so upgraded the firmware and it was OK. I have now been doing
>> this on each PC. So far I have not lost a single FET. There is something
>> odd going on but I never seem to have the time to track it down. It is
>> usually once I get everything going that I am late with a project and
>> this takes priority. I am sure you know the situation!
>>
>>
>>
>> Peter
>>
>
>
> Yahoo Groups Links
On 11/02/2014 3:00 PM, Peter Grey wrote: > Al,
>
> One thing I did was upgrade the firmware on the FET. At one stage a
> year or so ago I thought I had blown 2 FETs but it was going between 3
> different computers and moving FETs about. I then decided to keep each
> FET to their own computer. When I upgraded IAR, I found it would not
> work and so upgraded the firmware and it was OK. I have now been doing
> this on each PC. So far I have not lost a single FET. There is
> something odd going on but I never seem to have the time to track it
> down. It is usually once I get everything going that I am late with a
> project and this takes priority. I am sure you know the situation!
>
> Peter
>
> *From:*m... [mailto:m...] *On
> Behalf Of *Onestone
> *Sent:* Tuesday, 11 February 2014 11:25 AM
> *To:* m...
> *Subject:* Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
>
> HERE WE GO AGAIN, GOT THE LICENCE SORTED. So finally got on to 5.60
> and what do I find? Well it now recognsies 2 hardware breakpoints on
> the 149, and gives the third as emulated. I could live with 2
> breakpoints very comfortably, but what the heck damn thing doesn't
> even recognise the second. Good thing though is that it doesn't crash,
> it just blows right through it. however it does give up and roll over
> if your in the debugger and try to set the third breakpoint.
>
> Enough already. bed time.
>
> Al
>
> On 11/02/2014 12:50 PM, Steve Mayfield wrote:
>
> I've had issues with the V3 FET software too...so I keep copies of
> the older HIL.DLL and MSP430.DLL files and then locate and replace
> the new versions after installing compilier updates.
>
> ----- Original Message -----
>
> *From:*Onestone *To:*m...
*Sent:*Monday, February 10, 2014 18:11
>
> *Subject:*Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
>
> I would pay for a decent assembler, but not the high costs for
> a compiler I don't want. I could go the Ti home tools route,
> but for unfathomable reasons their assembler syntax doesn't
> appear to be compatible with IARs, which is what I am more
> familiar with. I know the 149 should have 3 breakpoints but
> IAR is giving 1 + 2 emulated, which it took me a while to
> figure were causing the crashes. The trouble is that there are
> also other issues. The new versions want to update the FET
> debugger, then don't always complete succesfully. I've lost
2
> FET debuggers in a weekend. I'm loathe to move to another
> piece of software which you already say is buggy, and lose my
> last debugger. I will be totally screwed if that happens.
>
> Al
>
> On 11/02/2014 12:09 PM, Peter Grey wrote:
>
> Al,
>
> It has 3 breakpoints with a 149. I was getting odd
> behaviour with breakpoints at one stage and ended up
> downloading the latest version to get over it. I know the
> software if free so should not complain. I would not mind
> paying something for a more reliable version, but I guess
> there is no choice.
>
> Good luck
>
> Peter
>
> *From:*m...
>
> [mailto:m...] *On Behalf Of *Onestone
> *Sent:* Monday, 10 February 2014 3:36 PM
> *To:* m...
> *Subject:* Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
>
> Thanks Peter, can you recall how many breakpoints it
> allows with a 149, and what type they are? I'm kind of at
> a point where every time the program stops at the only
> working breakpoint I have to reset and reload the software
> so it is almost impossible to progress.
>
> Al
>
> On 10/02/2014 6:01 PM, Peter Grey wrote:
>
> Al
>
> I also downloaded the latest version from IAR, which
> needed a few back and forth comms with them. This was
> although I did this from the TI site. The version I
> downloaded was SLAC050at.zip. I have been using it fot
> some of the newer micros and also the older ones like
> the F149. The system gives a lot more errors than a
> few years ago. It is hard to define what is going on.
> I find that I have to have an external power supply or
> it fails. Like you I am using Windows XP. I have tried
> to run earlier versions but have never been able to do
> so. If I get to many crashes I get the latest version
> and it seems OK for a time. I have not had any issues
> with breakpoints.
>
> Cheers
>
> Peter
>
> *From:*m...
>
> [mailto:m...] *On Behalf Of *Onestone
> *Sent:* Monday, 10 February 2014 3:11 PM
> *To:* m...
>
> *Subject:* [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
>
> I've gone back to an older design to upgrade the
> software. The design uses an MSP430F149. A couple of
> months ago I upgraded Kickstarter to slac050aq, or
> version 5.52. It seemed to be OK for the newer micros
> I was working with, but now it seems to be behaving
> strangely. It won't revert to compiler mode from debug
> mode, it crashes. It doesn't seem to recognise or act
> on most breakpoints, if I try to modify a breakpoint
> it disappears upo its own butt, and hangs the system.
>
> Checking through I discover that it lists only the
> first breakpoint as hardware, and all others as
> emulated, and it can't hgandle the emulated
> breakpoints since the 149 doesn't have the advanced
> EEM module required.
>
> I tried to backstep to an older version (both slac050r
> and slac050x) but it bombed declaring it couldn't find
> a xerces-c dll file, which a search reveals is in
> common/bin. I'm running XP because I hate the options.
> Any ideas on how I can backstep or force the new
> version to recognise all 3 hardware breakpoints?
>
> Thanks
>
> Al
>
Reply by Matthias Weingart●February 11, 20142014-02-11
Another hint to USB-FET's that solved some of my weired problems: remove
all
usb-serial adapters from your system. It seems that there is a driver
confusion when some of these are connected (FTDI).
Matthias
"Peter Grey" :
> Al,
>
>
>
> One thing I did was upgrade the firmware on the FET. At one stage a year
> or so ago I thought I had blown 2 FETs but it was going between 3
> different computers and moving FETs about. I then decided to keep each
> FET to their own computer. When I upgraded IAR, I found it would not
> work and so upgraded the firmware and it was OK. I have now been doing
> this on each PC. So far I have not lost a single FET. There is something
> odd going on but I never seem to have the time to track it down. It is
> usually once I get everything going that I am late with a project and
> this takes priority. I am sure you know the situation!
>
>
>
> Peter
>
One thing I did was upgrade the firmware on the FET. At one stage a year or
so ago I thought I had blown 2 FETs but it was going between 3 different
computers and moving FETs about. I then decided to keep each FET to their
own computer. When I upgraded IAR, I found it would not work and so upgraded
the firmware and it was OK. I have now been doing this on each PC. So far I
have not lost a single FET. There is something odd going on but I never seem
to have the time to track it down. It is usually once I get everything going
that I am late with a project and this takes priority. I am sure you know
the situation!
Peter
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Tuesday, 11 February 2014 11:25 AM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
HERE WE GO AGAIN, GOT THE LICENCE SORTED. So finally got on to 5.60 and what
do I find? Well it now recognsies 2 hardware breakpoints on the 149, and
gives the third as emulated. I could live with 2 breakpoints very
comfortably, but what the heck damn thing doesn't even recognise the
second.
Good thing though is that it doesn't crash, it just blows right through
it.
however it does give up and roll over if your in the debugger and try to set
the third breakpoint.
Enough already. bed time.
Al
On 11/02/2014 12:50 PM, Steve Mayfield wrote:
I've had issues with the V3 FET software too...so I keep copies of the
older
HIL.DLL and MSP430.DLL files and then locate and replace the new versions
after installing compilier updates.
----- Original Message -----
From: Onestone
To: m...
Sent: Monday, February 10, 2014 18:11
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I would pay for a decent assembler, but not the high costs for a compiler I
don't want. I could go the Ti home tools route, but for unfathomable
reasons
their assembler syntax doesn't appear to be compatible with IARs, which
is
what I am more familiar with. I know the 149 should have 3 breakpoints but
IAR is giving 1 + 2 emulated, which it took me a while to figure were
causing the crashes. The trouble is that there are also other issues. The
new versions want to update the FET debugger, then don't always complete
succesfully. I've lost 2 FET debuggers in a weekend. I'm loathe to
move to
another piece of software which you already say is buggy, and lose my last
debugger. I will be totally screwed if that happens.
Al
On 11/02/2014 12:09 PM, Peter Grey wrote:
Al,
It has 3 breakpoints with a 149. I was getting odd behaviour with
breakpoints at one stage and ended up downloading the latest version to get
over it. I know the software if free so should not complain. I would not
mind paying something for a more reliable version, but I guess there is no
choice.
Good luck
Peter
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Monday, 10 February 2014 3:36 PM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
Thanks Peter, can you recall how many breakpoints it allows with a 149, and
what type they are? I'm kind of at a point where every time the program
stops at the only working breakpoint I have to reset and reload the software
so it is almost impossible to progress.
Al
On 10/02/2014 6:01 PM, Peter Grey wrote:
Al
I also downloaded the latest version from IAR, which needed a few back and
forth comms with them. This was although I did this from the TI site. The
version I downloaded was SLAC050at.zip. I have been using it fot some of the
newer micros and also the older ones like the F149. The system gives a lot
more errors than a few years ago. It is hard to define what is going on. I
find that I have to have an external power supply or it fails. Like you I am
using Windows XP. I have tried to run earlier versions but have never been
able to do so. If I get to many crashes I get the latest version and it
seems OK for a time. I have not had any issues with breakpoints.
Cheers
Peter
From: m... [mailto:m...] On Behalf Of
Onestone
Sent: Monday, 10 February 2014 3:11 PM
To: m...
Subject: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I've gone back to an older design to upgrade the software. The design
uses
an MSP430F149. A couple of months ago I upgraded Kickstarter to slac050aq,
or version 5.52. It seemed to be OK for the newer micros I was working with,
but now it seems to be behaving strangely. It won't revert to compiler
mode
from debug mode, it crashes. It doesn't seem to recognise or act on most
breakpoints, if I try to modify a breakpoint it disappears upo its own butt,
and hangs the system.
Checking through I discover that it lists only the first breakpoint as
hardware, and all others as emulated, and it can't hgandle the emulated
breakpoints since the 149 doesn't have the advanced EEM module required.
I tried to backstep to an older version (both slac050r and slac050x) but it
bombed declaring it couldn't find a xerces-c dll file, which a search
reveals is in common/bin. I'm running XP because I hate the options. Any
ideas on how I can backstep or force the new version to recognise all 3
hardware breakpoints?
Thanks
Al
Reply by Onestone●February 10, 20142014-02-10
HERE WE GO AGAIN, GOT THE LICENCE SORTED. So finally got on to 5.60 and
what do I find? Well it now recognsies 2 hardware breakpoints on the
149, and gives the third as emulated. I could live with 2 breakpoints
very comfortably, but what the heck damn thing doesn't even recognise
the second. Good thing though is that it doesn't crash, it just blows
right through it. however it does give up and roll over if your in the
debugger and try to set the third breakpoint.
Enough already. bed time.
Al
On 11/02/2014 12:50 PM, Steve Mayfield wrote: > I've had issues with the V3 FET software
too...so I keep copies of the
> older HIL.DLL and MSP430.DLL files and then locate and replace the new
> versions after installing compilier updates.
>
> ----- Original Message -----
> *From:* Onestone
> *To:* m...
> *Sent:* Monday, February 10, 2014 18:11
> *Subject:* Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
>
> I would pay for a decent assembler, but not the high costs for a
> compiler I don't want. I could go the Ti home tools route, but for
> unfathomable reasons their assembler syntax doesn't appear to be
> compatible with IARs, which is what I am more familiar with. I
> know the 149 should have 3 breakpoints but IAR is giving 1 + 2
> emulated, which it took me a while to figure were causing the
> crashes. The trouble is that there are also other issues. The new
> versions want to update the FET debugger, then don't always
> complete succesfully. I've lost 2 FET debuggers in a weekend.
I'm
> loathe to move to another piece of software which you already say
> is buggy, and lose my last debugger. I will be totally screwed if
> that happens.
>
> Al
>
> On 11/02/2014 12:09 PM, Peter Grey wrote:
>>
>> Al,
>>
>> It has 3 breakpoints with a 149. I was getting odd behaviour
>> with breakpoints at one stage and ended up downloading the latest
>> version to get over it. I know the software if free so should not
>> complain. I would not mind paying something for a more reliable
>> version, but I guess there is no choice.
>>
>> Good luck
>>
>> Peter
>>
>> *From:*m... [mailto:m...] *On
>> Behalf Of *Onestone
>> *Sent:* Monday, 10 February 2014 3:36 PM
>> *To:* m...
>> *Subject:* Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
>>
>> Thanks Peter, can you recall how many breakpoints it allows with
>> a 149, and what type they are? I'm kind of at a point where every
>> time the program stops at the only working breakpoint I have to
>> reset and reload the software so it is almost impossible to progress.
>>
>> Al
>>
>> On 10/02/2014 6:01 PM, Peter Grey wrote:
>>
>> Al
>>
>> I also downloaded the latest version from IAR, which needed a
>> few back and forth comms with them. This was although I did
>> this from the TI site. The version I downloaded was
>> SLAC050at.zip. I have been using it fot some of the newer
>> micros and also the older ones like the F149. The system
>> gives a lot more errors than a few years ago. It is hard to
>> define what is going on. I find that I have to have an
>> external power supply or it fails. Like you I am using
>> Windows XP. I have tried to run earlier versions but have
>> never been able to do so. If I get to many crashes I get the
>> latest version and it seems OK for a time. I have not had any
>> issues with breakpoints.
>>
>> Cheers
>>
>> Peter
>>
>> *From:*m...
>> [mailto:m...] *On Behalf Of *Onestone
>> *Sent:* Monday, 10 February 2014 3:11 PM
>> *To:* m...
>> *Subject:* [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
>>
>> I've gone back to an older design to upgrade the software.
>> The design uses an MSP430F149. A couple of months ago I
>> upgraded Kickstarter to slac050aq, or version 5.52. It seemed
>> to be OK for the newer micros I was working with, but now it
>> seems to be behaving strangely. It won't revert to compiler
>> mode from debug mode, it crashes. It doesn't seem to
>> recognise or act on most breakpoints, if I try to modify a
>> breakpoint it disappears upo its own butt, and hangs the system.
>>
>> Checking through I discover that it lists only the first
>> breakpoint as hardware, and all others as emulated, and it
>> can't hgandle the emulated breakpoints since the 149
doesn't
>> have the advanced EEM module required.
>>
>> I tried to backstep to an older version (both slac050r and
>> slac050x) but it bombed declaring it couldn't find a xerces-c
>> dll file, which a search reveals is in common/bin. I'm
>> running XP because I hate the options. Any ideas on how I can
>> backstep or force the new version to recognise all 3 hardware
>> breakpoints?
>>
>> Thanks
>>
>> Al
>>
>>
>
Reply by Steve Mayfield●February 10, 20142014-02-10
I've had issues with the V3 FET software too...so I keep copies of the
older HIL.DLL and MSP430.DLL files and then locate and replace the new versions
after installing compilier updates.
----- Original Message -----
From: Onestone
To: m...
Sent: Monday, February 10, 2014 18:11
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I would pay for a decent assembler, but not the high costs for a compiler I
don't want. I could go the Ti home tools route, but for unfathomable
reasons their assembler syntax doesn't appear to be compatible with IARs,
which is what I am more familiar with. I know the 149 should have 3 breakpoints
but IAR is giving 1 + 2 emulated, which it took me a while to figure were
causing the crashes. The trouble is that there are also other issues. The new
versions want to update the FET debugger, then don't always complete
succesfully. I've lost 2 FET debuggers in a weekend. I'm loathe to
move to another piece of software which you already say is buggy, and lose my
last debugger. I will be totally screwed if that happens.
Al
On 11/02/2014 12:09 PM, Peter Grey wrote:
Al,
It has 3 breakpoints with a 149. I was getting odd behaviour with
breakpoints at one stage and ended up downloading the latest version to get over
it. I know the software if free so should not complain. I would not mind paying
something for a more reliable version, but I guess there is no choice.
Good luck
Peter
From: m... [mailto:m...] On Behalf Of Onestone
Sent: Monday, 10 February 2014 3:36 PM
To: m...
Subject: Re: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
Thanks Peter, can you recall how many breakpoints it allows with a 149, and
what type they are? I'm kind of at a point where every time the program
stops at the only working breakpoint I have to reset and reload the software so
it is almost impossible to progress.
Al
On 10/02/2014 6:01 PM, Peter Grey wrote:
Al
I also downloaded the latest version from IAR, which needed a few back and
forth comms with them. This was although I did this from the TI site. The
version I downloaded was SLAC050at.zip. I have been using it fot some of the
newer micros and also the older ones like the F149. The system gives a lot more
errors than a few years ago. It is hard to define what is going on. I find that
I have to have an external power supply or it fails. Like you I am using Windows
XP. I have tried to run earlier versions but have never been able to do so. If I
get to many crashes I get the latest version and it seems OK for a time. I have
not had any issues with breakpoints.
Cheers
Peter
From: m... [mailto:m...] On Behalf Of Onestone
Sent: Monday, 10 February 2014 3:11 PM
To: m...
Subject: [msp430] WEIRD BEHAVIOUR OF IAR (YET AGAIN)
I've gone back to an older design to upgrade the software. The design
uses an MSP430F149. A couple of months ago I upgraded Kickstarter to slac050aq,
or version 5.52. It seemed to be OK for the newer micros I was working with, but
now it seems to be behaving strangely. It won't revert to compiler mode
from debug mode, it crashes. It doesn't seem to recognise or act on most
breakpoints, if I try to modify a breakpoint it disappears upo its own butt, and
hangs the system.
Checking through I discover that it lists only the first breakpoint as
hardware, and all others as emulated, and it can't hgandle the emulated
breakpoints since the 149 doesn't have the advanced EEM module required.
I tried to backstep to an older version (both slac050r and slac050x) but
it bombed declaring it couldn't find a xerces-c dll file, which a search
reveals is in common/bin. I'm running XP because I hate the options. Any
ideas on how I can backstep or force the new version to recognise all 3 hardware
breakpoints?
