Thanks again, Robert, The display now works and I've been able to loop the SPI back to the BBB.
I'm grateful for your help, /Jon. Den tisdag 3 april 2018 kl. 17:32:17 UTC+2 skrev RobertCNelson: > > On Tue, Apr 3, 2018 at 10:26 AM, Jon Lundstrom <j.b.lu...@gmail.com > <javascript:>> wrote: > > > > Thank you Robert, > > > > That did the trick. > > > > However, it has the side-effect of turning my display all black. > > I use a Newhaven display cape and according to its User Guide, there > should > > be no conflict for these SPI-pins. > > ( > http://www.newhavendisplay.com/userguides/NHD-7.0CTP-CAPE_User_Guide.pdf) > > > > So I had a look at the assigned pins in > > /sys/kernel/debug/pinctrl/44e10800.pinmux/pingroups and see that > following > > group is added (using diff): > > > >> group: pinmux_bb_spi0_pins > >> pin 84 (PIN84) > >> pin 85 (PIN85) > >> pin 86 (PIN86) > >> pin 87 (PIN87) > > > > which seems in order, but following groups were removed: > > > > < group: pinmux_bb_lcd_pwm_backlight_pins > > < pin 18 (PIN18) > > > > < group: pinmux_bb_lcd_lcd_pins > > < pin 40 (PIN40) > > < pin 41 (PIN41) > > < pin 42 (PIN42) > > < pin 43 (PIN43) > > < pin 44 (PIN44) > > < pin 45 (PIN45) > > < pin 46 (PIN46) > > < pin 47 (PIN47) > > < pin 48 (PIN48) > > < pin 49 (PIN49) > > < pin 50 (PIN50) > > < pin 51 (PIN51) > > < pin 52 (PIN52) > > < pin 53 (PIN53) > > < pin 54 (PIN54) > > < pin 55 (PIN55) > > < pin 15 (PIN15) > > < pin 14 (PIN14) > > < pin 13 (PIN13) > > < pin 12 (PIN12) > > < pin 11 (PIN11) > > < pin 10 (PIN10) > > < pin 9 (PIN9) > > < pin 8 (PIN8) > > < pin 56 (PIN56) > > < pin 57 (PIN57) > > < pin 58 (PIN58) > > < pin 59 (PIN59) > > < pin 35 (PIN35) > > > > < group: pinmux_edt_ft5x06_pins > > < pin 105 (PIN105) > > > > I don't know about the last group (PIN105) but the other two groups most > > certainly affect the display function. > > > > I haven't seen the corresponding .dts-file for BB-SPIDEV0-00A0.dtbo, but > I > > tried making my own that should not touch these pins: Still, the same > result > > (same pin groups are removed). > > > > There seems to be some mechanism that disables the display pins when > adding > > an overlay to the uEnv.txt. > > > > Robert, as an expert in BBB, do you have answer to this? > > Well, addr0 -> addr3 is for eeprom detected capes, so change: > > uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo > > to > > uboot_overlay_addr4=/lib/firmware/BB-SPIDEV0-00A0.dtbo > > https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/d5721165-7051-4370-ae86-f0ddc0644191%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.