can1 not available with kernel 5.10.168-ti-r81

[sans-ltd]

With our own built image using the Kernel 5.10 package with the universal cape activated.
We use the following kernel packages:

repo_rcnee_pkg_list="	\
	bbb.io-kernel-5.10-ti	\
	bbb.io-kernel-5.10-ti-am335x	\
...
	bb-u-boot-am335x-evm	\
	bb-u-boot-am57xx-evm	\

After booting, only can0 is available, not can1:

debian@BeagleBone:~$ uname -a
Linux BeagleBone 5.10.168-ti-r81 #1bookworm SMP PREEMPT Fri Jan 24 01:55:53 UTC 2025 armv7l GNU/Linux
debian@BeagleBone:~$ dmesg | grep can
[   79.780371] c_can_platform 481cc000.can: c_can_platform device registered (regs=ff3f4f7a, irq=47)

With the vanilla IOT image (kernel 5.10.168-ti-r72), both can devices are available:

debian@BeagleBone:~$ uname -a
Linux BeagleBone 5.10.168-ti-r72 #1bookworm SMP PREEMPT Sat Sep 30 03:40:45 UTC 2023 armv7l GNU/Linux
debian@BeagleBone:~$ dmesg | grep can
[   20.437511] systemd[1]: Created slice system-candump.slice - Slice /system/candump.
[   53.473604] c_can_platform 481cc000.can: c_can_platform device registered (regs=afdb0c80, irq=48)
[   53.632398] c_can_platform 481d0000.can: c_can_platform device registered (regs=2712f578, irq=49)
[   86.972158] c_can_platform 481cc000.can can0: setting BTR=1c02 BRPE=0000
[   87.020238] c_can_platform 481d0000.can can1: setting BTR=1c02 BRPE=0000
[   87.371233] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[   87.371312] IPv6: ADDRCONF(NETDEV_CHANGE): can1: link becomes ready
[   91.411280] can: controller area network core
[   91.509853] can: raw protocol

What are we missing?

[RobertCNelson]

the second can port is shared with the i2c eeprom cape bus, as long as cape-universal loaded it should show up.. (been awhile since i tested that 2nd port)..