[How-to] BB-View on latest Debian

You mean on the paper 'Quick Start Guide' where it says "Connect the BB View: Connect the BB View to the BeagleBone or Beaglebone Black using the 46 pin dual-row connectors (J1 and J2)" ?

J1 & J2 are the two 46pin headers on the cape

If you've disconnected something else then yes you will likely have a problem.  What problem is hard to tell, maybe the backlight, maybe the touchscreen..  How many connections in the one you removed ?  If it's four then it could be the touchscreen.

No.  Not on the header.  On the 7" LCD.  The ribbon cables for both J1 and J2 are connected via the clamps, to each connector.  When you take it out of the box, the J2 is wrapped around and foam/taped to the underside of the LCD, just on the edge.  I thought the J1 was the same, so, since I'm using J2 and the larger ribbon cable, I pulled (lightly) on the smaller ribbon cable, and it came loose the same way.  Only I double checked with a flashlight, and that smaller ribbon cable does actually have a connector on the underside of the board.  This cable doesn't need to be looped around and remain in the J1 connector does it?  For some sort of continuity?

                  Left connector is J2.  It goes to my BBB

                          |                             Right connector is J1 (not connected)

                          |                                  | 

                         \/                                 \/

                                                /\

                                                 |

Underside of 7" LCD display - this is a connector, not just a foam/tape!

The ribbon cable for J1 was "plugged in", and wrapped around the board

and connected to J1

Ah.. I have the 4.3" one. Nothing like that on mine.  Someone with a 7" one might be able to help.

Back of the 4.3" one looks like this

the white cable to the right goes to the cape.  I take it this is totally different to the back of the 7" one ?

Here's the board.  So I'm on a wild goose chase I think.  The J1 connected ribbon cable should probably have been taken out.

I'm reflashing my Debian ARM image.  I'm thinking I corrupted the image when I didn't wait until the 4 lights came on.  It seemed like

a long time (>45 min), and the 4 lights never came on.  But when I restarted on my HDMI, I saw the penguin, so at least part of

the image was flashed.  It never let me logon though, and the screen went blank, so the disable HDMI is working, but it's not starting up the LCD. I need to be

able to SSH into the BBB, or otherwise start over I guess.

> 45mins was common with the Angstrom images, but from what I've read it should be approx 15mins with debian.

if the HDMI disable has worked properly, then in theory you shouldn't see anything on the HDMI output as that driver won't load.  However as the LCD and HDMI framer share the same set of pins I suppose it's possible to have output on both if the timings work out and the monitor, by some miracle, supports the same timings.

To be sure you properly boot from the uSD to flash, be sure to remove power, hold the boot button, then apply power. The state of the button is only sampled at power-on, not reset, and the sampled state survives a reset, so you keep booting from uSD until you power cycle again.

OK.  New power supply.  I was using one that was older, though the specs were 5A, it seemed the lights were dimmer than using USB power.  This one is w/ the DC connector, and 3.5A 5VDC.  Lights seem brighter now.  Not getting anything on the display, not even a backlight.  Blue lights are blinking, Blue power light is on and bright.  On the cape, I noticed that the Green light is solid, but the red light (LED0) is off now.

Interesting.  I seem to remember that one of the LEDs on the cape was configured as heartbeat.  Perhaps that was the TI-SDK image then as looking at the overlay files I see:

gpio-leds-cape-lcd {

  compatible = "gpio-leds";

  pinctrl-names = "default";

  pinctrl-0 = <&bb_view_lcd_cape_led_pins>;

  bb_view_led0 {

    label = "bb-view:led0";

    gpios = <&gpio2 28 0>;

    linux,default-trigger = "none";

    default-state = "off";

  };

  bb_view_led1 {

    label = "bb-view:led1";

    gpios = <&gpio1 12 0>;

    linux,default-trigger = "none";

    default-state = "off";

  };

};

which implies they should both be off.

Are you able to ssh into the board, or to use a console cable?

If you are, you can look see if /sys/class/leds has bb-view:led1 & bb-view:led2 if those dirs exist, you can go into one of them and type "echo heartbeat > trigger" which should result in that led flashing a heartbeat pattern. Should that work the overlay would appear to be loaded ok.

Matthew Trippy wrote:

 

OK.  New power supply.  I was using one that was older, though the specs were 5A, it seemed the lights were dimmer than using USB power.  This one is w/ the DC connector, and 3.5A 5VDC.

As an aside, if your power supply is of the 'USB Charger' type, I'd refer you to the experiences of the Raspberry Pi people who found that the specs on the label on most of them simply can't be trusted...

A decent PSU is likely to be necessary with the LCD connected as you have and additional thing to power.

hello , everyone if someone interesting how to  fix colors for 3.8.13, to work without X  , here is the fix:

replace blue and red color offset values

compile new kernel and enjoy. (tested on 3.8.13-bone43_1)

/linux-dev/KERNEL/drivers/gpu/drm/drm_fb_helper.c
@@ -621,9 +621,9 @@
  var->transp.offset = 15;
  break;
  case 16:
- var->red.offset = 11;
+ var->blue.offset = 11;
  var->green.offset = 5;
- var->blue.offset = 0;
+ var->red.offset = 0;
  var->red.length = 5;
  var->green.length = 6;
  var->blue.length = 5;
@@ -631,9 +631,9 @@
  var->transp.offset = 0;
  break;
  case 24:
- var->red.offset = 16;
+ var->blue.offset = 16;
  var->green.offset = 8;
- var->blue.offset = 0;
+ var->red.offset = 0;
  var->red.length = 8;
  var->green.length = 8;
  var->blue.length = 8;
@@ -641,9 +641,9 @@
  var->transp.offset = 0;
  break;
  case 32:
- var->red.offset = 16;
+ var->blue.offset = 16;
  var->green.offset = 8;
- var->blue.offset = 0;
+ var->red.offset = 0;
  var->red.length = 8;
  var->green.length = 8;
  var->blue.length = 8;
@@ -888,9 +888,9 @@
  info->var.transp.length = 0;
  break;
  case 15:
- info->var.red.offset = 10;
+ info->var.blue.offset = 10;
  info->var.green.offset = 5;
- info->var.blue.offset = 0;
+ info->var.red.offset = 0;
  info->var.red.length = 5;
  info->var.green.length = 5;
  info->var.blue.length = 5;
@@ -898,18 +898,18 @@
  info->var.transp.length = 1;
  break;
  case 16:
- info->var.red.offset = 11;
+ info->var.blue.offset = 11;
  info->var.green.offset = 5;
- info->var.blue.offset = 0;
+ info->var.red.offset = 0;
  info->var.red.length = 5;
  info->var.green.length = 6;
  info->var.blue.length = 5;
  info->var.transp.offset = 0;
  break;
  case 24:
- info->var.red.offset = 16;
+ info->var.blue.offset = 16;
  info->var.green.offset = 8;
- info->var.blue.offset = 0;
+ info->var.red.offset = 0;
  info->var.red.length = 8;
  info->var.green.length = 8;
  info->var.blue.length = 8;@

@Vagif Thanks for posting this, I was just about to tackle that. I will test out your patch.

@ Matthew I will look at my 7 inch screen tomorrow and possibly send photos. I have it connected to a BBB, but have not tried to run it on a BBW.

Louis