I've been using the MSP430F1121A for some time. The app was written with
the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to
program the chip.
This has been working fine until I got a new batch of chips (perhaps 4 months
ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware
(Device unknown) do not match.
I did have one old chip left over, and it programs just fine, so I'm
thinking TI has changed something on the MSP4301121A. Any one experienced
something like this?
What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a
different compiler package (very small program, small budget.) Other? I'm
also wondering about the tradoffs between a quick fix and a fix that will last
longer.
Or do I need to bang on TI about defective chips? (purchased from two different
sources.)
Suddenly unable to program chip
Started by ●July 25, 2012
Reply by ●July 25, 20122012-07-25
Hi Leroy :-P
You're stuffing up the programmers now are you??
Ok this problem occurs with certain types of MSP430. For example it
happens to me all the time with the MSP320F2254, which the device rerads
as a 2274. For me simply telling IAR to continue works fine.
Ti embeds a device type code into the BSL., but there are a limited
number of codes, and some seem to be generic, however it may be, from
your post, that you are trying to call the device an 1121 when it is a
1121A which should have its own device type. The BSL sits in flash from
0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
BSL version. The CHIP ID sits at FF0 - FF1.
The document you need to read is SLAU319B
Hope that helps
Al
On 26/07/2012 8:28 AM, baxtercodeworks wrote:
> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
>
> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware (Device unknown) do not match.
>
> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
>
> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
>
> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
>
You're stuffing up the programmers now are you??
Ok this problem occurs with certain types of MSP430. For example it
happens to me all the time with the MSP320F2254, which the device rerads
as a 2274. For me simply telling IAR to continue works fine.
Ti embeds a device type code into the BSL., but there are a limited
number of codes, and some seem to be generic, however it may be, from
your post, that you are trying to call the device an 1121 when it is a
1121A which should have its own device type. The BSL sits in flash from
0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
BSL version. The CHIP ID sits at FF0 - FF1.
The document you need to read is SLAU319B
Hope that helps
Al
On 26/07/2012 8:28 AM, baxtercodeworks wrote:
> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
>
> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware (Device unknown) do not match.
>
> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
>
> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
>
> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
>
Reply by ●July 25, 20122012-07-25
Well, the sudden break kind of threw me. IAR KS 3.2 does not have an option for
MSP430F1121A. I do know that the most recent IAR version does have an option
for both MSP430F1121 and MSP430F1121A. I was hesitant because the error popup
showed "(Device unknown)".
I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
--- In m..., Onestone wrote:
>
> Hi Leroy :-P
>
> You're stuffing up the programmers now are you??
>
> Ok this problem occurs with certain types of MSP430. For example it
> happens to me all the time with the MSP320F2254, which the device rerads
> as a 2274. For me simply telling IAR to continue works fine.
>
> Ti embeds a device type code into the BSL., but there are a limited
> number of codes, and some seem to be generic, however it may be, from
> your post, that you are trying to call the device an 1121 when it is a
> 1121A which should have its own device type. The BSL sits in flash from
> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
> BSL version. The CHIP ID sits at FF0 - FF1.
>
> The document you need to read is SLAU319B
>
> Hope that helps
>
> Al
>
> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
> > I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
> >
> > This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
> >
> > I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
> >
> > What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
> >
> > Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
--- In m..., Onestone wrote:
>
> Hi Leroy :-P
>
> You're stuffing up the programmers now are you??
>
> Ok this problem occurs with certain types of MSP430. For example it
> happens to me all the time with the MSP320F2254, which the device rerads
> as a 2274. For me simply telling IAR to continue works fine.
>
> Ti embeds a device type code into the BSL., but there are a limited
> number of codes, and some seem to be generic, however it may be, from
> your post, that you are trying to call the device an 1121 when it is a
> 1121A which should have its own device type. The BSL sits in flash from
> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
> BSL version. The CHIP ID sits at FF0 - FF1.
>
> The document you need to read is SLAU319B
>
> Hope that helps
>
> Al
>
> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
> > I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
> >
> > This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
> >
> > I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
> >
> > What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
> >
> > Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
Reply by ●July 25, 20122012-07-25
I am using slac050x, which reports itself as 5.10.1, so couldn't tell
you about later versions.
I'm forever having minor, and occasionally major issues with KS, but I
still think it's better than CCS, especially for an assembly writer like
myself. In general though the newer versions tend to be more stable than
older versions. I haven't had major issues when upgrading except with
older versions where sometimes KS seemed to cross up its directories,
now I just make sure all traces of IAR are removed before upgrading, and
I always keepe the previous few versions. I don't know how it would go
on Win 2000, I run Xp and have no issues
Al
On 26/07/2012 9:21 AM, baxtercodeworks wrote:
> Well, the sudden break kind of threw me. IAR KS 3.2 does not have an option for MSP430F1121A. I do know that the most recent IAR version does have an option for both MSP430F1121 and MSP430F1121A. I was hesitant because the error popup showed "(Device unknown)".
>
> I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
>
> I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
>
> --- In m..., Onestone wrote:
>> Hi Leroy :-P
>>
>> You're stuffing up the programmers now are you??
>>
>> Ok this problem occurs with certain types of MSP430. For example it
>> happens to me all the time with the MSP320F2254, which the device rerads
>> as a 2274. For me simply telling IAR to continue works fine.
>>
>> Ti embeds a device type code into the BSL., but there are a limited
>> number of codes, and some seem to be generic, however it may be, from
>> your post, that you are trying to call the device an 1121 when it is a
>> 1121A which should have its own device type. The BSL sits in flash from
>> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
>> BSL version. The CHIP ID sits at FF0 - FF1.
>>
>> The document you need to read is SLAU319B
>>
>> Hope that helps
>>
>> Al
>>
>> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
>>> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
>>>
>>> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
>>>
>>> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
>>>
>>> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
>>>
>>> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
>
you about later versions.
I'm forever having minor, and occasionally major issues with KS, but I
still think it's better than CCS, especially for an assembly writer like
myself. In general though the newer versions tend to be more stable than
older versions. I haven't had major issues when upgrading except with
older versions where sometimes KS seemed to cross up its directories,
now I just make sure all traces of IAR are removed before upgrading, and
I always keepe the previous few versions. I don't know how it would go
on Win 2000, I run Xp and have no issues
Al
On 26/07/2012 9:21 AM, baxtercodeworks wrote:
> Well, the sudden break kind of threw me. IAR KS 3.2 does not have an option for MSP430F1121A. I do know that the most recent IAR version does have an option for both MSP430F1121 and MSP430F1121A. I was hesitant because the error popup showed "(Device unknown)".
>
> I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
>
> I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
>
> --- In m..., Onestone wrote:
>> Hi Leroy :-P
>>
>> You're stuffing up the programmers now are you??
>>
>> Ok this problem occurs with certain types of MSP430. For example it
>> happens to me all the time with the MSP320F2254, which the device rerads
>> as a 2274. For me simply telling IAR to continue works fine.
>>
>> Ti embeds a device type code into the BSL., but there are a limited
>> number of codes, and some seem to be generic, however it may be, from
>> your post, that you are trying to call the device an 1121 when it is a
>> 1121A which should have its own device type. The BSL sits in flash from
>> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
>> BSL version. The CHIP ID sits at FF0 - FF1.
>>
>> The document you need to read is SLAU319B
>>
>> Hope that helps
>>
>> Al
>>
>> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
>>> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
>>>
>>> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
>>>
>>> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
>>>
>>> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
>>>
>>> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
>
Reply by ●July 25, 20122012-07-25
We had some problems with IAR and the 1611 chip displaying the same error
message. We tracked the problem down to a capacitor across the reset line (used
to help reduce Reset switch bounce) that was too large, causing the JTAG reset
part of the initialization sequence (generated by the FET pod) to be too long
for the FET pod to get control thru the JTAG port. Reducing the value from 10uf
to 0.1uf seemed to correct the issue.
----- Original Message -----
From: Onestone
To: m...
Sent: Wednesday, July 25, 2012 18:20
Subject: Re: [msp430] Re: Suddenly unable to program chip
I am using slac050x, which reports itself as 5.10.1, so couldn't tell
you about later versions.
I'm forever having minor, and occasionally major issues with KS, but I
still think it's better than CCS, especially for an assembly writer like
myself. In general though the newer versions tend to be more stable than
older versions. I haven't had major issues when upgrading except with
older versions where sometimes KS seemed to cross up its directories,
now I just make sure all traces of IAR are removed before upgrading, and
I always keepe the previous few versions. I don't know how it would go
on Win 2000, I run Xp and have no issues
Al
On 26/07/2012 9:21 AM, baxtercodeworks wrote:
> Well, the sudden break kind of threw me. IAR KS 3.2 does not have an option for MSP430F1121A. I do know that the most recent IAR version does have an option for both MSP430F1121 and MSP430F1121A. I was hesitant because the error popup showed "(Device unknown)".
>
> I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
>
> I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
>
> --- In m..., Onestone wrote:
>> Hi Leroy :-P
>>
>> You're stuffing up the programmers now are you??
>>
>> Ok this problem occurs with certain types of MSP430. For example it
>> happens to me all the time with the MSP320F2254, which the device rerads
>> as a 2274. For me simply telling IAR to continue works fine.
>>
>> Ti embeds a device type code into the BSL., but there are a limited
>> number of codes, and some seem to be generic, however it may be, from
>> your post, that you are trying to call the device an 1121 when it is a
>> 1121A which should have its own device type. The BSL sits in flash from
>> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
>> BSL version. The CHIP ID sits at FF0 - FF1.
>>
>> The document you need to read is SLAU319B
>>
>> Hope that helps
>>
>> Al
>>
>> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
>>> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
>>>
>>> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
>>>
>>> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
>>>
>>> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
>>>
>>> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
>
>
>
>
>
>
>
----- Original Message -----
From: Onestone
To: m...
Sent: Wednesday, July 25, 2012 18:20
Subject: Re: [msp430] Re: Suddenly unable to program chip
I am using slac050x, which reports itself as 5.10.1, so couldn't tell
you about later versions.
I'm forever having minor, and occasionally major issues with KS, but I
still think it's better than CCS, especially for an assembly writer like
myself. In general though the newer versions tend to be more stable than
older versions. I haven't had major issues when upgrading except with
older versions where sometimes KS seemed to cross up its directories,
now I just make sure all traces of IAR are removed before upgrading, and
I always keepe the previous few versions. I don't know how it would go
on Win 2000, I run Xp and have no issues
Al
On 26/07/2012 9:21 AM, baxtercodeworks wrote:
> Well, the sudden break kind of threw me. IAR KS 3.2 does not have an option for MSP430F1121A. I do know that the most recent IAR version does have an option for both MSP430F1121 and MSP430F1121A. I was hesitant because the error popup showed "(Device unknown)".
>
> I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
>
> I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
>
> --- In m..., Onestone wrote:
>> Hi Leroy :-P
>>
>> You're stuffing up the programmers now are you??
>>
>> Ok this problem occurs with certain types of MSP430. For example it
>> happens to me all the time with the MSP320F2254, which the device rerads
>> as a 2274. For me simply telling IAR to continue works fine.
>>
>> Ti embeds a device type code into the BSL., but there are a limited
>> number of codes, and some seem to be generic, however it may be, from
>> your post, that you are trying to call the device an 1121 when it is a
>> 1121A which should have its own device type. The BSL sits in flash from
>> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
>> BSL version. The CHIP ID sits at FF0 - FF1.
>>
>> The document you need to read is SLAU319B
>>
>> Hope that helps
>>
>> Al
>>
>> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
>>> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
>>>
>>> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
>>>
>>> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
>>>
>>> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
>>>
>>> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
>
>
>
>
>
>
>
>
Reply by ●July 26, 20122012-07-26
The capacitor from reset to GND should be no larger than 2.2nF
Al
On 26/07/2012 12:10 PM, Steve Mayfield wrote:
> We had some problems with IAR and the 1611 chip displaying the same error message. We tracked the problem down to a capacitor across the reset line (used to help reduce Reset switch bounce) that was too large, causing the JTAG reset part of the initialization sequence (generated by the FET pod) to be too long for the FET pod to get control thru the JTAG port. Reducing the value from 10uf to 0.1uf seemed to correct the issue.
> ----- Original Message -----
> From: Onestone
> To: m...
> Sent: Wednesday, July 25, 2012 18:20
> Subject: Re: [msp430] Re: Suddenly unable to program chip
>
> I am using slac050x, which reports itself as 5.10.1, so couldn't tell
> you about later versions.
>
> I'm forever having minor, and occasionally major issues with KS, but I
> still think it's better than CCS, especially for an assembly writer like
> myself. In general though the newer versions tend to be more stable than
> older versions. I haven't had major issues when upgrading except with
> older versions where sometimes KS seemed to cross up its directories,
> now I just make sure all traces of IAR are removed before upgrading, and
> I always keepe the previous few versions. I don't know how it would go
> on Win 2000, I run Xp and have no issues
>
> Al
>
> On 26/07/2012 9:21 AM, baxtercodeworks wrote:
> > Well, the sudden break kind of threw me. IAR KS 3.2 does not have an option for MSP430F1121A. I do know that the most recent IAR version does have an option for both MSP430F1121 and MSP430F1121A. I was hesitant because the error popup showed "(Device unknown)".
> >
> > I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
> >
> > I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
> >
> > --- In m..., Onestone wrote:
> >> Hi Leroy :-P
> >>
> >> You're stuffing up the programmers now are you??
> >>
> >> Ok this problem occurs with certain types of MSP430. For example it
> >> happens to me all the time with the MSP320F2254, which the device rerads
> >> as a 2274. For me simply telling IAR to continue works fine.
> >>
> >> Ti embeds a device type code into the BSL., but there are a limited
> >> number of codes, and some seem to be generic, however it may be, from
> >> your post, that you are trying to call the device an 1121 when it is a
> >> 1121A which should have its own device type. The BSL sits in flash from
> >> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
> >> BSL version. The CHIP ID sits at FF0 - FF1.
> >>
> >> The document you need to read is SLAU319B
> >>
> >> Hope that helps
> >>
> >> Al
> >>
> >> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
> >>> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
> >>>
> >>> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
> >>>
> >>> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
> >>>
> >>> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
> >>>
> >>> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
> >
> >
> >
> >
> >
> >
> >
> >
Al
On 26/07/2012 12:10 PM, Steve Mayfield wrote:
> We had some problems with IAR and the 1611 chip displaying the same error message. We tracked the problem down to a capacitor across the reset line (used to help reduce Reset switch bounce) that was too large, causing the JTAG reset part of the initialization sequence (generated by the FET pod) to be too long for the FET pod to get control thru the JTAG port. Reducing the value from 10uf to 0.1uf seemed to correct the issue.
> ----- Original Message -----
> From: Onestone
> To: m...
> Sent: Wednesday, July 25, 2012 18:20
> Subject: Re: [msp430] Re: Suddenly unable to program chip
>
> I am using slac050x, which reports itself as 5.10.1, so couldn't tell
> you about later versions.
>
> I'm forever having minor, and occasionally major issues with KS, but I
> still think it's better than CCS, especially for an assembly writer like
> myself. In general though the newer versions tend to be more stable than
> older versions. I haven't had major issues when upgrading except with
> older versions where sometimes KS seemed to cross up its directories,
> now I just make sure all traces of IAR are removed before upgrading, and
> I always keepe the previous few versions. I don't know how it would go
> on Win 2000, I run Xp and have no issues
>
> Al
>
> On 26/07/2012 9:21 AM, baxtercodeworks wrote:
> > Well, the sudden break kind of threw me. IAR KS 3.2 does not have an option for MSP430F1121A. I do know that the most recent IAR version does have an option for both MSP430F1121 and MSP430F1121A. I was hesitant because the error popup showed "(Device unknown)".
> >
> > I'm also concerned about compatibility, etc. - would there be any traps upgrading the IAR KS from v3.2 to v6.4? Or would I be better off going to a different compiler platform?
> >
> > I'm using Win2000, and the TI MSP-FET430 Flash Emulation Tool (Parallel port).
> >
> > --- In m..., Onestone wrote:
> >> Hi Leroy :-P
> >>
> >> You're stuffing up the programmers now are you??
> >>
> >> Ok this problem occurs with certain types of MSP430. For example it
> >> happens to me all the time with the MSP320F2254, which the device rerads
> >> as a 2274. For me simply telling IAR to continue works fine.
> >>
> >> Ti embeds a device type code into the BSL., but there are a limited
> >> number of codes, and some seem to be generic, however it may be, from
> >> your post, that you are trying to call the device an 1121 when it is a
> >> 1121A which should have its own device type. The BSL sits in flash from
> >> 0x0C00 to 0x0FFF, and the upper 16 bytes from 0x0FF0 are device info and
> >> BSL version. The CHIP ID sits at FF0 - FF1.
> >>
> >> The document you need to read is SLAU319B
> >>
> >> Hope that helps
> >>
> >> Al
> >>
> >> On 26/07/2012 8:28 AM, baxtercodeworks wrote:
> >>> I've been using the MSP430F1121A for some time. The app was written with the IAR kickstart v3.2. And I use the Debugger with TI hardware Emulator to program the chip.
> >>>
> >>> This has been working fine until I got a new batch of chips (perhaps 4 months ago?), now I get a message "Chosen derivative (MSP430F1121) and actual hardware do not match.
> >>>
> >>> I did have one old chip left over, and it programs just fine, so I'm thinking TI has changed something on the MSP4301121A. Any one experienced something like this?
> >>>
> >>> What is my best course? Upgrade to the newer IAR kickstart (v6.4)? Switch to a different compiler package (very small program, small budget.) Other? I'm also wondering about the tradoffs between a quick fix and a fix that will last longer.
> >>>
> >>> Or do I need to bang on TI about defective chips? (purchased from two different sources.)
> >
> >
> >
> >
> >
> >
> >
> >
Reply by ●July 26, 20122012-07-26
Well, I'm trying to program the chip before soldering it into the circuit.
I'm using the Flash Emulation Too (http://www.ti.com/tool/msp-fet430x110)
and the MSP-FETP430IF parallel port programmer -- neither of which work with the
latest shipments of chips, but work fine with older chips of the same P/N.
I'm thinking it would be beneficial to know if anyone here has recently programmed the MSP430F1121A, and if so, what were they using.
--- In m..., "Steve Mayfield" wrote:
>
> We had some problems with IAR and the 1611 chip displaying the same error message. We tracked the problem down to a capacitor across the reset line (used to help reduce Reset switch bounce) that was too large, causing the JTAG reset part of the initialization sequence (generated by the FET pod) to be too long for the FET pod to get control thru the JTAG port. Reducing the value from 10uf to 0.1uf seemed to correct the issue.
>
I'm thinking it would be beneficial to know if anyone here has recently programmed the MSP430F1121A, and if so, what were they using.
--- In m..., "Steve Mayfield" wrote:
>
> We had some problems with IAR and the 1611 chip displaying the same error message. We tracked the problem down to a capacitor across the reset line (used to help reduce Reset switch bounce) that was too large, causing the JTAG reset part of the initialization sequence (generated by the FET pod) to be too long for the FET pod to get control thru the JTAG port. Reducing the value from 10uf to 0.1uf seemed to correct the issue.
>
