[beagleboard] Re: How to read binary (10101..) data from a device?

[JJ]

>
> Here's my current python code:
>
import Adafruit_BBIO.GPIO as GPIO
import time
import sys

import psutil, os
p = psutil.Process(os.getpid())
p.nice(-20)

GPIO.setup("P8_10", GPIO.OUT)
GPIO.output("P8_10", GPIO.LOW)
GPIO.setup("P8_12", GPIO.IN)


while True:

data = []
GPIO.wait_for_edge("P8_12", GPIO.RISING)
for i in range (0,41):
if GPIO.input("P8_12"):
data.append(1)
else:
data.append(0)


if (i == 0):
time.sleep(1.8*0.001)
else:
time.sleep(1.2*0.001)


print(data)


 
However it doesnt capture the bits correctly, the 5 first bits are *often* 
11011 
but not always (I changed the time.wait for very first bit but it didnt 
help much). How can I improve the reception speed?
I dont know assembly at all and very little C. Is there better python 
solution available?

-- 
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: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[liyaoshi]

http://www.freescale.com/lgfiles/NMG/MAD/YOCTO/gpu-viv-bin-mx6q-3.10.17-1.0.0-hfp.bin

Do you mean this ?


2014-11-30 9:35 GMT+08:00 Robert Nelson :

>
> On Nov 29, 2014 7:22 PM, "Nick Apperley"  wrote:
> >
> > Robert - thanks for the advise. Would it make sense economically to go
> for the Wandboard Quad over the upcoming Beagleboard X15 when it comes to
> running GUI programs?
>
> 3d: vivante will be reversed engineered before powervr. Freescale hasn't
> released 'armhf' drivers whereas ti has..
>
> The 'x15' will be supported by bb.org and ti.. Who really supports the
> wand? All the info I put out is just because I replaced my failing pandas
> with quad wands...
>
> 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.
>

-- 
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] Switching to Jessie from Wheezy.

[Robert Nelson]

On Nov 29, 2014 6:55 PM, "Jason Lange"  wrote:
>
>
>>> # apt-get update
>>> # reboot
>>
>> ..that's meant to be: "apt-get dist-update"
>
> damn.. that's "apt-get dist-upgrade"

This syntax is pretty reliable:

http://elinux.org/BeagleBoardDebian#Upgrading_from_Debian_6_.28Squeeze.29_to_Debian_7_.28Wheezy.29

You can drop the bb.org repo and add my repos.rcn-ee.net to get those
specific packages that where in the bb.org repo..

>
> --
> 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] Re: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[Robert Nelson]

On Nov 29, 2014 7:22 PM, "Nick Apperley"  wrote:
>
> Robert - thanks for the advise. Would it make sense economically to go
for the Wandboard Quad over the upcoming Beagleboard X15 when it comes to
running GUI programs?

3d: vivante will be reversed engineered before powervr. Freescale hasn't
released 'armhf' drivers whereas ti has..

The 'x15' will be supported by bb.org and ti.. Who really supports the
wand? All the info I put out is just because I replaced my failing pandas
with quad wands...

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.

Re: [beagleboard] Re: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[Nick Apperley]

Robert - thanks for the advise. Would it make sense economically to go for 
the Wandboard Quad over the upcoming Beagleboard X15 when it comes to 
running GUI programs?


On Sunday, 30 November 2014 13:32:01 UTC+13, RobertCNelson wrote:
>
>
> On Nov 29, 2014 6:21 PM, "Nick Apperley" > 
> wrote:
> >
> > Robert - What is the performance like with a Dual Core Cortex A9 
> compared to a Quad Core Cortex A9?
>
> With the quad wand, you also get 2gb of ram over the dual which only has 
> 1gb.. That alone is worth the price delta. For the price/performance it's 
> really hard to beat the wand quad.
>
> >
> >
> > On Sunday, 30 November 2014 04:51:10 UTC+13, RobertCNelson wrote:
> >>
> >> omap5_uevm: (i was also building cloud9 during week, let's say 95% of 
> >> the time was openjdk) 
> >> Build needed 38:19:47, 6215244k disc space 
> >>
> >> wand quad: (i was out of state while this was running, so 100% core 
> usage..) 
> >> Build needed 50:06:26, 6215460k disc space 
> >>
> >> The dual a15's come out to 30% faster then the quad a9's... 
> >>
> >> 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...@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] Switching to Jessie from Wheezy.

[Jason Lange]

> # apt-get update
>> # reboot
>>
>> ..that's meant to be: "apt-get dist-update"
>
damn.. that's "apt-get dist-upgrade"

-- 
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] Switching to Jessie from Wheezy.

[Jason Lange]

# apt-get update
> # reboot
>
> ..that's meant to be: "apt-get dist-update"

-- 
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] Switching to Jessie from Wheezy.

[Jason Lange]

That was rude of me;  the answer was pretty much low hanging fruit, and I
didn't have the sense to look.
However I did have one glitch and I don't know that it's not important...

This is what I did:

# apt-get update
# apt-get upgrade
# cp /etc/apt/sources.list{,.bak}
# sed -i -e 's/wheezy/jessie/g' /etc/apt/sources.list
# apt-get update

At this point it became apparent that this line from my new
/etc/apt/sources file was not working:

deb [arch=armhf] http://debian.beagleboard.org/packages jessie-bbb main

I continued anyway with:

# apt-get update
# reboot

Things seem to have worked out.
But if someone sees a problem with that one repo not translating over
to "jessie" please let me know
(otherwise I'll just comment it out to get rid of the warnings)

Thanks.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[Robert Nelson]

On Nov 29, 2014 6:21 PM, "Nick Apperley"  wrote:
>
> Robert - What is the performance like with a Dual Core Cortex A9 compared
to a Quad Core Cortex A9?

With the quad wand, you also get 2gb of ram over the dual which only has
1gb.. That alone is worth the price delta. For the price/performance it's
really hard to beat the wand quad.

>
>
> On Sunday, 30 November 2014 04:51:10 UTC+13, RobertCNelson wrote:
>>
>> omap5_uevm: (i was also building cloud9 during week, let's say 95% of
>> the time was openjdk)
>> Build needed 38:19:47, 6215244k disc space
>>
>> wand quad: (i was out of state while this was running, so 100% core
usage..)
>> Build needed 50:06:26, 6215460k disc space
>>
>> The dual a15's come out to 30% faster then the quad a9's...
>>
>> 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.

-- 
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: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[Nick Apperley]

Robert - What is the performance like with a Dual Core Cortex A9 compared 
to a Quad Core Cortex A9?


On Sunday, 30 November 2014 04:51:10 UTC+13, RobertCNelson wrote:
>
> omap5_uevm: (i was also building cloud9 during week, let's say 95% of 
> the time was openjdk) 
> Build needed 38:19:47, 6215244k disc space 
>
> wand quad: (i was out of state while this was running, so 100% core 
> usage..) 
> Build needed 50:06:26, 6215460k disc space 
>
> The dual a15's come out to 30% faster then the quad a9's... 
>
> 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.

[beagleboard] Wifi unreliable

[Tommi]

Hey everyone, 

I have been using the BBB now for quite a while and I really like it. There 
is only one persistent problem I do not seem to get rid of. So I hope you 
can guide me into the right direction. 

I am using the Ourlink wifi dongle  
to connect to the internet and wicd-curses to set up the wifi. Initially it 
seems to work fine. 

However, quite often the dongle disconnects and I am no longer connected to 
the internet. I am unsure how to proceed or what I could try. A couple of 
observations/comments:
- I am using an external usb hub 
 and 
the beaglebone is also powered from a 5V wall plug 
. So sketchy power supply should not 
be the issue as some people indicate.
- Interestingly wicd-curses still indicates that it is connected, however 
the router does not confirm that and I cannot connect to the BBB. 
- It seems to happen more often when I try to run BTSync to push a lot of 
data through the BBB to an external HDD. If it sits just there and idles it 
can be online for days without problem. 

Do you guys have any advice what to try? I am quite lost and the internet 
does not give me any more help...

Thanks!
Tommi

-- 
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] UARTs enabled but don't work on Debian!

[Steve G]

I googled around and added the following line to uEnv.txt and rebooted:

optargs=capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4,BB-UART5

Now I have /dev/ttyO1-5 but I don't know if they work yet.

On Saturday, November 29, 2014 7:25:54 AM UTC-5, Steve G wrote:
>
> I noticed that on my BBB running the RCN demo image from August 
> (debian-7.6-console-armhf-2014-08-13) on a microSD card the uEnv.txt file 
> is actually in /boot/uboot, not in /boot.  Also there was a warning in 
> uEnv.txt "##Note: On the BeagleBone Black, there is also an uEnv.txt in the 
> eMMC, so if these changes do not seem to be makeing a difference..."  Since 
> I'm booting directly from microSD maybe it's looking here though I don't 
> think eMMC is even mounted.
>
>>
>>

-- 
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: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[John Syn]

On 11/29/14, 7:50 AM, "Robert Nelson"  wrote:

>On Wed, Nov 26, 2014 at 2:38 PM, John Syn  wrote:
>>
>> On 11/26/14, 7:59 AM, "Robert Nelson"  wrote:
>>
>>>On Tue, Nov 25, 2014 at 4:42 PM, Nick Apperley 
>>>wrote:
 Can't see the OpenJDK 8 build. I take it the build failed?

 Have some fantastic news on the Ubuntu front. Various OpenJDK 8
packages via
 an unofficial PPA are available for Ubuntu 12.04 (Precise) and 14.04
 (Trusty).
>>>
>>>So it only took 38 hours 19 minutes. ;)
>> So the Quad CortexA9 took 5 days (120 hours) and the OMAP5 took 38 hours
>> which is more then 3X performance. My bet is the build was running all
>> CPUs close to 100% for the entire build so this would be a good
>>comparison.
>
>So over thanksgiving i let my quad wand do the same task:
>
>omap5_uevm: (i was also building cloud9 during week, let's say 95% of
>the time was openjdk)
>Build needed 38:19:47, 6215244k disc space
>
>wand quad: (i was out of state while this was running, so 100% core
>usage..)
>Build needed 50:06:26, 6215460k disc space
>
>The dual a15's come out to 30% faster then the quad a9's...
Interesting.

http://www.arm.com/products/processors/cortex-a/cortex-a15.php

In this article, ARM says the CortexA15 is 2X performance compared to the
CortexA9, so 2xA15 = 4xA9; however, the OMAP5432 is running at 1.5MHz and
the Wandboard running at 1MHz, so given that, I would expect the OMAP5 to
be about 50% faster. Clearly Debian are running much slower hardware.

Regards,
John
>
>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.


-- 
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] Beaglebone Black Ethernet Phy Not Detected on Boot.

[Christopher and Christina Myers]

Hi!

I would assume that things would be fine without going into single-user
mode. If it happens again, I can try as you suggested and post back :)

On Saturday, November 29, 2014,  wrote:

> to myersco...@gmail.com
> :
>
> Hi,
>
> I noticed that simply pushing RESET button actually helps sometimes, in my
> recent experiments. At the same time, pushing POWER button may not help
> sometimes. I have an impression that this issue is a bit different by
> different people.
>
> Have you tried resetting the board by means of RESET button many times,
> without "init 1" command, to see whether RESET button alone can help?
>
> Regards,
> Alex
>
> On Friday, November 28, 2014 11:43:15 PM UTC+1, myersco...@gmail.com
>  wrote:
>>
>> Ok, so this just happened to me. What I think ultimately caused it in my
>> case is the OS hung on shutdown, so I had to hard-power-off the board with
>> the power button. When it came back up, no network :/ Connected via the
>> serial terminal and was seeing the same things as others had reported. I
>> have a rev. C board, and this was the first problem I've had with it,
>> running 24x7 since it arrived back in July :)
>>
>> Linux envmon 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l
>>
>> From what I gleaned from what some folks commented a few posts above,
>> this is what I did, and so far it seems to have worked for me:
>>
>>  - Logged in as root to the board via the serial terminal
>>  - ran the command "init 1" to take the OS into emergency maintenance
>> mode. (I wanted to be in single-user mode because of what I was about to
>> do.)
>>  - Once there, I pressed the reset button on the board once.
>>
>> When the board rebooted, I had network again :)
>>
>

-- 
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] Beaglebone Black Ethernet Phy Not Detected on Boot.

[alexschneider250]

to myersco...@gmail.com:

Hi,

I noticed that simply pushing RESET button actually helps sometimes, in my 
recent experiments. At the same time, pushing POWER button may not help 
sometimes. I have an impression that this issue is a bit different by 
different people.

Have you tried resetting the board by means of RESET button many times, 
without "init 1" command, to see whether RESET button alone can help?

Regards,
Alex

On Friday, November 28, 2014 11:43:15 PM UTC+1, myersco...@gmail.com wrote:
>
> Ok, so this just happened to me. What I think ultimately caused it in my 
> case is the OS hung on shutdown, so I had to hard-power-off the board with 
> the power button. When it came back up, no network :/ Connected via the 
> serial terminal and was seeing the same things as others had reported. I 
> have a rev. C board, and this was the first problem I've had with it, 
> running 24x7 since it arrived back in July :)
>
> Linux envmon 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l
>
> From what I gleaned from what some folks commented a few posts above, this 
> is what I did, and so far it seems to have worked for me:
>
>  - Logged in as root to the board via the serial terminal
>  - ran the command "init 1" to take the OS into emergency maintenance 
> mode. (I wanted to be in single-user mode because of what I was about to 
> do.)
>  - Once there, I pressed the reset button on the board once.
>
> When the board rebooted, I had network again :)
>

-- 
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] Beaglebone Black Ethernet Phy Not Detected on Boot.

[alexschneider250]

Pratik,

Thank you very much for sharing you experience with this issue. Could you 
please provide more details on what and how you changed in cpsw platform 
data?

Actually, rebuilding the kernel sounds a bit dangerous to me, because it 
may have some side effects, in my opinion. For instance, that "dynamical 
fix" you mentioned results in the situation when the processor communicates 
to the transceiver chip using some other address, not the default 0. OK, 
now everything works, it's fine. But what if some piece of code unknown to 
you still relies on that default address 0, and it gets executed some time 
later, under certain conditions? Theoretically, it could cause something 
even worse than this current issue.

Regards,
Alex

On Tuesday, November 25, 2014 6:00:16 AM UTC+1, rathod@gmail.com wrote:
>
> Well, may be you can add your mdio command inside u-boot source code's 
> default bootcmd and rebuild the u-boot.
> In my case, I updated my cpsw platform data (I use 3.2 kernel, so no 
> device tree) inside kernel dynamically to fix this problem. It seems to be 
> working for me. 
>
> Regards,
> Pratik
>
> On Monday, 24 November 2014 21:12:50 UTC+5:30, alexschn...@gmail.com 
> wrote:
>>
>> It appears that the issue is known for a long time: several registers of 
>> the LAN8710A Ethernet transceiver sometimes get wrong values at power-up, 
>> in spite of correct pin strapping configurations. One of those wrong values 
>> is PHYAD (PHY address in the Special Modes Register), which is erroneously 
>> initialized to 2, while the processor expects it to be 0. This makes it 
>> impossible for the processor to communicate with the transceiver and 
>> override those wrong values.
>>
>> Here , 
>> they suggest that this issue is inherent in the LAN8710A by Microchip, and 
>> may be caused by some interference from the clock signal. However, 
>> Microchip did not admit that.
>>
>> The messages within this topic propose 3 main solutions:
>>
>> 1) Rebuilt the device tree to make it somehow work with a PHY address 
>> that can take on 0 or 2, or probably some other values
>>
>> 2) Remove C24 capacitor (this is not safe)
>>
>> 3) Change the file drivers/net/ethernet/ti/davinci_mdio.c and rebuild the 
>> Linux (this patch, as far as I understand, will update the device tree in 
>> such a way that other, non-zero PHY addresses, will become also acceptable)
>>
>> I have tried to do another thing: to rewrite wrong register values with 
>> U-Boot, using commands like "mdio write 2 18 0xe0", and I managed to make 
>> the content of those registers looking like that of a successfully started 
>> transceiver (including the PHYAD and MODE). However, to successfully apply 
>> these changes, a reset with RESET button is required. And if I just run 
>> "reset" command in U-Boot, the transceiver doesn't work properly after 
>> reboot, even though it already has the right PHY address: 0. In this case 
>> the registers look like as if the auto-negotiation fails, and as if the 
>> link partner (i.e. the processor) doesn't have auto-negotiation ability 
>> (the Auto Negotiation Expansion Register contains 0).
>>
>> If that worked, it would be possible to append all required "rewriting 
>> commands" into "bootcmd" variable, thus forcing U-Boot to rewrite wrong 
>> values automatically. But there is another obstacle on this way: the U-boot 
>> I have (2014.10-dirty) does not have "saveenv" command, for some reason. 
>> So, I cannot save any changes in environmental variables there.
>>
>> If anyone solved this problem by modifying the device tree or by some 
>> U-Boot script, please share the details.
>>
>> On Monday, November 24, 2014 8:18:31 AM UTC+1, Jerin George wrote:
>>>
>>> As suggested in this discussion i moved to 3.14.1 kernel and everything 
>>> went well for the first 48 hours. 
>>> After that i could see that the ETH stopped responding for close to 10 
>>> seconds. 
>>> Then it came back. 
>>>
>>> Test set up:-
>>> I'm using BBB for Data acquisition thru ETH. For testing i have 
>>> connected BBB and 2 PC in a switch. One PC is running a data acquisition 
>>> software to collect data from BBB. Another PC is running the software 
>>> "Total Network Monitor" and it keeps on logging the Network status by 
>>> pinging to both BBB & the other PC. 
>>>
>>> After 48 Hours :-
>>> I could see that the Total Network monitor reported that link to BBB was 
>>> lost for close to 10 seconds. 
>>>
>>> Is this a known issue ? Is there any fix to this. 
>>>
>>> regards, 
>>> Jerin
>>>
>>> On Saturday, 22 November 2014 14:25:03 UTC+5:30, alexschn...@gmail.com 
>>> wrote:

 But the SW can do that only when the transceiver chip is always in a 
 "writable" state, which is unfortunately not the case.

 On Saturday, November 22, 2014 1:38:54 AM UTC+1, Gerald wrote:
>
> All the SW has to do itvwrite to the registers and not rely on the 
> straps. Hmm 

Re: [beagleboard] Re: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[Robert Nelson]

On Sat, Nov 29, 2014 at 9:50 AM, Robert Nelson  wrote:
> On Wed, Nov 26, 2014 at 2:38 PM, John Syn  wrote:
>>
>> On 11/26/14, 7:59 AM, "Robert Nelson"  wrote:
>>
>>>On Tue, Nov 25, 2014 at 4:42 PM, Nick Apperley 
>>>wrote:
 Can't see the OpenJDK 8 build. I take it the build failed?

 Have some fantastic news on the Ubuntu front. Various OpenJDK 8
packages via
 an unofficial PPA are available for Ubuntu 12.04 (Precise) and 14.04
 (Trusty).
>>>
>>>So it only took 38 hours 19 minutes. ;)
>> So the Quad CortexA9 took 5 days (120 hours) and the OMAP5 took 38 hours
>> which is more then 3X performance. My bet is the build was running all
>> CPUs close to 100% for the entire build so this would be a good comparison.
>
> So over thanksgiving i let my quad wand do the same task:
>
> omap5_uevm: (i was also building cloud9 during week, let's say 95% of
> the time was openjdk)
> Build needed 38:19:47, 6215244k disc space
>
> wand quad: (i was out of state while this was running, so 100% core usage..)
> Build needed 50:06:26, 6215460k disc space
>
> The dual a15's come out to 30% faster then the quad a9's...

I'm thinking debian might still have been using a mx53loco based box
for that 120hour run..

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] Re: JavaFX 8 on BeagleBone Black (SGX driver problem?)

[Robert Nelson]

On Wed, Nov 26, 2014 at 2:38 PM, John Syn  wrote:
>
> On 11/26/14, 7:59 AM, "Robert Nelson"  wrote:
>
>>On Tue, Nov 25, 2014 at 4:42 PM, Nick Apperley 
>>wrote:
>>> Can't see the OpenJDK 8 build. I take it the build failed?
>>>
>>> Have some fantastic news on the Ubuntu front. Various OpenJDK 8
>>>packages via
>>> an unofficial PPA are available for Ubuntu 12.04 (Precise) and 14.04
>>> (Trusty).
>>
>>So it only took 38 hours 19 minutes. ;)
> So the Quad CortexA9 took 5 days (120 hours) and the OMAP5 took 38 hours
> which is more then 3X performance. My bet is the build was running all
> CPUs close to 100% for the entire build so this would be a good comparison.

So over thanksgiving i let my quad wand do the same task:

omap5_uevm: (i was also building cloud9 during week, let's say 95% of
the time was openjdk)
Build needed 38:19:47, 6215244k disc space

wand quad: (i was out of state while this was running, so 100% core usage..)
Build needed 50:06:26, 6215460k disc space

The dual a15's come out to 30% faster then the quad a9's...

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] Bonescripts not running properly on webserver and Cloud9 IDE Jessie Snapshot (2014-11-19)

[Robert Nelson]

On Sat, Nov 29, 2014 at 9:00 AM, Husam Ceceli  wrote:
> I just flashed the newest Jessie snapshot and I have not been able to
> successfully run the test scripts on the webserver.
>
> Even when i run the blinkled.js example I get this error:
>
> debugger listening on port 15454
> error: Unable to find LED: usr0
> error: Unable to find LED: usr1
> error: Unable to find LED: usr2
> error: Unable to find LED: usr3

retry with the v3.8.x based kernel:

sudo apt-get update
sudo apt-get install linux-image-3.8.13-bone68
sudo reboot

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] Re: Books or Internet resources on Embedded linux

[Mark A. Yoder]

> I'd also recommend the BeagleBone Cookbook[1], but it won't be out until 
>> April!
>>
>
--Mark

[1] http://shop.oreilly.com/product/0636920033899.do  

-- 
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] Bonescripts not running properly on webserver and Cloud9 IDE Jessie Snapshot (2014-11-19)

[Husam Ceceli]

I just flashed the newest Jessie snapshot and I have not been able to 
successfully run the test scripts on the webserver. 

Even when i run the blinkled.js example I get this error:

debugger listening on port 15454
error: Unable to find LED: usr0
error: Unable to find LED: usr1
error: Unable to find LED: usr2
error: Unable to find LED: usr3

/usr/local/lib/node_modules/bonescript/index.js:161
if(typeof resp.err != 'undefined') {
  ^
TypeError: Cannot read property 'err' of undefined
at Object.f.pinMode 
(/usr/local/lib/node_modules/bonescript/index.js:161:19)
at Object. (/var/lib/cloud9/examples/blinkled.js:6:7)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.runMain [as _onTimeout] (module.js:497:10)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

[Process stopped]

-- 
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] PRU C Project - from device tree to program execution

[Peter Gregory]

I finally got my Beaglebone Black PRU C code project up and going.
It took a lot of googling and posting, but I thought it would be nice to post a 
condensed version of the notes needed to get C code running on the BBB PRU.
This is targeting Debian 3.8 kernel versions.

--
Possible PRU pin mappings + values for device tree building + BBB conflict pins
--
Bit pr1_pru0_pru_r30_? (out)
0   P9_31, gpio3[14], 0x190 , Mode 6
1   P9-29, gpio3[15], 0x194, Mode 6
2   P9-30, gpio3[16], 0x198,  Mode 6 (HDMI, LCD)
3   P9-28, gpio3[17], 0x19c,  Mode 6
4   P9-42, gpio3[14], 0x1a0,  Mode 6
5   P9-27, gpio3[19], 0x1a4,  Mode 6 (HDMI, LCD)
6   P9-41, gpio3[20], 0x1a8,  Mode 6
7   P9-25, gpio3[21], 0x1ac, Mode 6
8   
9   
10  
11  
12  
13  
14  P8-12, gpio1[12], 0x030, Mode 6
15  P8-11, gpio1[13], 0x034, Mode 6


Bit pr1_pru0_pru_r31_?  (in)
0   P9-31, gpio3[14], 0x190, Mode 5
1   P9-29, gpio3[15], 0x194, Mode 5
2   P9-30, gpio3[16], 0x198, Mode 5 (HDMI, LCD)
3   P9-28, gpio3[17], 0x19c, Mode 5
4   P9-42, gpio3[14], 0x1a0, Mode 5
5   P9-27, gpio3[19], 0x1a4, Mode 5
6   P9-41, gpio3[20], 0x1a8, Mode 5 
7   P9-25, gpio3[21], 0x1ac, Mode 5 
8   
9   
10  
11  
12  
13  
14  P8-16, gpio1[14], 0x038, Mode 6
15  P8-15, gpio1[15], 0x03c, Mode 6
16  P9-24, gpio0[15], 0x0184, Mode 6 (HDMI, LCD) 
16  P9-41, gpio3[20], 0x164, Mode 5 

Bit pr1_pru1_pru_r30_? (out)
0   P8-45, gpio2[6], 0x0a0, Mode 5 (HDMI, LCD)
1   P8-46, gpio2[7], 0x0a0, Mode 5 (HDMI, LCD) 
2   P8-43, gpio2[8], 0x0a8, Mode 5 (HDMI, LCD)
3   P8-44, gpio2[9], 0x0ac, Mode 5 (HDMI, LCD)
4   P8-41, gpio2[10], 0x0b0, Mode 5 (HDMI, LCD)
5   P8-42, gpio2[11], 0x0b4, Mode 5 (HDMI, LCD)
6   P8-39, gpio2[12], 0x0b8, Mode 5 (HDMI, LCD)
7   P8-40, gpio2[13], 0x0bc, Mode 5 (HDMI, LCD)
8   P8-27, gpio2[22], 0x0e0, Mode 5 (HDMI, LCD)
9   P8-29, gpio2[23], 0x0e4, Mode 5 (HDMI, LCD)
10  P8-28, gpio2[24], 0x0e8, Mode 5 (HDMI, LCD)
11  
12  P8-21, gpio1[30], 0x080, Mode 5 (HDMI, LCD)
13  P8-20, gpio1[31], 0x084, Mode 5 (HDMI, LCD)
14  
15  
16  

Bit pr1_pru1_pru_r31_?  (in)
0   P8-45, gpio2[6], 0x0a0, Mode 6 (HDMI, LCD)
1   P8-46, gpio2[7], 0x0a0, Mode 6 (HDMI, LCD)
2   P8-43, gpio2[8], 0x0a8, Mode 6 (HDMI, LCD)
3   P8-44, gpio2[9], 0x0ac, Mode 6 (HDMI, LCD)
4   P8-41, gpio2[10], 0x0b0, Mode 6 (HDMI, LCD)
5   P8-42, gpio2[11], 0x0b4, Mode 6 (HDMI, LCD)
6   P8-39, gpio2[12], 0x0b8, Mode 6 (HDMI, LCD)
7   P8-40, gpio2[13], 0x0bc, Mode 6 (HDMI, LCD)
8   P8-27, gpio2[22], 0x0e0, Mode 6 (HDMI, LCD)
9   P8-29, gpio2[23], 0x0e4, Mode 6 (HDMI, LCD)
10  P8-28, gpio2[24], 0x0e8, Mode 6 (HDMI, LCD)
11  
12  P8-21, gpio1[30], 0x080, Mode 6 (HDMI, LCD)
13  P8-20, gpio1[31], 0x084, Mode 6 (HDMI, LCD)
14  
15  
16  P9-26, gpio1[29], 0x180, Mode 6
--
Beaglebone Black Kernel 3.8 Device Tree Overlay - map GPIO pins directly to PRU 
R30 or R31
Create overlay file /lib/kernel/myoverlay-00A0.dts using contents below.
Compile using device tree compiler (dtc):
#sudo apt-get install device-tree-compiler
#sudo dtc -O dtb -o /lib/firmware/myoverlay-00A0.dtbo -b 0 -@ 
/lib/firmware/myoverlay-00A0.dts
Modify cape manager file in /etc/default/capemgr to load overlay during boot:
#sudo nano /etc/default/capemgr
CAPE=myoverlay
Edit /etc/modules and append text
#sudo nano /etc/modules
uio_pruss
--
/dts-v1/;
/plugin/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
part-number = "MYOVERLAY";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
// PRU resources used
"pruss",
"pru0",
// PRU Input pins
"P8.16","pr1_pru0_pru_r31_14",  // PIN Name and the PRU port it 
maps to (see table above)
// PRU Output pins
"P9.31","pr1_pru0_pru_r30_0";

// MUX Bit Maps:
// 0x40 = slow slew (0 = fast slew)
// 0x20 = input (0 = output)
// 0x10 = pullup, 0x08 = disabled (0 = pulldown)
// 0x01 to 0x07 = mode 1 to 7
fragment@8 {
target = <&am33xx_pinmux>;
__overlay__ {

pruss_pins: pruss_pins {
pinctrl-single,pins = <
0x038 0x36  // P8_16, gpio3[14] mode 6, input pull-up
0x190 0x15  // P9_31 gpio1[19] mode 5, output, pull-down
>;
};
};
};

fragment@10 {
target = <&pruss>;
__overlay__

Re: [beagleboard] Re: Books or Internet resources on Embedded linux

[Mark A. Yoder]

I have a bunch of wiki pages I use with my students[1].  They might be of 
some help.

--Mark

[1] http://elinux.org/index.php?title=Category:ECE597

On Friday, November 28, 2014 11:41:41 AM UTC-5, Philip Polstra wrote:
>
> If you aren't doing anything with hardware (using capes, etc.) then doing 
> C/C++ on the BBB is no different from any other Linux system.  There are 
> lots of resources for that kind of stuff.  Even if you want to talk to 
> external devices using serial communications (UART) or some other standard 
> protocol it's all the same once you have configured the pins on the BBB to 
> do what you want.
>
> On Fri, Nov 28, 2014 at 11:00 AM, Rimvis Janusauskas  > wrote:
>
>> Well it's quite sad that the book will be released only on December 31~ 
>> 2014. The other tutorials are quite interesting and helpful, but he uses a 
>> lot of other stuff like capes. I don't have such resources, so it would be 
>> impossible to test what i learned and coded :(.
>>
>> 2014 m. lapkritis 28 d., penktadienis 16:20:15 UTC+2, Graham rašė:
>>>
>>>
>>> http://derekmolloy.ie/beaglebone/
>>>
>>> http://derekmolloy.ie/beaglebone/setting-up-eclipse-
>>> on-the-beaglebone-for-c-development/
>>>
>>> http://derekmolloy.ie/category/embedded-systems/beaglebone/
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>> On Friday, November 28, 2014 6:54:49 AM UTC-6, Rimvis Janusauskas wrote:


 Hi, yesterday i received my BeagleBone Black and started to examine it, 
 written some programs in C to test it, but after some time i realized that 
 many projects in net is in bonescript or you need many other additional 
 parts to make projects. So i would like to start to learn how to program 
 on 
 embedded linux systems. in particularly ARM plate-form.I would like to 
 learn   how to do low level programming in C/C++ (device drivers, 
 interfacing with BeagleBoard peripherals, compiling customized kernels, 
 etc).
  Could you tell me any books to learn to program c/c++ on linux for 
 ARM? 

>>>  -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Purpose of the GND_OSC zero ohm resistors?

[Gerald Coley]

You do not need the resistors.

Gerald

On Friday, November 28, 2014, Seth  wrote:

> I'm looking at making my own version of the BBB for a custom project. I
> see a note on Revision A6: "Noise issues were observed in other designs
> where the clock oscillator was getting hit due to a suspected issue in
> ground bounce. A zero ohm resistor was added to connect the OSC_GND to the
> system ground." A second resistor was added in the next revision to the
> 32kHz crystal circuit.
>
> Could the GND_OSC nets be tied directly to DGND without zero ohm
> resistors? Was the resistor used just in case the change caused problems
> and could be left unpopulated if so? I see no issues in further revisions
> so I'd assume that these changes fixed the issue, is that right? I'm asking
> because I suspect there might be another reason why resistors were used
> instead of just direct traces (like needing a 'single connection point'
> type of thing). Some clarification would be helpful indeed.
>
> Thanks,
> -Seth
>
> --
> 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.
>


-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
http://circuitco.com/support/

-- 
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] UARTs enabled but don't work on Debian!

[Steve G]

I noticed that on my BBB running the RCN demo image from August 
(debian-7.6-console-armhf-2014-08-13) on a microSD card the uEnv.txt file 
is actually in /boot/uboot, not in /boot.  Also there was a warning in 
uEnv.txt "##Note: On the BeagleBone Black, there is also an uEnv.txt in the 
eMMC, so if these changes do not seem to be makeing a difference..."  Since 
I'm booting directly from microSD maybe it's looking here though I don't 
think eMMC is even mounted.

On Friday, November 28, 2014 5:27:11 PM UTC-5, RobertCNelson wrote:
>
> On Fri, Nov 28, 2014 at 4:22 PM, Steve G > 
> wrote: 
> > Thanks that got me a lot further along. 
> > 
> > The problem I have now is the serial ports I believe I enabled didn't 
> appear 
> > in the /dev directory. 
> > 
> > What I did was uncomment the lines like the following in 
> > am335x-boneblack.dts, recompiled and installed: 
> > 
> > #include "am335x-bone-ttyO1.dtsi" 
> > 
> > I have /dev/ttyO0, ttyS1, ttyS2 and ttyS3  but I was expecting more 
> ttyO* 
> > devices. 
>
> ^ that should have gotten you /dev/ttyO1... 
>
> btw, if all you need to do is enable ttyO1 you can also do in 
> /boot/uEnv.txt: 
>
> dtb=am335x-boneblack-ttyO1.dtb 
>
> Which is boneblack + ttyO1 enabled.. 
>
> (I've done this for all device + one cape setups') 
>
> 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.

[beagleboard] Help reading MLX90614 with Beaglebone Black

[JJ]

Hello

I need help with reading the MLX90614 ir sensor... When I attach it to BBB 
and run sudo i2cdetect -y -r 1, it slowly looks for i2c addresses and dmesg 
says "controller timed out" every time.

The problem seems to be in the MLX90614 communication, because if I plug it 
out, i2cdetect finds other sensors attached to BBB just fine and rapidly 
without errors. 
I find out that Raspberry Pi has had similar problems and that linux kernel 
version 3.17 does have support for the sensor.

http://lxr.free-electrons.com/source/drivers/iio/temperature/mlx90614.c
http://www.raspberrypi.org/forums/viewtopic.php?p=362243

But how to get this sensor working with Beaglebone Black? My distro is 
debian, and the kernel is 3.8.13-bone67.

-- 
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] Switching to Jessie from Wheezy.

[Jason Lange]

@Robert -- How do I switch to Jessie?

(I notice gcc-4.9 is a happening thing for your latest jessie images and 
suspect that jessie is further along in it's support for systemd, but your 
your latest console images are wheezy only.)

"apt-get dist-upgrade" didn't work.  I thought about trying a search and 
replace wheezy/jessie  in apt-sources but there must be a better way.

Thanks in advance / IOU beer.

Cheers.

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