Hi @cmbaker/Chad, which version of Debian were you using at that time? Could you also copy your whole /boot/uEnv.txt file? I have followed the exact instructions given by you, but I'm still getting the same message:
P9_28 pinmux file not found! On Saturday, May 5, 2018 at 8:20:24 PM UTC+5:30, cmbaker3 wrote: > > My /boot/uEnv.txt differs, I do not use the uboot_overlay_addr lines, they > are commented out. > I have a few more lines following the command=coherent ... > The last lines in my file are > > cmdline=coherent_pool=1M net.ifnames=0 quiet > > #In the event of edid real failures, uncomment this next line: > #cmdline=coherent_pool=1M net.ifnames=0 quiet 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=/lib/firmware/BB-SPIDEV1-00A0.dtbo > > ##enable Generic eMMC Flasher: > ##make sure, these tools are installed: dosfstools rsync > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh > > You might have the cape_enable line as > > > cape_enable=bone_capemgr.enable_partno=/lib/firmware/BB-SPIDEV0-00A0.dtbo,/lib/firmware/BB-SPIDEV1-00A0.dtbo > > > Hope this helps, > Chad > > > On 5/4/18 1:54 AM, [email protected] <javascript:> wrote: > > Hi guys, > > I edited uEnv.txt according to the discussion. In particular I added these > lines (I also copied my entire uEnv file in this post; see below): > uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo > uboot_overlay_addr1=/lib/firmware/BB-SPIDEV1-00A0.dtbo > > > but doesn't change anything; after reboot I still can't use "config-pin > p9_28 spi_cs" to enable SPI1. > > My system: uname -a > Linux beaglebone 4.9.78-ti-r94 > > I also used "/opt/scripts/tools$ ./version.sh" to get more information > (please find full log below) and found some interesting lines: > dmesg | grep pinctrl-single > [ 1.404852] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 > size 568 > [ 1.648918] pinctrl-single 44e10800.pinmux: pin PIN103 already > requested by 481a0000.spi; cannot claim for 48038000.mcasp > [ 1.660206] pinctrl-single 44e10800.pinmux: pin-103 (48038000.mcasp) > status -22 > [ 1.667697] pinctrl-single 44e10800.pinmux: could not request pin 103 > (PIN103) from group mcasp0_pins on device pinctrl-single > > -> Pin103 is P9_28. > > Any hints what I could try next? > > Would really appreciate your help and thank you all in advance! > > Best regards, > Marco > > > > > ##### MY UENV FILE > > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 > > uname_r=4.9.78-ti-r94 > #uuid= > #dtb= > > > ###U-Boot Overlays### > ###Documentation: > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > ###Master Enable > enable_uboot_overlays=1 > ### > ###Overide capes with eeprom > uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo > uboot_overlay_addr1=/lib/firmware/BB-SPIDEV1-00A0.dtbo > #uboot_overlay_addr2=/lib/firmware/<file2>.dtbo > #uboot_overlay_addr3=/lib/firmware/<file3>.dtbo > ### > ###Additional custom capes > #uboot_overlay_addr4=/lib/firmware/<file4>.dtbo > #uboot_overlay_addr5=/lib/firmware/<file5>.dtbo > #uboot_overlay_addr6=/lib/firmware/<file6>.dtbo > #uboot_overlay_addr7=/lib/firmware/<file7>.dtbo > ### > ###Custom Cape > #dtb_overlay=/lib/firmware/<file8>.dtbo > ### > ###Disable auto loading of virtual capes (emmc/video/wireless/adc) > #disable_uboot_overlay_emmc=1 > #disable_uboot_overlay_video=1 > #disable_uboot_overlay_audio=1 > #disable_uboot_overlay_wireless=1 > #disable_uboot_overlay_adc=1 > ### > ###PRUSS OPTIONS > ###pru_rproc (4.4.x-ti kernel) > #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo > ###pru_uio (4.4.x-ti & mainline/bone kernel) > #uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > ### > ###Cape Universal Enable > enable_uboot_cape_universal=1 > ### > ###Debug: disable uboot autoload of Cape > #disable_uboot_overlay_addr0=1 > #disable_uboot_overlay_addr1=1 > #disable_uboot_overlay_addr2=1 > #disable_uboot_overlay_addr3=1 > ### > ###U-Boot fdt tweaks... (60000 = 384KB) > #uboot_fdt_buffer=0x60000 > ###U-Boot Overlays### > > cmdline=coherent_pool=1M net.ifnames=0 quiet > > > ==================================================== > > debian@beaglebone:/opt/scripts/tools$ sudo ./version.sh > > git:/opt/scripts/:[5935e83ecaedfd4fd88a4b870ffe5af33ded0617] > eeprom:[A335BNLT00C02215BBBK12B4] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[BeagleBoard.org Debian Image 2018-01-28] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2018.01-00002-g9aa111a004]:[location: dd MBR] > kernel:[4.9.78-ti-r94] > nodejs:[v6.13.0] > uboot_overlay_options:[enable_uboot_overlays=1] > > uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo] > > uboot_overlay_options:[uboot_overlay_addr1=/lib/firmware/BB-SPIDEV1-00A0.dtbo] > uboot_overlay_options:[enable_uboot_cape_universal=1] > pkg:[bb-cape-overlays]:[4.4.20180223.0-0rcnee0~stretch+20180223] > pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104] > pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830] > groups:[debian : debian adm kmem dialout cdrom floppy audio dip video > plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep > admin spi tisdk weston-launch xenomai] > cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M > net.ifnames=0 quiet] > dmesg | grep pinctrl-single > [ 1.404852] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 > size 568 > [ 1.648918] pinctrl-single 44e10800.pinmux: pin PIN103 already > requested by 481a0000.spi; cannot claim for 48038000.mcasp > [ 1.660206] pinctrl-single 44e10800.pinmux: pin-103 (48038000.mcasp) > status -22 > [ 1.667697] pinctrl-single 44e10800.pinmux: could not request pin 103 > (PIN103) from group mcasp0_pins on device pinctrl-single > dmesg | grep gpio-of-helper > [ 1.405879] gpio-of-helper ocp:cape-universal: ready > END > > > > > Am Dienstag, 1. Mai 2018 00:23:29 UTC+2 schrieb Rick M: >> >> >> >> > On Apr 30, 2018, at 12:47 , Chad Baker <[email protected]> wrote: >> > >> > It is a workaround for a bug, I believe. When I enable the dtbo, I get >> the following directory constructed during the boot process >> > /sys/devices/platform/ocp/ocp:P9_28_pinmux >> > Without the dtbo, this directory is missing. >> >> Oh I see, thanks. >> >> > Chad >> > >> > On 4/30/18 2:24 PM, Rick Mann wrote: >> >>> On Apr 30, 2018, at 08:22 , Chad Baker <[email protected]> wrote: >> >>> >> >>> Did you add the BB-SPIDEV1-00A0.dtbo to the device tree boot list in >> uEnv.txt? >> >> Should that be necessary if one is using CAPE-UNIVERSAL? >> >> >> >> >> >>> Chad >> >>> >> >>> >> >>> On 4/30/18 7:51 AM, [email protected] wrote: >> >>>> Hi all, >> >>>> >> >>>> I have to bring this thread to life again, as I'm facing the same >> issue: >> >>>> >> >>>> all I want to do is to assign p9_29 as "spi_cs" on my BBB running >> "4.9.78-ti-r94". >> >>>> >> >>>> Running "config-pin -l p9_28" leads to "default gpio gpio_pu gpio_pd >> gpio_input spi_cs pwm pruout pruin". So all looks good, as this pin can be >> used in spi_cs mode. >> >>>> >> >>>> Now I want to configure the pin to actually work as spi pin: >> >>>> >> >>>> config-pin p9_28 spi_cs >> >>>> P9_28 pinmux file not found! >> >>>> sudo: no askpass program specified, try setting SUDO_ASKPASS >> >>>> Cannot write pinmux file: >> /sys/devices/platform/ocp/ocp*P9_28_pinmux/state >> >>>> >> >>>> The same error is printed when running "config-pin p9_29 spi" or >> "config-pin p9_31 spi_sclk". However, command "config-pin p9_30 spi" works >> well. >> >>>> >> >>>> Would really appreciate if someone can help out here! >> >>>> >> >>>> Best regards, >> >>>> Marco >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> Am Samstag, 28. Januar 2017 02:51:38 UTC+1 schrieb Charles >> Steinkuehler: >> >>>> On 1/27/2017 7:43 PM, Drew Fustini wrote: >> >>>>> Charles / Robert: >> >>>>> Should P9.28 be SPI by default? >> >>>> All pins are GPIO by default, with pull up/down set to match the >> reset >> >>>> defaults of the processor. To use P9.28 as SPI, in addition to >> >>>> loading cape-universal, it is necessary to run: >> >>>> >> >>>> config-pin P9.28 spi >> >>>> >> >>>> If this does not result in the pinmux being set to spi, it's a bug. >> >>>> >> >>>> -- >> >>>> Charles Steinkuehler >> >>>> [email protected] >> >>>> -- >> >>>> 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 [email protected]. >> >>>> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/89254b2e-33ca-4ea0-bb9f-3ca89270f89c%40googlegroups.com. >> >> >> >>>> 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 [email protected]. >> >>> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/30e8fef7-bd03-37a6-b8a9-e4bfad41445d%40gmail.com. >> >> >> >>> 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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/22d4ab18-c370-d437-fa7b-c4cf404ea358%40gmail.com. >> >> >> > For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> Rick Mann >> [email protected] >> >> >> -- > 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 [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/61eabc32-c58e-460a-9992-e32cf395e19b%40googlegroups.com > > <https://groups.google.com/d/msgid/beagleboard/61eabc32-c58e-460a-9992-e32cf395e19b%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 the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0fb94d0a-bcb7-4bbe-abde-319cafc0db2b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
