On Tue, Mar 31, 2015 at 9:33 AM,  <[email protected]> wrote:
> Thank you very much for the answer!
>
> By the truth, I need to be able to use also other interfaces (GPIOs, PWM,
> Analog Input, I2C, SPI, UART, USB, Ethernet).
> I followed your suggestions (installed 3.14 RT kernel):
> root@beaglebone:~# uname -a
> Linux beaglebone 3.14.35-ti-rt-r56 #1 SMP PREEMPT Sun Mar 29 01:13:05 UTC
> 2015 armv7l GNU/Linux

Did you change dtb in /boot/uEnv.txt ?

dtb=am335x-black-can1.dtb


> ... but I have the following problems:
> 1) with SocketCAN. Giving the commands:
> root@beaglebone:~# /sbin/ip set link can1 type can bitrate 500000
> root@beaglebone:~# ifconfig can1 up
> I enable can1:
> root@beaglebone:~# ifconfig can1
> can1      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:71
> Now I just perform the candump - cansend (can-utils installed on BBB from
> https://github.com/digitalbond/canbus-beaglebone) test on can1 but cansend
> doesn't send anything.

The peripheral is enabled, but the pinmux is not set by default..


> 2) New device tree overlay management. I cannot see any longer the slots
> file for pin muxing (before it was located in the directory
> /sys/devices/bone_capemgr.9):
> root@beaglebone:~# find / -name "bone_capemgr*"
> root@beaglebone:~# find / -name "slots"
> /sys/module/snd/parameters/slots
> root@beaglebone:~#
>
> So far, I have always handled pins with device tree overlays, by taking the
> available ones (placed in /lib/firmware) or creating new ones. Do I need to
> adapt all my existing programs according to the new management?

capemgr = 3.8.x

> 3) Ethernet-over-USB is no longer working with kernel 3.14: the interface
> usb0 doesn't come up any more with ifconfig.

odd.. cat /etc/dogtag


> 4) I went back to 3.8 kernel (by modifying properly uname_r variable in
> uEnv.txt and rebooting) and then I tried to return to 3.14 (always by
> modifying uEnv.txt and rebooting), but the system doesn't boot.

cat /etc/dogtag

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.

Reply via email to