In SX Microcontrollers, SX/B Compiler and SX-Key Tool, darco wrote:

I run into this issue all the time, and I'm amazed more people aren't aware of it. Maybe most people are using the SX-Key. *shrugs*

I'm thinking that this issue could be caused by one (or both) of the following:

1) When connecting the blitz to an already powered-on board ("Hot-plugging"), it is possible that an oscillator pin is being connected before both of the power pins are connected, which might put the SX chip on the blitz into an bad state. (If this is indeed the problem, it could be fixed by making sure that the oscillator pins on the connector are shorter than the power pins)

2) When the blitz is only connected to the computer, some of the power from the FTDI chip might be bleeding into the SX chip, putting it into a bad state. The only solution here (aside from a hardware revision) is to make sure that you always plug the blitz into the USB port last.

After coming up with the above mentioned procedure, I haven't bothered debugging the issue further. It would be nice if it could be fixed in a future hardware revision, so as to save others the frustration.

---------- End of Message ----------


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=229999#m230470

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2007 (http://www.dotNetBB.com)