Amiga 1200 - internal Gotek and Blackberry Trackball

[solarmon]

Originally Posted by XsamX1987

That is some Beautiful work truly.

Question So when you buy the screen Does it come with an accompanying board for the ribbon to attach to for wiring it to the Gotek?

Yes, the OLED screen typically comes with the board (although, some you can get separately, I believe). However, only some comes with a frame and a detachable ribbon, which is a requirement for this solution.

See the various OLED screens I have tested with the Gotek:

https://github.com/solarmon/Gotek/wi...C-OLED-Screens

[katarakt]

Thanks. Solarmon, with these settings you told i got only the lower 2 blue rows as i mentioned before, but not the first yellow one. I'll try it tomorrow again with new copied ff.cfg and changing the settings again. Trackball is working without any problem as a normal 2-row display is working without any problems.

[solarmon]

FlsshFloppy may be caching your config.

You can reset it and get it to read the config file in again:

https://github.com/keirf/FlashFloppy...-File#defaults

[XsamX1987]

Originally Posted by solarmon

Yes, the OLED screen typically comes with the board (although, some you can get separately, I believe). However, only some comes with a frame and a detachable ribbon, which is a requirement for this solution.

See the various OLED screens I have tested with the Gotek:

https://github.com/solarmon/Gotek/wi...C-OLED-Screens

Thank you for getting back to me, another question so from looking at the link you provided I would have to modify the larger screens?

[solarmon]

Originally Posted by XsamX1987

Thank you for getting back to me, another question so from looking at the link you provided I would have to modify the larger screens?

Yes, if you want to mount it on/through the grill of the Amiga 1200 (or on top of the Gotek), I find the 2.42" DIY More screen the easiest to mod.

https://github.com/solarmon/Gotek/wi...IY-More-7-wire

[XsamX1987]

Originally Posted by solarmon

Yes, if you want to mount it on/through the grill of the Amiga 1200 (or on top of the Gotek), I find the 2.42" DIY More screen the easiest to mod.

https://github.com/solarmon/Gotek/wi...IY-More-7-wire

Thanks but I just read the changing of resistors, my eyesight and my soldering skills are not the best so I will leave this one for the time being.

[katarakt]

Everytime you power-on FlashFloppy it reads the config again, no need for reset but i've tried this too and all the same. I'm going to send the pictures to Keir, maybe the firmware needs some corrections.

[solarmon]

Originally Posted by katarakt

Everytime you power-on FlashFloppy it reads the config again, no need for reset but i've tried this too and all the same. I'm going to send the pictures to Keir, maybe the firmware needs some corrections.

Join the FlashFloppy Facebook group and post the issue, with pictures, on there.

[solarmon]

@katarakt

Did you manage to get it working?

[katarakt]

No. This doesn't work how it should. Somthing in firmware is wrong i think. Config file is correct, it should work. I don't have facebook and i don't have a github account to post it there. 2 row display is working fine. I'll waiting for the 3rd 128x64 OLED and will check again. First doesn't work at all (exactly the one whats on your list you've posted, i think its damaged from transportation), second the one what i posted here and third will be the next surprise. If this doesn't work too i'll never try those again, don't have the time.

This is the one which is not working right, i can't get all 3 rows showing on the display:

[solarmon]

Originally Posted by katarakt

No. This doesn't work how it should. Somthing in firmware is wrong i think. Config file is correct, it should work. I don't have facebook and i don't have a github account to post it there. 2 row display is working fine. I'll waiting for the 3rd 128x64 OLED and will check again. First doesn't work at all (exactly the one whats on your list you've posted, i think its damaged from transportation), second the one what i posted here and third will be the next surprise. If this doesn't work too i'll never try those again, don't have the time.

This is the one which is not working right, i can't get all 3 rows showing on the display:

Send me your FF.cfg file (put it in The Zone?) and I will try it out.

The only difference I can see, is that you have a two colour display - the top x rows are a difference colour to the rest of the screen. I don't know if this makes a significant difference, but I have not tested these types of OLED screens.

Maybe I'll get one myself to try out.

[solarmon]

And my 128x64 0.96" OLED screen (not exactly the same as yours, looking at the back of it) is working fine with three lines, using FF 3.2a:



And here is the FF.cfg for it:

## FF.CFG: Example FlashFloppy Configuration File

# Place in the root folder or FF/ subfolder of your USB drive.
# Uncommented lines below are the default settings.
# Uncommented options cannot be overridden by settings in other config files.

##
## DRIVE EMULATION

# Floppy-drive interface mode
# shugart: P2=DSKCHG, P34=RDY
# ibmpc: P2=unused, P34=DSKCHG
# ibmpc-hdout: P2=HD_OUT, P34=DSKCHG (not generally needed: prefer 'ibmpc')
# akai-s950: P2=HD_OUT, P34=RDY (Akai S950)
# amiga: P2=DSKCHG, P34=DRIVE_ID (not generally needed: prefer 'shugart')
# jc: JC closed: ibmpc, JC open: shugart
interface = jc

# Host platform: Improves image-format detection for generic types such as IMG
# acorn: Acorn ADFS
# akai: Akai (S01, S20, S950), Korg, SC Prophet 3000
# casio: Casio (FZ-1)
# dec: DEC (RX33, RX50)
# ensoniq: Ensoniq (ASR, TS, etc)
# fluke: Fluke 9100
# gem: General Music (S2, S3)
# kaypro: Kaypro
# memotech: Memotech
# msx: MSX
# nascom: Nascom
# pc98: NEC PC-98
# pc-dos: PC DOS Format (geometry determined from Bios Parameter Block)
# tandy-coco: Tandy Color Computer (CoCo)
# ti99: TI-99/4A
# uknc: UKNC / DVK Soviet PDP-11
# unspecified: Common default geometries (including IBM PC)
host = unspecified

# Pins 2 & 34 output (drive->host) manual configuration
# auto: Auto-configure from interface= setting
# nc: Unused/No Connection [eg. if pin is an input (host->drive) on your host]
# low: Always 0 volts (0v)
# high: Always 5 volts (5v)
# rdy: Drive ready (Ready = 0v)
# nrdy: Logical complement of above
# dens: Density mode (High Density = 0v)
# ndens: Logical complement of above
# chg: Disk changed (Changed = 0v)
# nchg: Logical complement of above
# Values: auto, nc, low, high, rdy, nrdy, dens, ndens, chg, nchg
pin02 = auto
pin34 = auto

# Forcibly write-protect images, or respect the FAT read-only attribute?
# Values: yes | no
write-protect = no

# Filter glitches in the SIDE-select signal shorter than N microseconds
# Values: 0 <= N <= 255
side-select-glitch-filter = 0

# Rotational offset of data after a track change
# instant: No rotation during track change
# realtime: Emulate rotation of disk while track is changing
# Values: instant | realtime
track-change = instant

# Index pulses suppressed when RDATA and WDATA inactive?
# Values: yes | no
index-suppression = yes

# Milliseconds from head-step start to RDATA active.
# Values: 0 <= N <= 255
head-settle-ms = 12

# Milliseconds delay from motor-on to drive ready.
# On a standard unmodified Gotek the motor signal is not connected and a
# non-default value here will have no effect. Most systems and software do
# not care about correct motor behaviour, and default (ignore) works fine.
# Values: ignore | 0 <= N <= 1000
motor-delay = ignore

# What causes the disk-change (chg) signal to reset?
# step: Step command received
# pa14: CHGRST (pin 1 on old Sony drives), connected to PA14 (JTCK/SWCLK)
chgrst = step

##
## STARTUP / INITIALISATION

# Disk image loaded or ejected at startup?
# Values: yes | no
ejected-on-startup = no

# Which image (or folder) is selected at startup?
# last: Last-selected item at power-off (recorded in IMAGE_A.CFG)
# static: Static path specified in IMAGE_A.CFG
# init: First item in root folder
# Values: last | static | init
image-on-startup = last

# Time in milliseconds to attempt to probe attached display.
# You may set this to 0 if you have a 2-digit LED display attached.
# Values: 0 <= N <= 65535
display-probe-ms = 3000

##
## IMAGE NAVIGATION

# Auto-select the current file after N seconds
# N=0: disable auto-select
# Values: 0 <= N <= 255
autoselect-file-secs = 2

# Auto-select the current folder after N seconds
# N=0: disable auto-select
# Values: 0 <= N <= 255
autoselect-folder-secs = 2

# Sorting of folder entries in native navigation mode.
# always: Always sort folder entries. Large folders may be truncated.
# never: Never sort folder entries, instead presenting them in FAT order.
# small: Only sort folders which are small enough to sort in full.
# Values: always | never | small
folder-sort = always

# Priority of files vs subfolders when sorting folder entries:
# folders: Folders listed before files
# files: Files listed before folders
# none: Files and folders are not differentiated
# Values: folders | files | none
sort-priority = folders

# Navigation mode for selecting images/slots
# native:  Navigate through all valid images/dirs
# indexed: Navigate through DSKA0000, DSKA0001, ...
# default: native unless overridden by HxC-compat-mode config
nav-mode = default

# When navigating slots or folder, loop at min/max?
# Values: yes | no
nav-loop = yes

# Actions of first two buttons.
#              B1     | B2     | Both
# zero:        Prev   | Next   | Slot 0
# eject:       Prev   | Next   | Eject/Insert
# rotary:      Up-dir | Select/Eject/Insert | -
# rotary-fast: Prev   | Next   | Up-dir [Prev/Next are accelerated]
# reverse:     Reverse sense of B1 and B2
# Multiple values can be separated by commas, eg twobutton-action=eject,reverse
twobutton-action = rotary

# Input sensor type at the rotary-encoder inputs (pins PC10 and PC11):
#  [full | half | quarter]:
#    Rotary encoder, identified by fraction of a Gray-code cycle performed
#    per detent/click. If default value ('full') requires multiple
#    clicks/detents to move position then change to 'half' (if 2 clicks
#    per move) or 'quarter' (if 4 clicks).
#  [trackball]:
#    Blackberry-style trackball (eg. using Hall-effect sensors).
#  [buttons]:
#    Push-to-ground Prev/Next buttons.
#  [reverse]:
#    If the input is working in reverse, use this option to swap directions.
# Multiple values can be separated by commas, eg rotary=quarter,reverse
# Values: none | quarter | half | full | trackball | buttons | reverse
rotary = trackball

# Prefix for image names in indexed navigation mode. String can be empty ("").
indexed-prefix = "DSKA"

##
## DISPLAY

# Display Type: <type>[-rotate][-narrow]
# auto: Auto-detect (7-seg LED, LCD, OLED)
# lcd-CCxRR: CCxRR backlit LCD with I2C backpack (16<=CC<=40, 02<=RR<=04)
# oled-128xNN: 128xNN I2C OLED (NN = 32 | 64)
#  -rotate:     OLED view is rotated 180 degrees
#  -narrow[er]: OLED view is restricted to Gotek display cutout
#               (-narrow: 18 chars; -narrower: 16 chars)
#  -ztech:      ZHONGJY_TECH 2.23" 128x32 SSD1305 OLED display
# Values: auto | lcd-CCxRR | oled-128xNN[-rotate][-narrow[er]][-ztech]

display-type = oled-128x64
#display-type = oled-128x32-ztech
#display-type = oled-128x64-narrow-rotate

# OLED Font. Narrow and wide options.
# Narrower 6x13 font permits:
#  - More characters per row
#  - Use of Gotek display cutout (eg. "display-type=oled-128x32-narrow")
# Values: 6x13 | 8x16
oled-font = 6x13

# OLED contrast/brightness.
# Values: 0 <= N <= 255
oled-contrast = 0

# Text height and arrangement on LCD/OLED
# 'default', or a comma-separated list (one entry per LCD/OLED row, top down).
# Each list item is a digit plus optional height specifier: <content-row>[d]
#  content-row: '0-3' = specified content row, '7' = blank
#    0: Current image name
#    1: Status
#    2: Image/Volume info
#    3: Current subfolder name
#  height specifier: 'd' = double height (32px, OLED only; ignored for LCD)
# 'default' depends on display, eg.: oled-128x32='0,1' ; oled-128x64='3,0d,1'
# Values: [0-7][d] | default
display-order = default

# Turn an LCD or OLED display off after N seconds of inactivity
# N=0: always off; N=255: always on
# Values: 0 <= N <= 255
display-off-secs = 255

# Automatically switch LCD/OLED display on when there is drive activity?
# Values: yes | no
display-on-activity = yes

# LCD/OLED long filename scroll rate in milliseconds per update
# Values: 100 <= N <= 65535
display-scroll-rate = 200

# LCD/OLED pause time at start/end of scroll, in milliseconds
# Zero means endless scroll
# Values: 0 <= N <= 65535
display-scroll-pause = 2000

# LCD/OLED long filename scroll rate during navigation (ms per update)
# Values: 0 <= N <= 65535
nav-scroll-rate = 80

# LCD/OLED long filename pause before scroll, during navigation (milliseconds)
# Values: 0 <= N <= 65535
nav-scroll-pause = 300

##
## MISCELLANEOUS

# Speaker volume for head STEP
# Values: 0 <= N <= 20
step-volume = 10

# Report the specified version number to host software
# Values: <quoted-string> ("" means report real version)
# eg. da-report-version = "v3.0.0.0"
da-report-version = ""

# Automatically extend certain types of truncated image file (SSD,DSD,TRD)?
# Values: yes | no
extend-image = yes

[katarakt]

This is the cfg for my OLED showing only two rows FF3.2a:

## FF.CFG: Example FlashFloppy Configuration File

# Place in the root folder or FF/ subfolder of your USB drive.
# Uncommented lines below are the default settings.
# Uncommented options cannot be overridden by settings in other config files.

##
## DRIVE EMULATION

# Floppy-drive interface mode
# shugart: P2=DSKCHG, P34=RDY
# ibmpc: P2=unused, P34=DSKCHG
# ibmpc-hdout: P2=HD_OUT, P34=DSKCHG (not generally needed: prefer 'ibmpc')
# akai-s950: P2=HD_OUT, P34=RDY (Akai S950)
# amiga: P2=DSKCHG, P34=DRIVE_ID (not generally needed: prefer 'shugart')
# jc: JC closed: ibmpc, JC open: shugart
interface = jc

# Host platform: Improves image-format detection for generic types such as IMG
# acorn: Acorn ADFS
# akai: Akai (S01, S20, S950), Korg, SC Prophet 3000
# casio: Casio (FZ-1)
# dec: DEC (RX33, RX50)
# ensoniq: Ensoniq (ASR, TS, etc)
# fluke: Fluke 9100
# gem: General Music (S2, S3)
# kaypro: Kaypro
# memotech: Memotech
# msx: MSX
# nascom: Nascom
# pc98: NEC PC-98
# pc-dos: PC DOS Format (geometry determined from Bios Parameter Block)
# tandy-coco: Tandy Color Computer (CoCo)
# ti99: TI-99/4A
# uknc: UKNC / DVK Soviet PDP-11
# unspecified: Common default geometries (including IBM PC)
host = unspecified

# Pins 2 & 34 output (drive->host) manual configuration
# auto: Auto-configure from interface= setting
# nc: Unused/No Connection [eg. if pin is an input (host->drive) on your host]
# low: Always 0 volts (0v)
# high: Always 5 volts (5v)
# rdy: Drive ready (Ready = 0v)
# nrdy: Logical complement of above
# dens: Density mode (High Density = 0v)
# ndens: Logical complement of above
# chg: Disk changed (Changed = 0v)
# nchg: Logical complement of above
# Values: auto, nc, low, high, rdy, nrdy, dens, ndens, chg, nchg
pin02 = auto
pin34 = auto

# Forcibly write-protect images, or respect the FAT read-only attribute?
# Values: yes | no
write-protect = no

# Filter glitches in the SIDE-select signal shorter than N microseconds
# Values: 0 <= N <= 255
side-select-glitch-filter = 0

# Rotational offset of data after a track change
# instant: No rotation during track change
# realtime: Emulate rotation of disk while track is changing
# Values: instant | realtime
track-change = instant

# Index pulses suppressed when RDATA and WDATA inactive?
# Values: yes | no
index-suppression = yes

# Milliseconds from head-step start to RDATA active.
# Values: 0 <= N <= 255
head-settle-ms = 12

# Milliseconds delay from motor-on to drive ready.
# On a standard unmodified Gotek the motor signal is not connected and a
# non-default value here will have no effect. Most systems and software do
# not care about correct motor behaviour, and default (ignore) works fine.
# Values: ignore | 0 <= N <= 1000
motor-delay = ignore

# What causes the disk-change (chg) signal to reset?
# step: Step command received
# pa14: CHGRST (pin 1 on old Sony drives), connected to PA14 (JTCK/SWCLK)
chgrst = step

##
## STARTUP / INITIALISATION

# Disk image loaded or ejected at startup?
# Values: yes | no
ejected-on-startup = no

# Which image (or folder) is selected at startup?
# last: Last-selected item at power-off (recorded in IMAGE_A.CFG)
# static: Static path specified in IMAGE_A.CFG
# init: First item in root folder
# Values: last | static | init
image-on-startup = last

# Time in milliseconds to attempt to probe attached display.
# You may set this to 0 if you have a 2-digit LED display attached.
# Values: 0 <= N <= 65535
display-probe-ms = 3000

##
## IMAGE NAVIGATION

# Auto-select the current file after N seconds
# N=0: disable auto-select
# Values: 0 <= N <= 255
autoselect-file-secs = 2

# Auto-select the current folder after N seconds
# N=0: disable auto-select
# Values: 0 <= N <= 255
autoselect-folder-secs = 2

# Sorting of folder entries in native navigation mode.
# always: Always sort folder entries. Large folders may be truncated.
# never: Never sort folder entries, instead presenting them in FAT order.
# small: Only sort folders which are small enough to sort in full.
# Values: always | never | small
folder-sort = always

# Priority of files vs subfolders when sorting folder entries:
# folders: Folders listed before files
# files: Files listed before folders
# none: Files and folders are not differentiated
# Values: folders | files | none
sort-priority = folders

# Navigation mode for selecting images/slots
# native:  Navigate through all valid images/dirs
# indexed: Navigate through DSKA0000, DSKA0001, ...
# default: native unless overridden by HxC-compat-mode config
nav-mode = default

# When navigating slots or folder, loop at min/max?
# Values: yes | no
nav-loop = yes

# Actions of first two buttons.
#              B1     | B2     | Both
# zero:        Prev   | Next   | Slot 0
# eject:       Prev   | Next   | Eject/Insert
# rotary:      Up-dir | Select/Eject/Insert | -
# rotary-fast: Prev   | Next   | Up-dir [Prev/Next are accelerated]
# reverse:     Reverse sense of B1 and B2
# Multiple values can be separated by commas, eg twobutton-action=eject,reverse
twobutton-action = zero

# Input sensor type at the rotary-encoder inputs (pins PC10 and PC11):
#  [full | half | quarter]:
#    Rotary encoder, identified by fraction of a Gray-code cycle performed
#    per detent/click. If default value ('full') requires multiple
#    clicks/detents to move position then change to 'half' (if 2 clicks
#    per move) or 'quarter' (if 4 clicks).
#  [trackball]:
#    Blackberry-style trackball (eg. using Hall-effect sensors).
#  [buttons]:
#    Push-to-ground Prev/Next buttons.
#  [reverse]:
#    If the input is working in reverse, use this option to swap directions.
# Multiple values can be separated by commas, eg rotary=quarter,reverse
# Values: none | quarter | half | default:full | trackball | buttons | reverse
rotary = trackball

# Prefix for image names in indexed navigation mode. String can be empty ("").
indexed-prefix = "DSKA"

##
## DISPLAY

# Display Type: <type>[-rotate][-narrow]
# auto: Auto-detect (7-seg LED, LCD, OLED)
# lcd-CCxRR: CCxRR backlit LCD with I2C backpack (16<=CC<=40, 02<=RR<=04)
# oled-128xNN: 128xNN I2C OLED (NN = 32 | 64)
#  -rotate:     OLED view is rotated 180 degrees
#  -narrow[er]: OLED view is restricted to Gotek display cutout
#               (-narrow: 18 chars; -narrower: 16 chars)
#  -ztech:      ZHONGJY_TECH 2.23" 128x32 SSD1305 OLED display
# Values: auto | lcd-CCxRR | oled-128xNN[-rotate][-narrow[er]][-ztech]
display-type = oled-128x64

# OLED Font. Narrow and wide options.
# Narrower 6x13 font permits:
#  - More characters per row
#  - Use of Gotek display cutout (eg. "display-type=oled-128x32-narrow")
# Values: 6x13 | 8x16
oled-font = 6x13

# OLED contrast/brightness.
# Values: 0 <= N <= 255
oled-contrast = 143

# Text height and arrangement on LCD/OLED
# 'default', or a comma-separated list (one entry per LCD/OLED row, top down).
# Each list item is a digit plus optional height specifier: <content-row>[d]
#  content-row: '0-3' = specified content row, '7' = blank
#    0: Current image name
#    1: Status
#    2: Image/Volume info
#    3: Current subfolder name
#  height specifier: 'd' = double height (32px, OLED only; ignored for LCD)
# 'default' depends on display, eg.: oled-128x32='0,1' ; oled-128x64='3,0d,1'
# Values: [0-7][d] | default
display-order = default

# Turn an LCD or OLED display off after N seconds of inactivity
# N=0: always off; N=255: always on
# Values: 0 <= N <= 255
display-off-secs = 60

# Automatically switch LCD/OLED display on when there is drive activity?
# Values: yes | no
display-on-activity = yes

# LCD/OLED long filename scroll rate in milliseconds per update
# Values: 100 <= N <= 65535
display-scroll-rate = 200

# LCD/OLED pause time at start/end of scroll, in milliseconds
# Zero means endless scroll
# Values: 0 <= N <= 65535
display-scroll-pause = 2000

# LCD/OLED long filename scroll rate during navigation (ms per update)
# Values: 0 <= N <= 65535
nav-scroll-rate = 80

# LCD/OLED long filename pause before scroll, during navigation (milliseconds)
# Values: 0 <= N <= 65535
nav-scroll-pause = 300

##
## MISCELLANEOUS

# Speaker volume for head STEP
# Values: 0 <= N <= 20
step-volume = 10

# Report the specified version number to host software
# Values: <quoted-string> ("" means report real version)
# eg. da-report-version = "v3.0.0.0"
da-report-version = ""

# Automatically extend certain types of truncated image file (SSD,DSD,TRD)?
# Values: yes | no
extend-image = yes

If i change display-order to '3,0d,1' i see only the yellow first row and not the others.

With the same display and your cfg it doesn't work at all!

The other display i got is the same as yours (back of it is exacty the same) but doesn't work at all with my cfg, maybe dead by transportation. Haven't tried your cfg with this yet.

[solarmon]

@katarakt

My Yellow/Blue 0.96" 128x64 screen came in.

It's not quite the same as yours:



But it is working as expected, with three lines:



Using the following settings:

display-type = oled-128x64

display-order = default

The only differrence (apart from a differrent board) is that your one has an SCK pin instead of SCL, but I think this is the same thing, as otherwise you would not be getting anything on your screen.

Where did you get your OLED screen from?

[katarakt]

SCK and SCL should be the same thing i think, btw. on the FF github pictures it says SCK...so 100% correct anyway.

I've ordered it from WAVGAT store:

0,96 zoll IIC Serien Weiß OLED Display Modul 128X64 I2C SSD1306 12864 LCD Screen Bord GND VCC SCL SDA 0,96 "für Arduino Schwarz

Where have you ordered yours? So i'll give it a try i think.


I have a question, the middle row is bigger than the others on your display. Can you change the config to get all 3 rows the same high? Or the upper row bigger and the lower 2 rows smaller but same high?

[solarmon]

Originally Posted by katarakt

SCK and SCL should be the same thing i think, btw. on the FF github pictures it says SCK...so 100% correct anyway.

I've ordered it from WAVGAT store:

0,96 zoll IIC Serien Weiß OLED Display Modul 128X64 I2C SSD1306 12864 LCD Screen Bord GND VCC SCL SDA 0,96 "für Arduino Schwarz

Where have you ordered yours? So i'll give it a try i think.


I have a question, the middle row is bigger than the others on your display. Can you change the config to get all 3 rows the same high? Or the upper row bigger and the lower 2 rows smaller but same high?

Where are you seeing 'SCK' in the FlashFloppy Github pages?

This one you linked to does not seem to be the one you showed previously - the back of it is different.

I one I got is from a UK seller which I just chose for quick delivery for me:

https://www.ebay.co.uk/itm/128X64-0-...72.m2749.l2649

But any 4-pin I2C OLED display, that is single or dual colour, should work - so I'm not sure why yours is not working.

[katarakt]

Sorry for late reply.

That from wavgat store doesn't work at all, and my other two ones (same components on the backside) only showing what i described before. In total i have 3 of these 3 row displays now. Hm, can't remember where i've seen SCK, but should be the same.

The one you've linked doesn't ship to my country.

I give up and sadly have to use the smaller 2 row display. There is nothing wrong with my setting, it's either not compatible OLED due to different layout/components/ControllerIC or something not good with FFfirmware.

Maybe i'll use the new addon with onscreen display.

[XsamX1987]

Ok So my set up a littil rough looking and i havent hooked it up yet to my Amiga but here it is

[solarmon]

Originally Posted by XsamX1987

Ok So my set up a littil rough looking and i havent hooked it up yet to my Amiga but here it is

Very nice!

The 'scanlines' effect is because the it is a 128x64 row displayed but the FF display settings is set to 128x32. You need to set the display to 128x64 in the FF.cfg file:

display-type = oled-128x64

[XsamX1987]

Originally Posted by solarmon

Very nice!

The 'scanlines' effect is because the it is a 128x64 row displayed but the FF display settings is set to 128x32. You need to set the display to 128x64 in the FF.cfg file:

display-type = oled-128x64

Awsome to be honest didn't even think of that or really bother me at the moment I'm just like wow I love it I will have a tinker with it later on.