[beagleboard] POV (Peripheral of Vision) Display ; Displaying temperature and time

[J_ROBO]

Hi All,

I'm in the process of creating a POV (Peripheral of VIsion ) display with 
the Beaglebone Black. I intend on displaying current time and temperature. 
I'm trying to figure out a way to access the time on the Beaglebone and 
values from my temperature sensor in C so I can display this information. 
Perhaps storing the numbers as integers? Any input would be helpful. Thank 
You.

-- 
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] not enabling (uart/spi) cape in arch-linux from uEnv.txt

[Sandip Patil]

hello everyone,

I have enbled uart/spidev cape from uEnv.txt file from /boot/uboot in 
debian.

i newly installed arch-linux on BBB

but in boot partition uEnv.txt file content only one line 
optargs=coherent_pool=1M

i have tried to load .dtbo(uart/spidev) file from here (like from debian) 
but not loaded.
cape_enable=capemgr.enable_partno=BB-SPIDEV1
cape_enable=capemgr.enable_partno=BB-UART1

how edit or add any content to uEnv.txt file like in debian to enable cape 
@ boot
how can i do uEnv.txt file same as debian

i followed below link to to install arch-linux 
http://archlinuxarm.org/platforms/armv7/ti/beaglebone-black

-- 
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] not enbling spi/uart cape from uEnv.txt in arch-linux

[Sandip Patil]

hello everyone,

I have enbled uart/spidev cape from uEnv.txt file from /boot/uboot in 
debian.

i newly installed arch-linux on BBB

but in boot partition uEnv.txt file content only one line 
optargs=coherent_pool=1M

i have tried to load .dtbo(uart/spidev) file from here (like from debian) 
but not loaded.
cape_enable=capemgr.enable_
partno=BB-SPIDEV1
cape_enable=capemgr.enable_partno=BB-UART1

how edit or add any content to uEnv.txt file like in debian to enable cape 
@ boot
how can i do uEnv.txt file same as debian

i followed below link to to install arch-linux
http://archlinuxarm.org/platforms/armv7/ti/beaglebone-black

-- 
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: New BeagleBone Black Metal Enclosure

[Rigid Concepts]

A cape should not hit the cable gland.  We modified the cable gland so that 
it is shorter and doesn't extend over the BBB.

The cable gland can be removed if you don't want it installed.

Please let me know if you have any more questions.  We welcome 
questions/comments.  We want the best design possible.  If this isn't it, 
we'll do another one!

Have a great week,



Johnny

On Thursday, April 9, 2015 at 10:05:15 PM UTC-5, William Hermans wrote:
>
> *One question though: Does the cable management get in the way of the 
>> cape?*
>
>
> This is something I was wondering about too. But at the time I did not 
> want to come off as really negative. 
>
> One thing I was curious about though is that the text says "black" but the 
> pictures on amazon shows green?
>
> Plus the cost is kind of high, but made in USA which can be a plus. 
>
> On Thu, Apr 9, 2015 at 7:21 PM, > 
> wrote:
>
>> On Thursday, April 2, 2015 at 5:40:58 PM UTC-4, Rigid Concepts wrote:
>>
>>> I've read topics on this board in the past and have dabbled with the 
>>> BeagleBone Black and love it as a device.  We decided to develop a new 
>>> innovative enclosure for the BeagleBone Black and we have.  
>>>
>>
>> Looks good.  Plenty of room for a cape. One question though: Does the 
>> cable management get in the way of the cape?  It kind of looks like the 
>> cape PCB might interfere with the inside of the cable bezel/grommet (or 
>> whatever that thing is called).
>>
>> -W
>>
>>  -- 
>> 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.

[beagleboard] Kernel 3.14 and LCD cape

[Keith Conger]

Hi All,

I'm trying to enable support for my 4DCAPE_43T LCD, UART1 and disable HDMI 
in kernel 3.14. 

I've modified "am335x-boneblack.dts" by commenting out HDMI, and all UARTs 
except UART1 then include the dtsi for my LCD.  I rebuilt the the dtb file 
and copied it to /boot/dtbs/.  Its appears to using mine since only UART1 
is enabled versus the default which has them all enabled.  However the LCD 
never turns on 

I'm new to device trees in 3.14, am I doing something wrong?  I have 
attached my .dts file.

Thanks,
Keith

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


am335x-boneblack.dts
Description: Binary data

[beagleboard] I can't read GPIO port on BBxM RevC2

[Erkan Güzeler]

Hi everyone,
I'm using BBxM Rev C2 board and trying to read GPIO_159 that is in 
expansion header. I successfully used it as output(Turn On LED and TURN OFF 
LED). But I can't read anything on this port. 

I used this steps;

   cd /sys/class/gpio/
   echo 159 > export 
   cd /sys/class/gpio/gpio159
   echo "in" > direction 
   cat value   // this always response me "0" zero. 

   I'm normally using pull up button so that it has high level when it's 
not pressed. But I always take "0" value when I write "cat value" command 
on terminal.

Has anybody idea?

Best Regards. 


-- 
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] Enable RTC function in TPS65950

[Hao Nguyen]

Hi,
Have anyone ever enable to use RTC function of TPS65950.
I can't enable it.
Plzz help me!

-- 
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] Generating a pulse using the beagle bone

[ggnamita]

Hello everybody,

I am new to this forum, so kindly some silly mistakes of mine.. I am trying 
to generate a pulse on the beaglebone board which is to be given to 
specific pins of the MCP23017.. I have previously worked on the raspberry 
pi and know that there is the pigpio library available that could do this 
for you.. http://abyz.co.uk/rpi/pigpio/python.html#gpio_trigger.. Is there 
something like this for the beaglebone black ?

Thank you,
Kind Regards,
Namita

-- 
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: Need help getting Debian to sync the system clock with my RTC on boot (and not with rtc-omap)

[whellenthal]

Did you find a solution? I'm having the same problem. It seems that during 
boot the /etc/timestamp is used to set the hwclock. I suspected the 
boot_script.sh file but after changing it the problem remained. I can set 
the timestamp during a shutdown but I would rather see a more general 
solution. 

 Regards,
Wim

On Wednesday, June 11, 2014 at 4:24:02 AM UTC+2, Justin Morgan wrote:
>
> I am using a BBB running the new Debian image. I have connected a DS1307 
> RTC (via a "Tiny RTC I2C modules" breakout board) to I2C2, and have added 
> "cape_enable=capemgr.enable_partno=BB-BONE-RTC" to uEnv.txt such that my 
> BBB does see this RTC as /dev/rtc1.
>
> I want to synchronize the system clock from *this* RTC on boot (and not 
> the BBB's rtc-omap that is registered as /dev/rtc0), so I modified 
> /etc/init.d/hwclock.sh such that HCTOSYS_DEVICE=rtc1. I thought that should 
> do it... *after all, I was able to get a Raspberry Pi running Raspian to 
> synchronize with a DS1307 on boot following these instructions: *
> *http://blog.elevendroids.com/2012/12/setting-up-hardware-rtc-in-raspbian/* 
> 
>
> However, my BBB keeps synchronizing with rtc-omap on boot... and doesn't 
> seem to be running hwclock.sh, either (time after boot is back in May, not 
> the current time as I confirm by sudo hwclock -r -f /dev/rtc1).
>
> So where is Debian actually synchronizing the time in the boot process, 
> and how do I tell it I want to use my battery-backed clock?
>

-- 
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] Wireless mesh networking

[abu . fahruddin]

hi...
Just try to implement mesh network by using raspberry and my usb wifi 
dongle is edimax ew 7811un with realtek rtl8192cu. But I still cannot ping 
each other refer to explanation that you ever use rtl7811cu, could you 
help me what the problem so I cannot ping each othe. I have been setting 
all node with same ssid and channel but still cannot connect 



> I had evaluated babel, OLSR, and Batman-adv two years ago on a test 
> network of 5 beaglebones to demonstrate wifi mesh networking. I concluded 
> Batman-adv was the one to explore further. I was using Robert Nelson's 
> ubuntu (3.2 kernel) on beaglebone white then. I had tried three different 
> long range wifi dongles from Alpha. The black one (http://www.amazon.com/ 
> 
> Alfa-AWUS036NHA-Wireless-Adaptor-Compatible/dp/B004Y6MIXS) has Atheros 
> ar9271 chipset and has the best kernel support on Beaglebone. The more 
> common model is based on realtek rtl8192cu chipset. Back then rtl8192cu 
> driver on arm was not anywhere near ready. I would still strongly prefer 
> AR9271 based wifi dongle today. I had to use a USB Y-cable to make sure 
> there is sufficient current during boot time to power up the wifi dongle. 
> BB only has a USB host port, so this was a bit inconvenient. I resorted 
> to tie the 5V and GND lines of the USB to a 5V supply to ensure smooth 
> boot. 
>
> With a 14" omnidirectional antenna and tx-power cranked up full, I was 
> able to sustain decent connectivity at ~300 meter per hop during field 
> demonstration. 
>
> For batman-adv, I configured every node's bat0 interface on 192.168.50.x 
> subnet. (wlan0 has its own static address assignment in 
> /etc/network/interfaces)
>  
> When starting a mesh node, a startbatman.sh is called that has the 
> following:
> modprobe batman-adv
> ifconfig wlan0 mtu 1528
> batctl if add wlan0
> ifconfig bat0 192.168.50.218 up
> batctl gw client
> ip route del default
> ip route add default via 192.168.50.1
>
> On the node serving as gateway through its eth0, I had the additional 
> lines for Network Address Translation.
> sysctl net.ipv4.ip_forward=1
> iptables --table nat --append POSTROUTING --out-interface eth0 -j 
> MASQUERADE
> iptables --append FORWARD --in-interface bat0 -j ACCEPT
>
> You could add an @reboot line in /etc/crontab that calls your startbatman.sh 
> on reboot every time.
>
> I have not updated this since the switch to 3.8 kernel, but I am pretty 
> sure it would work on the current Debian image. I would recommend you use 
> the 3.14 kernel to benefit from the more reliable USB.
>
> George
>
> On Fri, Sep 26, 2014 at 2:30 PM, Brian Anderson  > wrote:
>
>> Hi all,
>>
>> I am interested in setting up a wireless mesh network using a collection 
>> of BBBs (and possibly other devices).  Does anyone have experience setting 
>> up a wireless mesh network using BBB?
>>
>> I am not really interested in a so-called "wireless distribution system" 
>> that is used to extend an SSID across a wide area using wireless mesh 
>> networking.  I am much more interested in setting up a network of 
>> cooperating nodes that talk with each other (and to the internet via a 
>> gateway/mesh portal connected simultaneously to the internet and the mesh).
>>
>> In particular, I'm interested in:
>>
>>   * What distro and kernel are you using?
>>   * Ideally this would be with one of RCNs Debian images, but if not, 
>> I'm interested in what you might have used.
>>   * If you have done something with a Linux based system other than a 
>> BBB, I'd like to know about that too.
>>   * What mesh routing protocol was used?  Batman, Babel/AHCP, HWMP, OLSR, 
>> ...
>>   * Steps to configure the mesh network and gateway.
>>   * Did you use 802.11s?  If so, presumably using the 802.11s support in 
>> the kernel?
>>   * WiFi chipset that was used (presumably supporting mesh mode).  
>> SOFTMAC or HARDMAC?
>>
>> I have researched the topic fairly extensively and can probably set 
>> something up via trial and error myself.  Prior to diving into that, I 
>> wanted to see if anyone has already done some work with wireless mesh 
>> networking and BBB (or something else) and would be willing to share their 
>> experience and knowledge!
>>
>> Thanks in advance.
>>
>> Cheers,
>>
>> ba
>>
>>  -- 
>> 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 
t

[beagleboard] LCD screen

[Julian Gold]

We have attached an LCD screen (4G) to our BBB rev C, and the serial port 
/dev/ttyO2 has vanished. Is this expected? Also the boot time has become 
ridiculous - it take about 4 minutes (including multiple reboots) to get to 
the (Debian) desktop. Can this be fixed?

-- 
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: PMIC not shutting down after CPU power off

[Brad Andersen]

Check out the following:

Bone VDD_3V3EXP Disable Issues

BBB battery connected doesn't powerdown VDD_3V3EXP P9_3/4.

BBB operation with battery

There's a bunch more references, but this describes a hardware fix.

On Monday, April 13, 2015 at 12:14:50 PM UTC-7, jean@dazedstudio.com 
wrote:
>
> Hi everyone,
>
> we are running for our project a BBB on Debian (stock image and updated 
> kernel to bone71) on a battery setup. In our circuit, we have an external 
> RTC that wakes up the BBB on a set interval to do reading and then close 
> back down. Our problem is that sometimes the CPU shuts down but not the 
> PMIC (TPS65217). At that moment, any signal on the power button is ignored 
> but the reset button still works. On the BBB, the power LED is lit up, but 
> all user LEDs are closed down.
>
> Has any one had simliar problems or is there any known fix for PMIC 
> problems? 
>
> Thank you for your help.
>

-- 
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] Jessie debian lxqt

[Jaime Fernández-Caro Belmonte]

Hello Robert,

Is this connman also killing Jessie Console configuration (ETH-WifI)? Since 
a Month or Two I´m having problems with WiFi configuration and also with 
Eth under /etc/network/interfaces.
It is installed by default for some reason now?

Thanks!

El lunes, 16 de marzo de 2015, 1:38:04 (UTC+1), RobertCNelson escribió:
>
> On Sun, Mar 15, 2015 at 7:34 PM, Ray Madigan  > wrote: 
> > I have an installation of Jessie lxqt running and am having difficulty 
> > getting it to use a static ip address. 
> > 
> > in /etc/network/interfaces I have 
> > 
> > auto eth0 
> > iface eth0 inet static 
> > address 192.168.1.113 
> > netmask 255.255.255.0 
> > network 192.168.1.0 
> > broadcast 192.168.1.255 
> > gateway 192.168.1.1 
> > dns-nameservers 184.16.33.54 184.16.4.22 
> > 
> > my router has a reserved address for this mac address 
> > and it worked on the angstrom and ubuntu images. 
> > I am clearly doing something wrong. 
>
> remove connman... 
>
> It takes over eth0.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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] Jessie debian lxqt

[Robert Nelson]

On Tue, Apr 14, 2015 at 12:43 PM, Jaime Fernández-Caro Belmonte
 wrote:
> Hello Robert,
>
> Is this connman also killing Jessie Console configuration (ETH-WifI)? Since
> a Month or Two I´m having problems with WiFi configuration and also with Eth
> under /etc/network/interfaces.
> It is installed by default for some reason now?

Yeah, it's installed by default too now on the console images.

Feel free to remove it asap..

The 2 minute delays on bootup when eth0 wasn't plugged in forced me to
install connman by default..

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] Jessie debian lxqt

[Jaime Fernández-Caro Belmonte]

Now I understand why I could not configure WiFi...!!!
I solved ETH0 issue commenting it.

Do you think is that a bug (to be solved) on jessie? 

Thnks for your answer!

El martes, 14 de abril de 2015, 19:50:24 (UTC+2), RobertCNelson escribió:
>
> On Tue, Apr 14, 2015 at 12:43 PM, Jaime Fernández-Caro Belmonte 
> > wrote: 
> > Hello Robert, 
> > 
> > Is this connman also killing Jessie Console configuration (ETH-WifI)? 
> Since 
> > a Month or Two I´m having problems with WiFi configuration and also with 
> Eth 
> > under /etc/network/interfaces. 
> > It is installed by default for some reason now? 
>
> Yeah, it's installed by default too now on the console images. 
>
> Feel free to remove it asap.. 
>
> The 2 minute delays on bootup when eth0 wasn't plugged in forced me to 
> install connman by default.. 
>
> 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] Jessie debian lxqt

[Jaime Fernández-Caro Belmonte]

By the way the 2 minute delay on boot is also solved replacing this: auto 
eth0 By this: allow-hotplug eth0


Best regards!


El martes, 14 de abril de 2015, 20:21:21 (UTC+2), Jaime Fernández-Caro 
Belmonte escribió:
>
> Now I understand why I could not configure WiFi...!!!
> I solved ETH0 issue commenting it.
>
> Do you think is that a bug (to be solved) on jessie? 
>
> Thnks for your answer!
>
> El martes, 14 de abril de 2015, 19:50:24 (UTC+2), RobertCNelson escribió:
>>
>> On Tue, Apr 14, 2015 at 12:43 PM, Jaime Fernández-Caro Belmonte 
>>  wrote: 
>> > Hello Robert, 
>> > 
>> > Is this connman also killing Jessie Console configuration (ETH-WifI)? 
>> Since 
>> > a Month or Two I´m having problems with WiFi configuration and also 
>> with Eth 
>> > under /etc/network/interfaces. 
>> > It is installed by default for some reason now? 
>>
>> Yeah, it's installed by default too now on the console images. 
>>
>> Feel free to remove it asap.. 
>>
>> The 2 minute delays on bootup when eth0 wasn't plugged in forced me to 
>> install connman by default.. 
>>
>> 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] Jessie debian lxqt

[Robert Nelson]

On Tue, Apr 14, 2015 at 1:35 PM, Jaime Fernández-Caro Belmonte
 wrote:
> By the way the 2 minute delay on boot is also solved replacing this: auto
> eth0 By this: allow-hotplug eth0

Unless eth0 is plugged in at boot..

Then it doesn't always get an ip address.

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] modify uart driver in BBB

[chinna4emb]

Hello All,
I am newbie to this group as well as usage of BBB. I am trying to write my 
own uart driver using BBB for prototype purpose. I Googled a lot, but no 
where a clear cut implementation is mentioned. I gone through many training 
material too. Here are the few things where I want clarity to proceed 
further..

1) where we get full source code of BBB( i got one link but it does contain 
many more arch - https://github.com/beagleboard/linux )
2) which device name should i use in my UART driver? and how should I 
select the device name?
3) what is the reference source code for existing UART driver in the BBB?
4) should I do any changes in Device Tree to create my new driver?
5) should I use DMA allways with UART driver?
6) How should my driver access the hardware data, i.e. for example in case 
of receive data, how this will access the Receive Buffer data? 

it will be a great pleasure if some helps me out to solve this problem. 
Best Regards
-Shiva



-- 
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] modify uart driver in BBB

[Robert Nelson]

On Tue, Apr 14, 2015 at 11:42 AM,   wrote:
>
> Hello All,
> I am newbie to this group as well as usage of BBB. I am trying to write my
> own uart driver using BBB for prototype purpose. I Googled a lot, but no
> where a clear cut implementation is mentioned. I gone through many training
> material too. Here are the few things where I want clarity to proceed
> further..
>
> 1) where we get full source code of BBB( i got one link but it does contain
> many more arch - https://github.com/beagleboard/linux )
> 2) which device name should i use in my UART driver? and how should I select
> the device name?
> 3) what is the reference source code for existing UART driver in the BBB?
> 4) should I do any changes in Device Tree to create my new driver?
> 5) should I use DMA allways with UART driver?
> 6) How should my driver access the hardware data, i.e. for example in case
> of receive data, how this will access the Receive Buffer data?

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/tty/serial/8250/8250_omap.c

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] Re: modify uart driver in BBB

[Lee Crocker]

If by "driver" you mean Linux driver, then the existing one is called 
"omap-serial", and you can find it in the kernel source tree, It is, 
unfortunately, not well documented or maintained. I think the TI employees 
who used to maintain it are gone. I applaud your enthusiasm to fix it, but 
I suspect it's quite a bit more of an undertaking than you imagine.

On Tuesday, April 14, 2015 at 12:48:54 PM UTC-7, chinn...@gmail.com wrote:
>
>
> Hello All,
> I am newbie to this group as well as usage of BBB. I am trying to write my 
> own uart driver using BBB for prototype purpose. I Googled a lot, but no 
> where a clear cut implementation is mentioned. I gone through many training 
> material too. Here are the few things where I want clarity to proceed 
> further..
>
> 1) where we get full source code of BBB( i got one link but it does 
> contain many more arch - https://github.com/beagleboard/linux )
> 2) which device name should i use in my UART driver? and how should I 
> select the device name?
> 3) what is the reference source code for existing UART driver in the BBB?
> 4) should I do any changes in Device Tree to create my new driver?
> 5) should I use DMA allways with UART driver?
> 6) How should my driver access the hardware data, i.e. for example in case 
> of receive data, how this will access the Receive Buffer data? 
>
> it will be a great pleasure if some helps me out to solve this problem. 
> Best Regards
> -Shiva
>
>
>
>

-- 
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: Generating a pulse using the beagle bone

[Lee Crocker]

Adafruit has a Python library for GPIO. You also have to enable them at the 
hardware/OS levels.

https://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/installation-on-ubuntu

On Tuesday, April 14, 2015 at 8:01:46 AM UTC-7, ggna...@gmail.com wrote:
>
> Hello everybody,
>
> I am new to this forum, so kindly some silly mistakes of mine.. I am 
> trying to generate a pulse on the beaglebone board which is to be given to 
> specific pins of the MCP23017.. I have previously worked on the raspberry 
> pi and know that there is the pigpio library available that could do this 
> for you.. http://abyz.co.uk/rpi/pigpio/python.html#gpio_trigger.. Is 
> there something like this for the beaglebone black ?
>
> Thank you,
> Kind Regards,
> Namita
>

-- 
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: modify uart driver in BBB

[Robert Nelson]

On Tue, Apr 14, 2015 at 4:09 PM, Lee Crocker  wrote:
> If by "driver" you mean Linux driver, then the existing one is called
> "omap-serial", and you can find it in the kernel source tree, It is,
> unfortunately, not well documented or maintained. I think the TI employees
> who used to maintain it are gone. I applaud your enthusiasm to fix it, but I
> suspect it's quite a bit more of an undertaking than you imagine.

I wonder what your 'definition' of mainintained really is?

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/tty/serial/omap-serial.c

ps.. "omap-serial" has been depreciated for "8250_omap" so going
foward "omap-serial" will become un-maintained..

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] Jessie debian lxqt

[William Hermans]

@Robert

Any idea what is causing this ? I've yet to experience this myself, but I
always use ethernet + static IP. Did I mention that I dislike connman with
a passion ?

On Tue, Apr 14, 2015 at 11:46 AM, Robert Nelson 
wrote:

> On Tue, Apr 14, 2015 at 1:35 PM, Jaime Fernández-Caro Belmonte
>  wrote:
> > By the way the 2 minute delay on boot is also solved replacing this: auto
> > eth0 By this: allow-hotplug eth0
>
> Unless eth0 is plugged in at boot..
>
> Then it doesn't always get an ip address.
>
> 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] Jessie debian lxqt

[Robert Nelson]

On Tue, Apr 14, 2015 at 4:32 PM, William Hermans  wrote:
> @Robert
>
> Any idea what is causing this ? I've yet to experience this myself, but I
> always use ethernet + static IP. Did I mention that I dislike connman with a
> passion ?

In Jessie, I've been playing around with, [ifplugd] this afternoon..
It seems to be doing what i want..

allow-hotplug eth0
iface eth0 inet dhcp

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] Jessie debian lxqt

[Jaime Fernández-Caro Belmonte]

Thanks for your answer again Robert.

Is this issue Kernel relevant? I mean, could be caused because Debian 
Jessie is supposed to be 3.16 by default 
and BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-09-2gb.img has 
3.14 on it for BBB?

BRegards.

-- 
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] Jessie debian lxqt

[Robert Nelson]

On Tue, Apr 14, 2015 at 5:06 PM, Jaime Fernández-Caro Belmonte
 wrote:
> Thanks for your answer again Robert.
>
> Is this issue Kernel relevant? I mean, could be caused because Debian Jessie
> is supposed to be 3.16 by default and
> BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-09-2gb.img has 3.14 on
> it for BBB?

Nope, the 'issue' goes back to the "Lenny" days, networking was changed as such:

The login (screen/prompt) only shows up after a valid network
connection is created on (auto eth0), or it'll wait 2 minutes...

For bb.org, i've been using these tools to bring up eth0 over
(/etc/network/interfaces)

wheezy: wicd
jessie: connman

More Background, we don't see this 2minute time out in ubuntu, as i
patch it out:

https://github.com/RobertCNelson/omap-image-builder/blob/master/scripts/chroot.sh#L403

However, in debian, the 2 minute delay is complied in the code.

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] Jessie debian lxqt

[Robert Nelson]

On Tue, Apr 14, 2015 at 4:40 PM, Robert Nelson  wrote:
> On Tue, Apr 14, 2015 at 4:32 PM, William Hermans  wrote:
>> @Robert
>>
>> Any idea what is causing this ? I've yet to experience this myself, but I
>> always use ethernet + static IP. Did I mention that I dislike connman with a
>> passion ?
>
> In Jessie, I've been playing around with, [ifplugd] this afternoon..
> It seems to be doing what i want..
>
> allow-hotplug eth0
> iface eth0 inet dhcp

yeah... Connman still works better then ifplugd:

After booting (without eth0 plugged in), then plug in i still get:

Apr 14 21:54:59 arm dhclient[195]: No DHCPOFFERS received.
Apr 14 21:54:59 arm dhclient[195]: No working leases in persistent
database - sleeping.
Apr 14 21:54:59 arm ifup[190]: No DHCPOFFERS received.
Apr 14 21:54:59 arm ifup[190]: No working leases in persistent
database - sleeping.

with:

allow-hotplug eth0
iface eth0 inet dhcp

and:

/etc/default/ifplugd

INTERFACES="eth0"
(or)
HOTPLUG_INTERFACES="eth0"

eth0 plugged in at power on: boots fast, eth0 works
eth0 un-plugged in at power on: boots fast, (eth0 doesn't auto connect
when connected..)

Yuck..

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] Re: Wireless mesh networking

[janszymanski12345]

Hi,

Have a look here http://processors.wiki.ti.com/index.php/Contiki-6LOWPAN 
(That's similar to what I'm working on now)

Good Luck
Jan

On Saturday, September 27, 2014 at 7:30:02 AM UTC+10, Brian Anderson wrote:
>
> Hi all,
>
> I am interested in setting up a wireless mesh network using a collection 
> of BBBs (and possibly other devices).  Does anyone have experience setting 
> up a wireless mesh network using BBB?
>
> I am not really interested in a so-called "wireless distribution system" 
> that is used to extend an SSID across a wide area using wireless mesh 
> networking.  I am much more interested in setting up a network of 
> cooperating nodes that talk with each other (and to the internet via a 
> gateway/mesh portal connected simultaneously to the internet and the mesh).
>
> In particular, I'm interested in:
>
>   * What distro and kernel are you using?
>   * Ideally this would be with one of RCNs Debian images, but if not, 
> I'm interested in what you might have used.
>   * If you have done something with a Linux based system other than a 
> BBB, I'd like to know about that too.
>   * What mesh routing protocol was used?  Batman, Babel/AHCP, HWMP, OLSR, 
> ...
>   * Steps to configure the mesh network and gateway.
>   * Did you use 802.11s?  If so, presumably using the 802.11s support in 
> the kernel?
>   * WiFi chipset that was used (presumably supporting mesh mode).  SOFTMAC 
> or HARDMAC?
>
> I have researched the topic fairly extensively and can probably set 
> something up via trial and error myself.  Prior to diving into that, I 
> wanted to see if anyone has already done some work with wireless mesh 
> networking and BBB (or something else) and would be willing to share their 
> experience and knowledge!
>
> Thanks in advance.
>
> Cheers,
>
> ba
>
>

-- 
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] Powering down a Beaglebone black that is being powered from a LiPo battery

[Matt Maher Peterson]

Hi,

Working a beaglebone black that I am trying to power both with a wall wart 
and with LiPo battery thru the TPS functionality.  I have all the power 
working well except that I cannot get the damn thing to power down from the 
power switch on the board.  Holding the switch down for 8 seconds causes 
the thing to power down momentarily but then it power back up.  Any idea 
how to work around this?

One piece of information I found with respect to this issue was on this 
forum where someone said:

...
Regarding the lithium battery pack idea, it's a good one 


*except for one little issue with the bone where a rework is required in 
order to power down into TPS65217 OFF or SLEEP modes when a battery is 
connected due to SYS voltage staying present and the way 3.3V_EXP is 
generated.* So
long as you don't want to power off with the battery still connected
there's no issue, though.

Anyone know what this workaround is or where I could find info on it? 

Cheers!

MMP

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