Set the id by a code on unused GPIO (if any). 5 spare bits will give you 32 ID's. So the devices location on the board defines it's id.

Dan Miner wrote:
Yes, this sounds like it will work for me. Thanks for the information.

I'll need 2 or 3 connectors but that's lots better than 16 to 20
of them.  FYI - I found the gang programmer specification here: 
http://focus.ti.com/lit/ug/slau101a/slau101a.pdf

I haven't had time to read it all yet (I'll do that tomorrow).
But after a quick look, it seems that the same program image
needs to go to all devices.  I was hoping to have a different
image for each device. Specifically, 99% of the code is the same with a device ID in Flash or EEPROM. I need to have each device know which one it is on the board. Any ideas on that? If the programmer can't support it directly, I'm sure I'll think of something...

                                - Dan Miner


-----Original Message-----
From: Steve Underwood [mailto:ste...@coppice.org]
Sent: Tuesday, January 27, 2004 5:35 PM
To: mspgcc-users@lists.sourceforge.net
Subject: Re: [Mspgcc-users] Programming multiple MSP430's on a board


Hi Dan,

TI sell a gang programmer which does basically what you want for production. It keeps most of the JTAG lines common for up ro 8 devices, and uses just one special wire for each device to select which one gets programmed. This idea could be extended to a greater number of devices. The development tools, on the other hand, do not currently support this type of operation. They are designed for one-to-one connections between the JTAG tool and the device. If you can live with a connector per MCU for development, naybe this will work out OK for you.

Regards,
Steve

Dan Miner wrote:


I have an application where I'll have multiple MSP430's on
the same board.  Since the programming interface is JTAG it
should be a trivial matter to daisy chain the chips together
so they can all be programmed from a single connector.
I don't have the space for one connecter per MSP.

However the word I got from TI is that their software doesn't
support this.  Does anyone know a way to do this?  Does the
mspgcc tool set support this? If not, can someone add this functionality to the tool set?

I'll have prototype hardware in a week or two.  For software
development, we added a connector per MSP, but we'll need to
get rid of those for production.
FYI - The production boards will have 16 to 20 MSP430's on
them so the connectors take up a LOT of space.



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users




Reply via email to