- #Stencyl has reached 90 memory full#
- #Stencyl has reached 90 memory code#
- #Stencyl has reached 90 memory series#
Rotated 90 degrees due to limited row-memory's limiting long rows of horizontal text.
This Test-Patten shows its capabilities at high-resolution. That-said, this is a hack, use it wisely!). I had two systems with two different displays running constantly for months on end in a wide range of weather conditions, and both suffered only minor image degradation. (Note, this is likely hard on your display's pixels. Some displays can even handle refreshes as slow as once every 5 seconds, allowing for high-resolution graphics from a lowly 8-bit processor with only 512 BYTES of RAM and no external memory. Slow refresh-rates (even down to 1Hz) can be viewed as a steady image on many displays. (The high-resolution row-seg-buffer method has only been tested-functional on two displays so far).Ī key-factor is that TFT displays have inherent "memory" at each pixel.
#Stencyl has reached 90 memory code#
SO FAR, all this timing-sensitive code is written in AVR Assembly, so conversion to Xmegas might be a bit of an undertaking.
#Stencyl has reached 90 memory full#
Possibly even providing full 1024x768 resolution(?) at likely a few Hz refresh, with their higher system clocks. There's room for exploration, and they'd likely work well with the high-resolution/low-refresh-rate (row-seg-buffer) method and displays that can handle the lower bit-rates. This will limit the data-rate, and thus refresh-rate, and some/more displays may not sync at all. Unfortunately, from what I understand, they have an "extension" scheme that means the dead-timers necessary for my FPD-Link emulation-method don't run at the PLL frequency. Or you can erase all the chip."Ĭould be promising: faster, more memory, and actually cheaper than the ATTiny861. I bashed my head against the wall for a good 10 minutes before I realised that the preferred method of programming is via Atmel Flip using the built in bootloader over USB. The part ships with programming protection enabled and bootloader code already in place.
"If you use it let me save you some time if you don’t read a datasheet in full everytime you touch a new part. Thanks 'hboy' and ' Garbz' via the Hackaday Blog)ĪTXmegas? (see note below, also thanks ' bogdan' also from the HaD Blog)ĭidja see the ATtiny85 in the list? Yep, We're talking about driving an LVDS laptop display from an 8-pin 8-bit microcontroller! PLL?)ĪTmega32u4/16u4 looks like they'll do, and have USB to boot.
#Stencyl has reached 90 memory series#
The remainder of the AT90PWM series (AT90PWM316, etc) requires MINOR code-changesĪTmega32M1/64M1 should work.
The following can most-likely be used with LVDS displays, with minimal code-changes, but are untested: Most development has been done with this chip)ĪTtiny85 (3 shades of blue, 1 shade of Red, 1 of green 64 colors with row-dithering) The following are FUNCTIONAL with LVDS displays:ĪTtiny861 (48 colors, 64 with "row-dithering". (There's no 1024x768 limitation, these just happen to be the displays I've acquired)ĭata Image FG050720DWSWDGL1 - 10in 800圆00įor Parallel-TTL displays, any AVR with enough pins can be used.įor LVDS displays, the AVR must have at least two PWM channels with "dead-timers" (aka "Dead Time Insertion," "Dead-Time-Generators," "Power Stage Controllers"), running at PLL frequencies. Development has reached a pretty good stopping-point for a while, as the system is quite functional in many configurations, (but display donations are gladly accepted!):