Hey Will!! My responses are in green
I am not clear from the guide what SPI things to install. SP0 & SP1-01? or just one of them? >From your comments it looks like you just need to talk out of 1 spi so my answers are for SPI0. Also should the optargs entry and the capemgr.enable_partno=BB-SP1-01 be present in that file, or removed? Replace it with BB-SPI0-01 Thank you Rudy for your files. I am not sure what to do with them. Given what I have detailed above, do I need to do anything with them? Put BB-SPI0-01-00A0.dtbo in /lib/firmware on your BBB .dts files are the pre compiled device tree files (human readable form) You create a .dtbo file by compiling a .dts file .dbto are files that the BBB will use (machine readable form) And a side-question about the slots listing at the top of this post, number 4.. why does it say 2Gb not 4Gb? I'm pretty sure I have the 4Gb. Is it that there are 2x2? Not sure, as far as I can tell it doesn't affect my 4G BBB in any way Reboot your BBB and cat the slots again you should see BB-SPI0-01 loaded root@beaglebone:/# cd /dev root@beaglebone:/dev# ls Check that spidev1.0 is in there IMPORTANT!!! Make sure that the Lenovo SPI is 3.3v and not 5v. If it's 5v you'll probably blow those pins on your BBB. Do you have a program that can send the data out of the SPI? On Tue, Jul 19, 2016 at 9:40 PM, Will Napier <w...@willnapier.com> wrote: > Thank you Vinay and Rudy for your replies. I am using the Kernel > Version 3.8.13-bone79. > > I realised about the L thing after my last post - thank you Rudy, that > is encouraging that I have successfully disabled HDMI. I have added > the suggested line in /etc/default/capemgr > (CAPE=ADAFRUIT-SP0). Following earlier advice the only other line I > have in this file is: > > CAPE=BB-SP1-01. > > Is this correct for my purpose (ie simply and only to use the BBB to > flash the Lenovo ROM)? > > After adding the line you suggested, I rebooted and this is what I now get > in /sys/devices/bone_capemgr.9/slots: > > 0: 54:PF--- > 1: 55:PF--- > 2: 56:PF--- > 3: 57:PF--- > 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G > 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI > 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN > 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI1-01 > > I am using the guide at > https://libreboot.org/docs/install/bbb_setup.html. In "Setting up > spidev on the BBB" it advises: > > Log on as root on the BBB, using either SSH or a serial console as > defined in #bbb_access. Make sure that you have internet access on > your BBB. > > > Follow the instructions at > http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0 up to (and > excluding) the point where it tells you to modify uEnv.txt > > > I did this, entering the .dtbo in the recommended location (for > SP01). Here is my uEnv.txt: > > ==================== > > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 > > uname_r=3.8.13-bone79 > ##uuid= > #dtb= > > ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..) > > ##BeagleBone Black: HDMI (Audio/Video) disabled: > #dtb=am335x-boneblack-emmc-overlay.dtb > > ##BeagleBone Black: eMMC disabled: > #dtb=am335x-boneblack-hdmi-overlay.dtb > > ##BeagleBone Black: HDMI Audio/eMMC disabled: > #dtb=am335x-boneblack-nhdmi-overlay.dtb > > ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled: > #dtb=am335x-boneblack-overlay.dtb > > ##BeagleBone Black: wl1835 > #dtb=am335x-boneblack-wl1835mod.dtb > > ##BeagleBone Black: replicape > am335x-boneblack-replicape.dtb > > ##BeagleBone Green: eMMC disabled > #dtb=am335x-bonegreen-overlay.dtb > > cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd > cape_universal=enable > > #In the event of edid real failures, uncomment this next line: > #cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd > cape_universal=enable video=HDMI-A-1:1024x768@60e > > ##Example v3.8.x > #cape_disable=capemgr.disable_partno= > #cape_enable=capemgr.enable_partno= > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno= > #cape_enable=bone_capemgr.enable_partno= > > ##Disable HDMI/eMMC (v3.8.x) > > #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G > > ##Disable HDMI (v3.8.x) > cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN > > ##Disable eMMC (v3.8.x) > #cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G > > ##Audio Cape (needs HDMI Audio disabled) (v3.8.x) > #cape_disable=capemgr.disable_partno=BB-BONELT-HDMI > #cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02 > > > ##enable Generic eMMC Flasher: > ##make sure, these tools are installed: dosfstools rsync > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh > > uuid=c3048a42-5170-419f-ae71-6f96bf7f6f11 > > cape_enable=bone_capemgr.enable_partno=BB-SPIDEV0 > > optargs=quiet drm.debug=7 > capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN > capemgr.enable_partno=BB-SPI1-01 > > ======= > > > So my current questions are: > > I am not clear from the guide what SPI things to install. SP0 & > SP1-01? or just one of them? > > Also should the optargs entry and the capemgr.enable_partno=BB-SP1-01 > be present in that file, or removed? > > Thank you Rudy for your files. I am not sure what to do with them. Given > what I have detailed above, do I need to do anything with them? > > And a side-question about the slots listing at the top of this post, > number 4.. why does it say 2Gb not 4Gb? I'm pretty sure I have the > 4Gb. Is it that there are 2x2? > > With thanks to you all for invaluable help. > > Will > > > On Mon, 18 Jul 2016, at 09:02 PM, w...@willnapier.com wrote: > > Hello all, I am new to BBB and using it to flash the ROM on my Lenovo > Thinkpad T400 with Libreboot, using these > <http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0> instructions on > eLinux. > > I disabled HDMI on the Beaglebone by opening vi and removing the comment > from the line that says it disables HDMI. > > I couldn't locate the uEnv.txt file at first, because there isn't a /lib/ > directory. It was found in /boot/ > > But when I did this, ie reboot and look, it seems that the HDMI is still > there: > > root@beaglebone:/var/lib/cloud9# cat /sys/devices/bone_capemgr.*/slots > 0: 54:PF--- > 1: 55:PF--- > 2: 56:PF--- > 3: 57:PF--- > 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G > 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI > 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN > root@beaglebone:/var/lib/cloud9# > ==== > > I have now tried the advice of Vinay: > > > > > Another solution is also simple, just include the line "CAPE=ADAFRUIT-SP0" > in /etc/default/capemgr file. Then reboot and all should work fine. > > ======== > > > This did not work. I still get the same slots listing. > > I then followed this advice also from vinay: > ============ > > > Re: [beagleboard] Re: Issues with Enabling SPIDev on Beaglebone Black > Other recipients: rudydelo...@gmail.com, jb...@eng.ucsd.edu > > Step 1 : Go to root@beaglebone: /boot# > Step 2 : Open uEnv.txt file > Step 3 : Inside the file > > You will find these lines, so do the following: In case If you dont find > these lines for your kernel, then just append the line > "cape_enable=bone_capemgr.enable_partno=BB-SPIDEV0" to the end of the file. > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno= > cape_enable=bone_capemgr.enable_partno=BB-SPIDEV0 > > Step 4 : Reboot your BBB > Step 5 : Go to /sys/devices/platform/bone_capemgr# cat slots or dmesg to > check. > > Then check if your SPI device has been loaded. > > This works with Linux beaglebone kernel 4.1.18-ti-r53 > > =============== > > This didn't work. there is no /sys/devices/platform/bone_capemgr. > > > I would be very grateful for any help with this. With thanks, Will > > > > -- > 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/2O0-NwbKc2M/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/f55ac74f-155f-4536-8e0d-49e471e6f044%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/f55ac74f-155f-4536-8e0d-49e471e6f044%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/2O0-NwbKc2M/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/1468928430.2674762.670488169.76C51D84%40webmail.messagingengine.com > <https://groups.google.com/d/msgid/beagleboard/1468928430.2674762.670488169.76C51D84%40webmail.messagingengine.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/CAGLDO90GHOaMAfFW9zktQTnpC%3DVvNhSnjX2dN3r3-ztR8bm2tg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
