Messages

1

TinyDuino Processors & TinyShields / Re: Cannot reprogram my Tinyduino

« on: May 27, 2016, 07:02:26 PM »

Solving the problem is easy once you realize what the problem is. The symptoms are identical to all of the other can't program because the programmer can't talk to the chip errors. All of those errors end up spewing a confusing set of messages about the "stk500...". Popular causes include connections on pins 1 or 2, power supply issues, wrong Arduino choice in the IDE, corrupt bootloader, etc... Figuring out which is the real problem is not easy. Although, this situation would only develop after loading a sketch with Serial.print() calls.

I read a few long threads turned up by googling those error messages. None of them mentioned "talking too much or too fast" as a cause. So I am assuming this issue is limited to codebender.cc, and within codebender.cc, it probably only appears in some configurations. I could get the behavior with the Chrome plugin on a MacBook Air, and a Chromebook, on both a real Uno, and on a TinyDuino. Since I can make it happen with the Uno, it definitely is not your problem.

If your customers have the issue, ask them if they are using Codebender. If so have them try using the standard Arduino IDE instead. If that isn't an option, they can also
 1. unplug the USB cable from their computer.
 2. fix the sketch so there is a delay() in any loop with Serial.print(), or put in a delay at the start of the program.
 3. Saved the fixed sketch.
 4. Hold "shift" and click on the refresh the page icon (the shift key gets Chrome to reload the Codebender plugin. Merely reloading the page is not sufficient.)
 5. Once Codebender finishes reloading, make sure it is the right sketch
 6. Plug in the TinyDuino
 7. Once the USB device shows up, click on "Run on Arduino"

If it doesn't work, try again. If it still doesn't work, try something else. Unfortunately, there are a gazillion errors that cause the same set of messages.

2

TinyDuino Processors & TinyShields / Re: Cannot reprogram my Tinyduino

« on: May 25, 2016, 10:57:38 AM »

Now that I think about it. The problem was not in the TinyDuino. I was using CodeBender.cc and 115kbaud on a not particularly fast Chromebook. The text being spewed by the TinyDuino was too much for the browser plugin. So the browser plugin was getting flaky. The browser plugin is either not sending the reset, or the timing was so messed up, that it wasn't useful.

I doubt people see this problem at all with the standard Arduino IDE. Or if they do see it, it only happens on really slows computers. Likewise, the codebender.cc browser plugin can probably handle lower baudrates, and/or running on faster computers.

3

TinyDuino Processors & TinyShields / Re: Cannot reprogram my Tinyduino

« on: May 10, 2016, 09:40:50 AM »

Just a "me too". I independently discovered the same behavior, including the same fix.

4

General Discussion / Can we make the boards glow in "Black Light"?

« on: October 22, 2015, 03:18:43 PM »

TinyCircuit products are tiny, and therefore, easy to lose. Some fluorescent paint or dye added to the boards would make them easier to find when misplaced. Those of us who are prone to losing things could turn off the main lights, and use a "black light" flashlight to search for the little boards.

Has anyone tried this? Which dyes or paints did you use? Did it work well?

It might take a little trial and error to figure out how to apply the paint or dye so it will last, while simultaneously not interfering with the electronics, or solderability of the TinyShield Proto Board.

Or am I the only one who repeatedly loses their computers and computer accessories? I didn't have this problem in 1982 with the VAX 11/750 I managed in college. So this might be an age thing.