Actions
Forum Thread Details
  • State Verified Answer
  • Replies 23 replies
  • Answers 6 answers
  • Subscribers 104 subscribers
  • Views 4350 views
  • Users 0 members are here
Related

Need help with E14  Beaglebone  4.3  LCD  Display

ninjatrent

I  am  having  trouble  flashing  the  Beaglebone  Black  Wireless eMMC  with  the  image  file  provided for  the  E14 Beaglebone  4.3  LCD  Display.

 

 

README - 4.3 LCD Display Cape for Beaglebone Black

 

4.3 LCD Display Cape for Beaglebone Board (White, Black, or Wireless)

 

 

I have  followed  the  instructions  for  flashing  the  eMMC but it's  not  working.

 

The  LED status lights  on the  BeagleBone  Black  W blink for  a  few seconds  and  go out. The  micro  SD status  light  remains  on constant after attempt  to  flash.

 

I can't figure  this  out. Beginning to  regret  the  purchase  of  this  Display.

The  first  one  arrived  damaged, had to  wait  for  a  replacement .

 

Now on day two  of  trying  to  get  this  display  to  work  with  the  Beaglebone  Black  W.

 

The image will boot from microSD and display will work.

 

I need to flash the eMMC with this image.

 

So far unsuccessful

 

It seems  the   image  is not   compatible  with  the  BBB Wireless.

 

When   checking   available   services  with   " connmanctl  technologies   ", ethernet   and gadget   were   listed   but   not   Bluetooth  and   wifi .image

 

This image   seems  to  be  only  compatible  with  the   Beaglebone  Black  and   not   the   Beaglebone  Black  Wireless .

 

Is there  any  one  who  might  be  able  to  assist  with  finding  a  solution  to  this  problem?

  • 0

    I don't have the wireless version, but I too had issues getting the image to transfer to the eMMC.  What I finally found was that the image that has the bbcape43 support has the eMMC disabled.

    So in /boot/uEnv.txt make sure that the folllowing two lines are NOT commented out:

     

    ##BeagleBone Black: HDMI (Audio/Video) disabled:

    dtb=am335x-boneblack-emmc-overlay.dtb

     

    and

     

    ##enable Generic eMMC Flasher:

    cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

     

    The first one enables the eMMC the second one enables the auto copy.  The blue LEDs should go into a night rider mode after 20 seconds or so to indicate thtat the copy is in progress.

    No button presses were required, just insert the SD card then power on.

     

    Aaron

     

    EDIT:

    These are the steps in order, just to be clear:

    1) boot using the SD image that has bbcape43 support.

    2) do the above edits (this will modify the SD card)

    3) reboot

  • 0 in reply to alager

    The main issue is that this bbcape43 image does not support the onboard wifi chip of the BBB Wireless.

     

     

    You are correct in enabling the eMMC flash process. This is helpful.

     

    The image is not compatible with the BBB Wireless. No matter what I do it only shows ethernet and usb host as available onboard resources. Wireless and Bluetooth work properly with the official Beagleboard Debian image with desktop and smaller iot image. I will have to try these images with the display attached.

     

    Hopefully the bbcape43 image will be updated in future for support of the Wireless and Bluetooth capabilities of the BBB Wireless.

     

    If the official Beagleboard image does not work then I might have to purchase a BBB for use with this display.

     

    Thanks for suggestion.

  • 0

    Hi Trent,

     

    Just by coincidence I was trying to put an image on the BBB Wireless a few nights ago. I don't have a display, so in my case I was using the images on the beagleboard website. Out of curiosity just now I checked and it appears to have a 'device tree' fragment file called BB-CAPE-DISP-CT4-00A0.dtbo, and this name appears in one of the comments here: README - 4.3 LCD Display Cape for Beaglebone Black   so I'm wondering if you might not need the specific image that is advertised for the cape, and instead the standard image could be used.

    To activate that device tree fragment, the command line (as root user) will be something like:

    echo BB-CAPE-DISP-CT4 > /sys/devices/platform/bone_capemgr/slots

    I don't know if anything more would be needed though. But it could be worth a try. You probably will also  need to use that command to disable the HDMI that Aaron mentions above too I guess.

    Also, incidentally, for the recent images, it would be worth just running from microSD and not eMMC, because they consume nearly the entire eMMC, not leaving much space for applications and updates. I found that out by accidentally filling up and the shell going crazy and having no bytes left to even delete files : )

    Also, things have changed for the past few releases, and now when you burn the image onto the SD card, it will no longer be readable on the PC, and it will seem as if the burn operation failed. But it will work.

    This really caught me out, because it isn't described anywhere that the image format has recently changed.

     

    Also some (nearly all) online documentation/blog posts about the device tree mention a path like /sys/devices/bone_capemgr/... but it looks like about a year ago, it changed, to /sys/devices/platform/bone_capemgr/.. which isn't great, since it means everyone's documentation is now incorrect : ( I wish they'd kept a link to the old path in the newer images : (

  • 0 in reply to shabaz

    Hey Shabaz,

     

    I have yet to try the official  images from beagleboard.

     

    Going to make some time to test this weekend.

     

    It would be awesome to get the iot image to work with the display. I prefer working with terminal over desktop.

     

    Thanks for the suggestion, with hope I will post good results soon.

     

    Thanks again

  • 0

    Beagle bone LCD cape has the device EEPROM which tells the Bone at boot to select the proper dTO files, is the EEProm intact? or may be the dot is not configured .

     

    GS GILL

  • 0 in reply to gsgill112

    Not sure. I recently moved and still unpacking things.

     

    Finally found the power supply so I will test the official Beagleboard image with the LCD Cape tonight.

     

    My apologies for the delay in response. Things have been hectic. I was foolish to put the power supply in a different box than the BBB W.

     

    Trent

  • 0

    The Debian 9.1 2017-08-31 4GB SD LXQT Desktop image available at Beagleboard is confirmed working properly with the Beaglebone LCD Display Cape.

     

    Wi-Fi and Bluetooth are detected.image

    image

    Chromium Desktop works.

     

    image

     

    Beaglebone Black Wireless with the LCD Cape.

     

    Everything seems to be in working order.

     

    I would really like to thank everyone for the help.

     

    Trent

  • 0

    I spoke too soon. Selecting Shutdown caused infinite loop of reboots.

    Same with " sudo shutdown -h now ".

    Holding Power button down is only way to power off now.

  • 0 in reply to ninjatrent

    Hi Trent,

     

    That may be an image issue.. I think I have the same problem on my  BeagleBone Blue  Black Wireless: (  (Just bare BB-Blue BBB-W, I don't have any cape attached).

     

    I'm getting used to super-rapidly pulling out the power after I think the board has powered down : )

    I wanted to investigate further to get to the bottom of it, but not had time so far : ( It's only a matter of time before I corrupt the microSD if I keep doing it this way : (

    I've not googled yet to see if others have this problem too, or if there was some resolution.

     

    It is awesome that you've got the display working though! I didn't realize it was capacitive touch enabled. Looks like a very useful product.

     

    (Edit: corrected, I meant to say BBB-W, not BB-Blue. I've not tested BB-Blue).