July 14, 2009
It turns out that it was a bad USB cable. The 5V version only worked when I connected 5V pin to the 5V rail on my breadboard. The 3V3 version didn’t work. However, since I’ve switched cables, both work without connecting the 5V (or 3V3) pin to the breadboard power rail. Problem solved.
I just received 2 FTDI basics for 5V and 3.3V. I’m using it to communicate with an ATTint4313. The 5V version works fine when the chip is running at 8MHz. Windows loads the driver (Windows bell sound) and I can see text in a Putty window. Perfect.
However, if I switch to 3.3V and try to use the 3V3 version. Windows doesn’t even recognize that I’ve plugged anything in.
Am I missing something here?
about 2 years ago
I’m a little late to the party here, but I’m having some issues with stability. It doesn’t like when I reset my uC (Mega644P). I’m using code derived from summoningdark’s upgraded firmware. When the screen decides to work, it’s great. Sometime if i have a scope on one of the pins it starts just fine. Doesn’t matter which pin. On my scope, I see a lot of noise on the pins. Stuff way below the 5v it’s running on. Any special tricks? Reset operations? Pullup/Pulldown resistors, filter caps?
about 4 years ago
This is really nice. But it’s in CPP. I use the gcc (win-avr) compiler. Do you have a link to a C library like this? Otherwise I’ll have to try to port this to C. Which would be a real task because I have no experience with CPP.
I just got 2 of these. Haven’t had a chance to hook them up yet. But I gather that the LEDs are green. Has anyone managed to lift up the display and change the LEDs for white or other color?
about 6 years ago
Is there an application for generating the image.h files?
Or better yet a Code routine to generate the data on the fly?
I’d like to be able to display battery voltage without having to create 800 img files (0-80V by tenths)
No public wish lists :(
Forgot your password?
No account? Register one!