[beagleboard] Re: can't load device tree on Debian jessie 8.6 with kernel version 4.4.43-ti-r84

[Ashwini Bhat]

I tried going past chapter 9 into 10 but now I am getting an error with 
prumodin.  Ideally I want to know how run a very simple pru set-up that I 
can debug...but going through what ti has to offer, it all done through 
code composer.  Doesn't seem like you used it.  Either way I was trying to 
give yours a shot a and here is where I ended up.
root@beaglebone:/home/debian/pru-software-support-package# ls /usr/bin/ | 
grep pru
abspru
acpiapru
arpru
asmpru
cgpru
clistpru
clpru
dempru
dispru
embedpru
hexpru
ilkpru
libinfopru
lnkpru
nmpru
ofdpru
optpru
prumodin
prumodout
prumsg
strippru
xrefpru
root@beaglebone:/home/debian/pru-software-support-package# ls /usr/bin/ | 
grep prumod
prumodin
prumodout
root@beaglebone:/home/debian/pru-software-support-package# ls
examples  labsMakefile  PRU-Package-v5.0-Manifest.html
include   libpru_cape  ReadMe.txt
root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# ls
AM335x_PRU.cmdmapfile1  PRU_PID_0.c  resource_table_empty.h
MakefilePRU_IO_1.cPRU_PID_0.obj  result
mapfile0PRU_IO_1.obj  resource_table_1.h  user_space
root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# make clean
make: Nothing to be done for 'clean'.
root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# make
clpru -I/usr/share/ti/cgt-pru/includeSupportPackage 
-I/usr/share/ti/cgt-pru/include -I/usr/share/ti/cgt-pru/lib 
--hardware_mac=on -O2 -v3 --display_error_number --endian=little 
PRU_PID_0.c -z -i/usr/share/ti/cgt-pru/lib -i/usr/share/ti/cgt-pru/include 
-i/usr/share/ti/cgt-pru/includeSupportPackage 
-i/usr/share/ti/cgt-pru/includeSupportPackage/am335x --reread_libs 
--stack_size=0x100 --heap_size=0x100 
--library=/usr/share/ti/cgt-pru/lib/rpmsg_lib.lib -m=mapfile0 
./AM335x_PRU.cmd -o ./result/am335x-pru0-fw --library=libc.a 

clpru -I/usr/share/ti/cgt-pru/includeSupportPackage 
-I/usr/share/ti/cgt-pru/include -I/usr/share/ti/cgt-pru/lib 
--hardware_mac=on -O2 -v3 --display_error_number --endian=little PRU_IO_1.c 
-z -i/usr/share/ti/cgt-pru/lib -i/usr/share/ti/cgt-pru/include 
-i/usr/share/ti/cgt-pru/includeSupportPackage 
-i/usr/share/ti/cgt-pru/includeSupportPackage/am335x --reread_libs 
--stack_size=0x100 --heap_size=0x100 
--library=/usr/share/ti/cgt-pru/lib/rpmsg_lib.lib -m=mapfile1 
./AM335x_PRU.cmd -o ./result/am335x-pru1-fw --library=libc.a 

gcc ./user_space/prumsg.c -o /usr/bin/prumsg
cd result
cp ./result/am335x-pru0-fw /lib/firmware
cp ./result/am335x-pru1-fw /lib/firmware
root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# ls
AM335x_PRU.cmdmapfile1  PRU_PID_0.c  resource_table_empty.h
MakefilePRU_IO_1.cPRU_PID_0.obj  result
mapfile0PRU_IO_1.obj  resource_table_1.h  user_space
root@beaglebone:/home/debian/pru-pid-motor/software/pru_firmware# prumodin
/usr/bin/prumodin: line 9: echo: write error: No such device
/usr/bin/prumodin: line 10: echo: write error: No such device

Any ideas as to what going on?

On Sunday, January 29, 2017 at 1:26:34 PM UTC-8, Ashwini Bhat wrote:
>
> Ok I did as your procedure says and followed chapter 9. All the outputs 
> you were looking for in your procedure showed up.  Now is there a simple 
> program I can run to see if the PRU is working and if it is able to toggle 
> a GPIO pin?  I can just see if a pin is being toggled by putting a scope on 
> it.  
>
> On Sunday, January 29, 2017 at 4:44:48 AM UTC-8, Greg wrote:
>>
>> I wouldn't update the kernel at this time.  Yes, try the procedure and 
>> see what happens.  I think you will be successful.  If not, we can work 
>> through it.
>>
>> That kernel is the TI version and it should be good to go for sure.  If 
>> not, there are problems we are not going to solve without help!
>> It's still not clear to me the differences between the TI and the Bone 
>> kernels.  The TI kernels definitely support the latest Remoteproc.
>>
>> If you don't need GUI, stick with the IOT image.  I've had very good luck 
>> with it.
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3cc59d8f-ca6f-4512-acd1-6fe5c96eaf5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Selecting closest 802.11s wireless mesh network to join

['woody stanford' via BeagleBoard]

This idea might not make too much sense at first...

Get a NEO6M GPS module connected to a UART on the BBB. Write a 
quick-and-dirty 2D pythagorean NEMA-compliant routine that determines the 
distance to each hotspot and then connect to the one that makes the most 
sense (since radio frequency fields are basically circular on the ground).

A nice side effect is your moving device wouldn't be "promiscuous" if it 
was out of range of your networks.

Just and idea.


On Tuesday, January 24, 2017 at 5:11:42 PM UTC-7, Utku Ozgur wrote:
>
>
> Hello,
>
> I am trying to find a way to make a Beaglebone Black device (powered by an 
> external battery) that I am moving near 2 mesh networks join the mesh 
> network with the best signal. I am able to join to the mesh network I want 
> manually by typing the commands given here: 
> https://github.com/o11s/open80211s/wiki/HOWTO. Is there a way to make 
> this selection and joining process automatically? I thought that I can do 
> the selection by writing a shell script, but I wanted to make sure that 
> there is no other solution easier than the solution I found.
>
> Thank you,
>
> Utku
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9e62ef1f-f0d9-4bfa-b686-f83599fe2e53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PRU cycle counter overflow

['woody stanford' via BeagleBoard]

Interesting problem. I agree with the clock idea.

How I would do it is by looking holistically at the overall situation and 
getting a timer interrupt function to periodically look at the cycle 
counter and see if its over like , and if it is call the code that 
recalibrates it before it maxes out.

Maybe I'm saying the same thing here.

On Saturday, December 17, 2016 at 4:06:08 PM UTC-7, Amr Alanwar wrote:
>
> HI All
>
> Is there a way to get an interrupt when there is PRU cycle counter 
> overflow ?
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/47be7e43-65a5-4fa1-b5c3-4a0d4415c876%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Serial Communication with BBB

['woody stanford' via BeagleBoard]

OK, the civilized way to do this stuff. It's called 0.1" header, ok? You do 
the traces on single-sided presensitized DIY PCB board and you solder the 
header on the down side. Then you have all your p8 and p9 signals broken 
out. Then the whole issue about where do I put all this stuff goes 
awayyou just mount it and connect it on the board.

You just pop in your BBB upside down using your headers as the mount. Then 
case it.

Voila.

On Sunday, July 31, 2016 at 4:17:41 AM UTC-7, Dror Lugasi wrote:
>
> hey guys,
> i am new to BBB and i need to use it for serial communication: reading 
> data from IMU and controlling motor drivers according to the readings.
>
> what is the best (easiest and fastest) way to do this? 
>
> the beagle is running as a stand alone PC with screen and a keyboard and 
> mouse.
> i haven't got any experience with coding serial communication, i just know 
> the basics, so i am also looking for a good source to read about it.
> is the Cloud9 that comes with it good for this application? and in what 
> language is it best? python? js? or maybe c++?
> a reference with explanation on how to receive and send data via the UART 
> and CAN ports is the best solution that i am after.
>
> the UART1,2,4 are already configured in ttyO1/2/4. but i wasn't able to 
> initialize the CAN ports.
>
> thanks for helping! 
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ff7b4b10-5eee-495f-9a8d-3195f225d890%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Serial Communication with BBB

['woody stanford' via BeagleBoard]

Best and fastest? Yes, yes.

Use C, namely GCC. We are men here.

OK, what you do is do it in hardware. Select a nice set of glue translating 
your TTL to 3.3v which the BBB uses. Use SSR chips or just plain logic 
chips to do this.

Next you'll be implementing quite a bit of hardware so get some 
presensitized board and ferric chloride and some cheap Chinese breadboards 
for designing. etc. etc. Mouser or Digikey is your new best friend. Connect 
your IMU via the glue to the UARTs on your BBB. Set it up bidirectional as 
you will need to configure your IMU (ie. both TX and RX). Set your sampling 
at about 10 to 100 hz with an "attitude engine" reading on your IMU 
(x,y,z,vx,vy,vz) not the raw signals (that's so 2000's).

OK, motor control. Real simple. PWM aka pulse width modulation. What you 
want to do is break out your PWM to a slave MCU (via BBB's UARTS) like a 
PIC16Fx and use software-implemented, crystal controlled PWM on your MCU. 
Then you 2 or 3 stage it (SSR, logic or driver) with quick circuitry to 
your MOSFETs (don't forget the backward diode or you'll damage your FETs 
and remember that FET's usually ground out the back so make sure you use a 
separate heat sink for each FET, some caps in there somewhere might be nice 
too).

Then use the BBB to crunch the numbers. Basically this set up transfers 
your underlying algorithm to a programming domain from a hardware one.

What are you building btw? A drone?


On Sunday, July 31, 2016 at 4:17:41 AM UTC-7, Dror Lugasi wrote:
>
> hey guys,
> i am new to BBB and i need to use it for serial communication: reading 
> data from IMU and controlling motor drivers according to the readings.
>
> what is the best (easiest and fastest) way to do this? 
>
> the beagle is running as a stand alone PC with screen and a keyboard and 
> mouse.
> i haven't got any experience with coding serial communication, i just know 
> the basics, so i am also looking for a good source to read about it.
> is the Cloud9 that comes with it good for this application? and in what 
> language is it best? python? js? or maybe c++?
> a reference with explanation on how to receive and send data via the UART 
> and CAN ports is the best solution that i am after.
>
> the UART1,2,4 are already configured in ttyO1/2/4. but i wasn't able to 
> initialize the CAN ports.
>
> thanks for helping! 
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9bb2089f-4ca7-45c0-a588-e559a934201c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Are Windows Driver Signings Going to be Updated?

[Robert Nelson]

On Sun, Jan 29, 2017 at 7:23 PM, Jared McIntyre  wrote:
> Unfortunately, the workaround isn't a workaround for everyone. IT departments 
> can block these settings, and in fact they can be locked at the UEFI level 
> requiring changes to UEFI settings that require a password. So, in the case I 
> described, only signed drives will work (or convincing an IT department to 
> change their policy). No amount of fiddling with bcdedit will work.
>

Updated 4 days ago:

https://github.com/beagleboard/beaglebone-getting-started/tree/master/Drivers/Windows

(and if you run: sudo apt update ; sudo apt upgrade on your beagle,
the flash drive *.img already has those updates)

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjQdzD3YSJwqUOZB7T9E%2BG%3DFavjBhLECtGU1LuuF139tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Are Windows Driver Signings Going to be Updated?

[Jared McIntyre]

Unfortunately, the workaround isn't a workaround for everyone. IT departments 
can block these settings, and in fact they can be locked at the UEFI level 
requiring changes to UEFI settings that require a password. So, in the case I 
described, only signed drives will work (or convincing an IT department to 
change their policy). No amount of fiddling with bcdedit will work.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3d7094f5-2dcc-43c2-be32-9f60c0e3ea63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB Enclosure from Netgate

['woody stanford' via BeagleBoard]

Mylar.

On Thursday, December 15, 2016 at 5:30:45 PM UTC-7, Mark wrote:
>
> Hello --
>
> Searched and found occasionally someone will post in re case/enclosure for 
> BeagleBone boards.
>
> Ordered and received an alloy case from Netgate in Austin TX. Designed for 
> BeagleBone Black. It's a nice case.
>
> http://store.netgate.com/BBB/Case.aspx
>
> Anyway, looks like they are getting out of BBB biz and are offering the 
> case for 10.95$, down from 18$. Similar in design to the former Logic 
> Supply case.
>
> Couple notes:
>
> Holes for enclosure fasteners have either some anodizing, or metal, in 
> there. So starting the fastener takes small bit of effort, on first use. Be 
> certain to chase those threads out, so no galls get on the board.
>
> Not shown in the product photos is the bottom, which allows M3 fasteners 
> to mount the enclosure to standoffs or another surface.
>
> They did a favor for me on a custom shipping request, just putting this 
> out there.
>
> Mark
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bbae68d7-98fa-425f-975c-5175af626331%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB Enclosure from Netgate

['woody stanford' via BeagleBoard]

That is nice. Serious, serious. I likey. And the price is right.

BUT I want to talk about about my dollar-store cased K150 bootleg I got 
from China (free shipping on Ebay). 2 dollar case and it looks awesome. Its 
even transparent. I'm even cool with the fact it doesn't have an RS232 
connector on it the USB works so good.

(I'm laughing so hard right now)

Go down to the dollar store and pick up a set of $1 machine screws (with 
nuts) and find a nice $1 plastic box (throw away whatever is in it). Then 
take your Harbor Freight Dremel-like tool (cutting wheel) and start cutting 
(after sharpy marking it out of course).

Have I ever mentioned how handy a Fiscar's drill is? Get oneyou will 
not be disappointed. Anyways.

But props out to ABS plastic and Altoids (don't forget to put the little 
sheet of insulator at the bottom through).



On Thursday, December 15, 2016 at 5:30:45 PM UTC-7, Mark wrote:
>
> Hello --
>
> Searched and found occasionally someone will post in re case/enclosure for 
> BeagleBone boards.
>
> Ordered and received an alloy case from Netgate in Austin TX. Designed for 
> BeagleBone Black. It's a nice case.
>
> http://store.netgate.com/BBB/Case.aspx
>
> Anyway, looks like they are getting out of BBB biz and are offering the 
> case for 10.95$, down from 18$. Similar in design to the former Logic 
> Supply case.
>
> Couple notes:
>
> Holes for enclosure fasteners have either some anodizing, or metal, in 
> there. So starting the fastener takes small bit of effort, on first use. Be 
> certain to chase those threads out, so no galls get on the board.
>
> Not shown in the product photos is the bottom, which allows M3 fasteners 
> to mount the enclosure to standoffs or another surface.
>
> They did a favor for me on a custom shipping request, just putting this 
> out there.
>
> Mark
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/17880c48-32d7-471a-b170-95f7ca908900%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Are Windows Driver Signings Going to be Updated?

['woody stanford' via BeagleBoard]

https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/JvklF3O5mHs

On Wednesday, January 4, 2017 at 5:44:19 PM UTC-7, Jared McIntyre wrote:
>
> The Window's drivers haven't been install-able without turning off sign 
> checking for several months. I have a number of machines that I can't do 
> that on due to IT policy. Is there going to be an updated installer with 
> updated signings?
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/82525d42-f48e-4b1b-bf73-fcf603c905cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: correct connection of an opto-coupler

['woody stanford' via BeagleBoard]

I agree with my fellow posters that using an optoisolator here is not the 
solution.

The solution is to use an isolated (preferably optoisolated) logic gate. In 
this case an OR gate. The critical thing to mention here is that the BBB 
uses 3.3V stuff which isn't TTL (which is 5V+ for on and 0V for off). Which 
makes it interesting because most of the stuff you'll connect is still TTL.

Here is a link to A chip (not the right one but has a lot of the 
characteristics we are looking forand the price is 
right). 
http://www.mouser.com/ProductDetail/Texas-Instruments/CD4075BE/?qs=sGAEpiMZZMtYFXwiBRPs05FGKgXIMzep

What you do is you connect up the power (GND and VCC) and tie one input of 
an OR gate to ground and then the other input to your BBB. Then you take 
the output of the gate as your isolated output. Most of these logic chips 
have such amazing isolation that you can do this, I think. And if you blow 
it you buy a cheapo plastic DIP socket and replace the logic chip like a 
fuse.

This is such a great question at its core, I think I'm going to shop for an 
inexpensive DIP chip that performs isolation AND the converstion from 3,3v 
to 5v necessary for any civilized conversation about BBB connectivity.

Thoughts?

On Tuesday, November 8, 2016 at 7:39:33 AM UTC-7, mzimmers wrote:
>
> Hi, all - I thought I posted something about this last week, but a search 
> doesn't turn it up, so here goes again.
>
> I'm working through Molloy's book, and trying to build the opto-coupler 
> circuit in chapter 6. I'm not a hardware guy, so I'm feeling my way along 
> here. The diagram doesn't show specifically how to wire up the four 
> connectors. I looked at the data sheet for the device, which was helpful, 
> but still doesn't get me home.
>
> I could trial and error, but I've already fried one component, and they're 
> not easy to come by in my area. Can anyone help clarify this configuration?
>
> This is the specific device: opto-coupler 
> 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3a382fb9-78cf-45fd-8f67-211bd6c5a1e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Phasors calculation using libpruio

[John Syne]

> On Jan 29, 2017, at 2:17 PM, Renzo Fabián  wrote:
> 
> I understand there are many ways to solve the problem.
> 
> 1. Using PRUs via libpruio suggested by TJF.
> 2. Using DMA via iio driver suggested by John.
Search for iio_generic_buffer, which is in mainline under tools/iio. This will 
show you how to read the IIO buffer from a user space app. 

Alternatively, you can use iiod which you will find in libiio, which allows you 
to read the samples remotely. You can use IIO_Oscilloscope to connect to iiod. 

https://wiki.analog.com/resources/tools-software/linux-software/iio_oscilloscope
 


Regards,
John

> 3. Using a external ADC suggested by Woody.
> 
> I understand the solution 1.
> 
> John, can you send a example of ADC sampling and DMA?
> 
> For 3, I don't want to use a external ADC for this project. But, for others 
> I'll have in mind this solution. This solution would be possible with RPi3?
> 
> Thanks you.
> 
> 
> El viernes, 27 de enero de 2017, 2:10:27 (UTC-2), Renzo Fabián escribió:
> 
> I have the following C code's parts that uses tables of sins and cosins to 
> calculate a fundamental phasor of 60 Hz electrical system using 16 samples 
> per cycle (960 Sps):
> 
> float cosins[]={1, 0.92388, 0.70711, 0.38268, 0, -0.38268, -0.70711, 
> -0.92388, -1,
>-0.92388, -0.70711, -0.38268, 0, 0.38268, 0.70711, 0.92388};
>   
> float sins[]={0, 0.38268, 0.70711, 0.92388, 1, 0.92388, 0.70711, 0.38268, 0,
>  -0.38268, -0.70711, -0.92388, -1, -0.92388, -0.70711, 
> -0.38268};
> 
> ...
> 
> for(i=0; i <16; i++){
>ret_r=x[15-i]*cosins[i]+ret_r;
>ret_i=x[15-i]*sins[i]+ret_i;
>}
> 
> return 0.088388*ret_r -0.088388*ret_i*I;
> 
> Is it possible to perform this using the libpruio in order to read 6 analog 
> inputs? If yes? What is the best way to implement it if other operations were 
> need, i.e. compute the division of 2 phasors.
> 
> 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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/a37f290e-bff8-4456-be21-bd72825b1bf0%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/E873E8C4-96B4-4A1B-9ED9-5C6014628D26%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to know which beagleblackBone version I am using?

['woody stanford' via BeagleBoard]

Command prompt? What you do flash it with MSDOS lol?

On Monday, August 15, 2016 at 9:25:39 PM UTC-7, Raulp wrote:
>
>
> Hi, 
> How can I know from the command prompt which BBB version(Rev A,B or C?) I 
> am using?Or by looking at its PCB?
> Thanks in advance !
> Rgds,
> Rp
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2f3d4929-70de-482b-b7a5-52285932baa7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UART connection question

['woody stanford' via BeagleBoard]

Ok, but seriously, these are great questions.

Standard for this kind of stuff is python (apparently). But I think C.

No such thing as a wireless UART in that a UART stands for "Universal 
Asychronous Receiver/Transmitter" and its a chip that outputs a TTL signal 
that requires wires to transmit the information to other TTL devices. BUT I 
get the point of your question.

If you are looking for a wireless link I would recommend wifi with a BBBW. 
You just have unerring faith that the TCP/IP stack is there. And then you 
just communicate over that. However the Zigbee guys might have a point.

(faux arrogantly) I mean let's be real, right? ;)

On Tuesday, January 19, 2016 at 10:01:41 AM UTC-7, Michael Williams wrote:
>
> I have a few questions regarding the UARTs on the Beaglebone Black & Green.
>
> What is a good resource for writing programs for the uarts? Which 
> programming language would be the best to write uart applications in C++, 
> Python, or Java?
>
> Is it possible to send data between the uarts without them being 
> physically connected?  
>
> Thank you in advance for your help.
>
> Mike
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c0c07763-9fd2-4367-8cc1-ce0c880b7bc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

I repeated everything: same problem. BBB does not boot anymore!? Did I do
something wrong here?
Please advise, regards,
Harke

On 29 January 2017 at 21:36, Harke Smits  wrote:

> Unfortunately that crashes the system. all four blue leds on
> I will try and reflash from mem card.
> H
>
> On 29 January 2017 at 21:13, Robert Nelson 
> wrote:
>
>> On Sun, Jan 29, 2017 at 2:04 PM, Harke Smits  wrote:
>> > Hello Robert,
>> >
>> > Thanks for your reaction. I understand /dev/ttyOx has been replaced by
>> > /dev/ttySx (x from 0-5). However the rest is far beyond my level of
>> skill. I
>> > do not know what dt overlay I load. I just flashed the latest Debian
>> > version. And then updated all (sudo apt-get update). I do not
>> understand C,
>> > just a bit of Python. I need to use the UARTs 2 and 4. and of course a
>> > number of I/O bits. I hope that is still the same? I can and are
>> prepared to
>> > move to the latest versions, just need to know what to do
>>
>> btw, you can also just do:
>>
>> cd /opt/scripts/tools/
>> git pull
>> sudo ./update_kernel.sh --bone-channel --stable
>> sudo reboot
>>
>> and then you can return to the classic 3.8.13 based kernel you are use
>> too..
>>
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHmciaYAMNbeW%2BzHUyMr35JwYu05wyWY44T2XOj0VfyrcJFptg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UART connection question

['woody stanford' via BeagleBoard]

And futher more, I will have you know that UART's only speak TTL 
(definition f' i_ve volts PLUS) attached thus with insulator.copper hashtag 
blinking blinkin WIRE.

On Tuesday, January 19, 2016 at 10:01:41 AM UTC-7, Michael Williams wrote:
>
> I have a few questions regarding the UARTs on the Beaglebone Black & Green.
>
> What is a good resource for writing programs for the uarts? Which 
> programming language would be the best to write uart applications in C++, 
> Python, or Java?
>
> Is it possible to send data between the uarts without them being 
> physically connected?  
>
> Thank you in advance for your help.
>
> Mike
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/db79761e-9888-44be-ac8f-6e039fc3dc94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UART connection question

['woody stanford' via BeagleBoard]

C is the ONLY language I will have you know, sir.

And I have to agree with Karl's assessment that your "physically connected" 
comment was patently moronic. lol. :D

On Tuesday, January 19, 2016 at 10:01:41 AM UTC-7, Michael Williams wrote:
>
> I have a few questions regarding the UARTs on the Beaglebone Black & Green.
>
> What is a good resource for writing programs for the uarts? Which 
> programming language would be the best to write uart applications in C++, 
> Python, or Java?
>
> Is it possible to send data between the uarts without them being 
> physically connected?  
>
> Thank you in advance for your help.
>
> Mike
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/38737862-1f90-4e0c-959b-d5e91faa7bad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Phasors calculation using libpruio

[Renzo Fabián]

I understand there are many ways to solve the problem.

1. Using PRUs via libpruio suggested by TJF.
2. Using DMA via iio driver suggested by John.
3. Using a external ADC suggested by Woody.

I understand the solution 1.

John, can you send a example of ADC sampling and DMA?

For 3, I don't want to use a external ADC for this project. But, for others 
I'll have in mind this solution. This solution would be possible with RPi3?

Thanks you.


El viernes, 27 de enero de 2017, 2:10:27 (UTC-2), Renzo Fabián escribió:
>
>
> I have the following C code's parts that uses tables of sins and cosins to 
> calculate a fundamental phasor of 60 Hz electrical system using 16 samples 
> per cycle (960 Sps):
>
> float cosins[]={1, 0.92388, 0.70711, 0.38268, 0, -0.38268, -0.70711, 
> -0.92388, -1,
>-0.92388, -0.70711, -0.38268, 0, 0.38268, 0.70711, 0.92388};
>   
> float sins[]={0, 0.38268, 0.70711, 0.92388, 1, 0.92388, 0.70711, 0.38268, 
> 0,
>  -0.38268, -0.70711, -0.92388, -1, -0.92388, -0.70711, 
> -0.38268};
>
> ...
>
> for(i=0; i <16; i++){
>ret_r=x[15-i]*cosins[i]+ret_r;
>ret_i=x[15-i]*sins[i]+ret_i;
>}
>
> return 0.088388*ret_r -0.088388*ret_i*I;
>
> Is it possible to perform this using the libpruio in order to read 6 
> analog inputs? If yes? What is the best way to implement it if other 
> operations were need, i.e. compute the division of 2 phasors.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a37f290e-bff8-4456-be21-bd72825b1bf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Cannot enable UART's

['woody stanford' via BeagleBoard]

This DOESN'T WORK but as far as I got.

I thought I would super-duper UART-ize my board. Still waiting for somebody 
to tell me "how it is done" kinda thing.

https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/JvklF3O5mHs

On Friday, December 30, 2016 at 3:45:35 AM UTC-7, truni wrote:
>
> Hi all 
>
> I cannot enable UARTS no matter what I try.
>
> See attached for the commands I am sending, has anybody come across this 
> problem before?
>
> My distro information :
>
> Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l 
> GNU/Linux
>
> I just cannot get this to work, no does editing uEnv.txt...
>
> Please help :)
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7853a621-d2ce-42dd-b14b-3e2f03b724f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: can't load device tree on Debian jessie 8.6 with kernel version 4.4.43-ti-r84

[Ashwini Bhat]

Ok I did as your procedure says and followed chapter 9. All the outputs you 
were looking for in your procedure showed up.  Now is there a simple 
program I can run to see if the PRU is working and if it is able to toggle 
a GPIO pin?  I can just see if a pin is being toggled by putting a scope on 
it.  

On Sunday, January 29, 2017 at 4:44:48 AM UTC-8, Greg wrote:
>
> I wouldn't update the kernel at this time.  Yes, try the procedure and see 
> what happens.  I think you will be successful.  If not, we can work through 
> it.
>
> That kernel is the TI version and it should be good to go for sure.  If 
> not, there are problems we are not going to solve without help!
> It's still not clear to me the differences between the TI and the Bone 
> kernels.  The TI kernels definitely support the latest Remoteproc.
>
> If you don't need GUI, stick with the IOT image.  I've had very good luck 
> with it.
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/749b25eb-ab1c-40ac-ac73-b16404b07558%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PWM generation using libpruio

['woody stanford' via BeagleBoard]

Break out your PWM on to a PIC16Fx (using it crystal-controlled with 
software-based PWM by counting the clock cycles per instruction) and then 
use UART to control it.

An alternative fix, but it does give you nice isolation in the process.

Depending on how powerful your servos are, you might have to 2 or 3 stage 
it with SSR's (solid state relay chips) or direct to MOSFET (Irfz24N is a 
nice cheap one, and use some beefy fast rectifiers going backward to null 
out the inductive blowback from the coils on stop).

Hobby servos can be controlled direct from a standard TTL level output btw.

On Tuesday, November 29, 2016 at 10:30:41 PM UTC-7, Akshay Gahlot wrote:
>
> I want to use for PWM generation to control servo motor. The problem i m 
> facing is :
>
> To enable libpruio i m using this dts file 
>
> https://github.com/jadonk/cape-firmware/blob/master/arch/arm/boot/dts/BB-BONE-PRU-01-00A0.dts
>
> To enable the pwm pin i m using cape-universaln 
>
> https://github.com/cdsteinkuehler/beaglebone-universal-io/blob/master/cape-universaln-00A0.dts
>
> These both files are kind of conflicting with each other as if one is 
> loaded to slots then other is not loading.
>
> If i do not load the cape-universaln i m not able to export the pwm pins.
>  
> Any help appreciated.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/cc6b758e-6ac8-4fa7-a722-135ada7fb6c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Phasors calculation using libpruio

['woody stanford' via BeagleBoard]

I'd break it out on a PIC16F so I got isolation from the BBB itself using 
their ADC's. Just read it in via UART. Then use the BBB to crunch the data,



On Thursday, January 26, 2017 at 9:10:27 PM UTC-7, Renzo Fabián wrote:
>
>
> I have the following C code's parts that uses tables of sins and cosins to 
> calculate a fundamental phasor of 60 Hz electrical system using 16 samples 
> per cycle (960 Sps):
>
> float cosins[]={1, 0.92388, 0.70711, 0.38268, 0, -0.38268, -0.70711, 
> -0.92388, -1,
>-0.92388, -0.70711, -0.38268, 0, 0.38268, 0.70711, 0.92388};
>   
> float sins[]={0, 0.38268, 0.70711, 0.92388, 1, 0.92388, 0.70711, 0.38268, 
> 0,
>  -0.38268, -0.70711, -0.92388, -1, -0.92388, -0.70711, 
> -0.38268};
>
> ...
>
> for(i=0; i <16; i++){
>ret_r=x[15-i]*cosins[i]+ret_r;
>ret_i=x[15-i]*sins[i]+ret_i;
>}
>
> return 0.088388*ret_r -0.088388*ret_i*I;
>
> Is it possible to perform this using the libpruio in order to read 6 
> analog inputs? If yes? What is the best way to implement it if other 
> operations were need, i.e. compute the division of 2 phasors.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2239e598-ecc5-43ef-ace8-b087c4d5e8fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Phasors calculation using libpruio

[John Syne]

Hi TJF,

The IIO ADC can sample at 800K samples per second [1]. You cannot achieve that 
sampling rate with with PRU and have it do something useful with those samples. 
 

[1] https://patchwork.kernel.org/patch/9391499/ 


I don’t see the purpose of having PRU read from /dev/iio:deviceX. This is for 
ARM only. The OP wanted to do phasor analysis which requires math not easily 
implemented on the PRU. Since the samples are already available on the ARM 
side, I suggested that the OP do phasor analysis on the ARM? 

Regards,
John




> On Jan 28, 2017, at 8:49 PM, TJF  wrote:
> 
> Hi John!
> 
> Am Sonntag, 29. Januar 2017 03:58:21 UTC+1 schrieb john3909:
> The IIO driver is faster and can achieve higher sampling rates.
> 
> The sampling rate limitation is the FiFo buffer in the TSC_ADC_SS. Both 
> drivers can operate at full speed. iio puts more load on the ARM CPU.
>  
> Also the IIO driver is easier to use because you just read from 
> /dev/iio:deviceX.
> 
> Can you please provide some PRU example code how to read from 
> /dev/iio:deviceX? iio is made for ARM side only. In contrast libpruio can 
> provide the data either for the ARM or for the second PRU.
>  
> 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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/c3607ea4-2f25-41c5-b885-54c920e7a7f2%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2EEAD11F-E727-484B-A797-358A16720757%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

Unfortunately that crashes the system. all four blue leds on
I will try and reflash from mem card.
H

On 29 January 2017 at 21:13, Robert Nelson  wrote:

> On Sun, Jan 29, 2017 at 2:04 PM, Harke Smits  wrote:
> > Hello Robert,
> >
> > Thanks for your reaction. I understand /dev/ttyOx has been replaced by
> > /dev/ttySx (x from 0-5). However the rest is far beyond my level of
> skill. I
> > do not know what dt overlay I load. I just flashed the latest Debian
> > version. And then updated all (sudo apt-get update). I do not understand
> C,
> > just a bit of Python. I need to use the UARTs 2 and 4. and of course a
> > number of I/O bits. I hope that is still the same? I can and are
> prepared to
> > move to the latest versions, just need to know what to do
>
> btw, you can also just do:
>
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh --bone-channel --stable
> sudo reboot
>
> and then you can return to the classic 3.8.13 based kernel you are use
> too..
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHmciabCvHYP4FxDHO0550Tyapb0qwZKMeiTOx5hgMdOtpwZNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Robert Nelson]

On Sun, Jan 29, 2017 at 2:04 PM, Harke Smits  wrote:
> Hello Robert,
>
> Thanks for your reaction. I understand /dev/ttyOx has been replaced by
> /dev/ttySx (x from 0-5). However the rest is far beyond my level of skill. I
> do not know what dt overlay I load. I just flashed the latest Debian
> version. And then updated all (sudo apt-get update). I do not understand C,
> just a bit of Python. I need to use the UARTs 2 and 4. and of course a
> number of I/O bits. I hope that is still the same? I can and are prepared to
> move to the latest versions, just need to know what to do

btw, you can also just do:

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-channel --stable
sudo reboot

and then you can return to the classic 3.8.13 based kernel you are use too..

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYghPc8Z7zLmyM9J1rbc-9HjDEQ_-mbWpYdscWD7_9Hj1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

Hello Robert,

Thanks for your reaction. I understand /dev/ttyOx has been replaced by
/dev/ttySx (x from 0-5). However the rest is far beyond my level of skill.
I do not know what dt overlay I load. I just flashed the latest Debian
version. And then updated all (sudo apt-get update). I do not understand C,
just a bit of Python. I need to use the UARTs 2 and 4. and of course a
number of I/O bits. I hope that is still the same? I can and are prepared
to move to the latest versions, just need to know what to do
Regards,
Harke

On 29 January 2017 at 20:03, Robert Nelson  wrote:

> On Sun, Jan 29, 2017 at 12:50 PM, Harke Smits  wrote:
> > Hello Dennis,
> >
> > That is a very relevant reaction! Thanks a lot! Now I have to find out
> what
> > port is connected with UART 2 (and others I need). I found ttyO0 and
> > ttyO3 working, i.e. no errors reported. But also no idea to what UART
> they
> > are connected. Definitely not UART2, I am using.
> > Apart from the fact that I cannot believe that someone deliberately
> messed
> > up with the serial ports. Compatibility with earlier scripts is
> > completely gone!
> > Can anyone supply me with the altest UART mapping? Or better yet:
> re-install
> > the old mapping?
>
> Well, userspace changed from: /dev/ttyOx -> /dev/ttySx, by default we
> have a udev rule setup to allow you to use /dev/ttyOx
>
> However if you are loading a device tree overlay from the 3.8.13 era,
> you need to update the device tree node name.
>
> for example usart 2: (today)
>
> https://github.com/beagleboard/bb.org-overlays/
> blob/master/src/arm/BB-UART2-00A0.dts#L47
>
> usart2 (yesterday with 3.8.13)
>
> https://github.com/beagleboard/linux/blob/3.8/
> firmware/capes/BB-UART2-00A0.dts#L41
>
> As you might have other issues causing the blockage, please add the output
> off
>
> dmesg | grep bone
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHmciabhdh92RjbOCgcq-wiyuN7fOf%3D%3DVy-MoXf_Td_7vYYTLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Robert Nelson]

On Sun, Jan 29, 2017 at 12:50 PM, Harke Smits  wrote:
> Hello Dennis,
>
> That is a very relevant reaction! Thanks a lot! Now I have to find out what
> port is connected with UART 2 (and others I need). I found ttyO0 and
> ttyO3 working, i.e. no errors reported. But also no idea to what UART they
> are connected. Definitely not UART2, I am using.
> Apart from the fact that I cannot believe that someone deliberately messed
> up with the serial ports. Compatibility with earlier scripts is
> completely gone!
> Can anyone supply me with the altest UART mapping? Or better yet: re-install
> the old mapping?

Well, userspace changed from: /dev/ttyOx -> /dev/ttySx, by default we
have a udev rule setup to allow you to use /dev/ttyOx

However if you are loading a device tree overlay from the 3.8.13 era,
you need to update the device tree node name.

for example usart 2: (today)

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART2-00A0.dts#L47

usart2 (yesterday with 3.8.13)

https://github.com/beagleboard/linux/blob/3.8/firmware/capes/BB-UART2-00A0.dts#L41

As you might have other issues causing the blockage, please add the output off

dmesg | grep bone

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYh_ChEqNEa0HjYQ9kKTYFu3dG%3D0HPP1aDPe7o-D9Ejq3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

Hello Dennis,

That is a very relevant reaction! Thanks a lot! Now I have to find out what
port is connected with UART 2 (and others I need). I found ttyO0 and
ttyO3 working, i.e. no errors reported. But also no idea to what UART they
are connected. Definitely not UART2, I am using.
Apart from the fact that I cannot believe that someone deliberately messed
up with the serial ports. Compatibility with earlier scripts is
completely gone!
Can anyone supply me with the altest UART mapping? Or better yet:
re-install the old mapping?
Cheers!
Harke

On 29 January 2017 at 17:04, Dennis Lee Bieber 
wrote:

> On Sun, 29 Jan 2017 03:17:51 -0800 (PST), Harke Smits
>  declaimed the following:
>
>
> >pyserial, if necessary. Now my old script does not work anymore. It leaves
> >me with error; Errno 2: could not open port /dev/ttyO2. No such file or
> >directory. Do I miss something here? What else do I need to do?
>
> Well, first thing: do you HAVE a ttyO2 in /dev? I don't -- using a
> "Wheezy" image from last summer, I'll dig up the SD card with "Jessie" in a
> moment... (apologies for the bad wrapping)
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 3.8.13-bone80 #1 SMP Wed Jun 15 17:03:55 UTC 2016 armv7l
> GNU/Linux
> debian@beaglebone:~$ ls /dev/tty*
> /dev/tty/dev/tty16  /dev/tty24  /dev/tty32  /dev/tty40  /dev/tty49
> /dev/tty57  /dev/tty8
> /dev/tty0   /dev/tty17  /dev/tty25  /dev/tty33  /dev/tty41  /dev/tty5
> /dev/tty58  /dev/tty9
> /dev/tty1   /dev/tty18  /dev/tty26  /dev/tty34  /dev/tty42  /dev/tty50
> /dev/tty59  /dev/ttyGS0
> /dev/tty10  /dev/tty19  /dev/tty27  /dev/tty35  /dev/tty43  /dev/tty51
> /dev/tty6   /dev/ttyO0
> /dev/tty11  /dev/tty2   /dev/tty28  /dev/tty36  /dev/tty44  /dev/tty52
> /dev/tty60  /dev/ttyS0
> /dev/tty12  /dev/tty20  /dev/tty29  /dev/tty37  /dev/tty45  /dev/tty53
> /dev/tty61  /dev/ttyS1
> /dev/tty13  /dev/tty21  /dev/tty3   /dev/tty38  /dev/tty46  /dev/tty54
> /dev/tty62  /dev/ttyS2
> /dev/tty14  /dev/tty22  /dev/tty30  /dev/tty39  /dev/tty47  /dev/tty55
> /dev/tty63  /dev/ttyS3
> /dev/tty15  /dev/tty23  /dev/tty31  /dev/tty4   /dev/tty48  /dev/tty56
> /dev/tty7
> debian@beaglebone:~$
>
> I show ttyS0 .. ttyS3
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l
> GNU/Linux
> debian@beaglebone:~$ ls /dev/tty*
> /dev/tty/dev/tty17  /dev/tty26  /dev/tty35  /dev/tty44  /dev/tty53
> /dev/tty62   /dev/ttyS0
> /dev/tty0   /dev/tty18  /dev/tty27  /dev/tty36  /dev/tty45  /dev/tty54
> /dev/tty63   /dev/ttyS1
> /dev/tty1   /dev/tty19  /dev/tty28  /dev/tty37  /dev/tty46  /dev/tty55
> /dev/tty7/dev/ttyS2
> /dev/tty10  /dev/tty2   /dev/tty29  /dev/tty38  /dev/tty47  /dev/tty56
> /dev/tty8/dev/ttyS3
> /dev/tty11  /dev/tty20  /dev/tty3   /dev/tty39  /dev/tty48  /dev/tty57
> /dev/tty9/dev/ttyS4
> /dev/tty12  /dev/tty21  /dev/tty30  /dev/tty4   /dev/tty49  /dev/tty58
> /dev/ttyGS0  /dev/ttyS5
> /dev/tty13  /dev/tty22  /dev/tty31  /dev/tty40  /dev/tty5   /dev/tty59
> /dev/ttyO0
> /dev/tty14  /dev/tty23  /dev/tty32  /dev/tty41  /dev/tty50  /dev/tty6
> /dev/ttyO1
> /dev/tty15  /dev/tty24  /dev/tty33  /dev/tty42  /dev/tty51  /dev/tty60
> /dev/ttyO2
> /dev/tty16  /dev/tty25  /dev/tty34  /dev/tty43  /dev/tty52  /dev/tty61
> /dev/ttyO4
> debian@beaglebone:~$
>
>
> Interesting -- Jessie (from last fall) shows both ttyO0/1/2/4 AND
> ttyS0/1/2/3/4/5
>
> debian@beaglebone:~$ ls -l /dev/ttyO*
> lrwxrwxrwx 1 root root 5 Dec 10 12:31 /dev/ttyO0 -> ttyS0
> lrwxrwxrwx 1 root root 5 Jan 29 10:57 /dev/ttyO1 -> ttyS1
> lrwxrwxrwx 1 root root 5 Jan 29 10:57 /dev/ttyO2 -> ttyS2
> lrwxrwxrwx 1 root root 5 Jan 29 10:57 /dev/ttyO4 -> ttyS4
> debian@beaglebone:~$ ls -l /dev/ttyS*
> crw--w 1 root tty 4, 64 Dec 10 12:32 /dev/ttyS0
> crw-rw 1 root dialout 4, 65 Jan 29 10:57 /dev/ttyS1
> crw-rw 1 root dialout 4, 66 Jan 29 10:57 /dev/ttyS2
> crw-rw 1 root dialout 4, 67 Dec 10 12:32 /dev/ttyS3
> crw-rw 1 root dialout 4, 68 Jan 29 10:57 /dev/ttyS4
> crw-rw 1 root dialout 4, 69 Dec 10 12:32 /dev/ttyS5
>
> Though the ttyO* are just links to the ttyS*
>
> Maybe in a month or so I'll have time to flash the eMMC up to
> Jessie,
> and set the SD cards to newer releases. (I prefer to keep the eMMC on an
> older working config)
>
> --
> Wulfraed Dennis Lee Bieber AF6VN
> wlfr...@ix.netcom.comHTTP://wlfraed.home.netcom.com/
>
> --
> 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/b4CG9YdoZK4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> 

Re: [beagleboard] change readonly file system to readwrite

[abhilash h]

Change it to rw and check one
On Sun, 29 Jan 2017 at 5:59 PM, Madhu K  wrote:

> It mounted as ro
>
> On Sun, Jan 29, 2017 at 1:50 PM, abhilash h  wrote:
>
> If your rfs mountes as ro or rw
>
> On Sun, 29 Jan 2017 at 11:48 AM, Madhu K  wrote:
>
>  Hi All
>
> I am trying to edit and save the /etc/network/interfaces file on
> beaglebone black board, the message i am getting while saving as"
> readonly", even though i am a root user.
>
> How to change the readonly to readwrite.
>
>
> Thanks & regards,
> Madhu
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/64d7ecda-9e85-497a-a9d0-2c3092cfd1d6%40googlegroups.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.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CA%2B-ZLiv-0G81tzoq5X9W479CBqJhZpfy5RGwE%3DPeXoQp2SCrXg%40mail.gmail.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAA2oCOm5fmdu3cR1BHtxRAo_hxW4J8qwr8DkRFOo%3D9C-_S%3D-5A%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2B-ZLivhNgoHeLV8ZbNk2%2BG5dF3e6aMh1R1qgL0Wyqd-AZEBOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: can't load device tree on Debian jessie 8.6 with kernel version 4.4.43-ti-r84

[Greg]

I wouldn't update the kernel at this time.  Yes, try the procedure and see 
what happens.  I think you will be successful.  If not, we can work through 
it.

That kernel is the TI version and it should be good to go for sure.  If 
not, there are problems we are not going to solve without help!
It's still not clear to me the differences between the TI and the Bone 
kernels.  The TI kernels definitely support the latest Remoteproc.

If you don't need GUI, stick with the IOT image.  I've had very good luck 
with it.


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/50da6b9a-be95-494f-8a21-a179fc1e714c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] change readonly file system to readwrite

[Madhu K]

It mounted as ro

On Sun, Jan 29, 2017 at 1:50 PM, abhilash h  wrote:

> If your rfs mountes as ro or rw
>
> On Sun, 29 Jan 2017 at 11:48 AM, Madhu K  wrote:
>
>>  Hi All
>>
>> I am trying to edit and save the /etc/network/interfaces file on
>> beaglebone black board, the message i am getting while saving as"
>> readonly", even though i am a root user.
>>
>> How to change the readonly to readwrite.
>>
>>
>> Thanks & regards,
>> Madhu
>>
>> --
>> 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.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/beagleboard/64d7ecda-9e85-497a-a9d0-2c3092cfd1d6%40googlegroups.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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/CA%2B-ZLiv-0G81tzoq5X9W479CBqJhZpfy5RGwE%
> 3DPeXoQp2SCrXg%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAA2oCOm5fmdu3cR1BHtxRAo_hxW4J8qwr8DkRFOo%3D9C-_S%3D-5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] pyserial stopped working after Debian update?

[Harke Smits]

Learned group,

Recently I updated (flashed) my Debian version from 2015-11-12 to Debian 
2017-01-22. The hw rest unchanged: BBB, 4D systems display and a universal 
board only to interface a simple N8M GPS receiver. I have a very simple 
Python script to read UART2 connected to the GPS receiver and show some 
lines of NMEA. In the old Debian version this (and my other applications) 
work good. At first the display did not work either, but I found I had to 
uncomment a line in uEnv.txt. The gui apparently has been changed. So 
far so good. I also did: sudo apt-get update and installed Adafruit and 
pyserial, if necessary. Now my old script does not work anymore. It leaves 
me with error; Errno 2: could not open port /dev/ttyO2. No such file or 
directory. Do I miss something here? What else do I need to do?
Please advise.
Thanks in advance,
Harke

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/396f0ce1-a593-4d48-8ee2-01681b32dd71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How do I keep a program running after disconnecting from ssh?

[Chris Green]

'woody stanford' via BeagleBoard  wrote:
> >
> > I use the BBB to turn on my christmas light using a simple relay circuit. 
> > I made a simple server in python that listens to post requests, so far it 
> > works, I also use Microsoft Cognitive Services to send post requests based 
> > on speech commands.
> > When I start up the python server: nohup python3 server.py & everything 
> > works fine while I am connected to the BBB over ssh but when I leave the 
> > server stops working.
> >
> > Could you please give me some advice on how to keep python3 server running 
> > after I disconnect from ssh?
> >
Look at the 'nohup' command.  Basically you do:-

nohup  &

The & after the command puts it in the background, the nohup tells the
system not to send it a hangup signal when you disconnect ssh.

-- 
Chris Green
·

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/r4r0md-qc1.ln1%40esprimo.zbmc.eu.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: [beagle-alpha] v4.9.x-ti now open for testing...

[Drew Fustini]

On Wed, Nov 2, 2016 at 11:23 AM,
Robert Nelson  wrote:
> I've just added a forward port of the eqep driver.. One of the big
> changes, the eqep clock should be enabled/setup via the device-tree,
> instead of the driver..
>
> [   36.292972] eqep 48300180.eqep: ver. 1.0
> [   36.293178] eqep 48300180.eqep: count_mode:0
> [   36.293187] eqep 48300180.eqep: invert_qa:1
> [   36.293195] eqep 48300180.eqep: invert_qb:1
> [   36.293201] eqep 48300180.eqep: invert_qi:0
> [   36.293208] eqep 48300180.eqep: invert_qs:0
> [   36.293215] eqep 48300180.eqep: swap_inputs:0
> [   36.293222] eqep 48300180.eqep: QDECCTL:0x0180
> [   36.293230] eqep 48300180.eqep: QPOSINIT:0x
> [   36.293236] eqep 48300180.eqep: QPOSMAX:0x
> [   36.293241] eqep 48300180.eqep: QPOSCNT:0x
> [   36.293249] eqep 48300180.eqep: omit_interrupt:0
> [   36.293254] eqep 48300180.eqep: QEINT:0x0800
> [   36.293261] eqep 48300180.eqep: QUPRD:0x05f5e100
> [   36.293267] eqep 48300180.eqep: QEPCTL:0x009e write
> [   36.293273] eqep 48300180.eqep: QEPCTL:0x009e read
> [   36.293296] eqep 48300180.eqep: irq:193, clk_rate:1
>
> It would be awesome if someone who had it working in v4.4.x-bone/etc..
> Could verify. ;)

eqep was working for me in 4.4.x but I get a segmentation fault when I
read the sysfs position file:
# cat /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/position

It seems to happen at this call to readl() in eqep_get_position():
Line 401: position = readl(eqep->mmio_base + QPOSCNT);

from dmesg:
[ 1858.085381] DEBUG: tieqep.c: eqep_get_position: QPOSCNT=0
[ 1858.102133] DEBUG: tieqep.c: eqep_get_position: eqep->mmio_base=fa304180
[ 1858.108446] Unhandled fault: external abort on non-linefetch
(0x1028) at 0xfa304184

I got some good hints from Google+:
https://plus.google.com/u/0/+DrewFustini/posts/MYfYUyQvv7W

Michael Welling wrote:
> This external abort fault is probably caused by the clock being dynamically
> disabled by runtime suspend. pm_runtime_get_sync is missing somewhere.

Felipe Balbi wrote:
> Looking at the diff, it works on 4.4 out of sheer luck. There's nothing 
> guaranteeing
> clock won't be gated. Enable pm runtime and call pm runtime get sync

I'm now reading about pm_runtime_get_sync() in
Documentation/power/runtime_pm.txt.  I'll update if I make any
progress.

Thanks,
Drew

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAEf4M_DUkK125T93P92-DEB8dtMP62YSunK5yxVMqfy%3DR%2Bh08A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: High speed encoder input capability of BBB?

[robertsmaria934 via BeagleBoard]

On Sun, 1/29/17, Drew Fustini  wrote:

 Subject: Re: [beagleboard] Re: High speed encoder input capability of BBB?
 To: "Beagle Board" 
 Date: Sunday, January 29, 2017, 9:34 AM
 
 On Sun, Jan 15, 2017 at 2:31 AM, TJF
 
 wrote:
 > Yes, QEP is ready. I also found a workarround for the
 PWM issue, so my
 > development version fully works on 4.x kernels. But I
 still couldn't find a
 > block of time to finish the documentation, yet.
 
 Have you tried it on the 4.9.x kernel yet?
 
 I've been unable to get the tiqep kernel driver in
 4.9.5-ti-r16 to
 work so far.  I'm curious if eQEP would still work with
 your method.
 
 thanks,
 drew
 
 -- 
 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.
 To view this discussion on the web visit
 
https://groups.google.com/d/msgid/beagleboard/CAEf4M_D6jaYDiOAmj1TBY3kiYpL-LhUghUvTRs8Rt8zn_WkEuQ%40mail.gmail.com.
 For more options, visit https://groups.google.com/d/optout.
 ramantari si rascoale taranesti  1888-1907 . Framantarile si agitatiile 
ranimii  al caror punct culminant l-au reprezentat rascoalele  au pus in lumina 
ontradictiile din sanul societatii romanesti in pragul secolului al XX-lea si 
au onstituit forme de actiune specifica in viata satului.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1560451244.2818331.1485678146461%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] change readonly file system to readwrite

[abhilash h]

If your rfs mountes as ro or rw

On Sun, 29 Jan 2017 at 11:48 AM, Madhu K  wrote:

>  Hi All
>
> I am trying to edit and save the /etc/network/interfaces file on
> beaglebone black board, the message i am getting while saving as"
> readonly", even though i am a root user.
>
> How to change the readonly to readwrite.
>
>
> Thanks & regards,
> Madhu
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/64d7ecda-9e85-497a-a9d0-2c3092cfd1d6%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2B-ZLiv-0G81tzoq5X9W479CBqJhZpfy5RGwE%3DPeXoQp2SCrXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.