Well, I got my TinyScreen Video Game Kit, but when I tried starting the TinyDuino, the green light turned on, but the screen didn't I turned it off, turned it back on, and the green light didn't work! I tried charging and starting it up, but nothing happened! I connected it to my PC, it showed a spark of life, and died. I don't know what to do! Please help! I don't wanna order another!

Does 'spark of life' mean you saw something on the screen, or the LEDs? It sounds like the processor board might not be programmed with a TinyScreen demo- can you try loading https://codebender.cc/sketch:90365 this and seeing if it is working?

Having similar issues. I ordered three Tinyscreens at the beginning of the month (two different orders). All three screens are not providing a display. Once in a blue moon, I may be able to turn them unit on and get a second or two worth of display, then they blank. Buttons work fine. I swapped out the units with an older Tinyscreen on hand and it works fine. The three screens with issues are all labeled Rev 5. The older screen is labeled Rev 4.

I just grabbed a couple Tinyscreens from stock and the example program seems to be working normally through both codebender and the IDE(1.6.8 with the latest library), so at this point I don't know what's wrong- can you send the screens back so I can take a look at them? We can send replacements ASAP and see if they work for you or wait until we figure out the issue. Send an email to info@tiny-circuits.com and let us know.

Thanks,
Ben

Thanks Ben. I will do that. Is there anything between rev 4 and 5 of that board that would cause me to revise code? It is just weird that all my new rev 5s were defective.

My TinyScreen+ Rev.3 suddenly stop working when I was debugging my code.
It doesn't appear in the COM ports anymore and there is nothing on the screen.
Resetting the device didn't help.
(BTW, to reset the device my one require to push the top button instead of the
closest to the power switch. Is this normal ?)

Any advices ?

Thanks,

Grimstone- technically yes, but only if you have a really old version of the library- otherwise, there shouldn't be any difference in user level code.

Terada, keep in mind TS+ is significantly different hardware. The correct button is the one closest to the USB port- some O-Watch documentation said 'closest to the power switch' in some places(please let me know if you are still seeing this anywhere). Give it another try with this in mind- while plugged in, power off, press the button closest to the USB port, power on again. Wait a few seconds, then check the COM port list a couple times to make sure the IDE is showing them properly. If it's still not working, send an email to info@tinycircuits.com

Well then Ben, let me test these screens with an example off the current library before sending any your way. The code I am using was written originally before the Tinyscreen had an official library and has been modified over time. However, the Tinyscreen calls have remained relatively untouched since the beginning. I'll keep you posted tonight.

Well... All three screens now work with the updated lib code which means 1) I don't need to send you guys anything back (awesome) and 2) I need to rewrite some code (sigh) to work with the new board rev. Maybe team TinyCircuits might consider listing board revision history changes in the footnotes somewhere of the products. It is great that you guys keep making things better and better, but we need to keep up with you.

Alright- As you say, good for our hardware, minus points for our documentation. The change I mentioned in Rev5 is that I implemented shutdown control for the OLED voltage boost circuit, something we totally missed in Rev4. I was able to implement this in software long before the hardware made it out there, so the relevant changes appear to be only in this commit from April 2015:

https://github.com/TinyCircuits/TinyCircuits-TinyScreen_Lib/commit/c649e1decf26fd0c0b4e379cbedeec5ff1675729

All that's happening is ensuring that the 'shutdown' pin controlled by the IO expander is in the correct state- hopefully an easy fix in your code. Let me know if this continues to cause problems.

I've put a band-aid note on the product page, but we will definitely try to improve this.