Re: [beagleboard] Problems with CANBus at BBB

2015-11-06 Thread William Hermans 
>
> *When I try to enable both "BB-CAN1" and "cape-CBB-Serial:r01", BBB
> doesn't let me to have them both activated at the same time and mentions
> P9.24 conflict.*
>
> *How should I solve this issue?*
> *Thanks in advance.*
> *Cheers*
> *Mojtaba*
>


The logic supply serial / can cape should automatically be detected at
boot. If you're using any of the official debian images. This means you do
not have to do anything, as far as loading the cape goes.

On Fri, Nov 6, 2015 at 2:04 AM, mojtaba moghimi 
wrote:

> Hello William
> I have the same problem as Markus has. I've done the same as Markus and
> I'm using Logic supply canbus cape. I don't see any message using candump
> and can't send any message.
> I use Microchip can analyzer to send can signals to my BBB.
> When I try to enable both "BB-CAN1" and "cape-CBB-Serial:r01", BBB doesn't
> let me to have them both activated at the same time and mentions P9.24
> conflict.
>
> How should I solve this issue?
> Thanks in advance.
> Cheers
> Mojtaba
>
> On Monday, October 26, 2015 at 11:21:55 PM UTC+10, William Hermans wrote:
>>
>> You need to use a can transceiver, and properly terminate the can
>> interface. Otherwise, the can interface will not work. in our case we're
>> using the Logic supply serial / canbus cape.
>> http://www.logicsupply.com/cbb-serial/
>>
>> $ sudo ifconfig
>> [sudo] password for william:
>> 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:38317627 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:282730298 (269.6 MiB)  TX bytes:0 (0.0 B)
>>   Interrupt:182
>>
>> $ candump -n 10 can0
>>   can0  19F00302   [8]  40 44 03 13 01 01 00 00
>>   can0  19F00302   [8]  41 00 00 00 00 00 00 00
>>   can0  19F00302   [8]  42 00 B8 0B 00 00 00 00
>>   can0  19F00302   [8]  43 00 00 00 00 02 01 00
>>   can0  19F00302   [8]  44 00 00 00 00 00 00 00
>>   can0  19F00302   [8]  45 00 00 B8 0B 00 00 00
>>   can0  19F00302   [8]  46 00 00 00 00 00 03 01
>>   can0  19F00302   [8]  47 00 00 00 00 00 00 00
>>   can0  19F00302   [8]  48 00 00 00 B8 0B 00 00
>>   can0  19F00302   [8]  49 00 00 00 00 00 00 FF
>>
>>
>> On Mon, Oct 26, 2015 at 6:04 AM, Robert Nelson 
>> wrote:
>>
>>> On Sun, Oct 25, 2015 at 7:49 AM,   wrote:
>>> > Hi out there,
>>> >
>>> > hope someone can help me to activate the CAN Bus interface at
>>> Beaglebone
>>> > Black. I describe shortly what I
>>> > have done so far
>>>
>>> The can interface works fine, what did you use to interface the bbb's
>>> pins to your can network?
>>>
>>> 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 beagleboard...@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.
>

-- 
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.

Re: [beagleboard] C compiler(s) for Beaglebone Black (BBB)

2015-11-06 Thread William Hermans 
>
> *What Linux C complier toolset(s) that can be used directly on the BBB? I
> am thinking that I might have to use the host PC (Ubuntu15,xx) and then
> load the compiled code on to the BBB (???).*
> *I like the Python tools (no compilation needed) but I am not sure how one
> can incorporate using the interrupts (on the ARM) in a *
> *Python environment development environment. So, I am thinking there are C
> complier tools that will work for the BBB.*
> *My first BBB is scheduled to arrive Friday and I am looking forward to
> start using the BBB.*


No idea what the official images come with( installed ), but just about
anything you would need for C development can be installed via the package
"build-essential". So . . .



*sudo apt-get install build-essential*
This is includes gcc, make, libc6-dev, and more . . .


On Fri, Nov 6, 2015 at 6:15 AM, Chad Baker  wrote:

> gcc is included in every OS that I have worked with on the BBB.
> Have you googled python and interrupts? There is a LOT of info out there.
> Also, you can take articles for the RPi (I know) and adapt.
> Chad
>
>
> On 11/5/2015 1:15 PM, jship1...@gmail.com wrote:
>
> What Linux C complier toolset(s) that can be used directly on the BBB? I
> am thinking that I might have to use the host PC (Ubuntu15,xx) and then
> load the compiled code on to the BBB (???).
> I like the Python tools (no compilation needed) but I am not sure how one
> can incorporate using the interrupts (on the ARM) in a
> Python environment development environment. So, I am thinking there are C
> complier tools that will work for the BBB.
> My first BBB is scheduled to arrive Friday and I am looking forward to
> start using the BBB.
>
>
> --
> 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.
>
>
>
> --
> Chad Baker Memphis, TN
>
> --
> 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.

Re: [beagleboard] DWA-131 driver fail using beaglebone as wi-fi hostspot

2015-11-06 Thread Robert Nelson 
On Fri, Nov 6, 2015 at 5:20 PM, Marcos Sousa
 wrote:
> Robert,
>
> I updated, but the error persist. I tried to use the default hostapd, but
> the erro still the same. Any other idea?

you need to use realtek's hostapd..

>
> Is there another wifi adapter model more compatible with beaglebone?

What happens when you disable "hdmi/nhdmi" cape? ;)

Otherwise fire up 4.1.12-ti-r28

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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] DWA-131 driver fail using beaglebone as wi-fi hostspot

2015-11-06 Thread Marcos Sousa 
Robert,

I updated, but the error persist. I tried to use the default hostapd, but 
the erro still the same. Any other idea?

Is there another wifi adapter model more compatible with beaglebone?

Thanks.

On Friday, November 6, 2015 at 8:33:07 PM UTC-2, RobertCNelson wrote:
>
> On Fri, Nov 6, 2015 at 4:22 PM, Marcos Sousa 
> > wrote: 
> > Hi, 
> > 
> > I remove the brigde=br0, but the message still the same: 
> > 
> > drv->ifindex=4 
> > l2_sock_recv==l2_sock_xmit=0x0x51638 
> > ioctl[SIOCSIWMODE]: Operation not supported 
> > Could not set interface to mode(3)! 
> > Could not set interface to master mode! 
> > rtl871xdrv driver initialization failed. 
> > 
> > The dmesg log is as attachment. 
>
> fyi: 
>
> Back in May 22, 2014, "wireless: rtl8192cu v4.0.2_9000.20130911" was 
> intergrated into the "3.8.13-boneX" tree and first released as 
> "3.8.13-bone55" 
>
>
> https://github.com/RobertCNelson/bb-kernel/commit/eb82d272f28d537ffb96011a2e561b40eddd9bc1
>  
>
> Your welcome to stay on "3.8.13-bone47" but upgrading to the "latest" 
> 3.8.13: "3.8.13-bone79" might be easier.. 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] DWA-131 driver fail using beaglebone as wi-fi hostspot

2015-11-06 Thread Robert Nelson 
On Fri, Nov 6, 2015 at 4:22 PM, Marcos Sousa
 wrote:
> Hi,
>
> I remove the brigde=br0, but the message still the same:
>
> drv->ifindex=4
> l2_sock_recv==l2_sock_xmit=0x0x51638
> ioctl[SIOCSIWMODE]: Operation not supported
> Could not set interface to mode(3)!
> Could not set interface to master mode!
> rtl871xdrv driver initialization failed.
>
> The dmesg log is as attachment.

fyi:

Back in May 22, 2014, "wireless: rtl8192cu v4.0.2_9000.20130911" was
intergrated into the "3.8.13-boneX" tree and first released as
"3.8.13-bone55"

https://github.com/RobertCNelson/bb-kernel/commit/eb82d272f28d537ffb96011a2e561b40eddd9bc1

Your welcome to stay on "3.8.13-bone47" but upgrading to the "latest"
3.8.13: "3.8.13-bone79" might be easier..

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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] DWA-131 driver fail using beaglebone as wi-fi hostspot

2015-11-06 Thread Marcos Sousa 
Hi,

I remove the brigde=br0, but the message still the same:

drv->ifindex=4
l2_sock_recv==l2_sock_xmit=0x0x51638
ioctl[SIOCSIWMODE]: Operation not supported
Could not set interface to mode(3)!
Could not set interface to master mode!
rtl871xdrv driver initialization failed.

The dmesg log is as attachment.

Thanks

On Friday, November 6, 2015 at 1:57:02 PM UTC-2, Jason Kridner wrote:
>
> Can you include the dmesg log? Are you sure br0 is how the adapter was 
> named?
>
> On Nov 6, 2015, at 9:18 AM, marcoscai...@gmail.com  wrote:
>
> I'm trying to create a wi-fi hostspot using a beaglebone black rev-C and 
> DWA-131 nano wi-if adapter.
>
> I followed this article to install the driver: 
> http://www.linux-hardware-guide.com/2013-11-16-d-link-dwa-131-n300-usb-wifi-adapter
>
> And this project do setup the hostapd: 
> https://github.com/jekader/hostapd-rtl
>
> But when I try to start I'm getting the following error:
>
> Configuration file: /etc/hostapd/hostapd.conf
> drv->ifindex=4
> l2_packet_init: ioctl[SIOCGIFINDEX]: No such device
> no br0 interface , let l2_sock_recv==l2_sock_xmit=0x0x51648
> ioctl[SIOCSIWMODE]: Operation not supported
> Could not set interface to mode(3)!
> Could not set interface to master mode!
> rtl871xdrv driver initialization failed.
> rmdir[ctrl_interface]: No such file or directory
>
> My hostapd.conf is:
>
> interface=usb0
> driver=rtl871xdrv
> bridge=br0
> ssid=NETWORK-NAME
> channel=1
> wmm_enabled=0
> wpa=1
> wpa_passphrase=NETWORK-PASSWORD
> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=TKIP
> rsn_pairwise=CCMP
> auth_algs=1
> macaddr_acl=0
>
> Hostapt version? Driver's name or config?
>
> ps: I'm not confortable because my network interface for the wi-fi is usb0 
> instead of wlan0. Is a driver issue?
>
> -- 
> 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...@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.


dmesg.log
Description: Binary data

[beagleboard] Userspace access to dmtimer interrupts

2015-11-06 Thread Andrew Szymkowiak 
In my application, I would like to have a thread which is waiting for an 
interrupt from one of the dmtimers.  I see how this is being done through 
the sysfs interface for gpio edges.  Has anyone done anything similar for 
the dmtimers, or have another suggestion for how to get this triggered? (I 
do want an interrupt, and not a scheme that involves constantly re-reading 
the dm timer registers).  This will be infrequent, and I do not require an 
immensely small latency.  (If necessary I'll write a kernel driver module 
to do this, but I'm hoping to not re-invent an existing wheel).

Thanks,
   Andy S.

-- 
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.

Re: [beagleboard] capemgr in 4.1.10-bone16 kernel not loading capes at boot

2015-11-06 Thread jlhessle 

>
> The dtbo file is present on the system. Below is the serial boot log
>
> U-Boot 2015.04-svn40 (Oct 23 2015 - 08:19:16)
>
>Watchdog enabled
> I2C:   ready
> DRAM:  512 MiB
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Net:not set. Validating first E-fuse MAC
> cpsw
> Hit any key to stop autoboot:  0 
> gpio: pin 53 (gpio 53) value is 1
> switch to partitions #0, OK
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> Checking for: /uEnv.txt ...
> reading uEnv.txt
> 983 bytes read in 6 ms (159.2 KiB/s)
> gpio: pin 55 (gpio 55) value is 1
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Checking if uenvcmd is set ...
> gpio: pin 56 (gpio 56) value is 1
> Running uenvcmd ...
> 924 bytes read in 40 ms (22.5 KiB/s)
> 6948760 bytes read in 430 ms (15.4 MiB/s)
> 5082010 bytes read in 329 ms (14.7 MiB/s)
> 54462 bytes read in 124 ms (428.7 KiB/s)
> Kernel image @ 0x8200 [ 0x00 - 0x6a0798 ]
> ## Flattened Device Tree blob at 8800
>Booting using the fdt blob at 0x8800
>Using Device Tree in place at 8800, end 880104bd
>
> Starting kernel ...
>
>
> The uenv.txt on the boot partition is:
> ##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
>
> loadaddr=0x8200
> fdtaddr=0x8800
> rdaddr=0x8808
>
> initrd_high=0x
> fdt_high=0x
>
> ##These are needed to be compliant with Debian 2014-05-14 u-boot.
>
> loadximage=load mmc 0:2 ${loadaddr} /boot/vmlinuz-${uname_r}
> loadxfdt=load mmc 0:2 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
> loadxrd=load mmc 0:2 ${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize 
> ${filesize}
> loaduEnvtxt=load mmc 0:2 ${loadaddr} /boot/uEnv.txt ; env import -t 
> ${loadaddr} ${filesize};
> check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;
> loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run 
> loadxfdt;
>
> mmcargs=setenv bootargs console=${console} ${optargs} no_console_suspend=1 
> vt.global_cursor_default=0 consoleblank=0 ${cape_disable} ${cape_enable} 
> root=/dev/mmcblk0p2 rootfstype=${mmcrootfstype} ${cmdline}
> uenvcmd=run loadall; run mmcargs; bootz ${loadaddr} ${rdaddr}:${rdsize} 
> ${fdtaddr};d from the 
>

I also found that if I remove the loadxrd, thereby removing the initrd from 
the uEnv.txt that it will load the capes properly when booting from the 
sdcard. However removing the initrd from the emmc boot causes the boot to 
hang when loading capes.

Thanks for the help

Jason

-- 
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.

Re: [beagleboard] kernel updates: 4.1.12-ti-r27 (BBB all spi/spidev users rejoice)

2015-11-06 Thread Robert Nelson 
On Fri, Nov 6, 2015 at 5:52 AM, Micka  wrote:
> Hi Robert,
>
> about this bug, are you also fixing the kernel am33x-rt-v4.1 ?
>
> I'm interested also by the spi in the kernel am33x-rt-v4.1.

ToDate:

4.1.12-ti-r27+
4.1.12-ti-rt-r27+

and what will become "4.4-rc1"..

Haven't had a chance to apply it "everywhere"..

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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cannot get linux logo (splash) to show correctly in Kernel 3.14-ti

2015-11-06 Thread E Mag 
Yes, I changed it for ttyO0 and now it just shows a black screen. I guess 
that's kind of better, but still no splash :(

Here's my current uEnv.txt if it helps:

uname_r=3.14.56-ti-r78
##This will work with: Angstrom's 2013.06.20 u-boot.
cmdline = splash
loadaddr=0x8200
fdtaddr=0x8800
rdaddr=0x8808

initrd_high=0x
fdt_high=0x

loadximage=load mmc 0:1 ${loadaddr} /boot/vmlinuz-${uname_r}
loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxrd=load mmc 0:1 ${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize 
${filesize}
loaduEnvtxt=load mmc 0:1 ${loadaddr} /boot/uEnv.txt ; env import -t 
${loadaddr} ${filesize};
loadall=run loaduEnvtxt; run loadximage; run loadxfdt;

mmcargs=setenv bootargs console=ttyO0  ${optargs}  root=${mmcroot} 
rootfstype=${mmcrootfstype} ${cmdline}

uenvcmd=run loadall; run mmcargs; bootz ${loadaddr} - ${fdtaddr};
dtb=am335x-boneblack-wl1835mod.dtb

Thanks again

On Friday, November 6, 2015 at 12:28:50 PM UTC-5, RobertCNelson wrote:
>
> On Fri, Nov 6, 2015 at 11:26 AM, E Mag > 
> wrote: 
> > Hi, 
> > 
> > I'm trying to get a boot splash to show by overwriting 
> > /drivers/video/logo/logo_linux_clut_224.ppm and rebuilding the kernel 
> (using 
> > version 3.14.56-ti-r78). This worked well in Kernel 3.8, but now it 
> doesn't 
> > show the logo at boot, just a console output of the boot process. 
> > 
> > Is there something different or additional config that has to be done 
> for 
> > kernel 3.14? I have the logo enabled in the .config and tried adding 
> "splash 
> > quiet" as kernel parameters in uEnv.txt, but I still only get a console 
> > display. 
> > 
> > Any ideas would be great! 
>
> Did you set: 
>
> console=tty0 ? 
>
> in your bootargs? 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cannot get linux logo (splash) to show correctly in Kernel 3.14-ti

2015-11-06 Thread Robert Nelson 
On Fri, Nov 6, 2015 at 11:26 AM, E Mag  wrote:
> Hi,
>
> I'm trying to get a boot splash to show by overwriting
> /drivers/video/logo/logo_linux_clut_224.ppm and rebuilding the kernel (using
> version 3.14.56-ti-r78). This worked well in Kernel 3.8, but now it doesn't
> show the logo at boot, just a console output of the boot process.
>
> Is there something different or additional config that has to be done for
> kernel 3.14? I have the logo enabled in the .config and tried adding "splash
> quiet" as kernel parameters in uEnv.txt, but I still only get a console
> display.
>
> Any ideas would be great!

Did you set:

console=tty0 ?

in your bootargs?

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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Cannot get linux logo (splash) to show correctly in Kernel 3.14-ti

2015-11-06 Thread E Mag 
Hi,

I'm trying to get a boot splash to show by overwriting 
/drivers/video/logo/logo_linux_clut_224.ppm and rebuilding the kernel 
(using version 3.14.56-ti-r78). This worked well in Kernel 3.8, but now it 
doesn't show the logo at boot, just a console output of the boot process.

Is there something different or additional config that has to be done for 
kernel 3.14? I have the logo enabled in the .config and tried adding 
"splash quiet" as kernel parameters in uEnv.txt, but I still only get a 
console display.

Any ideas would be great!

Thanks

-- 
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.

[beagleboard] Re: beaglebone black ADC via Bonescript slow? - how to improve or alternatives?

2015-11-06 Thread TJF 
Hi Istvan,

I think your understanding of Av, OpD and SaD is pretty much right. For 
detailed information check the TI ARM335x Technical Reference Manual 
, chapter 12 (TSC_ADC_SS).

Note: the parameters of pruio_new() are used to pre-configure steps 1 to 8 
(for AIN-0 to AIN-7).

BR

-- 
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.

[beagleboard] RE: beaglebone black ADC via Bonescript slow? - how to improve or alternatives?

2015-11-06 Thread Istvan Biro 
  Hello,

 

Thank you for your mail. 

The problem is that I do not know any FreeBasic whatsoever ...  so I am trying 
hard to figure out the C equivalent. 

 

I think I got it to work now, I can sample at 7us for a single channel in RB 
mode.  

 

I would like to ask about the parameters of pruio_new(ACT, Av, OpD, SaD) :

 

-   Av: documentation says it is averaging. Say, if I set this to 4, 
does it mean that -during one sampling time- each AINx gives one output (each), 
but this output is the mean of 4 samples taken from the same AIN? E.g. for 
Av=4:AIN0_out = (AIN0_sample1+ …+AIN0_sample4)/4  and:AIN1_out = 
(AIN1_sample1+ …+AIN1_sample4)/4 and ……  ?

 

-   OpD: open delay : “number of clock cycles the ADC waits between setting 
the step configuration and sending the start of conversion signal” --- Is this 
the so called ‘settling time’ of a DAQ device, i.e., the time we wait for the 
internal capacitor to charge/for the voltage signal to settle before we 
actually make a measurement? 

 

 

-   SaD : “sets the sample delay, which is the number of clock cycles the 
ADC waits before starting (the width of the start of conversion signal). It 
specifies the number of clock cycles between the single conversion processes” – 
I do not see why this should not be always 0…. Is there a reason for it, maybe 
it defines how far in time the measurements will be made if averaging ‘Av’ is 
used?

 

Sorry if the questions are somewhat stupid –  if you had some good sources 
where these are taken from/understood/explained, I’d appreciate.

 

 

Thanks a lot!

 

Best regards,

Istvan

 

 

 

From: TJF [mailto:jeli.freih...@gmail.com] 
Sent: 27 October 2015 19:12
To: BeagleBoard
Cc: jeli.freih...@gmail.com; istvan.biro.m...@gmail.com
Subject: Re: beaglebone black ADC via Bonescript slow? - how to improve or 
alternatives?

 

Hi!

Am Dienstag, 27. Oktober 2015 19:16:51 UTC+1 schrieb Istvan Biro:

   Hello,

 

Thank you for your reply! 

 

I have installed the package successfully and am now looking at the code 
(examples) to figure out the usage. I find this very hard… now I am looking at 
example io_input.c, but there is very little comments included and I do not 
understand most of the code (e.g., commands like FD_ZERO(&set);

  FD_SET(STDIN_FILENO, &set);


FD_... function family is C stuff (I'm no C expert). Look them up in C 
documentation.

  -- or why pruio_new(PRUIO_DEF_ACTIVE, 0x98, 0, 1) has these arguments, etc… 
). 


Sorry, this is a bug (wrong parameter order). For full speed us

pruio_new(PRUIO_DEF_ACTIVE, 0, 0, 0)

 

Is there any description for more naive users?  I mean something to explain how 
to use this library?


Did you find the online documentation 
 ?

Tasks I would like to do: 

--switch to MM or RB, 

-- read analog values (how to access buffer?) – theoretically 3 functions…


MM mode is used in example triggers.bas (FreeBASIC only since it uses graphics).

RB mode example isn't included in version 0.2. You can find pre-published code 
by searching this forum for "rb_file". Find also information on how to 
re-compile version 0.2 in order to use rb_file (and trigger.bas) at full speed.

BR

-- 
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.

Re: [beagleboard] DWA-131 driver fail using beaglebone as wi-fi hostspot

2015-11-06 Thread Jason Kridner 
Can you include the dmesg log? Are you sure br0 is how the adapter was named?

> On Nov 6, 2015, at 9:18 AM, marcoscaixetaso...@gmail.com wrote:
> 
> I'm trying to create a wi-fi hostspot using a beaglebone black rev-C and 
> DWA-131 nano wi-if adapter.
> 
> I followed this article to install the driver: 
> http://www.linux-hardware-guide.com/2013-11-16-d-link-dwa-131-n300-usb-wifi-adapter
> 
> And this project do setup the hostapd: https://github.com/jekader/hostapd-rtl
> 
> But when I try to start I'm getting the following error:
> 
> Configuration file: /etc/hostapd/hostapd.conf
> drv->ifindex=4
> l2_packet_init: ioctl[SIOCGIFINDEX]: No such device
> no br0 interface , let l2_sock_recv==l2_sock_xmit=0x0x51648
> ioctl[SIOCSIWMODE]: Operation not supported
> Could not set interface to mode(3)!
> Could not set interface to master mode!
> rtl871xdrv driver initialization failed.
> rmdir[ctrl_interface]: No such file or directory
> My hostapd.conf is:
> 
> interface=usb0
> driver=rtl871xdrv
> bridge=br0
> ssid=NETWORK-NAME
> channel=1
> wmm_enabled=0
> wpa=1
> wpa_passphrase=NETWORK-PASSWORD
> wpa_key_mgmt=WPA-PSK
> wpa_pairwise=TKIP
> rsn_pairwise=CCMP
> auth_algs=1
> macaddr_acl=0
> Hostapt version? Driver's name or config?
> 
> ps: I'm not confortable because my network interface for the wi-fi is usb0 
> instead of wlan0. Is a driver issue?
> 
> -- 
> 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.

[beagleboard] DWA-131 driver fail using beaglebone as wi-fi hostspot

2015-11-06 Thread marcoscaixetasousa 


I'm trying to create a wi-fi hostspot using a beaglebone black rev-C and 
DWA-131 nano wi-if adapter.

I followed this article to install the driver: 
http://www.linux-hardware-guide.com/2013-11-16-d-link-dwa-131-n300-usb-wifi-adapter

And this project do setup the hostapd: 
https://github.com/jekader/hostapd-rtl

But when I try to start I'm getting the following error:

Configuration file: /etc/hostapd/hostapd.conf
drv->ifindex=4
l2_packet_init: ioctl[SIOCGIFINDEX]: No such device
no br0 interface , let l2_sock_recv==l2_sock_xmit=0x0x51648
ioctl[SIOCSIWMODE]: Operation not supported
Could not set interface to mode(3)!
Could not set interface to master mode!
rtl871xdrv driver initialization failed.
rmdir[ctrl_interface]: No such file or directory

My hostapd.conf is:

interface=usb0
driver=rtl871xdrv
bridge=br0
ssid=NETWORK-NAME
channel=1
wmm_enabled=0
wpa=1
wpa_passphrase=NETWORK-PASSWORD
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
auth_algs=1
macaddr_acl=0

Hostapt version? Driver's name or config?

ps: I'm not confortable because my network interface for the wi-fi is usb0 
instead of wlan0. Is a driver issue?

-- 
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.

[beagleboard] DWA-131 driver fail using beaglebone as wi-fi hostspot

2015-11-06 Thread Marcos Sousa 


I'm trying to create a wi-fi hostspot using a beaglebone black rev-C and 
DWA-131 nano wi-if adapter.


I followed this article to install the driver: 
http://www.linux-hardware-guide.com/2013-11-16-d-link-dwa-131-n300-usb-wifi-adapter


And this project do setup the hostapd: 
https://github.com/jekader/hostapd-rtl


But when I try to start I'm getting the following error:

Configuration file: /etc/hostapd/hostapd.conf
drv->ifindex=4
l2_packet_init: ioctl[SIOCGIFINDEX]: No such device
no br0 interface , let l2_sock_recv==l2_sock_xmit=0x0x51648
ioctl[SIOCSIWMODE]: Operation not supported
Could not set interface to mode(3)!
Could not set interface to master mode!
rtl871xdrv driver initialization failed.
rmdir[ctrl_interface]: No such file or directory


My hostapd.conf is:

interface=usb0
driver=rtl871xdrv
bridge=br0
ssid=NETWORK-NAME
channel=1
wmm_enabled=0
wpa=1
wpa_passphrase=NETWORK-PASSWORD
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
auth_algs=1
macaddr_acl=0


Hostapt version? Driver's name or config?


ps: I'm not comfortable because my network interface for the wi-fi is usb0 
instead of wlan0. Is a driver issue?

-- 
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.

Re: [beagleboard] Looking for SPI Salve configuration and sample code for testing on BBB with kernel 3.8.13

2015-11-06 Thread ravi . hpv 
Hi John,

Thank you for your valuable information.

I will try your suggestion but still i have to learn kernel driver 
development. 

Please share the slave sample code whenever it completes.

Regards,
Ravi 

On Wednesday, November 4, 2015 at 12:24:13 AM UTC+5:30, john3909 wrote:
>
> Hi Ravi,
>
> My best advise is to look at Starterware example code for McSPI. This will 
> give you some idea on how to configure and use the McSPI at the register 
> level. When that is familiar, then reading through the /drivers/dma/edma.c 
> code will be easier to understand. You will notice that the McSPI is 
> configures in slave mode by default and then the driver configures it to 
> master mode. The complete SPI framework in Linux is based on master mode 
> and there is as far an I know no slave mode framework. I am looking at 
> using McSPI with EDMA so that packets received by the McSPI are stored in a 
> ping-pong buffer and then using a callback, process that buffer. At the 
> moment this is WIP and I’m hoping with some help from others on the mailing 
> list I will get this done shortly. 
>
> Regards,
> John
>
>
>
>
> On Nov 3, 2015, at 4:22 AM, ravi...@gmail.com  wrote:
>
>
> Hi ALL,
>
> Please provide your support on this BBB SPI slave configuration and sample 
> code for kernel 3.8.13 .
>
> I have done Master mode communication  with slave memory device, but i 
> want to communication with two BBB. one is mater and another is salve 
> device.
>
> I guess present kernel doesn't support slave mode but i don't know kernel 
> modification to change master to salve mode.
>
> Please provide your valuable inputs to me.
>
> Thank you in advance
>
> Regards
> Ravi 
>
> -- 
> 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...@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.

Re: [beagleboard] SPI BBB Master, BBB Slave

2015-11-06 Thread ravi s 
Hi John,

Yes I can use UART or other protocol to achieve same data communication.
But I'm working for client . They should require spi slave in kernel.  So
struggling to get it up. We asked TI also regarding this but they also
don't have any sample code for testing spi slave..

Regards
Ravi
On 5 Nov 2015 23:46, "John Syne"  wrote:

> Hi Ravi,
>
> This is something I’m currently working on. However, for your application,
> why do you need to use SPI? Surely you could use IP Sockets or UART to
> achieve the same thing. Also, McASP has both master and slave support
> through the sound subsystem. Specifically you can use spdif_receiver.c and
> spdif_transmitter.c codecs to do what you need as show in[1]. Thereafter,
> implement something similar to alsa arecord and aplay to send and receive
> data from a user space app.
>
> [1] http://processors.wiki.ti.com/index.php/Sitara_Linux_Audio_DAC_Example
>
> Regards,
> John
>
>
>
>
> On Nov 4, 2015, at 2:29 AM, ravi@gmail.com wrote:
>
> Hi,
>
> I'm trying to setup SPI slave mode with same above method and
> changed OMAP2_MCSPI_MODULCTRL_MS set to 0 for slave mode.
>
> i'm facing issue in master mode and slave both on sckl pin configuration.
>
> http://elinux.org/BeagleBone_Black_Enable_SPIDEV in this link why sckl
> pin is configured as INPUT 0x33 but it will work with same configuration if
> i change it to OUTPUT it doesn't work with any slave device and no clock on
> that pin.
>
> Please anyone clarify this doubt and issues.
>
> For slave mode i tried to change OMAP2_MCSPI_MODULCTRL_MS bit in driver
> file spi_omap2_mcspi.c but no use. still its master only.
>
> Please provide any suggestion or exact procedure.
>
> Thank you in advance.
>
> Regard s
> Ravi
>
> On Thursday, September 18, 2014 at 5:45:47 AM UTC+5:30, phil...@gmail.com
> wrote:
>>
>>
>> I am having issues with SPI between two BBB that may be simple to solve.
>> I have spidev_test loopback working on each board but am having problems
>> connecting the two.
>>
>> spi0 master dts:
>>   0x150 0x10  /* spi0_sclk, OUTPUT_PULLUP | MODE0 */
>>   0x154 0x30  /* spi0_d0, INPUT_PULLUP | MODE0 */
>>   0x158 0x10  /* spi0_d1, OUTPUT_PULLUP | MODE0 */
>>   0x15c 0x10  /* spi0_cs0, OUTPUT_PULLUP | MODE0 */
>>
>> spi slave dts:
>>   0x150 0x30  /* spi0_sclk, INPUT_PULLUP | MODE0 */
>>   0x154 0x10  /* spi0_d0, OUTPUT_PULLUP | MODE0 */
>>   0x158 0x30  /* spi0_d1, INPUT_PULLUP | MODE0 */
>>   0x15c 0x30  /* spi0_cs0, INPUT_PULLUP | MODE0 */
>>
>>
>> The oscilloscope shows activity when spi0_sckl (P9_17) is not connected
>> but nothing when P9_17 is connected between both boards.
>> I am sending bytes from master with the command: echo 1 > /dev/spidev1.0
>>
>> I need 4-8mbit/sec transfer, is this achievable by bit banging over GPIO
>> and would that be a viable alternative to getting SPI working?
>>
>>
> --
> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/jQ1LH6IDH1A/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

Re: [beagleboard] C compiler(s) for Beaglebone Black (BBB)

2015-11-06 Thread Chad Baker 

gcc is included in every OS that I have worked with on the BBB.
Have you googled python and interrupts? There is a LOT of info out there.
Also, you can take articles for the RPi (I know) and adapt.
Chad

On 11/5/2015 1:15 PM, jship1...@gmail.com wrote:
What Linux C complier toolset(s) that can be used directly on the BBB? 
I am thinking that I might have to use the host PC (Ubuntu15,xx) and 
then load the compiled code on to the BBB (???).
I like the Python tools (no compilation needed) but I am not sure how 
one can incorporate using the interrupts (on the ARM) in a
Python environment development environment. So, I am thinking there 
are C complier tools that will work for the BBB.
My first BBB is scheduled to arrive Friday and I am looking forward to 
start using the BBB.



--
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.



--
Chad Baker Memphis, TN

--
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.

Re: [beagleboard] Re: I2C driver by PRU

2015-11-06 Thread Micka 
Thx GianFranco,

I managed to understand your code, which is well made.

My first test was to verify if I was able to compile the program and see if
something goes out of the I2C 1.

And yes it works ! I saw something on the scope.

Now, I have to modify your code to be able to use the AD7997.


Thank you very much for your code and the comment !


Micka,

Le mer. 4 nov. 2015 à 12:47, Gianfranco Rosso 
a écrit :

> hello Micka,
>
>  in attach you'll find the archive with both asm and c sources: I've
> translated comments to english in order to make them more readable.
>
> I've used https://github.com/beagleboard/am335x_pru_package as develop
> enviroment.
>
> This example uses 2 I/O expanders (one for inputs and the other for
> outputs) and simply echoes the inputs to the outputs: the echo is done into
> the c code (that runs in the ARM core) with data passed to and for the PRU
> into the RAM.
> The PRU manages the I2C1 module for init and refresh the I/O expanders.
>
> Mux setting of I2C pins have to be done before execution.
> It can't be done by the PRU itself because the CONTROL_MODULE can't be
> accessed (writing) by the PRU.
> So I used cape-universal and a shell script for that.
>
>
>
> On Sunday, November 1, 2015 at 10:46:26 PM UTC+1, Mickae1 wrote:
>>
>> Hi,
>>
>> I'm interested by what you have done.  I want to use i2c to read analog
>> value from a component.
>>
>> The first solution that I found was to bitbang the i2c. But you, you use
>> the i2c driver which is nice.
>>
>> Could you give us the peace of asm code that you use to interface with
>> the MCP23017. And if you have the c code also it would be great.
>>
>> ( if possible, also the part of you managed to activate the module by
>> writing MODULEMODE field into register CM_PER_I2C1_CLKCTRL register and
>> also the code that wait for IDLEST field to confirm that module is ready).
>>
>> Micka,
>>
>>
>> --
> 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.

Re: [beagleboard] kernel updates: 4.1.12-ti-r27 (BBB all spi/spidev users rejoice)

2015-11-06 Thread Micka 
Hi Robert,

about this bug, are you also fixing the kernel am33x-rt-v4.1 ?

I'm interested also by the spi in the kernel am33x-rt-v4.1.


Micka,


Le jeu. 5 nov. 2015 à 15:47, Robert Nelson  a
écrit :

> The journey into spi & dma..
>
> So for awhile now, we've had a bug for spi users, where the system
> would hardlock at the "160" byte threashold:
>
> debian@beaglebone:~$ sudo dd if=/dev/zero of=/dev/spidev1.0 bs=159 count=1
> 1+0 records in
> 1+0 records out
> 159 bytes (159 B) copied, 0.000508833 s, 312 kB/s
> debian@beaglebone:/sys$ dd if=/dev/zero of=/dev/spidev1.0 bs=160 count=1
> ^C
>
> (hangs..)
>
> "160" happens to be a the magic number where DMA takes over from PIO
> mode...
>
> Well as of yesterday:
>
> debian@beaglebone:~$ sudo dd if=/dev/zero of=/dev/spidev1.0 bs=320 count=1
> 1+0 records in
> 1+0 records out
> 320 bytes (320 B) copied, 0.00266366 s, 120 kB/s
>
> So here's the deal, it looks to be a spi/overlay bug, as we don't seem
> to get the correct dma tx/rx channels..
>
> What interesting, when the "spi" node is enabled in the main dtb:
>
>
> https://github.com/RobertCNelson/dtb-rebuilder/blob/4.1-ti/src/arm/am335x-boneblack-spi0.dts#L120-L137
>
> it works fine in dma mode...
>
> So with "4.1.12-ti-r27" spi-dma is now disabled..
>
> *btw:
>
> Late last night i wrote a better fix (will be r28)
>
> where you can disable "spi-dma" via the dt option:
>
> ti,pio-mode;
>
>
> https://github.com/beagleboard/bb.org-overlays/commit/48d33d4d22f284103db83626b343724cf18c578d
>
> 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 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.

Re: [beagleboard] Problems with CANBus at BBB

2015-11-06 Thread mojtaba moghimi 
Hello William
I have the same problem as Markus has. I've done the same as Markus and I'm 
using Logic supply canbus cape. I don't see any message using candump and 
can't send any message.
I use Microchip can analyzer to send can signals to my BBB.
When I try to enable both "BB-CAN1" and "cape-CBB-Serial:r01", BBB doesn't 
let me to have them both activated at the same time and mentions P9.24 
conflict.

How should I solve this issue?
Thanks in advance.
Cheers
Mojtaba

On Monday, October 26, 2015 at 11:21:55 PM UTC+10, William Hermans wrote:
>
> You need to use a can transceiver, and properly terminate the can 
> interface. Otherwise, the can interface will not work. in our case we're 
> using the Logic supply serial / canbus cape. 
> http://www.logicsupply.com/cbb-serial/
>
> $ sudo ifconfig
> [sudo] password for william:
> 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:38317627 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:282730298 (269.6 MiB)  TX bytes:0 (0.0 B)
>   Interrupt:182
>
> $ candump -n 10 can0
>   can0  19F00302   [8]  40 44 03 13 01 01 00 00
>   can0  19F00302   [8]  41 00 00 00 00 00 00 00
>   can0  19F00302   [8]  42 00 B8 0B 00 00 00 00
>   can0  19F00302   [8]  43 00 00 00 00 02 01 00
>   can0  19F00302   [8]  44 00 00 00 00 00 00 00
>   can0  19F00302   [8]  45 00 00 B8 0B 00 00 00
>   can0  19F00302   [8]  46 00 00 00 00 00 03 01
>   can0  19F00302   [8]  47 00 00 00 00 00 00 00
>   can0  19F00302   [8]  48 00 00 00 B8 0B 00 00
>   can0  19F00302   [8]  49 00 00 00 00 00 00 FF
>
>
> On Mon, Oct 26, 2015 at 6:04 AM, Robert Nelson  > wrote:
>
>> On Sun, Oct 25, 2015 at 7:49 AM,  > 
>> wrote:
>> > Hi out there,
>> >
>> > hope someone can help me to activate the CAN Bus interface at Beaglebone
>> > Black. I describe shortly what I
>> > have done so far
>>
>> The can interface works fine, what did you use to interface the bbb's
>> pins to your can network?
>>
>> 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 beagleboard...@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.