So . . . The cape loads, and the pins mostly seem to be in order. The
output on the column that was previously pin_mux column ( I guess ) is
different. Not sure what it's telling me. But after compiling can-utils, I
was able to bring up can0, and run candump on it. No output as its not
connected to our external can device yet. Perhaps I'll connect it up
tomorrow, and check it out.
debian@beaglebone:~$ uname -r
4.1.0-rc3-bone0
debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-CAN1
debian@beaglebone:~$ sudo cat
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins |grep can
pin 96 (44e10980.0): 481d0000.can (GPIO UNCLAIMED) function
pinmux_dcan1_pins group pinmux_dcan1_pins
pin 97 (44e10984.0): 481d0000.can (GPIO UNCLAIMED) function
pinmux_dcan1_pins group pinmux_dcan1_pins
debian@beaglebone:~$ sudo ifconfig
can0 can0 Link encap:UNSPEC
HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:180
On Fri, May 8, 2015 at 7:57 PM, William Hermans <[email protected]> wrote:
> Robert,
>
> So what now ? Wait until mothersday evening, and install a "proper"
> linux-image and proceed from there ? I know nearly nothing about using git(
> e.g. branch / push request ), and I'd hate to burden you with that. I think
> I've done enough to wear you, this post, and myself out. heh.
>
> On Fri, May 8, 2015 at 7:51 PM, William Hermans <[email protected]> wrote:
>
>> pin 96 (44e10980.0): 481d0000.can (GPIO UNCLAIMED) function
>>> pinmux_dcan1_pins group pinmux_dcan1_pins
>>> pin 97 (44e10984.0): 481d0000.can (GPIO UNCLAIMED) function
>>> pinmux_dcan1_pins group pinmux_dcan1_pins
>>>
>>
>> This seems to fall in line with the data I have at hand from Mark Irwins
>> post
>>
>>>
>>>
>> On Fri, May 8, 2015 at 7:43 PM, William Hermans <[email protected]>
>> wrote:
>>
>>> OKay . . . forward traction now.
>>>
>>> william@eee-pc:~$ ssh [email protected]
>>>> Debian GNU/Linux 7
>>>>
>>>> BeagleBoard.org Debian Image 2015-03-01
>>>>
>>>> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
>>>>
>>>> default username:password is [debian:temppwd]
>>>>
>>>> [email protected]'s password:
>>>> Last login: Fri May 8 19:00:15 2015 from 192.168.7.1
>>>> debian@beaglebone:~$ dmesg | grep capemgr
>>>> [ 0.000000] Kernel command line: console=tty0 console=ttyO0,115200n8
>>>> beaglebone-capemgr.enable_partno=BB-CAN1 root=/dev/mmcblk0p1
>>>> rootfstype=ext4 rootwait
>>>> [ 3.862818] bone-capemgr bone_capemgr: Failed to find baseboard i2c
>>>> client
>>>> [ 4.544448] bone-capemgr bone_capemgr: Baseboard:
>>>> 'A335BNLT,00C0,3214BBBK0403'
>>>> [ 4.552139] bone-capemgr bone_capemgr:
>>>> compatible-baseboard=ti,beaglebone-black
>>>> [ 4.613921] bone-capemgr bone_capemgr: slot #0: No cape found
>>>> [ 4.673918] bone-capemgr bone_capemgr: slot #1: No cape found
>>>> [ 4.733918] bone-capemgr bone_capemgr: slot #2: No cape found
>>>> [ 4.793918] bone-capemgr bone_capemgr: slot #3: No cape found
>>>> [ 4.800009] bone-capemgr bone_capemgr: enabled_partno part_number
>>>> 'BB-CAN1', version 'N/A', prio '0'
>>>> [ 4.809716] bone-capemgr bone_capemgr: slot #4: generic override
>>>> [ 4.816095] bone-capemgr bone_capemgr: bone: Using override eeprom
>>>> data at slot 4
>>>> [ 4.824047] bone-capemgr bone_capemgr: slot #4: 'Override Board
>>>> Name,00A0,Override Manuf,BB-CAN1'
>>>> [ 4.833698] bone-capemgr bone_capemgr: initialized OK.
>>>> [ 4.840501] bone-capemgr bone_capemgr: slot #4: dtbo
>>>> 'BB-CAN1-00A0.dtbo' loaded; overlay id #0
>>>>
>>>> debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>>>> 0: 54:PF---
>>>> 1: 55:PF---
>>>> 2: 56:PF---
>>>> 3: 57:PF---
>>>> 4: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-CAN1
>>>>
>>>> debian@beaglebone:~$ uname -r
>>>> 4.1.0-rc2-gitea4764e19551fffe445d7e2f2094adcc04cdb2b1
>>>>
>>>
>>> Now, I'm starting to feel wore out after fighting this off and on - this
>>> afternoon. It loads, but no idea if it'll work. I made zero changes to the
>>> source, and honestly did not even look at the source. But, I suppose I
>>> could check the pins to se if they match the notes I have from another
>>> beagelboard.org user . . .
>>>
>>>
>>> On Fri, May 8, 2015 at 7:21 PM, Robert Nelson <[email protected]>
>>> wrote:
>>>
>>>> On Fri, May 8, 2015 at 9:21 PM, Robert Nelson <[email protected]>
>>>> wrote:
>>>> > On Fri, May 8, 2015 at 9:17 PM, William Hermans <[email protected]>
>>>> wrote:
>>>> >> Hey Robert. Thus far it has not worked for me. I was getting
>>>> frustrated, so
>>>> >> had to slow down . . .
>>>> >>
>>>> >> Anyway, seems the sources.list file does not have a listing for your
>>>> repo .
>>>> >> . . well one that is uncommented.
>>>> >>
>>>> >> debian@beaglebone:~$ uname -r
>>>> >> 4.1.0-rc2-bone0
>>>> >
>>>> > That was 3-4 days before capemgr came out..
>>>> >
>>>> > wget
>>>> http://builds.beagleboard.org/linux/4.1/ea4764e19551fffe445d7e2f2094adcc04cdb2b1/linux-image-4.1.0-rc2-gitea4764e19551fffe445d7e2f2094adcc04cdb2b1_1cross_armhf.deb
>>>> >
>>>> > sudo dpkg -i
>>>> linux-image-4.1.0-rc2-gitea4764e19551fffe445d7e2f2094adcc04cdb2b1_1cross_armhf.deb
>>>> >
>>>> > sudo reboot
>>>> >
>>>> >>
>>>> >> debian@beaglebone:~$ dmesg | grep capemgr
>>>> >> [ 0.000000] Kernel command line: console=tty0
>>>> console=ttyO0,115200n8
>>>> >> beaglebone-capemgr.enable_partno=BB-CAN1 root=/dev/mmcblk0p1
>>>> rootfstype=ext4
>>>> >> rootwait
>>>> >>
>>>> >> debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
>>>> >> cat: /sys/devices/platform/bone_capemgr/slots: No such file or
>>>> directory
>>>> >>
>>>> >> debian@beaglebone:~$ ls /sys/devices/platform/
>>>> >> alarmtimer hdmi omap-pcm-audio pmu serial8250
>>>> >> cpufreq-dt.0 leds omap_hwspinlock.0 power soc
>>>> >> fixedregulator@0 ocp oprofile-perf.0 reg-dummy uevent
>>>> >>
>>>> >> debian@beaglebone:~$ nano /etc/apt/sources.list
>>>> >>
>>>> >> etc etc.
>>>> >>
>>>> >> Too many variables here for me to 100% decide where to look next. As
>>>> in am I
>>>> >> even working with a workable linux-image ?
>>>> >
>>>> > On late sunday night, it'll be
>>>> >
>>>> > sudo apt-get update ; sudo apt-get install linux-image-4.1.0-rc2-bone0
>>>> > ; sudo reboot
>>>>
>>>> err..
>>>>
>>>> sudo apt-get update ; sudo apt-get install linux-image-4.1.0-rc3-bone0
>>>> ; sudo reboot
>>>>
>>>> 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].
>>>> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.
