Im tring to get this code to work with my 3x3 panel and it works with my arduino uno, but Im trying to program an attiny44 to work with this code, but it seems like its not displaying properly. It seems as if the pins are different. Here is my code, Im aware of the clock speed difference and Ive adjusted the delays and the delays appears to be fine.

Im tring to get this code to work with my 3x3 panel and it works with my arduino uno, but Im trying to program an attiny44 to work with this code, but it seems like its not displaying properly. It seems as if the pins are different.

Of course the pins are different. The 'core' you are using will map the Arduino pin names to physical pins. You'll have to look at the documentation for the core you are using to find out what that mapping is.

The core should also take care of the timing so you shouldn't need to modify delays to get it to work.

Im tring to get this code to work with my 3x3 panel and it works with my arduino uno, but Im trying to program an attiny44 to work with this code, but it seems like its not displaying properly. It seems as if the pins are different.

Of course the pins are different. The 'core' you are using will map the Arduino pin names to physical pins. You'll have to look at the documentation for the core you are using to find out what that mapping is.

The core should also take care of the timing so you shouldn't need to modify delays to get it to work.

Did you "burn a bootloader" to get the fuses set properly?

Yes Im aware of this, I have changed them to match. I know that its not the same as the arduino. Ive looked to the documentation and matched accordingly. One section of the sketch works fine but the rest is all over the place. I haven't "bootloaded" it yet so I should do that and give it a try.

Hey man! Unfortunately the attinies are just sort of "stupid". I've used the attiny84 (the same as yours but with 8KB of flash) in my project and it just seems that when you put allot of functions, loops, if's, for's, outputs and inputs it becomes exusted.

I don't know how familiar you are with using macros in C/C++, but they can make the task of storing constant bits in packed bytes a lot easier. Also, if you use the "const" keyword for arrays which should be constant, they should be stored in Flash area, not in SRAM, saving the precious SRAM space. Here is a small example of defining a graphic character using macros. This 8x8 pixel character (including space) uses only 8 bytes of constant Flash memory. Please note that I coded this on-the-fly and have not compiled it, so...