• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1573 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux: Beaglebone Black display fails

Manali Patil
Prodigy 240 points

Tool/software: Linux

Hi,

LCD 7" Display connected to  Beagle bone black is not coming up on boot up and I have observed below errors in boot up log,

[   12.518022] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 187, base_baud = 3000000) is a 8250
[   12.519422] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 188, base_baud = 3000000) is a 8250
[   12.520309] pinctrl-single 44e10800.pinmux: pin 44e10958.0 already requested by 48022000.serial; cannot claim for 481a8000.serial
[   12.520318] pinctrl-single 44e10800.pinmux: pin-86 (481a8000.serial) status -22
[   12.520327] pinctrl-single 44e10800.pinmux: could not request pin 86 (44e10958.0) from group pinmux_bb_i2c1_pins  on device pinctrl-single
[   12.520333] omap8250 481a8000.serial: Error applying setting, reverse things back
[   12.520724] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 189, base_baud = 3000000) is a 8250
[   12.521492] pinctrl-single 44e10800.pinmux: pin 44e10958.0 already requested by 48022000.serial; cannot claim for 4802a000.i2c
[   12.521500] pinctrl-single 44e10800.pinmux: pin-86 (4802a000.i2c) status -22
[   12.521507] pinctrl-single 44e10800.pinmux: could not request pin 86 (44e10958.0) from group pinmux_bb_i2c1_pins  on device pinctrl-single
[   12.521513] omap_i2c 4802a000.i2c: Error applying setting, reverse things back
[   12.523440] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 100 kHz

I have below settings in uEnv.txt file

uname_r=4.4.27-bone-rt-r14
cmdline=coherent_pool=1M quiet
                                  cmdline=cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI, BB-BONELT-HDMIN, BB-BONE-HDMI bone_capemgr.enable_partno=BB-UART1,BB-AAIM-LCD7:00A1,BB-UART4,BB-UART2,BB-I2C1

Kindly share your views/ suggestions.

  • 0
    TI__Guru**** 170625 points

    Hi Manali,

    Manali Patil said:
    [   12.521507] pinctrl-single 44e10800.pinmux: could not request pin 86 (44e10958.0) from group pinmux_bb_i2c1_pins  on device pinctrl-single
    [   12.521513] omap_i2c 4802a000.i2c: Error applying setting, reverse things back

    Seems that you have some pinmux conflict issue. Revise your pinmux settings.

    Manali Patil said:
    uname_r=4.4.27-bone-rt-r14

    TI e2e forum support only AM335x TI PSDK (link below). Regarding another Linux distribution, you can check in the beagle community forums.

    software-dl.ti.com/.../index_FDS.html

  • 0 in reply to Pavel Botev
    Prodigy 240 points
    Thank you !

    I am not getting the same error every time. it is different always. As I have dtb overlays which i have compiled and loading in kernel.
    So Where to check this pinmux configuration and how can i resolve this?
  • 0 in reply to Manali Patil
    TI__Guru**** 170625 points

    Manali Patil said:
    So Where to check this pinmux configuration and how can i resolve this?

    If you switch to AM335x TI PSDK, I will be able to help. Please have a try and report if you have the same issue there.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Thank you Pavel!

    Now I have released one version of current build to our customer and in the field they are facing this problem. So this is very critical time. So I won't be able to switch to  AM335x TI PSDK. So could you please guide me on the current senior without switching to AM335x TI PSDK. It would be grateful if we could resolve this on current build repository.

    I am using dtb overlays which have been loaded using kernel. Is it because of Overlays having conflicts with the kernel pinmux configuration?

  • 0 in reply to Manali Patil
    TI__Guru**** 170625 points

    Manali,

    You can use the pinmux tool for checking regarding pin muxing conflicts:

  • 0
    TI__Guru**** 170625 points

    Manali Patil said:
    [   12.521492] pinctrl-single 44e10800.pinmux: pin 44e10958.0 already requested by 48022000.serial; cannot claim for 4802a000.i2c
    [   12.521500] pinctrl-single 44e10800.pinmux: pin-86 (4802a000.i2c) status -22
    [   12.521507] pinctrl-single 44e10800.pinmux: could not request pin 86 (44e10958.0) from group pinmux_bb_i2c1_pins  on device pinctrl-single
    [   12.521513] omap_i2c 4802a000.i2c: Error applying setting, reverse things back
    [   12.523440] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 100 kHz

    From this log, it seems that pin SPI0_D1 can NOT be configured in i2c mode (i2c1_sda) (muxmode 2), thus kernel can not configure the display through the I2C1 interface.