Open Apnet66 opened 3 months ago
Could you check if any of the GPIO pins used for the display is overlapping with pins defined here https://github.com/kwahoo2/Mortar/blob/master/MotorWorker.cpp
Try changing the driver preset before starting Mortar, editing ~./config/kwahoo/Mortar.conf
eg.:
[Common]
driver=DRV8825 Hat
Here are the pins that the display uses ср, ., 18:21 kwahoo2 @.***>:
Could you check if any of the GPIO pins used for the display is overlapping with pins defined here https://github.com/kwahoo2/Mortar/blob/master/MotorWorker.cpp
Try changing the driver preset before starting Mortar, editing ~./config/kwahoo/Mortar.conf eg.:
[Common] driver=DRV8825 Hat
— Reply to this email directly, view it on GitHub https://github.com/kwahoo2/Mortar/issues/5#issuecomment-2112844013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM5MLRXUEK5N6P33RJIQQP3ZCN4QFAVCNFSM6AAAAABHXWHULCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJSHA2DIMBRGM . You are receiving this because you authored the thread.Message ID: @.***>
Isn't this physical pin numbering scheme? If it is, then only physical pin 18 is an issue if DRV 8825 Waveshare Hat is selected:
dirPinAzi = std::make_unique<pigpio_wcpp::DigitalOutput>(24); //GPIO 24, physical pin 18
I connect a 3.2"RPI display (320240 xpt2046) via gpio, everything is fine with it. I connect a 3.5"RPI (480320 xpt2046) display via gpio, after launching Mortar, the image disappears, blinks, moves, I corrected the screen frequency, it does not help. without starting Mortar, everything works. Help me to understand.