2022-03-07, 07:45 PM
Check the pypilot/hat/gpio.py for which gpio pins are used for buttons.
edit pypilot/hat/ugfx/ugfx.cpp to add a driver for your screen. I would not accept a patch that overwrites the existing driver, you would have to create a new driver which should be easy enough.
The i2c eeprom is not required. It is useful for me, as I produce a lot of hardware, and any changes can be recorded here, so the user does not have to edit the hat.conf file.
the linux framebuffer is a possible output source. If you can get the kernel module which supports your screen working you could avoid writing the driver in ugfx.cpp Sorry it's fbtft not tftfb.
If you have esp32, I believe your display is already supported. So the esp32 communicates over wifi to the raspberry pi and acts as a control interface.
edit pypilot/hat/ugfx/ugfx.cpp to add a driver for your screen. I would not accept a patch that overwrites the existing driver, you would have to create a new driver which should be easy enough.
The i2c eeprom is not required. It is useful for me, as I produce a lot of hardware, and any changes can be recorded here, so the user does not have to edit the hat.conf file.
the linux framebuffer is a possible output source. If you can get the kernel module which supports your screen working you could avoid writing the driver in ugfx.cpp Sorry it's fbtft not tftfb.
If you have esp32, I believe your display is already supported. So the esp32 communicates over wifi to the raspberry pi and acts as a control interface.