SDrive troubles - help appreciated

[+slx]

I built an SDrive Max some time ago and used it infrequently. It was working with firmware 1.0 which I upgraded to the latest beta of 1.3 available on GitHub today. After re-flashing it it still works when connected to the Atari but I don't get any response from the touchscreen. The screen driver seems to be the right version (using another screen driver with a different but legible color scheme does not help either and I am pretty sure I have a 9341 screen anyway - at least that what it displays at startup). 

 

Could it be that the screen needs re-calibration? While the documentation says that touching the screen during startup will force calibration mode, this does not happen.

 

Any tricks/hints/suggestions welcome!

 

Thanks!

[Mrshoujo]

36 minutes ago, slx said:

Could it be that the screen needs re-calibration? While the documentation says that touching the screen during startup will force calibration mode, this does not happen.

Are you holding down your touch long enough? Think Long Tap using Chrome on Android to save an image.

[a8isa1]

Pressing on the touchscreen when powering up SDrive max should bring up the calibration screen, assuming the correct screen driver is installed

 

-SteveS

[Beeblebrox]

From De Re Sdrivemax website:https://atari8bit.net/tutorials/de-re-sdrive-max/

 

Once you have built your SDrive-MAX, it will need to have the SDrive-MAX software on it for it to work. You can get the latest release of the software from the GitHub page of the developers. The latest release is always at the top, you want the zip file from the assets section. Download it and unzip it; you will find some documents and five folders named “atmega328-<screen-driver>“. Pick the folder with the right driver for your screen. If you don’t know which driver your screen uses, it doesn’t matter, you can just do this for each folder in turn until you get the right one, you cannot brick your SDrive-MAX by doing this.

 

 

[+slx]

I tried all of them and the 9341 worked. I got a slightly different screen with strang colors using another but no touch with either.

[Beeblebrox]

perhaps the screen itself is faulty?

[+slx]

On 11/19/2022 at 10:37 AM, Beeblebrox said:

perhaps the screen itself is faulty?

It worked before I upgraded the firmware, so I doubt that a bit. But I should have another screen somewhere to test. Thanks for the hint.

[xrbrevin]

On 11/19/2022 at 9:37 AM, Beeblebrox said:

perhaps the screen itself is faulty?

maybe a clone, there are many about

[kbr]

Sounds like you haven't flashed the eeprom_writer.hex before.