Actions
Forum Thread Details
  • State Verified Answer
  • Replies 11 replies
  • Subscribers 57 subscribers
  • Views 1175 views
  • Users 0 members are here
Related

BB View + BeagleBone Board

rattustrattus

Hi,

 

I am having a little trouble with a BB View 7 inch lcd panel, I followed the instructions and have a setup as per what should work. But I am not seeing the cape listed, do I have a DOA bit of hardware?

 

See below console extract which also confirms I a running "their" kernel :-

 

 

[    0.301532] bone-capemgr bone_capemgr.7: slot #0: No cape found

[    0.350356] bone-capemgr bone_capemgr.7: slot #1: No cape found

[    0.406998] bone-capemgr bone_capemgr.7: slot #2: No cape found

[    0.479261] bone-capemgr bone_capemgr.7: slot #3: No cape found 

[    0.502987] omap_hsmmc mmc.3: of_parse_phandle_with_args of 'reset' failed 

[    0.540364] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.6 

[    0.552121] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.6) status -22 

[    0.559431] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single 

systemd-fsck[77]: Angstrom: clean, 51645/218160 files, 336623/872448 blocks 

 

.---O---.

|       |                  .-.           o

|   |   |-----.-----.-----.| |   .----..-----.-----.

|       |     | __ |  ---'| '--.|  .-'| |     |

|   |   | |  |     |--- ||  --'|  | |  '  | | | |

'---'---'--'--'--. |-----''----''--'  '-----'-'-'-'

-'  | 

                '---' 

 

The Angstrom Distribution beaglebone ttyO0 

 

Angstrom v2012.12 - Kernel 3.8.13-00723-gdabc3b0 

 

beaglebone login:

 

As you can see there are no capes? Is it me or the board?


thanks in advance,


Kevin.


p.s. I noticed there was no cape slot/address selector switch on the bottom of this board which I thought was odd at the time, is this true for everyones boards?

  • 0

    Are you using a BeagleBone Black, or the original BeagleBone White ?

     

    Get to a root shell, type the following two commands and paste the output here

     

    cat /sys/devices/bone_capemgr.*/slots

     

    cat /proc/cmdline

     

    You might also want to read through the thread at http://www.element14.com/community/message/102166/l/how-to-bb-view-on-latest-debian while that's not directly applicable to angstrom it has a lot of things to look for when debugging.

     

    It's correct that there's no slot/address selector, the BB-View doesn't have an eeprom on it, so there's no point.  However, due to that there are some extra steps needed to get it working as the cape won't be detected automatically.

  • 0 in reply to Former Member

    Thanks, it an original white Rev A6a, wanted a black but everyone seems to be out of stock image

     

    I tried looking at the debian stuff earlier tried modifying the uEnv.txt to match the one suggested but still nothing different.

     

    The output you asked about was :-

    root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots

    0: 54:PF---

    1: 55:PF---

    2: 56:PF---

    3: 57:PF---

    root@beaglebone:~# cat /proc/cmdline

    console=ttyO0,115200n8 run_hardware_tests quiet root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait

    root@beaglebone:~#

     

    Thanks for the info about the lack of a slot/address selector ... one less thing to worry about. I did download the stuff from the element 14 site, put the dtb files in /boot with the new uImage and extracted the modules so they went into the correct place but still nothing? Any suggestions would be helpful?

     

    thanks in advance,

     

    Kev.

     

    p.s. should I really be using the 

     

    BB-View Pre-Compiled TI-SDK Image.zip

     

     

       image instead of the download of just the kernel and other bits?

  • 0 in reply to rattustrattus

    Ok, things are obviously slightly different on the original BBW, most of the stuff you'll have been reading is probably aimed at the BBB

     

    can you try just changing uEnv.txt to have

    optargs=capemgr.enable_partno=BB-VIEW-LCD7-01

    and then reboot.  Hopefully you should see capemgr.enable_partno=BB-VIEW-LCD7-01 in the output of cat /proc/cmdline

     

    Or you can probably do

    echo BB-VIEW-LCD7-01 > /sys/devices/bone_capemgr.<n>/slots

    but change the <n> to the correct number, it's usually a 7 or an 8 on the BBB but is assigned dynamically, so could be anything on the BBW.

     

    Either way, the goal is to have the BB-VIEW-LCD7-01 line turn up in the output of cat /sys/devices/bone_capemgr.*/slots


    If you can get that to happen then the display should work. If you still have problems, you can type dmesg | less at the console and look for lines with capemgr, if the overlay doesn't load then you should find some message telling you why.

     

    I used the TI SDK image on a BBB just to check that the display worked. It's essentially just a demo, what you see on the display in the photos in the manual and on the box is there along with a few other things, but it's not terribly useful itself other than to prove everything works.

  • 0 in reply to Former Member

    Tried the TI image screen light up red light on the cape flashed imagescreen gave a weird pattern with a line across the middle and slowly went dark but the back light is on any suggestions?

  • 0 in reply to rattustrattus

    Ignore that I am an idiot ... forgot the size line .... so shows display/hardware fine me stupid .... need to fix the last part probably end up putting debian on it ....

     

    Thanks for your help

  • 0 in reply to rattustrattus

    You're welcome. Main thing is that you now know the display works, so you can take some time to get it all setup the way you want with an OS that suits you.

  • 0 in reply to Former Member

    image

     

    FYI got it working ... at last, I stole the kernel and initial boot from the TI demo image, and stuck a debian rootfs on that, I don't get the cape manager as a result, but with the addition of having to build fbdev and evdev input device and custom X11 config files, I now have stellarium running image. So it can be done.

     

    So anyone trying it with a White Beaglebone it is possible,

  • 0 in reply to Former Member

    Hi,
    I do as you write here and I am able to initially lunch my LCD. 

    echo BB-BONE-LCD7-01:00A4 > /sys/devices/bone_capemgr.7/slots

     

    It shows me Angstrom login screen. I can log in (I set autologin). But can't startx. From this site I learned to use "fbdev". I modify my xorg.conf, 10-evdev.conf etc. But still no success. I mange to see white screen with mouse on the middle. And nothing more. Author of this topic manage to merge TI with Angstrom Image, but unfortunately for me I don't know how to do it. I am still a beginner with embedded, but I hope with time it will change.
    If I install TI-SDK image, LCD works well, but I want to lunch there normal system, not SDK.

     

    Here is my error: (I try to search internet for hints with twm and xclock, but no success ;/

    root@beaglebone:/etc/X11# startx
hostname: beaglebone: Unknown host
xauth:  file /home/root/.serverauth.577 does not exist


X.Org X Server 1.11.2
Release Date: 2011-11-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.11.0 x86_64 
Current Operating System: Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l
Kernel command line: console=ttyO0,115200n8 quiet root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait
Build Date: 09 September 2013  01:21:29PM
 
Current version of pixman: 0.27.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Sun Oct  5 19:05:52 2014
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
(EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
/usr/lib/X11/xinit/xinitrc: line 76: twm: command not found
/usr/lib/X11/xinit/xinitrc: line 77: xclock: command not found
Warning: locale not supported by Xlib, locale set to C
Warning: X locale modifiers not supported, using default
Warning: locale not supported by Xlib, locale set to C
Warning: locale not supported by Xlib, locale set to C
Warning: X locale modifiers not supported, using default
Warning: X locale modifiers not supported, using default
xterm: Failed to open input method
xterm: Failed to open input method
xterm: Failed to open input method

  • 0 in reply to pawel_krzy

    I manage to push it forward a bit. Now there are no errors. But all I get is a white screen with working shell ;/ My mouse is working and my keyboard works too. So maybe I am wrong and all i should get from this Angstrom is only this white screen with shells? Here is my screen:

    image

     

     

     

     

    And my logs:

     

     

    root@beaglebone:~# startx
hostname: beaglebone: Unknown host
xauth:  file /home/root/.serverauth.482 does not exist


X.Org X Server 1.11.2
Release Date: 2011-11-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.9.6 x86_64 
Current Operating System: Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l
Kernel command line: console=ttyO0,115200n8 quiet root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait
Build Date: 03 July 2013  07:26:12PM

Current version of pixman: 0.27.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct  7 11:54:09 2014
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
/usr/lib/X11/xinit/xinitrc: line 76: twm: command not found
/usr/lib/X11/xinit/xinitrc: line 77: xclock: command not found
Warning: locale not supported by Xlib, locale set to C
Warning: X locale modifiers not supported, using default
Warning: locale not supported by Xlib, locale set to C
Warning: X locale modifiers not supported, using default
Warning: locale not supported by Xlib, locale set to C
Warning: X locale modifiers not supported, using default
xterm: Failed to open input method
xterm: Failed to open input method
xterm: Failed to open input method

  • 0 in reply to pawel_krzy

    Pawel,

     

    looks like you need to run a window manager, I haven't bothered for what I am doing because I wanted the application to be the only one running. So just start the X server then run the app on it.

     

    If you look at your log its trying to run twm which is an old window manager if you install it you should then get your windows with frames.

     

    Kevin