SDrive-max ILI9325 support added.

[willyvmm]

HI.

 

Some time go my friend (Drygol/Lamers) has bought a 2.8" display ... but received a 2.4" mcufriend based on ILI9325 chip.

As the firmware do not support this display, I have done "driver" that support this lcd controller. 

 

Link with compiled firmware and link to source code that support this LCD is available here: https://retrohax.net/atari-800-xl-refurb-sdrive-max/

 

Pull request is pending, and hopefully will be merged with official firmware soon.

 

Best

Willy

 

 

[+Mr Robot]

1 hour ago, willyvmm said:

Pull request is pending, and hopefully will be merged with official firmware soon.

Thank you!

[E474]

Thanks very much!

 

   If I can ask a naive question, how difficult is it to add support for a screen, the flip side being, are there a lot of different screens that you can plug into this model of Arduino?

[mamejay]

Tested with my screens I got.  Can only get a white screen.

If I use the normal firmware the writing is back to front and touch screen doesn't work

[willyvmm]

@E474 it depend on Your difficulty definition.

Compared to blinking LED id Rocket science.

Compared to Apollo guidance computers od easy.

Yo have to know how to read datasheet, how the software is working, how the hardware isvworking, and what to expect. Then is easy.

 

I have no idea how mamy LCD types are sharing same layout and can be used with Arduino.

 

@mamejay if Your LCD is working with original firmware, then  it is not ili9325.

 

The ili9325 seems to be an early version of lcd controller family, and is not compatible with newer chips. (Also more difficult to program).

 

I have dissected some of the mcufriend lcd's, and there is possibile to mount at least 5 different LCD on PCB that are almost identical. 

The Only way to identify your lcd chip is to run a diagnostic software. 

Another problem is quality. 2 of 4 was broken when arrived. Only white screen and problem with reading id. One of them has identified itself as Renesans R61xxx (afair).

 

So... It's lottery.

 

 

 

[mamejay]

On 10/9/2019 at 8:31 PM, willyvmm said:

@E474 it depend on Your difficulty definition.

Compared to blinking LED id Rocket science.

Compared to Apollo guidance computers od easy.

Yo have to know how to read datasheet, how the software is working, how the hardware isvworking, and what to expect. Then is easy.

 

I have no idea how mamy LCD types are sharing same layout and can be used with Arduino.

 

@mamejay if Your LCD is working with original firmware, then  it is not ili9325.

 

The ili9325 seems to be an early version of lcd controller family, and is not compatible with newer chips. (Also more difficult to program).

 

I have dissected some of the mcufriend lcd's, and there is possibile to mount at least 5 different LCD on PCB that are almost identical. 

The Only way to identify your lcd chip is to run a diagnostic software. 

Another problem is quality. 2 of 4 was broken when arrived. Only white screen and problem with reading id. One of them has identified itself as Renesans R61xxx (afair).

 

So... It's lottery.

 

 

 

Thanks for that.  What Diag software can I use to determine exact what the type of LCD display I have?  Seems a waste to have these screen and no use for them

[willyvmm]

Compiled diagnostic software has been attached to the blog post as well as link to source code repository.

 

If your screen is blank, and is a mcufriend type, likely is just broken. You may use serial console (arduino serial console) to get some debug output. 

 

https://retrohax.net/atari-800-xl-refurb-sdrive-max/

 

w.

[willyvmm]

HI again.

 

Finally i got a fully working display, so i can show You that is really working

 

 

Enjoy.

 

[mamejay]

Hi Willyvmm,

I ordered more screens and  ow the 2.8" screens have a RM68090 chip in the.  I have found that its supposed to be the same as a ili9325

I am useless at compiling code.  Is it possible to get your ready made hex files?  or guide me to a easy way to compile in Windows?

Thanks

 

[mamejay]

Found your firmware.  Unfortunately I still get a blank screen.  How do you go about adding support for a different screen.  What high level steps are required?  I have a friend that can help with the coding I just have no idea where to start.  Going from your Github I suspect that Display.c and makefile need to be updated.