Reply by Aaron Greer April 29, 20082008-04-29
I'm sorry to inform you that your EZ430 is dead.
The good news is that TI support should replace it for free. Create a service ticket and they should email you back with instructions for how to exchange it.

----- Original Message -----
From: "Hans"
To: m...
Sent: Monday, April 28, 2008 5:06:58 AM (GMT-0700) America/Denver
Subject: [msp430] Re: EZ430 firmware update? --hacking

Hello,

i dinĀ“t use my EZ430 for several Months..today i connected it to my
PC ?? the PC asked for update the tool ..i agreed...and my EZ430 is
dead.
Could anyone tell me, where firmware for this tool can be found ?

Thanks
Hans

--- In m... , "old_cow_yellow"
wrote:
>
> IAR might work too. But I used the free version of FET-Pro430 from
> www.elprotronc.com
>
> --- In m... , Aaron Greer wrote:
> >
> > Do you use the "memory dump" function in IAR or some other method
to
> get the flash image?
> >
> > ----- Original Message -----
> > From: "old_cow_yellow"
> > To: m...
> > Sent: Wednesday, October 10, 2007 1:10:38 PM (GMT-0700)
America/Denver
> > Subject: [msp430] Re: EZ430 firmware update? --hacking
> >
> >
> >
> >
> >
> >
> >
> > I solder those 6 wires to a working eZ430 and got the image of its
> Flash.
> >
> > --- In m... , Aaron Greer wrote:
> > >
> > > To do this, I think you would either need the EZ430 JTAG
firmware
> > image to download manually, or you'd have to try and program the
EZ430
> > concurrently (in parallel) with the functioning tool. Is there
any
> > other way to do this? If the first is the what you are trying to
do,
> > where did you find the EZ430 firmware?
> > >
> > > Like I said before, I RMA'd my broken EZ430, but I'd like to
know
> > what you've got in mind for the fix. I believe you are right
about the
> > similarities and differences. I installed IAR on a different
machine
> > today and noticed that the Windows Driver Installation dialog box
> > showed the UIF driver being loaded.
> > >
> > > ----- Original Message -----
> > > From: "old_cow_yellow"
> > > To: m...
> > > Sent: Wednesday, October 10, 2007 12:52:14 PM (GMT-0700)
> America/Denver
> > > Subject: [msp430] Re: EZ430 firmware update? --hacking
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-
tools use
> > > TUSB3410 chip to interface to the USB port of a PC. They both
use the
> > > same USB vender ID and same USB device ID. They both use
MSP430F1612
> > > chip to handle the JTAG signals for the target. They both are
capable
> > > of downloading firmware from the PC into the MSP430F1612.
> > >
> > > But the hardware interfaces to the target JTAG of UIF and eZ430
are
> > > different. The consequence is that these two similar but
different
> > > tools need similar but different firmware.
> > >
> > > I think (but not sure) the software in PC sometime mistakenly
> > > recognizes an eZ430 as an UIF, and offers to update the UIF
firmware.
> > > If the unlucky user accepts the offer, the UIF firmware is
downloaded
> > > into the eZ430 and it will not work anymore.
> > >
> > > I think (but again not sure) that I found a way to resurrect
such
> dead
> > > eZ430. I do not have such dead eZ430, thus I cannot try it
myself. Is
> > > there any body out there willing to try?
> > >
> > > You need an eZ430 that was killed by "firmware update", not
killed by
> > > other reasons.
> > >
> > > You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer,
or
> > > others all can do the job.
> > >
> > > You need to solder 6 wires from 6 of the 7 Test Points on the
dead
> > > eZ430 to the JTAG connector of the tool.
> > >
> > > If you have the above and willing to spend half an hour to try,
I
> will
> > > send you more details for you to try at your own risk.
> > >
> > > --- In m... , "old_cow_yellow"

> > > wrote:
> > > >
> > > > --- In m... , Aaron Greer
wrote:
> > > > >
> > > > > I have two files with similar names:
> > > > > msp430.dll (company = TI)
> > > > > sbmsp430.dll (company = Softbaugh)
> > > > > Both are located in: C:\Program Files\IAR Systems\Embedded
> > > > > Workbench 4.0\430\bin\
> > > > > Could the second one be causing a problem? The file
property
> > > > > comments for smsp430.dll says it is a "USBP Emulation DLL".
> > > >
> > > > ** I think "similar" names are fine; "identical" names are
more
> > > > dangerous.
> > > >
> > > > > I have been in contact with TI tech support and they are
> > > > > aware of the problem, but aren't sure of the cause. They
> > > > > are replacing my damaged EZ430 module for free and have
> > > > > asked for any information that could help them figure out
> > > > > the cause.
> > > >
> > > > ** Thanks.
> > > >
> > > > > If we can pass on our findings to them, it might help to
solve
> > > > > the problem for everyone.
> > > >
> > > > ** I will try to dig into this problem and post my findings.
> > > >
> > >
> > >
> > >
> > > --
> > > CONFIDENTIALITY NOTICE: This communication, and any files or
> > previous e-mail messages attached to it, is confidential
information
> > and may contain information that is privileged. It is for use of
the
> > named recipient(s) only.
> > > Do not read this e-mail if you are not the intended recipient.
If
> > you are not the intended recipient, or a person responsible for
> > delivering it to the intended recipient, please do not copy or
> > disclose its contents to any person or body.
> > > If you have received this transmission in error, please
immediately
> > notify us by e-mail and destroy the original transmission and its
> > attachments. Thank you.
> > >
> > >
> > >
> > >
> >
> >
> >
> > --
> > CONFIDENTIALITY NOTICE: This communication, and any files or
> previous e-mail messages attached to it, is confidential information
> and may contain information that is privileged. It is for use of the
> named recipient(s) only.
> > Do not read this e-mail if you are not the intended recipient. If
> you are not the intended recipient, or a person responsible for
> delivering it to the intended recipient, please do not copy or
> disclose its contents to any person or body.
> > If you have received this transmission in error, please
immediately
> notify us by e-mail and destroy the original transmission and its
> attachments. Thank you.
> >
> >
> >
> >
>


Beginning Microcontrollers with the MSP430

Reply by Hans April 28, 20082008-04-28
Hello,

i dint use my EZ430 for several Months..today i connected it to my
PC ?? the PC asked for update the tool ..i agreed...and my EZ430 is
dead.
Could anyone tell me, where firmware for this tool can be found ?

Thanks
Hans

--- In m..., "old_cow_yellow"
wrote:
>
> IAR might work too. But I used the free version of FET-Pro430 from
> www.elprotronc.com
>
> --- In m..., Aaron Greer wrote:
> >
> > Do you use the "memory dump" function in IAR or some other method
to
> get the flash image?
> >
> > ----- Original Message -----
> > From: "old_cow_yellow"
> > To: m...
> > Sent: Wednesday, October 10, 2007 1:10:38 PM (GMT-0700)
America/Denver
> > Subject: [msp430] Re: EZ430 firmware update? --hacking
> >
> >
> >
> >
> >
> >
> >
> > I solder those 6 wires to a working eZ430 and got the image of its
> Flash.
> >
> > --- In m... , Aaron Greer wrote:
> > >
> > > To do this, I think you would either need the EZ430 JTAG
firmware
> > image to download manually, or you'd have to try and program the
EZ430
> > concurrently (in parallel) with the functioning tool. Is there
any
> > other way to do this? If the first is the what you are trying to
do,
> > where did you find the EZ430 firmware?
> > >
> > > Like I said before, I RMA'd my broken EZ430, but I'd like to
know
> > what you've got in mind for the fix. I believe you are right
about the
> > similarities and differences. I installed IAR on a different
machine
> > today and noticed that the Windows Driver Installation dialog box
> > showed the UIF driver being loaded.
> > >
> > > ----- Original Message -----
> > > From: "old_cow_yellow"
> > > To: m...
> > > Sent: Wednesday, October 10, 2007 12:52:14 PM (GMT-0700)
> America/Denver
> > > Subject: [msp430] Re: EZ430 firmware update? --hacking
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-
tools use
> > > TUSB3410 chip to interface to the USB port of a PC. They both
use the
> > > same USB vender ID and same USB device ID. They both use
MSP430F1612
> > > chip to handle the JTAG signals for the target. They both are
capable
> > > of downloading firmware from the PC into the MSP430F1612.
> > >
> > > But the hardware interfaces to the target JTAG of UIF and eZ430
are
> > > different. The consequence is that these two similar but
different
> > > tools need similar but different firmware.
> > >
> > > I think (but not sure) the software in PC sometime mistakenly
> > > recognizes an eZ430 as an UIF, and offers to update the UIF
firmware.
> > > If the unlucky user accepts the offer, the UIF firmware is
downloaded
> > > into the eZ430 and it will not work anymore.
> > >
> > > I think (but again not sure) that I found a way to resurrect
such
> dead
> > > eZ430. I do not have such dead eZ430, thus I cannot try it
myself. Is
> > > there any body out there willing to try?
> > >
> > > You need an eZ430 that was killed by "firmware update", not
killed by
> > > other reasons.
> > >
> > > You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer,
or
> > > others all can do the job.
> > >
> > > You need to solder 6 wires from 6 of the 7 Test Points on the
dead
> > > eZ430 to the JTAG connector of the tool.
> > >
> > > If you have the above and willing to spend half an hour to try,
I
> will
> > > send you more details for you to try at your own risk.
> > >
> > > --- In m... , "old_cow_yellow"

> > > wrote:
> > > >
> > > > --- In m... , Aaron Greer
wrote:
> > > > >
> > > > > I have two files with similar names:
> > > > > msp430.dll (company = TI)
> > > > > sbmsp430.dll (company = Softbaugh)
> > > > > Both are located in: C:\Program Files\IAR Systems\Embedded
> > > > > Workbench 4.0\430\bin\
> > > > > Could the second one be causing a problem? The file
property
> > > > > comments for smsp430.dll says it is a "USBP Emulation DLL".
> > > >
> > > > ** I think "similar" names are fine; "identical" names are
more
> > > > dangerous.
> > > >
> > > > > I have been in contact with TI tech support and they are
> > > > > aware of the problem, but aren't sure of the cause. They
> > > > > are replacing my damaged EZ430 module for free and have
> > > > > asked for any information that could help them figure out
> > > > > the cause.
> > > >
> > > > ** Thanks.
> > > >
> > > > > If we can pass on our findings to them, it might help to
solve
> > > > > the problem for everyone.
> > > >
> > > > ** I will try to dig into this problem and post my findings.
> > > >
> > >
> > >
> > >
> > > --
> > > CONFIDENTIALITY NOTICE: This communication, and any files or
> > previous e-mail messages attached to it, is confidential
information
> > and may contain information that is privileged. It is for use of
the
> > named recipient(s) only.
> > > Do not read this e-mail if you are not the intended recipient.
If
> > you are not the intended recipient, or a person responsible for
> > delivering it to the intended recipient, please do not copy or
> > disclose its contents to any person or body.
> > > If you have received this transmission in error, please
immediately
> > notify us by e-mail and destroy the original transmission and its
> > attachments. Thank you.
> > >
> > >
> > >
> > >
> >
> >
> >
> > --
> > CONFIDENTIALITY NOTICE: This communication, and any files or
> previous e-mail messages attached to it, is confidential information
> and may contain information that is privileged. It is for use of the
> named recipient(s) only.
> > Do not read this e-mail if you are not the intended recipient. If
> you are not the intended recipient, or a person responsible for
> delivering it to the intended recipient, please do not copy or
> disclose its contents to any person or body.
> > If you have received this transmission in error, please
immediately
> notify us by e-mail and destroy the original transmission and its
> attachments. Thank you.
> >
> >
> >
>
Reply by Aaron Greer October 11, 20072007-10-11
Do you use the "memory dump" function in IAR or some other method to get the flash image?

----- Original Message -----
From: "old_cow_yellow"
To: m...
Sent: Wednesday, October 10, 2007 1:10:38 PM (GMT-0700) America/Denver
Subject: [msp430] Re: EZ430 firmware update? --hacking

I solder those 6 wires to a working eZ430 and got the image of its Flash.

--- In m... , Aaron Greer wrote:
>
> To do this, I think you would either need the EZ430 JTAG firmware
image to download manually, or you'd have to try and program the EZ430
concurrently (in parallel) with the functioning tool. Is there any
other way to do this? If the first is the what you are trying to do,
where did you find the EZ430 firmware?
>
> Like I said before, I RMA'd my broken EZ430, but I'd like to know
what you've got in mind for the fix. I believe you are right about the
similarities and differences. I installed IAR on a different machine
today and noticed that the Windows Driver Installation dialog box
showed the UIF driver being loaded.
>
> ----- Original Message -----
> From: "old_cow_yellow"
> To: m...
> Sent: Wednesday, October 10, 2007 12:52:14 PM (GMT-0700) America/Denver
> Subject: [msp430] Re: EZ430 firmware update? --hacking
>
> Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-tools use
> TUSB3410 chip to interface to the USB port of a PC. They both use the
> same USB vender ID and same USB device ID. They both use MSP430F1612
> chip to handle the JTAG signals for the target. They both are capable
> of downloading firmware from the PC into the MSP430F1612.
>
> But the hardware interfaces to the target JTAG of UIF and eZ430 are
> different. The consequence is that these two similar but different
> tools need similar but different firmware.
>
> I think (but not sure) the software in PC sometime mistakenly
> recognizes an eZ430 as an UIF, and offers to update the UIF firmware.
> If the unlucky user accepts the offer, the UIF firmware is downloaded
> into the eZ430 and it will not work anymore.
>
> I think (but again not sure) that I found a way to resurrect such dead
> eZ430. I do not have such dead eZ430, thus I cannot try it myself. Is
> there any body out there willing to try?
>
> You need an eZ430 that was killed by "firmware update", not killed by
> other reasons.
>
> You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer, or
> others all can do the job.
>
> You need to solder 6 wires from 6 of the 7 Test Points on the dead
> eZ430 to the JTAG connector of the tool.
>
> If you have the above and willing to spend half an hour to try, I will
> send you more details for you to try at your own risk.
>
> --- In m... , "old_cow_yellow"
> wrote:
> >
> > --- In m... , Aaron Greer wrote:
> > >
> > > I have two files with similar names:
> > > msp430.dll (company = TI)
> > > sbmsp430.dll (company = Softbaugh)
> > > Both are located in: C:\Program Files\IAR Systems\Embedded
> > > Workbench 4.0\430\bin\
> > > Could the second one be causing a problem? The file property
> > > comments for smsp430.dll says it is a "USBP Emulation DLL".
> >
> > ** I think "similar" names are fine; "identical" names are more
> > dangerous.
> >
> > > I have been in contact with TI tech support and they are
> > > aware of the problem, but aren't sure of the cause. They
> > > are replacing my damaged EZ430 module for free and have
> > > asked for any information that could help them figure out
> > > the cause.
> >
> > ** Thanks.
> >
> > > If we can pass on our findings to them, it might help to solve
> > > the problem for everyone.
> >
> > ** I will try to dig into this problem and post my findings.
> > --
> CONFIDENTIALITY NOTICE: This communication, and any files or
previous e-mail messages attached to it, is confidential information
and may contain information that is privileged. It is for use of the
named recipient(s) only.
> Do not read this e-mail if you are not the intended recipient. If
you are not the intended recipient, or a person responsible for
delivering it to the intended recipient, please do not copy or
disclose its contents to any person or body.
> If you have received this transmission in error, please immediately
notify us by e-mail and destroy the original transmission and its
attachments. Thank you.
>
>

--
CONFIDENTIALITY NOTICE: This communication, and any files or previous e-mail messages attached to it, is confidential information and may contain information that is privileged. It is for use of the named recipient(s) only.
Do not read this e-mail if you are not the intended recipient. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, please do not copy or disclose its contents to any person or body.
If you have received this transmission in error, please immediately notify us by e-mail and destroy the original transmission and its attachments. Thank you.
Reply by old_cow_yellow October 10, 20072007-10-10
IAR might work too. But I used the free version of FET-Pro430 from
www.elprotronc.com

--- In m..., Aaron Greer wrote:
>
> Do you use the "memory dump" function in IAR or some other method to
get the flash image?
>
> ----- Original Message -----
> From: "old_cow_yellow"
> To: m...
> Sent: Wednesday, October 10, 2007 1:10:38 PM (GMT-0700) America/Denver
> Subject: [msp430] Re: EZ430 firmware update? --hacking
>
> I solder those 6 wires to a working eZ430 and got the image of its
Flash.
>
> --- In m... , Aaron Greer wrote:
> >
> > To do this, I think you would either need the EZ430 JTAG firmware
> image to download manually, or you'd have to try and program the EZ430
> concurrently (in parallel) with the functioning tool. Is there any
> other way to do this? If the first is the what you are trying to do,
> where did you find the EZ430 firmware?
> >
> > Like I said before, I RMA'd my broken EZ430, but I'd like to know
> what you've got in mind for the fix. I believe you are right about the
> similarities and differences. I installed IAR on a different machine
> today and noticed that the Windows Driver Installation dialog box
> showed the UIF driver being loaded.
> >
> > ----- Original Message -----
> > From: "old_cow_yellow"
> > To: m...
> > Sent: Wednesday, October 10, 2007 12:52:14 PM (GMT-0700)
America/Denver
> > Subject: [msp430] Re: EZ430 firmware update? --hacking
> >
> >
> >
> >
> >
> >
> >
> > Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-tools use
> > TUSB3410 chip to interface to the USB port of a PC. They both use the
> > same USB vender ID and same USB device ID. They both use MSP430F1612
> > chip to handle the JTAG signals for the target. They both are capable
> > of downloading firmware from the PC into the MSP430F1612.
> >
> > But the hardware interfaces to the target JTAG of UIF and eZ430 are
> > different. The consequence is that these two similar but different
> > tools need similar but different firmware.
> >
> > I think (but not sure) the software in PC sometime mistakenly
> > recognizes an eZ430 as an UIF, and offers to update the UIF firmware.
> > If the unlucky user accepts the offer, the UIF firmware is downloaded
> > into the eZ430 and it will not work anymore.
> >
> > I think (but again not sure) that I found a way to resurrect such
dead
> > eZ430. I do not have such dead eZ430, thus I cannot try it myself. Is
> > there any body out there willing to try?
> >
> > You need an eZ430 that was killed by "firmware update", not killed by
> > other reasons.
> >
> > You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer, or
> > others all can do the job.
> >
> > You need to solder 6 wires from 6 of the 7 Test Points on the dead
> > eZ430 to the JTAG connector of the tool.
> >
> > If you have the above and willing to spend half an hour to try, I
will
> > send you more details for you to try at your own risk.
> >
> > --- In m... , "old_cow_yellow"
> > wrote:
> > >
> > > --- In m... , Aaron Greer wrote:
> > > >
> > > > I have two files with similar names:
> > > > msp430.dll (company = TI)
> > > > sbmsp430.dll (company = Softbaugh)
> > > > Both are located in: C:\Program Files\IAR Systems\Embedded
> > > > Workbench 4.0\430\bin\
> > > > Could the second one be causing a problem? The file property
> > > > comments for smsp430.dll says it is a "USBP Emulation DLL".
> > >
> > > ** I think "similar" names are fine; "identical" names are more
> > > dangerous.
> > >
> > > > I have been in contact with TI tech support and they are
> > > > aware of the problem, but aren't sure of the cause. They
> > > > are replacing my damaged EZ430 module for free and have
> > > > asked for any information that could help them figure out
> > > > the cause.
> > >
> > > ** Thanks.
> > >
> > > > If we can pass on our findings to them, it might help to solve
> > > > the problem for everyone.
> > >
> > > ** I will try to dig into this problem and post my findings.
> > >
> >
> >
> >
> > --
> > CONFIDENTIALITY NOTICE: This communication, and any files or
> previous e-mail messages attached to it, is confidential information
> and may contain information that is privileged. It is for use of the
> named recipient(s) only.
> > Do not read this e-mail if you are not the intended recipient. If
> you are not the intended recipient, or a person responsible for
> delivering it to the intended recipient, please do not copy or
> disclose its contents to any person or body.
> > If you have received this transmission in error, please immediately
> notify us by e-mail and destroy the original transmission and its
> attachments. Thank you.
> >
> >
> >
> >
>
> --
> CONFIDENTIALITY NOTICE: This communication, and any files or
previous e-mail messages attached to it, is confidential information
and may contain information that is privileged. It is for use of the
named recipient(s) only.
> Do not read this e-mail if you are not the intended recipient. If
you are not the intended recipient, or a person responsible for
delivering it to the intended recipient, please do not copy or
disclose its contents to any person or body.
> If you have received this transmission in error, please immediately
notify us by e-mail and destroy the original transmission and its
attachments. Thank you.
>
>
Reply by Microbit October 10, 20072007-10-10
Thanks Lichen,

That looks different.
Perhaps it's a bug in the driver code ? Dunno, but your theorem seems very plausible.
I use CrossWorks, so I don't suffer all those pains.

Best Regards,
Kris

-----Original Message-----
From: m... [mailto:m...] On Behalf Of old_cow_yellow
Sent: Thursday, 11 October 2007 5:52 AM
To: m...
Subject: [msp430] Re: EZ430 firmware update? --hacking

Kris,

One of my eZ430 has: USB\VID_0451&PID_F430\TUSB34103E410CDDC558FF43
Another eZ430 has--: USB\VID_0451&PID_F430\TUSB341017264545D858FFFB
And the UIP has----: USB\VID_0451&PID_F430\TUSB3410324B4534C255FFD9

-- Lichen

--- In m..., "Microbit" wrote:
>
> Hi Lichen,
>
> > TUSB3410 chip to interface to the USB port of a PC. They both use the
> > same USB vender ID and same USB device ID.
>
> That's pretty bad :-(
> Does the UIF have a unique ID (USB)? I don't use it, so I don't know.
> If it does, the enumeration can only confuse the 2 when the IDs
match AFAIK.
> Or at least, when the unique ID differs, you have to let WIN
register the new (identical) device
> to the same driver.
>
> Best Regards,
> Kris
>
> -----Original Message-----
> From: m... [mailto:m...] On
Behalf Of old_cow_yellow
> Sent: Thursday, 11 October 2007 4:52 AM
> To: m...
> Subject: [msp430] Re: EZ430 firmware update? --hacking
>
> Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-tools use
> TUSB3410 chip to interface to the USB port of a PC. They both use the
> same USB vender ID and same USB device ID. They both use MSP430F1612
> chip to handle the JTAG signals for the target. They both are capable
> of downloading firmware from the PC into the MSP430F1612.
>
> But the hardware interfaces to the target JTAG of UIF and eZ430 are
> different. The consequence is that these two similar but different
> tools need similar but different firmware.
>
> I think (but not sure) the software in PC sometime mistakenly
> recognizes an eZ430 as an UIF, and offers to update the UIF firmware.
> If the unlucky user accepts the offer, the UIF firmware is downloaded
> into the eZ430 and it will not work anymore.
>
> I think (but again not sure) that I found a way to resurrect such dead
> eZ430. I do not have such dead eZ430, thus I cannot try it myself. Is
> there any body out there willing to try?
>
> You need an eZ430 that was killed by "firmware update", not killed by
> other reasons.
>
> You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer, or
> others all can do the job.
>
> You need to solder 6 wires from 6 of the 7 Test Points on the dead
> eZ430 to the JTAG connector of the tool.
>
> If you have the above and willing to spend half an hour to try, I will
> send you more details for you to try at your own risk.
> --- In m..., "old_cow_yellow"
> wrote:
> >
> > --- In m..., Aaron Greer wrote:
> > >
> > > I have two files with similar names:
> > > msp430.dll (company = TI)
> > > sbmsp430.dll (company = Softbaugh)
> > > Both are located in: C:\Program Files\IAR Systems\Embedded
> > > Workbench 4.0\430\bin\
> > > Could the second one be causing a problem? The file property
> > > comments for smsp430.dll says it is a "USBP Emulation DLL".
> >
> > ** I think "similar" names are fine; "identical" names are more
> > dangerous.
> >
> > > I have been in contact with TI tech support and they are
> > > aware of the problem, but aren't sure of the cause. They
> > > are replacing my damaged EZ430 module for free and have
> > > asked for any information that could help them figure out
> > > the cause.
> >
> > ** Thanks.
> >
> > > If we can pass on our findings to them, it might help to solve
> > > the problem for everyone.
> >
> > ** I will try to dig into this problem and post my findings.
> >
>
>
Reply by old_cow_yellow October 10, 20072007-10-10
Kris,

One of my eZ430 has: USB\VID_0451&PID_F430\TUSB34103E410CDDC558FF43
Another eZ430 has--: USB\VID_0451&PID_F430\TUSB341017264545D858FFFB
And the UIP has----: USB\VID_0451&PID_F430\TUSB3410324B4534C255FFD9

-- Lichen

--- In m..., "Microbit" wrote:
>
> Hi Lichen,
>
> > TUSB3410 chip to interface to the USB port of a PC. They both use the
> > same USB vender ID and same USB device ID.
>
> That's pretty bad :-(
> Does the UIF have a unique ID (USB)? I don't use it, so I don't know.
> If it does, the enumeration can only confuse the 2 when the IDs
match AFAIK.
> Or at least, when the unique ID differs, you have to let WIN
register the new (identical) device
> to the same driver.
>
> Best Regards,
> Kris
>
> -----Original Message-----
> From: m... [mailto:m...] On
Behalf Of old_cow_yellow
> Sent: Thursday, 11 October 2007 4:52 AM
> To: m...
> Subject: [msp430] Re: EZ430 firmware update? --hacking
>
> Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-tools use
> TUSB3410 chip to interface to the USB port of a PC. They both use the
> same USB vender ID and same USB device ID. They both use MSP430F1612
> chip to handle the JTAG signals for the target. They both are capable
> of downloading firmware from the PC into the MSP430F1612.
>
> But the hardware interfaces to the target JTAG of UIF and eZ430 are
> different. The consequence is that these two similar but different
> tools need similar but different firmware.
>
> I think (but not sure) the software in PC sometime mistakenly
> recognizes an eZ430 as an UIF, and offers to update the UIF firmware.
> If the unlucky user accepts the offer, the UIF firmware is downloaded
> into the eZ430 and it will not work anymore.
>
> I think (but again not sure) that I found a way to resurrect such dead
> eZ430. I do not have such dead eZ430, thus I cannot try it myself. Is
> there any body out there willing to try?
>
> You need an eZ430 that was killed by "firmware update", not killed by
> other reasons.
>
> You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer, or
> others all can do the job.
>
> You need to solder 6 wires from 6 of the 7 Test Points on the dead
> eZ430 to the JTAG connector of the tool.
>
> If you have the above and willing to spend half an hour to try, I will
> send you more details for you to try at your own risk.
> --- In m..., "old_cow_yellow"
> wrote:
> >
> > --- In m..., Aaron Greer wrote:
> > >
> > > I have two files with similar names:
> > > msp430.dll (company = TI)
> > > sbmsp430.dll (company = Softbaugh)
> > > Both are located in: C:\Program Files\IAR Systems\Embedded
> > > Workbench 4.0\430\bin\
> > > Could the second one be causing a problem? The file property
> > > comments for smsp430.dll says it is a "USBP Emulation DLL".
> >
> > ** I think "similar" names are fine; "identical" names are more
> > dangerous.
> >
> > > I have been in contact with TI tech support and they are
> > > aware of the problem, but aren't sure of the cause. They
> > > are replacing my damaged EZ430 module for free and have
> > > asked for any information that could help them figure out
> > > the cause.
> >
> > ** Thanks.
> >
> > > If we can pass on our findings to them, it might help to solve
> > > the problem for everyone.
> >
> > ** I will try to dig into this problem and post my findings.
> >
>
>
Reply by old_cow_yellow October 10, 20072007-10-10
I solder those 6 wires to a working eZ430 and got the image of its Flash.

--- In m..., Aaron Greer wrote:
>
> To do this, I think you would either need the EZ430 JTAG firmware
image to download manually, or you'd have to try and program the EZ430
concurrently (in parallel) with the functioning tool. Is there any
other way to do this? If the first is the what you are trying to do,
where did you find the EZ430 firmware?
>
> Like I said before, I RMA'd my broken EZ430, but I'd like to know
what you've got in mind for the fix. I believe you are right about the
similarities and differences. I installed IAR on a different machine
today and noticed that the Windows Driver Installation dialog box
showed the UIF driver being loaded.
>
> ----- Original Message -----
> From: "old_cow_yellow"
> To: m...
> Sent: Wednesday, October 10, 2007 12:52:14 PM (GMT-0700) America/Denver
> Subject: [msp430] Re: EZ430 firmware update? --hacking
>
> Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-tools use
> TUSB3410 chip to interface to the USB port of a PC. They both use the
> same USB vender ID and same USB device ID. They both use MSP430F1612
> chip to handle the JTAG signals for the target. They both are capable
> of downloading firmware from the PC into the MSP430F1612.
>
> But the hardware interfaces to the target JTAG of UIF and eZ430 are
> different. The consequence is that these two similar but different
> tools need similar but different firmware.
>
> I think (but not sure) the software in PC sometime mistakenly
> recognizes an eZ430 as an UIF, and offers to update the UIF firmware.
> If the unlucky user accepts the offer, the UIF firmware is downloaded
> into the eZ430 and it will not work anymore.
>
> I think (but again not sure) that I found a way to resurrect such dead
> eZ430. I do not have such dead eZ430, thus I cannot try it myself. Is
> there any body out there willing to try?
>
> You need an eZ430 that was killed by "firmware update", not killed by
> other reasons.
>
> You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer, or
> others all can do the job.
>
> You need to solder 6 wires from 6 of the 7 Test Points on the dead
> eZ430 to the JTAG connector of the tool.
>
> If you have the above and willing to spend half an hour to try, I will
> send you more details for you to try at your own risk.
>
> --- In m... , "old_cow_yellow"
> wrote:
> >
> > --- In m... , Aaron Greer wrote:
> > >
> > > I have two files with similar names:
> > > msp430.dll (company = TI)
> > > sbmsp430.dll (company = Softbaugh)
> > > Both are located in: C:\Program Files\IAR Systems\Embedded
> > > Workbench 4.0\430\bin\
> > > Could the second one be causing a problem? The file property
> > > comments for smsp430.dll says it is a "USBP Emulation DLL".
> >
> > ** I think "similar" names are fine; "identical" names are more
> > dangerous.
> >
> > > I have been in contact with TI tech support and they are
> > > aware of the problem, but aren't sure of the cause. They
> > > are replacing my damaged EZ430 module for free and have
> > > asked for any information that could help them figure out
> > > the cause.
> >
> > ** Thanks.
> >
> > > If we can pass on our findings to them, it might help to solve
> > > the problem for everyone.
> >
> > ** I will try to dig into this problem and post my findings.
> >
>
> --
> CONFIDENTIALITY NOTICE: This communication, and any files or
previous e-mail messages attached to it, is confidential information
and may contain information that is privileged. It is for use of the
named recipient(s) only.
> Do not read this e-mail if you are not the intended recipient. If
you are not the intended recipient, or a person responsible for
delivering it to the intended recipient, please do not copy or
disclose its contents to any person or body.
> If you have received this transmission in error, please immediately
notify us by e-mail and destroy the original transmission and its
attachments. Thank you.
>
>
Reply by Microbit October 10, 20072007-10-10
Hi Lichen,

> TUSB3410 chip to interface to the USB port of a PC. They both use the
> same USB vender ID and same USB device ID.

That's pretty bad :-(
Does the UIF have a unique ID (USB)? I don't use it, so I don't know.
If it does, the enumeration can only confuse the 2 when the IDs match AFAIK.
Or at least, when the unique ID differs, you have to let WIN register the new (identical) device
to the same driver.

Best Regards,
Kris

-----Original Message-----
From: m... [mailto:m...] On Behalf Of old_cow_yellow
Sent: Thursday, 11 October 2007 4:52 AM
To: m...
Subject: [msp430] Re: EZ430 firmware update? --hacking

Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-tools use
TUSB3410 chip to interface to the USB port of a PC. They both use the
same USB vender ID and same USB device ID. They both use MSP430F1612
chip to handle the JTAG signals for the target. They both are capable
of downloading firmware from the PC into the MSP430F1612.

But the hardware interfaces to the target JTAG of UIF and eZ430 are
different. The consequence is that these two similar but different
tools need similar but different firmware.

I think (but not sure) the software in PC sometime mistakenly
recognizes an eZ430 as an UIF, and offers to update the UIF firmware.
If the unlucky user accepts the offer, the UIF firmware is downloaded
into the eZ430 and it will not work anymore.

I think (but again not sure) that I found a way to resurrect such dead
eZ430. I do not have such dead eZ430, thus I cannot try it myself. Is
there any body out there willing to try?

You need an eZ430 that was killed by "firmware update", not killed by
other reasons.

You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer, or
others all can do the job.

You need to solder 6 wires from 6 of the 7 Test Points on the dead
eZ430 to the JTAG connector of the tool.

If you have the above and willing to spend half an hour to try, I will
send you more details for you to try at your own risk.
--- In m..., "old_cow_yellow"
wrote:
>
> --- In m..., Aaron Greer wrote:
> >
> > I have two files with similar names:
> > msp430.dll (company = TI)
> > sbmsp430.dll (company = Softbaugh)
> > Both are located in: C:\Program Files\IAR Systems\Embedded
> > Workbench 4.0\430\bin\
> > Could the second one be causing a problem? The file property
> > comments for smsp430.dll says it is a "USBP Emulation DLL".
>
> ** I think "similar" names are fine; "identical" names are more
> dangerous.
>
> > I have been in contact with TI tech support and they are
> > aware of the problem, but aren't sure of the cause. They
> > are replacing my damaged EZ430 module for free and have
> > asked for any information that could help them figure out
> > the cause.
>
> ** Thanks.
>
> > If we can pass on our findings to them, it might help to solve
> > the problem for everyone.
>
> ** I will try to dig into this problem and post my findings.
>
Reply by old_cow_yellow October 10, 20072007-10-10
Both the MSP-FET430UIF (UIF) and the MSP-EZ430U (eZ430) USB-tools use
TUSB3410 chip to interface to the USB port of a PC. They both use the
same USB vender ID and same USB device ID. They both use MSP430F1612
chip to handle the JTAG signals for the target. They both are capable
of downloading firmware from the PC into the MSP430F1612.

But the hardware interfaces to the target JTAG of UIF and eZ430 are
different. The consequence is that these two similar but different
tools need similar but different firmware.

I think (but not sure) the software in PC sometime mistakenly
recognizes an eZ430 as an UIF, and offers to update the UIF firmware.
If the unlucky user accepts the offer, the UIF firmware is downloaded
into the eZ430 and it will not work anymore.

I think (but again not sure) that I found a way to resurrect such dead
eZ430. I do not have such dead eZ430, thus I cannot try it myself. Is
there any body out there willing to try?

You need an eZ430 that was killed by "firmware update", not killed by
other reasons.

You need a working 4-wire JTAG tool. UIF, PIF, Gang-Programmer, or
others all can do the job.

You need to solder 6 wires from 6 of the 7 Test Points on the dead
eZ430 to the JTAG connector of the tool.

If you have the above and willing to spend half an hour to try, I will
send you more details for you to try at your own risk.
--- In m..., "old_cow_yellow"
wrote:
>
> --- In m..., Aaron Greer wrote:
> >
> > I have two files with similar names:
> > msp430.dll (company = TI)
> > sbmsp430.dll (company = Softbaugh)
> > Both are located in: C:\Program Files\IAR Systems\Embedded
> > Workbench 4.0\430\bin\
> > Could the second one be causing a problem? The file property
> > comments for smsp430.dll says it is a "USBP Emulation DLL".
>
> ** I think "similar" names are fine; "identical" names are more
> dangerous.
>
> > I have been in contact with TI tech support and they are
> > aware of the problem, but aren't sure of the cause. They
> > are replacing my damaged EZ430 module for free and have
> > asked for any information that could help them figure out
> > the cause.
>
> ** Thanks.
>
> > If we can pass on our findings to them, it might help to solve
> > the problem for everyone.
>
> ** I will try to dig into this problem and post my findings.
>
Reply by old_cow_yellow October 6, 20072007-10-06
--- In m..., Aaron Greer wrote:
>
> I have two files with similar names:
> msp430.dll (company = TI)
> sbmsp430.dll (company = Softbaugh)
> Both are located in: C:\Program Files\IAR Systems\Embedded
> Workbench 4.0\430\bin\
> Could the second one be causing a problem? The file property
> comments for smsp430.dll says it is a "USBP Emulation DLL".

** I think "similar" names are fine; "identical" names are more
dangerous.

> I have been in contact with TI tech support and they are
> aware of the problem, but aren't sure of the cause. They
> are replacing my damaged EZ430 module for free and have
> asked for any information that could help them figure out
> the cause.

** Thanks.

> If we can pass on our findings to them, it might help to solve
> the problem for everyone.

** I will try to dig into this problem and post my findings.