Having installed the newish
http://downloads.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.04.13.img.xz
with kernel 3.8.6-r22d.3 on my (good old white) BeagleBone Rev. A4 with
TowerTech CAN cape TT3201, the can interfaces don't show up. Dmesg reports[ 0.548352] bone-capemgr bone_capemgr.7: Baseboard:
'A335BONE,00A4,0312BB000031'
[ 0.548390] bone-capemgr bone_capemgr.7:
compatible-baseboard=ti,beaglebone
[ 0.579168] bone-capemgr bone_capemgr.7: slot #0: No cape found
[ 0.616276] bone-capemgr bone_capemgr.7: slot #1: No cape found
[ 0.653384] bone-capemgr bone_capemgr.7: slot #2: No cape found
[ 0.683642] bone-capemgr bone_capemgr.7: slot #3: 'TT3201 CAN
Cape,01,TowerTech,TT3201-001'
[ 0.684120] bone-capemgr bone_capemgr.7: initialized OK.
[ 0.688579] bone-capemgr bone_capemgr.7: slot #3: Requesting part
number/version based 'TT3201-001-01.dtbo
[ 0.688614] bone-capemgr bone_capemgr.7: slot #3: Requesting firmware
'TT3201-001-01.dtbo' for board-name 'TT3201 CAN Cape', version '01'
[ 4.097573] bone-capemgr bone_capemgr.7: failed to load firmware
'TT3201-001-01.dtbo'Haven't found info about it elsewhere, any clues from here? CAN works fine
with the older 3.2 kernel. Manually loading various CAN modules doesn't make
the kernel discover any interfaces either, as far as I can see.
Someone needs to create "TT3201-001-01.dtbo" and drop it into
/lib/firmware. I don't see a schematic at [1], but I do see a patch
[2] that should help us figure it out. The only hints I have today
are [3] and [4], but if you take a stab at it I might be able to help.
[1] Tower Technologies - TT3201 CAN Cape User's Manual
[2] https://github.com/koenkooi/linux/commit/af31b4d5a2d52284b169633b9a601c39c7300300.patch
[3] validation-scripts/test-capemgr at master · jadonk/validation-scripts · GitHub
[4] validation-scripts/test-pwm at master · jadonk/validation-scripts · GitHub