Hello all,
I have sampled a handful of the new MSP430F471xx chips, and I can't get the
first one to program. I am getting tempted to remove the chip and try another
from the sample bag.......but what are the odds of pulling a bad chip?
I have all of the proper linker files ect. But everytime I try to flash I get
"communication error, please connect the device and press retry". I'm
stumped, never had this issue before. Just to make sure it "wasn't me" I
downloaded the latest version of kickstart and did a fresh install to make sure
my IAR version wasn't screwing up. I got the same message. I am using a
USBPro JTAG, and although Softbaugh hasn't updated anything on that in
awhile, I doubt it would be the culprit.
Is there anything odd about the JTAG on these parts?
Anyone program one of these with success yet?
It seems to be a regular 5 wire JTAG.....am I missing something?
Thanks,
Andrew
New MSP430F471xx programming issues (communication error)
Started by ●July 27, 2009
Reply by ●July 27, 20092009-07-27
There are lots of possible causes for the trouble you have seen.
One of them is the board that you soldered the chip. If I were you, I would get a "Target board" from TI that has ZIF socket and try another chip from the "same bag".
--- In m..., "andyrg32" wrote:
>
> Hello all,
>
> I have sampled a handful of the new MSP430F471xx chips, and I can't get the first one to program. I am getting tempted to remove the chip and try another from the sample bag.......but what are the odds of pulling a bad chip?
>
> I have all of the proper linker files ect. But everytime I try to flash I get "communication error, please connect the device and press retry". I'm stumped, never had this issue before. Just to make sure it "wasn't me" I downloaded the latest version of kickstart and did a fresh install to make sure my IAR version wasn't screwing up. I got the same message. I am using a USBPro JTAG, and although Softbaugh hasn't updated anything on that in awhile, I doubt it would be the culprit.
>
> Is there anything odd about the JTAG on these parts?
>
> Anyone program one of these with success yet?
>
> It seems to be a regular 5 wire JTAG.....am I missing something?
>
> Thanks,
> Andrew
>
One of them is the board that you soldered the chip. If I were you, I would get a "Target board" from TI that has ZIF socket and try another chip from the "same bag".
--- In m..., "andyrg32" wrote:
>
> Hello all,
>
> I have sampled a handful of the new MSP430F471xx chips, and I can't get the first one to program. I am getting tempted to remove the chip and try another from the sample bag.......but what are the odds of pulling a bad chip?
>
> I have all of the proper linker files ect. But everytime I try to flash I get "communication error, please connect the device and press retry". I'm stumped, never had this issue before. Just to make sure it "wasn't me" I downloaded the latest version of kickstart and did a fresh install to make sure my IAR version wasn't screwing up. I got the same message. I am using a USBPro JTAG, and although Softbaugh hasn't updated anything on that in awhile, I doubt it would be the culprit.
>
> Is there anything odd about the JTAG on these parts?
>
> Anyone program one of these with success yet?
>
> It seems to be a regular 5 wire JTAG.....am I missing something?
>
> Thanks,
> Andrew
>
Reply by ●July 27, 20092009-07-27
Well,
Taking that suggestion, I populated another prototype with only the MSP chip. I also verified that all traces that go to it were OK. The JTAG is routed correctly, so is all of the power, and everything else attached to the MSP on proto 2 was going no-where since the MSP was the only device on the PCB. Still get the same error.
This is very odd. I have never used target boards before with the MSP because I have never really needed them. MSPs are usually fire and forget as far as I am concerned. But this is weird. The JTAG does attempt to talk with the MSP; because instead of getting the "There is no device connected" error, I get the "communication error" error....
There is just something fundamentally wrong with the way I am doing this.... I would think anyone else would have the same problem. I migrated from 423s to 427s, 4250s, and 4794s with no problems whatsoever. There is something different about this MSP and how it interacts with the JTAG.
Any other ideas?
--- In m..., "old_cow_yellow" wrote:
>
> There are lots of possible causes for the trouble you have seen.
>
> One of them is the board that you soldered the chip. If I were you, I would get a "Target board" from TI that has ZIF socket and try another chip from the "same bag".
>
> --- In m..., "andyrg32" wrote:
> >
> > Hello all,
> >
> > I have sampled a handful of the new MSP430F471xx chips, and I can't get the first one to program. I am getting tempted to remove the chip and try another from the sample bag.......but what are the odds of pulling a bad chip?
> >
> > I have all of the proper linker files ect. But everytime I try to flash I get "communication error, please connect the device and press retry". I'm stumped, never had this issue before. Just to make sure it "wasn't me" I downloaded the latest version of kickstart and did a fresh install to make sure my IAR version wasn't screwing up. I got the same message. I am using a USBPro JTAG, and although Softbaugh hasn't updated anything on that in awhile, I doubt it would be the culprit.
> >
> > Is there anything odd about the JTAG on these parts?
> >
> > Anyone program one of these with success yet?
> >
> > It seems to be a regular 5 wire JTAG.....am I missing something?
> >
> > Thanks,
> > Andrew
>
Taking that suggestion, I populated another prototype with only the MSP chip. I also verified that all traces that go to it were OK. The JTAG is routed correctly, so is all of the power, and everything else attached to the MSP on proto 2 was going no-where since the MSP was the only device on the PCB. Still get the same error.
This is very odd. I have never used target boards before with the MSP because I have never really needed them. MSPs are usually fire and forget as far as I am concerned. But this is weird. The JTAG does attempt to talk with the MSP; because instead of getting the "There is no device connected" error, I get the "communication error" error....
There is just something fundamentally wrong with the way I am doing this.... I would think anyone else would have the same problem. I migrated from 423s to 427s, 4250s, and 4794s with no problems whatsoever. There is something different about this MSP and how it interacts with the JTAG.
Any other ideas?
--- In m..., "old_cow_yellow" wrote:
>
> There are lots of possible causes for the trouble you have seen.
>
> One of them is the board that you soldered the chip. If I were you, I would get a "Target board" from TI that has ZIF socket and try another chip from the "same bag".
>
> --- In m..., "andyrg32" wrote:
> >
> > Hello all,
> >
> > I have sampled a handful of the new MSP430F471xx chips, and I can't get the first one to program. I am getting tempted to remove the chip and try another from the sample bag.......but what are the odds of pulling a bad chip?
> >
> > I have all of the proper linker files ect. But everytime I try to flash I get "communication error, please connect the device and press retry". I'm stumped, never had this issue before. Just to make sure it "wasn't me" I downloaded the latest version of kickstart and did a fresh install to make sure my IAR version wasn't screwing up. I got the same message. I am using a USBPro JTAG, and although Softbaugh hasn't updated anything on that in awhile, I doubt it would be the culprit.
> >
> > Is there anything odd about the JTAG on these parts?
> >
> > Anyone program one of these with success yet?
> >
> > It seems to be a regular 5 wire JTAG.....am I missing something?
> >
> > Thanks,
> > Andrew
>
Reply by ●July 27, 20092009-07-27
Hi,
> There is just something fundamentally wrong with the way I am doing
> this.... I would think anyone else would have the same problem. I
migrated
> from 423s to 427s, 4250s, and 4794s with no problems whatsoever. There is
> something different about this MSP and how it interacts with the JTAG.
>
> Any other ideas?
Why not ask Tom Baugh? I mean, it's his product, and therefore you might
stop all this farting about if you asked for support from the vendor rather
than wondering whether it might or might not be the chip mthe board, or the
JTAG device, hey?
You know, just my perspective.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!
> There is just something fundamentally wrong with the way I am doing
> this.... I would think anyone else would have the same problem. I
migrated
> from 423s to 427s, 4250s, and 4794s with no problems whatsoever. There is
> something different about this MSP and how it interacts with the JTAG.
>
> Any other ideas?
Why not ask Tom Baugh? I mean, it's his product, and therefore you might
stop all this farting about if you asked for support from the vendor rather
than wondering whether it might or might not be the chip mthe board, or the
JTAG device, hey?
You know, just my perspective.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!
Reply by ●July 27, 20092009-07-27
Thanks for that suggestion. I am not usually one to call tech support; because
I usually don't need it. Thanks for the idea, I did call Softbaugh and
found that the USBP does not support MSP430x (extended Memory) devices.
So there you have it.
I have a TI USB JTAG on its way already.
What a waste. I probably have 3 of the USBPs floating around the lab and they won't be supporting any new devices. blah...........
cheers,
Andrew
> > There is just something fundamentally wrong with the way I am doing
> > this.... I would think anyone else would have the same problem. I
> migrated
> > from 423s to 427s, 4250s, and 4794s with no problems whatsoever. There is
> > something different about this MSP and how it interacts with the JTAG.
> >
> > Any other ideas?
>
> Why not ask Tom Baugh? I mean, it's his product, and therefore you might
> stop all this farting about if you asked for support from the vendor rather
> than wondering whether it might or might not be the chip mthe board, or the
> JTAG device, hey?
>
> You know, just my perspective.
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!
>
So there you have it.
I have a TI USB JTAG on its way already.
What a waste. I probably have 3 of the USBPs floating around the lab and they won't be supporting any new devices. blah...........
cheers,
Andrew
> > There is just something fundamentally wrong with the way I am doing
> > this.... I would think anyone else would have the same problem. I
> migrated
> > from 423s to 427s, 4250s, and 4794s with no problems whatsoever. There is
> > something different about this MSP and how it interacts with the JTAG.
> >
> > Any other ideas?
>
> Why not ask Tom Baugh? I mean, it's his product, and therefore you might
> stop all this farting about if you asked for support from the vendor rather
> than wondering whether it might or might not be the chip mthe board, or the
> JTAG device, hey?
>
> You know, just my perspective.
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks V2 is out for LPC1700, LPC3100, LPC3200, SAM9, and more!
>
