On Thu, Aug 29, 2019 at 2:23 PM <[email protected]> wrote:
>
> While attempting to use the SPI1 pins, I have had trouble in configuring the 
> pins. I had it working after updating to the 4.19.50-ti-rt-r25 kernel, but 
> then it mysteriously stopped working. I believe it stopped when I included 
> the BB-I2C2-00A0.dtbo file in the uBoot, but I can't be sure.
>
> Here's where the error happens:
> debian@beaglebone:~$ config-pin -a 928 spi_cs
> P9_28 pinmux file not found!
> bash: /sys/devices/platform/ocp/ocp*P9_28_pinmux/state: No such file or 
> directory
> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_28_pinmux/state
>
> When I look for this P9_28 file in the ocp directory, I do not see 9_28, 
> 9_29, 9_30, nor 9_31 pinmux.
> drwxrwxr-x   3 root gpio    0 Aug 23 15:14 ocp:P9_27_pinmux
> drwxrwxr-x   3 root gpio    0 Aug 23 15:14 ocp:P9_41_pinmux
> It skips right over.
>
> debian@beaglebone:~$ uname -r
> 4.19.59-ti-rt-r25
>
> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> [sudo] password for debian:
> git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
> eeprom:[A335BNLTEIA04218BBBK0D06]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2018.09-00002-g0b54a51eee]:[location: dd MBR]
> kernel:[4.19.59-ti-rt-r25]
> nodejs:[v6.14.4]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-SPIDEV1-00A0.dtbo]

Well yeah... 9_28 is already CS..

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-SPIDEV1-00A0.dts

Regards.

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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/CAOCHtYh3G05fuGYEdh%2BtPsbEZ6JfFCOizeVaQdY%3Dz-DikG0sNg%40mail.gmail.com.

Reply via email to