Jump to content
43oh

Recommended Posts

Thanks for the update.

 

Which MCU did you settle for in the end? What's the bare minimum required to get this board to work?

 

Do you have plans to put the design up on the store or something?

 

Sorry I thought I had uploaded the new schematics+BOM. the board is pretty simple. basically I've taken TI's freely available ezFET lite schematics and created this board, this way it is fully compatible with their code.

I just used a MSP430f5528, so it's the biggest in the family. But this also ensures it's always fully compatible with TI's code. I don't want to re-invent the wheel here.

 

No plans to mass-sell this at the moment, I could make one off individual boards at cost.

 

It fills a very small niece market. Most people using the tag-connect for MSP430 work will be using it, via adapter with their UIF FETs for high volumes and wouldn't want to rely on a cheap programmer like this.

Link to post
Share on other sites
  • 3 weeks later...
  • Replies 62
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Soldered up a new board. Works like a charm, unfortunately I don't know actually have any target boards to use this with, as it's a different pinout.     Fuse is a 1206 footprint, but I ordered 0

I recently built my own ezFET lite based of the files that TI have made available.   Update 9/06: Works "kinda" as expected. Board disconnects from USB when a target board is attached and is bei

@@zeke I've added this to the silk on one of my new boards, Guess I'll see how it turns out.   Feels like there is too much free space in the clock.

Posted Images

If I made this programmer, can I use a Launchpad to upload the firmware to the MSP430F5528?

Do you think it is possible to make a single side board design? thinking in a homemade pcb....

Possible yes. The QFN has a pretty tight pitch. 0.25 track/gap are required. If you are confident in your home PCB etching then go ahead :)

 

I'm not sire if the G-launchpad will work. But the F5529LP and FR5969LP will be able to program the MSP430F5528

Link to post
Share on other sites
  • 2 months later...

Dear Greeeg.

Let me allow to say a big "Hey Good Work Man" :) .
Im also planning to build my own eZ-FET Lite, but i have many things what is not clear. The First is that , What is the exact size of the firmware. Is it possible to make it smaller??
I just would like to use it as a programmer, not needed the debugging functions. 

Link to post
Share on other sites

Im also planning to build my own eZ-FET Lite, but i have many things what is not clear. The First is that , What is the exact size of the firmware. Is it possible to make it smaller??

I just would like to use it as a programmer, not needed the debugging functions. 

 

If you want to have exact copy of eZ-FET Lite, than original MSP430F5528/5529 must be used. MSP430F5528 and MSP430F5529 are the same devices, except footprint. Maybe compatible part (from MSP430F552x family) with smaller flash size will work.

 

Flashing part (without debugging) probably can fit to MSP430F5510, but in this case code customization is needed, and question is how this part with changed original firmware will be recognized by TI / IAR or any other MSP430 development platform.

Link to post
Share on other sites

If you want to have exact copy of eZ-FET Lite, than original MSP430F5528/5529 must be used. MSP430F5528 and MSP430F5529 are the same devices, except footprint. Maybe compatible part (from MSP430F552x family) with smaller flash size will work.

 

Flashing part (without debugging) probably can fit to MSP430F5510, but in this case code customization is needed, and question is how this part with changed original firmware will be recognized by TI / IAR or any other MSP430 development platform.

Yes, you are right, it would be better an open source Firmware from TI. So the short answer is: built the exact copy or do nothing :)

 

what do you think , the 1:1 copy can supply the target board with enough power ? 

 

Link to post
Share on other sites

Yes, you are right, it would be better an open source Firmware from TI. So the short answer is: built the exact copy or do nothing :)

 

what do you think , the 1:1 copy can supply the target board with enough power ? 

 

 

Hardware, including supply, can be done by yourself on any way you want. Changing (shrinking down) original software is not one-day job, and finial result is unknown. I am already working on my own flasher so don't have any interest in customizing eZ-FET Lite software.

Link to post
Share on other sites

Yes, you are right, it would be better an open source Firmware from TI. So the short answer is: built the exact copy or do nothing :)

 

what do you think , the 1:1 copy can supply the target board with enough power ? 

 

 

There is an open source firmware from TI, provided with the MSP Debug stack. http://processors.wiki.ti.com/index.php/MSP_Debug_Stack

 

Not exactly simple, though.

Link to post
Share on other sites
  • 2 months later...

Hello,

 

I am new to this and I have recently built one of these EzFET Lite boards but am having problems when going to program using code composer. Board will program a MSP430G2553 when using IAR embedded workbench but will not program at all with code composer or in linux. It come up with an error that it could not set device VCC. Attached is a print screen of the error and the schematic. Have you any suggestions. What software package do you recommend to upload firmware to the programmer and what firmware should be uploaded. This should tell me if i am uploading the firmware correctly.

 

Thanks

 

Shane

ezFet.pdf

post-34674-0-09752200-1424423546_thumb.png

Link to post
Share on other sites
  • 1 month later...
...built one of these EzFET Lite boards but am having problems when going to program using code composer. Board will program a MSP430G2553 when using IAR embedded workbench but will not program at all with code composer or in linux. It come up with an error that it could not set device VCC....

 

Hi Shane, From this description, It appreas as though you have not properly flashed the custom BSL portion of the ezFET firmaware. Note that the BSL requires the programmer to send a specific unlock code, since the BSL does typically not need to be changed. I had trouble getting mspdebug to perform this task, however the cross platform MSPFlasher worked flawlessly.

Link to post
Share on other sites
  • 8 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...