Has anyone investigated whether the F1612 can be reprogrammed via the JTAG port.
I don't have a 4 wire JTAG, so I can't check it myself.
If the F1612 can be reprogrammed it greatly expands what can be done w/ a
LaunchPad.
Reg
Is the LaunchPad F1612 fuse blown?
Started by ●February 4, 2012
Reply by ●February 4, 20122012-02-04
All the F1611s on the LaunchPads I got can be reprogrammed.
So are the ones on all others FET tools I got from TI.
-OCY
--- In m..., "Reginald" wrote:
>
> Has anyone investigated whether the F1612 can be reprogrammed via the JTAG port. I don't have a 4 wire JTAG, so I can't check it myself.
>
> If the F1612 can be reprogrammed it greatly expands what can be done w/ a LaunchPad.
>
> Reg
>
So are the ones on all others FET tools I got from TI.
-OCY
--- In m..., "Reginald" wrote:
>
> Has anyone investigated whether the F1612 can be reprogrammed via the JTAG port. I don't have a 4 wire JTAG, so I can't check it myself.
>
> If the F1612 can be reprogrammed it greatly expands what can be done w/ a LaunchPad.
>
> Reg
>
Reply by ●February 6, 20122012-02-06
I am not 100% sure but if they blew the fuse they could never update the
firmware on the FET/Launch pads and considering what happened with the
MSPG2452(think that was the broken chip maybe it was MSP430G2553) and
the 1.4 rev of the Launchpad it is probably very wise they left updates
open.
Jake G.
On 2/4/2012 12:36 PM, old_cow_yellow wrote:
>
> All the F1611s on the LaunchPads I got can be reprogrammed.
> So are the ones on all others FET tools I got from TI.
>
> -OCY
>
> --- In m... ,
> "Reginald" wrote:
> >
> > Has anyone investigated whether the F1612 can be reprogrammed via
> the JTAG port. I don't have a 4 wire JTAG, so I can't check it myself.
> >
> > If the F1612 can be reprogrammed it greatly expands what can be done
> w/ a LaunchPad.
> >
> > Reg
> >
firmware on the FET/Launch pads and considering what happened with the
MSPG2452(think that was the broken chip maybe it was MSP430G2553) and
the 1.4 rev of the Launchpad it is probably very wise they left updates
open.
Jake G.
On 2/4/2012 12:36 PM, old_cow_yellow wrote:
>
> All the F1611s on the LaunchPads I got can be reprogrammed.
> So are the ones on all others FET tools I got from TI.
>
> -OCY
>
> --- In m... ,
> "Reginald" wrote:
> >
> > Has anyone investigated whether the F1612 can be reprogrammed via
> the JTAG port. I don't have a 4 wire JTAG, so I can't check it myself.
> >
> > If the F1612 can be reprogrammed it greatly expands what can be done
> w/ a LaunchPad.
> >
> > Reg
> >
Reply by ●February 6, 20122012-02-06
They do not use JTAG to update the firmware. The existing firmware inside F1611
has two parts. One part is able to erase and update the other part.
--- In m..., "Jake G." wrote:
>
> I am not 100% sure but if they blew the fuse they could never update the
> firmware on the FET/Launch pads and considering what happened with the
> MSPG2452(think that was the broken chip maybe it was MSP430G2553) and
> the 1.4 rev of the Launchpad it is probably very wise they left updates
> open.
>
> Jake G.
>
> On 2/4/2012 12:36 PM, old_cow_yellow wrote:
> >
> > All the F1611s on the LaunchPads I got can be reprogrammed.
> > So are the ones on all others FET tools I got from TI.
> >
> > -OCY
> >
> > --- In m... ,
> > "Reginald" wrote:
> > >
> > > Has anyone investigated whether the F1612 can be reprogrammed via
> > the JTAG port. I don't have a 4 wire JTAG, so I can't check it myself.
> > >
> > > If the F1612 can be reprogrammed it greatly expands what can be done
> > w/ a LaunchPad.
> > >
> > > Reg
> > >
> >
> >
>
--- In m..., "Jake G." wrote:
>
> I am not 100% sure but if they blew the fuse they could never update the
> firmware on the FET/Launch pads and considering what happened with the
> MSPG2452(think that was the broken chip maybe it was MSP430G2553) and
> the 1.4 rev of the Launchpad it is probably very wise they left updates
> open.
>
> Jake G.
>
> On 2/4/2012 12:36 PM, old_cow_yellow wrote:
> >
> > All the F1611s on the LaunchPads I got can be reprogrammed.
> > So are the ones on all others FET tools I got from TI.
> >
> > -OCY
> >
> > --- In m... ,
> > "Reginald" wrote:
> > >
> > > Has anyone investigated whether the F1612 can be reprogrammed via
> > the JTAG port. I don't have a 4 wire JTAG, so I can't check it myself.
> > >
> > > If the F1612 can be reprogrammed it greatly expands what can be done
> > w/ a LaunchPad.
> > >
> > > Reg
> > >
> >
> >
>
Reply by ●February 6, 20122012-02-06
What happened w/ rev 1.4 of the LaunchPad? I noticed when I pulled up the guide
a couple of days ago that the schematic was rev 1.5, but didn't see an
explanation anywhere.
I already had one rev 1.4 and just received two more along w/ a bunch of MSP430G2553s from Digikey. So it would be a big help to know if there is an issue I'm about to collide w/.
I've been able to run a simple paced loop on the 2553, but I'm just now getting the gcc toolchain, TI docs and example code in place. So I've not gotten down to anything more than a trivial test.
BTW Is the MSP430F2013 compatible w/ the LaunchPad? From looking at the datasheet it would appear to be, but TI doesn't list it among the compatible parts for the LaunchPad. Since none of the parts TI lists have 16 bit A/D, I'll need to make other arrangements to use the F2013 if it's not compatible.
Have Fun!
Reg
--- On Mon, 2/6/12, Jake G. wrote:
> From: Jake G.
> Subject: Re: [msp430] Re: Is the LaunchPad F1612 fuse blown?
> To: m...
> Date: Monday, February 6, 2012, 10:36 AM
> I am not 100% sure but if they blew
> the fuse they could never update the
> firmware on the FET/Launch pads and considering what
> happened with the
> MSPG2452(think that was the broken chip maybe it was
> MSP430G2553) and
> the 1.4 rev of the Launchpad it is probably very wise they
> left updates
> open.
>
> Jake G.
I already had one rev 1.4 and just received two more along w/ a bunch of MSP430G2553s from Digikey. So it would be a big help to know if there is an issue I'm about to collide w/.
I've been able to run a simple paced loop on the 2553, but I'm just now getting the gcc toolchain, TI docs and example code in place. So I've not gotten down to anything more than a trivial test.
BTW Is the MSP430F2013 compatible w/ the LaunchPad? From looking at the datasheet it would appear to be, but TI doesn't list it among the compatible parts for the LaunchPad. Since none of the parts TI lists have 16 bit A/D, I'll need to make other arrangements to use the F2013 if it's not compatible.
Have Fun!
Reg
--- On Mon, 2/6/12, Jake G. wrote:
> From: Jake G.
> Subject: Re: [msp430] Re: Is the LaunchPad F1612 fuse blown?
> To: m...
> Date: Monday, February 6, 2012, 10:36 AM
> I am not 100% sure but if they blew
> the fuse they could never update the
> firmware on the FET/Launch pads and considering what
> happened with the
> MSPG2452(think that was the broken chip maybe it was
> MSP430G2553) and
> the 1.4 rev of the Launchpad it is probably very wise they
> left updates
> open.
>
> Jake G.
Reply by ●February 6, 20122012-02-06
Looking at my notes I am pretty sure it was the 2452(was a while ago),
but what happened is the launchpad would not program the chip until you
did a firmware update. So if your chips are programming with out a
problem chances are you don't have the bug. If I have the time I will
find the TIe2e post that fixed it for me and post it here.
Jake G.
On 2/6/2012 10:21 AM, Reginald Beardsley wrote:
>
> What happened w/ rev 1.4 of the LaunchPad? I noticed when I pulled up
> the guide a couple of days ago that the schematic was rev 1.5, but
> didn't see an explanation anywhere.
>
> I already had one rev 1.4 and just received two more along w/ a bunch
> of MSP430G2553s from Digikey. So it would be a big help to know if
> there is an issue I'm about to collide w/.
>
> I've been able to run a simple paced loop on the 2553, but I'm just
> now getting the gcc toolchain, TI docs and example code in place. So
> I've not gotten down to anything more than a trivial test.
>
> BTW Is the MSP430F2013 compatible w/ the LaunchPad? From looking at
> the datasheet it would appear to be, but TI doesn't list it among the
> compatible parts for the LaunchPad. Since none of the parts TI lists
> have 16 bit A/D, I'll need to make other arrangements to use the F2013
> if it's not compatible.
>
> Have Fun!
> Reg
>
> --- On Mon, 2/6/12, Jake G. > > wrote:
>
> > From: Jake G. >
> > Subject: Re: [msp430] Re: Is the LaunchPad F1612 fuse blown?
> > To: m...
> > Date: Monday, February 6, 2012, 10:36 AM
> > I am not 100% sure but if they blew
> > the fuse they could never update the
> > firmware on the FET/Launch pads and considering what
> > happened with the
> > MSPG2452(think that was the broken chip maybe it was
> > MSP430G2553) and
> > the 1.4 rev of the Launchpad it is probably very wise they
> > left updates
> > open.
> >
> > Jake G.
but what happened is the launchpad would not program the chip until you
did a firmware update. So if your chips are programming with out a
problem chances are you don't have the bug. If I have the time I will
find the TIe2e post that fixed it for me and post it here.
Jake G.
On 2/6/2012 10:21 AM, Reginald Beardsley wrote:
>
> What happened w/ rev 1.4 of the LaunchPad? I noticed when I pulled up
> the guide a couple of days ago that the schematic was rev 1.5, but
> didn't see an explanation anywhere.
>
> I already had one rev 1.4 and just received two more along w/ a bunch
> of MSP430G2553s from Digikey. So it would be a big help to know if
> there is an issue I'm about to collide w/.
>
> I've been able to run a simple paced loop on the 2553, but I'm just
> now getting the gcc toolchain, TI docs and example code in place. So
> I've not gotten down to anything more than a trivial test.
>
> BTW Is the MSP430F2013 compatible w/ the LaunchPad? From looking at
> the datasheet it would appear to be, but TI doesn't list it among the
> compatible parts for the LaunchPad. Since none of the parts TI lists
> have 16 bit A/D, I'll need to make other arrangements to use the F2013
> if it's not compatible.
>
> Have Fun!
> Reg
>
> --- On Mon, 2/6/12, Jake G. > > wrote:
>
> > From: Jake G. >
> > Subject: Re: [msp430] Re: Is the LaunchPad F1612 fuse blown?
> > To: m...
> > Date: Monday, February 6, 2012, 10:36 AM
> > I am not 100% sure but if they blew
> > the fuse they could never update the
> > firmware on the FET/Launch pads and considering what
> > happened with the
> > MSPG2452(think that was the broken chip maybe it was
> > MSP430G2553) and
> > the 1.4 rev of the Launchpad it is probably very wise they
> > left updates
> > open.
> >
> > Jake G.
Reply by ●February 6, 20122012-02-06
Reginald Beardsley wrote:
> I've been able to run a simple paced loop on the 2553, but I'm just now getting the gcc toolchain, TI docs and example code in place. So I've not gotten down to anything more than a trivial test.
>
> BTW Is the MSP430F2013 compatible w/ the LaunchPad? From looking at the datasheet it would appear to be, but TI doesn't list it among the compatible parts for the LaunchPad. Since none of the parts TI lists have 16 bit A/D, I'll need to make other arrangements to use the F2013 if it's not compatible.
I thought I'd mention I've been working with the 2533 fine on the
launchpad. Just about done with what may be our first commercial
product!! The only catch was the uart tx and rx pins are swapped if you
want to use the launchpad port for testing.
And yes, the 2013 will develop on the launchpad from what I've read.
I'm using CCS for this, not GCC. The only issue I've seen is I can't
hover 64 bit ints, they all comeback zero even if they have the proper
value.
Best, Dan.
--
Newspapers are unable, seemingly to discriminate between a bicycle accident and the collapse of civilization.
George Bernard Shaw
> I've been able to run a simple paced loop on the 2553, but I'm just now getting the gcc toolchain, TI docs and example code in place. So I've not gotten down to anything more than a trivial test.
>
> BTW Is the MSP430F2013 compatible w/ the LaunchPad? From looking at the datasheet it would appear to be, but TI doesn't list it among the compatible parts for the LaunchPad. Since none of the parts TI lists have 16 bit A/D, I'll need to make other arrangements to use the F2013 if it's not compatible.
I thought I'd mention I've been working with the 2533 fine on the
launchpad. Just about done with what may be our first commercial
product!! The only catch was the uart tx and rx pins are swapped if you
want to use the launchpad port for testing.
And yes, the 2013 will develop on the launchpad from what I've read.
I'm using CCS for this, not GCC. The only issue I've seen is I can't
hover 64 bit ints, they all comeback zero even if they have the proper
value.
Best, Dan.
--
Newspapers are unable, seemingly to discriminate between a bicycle accident and the collapse of civilization.
George Bernard Shaw
Reply by ●February 6, 20122012-02-06
Dan,
THANK YOU!!!
I just built a level shifter to connect to the UART on the 2553. Most horrible looking piece of work I've ever done, but it's been 15+ years since I did any significant amount of electronics construction, so I just had to swallow my pride and accept that I'm starting over. I can't extemporize w/ a prototype board and a schematic the way I once could. So I'm pretty nervous about testing it.
Knowing that the pins might be swapped on the 2553 part is a huge help. Particularly since after sitting in storage for almost 10 years, my Tek 465 is unlikely to be helpful w/o a lot of attention. I'm giving a lot of thought to getting a Rigol 1102E. In part for the DSO function, and in larger part because socketed transistor instruments become very tempermental as they age.
Have Fun!
Reg
THANK YOU!!!
I just built a level shifter to connect to the UART on the 2553. Most horrible looking piece of work I've ever done, but it's been 15+ years since I did any significant amount of electronics construction, so I just had to swallow my pride and accept that I'm starting over. I can't extemporize w/ a prototype board and a schematic the way I once could. So I'm pretty nervous about testing it.
Knowing that the pins might be swapped on the 2553 part is a huge help. Particularly since after sitting in storage for almost 10 years, my Tek 465 is unlikely to be helpful w/o a lot of attention. I'm giving a lot of thought to getting a Rigol 1102E. In part for the DSO function, and in larger part because socketed transistor instruments become very tempermental as they age.
Have Fun!
Reg
Reply by ●February 6, 20122012-02-06
Reg,
>I'm giving a lot of thought to getting a Rigol 1102E
I picked one up about year ago; it's been pretty useful. Also, if you haven't run across it already, Dave Jones' EEVBlog.com has a couple of interesting reviews and hacks for that scope.
Bob
--- In m..., Reginald Beardsley wrote:
>
> Dan,
>
> THANK YOU!!!
>
> I just built a level shifter to connect to the UART on the 2553. Most horrible looking piece of work I've ever done, but it's been 15+ years since I did any significant amount of electronics construction, so I just had to swallow my pride and accept that I'm starting over. I can't extemporize w/ a prototype board and a schematic the way I once could. So I'm pretty nervous about testing it.
>
> Knowing that the pins might be swapped on the 2553 part is a huge help. Particularly since after sitting in storage for almost 10 years, my Tek 465 is unlikely to be helpful w/o a lot of attention. I'm giving a lot of thought to getting a Rigol 1102E. In part for the DSO function, and in larger part because socketed transistor instruments become very tempermental as they age.
>
> Have Fun!
> Reg
>
>I'm giving a lot of thought to getting a Rigol 1102E
I picked one up about year ago; it's been pretty useful. Also, if you haven't run across it already, Dave Jones' EEVBlog.com has a couple of interesting reviews and hacks for that scope.
Bob
--- In m..., Reginald Beardsley wrote:
>
> Dan,
>
> THANK YOU!!!
>
> I just built a level shifter to connect to the UART on the 2553. Most horrible looking piece of work I've ever done, but it's been 15+ years since I did any significant amount of electronics construction, so I just had to swallow my pride and accept that I'm starting over. I can't extemporize w/ a prototype board and a schematic the way I once could. So I'm pretty nervous about testing it.
>
> Knowing that the pins might be swapped on the 2553 part is a huge help. Particularly since after sitting in storage for almost 10 years, my Tek 465 is unlikely to be helpful w/o a lot of attention. I'm giving a lot of thought to getting a Rigol 1102E. In part for the DSO function, and in larger part because socketed transistor instruments become very tempermental as they age.
>
> Have Fun!
> Reg
>
Reply by ●February 6, 20122012-02-06
Reginald Beardsley wrote:
> Dan,
>
> THANK YOU!!!
Hi Reg,
Your welcome, thanks to you too.
Here is what I did for the board I'll put in the box.
I just soldered the wires to one side of the jumper thingies. A two bird
solution because the laptop for testing won't have the launchpad drivers
installed. I can just move the wires to a cp2102 or FTDI chip on a board
in the box to get usb access.
Best, Dan.
(And if you've seen some of the stuff I'd never show anyone you may not
think your stuff is ugly :)
--
"If they can get you asking the wrong questions, they dont
have to worry about answers."
-- Thomas Pynchon
> Dan,
>
> THANK YOU!!!
Hi Reg,
Your welcome, thanks to you too.
Here is what I did for the board I'll put in the box.
I just soldered the wires to one side of the jumper thingies. A two bird
solution because the laptop for testing won't have the launchpad drivers
installed. I can just move the wires to a cp2102 or FTDI chip on a board
in the box to get usb access.
Best, Dan.
(And if you've seen some of the stuff I'd never show anyone you may not
think your stuff is ugly :)
--
"If they can get you asking the wrong questions, they dont
have to worry about answers."
-- Thomas Pynchon
