I failed earlier with BB VIEW and Debian 8.4 because I downloaded a patched 3.8.13 kernel from element14 (formerly Newark). element14 is the current vendor of the BB VIEW cape. The patches are offered at https://www.element14.com/community/docs/DOC-67958/l/element14-bb-view-lcd-cape-software-download-centre1 . Idiot me, I thought these were current.
I then attempted to follow instructions found on element14's bulletin boards to install the patches. Most or all of the destinations to which posters advised to install files found in http://downloads.element14.com/downloads/bb-view/BB%20VIEW%20Debian%20Image.zip?COM=BeagleBoneBlack were non-existent either in 7.9 (which pre-existed on BeagleBone Black) or in 8.4. Eventually I figured out where to install the files, however note that I most certainly ended up replacing something in 8.4 that was not meant to be replaced. It appears that the patches were targeted solely at 7.9. What I ended up with in 8.4 was, past a display calibration screen, a working BB VIEW with LCD4. However X would not start. I only had the login prompt. So, I could not understand whether the touch was working or not. I then found a statement from someone apparently at element14 who is responsible in some way for BB VIEW. The statement was "BB-VIEW is supported (with patches [...]) on kernel 3.8.13 [...] Support for BB View on 4.1.x kernel is not yet available." https://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone/blog/2015/05/20/beaglebone-black-with-the-bbview-and-the-new-beaglebone-debian-image#comment-68910 Therefore I reverted to 7.9. I just now followed Robert's instructions. I started with the 8.4 image downloaded from https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz . I modified two lines in /boot/uEnv.txt as above. I didn't edit /etc/X11/xorg.conf because it said DefaultDepth 24 and contained no instances of 16. I made absolutely no changes to anything else on the distribution, only the two lines in /boot/uEnv.txt . I then booted off the SD card. What I got was a half-screen-wide calibration screen, followed by a half-screen-wide desktop. That is, the image on the screen contained the entire Debian desktop, but was 240 px wide and 272 px tall, compressed along the x axis. The orientation was normal and the cursor tracked correctly. Also, the Ethernet-over-USB link did not start correctly. On my Windows host, I saw the host's IP address as 169.254.240.185 and not as 192.168.7.1 as in 7.9 (with BeagleBone itself being 192.168.7.2 in 7.9). I then rebooted the BeagleBone again, and this second time the Ethernet link came up as 192.168.7.1 / 192.168.7.2. But, I still have the half-size display image. A number of error messages are output to terminal before X starts, filling up most of the screen (this was also the case earlier with 8.4, but not with 7.9). On Fri, Jun 10, 2016 at 2:09 PM, William Hermans <yyrk...@gmail.com> wrote: > *Indeed I started the discussion with Jessie (8.4), but then found out my >> cape is not supported under 4.x kernel, so switched to Wheezy (7.9). I then >> tried expanding the SD card partition on the SD card with the 7.9 image >> according to the instructions, and got the SD card into the trouble >> described above.* > > > Which cape ? How is it not working ? As in what is happening. We may be > able to help there. > > On Fri, Jun 10, 2016 at 2:03 PM, Vladimir Gusiatnikov < > tundra1des...@gmail.com> wrote: > >> Indeed I started the discussion with Jessie (8.4), but then found out my >> cape is not supported under 4.x kernel, so switched to Wheezy (7.9). I then >> tried expanding the SD card partition on the SD card with the 7.9 image >> according to the instructions, and got the SD card into the trouble >> described above. >> >> The FAT32 partition appears to be part of the 7.9 image. >> >> On Friday, June 10, 2016 at 12:26:43 PM UTC-7, William Hermans wrote: >>> >>> > So, why do you state "Robert's Debian images have not used a two >>>> partition >>>> > layout in quite some times now"? Please explain. There were two >>>> partitions >>>> > on the SD card that I flashed with the 7.9 image above. The smaller >>>> > partition was the FAT32 one that shows up as a drive in Windows if I >>>> connect >>>> > the Beaglebone to a Windows host with a USB cable. This smaller >>>> partition >>>> > has mostly getting-started documents. >>>> >>>> On newer image's we use an *.img file instead of a hard-coded fat32 >>>> partition... >>>> >>> >>> I'm adding on to what Robert has already said. It's been a long time >>> since there were two paritions on any Debian image. The main reason as I >>> understand it is that there was a ~100M FAT partition because MLO, and >>> u-boot.img needed a place to live. Passed that, g_multi( g_mass_storage ) >>> *has to have* a path to export, so since the FAT partition was already >>> needed, it was also used for that purpose. >>> >>> But a long time ago, I do not remember exact time frame, but Robert >>> probably could. Robert did away with the FAT partition because a lot of >>> inexperienced people were deleting files, and causing their boards being >>> unable to boot. This was done by putting MLO / u-boot.img into the MBR of >>> the disk. So for a long time there was no FAT partition, and only one ext4 >>> partition. As far as how Robert dealt with g_multi needing a path . .. yeah >>> I do not know, or care. I do not use it. >>> >>> Anyway, you have a "real" FAT living right here: >>> >>> >>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>> sdb1 8:17 1 96M 0 part /media/vladimir/BEAGLEBONE >>> >>> How or why, I do not know, and yes I suppose that could be an ext4 >>> partition, but that would make far less sense. I'm pretty sure thats a FAT >>> partition. >>> >>> -- >> 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 beagleboard+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/eeaaac17-4261-4bee-b972-d1b8686e0274%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/eeaaac17-4261-4bee-b972-d1b8686e0274%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/UJDkWhUH3eU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CALHSORoC-duRSSESnL_dhDxjZu-qGsgWsMHm7Chh9sEf2M%2BGAw%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CALHSORoC-duRSSESnL_dhDxjZu-qGsgWsMHm7Chh9sEf2M%2BGAw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAEof%2BYDjLuQy%2BN_ZHZJA%2BEx%2B1Fk%2B1KdyPuvaKTOXZ6DVo%3D4WYw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
