On Fri, 17 Jul 2020 14:44:25 -0700 (PDT), in gmane.comp.hardware.beagleboard.user John Dammeyer <[email protected]> wrote:
>But I'd like to access the the display in much the same way as if I >connected say an SPI based LCD display like >https://www.sparkfun.com/products/12085 which is the 4D Cape or even the >https://www.sparkfun.com/products/15152#description-tab . And there are >others. Generally SPI but the Beagle Cape is mapped to the Beagle pins. > Based upon the documentation I looked at (apologies for the Google tracking overhead) https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwjxrImVttXqAhVCIKwKHcm2Bu4QFjABegQIAhAB&url=https%3A%2F%2F4dsystems.com.au%2Fmwdownloads%2Fdownload%2Flink%2Fid%2F284%2F&usg=AOvVaw10MtWIPYfhFh1lMI_qrL7f this display /requires/ the LCD pins on the board -- which means it is a parallel LCD driver using the same graphics system as the HDMI framer. That document also implies it uses the same drivers as the CircuitCo LCD4. The biggest problem is likely to be that the Wheezy time frame was still relying upon the kernel to load the device tree during start-up. That scheme was discontinued sometime in the Jessie time frame, and it is now u-boot that loads device trees. So, presuming the driver is still in the archive, you likely need to have a DT overlay for the display AND specify that overlay in /boot/uEnv.txt so that it gets loaded before the kernel starts up. -- Dennis L Bieber -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/g1d4hftc8tb1a7ai8aed7h5b9d8cpiooqu%404ax.com.
