> > *But I don't want to use I2C-2... and i don't know how to disable that.* > *Here is my slots:* >
So, this is probably enabled in the main board dtb file. Which means, in order to disable i2c-2, you'll have to edit that file. **HOWEVER* *if i2c-2 is enabled in the main board file, then there is a good chance it is needed for something in relation to booting. I do know that the on board eeprom is used through i2c, for serial number, board type identification, etc. But not sure which i2c is used. Probably safe to guess that i2c-2 is what's used though . . . On Sat, Feb 6, 2016 at 12:23 PM, <darek.smi...@gmail.com> wrote: > Hello > I'm using image: bone-debian-8.2-console-armhf-2015-12-20-2gb > > root@beaglebone:~# uname -a > Linux beaglebone 4.1.13-ti-r36 #1 SMP PREEMPT Fri Dec 11 00:44:56 UTC > 2015 armv7l GNU/Linux > > I can't load cape to use UART1 with CTS/RTS. It looks like pin 95 conflict > witch I2C-2. > > [ 4.044320] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART1' > VER 'N/A' PR '0' > [ 4.044334] bone_capemgr bone_capemgr: slot #4: override > ........ > [ 4.045402] bone_capemgr bone_capemgr: initialized OK. > [ 4.047681] pinctrl-single 44e10800.pinmux: pin 44e1097c.0 already > requested by 4819c000.i2c; cannot claim for 48022000.serial > ........ > [ 4.083531] pinctrl-single 44e10800.pinmux: pin-95 (48022000.serial) > status -22 > [ 4.098640] pinctrl-single 44e10800.pinmux: could not request pin 95 ( > 44e1097c.0) from group pinmux_bb_uart1_pins on device pinctrl-single > > But I don't want to use I2C-2... and i don't know how to disable that. > Here is my slots: > > root@beaglebone:~# cat /sys/devices/platform/bone_capemgr/slots > 0: PF---- -1 > 1: PF---- -1 > 2: PF---- -1 > 3: PF---- -1 > 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-UART1 > 5: P-O-L- 1 Override Board Name,00A0,Override Manuf,BB-UART2 > 6: P-O-L- 2 Override Board Name,00A0,Override Manuf,BB-UART4 > 7: P-O-L- 3 Override Board Name,00A0,Override Manuf,BB-UART5 > > Other UART's are loading without any problem. > > Here is my uEnv.txt > root@beaglebone:~# cat /boot/uEnv.txt > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 > > uname_r=4.1.13-ti-r36 > #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 > #dtb=am335x-boneblack-replicape.dtb > > ##BeagleBone Green: eMMC disabled > #dtb=am335x-bonegreen-overlay.dtb > > cmdline=coherent_pool=1M quiet cape_universal=enable > > #In the event of edid real failures, uncomment this next line: > #cmdline=coherent_pool=1M quiet 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=BB-UART1,BB-UART2,BB-UART4,BB-UART5 > > ##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 > > > I would be wery thankfull if someone explain me how to disable i2c-2 on > system startup. > > > > > -- > 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. > 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. For more options, visit https://groups.google.com/d/optout.
