From the december 2016 versions, the graphics screens are scalable.
I have some questions around.
1/ Is anyone using a different screen size than H320-V240 ?
I am interested in how the problem is solved with the splash-screens.
2/ Is anyone using a display with an ID EEPROM
it has a 40P header instead of a 26P.
As far as I could ascertain, the OS expected just 1 HAT
the HIFIBberry-DAC’s are HAT’s with an ID EEPROM.
If that’s true, then there is much chance of a conflict on the I²C(0) bus!
Does anyone have more information on this ?
3/ HDMI-PITFT-HDMI mechanism
at boot time the HDMI screen is used.
Just before or at start of zynthian the screen is switched to PITFT
When selecting powerdown or reboot the opposite happens.
Where are these changeovers programmed ?
Currently the splash screens are implemented using a direct “framebuffer dump”. The most simple solution would be having different splash-screen versions for the typical screen sizes.
The perfect solution would be to have a configuration script that down-scale the splash-screens from high resolution versions and use a display utility (like “fbi”) to generate the frambuffer dumps.
As much as i know, almost all “hat-screens” use SPI bus and shouldn’t have any conflict with I2C bus.
I have no experience with displays using an ID EEPROM, but it should be considered when configuring the address for the MCP23xxx.
PiTFT’s framebuffer (/dev/fb1) is used for dumping the splash screens and as X11 display. It’s specified when starting X11 in:
/etc/systemd/systemd/system/zynthian.service
Display configuration should be improved and simplified. Added to the TODO list in the Wiki
1/ to be able to test a different format , that should be solved first !
splas-screens can have better a format of 240 x 240 (fit all)
and then with fbi be placed in the center of the screen.
Some choose Portrait- above Landscape format on larger displays !
2/ The MCP’s use I²C(1) headerpins 3-5 and not I²C(0) headerpins 27-28
I²C(0) is only for the ID-EEPROM and the Raspberry Pi 7" Touch Screen Display https://github.com/raspberrypi/hats
3/ What needs to be changed to not go to the PITFT?
I want to do a test with the Raspberry Pi 7" Touch Screen Display
who uses the framebuffer(0) same as the HDMI screen.
After changing this files you won’t be allowed to update from the admin menu. Sorry ;-(
I know. This is far from optimal. I will move this to a unique configuration file ASAP. It’s in the TODO list.
Yes, you can use HDMI display with Zynthian. It needs a few tweeks of the configuration. The best thing is that the GUI is now scalable, so you can match resolution of your monitor.
Just adjust these value to match your screen resolution & the GUI will scale itself.
I’m building a Zynthian with a 800 x 480 HDMI display. This is a non standard resolution so I needed to add some lines to config.txt to force this. I followed the instructions on the manufacturer’s website.
My 5 cents
If you put to “None” the width and height variables in the config file, the UI will autodetect the screen size.
This wont work in a “fresh” Gorgona, but it should work after updating.
Trying with the raspberry pi standard 7" touchscreen .
Set the fb0 as per file details set the width and height to 800 * 480
I get the prompt start up I see a distorted zynthian logo then just a white cursor line top/left.
No response to qwerty keyboard
No knobs connected, with & without AudioInjector.
Sadly I can’t see the ip address so I can’t get to it over ssh . . .
Any thoughts?
following suggestions from here also
