Has anybody else here encountered the following messages under IAR? This
is behaviour that I found only after moving from slac050l to versions
after slac050q a couple of days ago. I am currently trying to use
slac050r, as I need this for the latest micros, and i consistently get
this message. The appropriate *.d43 file is produced, in the correct
directory. The first pair of messages are from the debug window. The
error message when I try to download is:-
The debuggiing session could not be started.
Either the debugger initialisation failed or else the file " E:\CLIENT
PROJECTS\...\Debug\Exe\MS_V0.d43" was corrupt or of an unsupported format.
There might be more information in the Debug window.
Of course there is nothing else there that is helpful. I can find
nothing meaningful in the docs, the same thing occurs on boards that ran
happily before 'upgrading'. My project configuration hasn't
changed,
other than when I tried various options for thew linker to try and get
the damned thing going
Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
PROJECTS\...\Debug\Exe\MS_V0.d43
Cheers
Al
WEIRD IAR STUFF
Started by ●May 24, 2008
Reply by ●May 24, 20082008-05-24
did you get any error message number (ex: Error[e12]:)?
I don't know it will be useful or not ,below is a IAR technical note on upgradation,
http://supp.iar.com/Support/?note@394&from=note+21914
----- Original Message ----
From: Onestone
To: m...
Sent: Saturday, May 24, 2008 6:18:33 PM
Subject: [msp430] WEIRD IAR STUFF
Has anybody else here encountered the following messages under IAR? This
is behaviour that I found only after moving from slac050l to versions
after slac050q a couple of days ago. I am currently trying to use
slac050r, as I need this for the latest micros, and i consistently get
this message. The appropriate *.d43 file is produced, in the correct
directory. The first pair of messages are from the debug window. The
error message when I try to download is:-
The debuggiing session could not be started.
Either the debugger initialisation failed or else the file " E:\CLIENT
PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an unsupported format.
There might be more information in the Debug window.
Of course there is nothing else there that is helpful. I can find
nothing meaningful in the docs, the same thing occurs on boards that ran
happily before 'upgrading'. My project configuration hasn't changed,
other than when I tried various options for thew linker to try and get
the damned thing going
Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
PROJECTS\... \Debug\Exe\ MS_V0.d43
Cheers
Al
I don't know it will be useful or not ,below is a IAR technical note on upgradation,
http://supp.iar.com/Support/?note@394&from=note+21914
----- Original Message ----
From: Onestone
To: m...
Sent: Saturday, May 24, 2008 6:18:33 PM
Subject: [msp430] WEIRD IAR STUFF
Has anybody else here encountered the following messages under IAR? This
is behaviour that I found only after moving from slac050l to versions
after slac050q a couple of days ago. I am currently trying to use
slac050r, as I need this for the latest micros, and i consistently get
this message. The appropriate *.d43 file is produced, in the correct
directory. The first pair of messages are from the debug window. The
error message when I try to download is:-
The debuggiing session could not be started.
Either the debugger initialisation failed or else the file " E:\CLIENT
PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an unsupported format.
There might be more information in the Debug window.
Of course there is nothing else there that is helpful. I can find
nothing meaningful in the docs, the same thing occurs on boards that ran
happily before 'upgrading'. My project configuration hasn't changed,
other than when I tried various options for thew linker to try and get
the damned thing going
Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
PROJECTS\... \Debug\Exe\ MS_V0.d43
Cheers
Al
Reply by ●May 24, 20082008-05-24
NOpe, I listed exactly what the pogram reported to me. More on this. I
can duplicate this by removing the jtag connector. The same gets
reported. So it seems like this is the stupid message that IAR now gives
when there is nothing hooked up to it. However exactly the same board,
programming connector and cable work on slac050l, provided I accept the
different micro. slac050q/r don't even get that far. Even weirder is
that it seemed to work at fist. I've done a re-install twice, even
manually clearing out every scrap of IAR I could find, that too hasn't
helped.
thansk for the effort anyway.
Al
Paddu Koti wrote:
>did you get any error message number (ex: Error[e12]:)?
>I don't know it will be useful or not ,below is a IAR technical note on upgradation,
>http://supp.iar.com/Support/?note@394&from=note+21914
>
>----- Original Message ----
>From: Onestone
>To: m...
>Sent: Saturday, May 24, 2008 6:18:33 PM
>Subject: [msp430] WEIRD IAR STUFF
>Has anybody else here encountered the following messages under IAR? This
>is behaviour that I found only after moving from slac050l to versions
>after slac050q a couple of days ago. I am currently trying to use
>slac050r, as I need this for the latest micros, and i consistently get
>this message. The appropriate *.d43 file is produced, in the correct
>directory. The first pair of messages are from the debug window. The
>error message when I try to download is:-
>
>The debuggiing session could not be started.
>Either the debugger initialisation failed or else the file " E:\CLIENT
>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an unsupported format.
>There might be more information in the Debug window.
>
>Of course there is nothing else there that is helpful. I can find
>nothing meaningful in the docs, the same thing occurs on boards that ran
>happily before 'upgrading'. My project configuration hasn't changed,
>other than when I tried various options for thew linker to try and get
>the damned thing going
>
>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>PROJECTS\... \Debug\Exe\ MS_V0.d43
>
>Cheers
>
>Al
>
>
>
>
can duplicate this by removing the jtag connector. The same gets
reported. So it seems like this is the stupid message that IAR now gives
when there is nothing hooked up to it. However exactly the same board,
programming connector and cable work on slac050l, provided I accept the
different micro. slac050q/r don't even get that far. Even weirder is
that it seemed to work at fist. I've done a re-install twice, even
manually clearing out every scrap of IAR I could find, that too hasn't
helped.
thansk for the effort anyway.
Al
Paddu Koti wrote:
>did you get any error message number (ex: Error[e12]:)?
>I don't know it will be useful or not ,below is a IAR technical note on upgradation,
>http://supp.iar.com/Support/?note@394&from=note+21914
>
>----- Original Message ----
>From: Onestone
>To: m...
>Sent: Saturday, May 24, 2008 6:18:33 PM
>Subject: [msp430] WEIRD IAR STUFF
>Has anybody else here encountered the following messages under IAR? This
>is behaviour that I found only after moving from slac050l to versions
>after slac050q a couple of days ago. I am currently trying to use
>slac050r, as I need this for the latest micros, and i consistently get
>this message. The appropriate *.d43 file is produced, in the correct
>directory. The first pair of messages are from the debug window. The
>error message when I try to download is:-
>
>The debuggiing session could not be started.
>Either the debugger initialisation failed or else the file " E:\CLIENT
>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an unsupported format.
>There might be more information in the Debug window.
>
>Of course there is nothing else there that is helpful. I can find
>nothing meaningful in the docs, the same thing occurs on boards that ran
>happily before 'upgrading'. My project configuration hasn't changed,
>other than when I tried various options for thew linker to try and get
>the damned thing going
>
>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>PROJECTS\... \Debug\Exe\ MS_V0.d43
>
>Cheers
>
>Al
>
>
>
>
Reply by ●May 24, 20082008-05-24
I've seen this error message using the USB FET Tool with a board
specific to the newest patch v4.10E. When I switched to the parallel
FET Tool the problem went away. I didn't have time to look into it
further, so I left it as that. You are also correct in that if you
don't have ANY FET Tool connected (or lack of power, although
sometimes it is generous enough to tell you voltage is too low), you
can get this message as well.
As a side note, I have noticed a few issues with the USB FET Tool
(although they seem to be getting fixed in later firmware versions)
and therefore I don't trust it fully yet. The parallel FET Tool,
although slower on the download, performs flawlessly as far as I have
seen. However, isn't it nice to have multiple USB FET Tools connected
to the same computer all running at once? It's not as easy to do that
with the Parallel FET Tool, is it?
darkwzrd00
--- In m..., Onestone wrote:
>
> NOpe, I listed exactly what the pogram reported to me. More on
this. I
> can duplicate this by removing the jtag connector. The same gets
> reported. So it seems like this is the stupid message that IAR now
gives
> when there is nothing hooked up to it. However exactly the same
board,
> programming connector and cable work on slac050l, provided I accept
the
> different micro. slac050q/r don't even get that far. Even weirder
is
> that it seemed to work at fist. I've done a re-install twice, even
> manually clearing out every scrap of IAR I could find, that too
hasn't
> helped.
>
> thansk for the effort anyway.
>
> Al
>
> Paddu Koti wrote:
>
> >did you get any error message number (ex: Error[e12]:)?
> >I don't know it will be useful or not ,below is a IAR technical
note on upgradation,
> >http://supp.iar.com/Support/?note@394&from=note+21914
> >
> >
> >
> >----- Original Message ----
> >From: Onestone
> >To: m...
> >Sent: Saturday, May 24, 2008 6:18:33 PM
> >Subject: [msp430] WEIRD IAR STUFF
> >
> >
> >Has anybody else here encountered the following messages under
IAR? This
> >is behaviour that I found only after moving from slac050l to
versions
> >after slac050q a couple of days ago. I am currently trying to use
> >slac050r, as I need this for the latest micros, and i consistently
get
> >this message. The appropriate *.d43 file is produced, in the
correct
> >directory. The first pair of messages are from the debug window.
The
> >error message when I try to download is:-
> >
> >The debuggiing session could not be started.
> >Either the debugger initialisation failed or else the file "
E:\CLIENT
> >PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
unsupported format.
> >There might be more information in the Debug window.
> >
> >Of course there is nothing else there that is helpful. I can find
> >nothing meaningful in the docs, the same thing occurs on boards
that ran
> >happily before 'upgrading'. My project configuration hasn't
changed,
> >other than when I tried various options for thew linker to try and
get
> >the damned thing going
> >
> >Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
> >Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
> >PROJECTS\... \Debug\Exe\ MS_V0.d43
> >
> >Cheers
> >
> >Al
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
specific to the newest patch v4.10E. When I switched to the parallel
FET Tool the problem went away. I didn't have time to look into it
further, so I left it as that. You are also correct in that if you
don't have ANY FET Tool connected (or lack of power, although
sometimes it is generous enough to tell you voltage is too low), you
can get this message as well.
As a side note, I have noticed a few issues with the USB FET Tool
(although they seem to be getting fixed in later firmware versions)
and therefore I don't trust it fully yet. The parallel FET Tool,
although slower on the download, performs flawlessly as far as I have
seen. However, isn't it nice to have multiple USB FET Tools connected
to the same computer all running at once? It's not as easy to do that
with the Parallel FET Tool, is it?
darkwzrd00
--- In m..., Onestone wrote:
>
> NOpe, I listed exactly what the pogram reported to me. More on
this. I
> can duplicate this by removing the jtag connector. The same gets
> reported. So it seems like this is the stupid message that IAR now
gives
> when there is nothing hooked up to it. However exactly the same
board,
> programming connector and cable work on slac050l, provided I accept
the
> different micro. slac050q/r don't even get that far. Even weirder
is
> that it seemed to work at fist. I've done a re-install twice, even
> manually clearing out every scrap of IAR I could find, that too
hasn't
> helped.
>
> thansk for the effort anyway.
>
> Al
>
> Paddu Koti wrote:
>
> >did you get any error message number (ex: Error[e12]:)?
> >I don't know it will be useful or not ,below is a IAR technical
note on upgradation,
> >http://supp.iar.com/Support/?note@394&from=note+21914
> >
> >
> >
> >----- Original Message ----
> >From: Onestone
> >To: m...
> >Sent: Saturday, May 24, 2008 6:18:33 PM
> >Subject: [msp430] WEIRD IAR STUFF
> >
> >
> >Has anybody else here encountered the following messages under
IAR? This
> >is behaviour that I found only after moving from slac050l to
versions
> >after slac050q a couple of days ago. I am currently trying to use
> >slac050r, as I need this for the latest micros, and i consistently
get
> >this message. The appropriate *.d43 file is produced, in the
correct
> >directory. The first pair of messages are from the debug window.
The
> >error message when I try to download is:-
> >
> >The debuggiing session could not be started.
> >Either the debugger initialisation failed or else the file "
E:\CLIENT
> >PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
unsupported format.
> >There might be more information in the Debug window.
> >
> >Of course there is nothing else there that is helpful. I can find
> >nothing meaningful in the docs, the same thing occurs on boards
that ran
> >happily before 'upgrading'. My project configuration hasn't
changed,
> >other than when I tried various options for thew linker to try and
get
> >the damned thing going
> >
> >Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
> >Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
> >PROJECTS\... \Debug\Exe\ MS_V0.d43
> >
> >Cheers
> >
> >Al
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
Reply by ●May 24, 20082008-05-24
hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL fet
TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT, IN
FACT, (whoops fingers0 i had as much trouble with that with flaky
behaviour as I didi with this one. Similar sort of thing, often the
computer would need to be reset or even IAR reloaded if I forgot to hold
the power button down on a self powered unit. That didi get a little
better over time, but never fully disappearred.
Up until now I have found the USB tool better than the old parallel one,
except that when I have been running the USB EZ430-2013 dongle I always
seem to have issues with downloads too. I have ran two instances of IAR
a couple of times, but i actuall don't like doing it. I like to reserve
my whole display for one program. It makes it easier to read. I used to
have several PC's running different applications often, but am down to
my last ancient PC, band-aided together and staggering along on a Zimmer
frame, so two windows it is.
It's hard to complain about a free tool, except that I alwasy remember
the MPLAB free tool as running far more smoothly than this one
does.Although I haven't used it in anger for a while.
Cheers
Al
darkwzrd00 wrote:
>I've seen this error message using the USB FET Tool with a board
>specific to the newest patch v4.10E. When I switched to the parallel
>FET Tool the problem went away. I didn't have time to look into it
>further, so I left it as that. You are also correct in that if you
>don't have ANY FET Tool connected (or lack of power, although
>sometimes it is generous enough to tell you voltage is too low), you
>can get this message as well.
>
>As a side note, I have noticed a few issues with the USB FET Tool
>(although they seem to be getting fixed in later firmware versions)
>and therefore I don't trust it fully yet. The parallel FET Tool,
>although slower on the download, performs flawlessly as far as I have
>seen. However, isn't it nice to have multiple USB FET Tools connected
>to the same computer all running at once? It's not as easy to do that
>with the Parallel FET Tool, is it?
>
>darkwzrd00
>--- In m..., Onestone wrote:
>
>
>>NOpe, I listed exactly what the pogram reported to me. More on
>>
>>
>this. I
>
>
>>can duplicate this by removing the jtag connector. The same gets
>>reported. So it seems like this is the stupid message that IAR now
>>
>>
>gives
>
>
>>when there is nothing hooked up to it. However exactly the same
>>
>>
>board,
>
>
>>programming connector and cable work on slac050l, provided I accept
>>
>>
>the
>
>
>>different micro. slac050q/r don't even get that far. Even weirder
>>
>>
>is
>
>
>>that it seemed to work at fist. I've done a re-install twice, even
>>manually clearing out every scrap of IAR I could find, that too
>>
>>
>hasn't
>
>
>>helped.
>>
>>thansk for the effort anyway.
>>
>>Al
>>
>>Paddu Koti wrote:
>>
>>
>>
>>>did you get any error message number (ex: Error[e12]:)?
>>>I don't know it will be useful or not ,below is a IAR technical
>>>
>>>
>note on upgradation,
>
>
>>>http://supp.iar.com/Support/?note@394&from=note+21914
>>>
>>>
>>>
>>>----- Original Message ----
>>>From: Onestone
>>>To: m...
>>>Sent: Saturday, May 24, 2008 6:18:33 PM
>>>Subject: [msp430] WEIRD IAR STUFF
>>>
>>>
>>>Has anybody else here encountered the following messages under
>>>
>>>
>IAR? This
>
>
>>>is behaviour that I found only after moving from slac050l to
>>>
>>>
>versions
>
>
>>>after slac050q a couple of days ago. I am currently trying to use
>>>slac050r, as I need this for the latest micros, and i consistently
>>>
>>>
>get
>
>
>>>this message. The appropriate *.d43 file is produced, in the
>>>
>>>
>correct
>
>
>>>directory. The first pair of messages are from the debug window.
>>>
>>>
>The
>
>
>>>error message when I try to download is:-
>>>
>>>The debuggiing session could not be started.
>>>Either the debugger initialisation failed or else the file "
>>>
>>>
>E:\CLIENT
>
>
>>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
>>>
>>>
>unsupported format.
>
>
>>>There might be more information in the Debug window.
>>>
>>>Of course there is nothing else there that is helpful. I can find
>>>nothing meaningful in the docs, the same thing occurs on boards
>>>
>>>
>that ran
>
>
>>>happily before 'upgrading'. My project configuration hasn't
>>>
>>>
>changed,
>
>
>>>other than when I tried various options for thew linker to try and
>>>
>>>
>get
>
>
>>>the damned thing going
>>>
>>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>>>PROJECTS\... \Debug\Exe\ MS_V0.d43
>>>
>>>Cheers
>>>
>>>Al
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT, IN
FACT, (whoops fingers0 i had as much trouble with that with flaky
behaviour as I didi with this one. Similar sort of thing, often the
computer would need to be reset or even IAR reloaded if I forgot to hold
the power button down on a self powered unit. That didi get a little
better over time, but never fully disappearred.
Up until now I have found the USB tool better than the old parallel one,
except that when I have been running the USB EZ430-2013 dongle I always
seem to have issues with downloads too. I have ran two instances of IAR
a couple of times, but i actuall don't like doing it. I like to reserve
my whole display for one program. It makes it easier to read. I used to
have several PC's running different applications often, but am down to
my last ancient PC, band-aided together and staggering along on a Zimmer
frame, so two windows it is.
It's hard to complain about a free tool, except that I alwasy remember
the MPLAB free tool as running far more smoothly than this one
does.Although I haven't used it in anger for a while.
Cheers
Al
darkwzrd00 wrote:
>I've seen this error message using the USB FET Tool with a board
>specific to the newest patch v4.10E. When I switched to the parallel
>FET Tool the problem went away. I didn't have time to look into it
>further, so I left it as that. You are also correct in that if you
>don't have ANY FET Tool connected (or lack of power, although
>sometimes it is generous enough to tell you voltage is too low), you
>can get this message as well.
>
>As a side note, I have noticed a few issues with the USB FET Tool
>(although they seem to be getting fixed in later firmware versions)
>and therefore I don't trust it fully yet. The parallel FET Tool,
>although slower on the download, performs flawlessly as far as I have
>seen. However, isn't it nice to have multiple USB FET Tools connected
>to the same computer all running at once? It's not as easy to do that
>with the Parallel FET Tool, is it?
>
>darkwzrd00
>--- In m..., Onestone wrote:
>
>
>>NOpe, I listed exactly what the pogram reported to me. More on
>>
>>
>this. I
>
>
>>can duplicate this by removing the jtag connector. The same gets
>>reported. So it seems like this is the stupid message that IAR now
>>
>>
>gives
>
>
>>when there is nothing hooked up to it. However exactly the same
>>
>>
>board,
>
>
>>programming connector and cable work on slac050l, provided I accept
>>
>>
>the
>
>
>>different micro. slac050q/r don't even get that far. Even weirder
>>
>>
>is
>
>
>>that it seemed to work at fist. I've done a re-install twice, even
>>manually clearing out every scrap of IAR I could find, that too
>>
>>
>hasn't
>
>
>>helped.
>>
>>thansk for the effort anyway.
>>
>>Al
>>
>>Paddu Koti wrote:
>>
>>
>>
>>>did you get any error message number (ex: Error[e12]:)?
>>>I don't know it will be useful or not ,below is a IAR technical
>>>
>>>
>note on upgradation,
>
>
>>>http://supp.iar.com/Support/?note@394&from=note+21914
>>>
>>>
>>>
>>>----- Original Message ----
>>>From: Onestone
>>>To: m...
>>>Sent: Saturday, May 24, 2008 6:18:33 PM
>>>Subject: [msp430] WEIRD IAR STUFF
>>>
>>>
>>>Has anybody else here encountered the following messages under
>>>
>>>
>IAR? This
>
>
>>>is behaviour that I found only after moving from slac050l to
>>>
>>>
>versions
>
>
>>>after slac050q a couple of days ago. I am currently trying to use
>>>slac050r, as I need this for the latest micros, and i consistently
>>>
>>>
>get
>
>
>>>this message. The appropriate *.d43 file is produced, in the
>>>
>>>
>correct
>
>
>>>directory. The first pair of messages are from the debug window.
>>>
>>>
>The
>
>
>>>error message when I try to download is:-
>>>
>>>The debuggiing session could not be started.
>>>Either the debugger initialisation failed or else the file "
>>>
>>>
>E:\CLIENT
>
>
>>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
>>>
>>>
>unsupported format.
>
>
>>>There might be more information in the Debug window.
>>>
>>>Of course there is nothing else there that is helpful. I can find
>>>nothing meaningful in the docs, the same thing occurs on boards
>>>
>>>
>that ran
>
>
>>>happily before 'upgrading'. My project configuration hasn't
>>>
>>>
>changed,
>
>
>>>other than when I tried various options for thew linker to try and
>>>
>>>
>get
>
>
>>>the damned thing going
>>>
>>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>>>PROJECTS\... \Debug\Exe\ MS_V0.d43
>>>
>>>Cheers
>>>
>>>Al
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
Reply by ●May 24, 20082008-05-24
I tend to be working on more than one project at once, which is why I
use multiple instances of IAR. Granted, there is one very annoying
issue I run into a lot when running more than one instance of IAR
simultaneously. It has to do with the stupid lisence dongle (I doubt
any of you are surprised to hear that).
Let's assume that I have 3 windows of IAR open. I can compile all
three without issue. However, if I connect to one device, and then
try to connect to another, sometimes IAR complains that it cannot
find my dongle. In order to "fix" the problem, I have to close (not
just disconnect from the target) from the project that was running.
It can take a little bit of finesse to get all three instances
connected and running. If anyone has a solution to this, please let
me know as it drives me nuts.
Because of this issue, I have only tried 3 at once.
darkwzrd00
--- In m..., Onestone wrote:
>
> hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL
fet
> TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT,
IN
> FACT, (whoops fingers0 i had as much trouble with that with flaky
> behaviour as I didi with this one. Similar sort of thing, often the
> computer would need to be reset or even IAR reloaded if I forgot to
hold
> the power button down on a self powered unit. That didi get a
little
> better over time, but never fully disappearred.
>
> Up until now I have found the USB tool better than the old parallel
one,
> except that when I have been running the USB EZ430-2013 dongle I
always
> seem to have issues with downloads too. I have ran two instances of
IAR
> a couple of times, but i actuall don't like doing it. I like to
reserve
> my whole display for one program. It makes it easier to read. I
used to
> have several PC's running different applications often, but am down
to
> my last ancient PC, band-aided together and staggering along on a
Zimmer
> frame, so two windows it is.
>
> It's hard to complain about a free tool, except that I alwasy
remember
> the MPLAB free tool as running far more smoothly than this one
> does.Although I haven't used it in anger for a while.
>
> Cheers
>
> Al
>
> darkwzrd00 wrote:
>
> >I've seen this error message using the USB FET Tool with a board
> >specific to the newest patch v4.10E. When I switched to the
parallel
> >FET Tool the problem went away. I didn't have time to look into it
> >further, so I left it as that. You are also correct in that if you
> >don't have ANY FET Tool connected (or lack of power, although
> >sometimes it is generous enough to tell you voltage is too low),
you
> >can get this message as well.
> >
> >As a side note, I have noticed a few issues with the USB FET Tool
> >(although they seem to be getting fixed in later firmware
versions)
> >and therefore I don't trust it fully yet. The parallel FET Tool,
> >although slower on the download, performs flawlessly as far as I
have
> >seen. However, isn't it nice to have multiple USB FET Tools
connected
> >to the same computer all running at once? It's not as easy to do
that
> >with the Parallel FET Tool, is it?
> >
> >darkwzrd00
> >
> >
> >--- In m..., Onestone wrote:
> >
> >
> >>NOpe, I listed exactly what the pogram reported to me. More on
> >>
> >>
> >this. I
> >
> >
> >>can duplicate this by removing the jtag connector. The same gets
> >>reported. So it seems like this is the stupid message that IAR
now
> >>
> >>
> >gives
> >
> >
> >>when there is nothing hooked up to it. However exactly the same
> >>
> >>
> >board,
> >
> >
> >>programming connector and cable work on slac050l, provided I
accept
> >>
> >>
> >the
> >
> >
> >>different micro. slac050q/r don't even get that far. Even weirder
> >>
> >>
> >is
> >
> >
> >>that it seemed to work at fist. I've done a re-install twice,
even
> >>manually clearing out every scrap of IAR I could find, that too
> >>
> >>
> >hasn't
> >
> >
> >>helped.
> >>
> >>thansk for the effort anyway.
> >>
> >>Al
> >>
> >>Paddu Koti wrote:
> >>
> >>
> >>
> >>>did you get any error message number (ex: Error[e12]:)?
> >>>I don't know it will be useful or not ,below is a IAR technical
> >>>
> >>>
> >note on upgradation,
> >
> >
> >>>http://supp.iar.com/Support/?note@394&from=note+21914
> >>>
> >>>
> >>>
> >>>----- Original Message ----
> >>>From: Onestone
> >>>To: m...
> >>>Sent: Saturday, May 24, 2008 6:18:33 PM
> >>>Subject: [msp430] WEIRD IAR STUFF
> >>>
> >>>
> >>>Has anybody else here encountered the following messages under
> >>>
> >>>
> >IAR? This
> >
> >
> >>>is behaviour that I found only after moving from slac050l to
> >>>
> >>>
> >versions
> >
> >
> >>>after slac050q a couple of days ago. I am currently trying to
use
> >>>slac050r, as I need this for the latest micros, and i
consistently
> >>>
> >>>
> >get
> >
> >
> >>>this message. The appropriate *.d43 file is produced, in the
> >>>
> >>>
> >correct
> >
> >
> >>>directory. The first pair of messages are from the debug window.
> >>>
> >>>
> >The
> >
> >
> >>>error message when I try to download is:-
> >>>
> >>>The debuggiing session could not be started.
> >>>Either the debugger initialisation failed or else the file "
> >>>
> >>>
> >E:\CLIENT
> >
> >
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
> >>>
> >>>
> >unsupported format.
> >
> >
> >>>There might be more information in the Debug window.
> >>>
> >>>Of course there is nothing else there that is helpful. I can
find
> >>>nothing meaningful in the docs, the same thing occurs on boards
> >>>
> >>>
> >that ran
> >
> >
> >>>happily before 'upgrading'. My project configuration hasn't
> >>>
> >>>
> >changed,
> >
> >
> >>>other than when I tried various options for thew linker to try
and
> >>>
> >>>
> >get
> >
> >
> >>>the damned thing going
> >>>
> >>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
> >>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43
> >>>
> >>>Cheers
> >>>
> >>>Al
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
use multiple instances of IAR. Granted, there is one very annoying
issue I run into a lot when running more than one instance of IAR
simultaneously. It has to do with the stupid lisence dongle (I doubt
any of you are surprised to hear that).
Let's assume that I have 3 windows of IAR open. I can compile all
three without issue. However, if I connect to one device, and then
try to connect to another, sometimes IAR complains that it cannot
find my dongle. In order to "fix" the problem, I have to close (not
just disconnect from the target) from the project that was running.
It can take a little bit of finesse to get all three instances
connected and running. If anyone has a solution to this, please let
me know as it drives me nuts.
Because of this issue, I have only tried 3 at once.
darkwzrd00
--- In m..., Onestone wrote:
>
> hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL
fet
> TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT,
IN
> FACT, (whoops fingers0 i had as much trouble with that with flaky
> behaviour as I didi with this one. Similar sort of thing, often the
> computer would need to be reset or even IAR reloaded if I forgot to
hold
> the power button down on a self powered unit. That didi get a
little
> better over time, but never fully disappearred.
>
> Up until now I have found the USB tool better than the old parallel
one,
> except that when I have been running the USB EZ430-2013 dongle I
always
> seem to have issues with downloads too. I have ran two instances of
IAR
> a couple of times, but i actuall don't like doing it. I like to
reserve
> my whole display for one program. It makes it easier to read. I
used to
> have several PC's running different applications often, but am down
to
> my last ancient PC, band-aided together and staggering along on a
Zimmer
> frame, so two windows it is.
>
> It's hard to complain about a free tool, except that I alwasy
remember
> the MPLAB free tool as running far more smoothly than this one
> does.Although I haven't used it in anger for a while.
>
> Cheers
>
> Al
>
> darkwzrd00 wrote:
>
> >I've seen this error message using the USB FET Tool with a board
> >specific to the newest patch v4.10E. When I switched to the
parallel
> >FET Tool the problem went away. I didn't have time to look into it
> >further, so I left it as that. You are also correct in that if you
> >don't have ANY FET Tool connected (or lack of power, although
> >sometimes it is generous enough to tell you voltage is too low),
you
> >can get this message as well.
> >
> >As a side note, I have noticed a few issues with the USB FET Tool
> >(although they seem to be getting fixed in later firmware
versions)
> >and therefore I don't trust it fully yet. The parallel FET Tool,
> >although slower on the download, performs flawlessly as far as I
have
> >seen. However, isn't it nice to have multiple USB FET Tools
connected
> >to the same computer all running at once? It's not as easy to do
that
> >with the Parallel FET Tool, is it?
> >
> >darkwzrd00
> >
> >
> >--- In m..., Onestone wrote:
> >
> >
> >>NOpe, I listed exactly what the pogram reported to me. More on
> >>
> >>
> >this. I
> >
> >
> >>can duplicate this by removing the jtag connector. The same gets
> >>reported. So it seems like this is the stupid message that IAR
now
> >>
> >>
> >gives
> >
> >
> >>when there is nothing hooked up to it. However exactly the same
> >>
> >>
> >board,
> >
> >
> >>programming connector and cable work on slac050l, provided I
accept
> >>
> >>
> >the
> >
> >
> >>different micro. slac050q/r don't even get that far. Even weirder
> >>
> >>
> >is
> >
> >
> >>that it seemed to work at fist. I've done a re-install twice,
even
> >>manually clearing out every scrap of IAR I could find, that too
> >>
> >>
> >hasn't
> >
> >
> >>helped.
> >>
> >>thansk for the effort anyway.
> >>
> >>Al
> >>
> >>Paddu Koti wrote:
> >>
> >>
> >>
> >>>did you get any error message number (ex: Error[e12]:)?
> >>>I don't know it will be useful or not ,below is a IAR technical
> >>>
> >>>
> >note on upgradation,
> >
> >
> >>>http://supp.iar.com/Support/?note@394&from=note+21914
> >>>
> >>>
> >>>
> >>>----- Original Message ----
> >>>From: Onestone
> >>>To: m...
> >>>Sent: Saturday, May 24, 2008 6:18:33 PM
> >>>Subject: [msp430] WEIRD IAR STUFF
> >>>
> >>>
> >>>Has anybody else here encountered the following messages under
> >>>
> >>>
> >IAR? This
> >
> >
> >>>is behaviour that I found only after moving from slac050l to
> >>>
> >>>
> >versions
> >
> >
> >>>after slac050q a couple of days ago. I am currently trying to
use
> >>>slac050r, as I need this for the latest micros, and i
consistently
> >>>
> >>>
> >get
> >
> >
> >>>this message. The appropriate *.d43 file is produced, in the
> >>>
> >>>
> >correct
> >
> >
> >>>directory. The first pair of messages are from the debug window.
> >>>
> >>>
> >The
> >
> >
> >>>error message when I try to download is:-
> >>>
> >>>The debuggiing session could not be started.
> >>>Either the debugger initialisation failed or else the file "
> >>>
> >>>
> >E:\CLIENT
> >
> >
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
> >>>
> >>>
> >unsupported format.
> >
> >
> >>>There might be more information in the Debug window.
> >>>
> >>>Of course there is nothing else there that is helpful. I can
find
> >>>nothing meaningful in the docs, the same thing occurs on boards
> >>>
> >>>
> >that ran
> >
> >
> >>>happily before 'upgrading'. My project configuration hasn't
> >>>
> >>>
> >changed,
> >
> >
> >>>other than when I tried various options for thew linker to try
and
> >>>
> >>>
> >get
> >
> >
> >>>the damned thing going
> >>>
> >>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
> >>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43
> >>>
> >>>Cheers
> >>>
> >>>Al
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
Reply by ●May 25, 20082008-05-25
At 04:21 AM 25/05/2008, you wrote:
Al,
I had something like this when I upgraded to 5.11. I was really in a
hurry and I had a flat battery on my target board. I charged the
battery up overnight and tried teh next day and all was OK. I am not
sure if this was the problem but the fault did not reappear. I
continually have faults with the IAR software but, as you say, it is
free. I never had these problems with any emulators such a the RICE17
or the 8051 emulators, but I did pay considerably more money for them.
Cheers
Peter
>hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL fet
>TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT, IN
>FACT, (whoops fingers0 i had as much trouble with that with flaky
>behaviour as I didi with this one. Similar sort of thing, often the
>computer would need to be reset or even IAR reloaded if I forgot to hold
>the power button down on a self powered unit. That didi get a little
>better over time, but never fully disappearred.
>
>Up until now I have found the USB tool better than the old parallel one,
>except that when I have been running the USB EZ430-2013 dongle I always
>seem to have issues with downloads too. I have ran two instances of IAR
>a couple of times, but i actuall don't like doing it. I like to reserve
>my whole display for one program. It makes it easier to read. I used to
>have several PC's running different applications often, but am down to
>my last ancient PC, band-aided together and staggering along on a Zimmer
>frame, so two windows it is.
>
>It's hard to complain about a free tool, except that I alwasy remember
>the MPLAB free tool as running far more smoothly than this one
>does.Although I haven't used it in anger for a while.
>
>Cheers
>
>Al
>
>darkwzrd00 wrote:
>
> >I've seen this error message using the USB FET Tool with a board
> >specific to the newest patch v4.10E. When I switched to the parallel
> >FET Tool the problem went away. I didn't have time to look into it
> >further, so I left it as that. You are also correct in that if you
> >don't have ANY FET Tool connected (or lack of power, although
> >sometimes it is generous enough to tell you voltage is too low), you
> >can get this message as well.
> >
> >As a side note, I have noticed a few issues with the USB FET Tool
> >(although they seem to be getting fixed in later firmware versions)
> >and therefore I don't trust it fully yet. The parallel FET Tool,
> >although slower on the download, performs flawlessly as far as I have
> >seen. However, isn't it nice to have multiple USB FET Tools connected
> >to the same computer all running at once? It's not as easy to do that
> >with the Parallel FET Tool, is it?
> >
> >darkwzrd00
> >
> >
> >--- In m..., Onestone wrote:
> >
> >
> >>NOpe, I listed exactly what the pogram reported to me. More on
> >>
> >>
> >this. I
> >
> >
> >>can duplicate this by removing the jtag connector. The same gets
> >>reported. So it seems like this is the stupid message that IAR now
> >>
> >>
> >gives
> >
> >
> >>when there is nothing hooked up to it. However exactly the same
> >>
> >>
> >board,
> >
> >
> >>programming connector and cable work on slac050l, provided I accept
> >>
> >>
> >the
> >
> >
> >>different micro. slac050q/r don't even get that far. Even weirder
> >>
> >>
> >is
> >
> >
> >>that it seemed to work at fist. I've done a re-install twice, even
> >>manually clearing out every scrap of IAR I could find, that too
> >>
> >>
> >hasn't
> >
> >
> >>helped.
> >>
> >>thansk for the effort anyway.
> >>
> >>Al
> >>
> >>Paddu Koti wrote:
> >>
> >>
> >>
> >>>did you get any error message number (ex: Error[e12]:)?
> >>>I don't know it will be useful or not ,below is a IAR technical
> >>>
> >>>
> >note on upgradation,
> >
> >
> >>>http://supp.iar.com/Support/?note@394&from=note+21914
> >>>
> >>>
> >>>
> >>>----- Original Message ----
> >>>From: Onestone
> >>>To: m...
> >>>Sent: Saturday, May 24, 2008 6:18:33 PM
> >>>Subject: [msp430] WEIRD IAR STUFF
> >>>
> >>>
> >>>Has anybody else here encountered the following messages under
> >>>
> >>>
> >IAR? This
> >
> >
> >>>is behaviour that I found only after moving from slac050l to
> >>>
> >>>
> >versions
> >
> >
> >>>after slac050q a couple of days ago. I am currently trying to use
> >>>slac050r, as I need this for the latest micros, and i consistently
> >>>
> >>>
> >get
> >
> >
> >>>this message. The appropriate *.d43 file is produced, in the
> >>>
> >>>
> >correct
> >
> >
> >>>directory. The first pair of messages are from the debug window.
> >>>
> >>>
> >The
> >
> >
> >>>error message when I try to download is:-
> >>>
> >>>The debuggiing session could not be started.
> >>>Either the debugger initialisation failed or else the file "
> >>>
> >>>
> >E:\CLIENT
> >
> >
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
> >>>
> >>>
> >unsupported format.
> >
> >
> >>>There might be more information in the Debug window.
> >>>
> >>>Of course there is nothing else there that is helpful. I can find
> >>>nothing meaningful in the docs, the same thing occurs on boards
> >>>
> >>>
> >that ran
> >
> >
> >>>happily before 'upgrading'. My project configuration hasn't
> >>>
> >>>
> >changed,
> >
> >
> >>>other than when I tried various options for thew linker to try and
> >>>
> >>>
> >get
> >
> >
> >>>the damned thing going
> >>>
> >>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
> >>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43
> >>>
> >>>Cheers
> >>>
> >>>Al
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
Al,
I had something like this when I upgraded to 5.11. I was really in a
hurry and I had a flat battery on my target board. I charged the
battery up overnight and tried teh next day and all was OK. I am not
sure if this was the problem but the fault did not reappear. I
continually have faults with the IAR software but, as you say, it is
free. I never had these problems with any emulators such a the RICE17
or the 8051 emulators, but I did pay considerably more money for them.
Cheers
Peter
>hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL fet
>TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT, IN
>FACT, (whoops fingers0 i had as much trouble with that with flaky
>behaviour as I didi with this one. Similar sort of thing, often the
>computer would need to be reset or even IAR reloaded if I forgot to hold
>the power button down on a self powered unit. That didi get a little
>better over time, but never fully disappearred.
>
>Up until now I have found the USB tool better than the old parallel one,
>except that when I have been running the USB EZ430-2013 dongle I always
>seem to have issues with downloads too. I have ran two instances of IAR
>a couple of times, but i actuall don't like doing it. I like to reserve
>my whole display for one program. It makes it easier to read. I used to
>have several PC's running different applications often, but am down to
>my last ancient PC, band-aided together and staggering along on a Zimmer
>frame, so two windows it is.
>
>It's hard to complain about a free tool, except that I alwasy remember
>the MPLAB free tool as running far more smoothly than this one
>does.Although I haven't used it in anger for a while.
>
>Cheers
>
>Al
>
>darkwzrd00 wrote:
>
> >I've seen this error message using the USB FET Tool with a board
> >specific to the newest patch v4.10E. When I switched to the parallel
> >FET Tool the problem went away. I didn't have time to look into it
> >further, so I left it as that. You are also correct in that if you
> >don't have ANY FET Tool connected (or lack of power, although
> >sometimes it is generous enough to tell you voltage is too low), you
> >can get this message as well.
> >
> >As a side note, I have noticed a few issues with the USB FET Tool
> >(although they seem to be getting fixed in later firmware versions)
> >and therefore I don't trust it fully yet. The parallel FET Tool,
> >although slower on the download, performs flawlessly as far as I have
> >seen. However, isn't it nice to have multiple USB FET Tools connected
> >to the same computer all running at once? It's not as easy to do that
> >with the Parallel FET Tool, is it?
> >
> >darkwzrd00
> >
> >
> >--- In m..., Onestone wrote:
> >
> >
> >>NOpe, I listed exactly what the pogram reported to me. More on
> >>
> >>
> >this. I
> >
> >
> >>can duplicate this by removing the jtag connector. The same gets
> >>reported. So it seems like this is the stupid message that IAR now
> >>
> >>
> >gives
> >
> >
> >>when there is nothing hooked up to it. However exactly the same
> >>
> >>
> >board,
> >
> >
> >>programming connector and cable work on slac050l, provided I accept
> >>
> >>
> >the
> >
> >
> >>different micro. slac050q/r don't even get that far. Even weirder
> >>
> >>
> >is
> >
> >
> >>that it seemed to work at fist. I've done a re-install twice, even
> >>manually clearing out every scrap of IAR I could find, that too
> >>
> >>
> >hasn't
> >
> >
> >>helped.
> >>
> >>thansk for the effort anyway.
> >>
> >>Al
> >>
> >>Paddu Koti wrote:
> >>
> >>
> >>
> >>>did you get any error message number (ex: Error[e12]:)?
> >>>I don't know it will be useful or not ,below is a IAR technical
> >>>
> >>>
> >note on upgradation,
> >
> >
> >>>http://supp.iar.com/Support/?note@394&from=note+21914
> >>>
> >>>
> >>>
> >>>----- Original Message ----
> >>>From: Onestone
> >>>To: m...
> >>>Sent: Saturday, May 24, 2008 6:18:33 PM
> >>>Subject: [msp430] WEIRD IAR STUFF
> >>>
> >>>
> >>>Has anybody else here encountered the following messages under
> >>>
> >>>
> >IAR? This
> >
> >
> >>>is behaviour that I found only after moving from slac050l to
> >>>
> >>>
> >versions
> >
> >
> >>>after slac050q a couple of days ago. I am currently trying to use
> >>>slac050r, as I need this for the latest micros, and i consistently
> >>>
> >>>
> >get
> >
> >
> >>>this message. The appropriate *.d43 file is produced, in the
> >>>
> >>>
> >correct
> >
> >
> >>>directory. The first pair of messages are from the debug window.
> >>>
> >>>
> >The
> >
> >
> >>>error message when I try to download is:-
> >>>
> >>>The debuggiing session could not be started.
> >>>Either the debugger initialisation failed or else the file "
> >>>
> >>>
> >E:\CLIENT
> >
> >
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
> >>>
> >>>
> >unsupported format.
> >
> >
> >>>There might be more information in the Debug window.
> >>>
> >>>Of course there is nothing else there that is helpful. I can find
> >>>nothing meaningful in the docs, the same thing occurs on boards
> >>>
> >>>
> >that ran
> >
> >
> >>>happily before 'upgrading'. My project configuration hasn't
> >>>
> >>>
> >changed,
> >
> >
> >>>other than when I tried various options for thew linker to try and
> >>>
> >>>
> >get
> >
> >
> >>>the damned thing going
> >>>
> >>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
> >>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
> >>>PROJECTS\... \Debug\Exe\ MS_V0.d43
> >>>
> >>>Cheers
> >>>
> >>>Al
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
Reply by ●May 25, 20082008-05-25
--- In m..., Peter Grey wrote:
> ...
> I continually have faults with the IAR software but, as you say,
> it is free. I never had these problems with any emulators such a
> the RICE17 or the 8051 emulators, but I did pay considerably more
> money for them.
> ...
And I never had any assembler (other than IAR) that assembles my
source op code into a different machine op code!
> ...
> I continually have faults with the IAR software but, as you say,
> it is free. I never had these problems with any emulators such a
> the RICE17 or the 8051 emulators, but I did pay considerably more
> money for them.
> ...
And I never had any assembler (other than IAR) that assembles my
source op code into a different machine op code!
Reply by ●May 25, 20082008-05-25
Well although I often have multiple things running I actually physically
try to be debuggiong or coding one, working on hardware, which allows me
to break my train of thought if I'm wrestling with a sticky bit of code,
and prpbably working on the actual design (ie pre-hardware stages of
something else) I may well have a couple of each going, but I only try
to physically be working on 1 type of task at a time.
Al
darkwzrd00 wrote:
>I tend to be working on more than one project at once, which is why I
>use multiple instances of IAR. Granted, there is one very annoying
>issue I run into a lot when running more than one instance of IAR
>simultaneously. It has to do with the stupid lisence dongle (I doubt
>any of you are surprised to hear that).
>
>Let's assume that I have 3 windows of IAR open. I can compile all
>three without issue. However, if I connect to one device, and then
>try to connect to another, sometimes IAR complains that it cannot
>find my dongle. In order to "fix" the problem, I have to close (not
>just disconnect from the target) from the project that was running.
>It can take a little bit of finesse to get all three instances
>connected and running. If anyone has a solution to this, please let
>me know as it drives me nuts.
>
>Because of this issue, I have only tried 3 at once.
>
>darkwzrd00
>
>--- In m..., Onestone wrote:
>
>
>>hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL
>>
>>
>fet
>
>
>>TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT,
>>
>>
>IN
>
>
>>FACT, (whoops fingers0 i had as much trouble with that with flaky
>>behaviour as I didi with this one. Similar sort of thing, often the
>>computer would need to be reset or even IAR reloaded if I forgot to
>>
>>
>hold
>
>
>>the power button down on a self powered unit. That didi get a
>>
>>
>little
>
>
>>better over time, but never fully disappearred.
>>
>>Up until now I have found the USB tool better than the old parallel
>>
>>
>one,
>
>
>>except that when I have been running the USB EZ430-2013 dongle I
>>
>>
>always
>
>
>>seem to have issues with downloads too. I have ran two instances of
>>
>>
>IAR
>
>
>>a couple of times, but i actuall don't like doing it. I like to
>>
>>
>reserve
>
>
>>my whole display for one program. It makes it easier to read. I
>>
>>
>used to
>
>
>>have several PC's running different applications often, but am down
>>
>>
>to
>
>
>>my last ancient PC, band-aided together and staggering along on a
>>
>>
>Zimmer
>
>
>>frame, so two windows it is.
>>
>>It's hard to complain about a free tool, except that I alwasy
>>
>>
>remember
>
>
>>the MPLAB free tool as running far more smoothly than this one
>>does.Although I haven't used it in anger for a while.
>>
>>Cheers
>>
>>Al
>>
>>darkwzrd00 wrote:
>>
>>
>>
>>>I've seen this error message using the USB FET Tool with a board
>>>specific to the newest patch v4.10E. When I switched to the
>>>
>>>
>parallel
>
>
>>>FET Tool the problem went away. I didn't have time to look into it
>>>further, so I left it as that. You are also correct in that if you
>>>don't have ANY FET Tool connected (or lack of power, although
>>>sometimes it is generous enough to tell you voltage is too low),
>>>
>>>
>you
>
>
>>>can get this message as well.
>>>
>>>As a side note, I have noticed a few issues with the USB FET Tool
>>>(although they seem to be getting fixed in later firmware
>>>
>>>
>versions)
>
>
>>>and therefore I don't trust it fully yet. The parallel FET Tool,
>>>although slower on the download, performs flawlessly as far as I
>>>
>>>
>have
>
>
>>>seen. However, isn't it nice to have multiple USB FET Tools
>>>
>>>
>connected
>
>
>>>to the same computer all running at once? It's not as easy to do
>>>
>>>
>that
>
>
>>>with the Parallel FET Tool, is it?
>>>
>>>darkwzrd00
>>>
>>>
>>>--- In m..., Onestone wrote:
>>>
>>>
>>>
>>>
>>>>NOpe, I listed exactly what the pogram reported to me. More on
>>>>
>>>>
>>>>
>>>>
>>>this. I
>>>
>>>
>>>
>>>
>>>>can duplicate this by removing the jtag connector. The same gets
>>>>reported. So it seems like this is the stupid message that IAR
>>>>
>>>>
>now
>
>
>>>>
>>>>
>>>>
>>>>
>>>gives
>>>
>>>
>>>
>>>
>>>>when there is nothing hooked up to it. However exactly the same
>>>>
>>>>
>>>>
>>>>
>>>board,
>>>
>>>
>>>
>>>
>>>>programming connector and cable work on slac050l, provided I
>>>>
>>>>
>accept
>
>
>>>>
>>>>
>>>>
>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>different micro. slac050q/r don't even get that far. Even weirder
>>>>
>>>>
>>>>
>>>>
>>>is
>>>
>>>
>>>
>>>
>>>>that it seemed to work at fist. I've done a re-install twice,
>>>>
>>>>
>even
>
>
>>>>manually clearing out every scrap of IAR I could find, that too
>>>>
>>>>
>>>>
>>>>
>>>hasn't
>>>
>>>
>>>
>>>
>>>>helped.
>>>>
>>>>thansk for the effort anyway.
>>>>
>>>>Al
>>>>
>>>>Paddu Koti wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>did you get any error message number (ex: Error[e12]:)?
>>>>>I don't know it will be useful or not ,below is a IAR technical
>>>>>
>>>>>
>>>>>
>>>>>
>>>note on upgradation,
>>>
>>>
>>>
>>>
>>>>>http://supp.iar.com/Support/?note@394&from=note+21914
>>>>>
>>>>>
>>>>>
>>>>>----- Original Message ----
>>>>>From: Onestone
>>>>>To: m...
>>>>>Sent: Saturday, May 24, 2008 6:18:33 PM
>>>>>Subject: [msp430] WEIRD IAR STUFF
>>>>>
>>>>>
>>>>>Has anybody else here encountered the following messages under
>>>>>
>>>>>
>>>>>
>>>>>
>>>IAR? This
>>>
>>>
>>>
>>>
>>>>>is behaviour that I found only after moving from slac050l to
>>>>>
>>>>>
>>>>>
>>>>>
>>>versions
>>>
>>>
>>>
>>>
>>>>>after slac050q a couple of days ago. I am currently trying to
>>>>>
>>>>>
>use
>
>
>>>>>slac050r, as I need this for the latest micros, and i
>>>>>
>>>>>
>consistently
>
>
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>this message. The appropriate *.d43 file is produced, in the
>>>>>
>>>>>
>>>>>
>>>>>
>>>correct
>>>
>>>
>>>
>>>
>>>>>directory. The first pair of messages are from the debug window.
>>>>>
>>>>>
>>>>>
>>>>>
>>>The
>>>
>>>
>>>
>>>
>>>>>error message when I try to download is:-
>>>>>
>>>>>The debuggiing session could not be started.
>>>>>Either the debugger initialisation failed or else the file "
>>>>>
>>>>>
>>>>>
>>>>>
>>>E:\CLIENT
>>>
>>>
>>>
>>>
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
>>>>>
>>>>>
>>>>>
>>>>>
>>>unsupported format.
>>>
>>>
>>>
>>>
>>>>>There might be more information in the Debug window.
>>>>>
>>>>>Of course there is nothing else there that is helpful. I can
>>>>>
>>>>>
>find
>
>
>>>>>nothing meaningful in the docs, the same thing occurs on boards
>>>>>
>>>>>
>>>>>
>>>>>
>>>that ran
>>>
>>>
>>>
>>>
>>>>>happily before 'upgrading'. My project configuration hasn't
>>>>>
>>>>>
>>>>>
>>>>>
>>>changed,
>>>
>>>
>>>
>>>
>>>>>other than when I tried various options for thew linker to try
>>>>>
>>>>>
>and
>
>
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>the damned thing going
>>>>>
>>>>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>>>>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43
>>>>>
>>>>>Cheers
>>>>>
>>>>>Al
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
try to be debuggiong or coding one, working on hardware, which allows me
to break my train of thought if I'm wrestling with a sticky bit of code,
and prpbably working on the actual design (ie pre-hardware stages of
something else) I may well have a couple of each going, but I only try
to physically be working on 1 type of task at a time.
Al
darkwzrd00 wrote:
>I tend to be working on more than one project at once, which is why I
>use multiple instances of IAR. Granted, there is one very annoying
>issue I run into a lot when running more than one instance of IAR
>simultaneously. It has to do with the stupid lisence dongle (I doubt
>any of you are surprised to hear that).
>
>Let's assume that I have 3 windows of IAR open. I can compile all
>three without issue. However, if I connect to one device, and then
>try to connect to another, sometimes IAR complains that it cannot
>find my dongle. In order to "fix" the problem, I have to close (not
>just disconnect from the target) from the project that was running.
>It can take a little bit of finesse to get all three instances
>connected and running. If anyone has a solution to this, please let
>me know as it drives me nuts.
>
>Because of this issue, I have only tried 3 at once.
>
>darkwzrd00
>
>--- In m..., Onestone wrote:
>
>
>>hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL
>>
>>
>fet
>
>
>>TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT,
>>
>>
>IN
>
>
>>FACT, (whoops fingers0 i had as much trouble with that with flaky
>>behaviour as I didi with this one. Similar sort of thing, often the
>>computer would need to be reset or even IAR reloaded if I forgot to
>>
>>
>hold
>
>
>>the power button down on a self powered unit. That didi get a
>>
>>
>little
>
>
>>better over time, but never fully disappearred.
>>
>>Up until now I have found the USB tool better than the old parallel
>>
>>
>one,
>
>
>>except that when I have been running the USB EZ430-2013 dongle I
>>
>>
>always
>
>
>>seem to have issues with downloads too. I have ran two instances of
>>
>>
>IAR
>
>
>>a couple of times, but i actuall don't like doing it. I like to
>>
>>
>reserve
>
>
>>my whole display for one program. It makes it easier to read. I
>>
>>
>used to
>
>
>>have several PC's running different applications often, but am down
>>
>>
>to
>
>
>>my last ancient PC, band-aided together and staggering along on a
>>
>>
>Zimmer
>
>
>>frame, so two windows it is.
>>
>>It's hard to complain about a free tool, except that I alwasy
>>
>>
>remember
>
>
>>the MPLAB free tool as running far more smoothly than this one
>>does.Although I haven't used it in anger for a while.
>>
>>Cheers
>>
>>Al
>>
>>darkwzrd00 wrote:
>>
>>
>>
>>>I've seen this error message using the USB FET Tool with a board
>>>specific to the newest patch v4.10E. When I switched to the
>>>
>>>
>parallel
>
>
>>>FET Tool the problem went away. I didn't have time to look into it
>>>further, so I left it as that. You are also correct in that if you
>>>don't have ANY FET Tool connected (or lack of power, although
>>>sometimes it is generous enough to tell you voltage is too low),
>>>
>>>
>you
>
>
>>>can get this message as well.
>>>
>>>As a side note, I have noticed a few issues with the USB FET Tool
>>>(although they seem to be getting fixed in later firmware
>>>
>>>
>versions)
>
>
>>>and therefore I don't trust it fully yet. The parallel FET Tool,
>>>although slower on the download, performs flawlessly as far as I
>>>
>>>
>have
>
>
>>>seen. However, isn't it nice to have multiple USB FET Tools
>>>
>>>
>connected
>
>
>>>to the same computer all running at once? It's not as easy to do
>>>
>>>
>that
>
>
>>>with the Parallel FET Tool, is it?
>>>
>>>darkwzrd00
>>>
>>>
>>>--- In m..., Onestone wrote:
>>>
>>>
>>>
>>>
>>>>NOpe, I listed exactly what the pogram reported to me. More on
>>>>
>>>>
>>>>
>>>>
>>>this. I
>>>
>>>
>>>
>>>
>>>>can duplicate this by removing the jtag connector. The same gets
>>>>reported. So it seems like this is the stupid message that IAR
>>>>
>>>>
>now
>
>
>>>>
>>>>
>>>>
>>>>
>>>gives
>>>
>>>
>>>
>>>
>>>>when there is nothing hooked up to it. However exactly the same
>>>>
>>>>
>>>>
>>>>
>>>board,
>>>
>>>
>>>
>>>
>>>>programming connector and cable work on slac050l, provided I
>>>>
>>>>
>accept
>
>
>>>>
>>>>
>>>>
>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>different micro. slac050q/r don't even get that far. Even weirder
>>>>
>>>>
>>>>
>>>>
>>>is
>>>
>>>
>>>
>>>
>>>>that it seemed to work at fist. I've done a re-install twice,
>>>>
>>>>
>even
>
>
>>>>manually clearing out every scrap of IAR I could find, that too
>>>>
>>>>
>>>>
>>>>
>>>hasn't
>>>
>>>
>>>
>>>
>>>>helped.
>>>>
>>>>thansk for the effort anyway.
>>>>
>>>>Al
>>>>
>>>>Paddu Koti wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>did you get any error message number (ex: Error[e12]:)?
>>>>>I don't know it will be useful or not ,below is a IAR technical
>>>>>
>>>>>
>>>>>
>>>>>
>>>note on upgradation,
>>>
>>>
>>>
>>>
>>>>>http://supp.iar.com/Support/?note@394&from=note+21914
>>>>>
>>>>>
>>>>>
>>>>>----- Original Message ----
>>>>>From: Onestone
>>>>>To: m...
>>>>>Sent: Saturday, May 24, 2008 6:18:33 PM
>>>>>Subject: [msp430] WEIRD IAR STUFF
>>>>>
>>>>>
>>>>>Has anybody else here encountered the following messages under
>>>>>
>>>>>
>>>>>
>>>>>
>>>IAR? This
>>>
>>>
>>>
>>>
>>>>>is behaviour that I found only after moving from slac050l to
>>>>>
>>>>>
>>>>>
>>>>>
>>>versions
>>>
>>>
>>>
>>>
>>>>>after slac050q a couple of days ago. I am currently trying to
>>>>>
>>>>>
>use
>
>
>>>>>slac050r, as I need this for the latest micros, and i
>>>>>
>>>>>
>consistently
>
>
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>this message. The appropriate *.d43 file is produced, in the
>>>>>
>>>>>
>>>>>
>>>>>
>>>correct
>>>
>>>
>>>
>>>
>>>>>directory. The first pair of messages are from the debug window.
>>>>>
>>>>>
>>>>>
>>>>>
>>>The
>>>
>>>
>>>
>>>
>>>>>error message when I try to download is:-
>>>>>
>>>>>The debuggiing session could not be started.
>>>>>Either the debugger initialisation failed or else the file "
>>>>>
>>>>>
>>>>>
>>>>>
>>>E:\CLIENT
>>>
>>>
>>>
>>>
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
>>>>>
>>>>>
>>>>>
>>>>>
>>>unsupported format.
>>>
>>>
>>>
>>>
>>>>>There might be more information in the Debug window.
>>>>>
>>>>>Of course there is nothing else there that is helpful. I can
>>>>>
>>>>>
>find
>
>
>>>>>nothing meaningful in the docs, the same thing occurs on boards
>>>>>
>>>>>
>>>>>
>>>>>
>>>that ran
>>>
>>>
>>>
>>>
>>>>>happily before 'upgrading'. My project configuration hasn't
>>>>>
>>>>>
>>>>>
>>>>>
>>>changed,
>>>
>>>
>>>
>>>
>>>>>other than when I tried various options for thew linker to try
>>>>>
>>>>>
>and
>
>
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>the damned thing going
>>>>>
>>>>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>>>>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43
>>>>>
>>>>>Cheers
>>>>>
>>>>>Al
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
Reply by ●May 25, 20082008-05-25
Wow. I still have a Rice17 emulator. I have some biards for it somwhere,
but couldn't lay my hands on them, and only have installed code
available, but it's free to a good home for postage. Tools used to be
exhorbitant, even from the manufacturer of the parts. i never understood
this. Often i would choose one part over another simply because the
tools were too coistly to evaluate the preferred part. Echelon was the
standout example of this. When they first hit the market they wanted
$64k for a dev kit, later they dropped tis to425k, but I think the
damage was done. they still exist, but could have been far bigger than
they are. Bluetooth is another example, the early days of $250k licences
and $100k dev tools killed it from the small implem,enters perspective,
an it still appears to be a solution looking for a real problem to me.
never quite enough of anything.
Al
Peter Grey wrote:
>At 04:21 AM 25/05/2008, you wrote:
>
>Al,
>
>I had something like this when I upgraded to 5.11. I was really in a
>hurry and I had a flat battery on my target board. I charged the
>battery up overnight and tried teh next day and all was OK. I am not
>sure if this was the problem but the fault did not reappear. I
>continually have faults with the IAR software but, as you say, it is
>free. I never had these problems with any emulators such a the RICE17
>or the 8051 emulators, but I did pay considerably more money for them.
>
>Cheers
>Peter
>
>
>>hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL fet
>>TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT, IN
>>FACT, (whoops fingers0 i had as much trouble with that with flaky
>>behaviour as I didi with this one. Similar sort of thing, often the
>>computer would need to be reset or even IAR reloaded if I forgot to hold
>>the power button down on a self powered unit. That didi get a little
>>better over time, but never fully disappearred.
>>
>>Up until now I have found the USB tool better than the old parallel one,
>>except that when I have been running the USB EZ430-2013 dongle I always
>>seem to have issues with downloads too. I have ran two instances of IAR
>>a couple of times, but i actuall don't like doing it. I like to reserve
>>my whole display for one program. It makes it easier to read. I used to
>>have several PC's running different applications often, but am down to
>>my last ancient PC, band-aided together and staggering along on a Zimmer
>>frame, so two windows it is.
>>
>>It's hard to complain about a free tool, except that I alwasy remember
>>the MPLAB free tool as running far more smoothly than this one
>>does.Although I haven't used it in anger for a while.
>>
>>Cheers
>>
>>Al
>>
>>darkwzrd00 wrote:
>>
>>
>>
>>>I've seen this error message using the USB FET Tool with a board
>>>specific to the newest patch v4.10E. When I switched to the parallel
>>>FET Tool the problem went away. I didn't have time to look into it
>>>further, so I left it as that. You are also correct in that if you
>>>don't have ANY FET Tool connected (or lack of power, although
>>>sometimes it is generous enough to tell you voltage is too low), you
>>>can get this message as well.
>>>
>>>As a side note, I have noticed a few issues with the USB FET Tool
>>>(although they seem to be getting fixed in later firmware versions)
>>>and therefore I don't trust it fully yet. The parallel FET Tool,
>>>although slower on the download, performs flawlessly as far as I have
>>>seen. However, isn't it nice to have multiple USB FET Tools connected
>>>to the same computer all running at once? It's not as easy to do that
>>>with the Parallel FET Tool, is it?
>>>
>>>darkwzrd00
>>>
>>>
>>>--- In m..., Onestone wrote:
>>>
>>>
>>>
>>>
>>>>NOpe, I listed exactly what the pogram reported to me. More on
>>>>
>>>>
>>>>
>>>>
>>>this. I
>>>
>>>
>>>
>>>
>>>>can duplicate this by removing the jtag connector. The same gets
>>>>reported. So it seems like this is the stupid message that IAR now
>>>>
>>>>
>>>>
>>>>
>>>gives
>>>
>>>
>>>
>>>
>>>>when there is nothing hooked up to it. However exactly the same
>>>>
>>>>
>>>>
>>>>
>>>board,
>>>
>>>
>>>
>>>
>>>>programming connector and cable work on slac050l, provided I accept
>>>>
>>>>
>>>>
>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>different micro. slac050q/r don't even get that far. Even weirder
>>>>
>>>>
>>>>
>>>>
>>>is
>>>
>>>
>>>
>>>
>>>>that it seemed to work at fist. I've done a re-install twice, even
>>>>manually clearing out every scrap of IAR I could find, that too
>>>>
>>>>
>>>>
>>>>
>>>hasn't
>>>
>>>
>>>
>>>
>>>>helped.
>>>>
>>>>thansk for the effort anyway.
>>>>
>>>>Al
>>>>
>>>>Paddu Koti wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>did you get any error message number (ex: Error[e12]:)?
>>>>>I don't know it will be useful or not ,below is a IAR technical
>>>>>
>>>>>
>>>>>
>>>>>
>>>note on upgradation,
>>>
>>>
>>>
>>>
>>>>>http://supp.iar.com/Support/?note@394&from=note+21914
>>>>>
>>>>>
>>>>>
>>>>>----- Original Message ----
>>>>>From: Onestone
>>>>>To: m...
>>>>>Sent: Saturday, May 24, 2008 6:18:33 PM
>>>>>Subject: [msp430] WEIRD IAR STUFF
>>>>>
>>>>>
>>>>>Has anybody else here encountered the following messages under
>>>>>
>>>>>
>>>>>
>>>>>
>>>IAR? This
>>>
>>>
>>>
>>>
>>>>>is behaviour that I found only after moving from slac050l to
>>>>>
>>>>>
>>>>>
>>>>>
>>>versions
>>>
>>>
>>>
>>>
>>>>>after slac050q a couple of days ago. I am currently trying to use
>>>>>slac050r, as I need this for the latest micros, and i consistently
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>this message. The appropriate *.d43 file is produced, in the
>>>>>
>>>>>
>>>>>
>>>>>
>>>correct
>>>
>>>
>>>
>>>
>>>>>directory. The first pair of messages are from the debug window.
>>>>>
>>>>>
>>>>>
>>>>>
>>>The
>>>
>>>
>>>
>>>
>>>>>error message when I try to download is:-
>>>>>
>>>>>The debuggiing session could not be started.
>>>>>Either the debugger initialisation failed or else the file "
>>>>>
>>>>>
>>>>>
>>>>>
>>>E:\CLIENT
>>>
>>>
>>>
>>>
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
>>>>>
>>>>>
>>>>>
>>>>>
>>>unsupported format.
>>>
>>>
>>>
>>>
>>>>>There might be more information in the Debug window.
>>>>>
>>>>>Of course there is nothing else there that is helpful. I can find
>>>>>nothing meaningful in the docs, the same thing occurs on boards
>>>>>
>>>>>
>>>>>
>>>>>
>>>that ran
>>>
>>>
>>>
>>>
>>>>>happily before 'upgrading'. My project configuration hasn't
>>>>>
>>>>>
>>>>>
>>>>>
>>>changed,
>>>
>>>
>>>
>>>
>>>>>other than when I tried various options for thew linker to try and
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>the damned thing going
>>>>>
>>>>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>>>>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43
>>>>>
>>>>>Cheers
>>>>>
>>>>>Al
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
but couldn't lay my hands on them, and only have installed code
available, but it's free to a good home for postage. Tools used to be
exhorbitant, even from the manufacturer of the parts. i never understood
this. Often i would choose one part over another simply because the
tools were too coistly to evaluate the preferred part. Echelon was the
standout example of this. When they first hit the market they wanted
$64k for a dev kit, later they dropped tis to425k, but I think the
damage was done. they still exist, but could have been far bigger than
they are. Bluetooth is another example, the early days of $250k licences
and $100k dev tools killed it from the small implem,enters perspective,
an it still appears to be a solution looking for a real problem to me.
never quite enough of anything.
Al
Peter Grey wrote:
>At 04:21 AM 25/05/2008, you wrote:
>
>Al,
>
>I had something like this when I upgraded to 5.11. I was really in a
>hurry and I had a flat battery on my target board. I charged the
>battery up overnight and tried teh next day and all was OK. I am not
>sure if this was the problem but the fault did not reappear. I
>continually have faults with the IAR software but, as you say, it is
>free. I never had these problems with any emulators such a the RICE17
>or the 8051 emulators, but I did pay considerably more money for them.
>
>Cheers
>Peter
>
>
>>hI AND THANKS FOR THE REPLY. uNFORTUNATELY i DON'T HAVE A PARALLEL fet
>>TOOL ANYMORE. MADE THE MISTAKE OF GIVING IT AWAY AS SURPLUS, BUT, IN
>>FACT, (whoops fingers0 i had as much trouble with that with flaky
>>behaviour as I didi with this one. Similar sort of thing, often the
>>computer would need to be reset or even IAR reloaded if I forgot to hold
>>the power button down on a self powered unit. That didi get a little
>>better over time, but never fully disappearred.
>>
>>Up until now I have found the USB tool better than the old parallel one,
>>except that when I have been running the USB EZ430-2013 dongle I always
>>seem to have issues with downloads too. I have ran two instances of IAR
>>a couple of times, but i actuall don't like doing it. I like to reserve
>>my whole display for one program. It makes it easier to read. I used to
>>have several PC's running different applications often, but am down to
>>my last ancient PC, band-aided together and staggering along on a Zimmer
>>frame, so two windows it is.
>>
>>It's hard to complain about a free tool, except that I alwasy remember
>>the MPLAB free tool as running far more smoothly than this one
>>does.Although I haven't used it in anger for a while.
>>
>>Cheers
>>
>>Al
>>
>>darkwzrd00 wrote:
>>
>>
>>
>>>I've seen this error message using the USB FET Tool with a board
>>>specific to the newest patch v4.10E. When I switched to the parallel
>>>FET Tool the problem went away. I didn't have time to look into it
>>>further, so I left it as that. You are also correct in that if you
>>>don't have ANY FET Tool connected (or lack of power, although
>>>sometimes it is generous enough to tell you voltage is too low), you
>>>can get this message as well.
>>>
>>>As a side note, I have noticed a few issues with the USB FET Tool
>>>(although they seem to be getting fixed in later firmware versions)
>>>and therefore I don't trust it fully yet. The parallel FET Tool,
>>>although slower on the download, performs flawlessly as far as I have
>>>seen. However, isn't it nice to have multiple USB FET Tools connected
>>>to the same computer all running at once? It's not as easy to do that
>>>with the Parallel FET Tool, is it?
>>>
>>>darkwzrd00
>>>
>>>
>>>--- In m..., Onestone wrote:
>>>
>>>
>>>
>>>
>>>>NOpe, I listed exactly what the pogram reported to me. More on
>>>>
>>>>
>>>>
>>>>
>>>this. I
>>>
>>>
>>>
>>>
>>>>can duplicate this by removing the jtag connector. The same gets
>>>>reported. So it seems like this is the stupid message that IAR now
>>>>
>>>>
>>>>
>>>>
>>>gives
>>>
>>>
>>>
>>>
>>>>when there is nothing hooked up to it. However exactly the same
>>>>
>>>>
>>>>
>>>>
>>>board,
>>>
>>>
>>>
>>>
>>>>programming connector and cable work on slac050l, provided I accept
>>>>
>>>>
>>>>
>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>different micro. slac050q/r don't even get that far. Even weirder
>>>>
>>>>
>>>>
>>>>
>>>is
>>>
>>>
>>>
>>>
>>>>that it seemed to work at fist. I've done a re-install twice, even
>>>>manually clearing out every scrap of IAR I could find, that too
>>>>
>>>>
>>>>
>>>>
>>>hasn't
>>>
>>>
>>>
>>>
>>>>helped.
>>>>
>>>>thansk for the effort anyway.
>>>>
>>>>Al
>>>>
>>>>Paddu Koti wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>did you get any error message number (ex: Error[e12]:)?
>>>>>I don't know it will be useful or not ,below is a IAR technical
>>>>>
>>>>>
>>>>>
>>>>>
>>>note on upgradation,
>>>
>>>
>>>
>>>
>>>>>http://supp.iar.com/Support/?note@394&from=note+21914
>>>>>
>>>>>
>>>>>
>>>>>----- Original Message ----
>>>>>From: Onestone
>>>>>To: m...
>>>>>Sent: Saturday, May 24, 2008 6:18:33 PM
>>>>>Subject: [msp430] WEIRD IAR STUFF
>>>>>
>>>>>
>>>>>Has anybody else here encountered the following messages under
>>>>>
>>>>>
>>>>>
>>>>>
>>>IAR? This
>>>
>>>
>>>
>>>
>>>>>is behaviour that I found only after moving from slac050l to
>>>>>
>>>>>
>>>>>
>>>>>
>>>versions
>>>
>>>
>>>
>>>
>>>>>after slac050q a couple of days ago. I am currently trying to use
>>>>>slac050r, as I need this for the latest micros, and i consistently
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>this message. The appropriate *.d43 file is produced, in the
>>>>>
>>>>>
>>>>>
>>>>>
>>>correct
>>>
>>>
>>>
>>>
>>>>>directory. The first pair of messages are from the debug window.
>>>>>
>>>>>
>>>>>
>>>>>
>>>The
>>>
>>>
>>>
>>>
>>>>>error message when I try to download is:-
>>>>>
>>>>>The debuggiing session could not be started.
>>>>>Either the debugger initialisation failed or else the file "
>>>>>
>>>>>
>>>>>
>>>>>
>>>E:\CLIENT
>>>
>>>
>>>
>>>
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43" was corrupt or of an
>>>>>
>>>>>
>>>>>
>>>>>
>>>unsupported format.
>>>
>>>
>>>
>>>
>>>>>There might be more information in the Debug window.
>>>>>
>>>>>Of course there is nothing else there that is helpful. I can find
>>>>>nothing meaningful in the docs, the same thing occurs on boards
>>>>>
>>>>>
>>>>>
>>>>>
>>>that ran
>>>
>>>
>>>
>>>
>>>>>happily before 'upgrading'. My project configuration hasn't
>>>>>
>>>>>
>>>>>
>>>>>
>>>changed,
>>>
>>>
>>>
>>>
>>>>>other than when I tried various options for thew linker to try and
>>>>>
>>>>>
>>>>>
>>>>>
>>>get
>>>
>>>
>>>
>>>
>>>>>the damned thing going
>>>>>
>>>>>Sat May 24 18:38:01 2008: Interface dll version 2.3.3.0
>>>>>Sat May 24 18:38:02 2008: Failed to load debugee: E:\CLIENT
>>>>>PROJECTS\... \Debug\Exe\ MS_V0.d43
>>>>>
>>>>>Cheers
>>>>>
>>>>>Al
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
