LaunchFET: Tag connect for launchpad

[spirilis 1,265]

Ordering 6 of these, will send @@bluehash 5 of them after I confirm they work-

 

 

OSHpark gerbers: OSH_TC2030_eZFET_Adapter_v2_0.zip

 

DipTrace Schematic (PDF): DipTrace Schematic - TC2030_eZFET_Adapter_draft2.pdf

 

DipTrace Design Files: TC2030_eZFET_Adapter_draft2_diptrace_designfiles.zip

(includes DipTrace .dch schematic file, .dip PCB layout file)

 

I have a 1st generation of this board which successfully programs an MSP430F5172 on a new project PCB of mine using both the F5529 LaunchPad and the Wolverine LaunchPad's eZFET interface w/ TC2030-MCP.  That first edition didn't have a Vcc hookup, this 2nd edition does via jumper and provides jumpers for TXD, RXD (in case you want to disconnect those) and a power header for tapping into the eZFET's GND, 3.3V and 5V rails.

 

RJ12 connector is this part: http://www.mouser.com/Search/ProductDetail.aspx?R=95501-6669virtualkey53810000virtualkey538-95501-6669

 

TAG-CONNECT footprint pinout compatible with this board:

[greeeg 460]

Have you guys noticed that TI use the 10-pin tagConnect on the debug interface for the tiva launchads? Not sure if they use it, or the ICs are pre-programed before soldering.

 

Those board look good @sprilis, I noticed @@mbeals boards feature isolation circuitry. Do you not think it's necessary?

 

 

I personally have destroyed the programming capabilities of my F5529, I ran +5v into the FETs SBWTDIO pin, and the FET enumerates fine, but can't talk to chips. I suspect I just damaged the IO pin. but at only $12 to replace the whole board I've never bothered with isolation circuitry.

[spirilis 1,265]

Yeah the MSP430 LaunchPads don't have isolation either. Not too concerned with it.

 

Sent from my Galaxy Note 10.1

[bluehash 1,581]

@@mbeals @@spirilis @@greeeg @@Fred

Your cables came in today. Please confirm if you want them and I'll ship them over.

Thanks!

Hope I did not miss anyone.

[spirilis 1,265]

Thanks! Looks good, definitely interested.

 

Sent from my Galaxy Note II with Tapatalk 4

[dpharris 13]

I would like to go this route, too ... but will let you guys figure out a single (if possible) standard first.  Thanks.  

 

David

[Fred 453]

SPY-BI-TAG adapters too. Awesome! I'm definitely still interested.

 

I'm in the middle of a board design at the moment and hope to etch this weekend, so I'll add a TagConnect footprint. It's not a particularly cramped board (and likely to get a revision anyway) so I might leave the pin headers on too just in case I screw something up.

 

@@dpharris I think for SBW there isn't much point deviating from what TagConnect have done. 6 pins will do and it would seem counter-productive to go with a different pin out to to the one that the kit above gives you. Spirilis seems to have sensibly gone with the same for his adapter as far as I can tell.

[spirilis 1,265]

Yeah I reappropriated some of the non-SBW pins for power & UART basically.

 

Sent from my Galaxy Note II with Tapatalk 4

[bluehash 1,581]

Sweet! I'll get this posted out today/tmw. 

Fred, greeeg have replied. I have spirilis' address.

[greeeg 460]

@@spirilis layout looks ideal. 

 

I'm not sure if it could be moved around for easier board routing? As it is now it's compatible with those SPY-BI-TAG adapters. (UART would be shorted, but IC should still program)

 

I have to renew my Altium subscription before I can edit my PCBs. Maybe I should try a different CAD suite (q_q)

[spirilis 1,265]

 

@@spirilis layout looks ideal. 

 

I'm not sure if it could be moved around for easier board routing? As it is now it's compatible with those SPY-BI-TAG adapters. (UART would be shorted, but IC should still program)

 

I have to renew my Altium subscription before I can edit my PCBs. Maybe I should try a different CAD suite (q_q)

 

Well I've already built boards with this pinout so I'm at least keeping it put for my uses.  I worked out the UART pins so that basically the UART_RXD pin would be exposed to the Vcc Tool, which is OK as it would just see no activity, UART_TXD goes to TCK I believe which isn't used here... and I re-appropriated the Vcc Target as the Vcc Input, which is a bit different from the spy-bi-tag.  Not sure if that'll cause any trouble but I doubt it.  Worst that happens is if using the Spy-Bi-Tag with FET430UIF, you'll have to source power for the board externally w/o the FET430's help.  I'm mostly going to use this with the eZFET anyhow.

[greeeg 460]

I'll be using your pinout for my boards. 

I don't own a FET430UIF so I doubt I'll face any issues. I just thought that the FET might be driving the TCK pin when it powers up. (would only be logic level anyway.)

[spirilis 1,265]

I'll be using your pinout for my boards. 

I don't own a FET430UIF so I doubt I'll face any issues. I just thought that the FET might be driving the TCK pin when it powers up. (would only be logic level anyway.)

Ah yeah good point.  Well the TXD pin is probably going to be Hi-Z anyway on poweron

[mbeals 74]

awesome!  I'll PM you my address

[mbeals 74]

i just updated the repo with a newer version of the boards.  I updated the footprint of the tag connect footprint to match the one @@spirilis made and switched to the same RJ-12 connector as well.  Spirilis's works with the FET430UFI programmer and mine attaches to the programming header on the side of a launchpad....other than that, they are equivalent.

 

I also added another programming header layout that uses a 2x5 .05" pin header.  This small header takes very little room (similar to the tag-connect) and the pinout is symmetric, so you can't plug it in the wrong way.  It's a good alternative if you need a small footprint ICSP header but don't want to invest in a tag-connect cable.