Scott: This kind of a problem had troubled me many months back as well, but I moved on to solve it another way using a Raspberry Pi based LCD. While that may not be helping you directly just now, you might want to consider writing to the TI-e2e community, where engineers are paid to support issues like this with the BBB hardware and firmware. Please take this there. I am not ruling out other kind of help you might find here.
My summary assessment on this display issue has been that the vast majority of people use BBB in embedded mode without displays. Those who do use a display (the small minority) know how to use a simple i2c based interface or the like, and get by. On Wed, Aug 28, 2019 at 12:47 PM Mecha Lec <[email protected]> wrote: > I have flagged this under "Beagle Bone Black " but maybe its more of a > CAPE issue. > > I have a BBB Revision C, with 4DSystems LCD Cape. > > I am hoping someone on this forum could possibly help with a software > related issue. > > I am running 2net 4.1 Kernal ,http://www.2net.co.uk/android4beagle.html > > The screen shows "Android" and then this fades out. > > Looking at serial I have this error: > > [ 3.353484] pinctrl-single 44e10800.pinmux: pin 44e108a0.0 already > requested by panel; cannot claim for 0-0070 > [ 3.363651] pinctrl-single 44e10800.pinmux: pin-40 (0-0070) status -22 > [ 3.370239] pinctrl-single 44e10800.pinmux: could not request pin 40 > (44e108a0.0) from group nxp_hdmi_bonelt_pins on device pinctrl-single > > I think this might be why it doesn't continue with the Kernal but I could > be wrong. > > Referring to all available forum posts regarding this LCD I have tried > many different options in uEnv.txt to disable HDMI, disable universal cape > and alike but nothing seems to work. > I am not sure what command options are actually relevant to this > particular build. > > I have also read that the boot int eh EMMC can also affect the overlays > which are being loaded by the image in the SD card. I have ensured I have > loaded one of the latest flasher images from official beagle bone site. > Running just this flasher image, the screen does display correctly so I > know it is not a hardware related issue. > > I have also double checked the overlay that is being used and all the pins > are correct and match the schematic of the display. > > I am a newbie to Beable Bone Black and Linux so this is incredibly > difficult and have spent weeks now trying to overcome this hurdle. > So any help would be greatly appreciated. > > I have attached the serial outputs from the problamatic SD image and also > for my base EMMC. > > Hoping someone could provide some info to push me in the right direction. > > -- > 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/6f716178-d227-4c24-a3f3-e54ab0fb0b92%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/6f716178-d227-4c24-a3f3-e54ab0fb0b92%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAHW0bczDipq44jMXA3BkNRuKqmG-S5c-HzA5RKhTChgFh5CKRA%40mail.gmail.com.
