[beagleboard] Debian Jessie USB drive problem

[Peter Hendricks]

I recently bought a BBG for use as a tiny NAS and print server. I installed 
a Debian Jessie image (for BBB) and ran updates. All X stuff was removed to 
save space and Samba installed.

When I plug in the external USB disk it is recognised and /dev/sda1 
appears. I added this to /etc/fstab:

UUID=F250C93950C904F7   /mnt/usbdrive   ntfs-3g exec,noatime,nofail 
0   0

This seems to work, the drive is mounted at boot time:

/dev/sda1 on /mnt/usbdrive type fuseblk 
(rw,noatime,user_id=0,group_id=0,allow_other,blksize=4096)

However, after a random period of time and without touching the USB bus, 
the drive suddenly switches to /dev/sdb1. This is while the drive is online 
and an IP camera is continuously recording to it. Needless to say, it all 
comes to a sudden halt, as /dev/sda1 disappears.

This must be something I am doing wrong. I have some experience running 
Linux systems as servers, but never had to deal with USB. I thought that 
perhaps the drive going to sleep when idle was a problem, so I hooked it up 
to my laptop and turned the sleep function off. It didn't help.

Thanks for any light you may be able to shed on my problem.

Kind regards,
Peter.

-- 
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/e41a9a55-85fe-4baa-945c-3e3543ff1552%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[Tinashe Mudavanhu]

Silva,

It does have MJPEG but opencv is converting the format to YUYV. And also
does your board have I/O pins digital and analogue?

On Thu, May 26, 2016 at 8:35 AM, Tinashe Mudavanhu 
wrote:

> The 160x120 video stream had no latency but the other camera with 1280x720
> was slow, video was displayed as images being flipped like book pages.
>
> I need to understand something from your files. Does it mean the rest of
> my iris recognition code has to be in the framegrabber.py client file and
> also this file can also run on BBB? Do i need the zhelper.h file when my PC
> is running Ubuntu?
>
> Here is my setup like. I have a PC running Ubuntu connected to the BBB via
> usb and also sharing internet via the same cable (there is no wired
> connection, only the PC is connected to wifi). I want to see the video
> stream on my BBB for debugging purposes and once it is working fine it
> doesn't have to show the video stream. I am accessing the BBB Desktop/GUI
> via a tightvnc client running on my Ubuntu PC. Thats when i will move to
> the hub for a wired connection so that everyone connected to the hub can
> access web pages served by the BBB (running lighttpd webserver).
>
> I was successful in the part of running BBB as a webserver (without an
> video stream to show on the site because i don't need it) but then the
> first part of getting a video stream to show was not possible because of
> select timeout errors.
>
> On Thu, May 26, 2016 at 12:35 AM, Matthew Witherwax 
> wrote:
>
>> Looks like framegrabber was able to capture images based on the output
>> you provided. Did you look at the images?
>>
>> If it works for you then the code for the subscriber here
>> http://blog.lemoneerlabs.com/post/bbb-mjpeg-streaming will show you how
>> to load it into opencv.
>> --
>> From: João M. S. Silva 
>> Sent: ‎5/‎25/‎2016 4:13 PM
>> To: beagleboard@googlegroups.com
>>
>> Subject: Re: [beagleboard] Re: VGA camera capture
>>
>> If the camera has a good compression mechanism (e.g. MJPEG), it may be
>> softer on the USB bus.
>>
>> In our board, we are using OpenCV but we don't capture images with the
>> OpenCV instruction. Instead, we use something like this:
>>
>> https://linuxtv.org/downloads/v4l-dvb-apis/v4l2grab-example.html
>>
>> For video capturing there is also an example:
>>
>> https://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html
>>
>> Note that OpenCV uses v4l underneath.
>>
>> On 25/05/2016 16:51, Tinashe Mudavanhu wrote:
>> > Silva,
>> >
>> > There has to be way. Dereck Molloy
>> > https://www.youtube.com/watch?v=8QouvYMfmQo was able to get a video
>> > stream then its possible to video stream with BBB. I don't have much
>> > time to look for another development board because the Project is due
>> > next week.
>> >
>> > On Wed, May 25, 2016 at 5:48 PM, Tinashe Mudavanhu > > > wrote:
>> >
>> > Hi,
>> >
>> > The same is happening on the other webcam i have (not sure if its
>> > openCV changing resolution). I bought it on AliExpress and has the
>> > following discription; HD 1.3 megapixel 960p 2.8-12mm varifocal lens
>> > Aptina AR0130 android external usb camera module with IR cut
>> > ELP-USB130W01MT-FV
>> > <
>> http://www.aliexpress.com/item/HD-1-3-megapixel-2-8-12mm-varifocal-lens-android-external-usb-camera-module-with-IR/32295825258.html
>> >.
>> > The supplier can be found on http://www.elpcctv.com.
>> >
>> > Since there are no errors, what could be the problem? Is there some
>> > dependencies i have to install?
>> >
>> > I tested with your framebrabber.c code and was getting this (see
>> > below) with the Logitech webcam,
>> >
>> > root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
>> > 1000 -I 30
>> > Startup took 0.01 seconds
>> > Captured 1000 frames in 0.22 seconds
>> > Shutdown took 0.00 seconds
>> >
>> >
>> > real0m42.068s
>> > user0m0.025s
>> > sys0m0.223s
>> >
>> > The no name webcam was giving the following results;
>> > root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
>> > 1000 -I 30
>> > Startup took 0.02 seconds
>> > Captured 1000 frames in 0.26 seconds
>> > Shutdown took 0.00 seconds
>> >
>> >
>> > real2m10.965s
>> > user0m0.033s
>> > sys0m0.262s
>> > root@beaglebone:~#
>> >
>> >
>> >
>> > On Wed, May 25, 2016 at 5:23 PM, Matthew Witherwax
>> > mailto:ablec...@gmail.com>> wrote:
>> >
>> > There are no actual errors in the output you posted.
>> >
>> > Do you have access to any other webcams?  I have tested this
>> > with the Logitech C920, the Logitech C270, and the PS3Eye.
>> > Without access to your webcam, it is hard for me to look into
>> > what is going on.
>> >
>> >
>> > On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe
>> > Mudavanhu wrote:
>> >
>> >   

Re: [beagleboard] Re: VGA camera capture

[Tinashe Mudavanhu]

The 160x120 video stream had no latency but the other camera with 1280x720
was slow, video was displayed as images being flipped like book pages.

I need to understand something from your files. Does it mean the rest of my
iris recognition code has to be in the framegrabber.py client file and also
this file can also run on BBB? Do i need the zhelper.h file when my PC is
running Ubuntu?

Here is my setup like. I have a PC running Ubuntu connected to the BBB via
usb and also sharing internet via the same cable (there is no wired
connection, only the PC is connected to wifi). I want to see the video
stream on my BBB for debugging purposes and once it is working fine it
doesn't have to show the video stream. I am accessing the BBB Desktop/GUI
via a tightvnc client running on my Ubuntu PC. Thats when i will move to
the hub for a wired connection so that everyone connected to the hub can
access web pages served by the BBB (running lighttpd webserver).

I was successful in the part of running BBB as a webserver (without an
video stream to show on the site because i don't need it) but then the
first part of getting a video stream to show was not possible because of
select timeout errors.

On Thu, May 26, 2016 at 12:35 AM, Matthew Witherwax 
wrote:

> Looks like framegrabber was able to capture images based on the output you
> provided. Did you look at the images?
>
> If it works for you then the code for the subscriber here
> http://blog.lemoneerlabs.com/post/bbb-mjpeg-streaming will show you how
> to load it into opencv.
> --
> From: João M. S. Silva 
> Sent: ‎5/‎25/‎2016 4:13 PM
> To: beagleboard@googlegroups.com
>
> Subject: Re: [beagleboard] Re: VGA camera capture
>
> If the camera has a good compression mechanism (e.g. MJPEG), it may be
> softer on the USB bus.
>
> In our board, we are using OpenCV but we don't capture images with the
> OpenCV instruction. Instead, we use something like this:
>
> https://linuxtv.org/downloads/v4l-dvb-apis/v4l2grab-example.html
>
> For video capturing there is also an example:
>
> https://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html
>
> Note that OpenCV uses v4l underneath.
>
> On 25/05/2016 16:51, Tinashe Mudavanhu wrote:
> > Silva,
> >
> > There has to be way. Dereck Molloy
> > https://www.youtube.com/watch?v=8QouvYMfmQo was able to get a video
> > stream then its possible to video stream with BBB. I don't have much
> > time to look for another development board because the Project is due
> > next week.
> >
> > On Wed, May 25, 2016 at 5:48 PM, Tinashe Mudavanhu  > > wrote:
> >
> > Hi,
> >
> > The same is happening on the other webcam i have (not sure if its
> > openCV changing resolution). I bought it on AliExpress and has the
> > following discription; HD 1.3 megapixel 960p 2.8-12mm varifocal lens
> > Aptina AR0130 android external usb camera module with IR cut
> > ELP-USB130W01MT-FV
> > <
> http://www.aliexpress.com/item/HD-1-3-megapixel-2-8-12mm-varifocal-lens-android-external-usb-camera-module-with-IR/32295825258.html
> >.
> > The supplier can be found on http://www.elpcctv.com.
> >
> > Since there are no errors, what could be the problem? Is there some
> > dependencies i have to install?
> >
> > I tested with your framebrabber.c code and was getting this (see
> > below) with the Logitech webcam,
> >
> > root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
> > 1000 -I 30
> > Startup took 0.01 seconds
> > Captured 1000 frames in 0.22 seconds
> > Shutdown took 0.00 seconds
> >
> >
> > real0m42.068s
> > user0m0.025s
> > sys0m0.223s
> >
> > The no name webcam was giving the following results;
> > root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
> > 1000 -I 30
> > Startup took 0.02 seconds
> > Captured 1000 frames in 0.26 seconds
> > Shutdown took 0.00 seconds
> >
> >
> > real2m10.965s
> > user0m0.033s
> > sys0m0.262s
> > root@beaglebone:~#
> >
> >
> >
> > On Wed, May 25, 2016 at 5:23 PM, Matthew Witherwax
> > mailto:ablec...@gmail.com>> wrote:
> >
> > There are no actual errors in the output you posted.
> >
> > Do you have access to any other webcams?  I have tested this
> > with the Logitech C920, the Logitech C270, and the PS3Eye.
> > Without access to your webcam, it is hard for me to look into
> > what is going on.
> >
> >
> > On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe
> > Mudavanhu wrote:
> >
> > The timeout error resurfaced again, i followed you blog post
> > on
> >
> http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html
> > but got the following errors in compiling libjpeg-turbo ;
> >
> > root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
> > make  all-recursive
> 

[beagleboard] kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

[Matt99eo]

Trying to clone a Debian Jesse distro (4.1.21)
I made a uSD using the beaglebone-black-make-microSD-flasher-from-eMMC.sh

What am I missing here?

When I insert this into another BBB it crashes before flashing completion.  
Here is what I see when a serial debug cable is connected:


Starting eMMC Flasher from microSD media
Version: [1.20160222: deal with v4.4.x+ back to old eeprom location...]
-
Checking for Valid bbb-eeprom header
Valid bbb-eeprom header found [335]
-
copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
lsblk:
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16   01M  1 disk 
mmcblk1boot1 179:24   01M  1 disk 
mmcblk0  179:00  3.7G  0 disk 
`-mmcblk0p1  179:10  3.7G  0 part /
mmcblk1  179:80  3.7G  0 disk 
-
df -h | grep rootfs:
-
Erasing: /dev/mmcblk1
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 16.1838 s, 7.0 MB/s
[   31.654940] random: nonblocking pool is initialized
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 4.25127 s, 26.6 MB/s
Erasing: /dev/mmcblk1 complete
-
Writing bootloader to [/dev/mmcblk1]
dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k
-
dd: failed to open '': No such file or directory[   33.281227] Kernel panic 
- not syncing: Attempted to kill init! exitcode=0x0100
[   33.281227] 
[   33.295345] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 
4.1.21-bone-rt-r20 #1
[   33.302856] Hardware name: Generic AM33XX (Flattened Device Tree)
[   33.309018] [] (unwind_backtrace) from [] 
(show_stack+0x11/0x14)
[   33.316808] [] (show_stack) from [] 
(panic+0x6d/0x188)
[   33.323719] [] (panic) from [] 
(complete_and_exit+0x1/0x18)
[   33.331063] [] (complete_and_exit) from [] 
(sigprocmask+0x59/0x88)
[   33.339019] [] (sigprocmask) from [<0001>] (0x1)
[   33.344883] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
[   33.344883] 

-- 
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/7470bec3-23df-487f-a559-9ae6e3967726%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] flashing BBB with image made from /opt/scripts/tools/beag.... and getting kernel panic

[Robert Nelson]

On Wed, May 25, 2016 at 7:42 PM, Matt99eo 
wrote:

> Trying to clone a Debian Jesse distro (4.1.21)
> I made a uSD using the beaglebone-black-make-microSD-flasher-from-eMMC.sh
>
> What am I missing here?
>
> When I insert this into another BBB it crashes before flashing
> completion.  Here is what I see when a serial debug cable is connected:
>
>
> Starting eMMC Flasher from microSD media
> Version: [1.20160222: deal with v4.4.x+ back to old eeprom location...]
> -
> Checking for Valid bbb-eeprom header
> Valid bbb-eeprom header found [335]
> -
> copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
> lsblk:
> NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> mmcblk1boot0 179:16   01M  1 disk
> mmcblk1boot1 179:24   01M  1 disk
> mmcblk0  179:00  3.7G  0 disk
> `-mmcblk0p1  179:10  3.7G  0 part /
> mmcblk1  179:80  3.7G  0 disk
> -
> df -h | grep rootfs:
> -
> Erasing: /dev/mmcblk1
> 108+0 records in
> 108+0 records out
> 113246208 bytes (113 MB) copied, 16.1838 s, 7.0 MB/s
> [   31.654940] random: nonblocking pool is initialized
> 108+0 records in
> 108+0 records out
> 113246208 bytes (113 MB) copied, 4.25127 s, 26.6 MB/s
> Erasing: /dev/mmcblk1 complete
> -
> Writing bootloader to [/dev/mmcblk1]
> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k
>

^^ that should have been:

dd if=/opt/backup/uboot/MLO of=/dev/mmcblk1...

Which means the "beaglebone-black-make-microSD-flasher-from-eMMC.sh" script
failed to get a network connect to grab a good bootloader:

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh#L445-L449

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/CAOCHtYhmmYnnH%3DNojCbJyPM%2B8L%3D9%3DTayyYAty8BHXceLqq%3DTOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] flashing BBB with image made from /opt/scripts/tools/beag.... and getting kernel panic

[Matt99eo]

Trying to clone a Debian Jesse distro (4.1.21)
I made a uSD using the beaglebone-black-make-microSD-flasher-from-eMMC.sh

What am I missing here?

When I insert this into another BBB it crashes before flashing completion.  
Here is what I see when a serial debug cable is connected:


Starting eMMC Flasher from microSD media
Version: [1.20160222: deal with v4.4.x+ back to old eeprom location...]
-
Checking for Valid bbb-eeprom header
Valid bbb-eeprom header found [335]
-
copying: [/dev/mmcblk0] -> [/dev/mmcblk1]
lsblk:
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16   01M  1 disk 
mmcblk1boot1 179:24   01M  1 disk 
mmcblk0  179:00  3.7G  0 disk 
`-mmcblk0p1  179:10  3.7G  0 part /
mmcblk1  179:80  3.7G  0 disk 
-
df -h | grep rootfs:
-
Erasing: /dev/mmcblk1
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 16.1838 s, 7.0 MB/s
[   31.654940] random: nonblocking pool is initialized
108+0 records in
108+0 records out
113246208 bytes (113 MB) copied, 4.25127 s, 26.6 MB/s
Erasing: /dev/mmcblk1 complete
-
Writing bootloader to [/dev/mmcblk1]
dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k
-
dd: failed to open '': No such file or directory[   33.281227] Kernel panic 
- not syncing: Attempted to kill init! exitcode=0x0100
[   33.281227] 
[   33.295345] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 
4.1.21-bone-rt-r20 #1
[   33.302856] Hardware name: Generic AM33XX (Flattened Device Tree)
[   33.309018] [] (unwind_backtrace) from [] 
(show_stack+0x11/0x14)
[   33.316808] [] (show_stack) from [] 
(panic+0x6d/0x188)
[   33.323719] [] (panic) from [] 
(complete_and_exit+0x1/0x18)
[   33.331063] [] (complete_and_exit) from [] 
(sigprocmask+0x59/0x88)
[   33.339019] [] (sigprocmask) from [<0001>] (0x1)
[   33.344883] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
[   33.344883] 

-- 
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/f5347472-b83a-4560-871f-851b3647accb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Re: VGA camera capture

[Matthew Witherwax]

Looks like framegrabber was able to capture images based on the output you 
provided. Did you look at the images?

If it works for you then the code for the subscriber here 
http://blog.lemoneerlabs.com/post/bbb-mjpeg-streaming will show you how to load 
it into opencv.

-Original Message-
From: "João M. S. Silva" 
Sent: ‎5/‎25/‎2016 4:13 PM
To: "beagleboard@googlegroups.com" 
Subject: Re: [beagleboard] Re: VGA camera capture

If the camera has a good compression mechanism (e.g. MJPEG), it may be 
softer on the USB bus.

In our board, we are using OpenCV but we don't capture images with the 
OpenCV instruction. Instead, we use something like this:

https://linuxtv.org/downloads/v4l-dvb-apis/v4l2grab-example.html

For video capturing there is also an example:

https://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html

Note that OpenCV uses v4l underneath.

On 25/05/2016 16:51, Tinashe Mudavanhu wrote:
> Silva,
>
> There has to be way. Dereck Molloy
> https://www.youtube.com/watch?v=8QouvYMfmQo was able to get a video
> stream then its possible to video stream with BBB. I don't have much
> time to look for another development board because the Project is due
> next week.
>
> On Wed, May 25, 2016 at 5:48 PM, Tinashe Mudavanhu  > wrote:
>
> Hi,
>
> The same is happening on the other webcam i have (not sure if its
> openCV changing resolution). I bought it on AliExpress and has the
> following discription; HD 1.3 megapixel 960p 2.8-12mm varifocal lens
> Aptina AR0130 android external usb camera module with IR cut
> ELP-USB130W01MT-FV
> 
> .
> The supplier can be found on http://www.elpcctv.com.
>
> Since there are no errors, what could be the problem? Is there some
> dependencies i have to install?
>
> I tested with your framebrabber.c code and was getting this (see
> below) with the Logitech webcam,
>
> root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
> 1000 -I 30
> Startup took 0.01 seconds
> Captured 1000 frames in 0.22 seconds
> Shutdown took 0.00 seconds
>
>
> real0m42.068s
> user0m0.025s
> sys0m0.223s
>
> The no name webcam was giving the following results;
> root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
> 1000 -I 30
> Startup took 0.02 seconds
> Captured 1000 frames in 0.26 seconds
> Shutdown took 0.00 seconds
>
>
> real2m10.965s
> user0m0.033s
> sys0m0.262s
> root@beaglebone:~#
>
>
>
> On Wed, May 25, 2016 at 5:23 PM, Matthew Witherwax
> mailto:ablec...@gmail.com>> wrote:
>
> There are no actual errors in the output you posted.
>
> Do you have access to any other webcams?  I have tested this
> with the Logitech C920, the Logitech C270, and the PS3Eye.
> Without access to your webcam, it is hard for me to look into
> what is going on.
>
>
> On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe
> Mudavanhu wrote:
>
> The timeout error resurfaced again, i followed you blog post
> on
> http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html
> but got the following errors in compiling libjpeg-turbo ;
>
> root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
> make  all-recursive
> make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
> Making all in java
> make[2]: Entering directory
> `/root/libjpeg-turbo-1.3.0/build/java'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
> `/root/libjpeg-turbo-1.3.0/build/java'
> Making all in simd
> make[2]: Entering directory
> `/root/libjpeg-turbo-1.3.0/build/simd'
> make  all-am
> make[3]: Entering directory
> `/root/libjpeg-turbo-1.3.0/build/simd'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory
> `/root/libjpeg-turbo-1.3.0/build/simd'
> make[2]: Leaving directory
> `/root/libjpeg-turbo-1.3.0/build/simd'
> Making all in md5
> make[2]: Entering directory
> `/root/libjpeg-turbo-1.3.0/build/md5'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
> make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
> root@beaglebone:~/libjpeg-turbo-1.3.0/build#
>
>
> Before compiling libjpeg-turbo i tested

Re: [beagleboard] BBB Enable UARTs

[William Hermans]

william@beaglebone:~/dev$ apt-cache search cape |grep overlay
bb-cape-overlays - Device tree overlays for Beaglebone.

The package above is the package you're wanting to download, if your
/lib/firmware is not populated, or is missing all together.

Sorry for the multi posts . . . but I'm pretty busy on my own ;)

On Wed, May 25, 2016 at 2:44 PM, William Hermans  wrote:

> Additionally I just read cameron's page there and . . .
>
> william@beaglebone:~/dev$ cat /boot/uEnv.txt
> ...
>
> ##Example v3.8.x
> #cape_disable=capemgr.disable_partno=
> #cape_enable=capemgr.enable_partno=
>
> ##Example v4.1.x
> #cape_disable=bone_capemgr.disable_partno=
> #cape_enable=bone_capemgr.enable_partno=
>  ...
>
> You're seeing the difference here ? But also I have no personally hands on
> tested this recently but ##Example v4.1.x should work for 4.4.x kernels
> too.
>
> On Wed, May 25, 2016 at 2:39 PM, William Hermans 
> wrote:
>
>> So the difference you're running into is the cape manager path naming I
>> bet. But here:
>> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/
>>
>> Read that, but you should not need worry about compiling the DTS files
>> for kernel 4.4.x. But you can tell if they're installed already by listing
>> the contents of /lib/firmware/. Obviously if the directory does not exist,
>> or it is empty, you need to either download the device tree overlay
>> package, or build your own as I describe from the beginning of the link
>> above.
>>
>> Let me know if that's enough information or not, and I'll answer back
>> answers to your questions . . .
>>
>> On Wed, May 25, 2016 at 2:08 PM,  wrote:
>>
>>> Hi,
>>>
>>> We've been using the BBB for a year or so now do act as webserver and a
>>> gateway to a zigbee based network. We have developed a cape that contains a
>>> zigbee device that we can easily communicate with through one of the UARTs.
>>>
>>> We have had a working setup using the old April 2014 image that the BBB
>>> came shipped with, this needed to be brought up to date and I have been
>>> developing new software with the January 2016 image and a USB based zigbee
>>> device.
>>>
>>> My trouble is, now I have come to test the software using the cape I
>>> cannot seem to enable the UARTs.
>>>
>>> In my 2014 version I followed the instructions on this page:
>>> http://beaglebone.cameon.net/home/serial-ports-uart and this work
>>> successfully.
>>>
>>> After "some" digging I found out about the config-pin application here:
>>> https://github.com/cdsteinkuehler/beaglebone-universal-io and have
>>> checked the help page of the app. I had hoped this would solve the problem
>>> and tried to set the use of pins I wanted (to enable UART5) however I got
>>> an error message that there was no pinmux file. Having re-read the above
>>> page I don't have half the directory structure that the instructions talk
>>> about, namely no ocp.* in /sys/devices/, so I'm completely stuck.
>>>
>>> I just need to know how to enable UART5, I'm a fairly experienced linux
>>> user and very experience programmer, though my knowledge of Linux kernal
>>> stuff is terrible.
>>>
>>> I also have a strange setup in my /dev/ for ttyO* I had expected there
>>> only to be ttyO0 as that was the only port enabled by default, is that
>>> still the case?
>>>
>>> /dev# dir -l ttyO*
>>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO0 -> ttyS0
>>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO1 -> ttyS1
>>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO2 -> ttyS2
>>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO4 -> ttyS4
>>>
>>> My Linux knowledge is also failing me here are these showing symbolic
>>> links? I'm not sure if this is part of why I can't use the UARTs or
>>> something separate.
>>>
>>> Sorry for the long post with a couple of problems in it.
>>>
>>> Thanks
>>>
>>> Lucent
>>>
>>> --
>>> 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/55ceb471-7879-4f0c-8396-007969e87e45%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/CALHSORqyxufvox-hpaCtsPT%2B-ji%3DSmRrvmTB69FfSJg8ti8RDg%40mail.gmail.com.
For more options, visit ht

Re: [beagleboard] BBB Enable UARTs

[William Hermans]

Additionally I just read cameron's page there and . . .

william@beaglebone:~/dev$ cat /boot/uEnv.txt
...

##Example v3.8.x
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=

##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
#cape_enable=bone_capemgr.enable_partno=
 ...

You're seeing the difference here ? But also I have no personally hands on
tested this recently but ##Example v4.1.x should work for 4.4.x kernels too.

On Wed, May 25, 2016 at 2:39 PM, William Hermans  wrote:

> So the difference you're running into is the cape manager path naming I
> bet. But here:
> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/
>
> Read that, but you should not need worry about compiling the DTS files for
> kernel 4.4.x. But you can tell if they're installed already by listing the
> contents of /lib/firmware/. Obviously if the directory does not exist, or
> it is empty, you need to either download the device tree overlay package,
> or build your own as I describe from the beginning of the link above.
>
> Let me know if that's enough information or not, and I'll answer back
> answers to your questions . . .
>
> On Wed, May 25, 2016 at 2:08 PM,  wrote:
>
>> Hi,
>>
>> We've been using the BBB for a year or so now do act as webserver and a
>> gateway to a zigbee based network. We have developed a cape that contains a
>> zigbee device that we can easily communicate with through one of the UARTs.
>>
>> We have had a working setup using the old April 2014 image that the BBB
>> came shipped with, this needed to be brought up to date and I have been
>> developing new software with the January 2016 image and a USB based zigbee
>> device.
>>
>> My trouble is, now I have come to test the software using the cape I
>> cannot seem to enable the UARTs.
>>
>> In my 2014 version I followed the instructions on this page:
>> http://beaglebone.cameon.net/home/serial-ports-uart and this work
>> successfully.
>>
>> After "some" digging I found out about the config-pin application here:
>> https://github.com/cdsteinkuehler/beaglebone-universal-io and have
>> checked the help page of the app. I had hoped this would solve the problem
>> and tried to set the use of pins I wanted (to enable UART5) however I got
>> an error message that there was no pinmux file. Having re-read the above
>> page I don't have half the directory structure that the instructions talk
>> about, namely no ocp.* in /sys/devices/, so I'm completely stuck.
>>
>> I just need to know how to enable UART5, I'm a fairly experienced linux
>> user and very experience programmer, though my knowledge of Linux kernal
>> stuff is terrible.
>>
>> I also have a strange setup in my /dev/ for ttyO* I had expected there
>> only to be ttyO0 as that was the only port enabled by default, is that
>> still the case?
>>
>> /dev# dir -l ttyO*
>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO0 -> ttyS0
>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO1 -> ttyS1
>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO2 -> ttyS2
>> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO4 -> ttyS4
>>
>> My Linux knowledge is also failing me here are these showing symbolic
>> links? I'm not sure if this is part of why I can't use the UARTs or
>> something separate.
>>
>> Sorry for the long post with a couple of problems in it.
>>
>> Thanks
>>
>> Lucent
>>
>> --
>> 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/55ceb471-7879-4f0c-8396-007969e87e45%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/CALHSORo_ULaz5%3D8UUyK8So9DeoNM4%2BMPAsJqzFgquzFv8SeHRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB Enable UARTs

[William Hermans]

So the difference you're running into is the cape manager path naming I
bet. But here:
http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/

Read that, but you should not need worry about compiling the DTS files for
kernel 4.4.x. But you can tell if they're installed already by listing the
contents of /lib/firmware/. Obviously if the directory does not exist, or
it is empty, you need to either download the device tree overlay package,
or build your own as I describe from the beginning of the link above.

Let me know if that's enough information or not, and I'll answer back
answers to your questions . . .

On Wed, May 25, 2016 at 2:08 PM,  wrote:

> Hi,
>
> We've been using the BBB for a year or so now do act as webserver and a
> gateway to a zigbee based network. We have developed a cape that contains a
> zigbee device that we can easily communicate with through one of the UARTs.
>
> We have had a working setup using the old April 2014 image that the BBB
> came shipped with, this needed to be brought up to date and I have been
> developing new software with the January 2016 image and a USB based zigbee
> device.
>
> My trouble is, now I have come to test the software using the cape I
> cannot seem to enable the UARTs.
>
> In my 2014 version I followed the instructions on this page:
> http://beaglebone.cameon.net/home/serial-ports-uart and this work
> successfully.
>
> After "some" digging I found out about the config-pin application here:
> https://github.com/cdsteinkuehler/beaglebone-universal-io and have
> checked the help page of the app. I had hoped this would solve the problem
> and tried to set the use of pins I wanted (to enable UART5) however I got
> an error message that there was no pinmux file. Having re-read the above
> page I don't have half the directory structure that the instructions talk
> about, namely no ocp.* in /sys/devices/, so I'm completely stuck.
>
> I just need to know how to enable UART5, I'm a fairly experienced linux
> user and very experience programmer, though my knowledge of Linux kernal
> stuff is terrible.
>
> I also have a strange setup in my /dev/ for ttyO* I had expected there
> only to be ttyO0 as that was the only port enabled by default, is that
> still the case?
>
> /dev# dir -l ttyO*
> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO0 -> ttyS0
> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO1 -> ttyS1
> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO2 -> ttyS2
> lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO4 -> ttyS4
>
> My Linux knowledge is also failing me here are these showing symbolic
> links? I'm not sure if this is part of why I can't use the UARTs or
> something separate.
>
> Sorry for the long post with a couple of problems in it.
>
> Thanks
>
> Lucent
>
> --
> 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/55ceb471-7879-4f0c-8396-007969e87e45%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/CALHSORq9Le8rJ9Ga-bHxX9m1AUCRR6M7tgiRz_eNZXVcfVFPWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB Enable UARTs

[lucent . peregrine]

Hi,

We've been using the BBB for a year or so now do act as webserver and a 
gateway to a zigbee based network. We have developed a cape that contains a 
zigbee device that we can easily communicate with through one of the UARTs.

We have had a working setup using the old April 2014 image that the BBB 
came shipped with, this needed to be brought up to date and I have been 
developing new software with the January 2016 image and a USB based zigbee 
device. 

My trouble is, now I have come to test the software using the cape I cannot 
seem to enable the UARTs.

In my 2014 version I followed the instructions on this page: 
http://beaglebone.cameon.net/home/serial-ports-uart and this work 
successfully.

After "some" digging I found out about the config-pin application here: 
https://github.com/cdsteinkuehler/beaglebone-universal-io and have checked 
the help page of the app. I had hoped this would solve the problem and 
tried to set the use of pins I wanted (to enable UART5) however I got an 
error message that there was no pinmux file. Having re-read the above page 
I don't have half the directory structure that the instructions talk about, 
namely no ocp.* in /sys/devices/, so I'm completely stuck.

I just need to know how to enable UART5, I'm a fairly experienced linux 
user and very experience programmer, though my knowledge of Linux kernal 
stuff is terrible.

I also have a strange setup in my /dev/ for ttyO* I had expected there only 
to be ttyO0 as that was the only port enabled by default, is that still the 
case?

/dev# dir -l ttyO*
lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO0 -> ttyS0
lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO1 -> ttyS1
lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO2 -> ttyS2
lrwxrwxrwx 1 root root 5 May 25 14:30 ttyO4 -> ttyS4

My Linux knowledge is also failing me here are these showing symbolic 
links? I'm not sure if this is part of why I can't use the UARTs or 
something separate.

Sorry for the long post with a couple of problems in it.

Thanks

Lucent 

-- 
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/55ceb471-7879-4f0c-8396-007969e87e45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[João M . S . Silva]

If the camera has a good compression mechanism (e.g. MJPEG), it may be 
softer on the USB bus.


In our board, we are using OpenCV but we don't capture images with the 
OpenCV instruction. Instead, we use something like this:


https://linuxtv.org/downloads/v4l-dvb-apis/v4l2grab-example.html

For video capturing there is also an example:

https://linuxtv.org/downloads/v4l-dvb-apis/capture-example.html

Note that OpenCV uses v4l underneath.

On 25/05/2016 16:51, Tinashe Mudavanhu wrote:

Silva,

There has to be way. Dereck Molloy
https://www.youtube.com/watch?v=8QouvYMfmQo was able to get a video
stream then its possible to video stream with BBB. I don't have much
time to look for another development board because the Project is due
next week.

On Wed, May 25, 2016 at 5:48 PM, Tinashe Mudavanhu mailto:tinam...@gmail.com>> wrote:

Hi,

The same is happening on the other webcam i have (not sure if its
openCV changing resolution). I bought it on AliExpress and has the
following discription; HD 1.3 megapixel 960p 2.8-12mm varifocal lens
Aptina AR0130 android external usb camera module with IR cut
ELP-USB130W01MT-FV

.
The supplier can be found on http://www.elpcctv.com.

Since there are no errors, what could be the problem? Is there some
dependencies i have to install?

I tested with your framebrabber.c code and was getting this (see
below) with the Logitech webcam,

root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
1000 -I 30
Startup took 0.01 seconds
Captured 1000 frames in 0.22 seconds
Shutdown took 0.00 seconds


real0m42.068s
user0m0.025s
sys0m0.223s

The no name webcam was giving the following results;
root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c
1000 -I 30
Startup took 0.02 seconds
Captured 1000 frames in 0.26 seconds
Shutdown took 0.00 seconds


real2m10.965s
user0m0.033s
sys0m0.262s
root@beaglebone:~#



On Wed, May 25, 2016 at 5:23 PM, Matthew Witherwax
mailto:ablec...@gmail.com>> wrote:

There are no actual errors in the output you posted.

Do you have access to any other webcams?  I have tested this
with the Logitech C920, the Logitech C270, and the PS3Eye.
Without access to your webcam, it is hard for me to look into
what is going on.


On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe
Mudavanhu wrote:

The timeout error resurfaced again, i followed you blog post
on
http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html
but got the following errors in compiling libjpeg-turbo ;

root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
make  all-recursive
make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
Making all in java
make[2]: Entering directory
`/root/libjpeg-turbo-1.3.0/build/java'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`/root/libjpeg-turbo-1.3.0/build/java'
Making all in simd
make[2]: Entering directory
`/root/libjpeg-turbo-1.3.0/build/simd'
make  all-am
make[3]: Entering directory
`/root/libjpeg-turbo-1.3.0/build/simd'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory
`/root/libjpeg-turbo-1.3.0/build/simd'
make[2]: Leaving directory
`/root/libjpeg-turbo-1.3.0/build/simd'
Making all in md5
make[2]: Entering directory
`/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
root@beaglebone:~/libjpeg-turbo-1.3.0/build#


Before compiling libjpeg-turbo i tested my code to see what
will be happening on the resolution and frame rate. I am
working with a Logitech QuickCam E3500 which has support for
both YUVY and MJPEG. I set the resolution to 320x240 with a
30fps frame rate but after running the code, got select
timeout errors and the resolution had changed to 640x480
YUVY with a 15fps frame rate;

root@beaglebone:~/libjpeg-turbo-1.3.0/build# v4l2-ctl -V
Format Video Capture:
 Width/Height  : 640/480
 Pixel Format  : 'YUYV'
 Field  

Re: [beagleboard] Flashing the on-board eMMC of the BB Green with new image

[Rick Mann]

The easiest way is to load one of the "flasher" images onto an SD card (there 
are instructions on how to do this). Then insert that SD card into the BBG, and 
power it up.

It will boot from the SD card, then flash the eMMC with that image.

Then remove power, remove the SD card, and apply power.

> On May 25, 2016, at 03:48 , cpe.3bda...@gmail.com wrote:
> 
> Hello
> 
> I got confused reading about this issue so some question came up: 
> 
> Can you please tell me the correct way to flash the eMMC with new image? 
> And also what is the correct way to boot only from SD-Card without flashing 
> on-board eMMC?
> Will any pre-built image copied with either Win32DiskImager or Linux dd work 
> when flashing the eMMC?
> What is the flasher image and what is the difference between it and the 
> pre-built image?
> 
> Thanks in advance.
> 
> -- 
> 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/474a3a35-3027-4a74-9f23-a1cb3373be5b%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


-- 
Rick Mann
rm...@latencyzero.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/2C0C1430-7A5F-4B79-86F3-086A8D0DB774%40latencyzero.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[Tinashe Mudavanhu]

I have flashed another Debian Wheezy image on my BBB. It comes with
preinstalled opencv (version 2.3.1) but with very old cv bindings. I posted
this in googlegroups as a solution which i mention or i dont see as a
solution because i just avoided the problem. I am able to stream a video
with both cameras. Whichever resolution i set the Logitech camera to, it
converts to the one shown below;
root@beaglebone:~/Project/py_servo_facetracker# v4l2-ctl -V
Format Video Capture:
Width/Height  : 160/120
Pixel Format  : 'YUYV'
Field : None
Bytes per Line: 320
Size Image: 38400
Colorspace: SRGB
root@beaglebone:~/Project/py_servo_facetracker#

The other webcam is set to a 1280x720 resolution with the pixel format set
as YUYV.

I am suspecting it has something to do with the opencv itself when it grabs
frames from the webcam. Is there a way i can set opencv to maintain the
camera resolution i set it to?

On Wed, May 25, 2016 at 5:51 PM, Tinashe Mudavanhu 
wrote:

> Silva,
>
> There has to be way. Dereck Molloy
> https://www.youtube.com/watch?v=8QouvYMfmQo was able to get a video
> stream then its possible to video stream with BBB. I don't have much time
> to look for another development board because the Project is due next week.
>
> On Wed, May 25, 2016 at 5:48 PM, Tinashe Mudavanhu 
> wrote:
>
>> Hi,
>>
>> The same is happening on the other webcam i have (not sure if its openCV
>> changing resolution). I bought it on AliExpress and has the following
>> discription; HD 1.3 megapixel 960p 2.8-12mm varifocal lens Aptina AR0130
>> android external usb camera module with IR cut ELP-USB130W01MT-FV
>> .
>> The supplier can be found on http://www.elpcctv.com.
>>
>> Since there are no errors, what could be the problem? Is there some
>> dependencies i have to install?
>>
>> I tested with your framebrabber.c code and was getting this (see below)
>> with the Logitech webcam,
>>
>> root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c 1000 -I
>> 30
>> Startup took 0.01 seconds
>> Captured 1000 frames in 0.22 seconds
>> Shutdown took 0.00 seconds
>>
>>
>> real0m42.068s
>> user0m0.025s
>> sys0m0.223s
>>
>> The no name webcam was giving the following results;
>> root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c 1000 -I
>> 30
>> Startup took 0.02 seconds
>> Captured 1000 frames in 0.26 seconds
>> Shutdown took 0.00 seconds
>>
>>
>> real2m10.965s
>> user0m0.033s
>> sys0m0.262s
>> root@beaglebone:~#
>>
>>
>>
>> On Wed, May 25, 2016 at 5:23 PM, Matthew Witherwax 
>> wrote:
>>
>>> There are no actual errors in the output you posted.
>>>
>>> Do you have access to any other webcams?  I have tested this with the
>>> Logitech C920, the Logitech C270, and the PS3Eye.  Without access to your
>>> webcam, it is hard for me to look into what is going on.
>>>
>>>
>>> On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe Mudavanhu wrote:
>>>
 The timeout error resurfaced again, i followed you blog post on
 http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html but
 got the following errors in compiling libjpeg-turbo ;

 root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
 make  all-recursive
 make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
 Making all in java
 make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/java'
 make[2]: Nothing to be done for `all'.
 make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/java'
 Making all in simd
 make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
 make  all-am
 make[3]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
 make[3]: Nothing to be done for `all-am'.
 make[3]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
 make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
 Making all in md5
 make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/md5'
 make[2]: Nothing to be done for `all'.
 make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
 make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
 make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
 make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
 root@beaglebone:~/libjpeg-turbo-1.3.0/build#


 Before compiling libjpeg-turbo i tested my code to see what will be
 happening on the resolution and frame rate. I am working with a Logitech
 QuickCam E3500 which has support for both YUVY and MJPEG. I set the
 resolution to 320x240 with a 30fps frame rate but after running the code,
 got select timeout errors and the resolution had changed to 640x480 YUVY
 with a 15fps frame rate;

 root@beaglebone:~/libjpeg-turbo-1.3.0/build# v4l2-ctl -V
 Format V

Re: [beagle-alpha] Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

[Robert Nelson]

On Wed, May 25, 2016 at 2:40 PM, Mark Yoder  wrote:

> Thanks..., but what did you do differently?
>

So after you click the pull request button, you need to manually change the
branch..

github assumes everything get's merged into master..  (which for bonescript
isn't true right now, as 0.5.0 is a seperate development branch)

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/CAOCHtYgOiDAZKLBdpfrgocz3E7%2BnFNmDmrrwGuV6MEK96rkx2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagle-alpha] Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

[Mark Yoder]

Thanks..., but what did you do differently?

--Mark

On Wednesday, May 25, 2016 at 3:37:08 PM UTC-4, robert nelson wrote:
>
>
>
> On Wed, May 25, 2016 at 2:32 PM, Mark Yoder  > wrote:
>
>> Well, I better pull Pro GIt off the shelf and look up how to do it 
>> right...
>>
>
> github need's there own book for the web interface, although it would 
> change weekly..
>
> staged it up for you: ;)
>
> https://github.com/jadonk/bonescript/pull/130
>
> 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/59111231-2ea8-414a-8fef-5cbc30e4004c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagle-alpha] Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

[Robert Nelson]

On Wed, May 25, 2016 at 2:32 PM, Mark Yoder  wrote:

> Well, I better pull Pro GIt off the shelf and look up how to do it right...
>

github need's there own book for the web interface, although it would
change weekly..

staged it up for you: ;)

https://github.com/jadonk/bonescript/pull/130

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/CAOCHtYixPuLFtDFeEn6itQHnPcqP46W4yqjVma2z_hc3AeKGWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagle-alpha] Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

[Mark Yoder]

Well, I better pull Pro GIt off the shelf and look up how to do it right...

--Mark

On Wednesday, May 25, 2016 at 3:30:19 PM UTC-4, robert nelson wrote:
>
>
>
> On Wed, May 25, 2016 at 2:24 PM, Mark Yoder  > wrote:
>
>> I'm rusting on this git stuff with remote repo's, but I think I've just 
>> put in a pull request with the fix.
>>
>
> Close, you want to merge your 0.5.0 into jason's 0.5.0.. (looks like 
> github defaulted to your "master" for some odd reason...)
>
> 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/b865b9a2-30d4-4fc9-95c2-7bbbe7ac1521%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagle-alpha] Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

[Robert Nelson]

On Wed, May 25, 2016 at 2:24 PM, Mark Yoder  wrote:

> I'm rusting on this git stuff with remote repo's, but I think I've just
> put in a pull request with the fix.
>

Close, you want to merge your 0.5.0 into jason's 0.5.0.. (looks like github
defaulted to your "master" for some odd reason...)

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/CAOCHtYiHbu6WQKYavW8RvyCvUr3pOooTcFW2BaPe2pzJaTDNjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

[Mark Yoder]

I'm rusting on this git stuff with remote repo's, but I think I've just put 
in a pull request with the fix.

--Mark

On Wednesday, May 25, 2016 at 3:07:55 PM UTC-4, robert nelson wrote:
>
>
>
> On Wed, May 25, 2016 at 1:52 PM, Mark Yoder  > wrote:
>
>> H.. the pwm path appears to have changed for the 4.4 kernel.  
>> Bonescript uses
>>
>> */sys/devices/platform/ocp/48304000.epwmss/48304200.ehrpwm/pwm/pwmchip6*, 
>> but the new 4.4 kernel path is
>>
>> */sys/devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip6* 
>>  (the ehr is missing).
>>
>> A quick hack is to edit : 
>> */usr/local/lib/node_modules/bonescript/src/hw_mainline.js* and remove 
>> the *ehr* from line 95.
>>
>
> This got changed in:
>
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/am33xx.dtsi?id=dce2a6524963f58e7fd0bb2d3791c150f42c
>
> and then backported to ti's v4.4.x branch..
>
> Since the 0.5.0 branch of bonescript became v4.4.x-ti + with:
>
>
> https://github.com/jadonk/bonescript/commit/afc63224575b014b8661ada52d553ac78140e6b6
>
> This should pwm change would be safe to push in..
>
> 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/8d6b004d-0ab5-40de-a6e0-1bf8c59ded28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: v4.4.x-ti changes (r25+)

[Robert Nelson]

On Wed, May 25, 2016 at 1:52 PM, Mark Yoder  wrote:

> H.. the pwm path appears to have changed for the 4.4 kernel.
> Bonescript uses
>
> */sys/devices/platform/ocp/48304000.epwmss/48304200.ehrpwm/pwm/pwmchip6*,
> but the new 4.4 kernel path is
>
> */sys/devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip6*
>  (the ehr is missing).
>
> A quick hack is to edit :
> */usr/local/lib/node_modules/bonescript/src/hw_mainline.js* and remove
> the *ehr* from line 95.
>

This got changed in:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/am33xx.dtsi?id=dce2a6524963f58e7fd0bb2d3791c150f42c

and then backported to ti's v4.4.x branch..

Since the 0.5.0 branch of bonescript became v4.4.x-ti + with:

https://github.com/jadonk/bonescript/commit/afc63224575b014b8661ada52d553ac78140e6b6

This should pwm change would be safe to push in..

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/CAOCHtYgrJQk5e6FPU5ScC5sZcYH3-Ut6inw%3DoxX3XWmN3Rccjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Schematic / BoM mismatch in /static/beaglebone/latest/Docs/Hardware/

[Gerald Coley]

No problem!

Gerald


On Wed, May 25, 2016 at 1:45 PM, Buck Smith  wrote:

> duh got it   sorry for the "dumb" question
>
> On Wednesday, May 25, 2016 at 7:35:25 AM UTC-7, Gerald wrote:
>>
>> I just checked the link. This is the BeagleBone. It has 256MB which is 2
>> Giga Bit.
>>
>> Gerald
>>
>>
>> On Wed, May 25, 2016 at 9:03 AM, Gerald Coley 
>> wrote:
>>
>>> The board uses 512MB DDR3. The previous version used 256MB.
>>>
>>> Gerald
>>>
>>>
>>> On Wed, May 25, 2016 at 8:58 AM, Buck Smith  wrote:
>>>
 I was checking major components on the schematic file at


 https://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SCH.pdf


 I noticed some differences with the Bill of Materials in BONE_BOM.xls
 in the same folder. In particular the schematic has a  Micro 2 Gigabyte
 DDRAM chip and the BoM has 256 Mbyte.  Is it possible these documents are
 not synch'd?

 I will check github for same issue and report here.

 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/beagleboard/4556bdc6-50e3-4f30-8ae3-f50ef7174b33%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Gerald
>>>
>>> ger...@beagleboard.org
>>> http://beagleboard.org/
>>> gco...@emprodesign.com
>>>
>>>
>>
>>
>> --
>> Gerald
>>
>> ger...@beagleboard.org
>> http://beagleboard.org/
>> gco...@emprodesign.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/89135534-69ac-45ed-9745-f24d76a6bbc1%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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/CAHK_S%2BdVaMzve-jNPtYcwt0rqw6YfFT2R%3Dv8AGZkTw3BjDF4XQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: v4.4.x-ti changes (r25+)

[Mark Yoder]

H.. the pwm path appears to have changed for the 4.4 kernel. 
 Bonescript uses

*/sys/devices/platform/ocp/48304000.epwmss/48304200.ehrpwm/pwm/pwmchip6*, 
but the new 4.4 kernel path is

*/sys/devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip6*  (the 
ehr is missing).

A quick hack is to edit : 
*/usr/local/lib/node_modules/bonescript/src/hw_mainline.js* and remove the 
*ehr* from line 95.

--Mark

On Tuesday, May 24, 2016 at 3:52:21 AM UTC-4, Baozhu Zuo wrote:
>
> I think there are some wrong with pwm driver on linux-v4.4 kernel. 
> run:
> var b = require('bonescript');
> b.pinMode('P9_14', b.OUTPUT);
> b.analogWrite('P9_14', 0.7, 2000.0, printStatus);
> function printStatus(x) {
> console.log('x.value = ' + x.value);
> console.log('x.err = ' + x.err);
> }
> output:
> x.err = error updating PWM freq and value: undefined/pwm0, Error: ENOENT, 
> no such file or directory 'undefined/pwm0/period'
>
> root@beaglebone:~/workspace# ls /sys/class/pwm/
> pwmchip0  pwmchip2  pwmchip4  pwmchip5pwmchip6
>
> the export and unexport file disappeared.
>
>
> 在 2016年5月6日星期五 UTC+8上午5:27:39，robert nelson写道：
>>
>>
>>
>> On Thu, May 5, 2016 at 1:18 PM, Robert Nelson  
>> wrote:
>>
>>> Just a heads up, TI just landed two large changes to the v4.4.x tree 
>>> today:
>>>
>>>
>>> https://github.com/RobertCNelson/ti-linux-kernel/compare/584991ea2c87ead7ce1e0ef145a9e66a4408a9d5...ee87bb1741b3e2f05a5ff46b1ad59ca82b8f2514
>>>
>>> remoteproc_pruss & sgx
>>>
>>> remoteproc_pruss: this should be compatible with v4.1.x-ti
>>>
>>> sgx: the "modules" should build and enter the archive when the kernel 
>>> *.deb get's built..
>>>
>>
>> The sgx modules for stretch were successfully built, the build farm is 
>> currently working on all of them, so they should get pushed to the deb repo 
>> later tonight..
>>
>> Thus, the sgx flag in the ./update_kernel.sh script is now set, so it'll 
>> install the sgx modules by default for v4.4.x-ti kernel's going forward..
>>
>> 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/7b06ae48-5a2d-417c-aaf9-b1b8c1128706%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Schematic / BoM mismatch in /static/beaglebone/latest/Docs/Hardware/

[Buck Smith]

duh got it   sorry for the "dumb" question

On Wednesday, May 25, 2016 at 7:35:25 AM UTC-7, Gerald wrote:
>
> I just checked the link. This is the BeagleBone. It has 256MB which is 2 
> Giga Bit.
>
> Gerald
>
>
> On Wed, May 25, 2016 at 9:03 AM, Gerald Coley  > wrote:
>
>> The board uses 512MB DDR3. The previous version used 256MB.
>>
>> Gerald
>>
>>
>> On Wed, May 25, 2016 at 8:58 AM, Buck Smith > > wrote:
>>
>>> I was checking major components on the schematic file at 
>>>
>>>
>>> https://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SCH.pdf
>>>
>>>
>>> I noticed some differences with the Bill of Materials in BONE_BOM.xls in 
>>> the same folder. In particular the schematic has a  Micro 2 Gigabyte DDRAM 
>>> chip and the BoM has 256 Mbyte.  Is it possible these documents are not 
>>> synch'd?
>>>
>>> I will check github for same issue and report here.
>>>
>>> -- 
>>> 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 .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/4556bdc6-50e3-4f30-8ae3-f50ef7174b33%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> Gerald
>>  
>> ger...@beagleboard.org 
>> http://beagleboard.org/
>> gco...@emprodesign.com 
>>
>>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
> gco...@emprodesign.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/89135534-69ac-45ed-9745-f24d76a6bbc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] v4.5.3+/v4.6.x+: mmcblk re-number

[Robert Nelson]

Just a heads up, users will start to notice a mmcblk numbering change.
(specially on devices with a populated eMMC)

Due to these kernel commits:

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=520bd7a8b4152aacfbd34eb7f7a447354b631039

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=58821da858919f93f85c7e6823b49d439722a9e9

So, starting with v4.5.3 & v4.6.x  (v4.5-rc1 -> v4.5.2, mmc was a dice
roll..)

eMMC: mmc1 = /dev/mmcblk1
microSD: mmc0 = /dev/mmcblk0

In the past, whatever got detected "first" ended up as /dev/mmcblk0

So with microSD empty (prior to 4.5.x/4.5.3)

eMMC: mmc1 = /dev/mmcblk0

BUT now with v4.5.3+/v4.6.x+

microSD empty:
eMMC: mmc1 = /dev/mmcblk1

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/CAOCHtYiWMB1L9gZ_SSocmcSW_E6POSzAoErVGWodMGA-ncm9Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] dd between boards

[Robert Nelson]

On Wed, May 25, 2016 at 11:20 AM, Antoine Rennuit  wrote:

> Hi all,
>
> I have several BBB in my system (all rev C). I need them to be configured
> the same way so I thought about setting up one and copying the setup using
> dd between boards. In order to do this I used a uSD with 2 partitions, the
> first one containing a full system and the 2nd one aimed at storing the
> image from the eMMC.
>
> I create the custom image from eMMC of the source board to the uSD card
> via:
>
> *root@beaglebone:~# dd if=/dev/mmcblk1 of=/dev/mmcblk0p3 bs=16M*
> *234+0 records in*
> *234+0 records out*
> *3925868544 bytes (3.9 GB) copied, 306.985 s, 12.8 MB/s*
>
> and copy it from the uSD board to the eMMC of the destination board via:
>
> *root@beaglebone:~# dd if=/dev/mmcblk0p3 of=/dev/mmcblk1 bs=16M count=234*
> *234+0 records in*
> *234+0 records out*
> *3925868544 bytes (3.9 GB) copied, 583.641 s, 6.7 MB/s*
>
> The operations run correctly but when I restart the destination board, I
> can never reach (whether its is via SSH to 192.168.7.2 or to the IP set for
> eth0, it does not work). I have also tried doing the dd to a file rather
> than to a partition, and changed the bs, but none of these options work.
> The only configuration that works is *when the source and destination
> boards are the same* (which is useless).
>
> I initially thought I had bricked all my boards except the source, but
> then I tried to install an official flasher image (from Robert C. Nelson)
> on the destination boards, and it worked fine (at least with
> *BBB-eMMC-flasher-debian-8.4-console-armhf-2016-04-10-2gb.img.xz* and
> *BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz*). So my boards are
> actually not bricked.
>
> I then tried to dd an official *non-flasher* image (also coming from
> Robert C Nelson), by putting the non-flasher image on the 2nd partition of
> my uSD card, mounting this partition and doing *dd
> if=bone-debian-8.4-console-armhf-2016-04-10-2gb.img of=/dev/mmcblk1p1 *but
> I had no luck.
>
> So it seems I can install the official flasher images (using the
> auto-flashing system), but when I flash using dd it does not work (whether
> I flash custom or official images). This gives me the feeling that the
> different boards are slightly different in hardware, could this be
> possible? Could this come from dead sectors in the eMMC? Is there a way to
> use the auto-flashing system with a custom image?
>
> I have looked for days on the internet how to go forward and get my dds
> right but cannot find any answer.
>
> Any idea of what I am doing wrong?
>

Don't bother with dd. ;)

Under:

/opt/scripts/tools/eMMC

run "git pull" then

sudo ./beaglebone-black-make-microSD-flasher-from-eMMC.sh

It'll "create an eMMC flasher based on the contents of the eMMC"..  Make
sure to insert a new microSD card..

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_%2By2iwuy1UBFiBDn9rZx5JH4dhqNCMAxO8AE3FYyQ%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] dd between boards

[Antoine Rennuit]

Hi all,

I have several BBB in my system (all rev C). I need them to be configured 
the same way so I thought about setting up one and copying the setup using 
dd between boards. In order to do this I used a uSD with 2 partitions, the 
first one containing a full system and the 2nd one aimed at storing the 
image from the eMMC.

I create the custom image from eMMC of the source board to the uSD card via:

*root@beaglebone:~# dd if=/dev/mmcblk1 of=/dev/mmcblk0p3 bs=16M*
*234+0 records in*
*234+0 records out*
*3925868544 bytes (3.9 GB) copied, 306.985 s, 12.8 MB/s*

and copy it from the uSD board to the eMMC of the destination board via:

*root@beaglebone:~# dd if=/dev/mmcblk0p3 of=/dev/mmcblk1 bs=16M count=234*
*234+0 records in*
*234+0 records out*
*3925868544 bytes (3.9 GB) copied, 583.641 s, 6.7 MB/s*

The operations run correctly but when I restart the destination board, I 
can never reach (whether its is via SSH to 192.168.7.2 or to the IP set for 
eth0, it does not work). I have also tried doing the dd to a file rather 
than to a partition, and changed the bs, but none of these options work. 
The only configuration that works is *when the source and destination 
boards are the same* (which is useless).

I initially thought I had bricked all my boards except the source, but then 
I tried to install an official flasher image (from Robert C. Nelson) on the 
destination boards, and it worked fine (at least with 
*BBB-eMMC-flasher-debian-8.4-console-armhf-2016-04-10-2gb.img.xz* and 
*BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz*). So my boards are 
actually not bricked.

I then tried to dd an official *non-flasher* image (also coming from Robert 
C Nelson), by putting the non-flasher image on the 2nd partition of my uSD 
card, mounting this partition and doing *dd 
if=bone-debian-8.4-console-armhf-2016-04-10-2gb.img of=/dev/mmcblk1p1 *but 
I had no luck.

So it seems I can install the official flasher images (using the 
auto-flashing system), but when I flash using dd it does not work (whether 
I flash custom or official images). This gives me the feeling that the 
different boards are slightly different in hardware, could this be 
possible? Could this come from dead sectors in the eMMC? Is there a way to 
use the auto-flashing system with a custom image?

I have looked for days on the internet how to go forward and get my dds 
right but cannot find any answer.

Any idea of what I am doing wrong?

Thanks,

Antoine.

-- 
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/fad78b5a-24a8-4046-88bb-24ab41527af5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[Tinashe Mudavanhu]

Silva,

There has to be way. Dereck Molloy
https://www.youtube.com/watch?v=8QouvYMfmQo was able to get a video stream
then its possible to video stream with BBB. I don't have much time to look
for another development board because the Project is due next week.

On Wed, May 25, 2016 at 5:48 PM, Tinashe Mudavanhu 
wrote:

> Hi,
>
> The same is happening on the other webcam i have (not sure if its openCV
> changing resolution). I bought it on AliExpress and has the following
> discription; HD 1.3 megapixel 960p 2.8-12mm varifocal lens Aptina AR0130
> android external usb camera module with IR cut ELP-USB130W01MT-FV
> .
> The supplier can be found on http://www.elpcctv.com.
>
> Since there are no errors, what could be the problem? Is there some
> dependencies i have to install?
>
> I tested with your framebrabber.c code and was getting this (see below)
> with the Logitech webcam,
>
> root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c 1000 -I
> 30
> Startup took 0.01 seconds
> Captured 1000 frames in 0.22 seconds
> Shutdown took 0.00 seconds
>
>
> real0m42.068s
> user0m0.025s
> sys0m0.223s
>
> The no name webcam was giving the following results;
> root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c 1000 -I
> 30
> Startup took 0.02 seconds
> Captured 1000 frames in 0.26 seconds
> Shutdown took 0.00 seconds
>
>
> real2m10.965s
> user0m0.033s
> sys0m0.262s
> root@beaglebone:~#
>
>
>
> On Wed, May 25, 2016 at 5:23 PM, Matthew Witherwax 
> wrote:
>
>> There are no actual errors in the output you posted.
>>
>> Do you have access to any other webcams?  I have tested this with the
>> Logitech C920, the Logitech C270, and the PS3Eye.  Without access to your
>> webcam, it is hard for me to look into what is going on.
>>
>>
>> On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe Mudavanhu wrote:
>>
>>> The timeout error resurfaced again, i followed you blog post on
>>> http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html but
>>> got the following errors in compiling libjpeg-turbo ;
>>>
>>> root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
>>> make  all-recursive
>>> make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
>>> Making all in java
>>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/java'
>>> make[2]: Nothing to be done for `all'.
>>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/java'
>>> Making all in simd
>>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
>>> make  all-am
>>> make[3]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
>>> make[3]: Nothing to be done for `all-am'.
>>> make[3]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
>>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
>>> Making all in md5
>>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/md5'
>>> make[2]: Nothing to be done for `all'.
>>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
>>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
>>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
>>> make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
>>> root@beaglebone:~/libjpeg-turbo-1.3.0/build#
>>>
>>>
>>> Before compiling libjpeg-turbo i tested my code to see what will be
>>> happening on the resolution and frame rate. I am working with a Logitech
>>> QuickCam E3500 which has support for both YUVY and MJPEG. I set the
>>> resolution to 320x240 with a 30fps frame rate but after running the code,
>>> got select timeout errors and the resolution had changed to 640x480 YUVY
>>> with a 15fps frame rate;
>>>
>>> root@beaglebone:~/libjpeg-turbo-1.3.0/build# v4l2-ctl -V
>>> Format Video Capture:
>>> Width/Height  : 640/480
>>> Pixel Format  : 'YUYV'
>>> Field : None
>>> Bytes per Line: 1280
>>> Size Image: 614400
>>> Colorspace: SRGB
>>> root@beaglebone:~/libjpeg-turbo-1.3.0/build#
>>>
>>>
>>>
>>>
>>> On Tue, May 24, 2016 at 1:22 AM, Tinashe Mudavanhu 
>>> wrote:
>>>
 Hi Matthew,

 I'm a rookie in this linux/opencv area i wouldn't really know what it
 means, only learning from you. I posted a question
 https://groups.google.com/forum/#!category-topic/beagleboard/debian/VFuvveM_8Gc
 looking for a solution because it always happened when i plugged in the
 webcam on BBB. Running the command i previously mentioned ended my woes.

 On Tue, May 24, 2016 at 1:04 AM, Matthew Witherwax 
 wrote:

> The issue causing the select time out detailed in my article has to do
> with how much data is being sent over the USB and how it is sent. Reducing
> the frame rate reduces the load on the USB. Looking at the articles you
> linked, one says it solved an issue but not the select timeout, an

Re: [beagleboard] Re: VGA camera capture

[Tinashe Mudavanhu]

Hi,

The same is happening on the other webcam i have (not sure if its openCV
changing resolution). I bought it on AliExpress and has the following
discription; HD 1.3 megapixel 960p 2.8-12mm varifocal lens Aptina AR0130
android external usb camera module with IR cut ELP-USB130W01MT-FV
.
The supplier can be found on http://www.elpcctv.com.

Since there are no errors, what could be the problem? Is there some
dependencies i have to install?

I tested with your framebrabber.c code and was getting this (see below)
with the Logitech webcam,

root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c 1000 -I 30
Startup took 0.01 seconds
Captured 1000 frames in 0.22 seconds
Shutdown took 0.00 seconds


real0m42.068s
user0m0.025s
sys0m0.223s

The no name webcam was giving the following results;
root@beaglebone:~# time ./framegrabber -f mjpeg -H 480 -W 640 -c 1000 -I 30
Startup took 0.02 seconds
Captured 1000 frames in 0.26 seconds
Shutdown took 0.00 seconds


real2m10.965s
user0m0.033s
sys0m0.262s
root@beaglebone:~#



On Wed, May 25, 2016 at 5:23 PM, Matthew Witherwax 
wrote:

> There are no actual errors in the output you posted.
>
> Do you have access to any other webcams?  I have tested this with the
> Logitech C920, the Logitech C270, and the PS3Eye.  Without access to your
> webcam, it is hard for me to look into what is going on.
>
>
> On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe Mudavanhu wrote:
>
>> The timeout error resurfaced again, i followed you blog post on
>> http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html but
>> got the following errors in compiling libjpeg-turbo ;
>>
>> root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
>> make  all-recursive
>> make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
>> Making all in java
>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/java'
>> make[2]: Nothing to be done for `all'.
>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/java'
>> Making all in simd
>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
>> make  all-am
>> make[3]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
>> make[3]: Nothing to be done for `all-am'.
>> make[3]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
>> Making all in md5
>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/md5'
>> make[2]: Nothing to be done for `all'.
>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
>> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
>> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
>> make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
>> root@beaglebone:~/libjpeg-turbo-1.3.0/build#
>>
>>
>> Before compiling libjpeg-turbo i tested my code to see what will be
>> happening on the resolution and frame rate. I am working with a Logitech
>> QuickCam E3500 which has support for both YUVY and MJPEG. I set the
>> resolution to 320x240 with a 30fps frame rate but after running the code,
>> got select timeout errors and the resolution had changed to 640x480 YUVY
>> with a 15fps frame rate;
>>
>> root@beaglebone:~/libjpeg-turbo-1.3.0/build# v4l2-ctl -V
>> Format Video Capture:
>> Width/Height  : 640/480
>> Pixel Format  : 'YUYV'
>> Field : None
>> Bytes per Line: 1280
>> Size Image: 614400
>> Colorspace: SRGB
>> root@beaglebone:~/libjpeg-turbo-1.3.0/build#
>>
>>
>>
>>
>> On Tue, May 24, 2016 at 1:22 AM, Tinashe Mudavanhu 
>> wrote:
>>
>>> Hi Matthew,
>>>
>>> I'm a rookie in this linux/opencv area i wouldn't really know what it
>>> means, only learning from you. I posted a question
>>> https://groups.google.com/forum/#!category-topic/beagleboard/debian/VFuvveM_8Gc
>>> looking for a solution because it always happened when i plugged in the
>>> webcam on BBB. Running the command i previously mentioned ended my woes.
>>>
>>> On Tue, May 24, 2016 at 1:04 AM, Matthew Witherwax 
>>> wrote:
>>>
 The issue causing the select time out detailed in my article has to do
 with how much data is being sent over the USB and how it is sent. Reducing
 the frame rate reduces the load on the USB. Looking at the articles you
 linked, one says it solved an issue but not the select timeout, and the
 other shows an error message that says it could not allocate memory.
 Neither one of these are the cause of the select timeout I addressed.

 The select timeout occurs when the select times out. Looks like in the
 cases in your links a previous call to allocate memory failed followed by
 select failing. I have never had an issue with memory allocation. All my
 troubles had to do with too much data on the USB. You might want to confir

Re: [beagleboard] Re: VGA camera capture

[Matthew Witherwax]

There are no actual errors in the output you posted.

Do you have access to any other webcams?  I have tested this with the 
Logitech C920, the Logitech C270, and the PS3Eye.  Without access to your 
webcam, it is hard for me to look into what is going on.

On Wednesday, May 25, 2016 at 8:57:55 AM UTC-5, Tinashe Mudavanhu wrote:
>
> The timeout error resurfaced again, i followed you blog post on  
> http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html but 
> got the following errors in compiling libjpeg-turbo ;
>
> root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
> make  all-recursive
> make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
> Making all in java
> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/java'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/java'
> Making all in simd
> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
> make  all-am
> make[3]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
> Making all in md5
> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/md5'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
> make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
> make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
> make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
> root@beaglebone:~/libjpeg-turbo-1.3.0/build# 
>
>
> Before compiling libjpeg-turbo i tested my code to see what will be 
> happening on the resolution and frame rate. I am working with a Logitech 
> QuickCam E3500 which has support for both YUVY and MJPEG. I set the 
> resolution to 320x240 with a 30fps frame rate but after running the code, 
> got select timeout errors and the resolution had changed to 640x480 YUVY 
> with a 15fps frame rate;
>
> root@beaglebone:~/libjpeg-turbo-1.3.0/build# v4l2-ctl -V
> Format Video Capture:
> Width/Height  : 640/480
> Pixel Format  : 'YUYV'
> Field : None
> Bytes per Line: 1280
> Size Image: 614400
> Colorspace: SRGB
> root@beaglebone:~/libjpeg-turbo-1.3.0/build# 
>
>
>
>
> On Tue, May 24, 2016 at 1:22 AM, Tinashe Mudavanhu  > wrote:
>
>> Hi Matthew,
>>
>> I'm a rookie in this linux/opencv area i wouldn't really know what it 
>> means, only learning from you. I posted a question 
>> https://groups.google.com/forum/#!category-topic/beagleboard/debian/VFuvveM_8Gc
>>  
>> looking for a solution because it always happened when i plugged in the 
>> webcam on BBB. Running the command i previously mentioned ended my woes.
>>
>> On Tue, May 24, 2016 at 1:04 AM, Matthew Witherwax > > wrote:
>>
>>> The issue causing the select time out detailed in my article has to do 
>>> with how much data is being sent over the USB and how it is sent. Reducing 
>>> the frame rate reduces the load on the USB. Looking at the articles you 
>>> linked, one says it solved an issue but not the select timeout, and the 
>>> other shows an error message that says it could not allocate memory.  
>>> Neither one of these are the cause of the select timeout I addressed. 
>>>
>>> The select timeout occurs when the select times out. Looks like in the 
>>> cases in your links a previous call to allocate memory failed followed by 
>>> select failing. I have never had an issue with memory allocation. All my 
>>> troubles had to do with too much data on the USB. You might want to confirm 
>>> what your actual problem is. 
>>> --
>>> From: Tinashe Mudavanhu 
>>> Sent: ‎5/‎23/‎2016 4:58 PM
>>> To: beagl...@googlegroups.com 
>>> Subject: Re: [beagleboard] Re: VGA camera capture
>>>
>>> Hi Matthew,
>>>
>>> I looked into the article as i went through your discussion but did not 
>>> try the framegrabber.c, will test it though. I finally got a solution to 
>>> the problem from links listed below. It kind of made sense to me (lack of 
>>> memory in ARM systems) because running the same code on my PC worked 
>>> perfectly well. Running this command `sysctl vm.overcommit_memory=1` worked 
>>> for me after a long struggle. What i'm not really sure are the implications 
>>> (being it on Hardware or Software) if there comes a state when large size 
>>> memory is really needed.
>>>
>>>
>>>   [1]: https://www.raspberrypi.org/forums/viewtopic.php?f=31&t=17773
>>>   [2]: 
>>> https://tequals0.wordpress.com/2014/03/24/libv4l2-error-allocation-conversion-buffer-using-opencv-on-a-pi/
>>>
>>> On Mon, May 23, 2016 at 10:25 PM, Matthew Witherwax >> > wrote:
>>>
 Hi Tinashe,

 Please see my article here 
 http://blog.lemoneerlabs.com/post/BBB-webcams
 There is a version of framegrabber.c linked to it that allows you to 
 specify the frame rate with the command li

Re: [beagleboard] Schematic / BoM mismatch in /static/beaglebone/latest/Docs/Hardware/

[evilwulfie]

Whats a few bytes between friends.

On 5/25/2016 7:35 AM, Gerald Coley wrote:
> I just checked the link. This is the BeagleBone. It has 256MB which is
> 2 Giga Bit.
>
> Gerald
>
>
> On Wed, May 25, 2016 at 9:03 AM, Gerald Coley  > wrote:
>
> The board uses 512MB DDR3. The previous version used 256MB.
>
> Gerald
>
>
> On Wed, May 25, 2016 at 8:58 AM, Buck Smith  > wrote:
>
> I was checking major components on the schematic file at 
>
> 
> https://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SCH.pdf
>
>
> I noticed some differences with the Bill of Materials in
> BONE_BOM.xls in the same folder. In particular the schematic
> has a  Micro 2 Gigabyte DDRAM chip and the BoM has 256 Mbyte. 
> Is it possible these documents are not synch'd?
>
> I will check github for same issue and report here.
> -- 
> 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/4556bdc6-50e3-4f30-8ae3-f50ef7174b33%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
> gcol...@emprodesign.com 
>
>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
> gcol...@emprodesign.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/CAHK_S%2BcGZwwdeOFiR-ePF5xUNnoxzcArpO-CWLdG62SpP_R15g%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/eb6621f8-aeac-9a9c-fd6b-14b980b47183%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Schematic / BoM mismatch in /static/beaglebone/latest/Docs/Hardware/

[Gerald Coley]

I just checked the link. This is the BeagleBone. It has 256MB which is 2
Giga Bit.

Gerald


On Wed, May 25, 2016 at 9:03 AM, Gerald Coley 
wrote:

> The board uses 512MB DDR3. The previous version used 256MB.
>
> Gerald
>
>
> On Wed, May 25, 2016 at 8:58 AM, Buck Smith  wrote:
>
>> I was checking major components on the schematic file at
>>
>>
>> https://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SCH.pdf
>>
>>
>> I noticed some differences with the Bill of Materials in BONE_BOM.xls in
>> the same folder. In particular the schematic has a  Micro 2 Gigabyte DDRAM
>> chip and the BoM has 256 Mbyte.  Is it possible these documents are not
>> synch'd?
>>
>> I will check github for same issue and report here.
>>
>> --
>> 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/4556bdc6-50e3-4f30-8ae3-f50ef7174b33%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Gerald
>
> ger...@beagleboard.org
> http://beagleboard.org/
> gcol...@emprodesign.com
>
>


-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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/CAHK_S%2BcGZwwdeOFiR-ePF5xUNnoxzcArpO-CWLdG62SpP_R15g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[João M . S . Silva]

Hi Tinashe,

My two cents:


root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
make  all-recursive
make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
Making all in java
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/java'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/java'
Making all in simd
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
make  all-am
make[3]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
Making all in md5
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
root@beaglebone:~/libjpeg-turbo-1.3.0/build#


There is no error above.


Before compiling libjpeg-turbo i tested my code to see what will be
happening on the resolution and frame rate. I am working with a Logitech
QuickCam E3500 which has support for both YUVY and MJPEG. I set the
resolution to 320x240 with a 30fps frame rate but after running the
code, got select timeout errors and the resolution had changed to
640x480 YUVY with a 15fps frame rate;


Due to this, among other reasons, we gave up on the BeagleBone Black and 
are now using an A20-OLinuXino-LIME.


João M. S. Silva

--
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/5745B238.8020505%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Schematic / BoM mismatch in /static/beaglebone/latest/Docs/Hardware/

[Gerald Coley]

The board uses 512MB DDR3. The previous version used 256MB.

Gerald


On Wed, May 25, 2016 at 8:58 AM, Buck Smith  wrote:

> I was checking major components on the schematic file at
>
> https://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SCH.pdf
>
>
> I noticed some differences with the Bill of Materials in BONE_BOM.xls in
> the same folder. In particular the schematic has a  Micro 2 Gigabyte DDRAM
> chip and the BoM has 256 Mbyte.  Is it possible these documents are not
> synch'd?
>
> I will check github for same issue and report here.
>
> --
> 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/4556bdc6-50e3-4f30-8ae3-f50ef7174b33%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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/CAHK_S%2BdFoUay%3D2k9M0rTtkjhcAHyVhebJo5UwZxATdQ5sXhsnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Schematic / BoM mismatch in /static/beaglebone/latest/Docs/Hardware/

[Buck Smith]

I was checking major components on the schematic file at 

https://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SCH.pdf


I noticed some differences with the Bill of Materials in BONE_BOM.xls in 
the same folder. In particular the schematic has a  Micro 2 Gigabyte DDRAM 
chip and the BoM has 256 Mbyte.  Is it possible these documents are not 
synch'd?

I will check github for same issue and report here.

-- 
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/4556bdc6-50e3-4f30-8ae3-f50ef7174b33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: VGA camera capture

[Tinashe Mudavanhu]

The timeout error resurfaced again, i followed you blog post on
http://blog.lemoneerlabs.com/3rdParty/Darling_BBB_30fps_DRAFT.html but got
the following errors in compiling libjpeg-turbo ;

root@beaglebone:~/libjpeg-turbo-1.3.0/build# make
make  all-recursive
make[1]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
Making all in java
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/java'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/java'
Making all in simd
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
make  all-am
make[3]: Entering directory `/root/libjpeg-turbo-1.3.0/build/simd'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/simd'
Making all in md5
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build/md5'
make[2]: Entering directory `/root/libjpeg-turbo-1.3.0/build'
make[2]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
make[1]: Leaving directory `/root/libjpeg-turbo-1.3.0/build'
root@beaglebone:~/libjpeg-turbo-1.3.0/build#


Before compiling libjpeg-turbo i tested my code to see what will be
happening on the resolution and frame rate. I am working with a Logitech
QuickCam E3500 which has support for both YUVY and MJPEG. I set the
resolution to 320x240 with a 30fps frame rate but after running the code,
got select timeout errors and the resolution had changed to 640x480 YUVY
with a 15fps frame rate;

root@beaglebone:~/libjpeg-turbo-1.3.0/build# v4l2-ctl -V
Format Video Capture:
Width/Height  : 640/480
Pixel Format  : 'YUYV'
Field : None
Bytes per Line: 1280
Size Image: 614400
Colorspace: SRGB
root@beaglebone:~/libjpeg-turbo-1.3.0/build#




On Tue, May 24, 2016 at 1:22 AM, Tinashe Mudavanhu 
wrote:

> Hi Matthew,
>
> I'm a rookie in this linux/opencv area i wouldn't really know what it
> means, only learning from you. I posted a question
> https://groups.google.com/forum/#!category-topic/beagleboard/debian/VFuvveM_8Gc
> looking for a solution because it always happened when i plugged in the
> webcam on BBB. Running the command i previously mentioned ended my woes.
>
> On Tue, May 24, 2016 at 1:04 AM, Matthew Witherwax 
> wrote:
>
>> The issue causing the select time out detailed in my article has to do
>> with how much data is being sent over the USB and how it is sent. Reducing
>> the frame rate reduces the load on the USB. Looking at the articles you
>> linked, one says it solved an issue but not the select timeout, and the
>> other shows an error message that says it could not allocate memory.
>> Neither one of these are the cause of the select timeout I addressed.
>>
>> The select timeout occurs when the select times out. Looks like in the
>> cases in your links a previous call to allocate memory failed followed by
>> select failing. I have never had an issue with memory allocation. All my
>> troubles had to do with too much data on the USB. You might want to confirm
>> what your actual problem is.
>> --
>> From: Tinashe Mudavanhu 
>> Sent: ‎5/‎23/‎2016 4:58 PM
>> To: beagleboard@googlegroups.com
>> Subject: Re: [beagleboard] Re: VGA camera capture
>>
>> Hi Matthew,
>>
>> I looked into the article as i went through your discussion but did not
>> try the framegrabber.c, will test it though. I finally got a solution to
>> the problem from links listed below. It kind of made sense to me (lack of
>> memory in ARM systems) because running the same code on my PC worked
>> perfectly well. Running this command `sysctl vm.overcommit_memory=1` worked
>> for me after a long struggle. What i'm not really sure are the implications
>> (being it on Hardware or Software) if there comes a state when large size
>> memory is really needed.
>>
>>
>>   [1]: https://www.raspberrypi.org/forums/viewtopic.php?f=31&t=17773
>>   [2]:
>> https://tequals0.wordpress.com/2014/03/24/libv4l2-error-allocation-conversion-buffer-using-opencv-on-a-pi/
>>
>> On Mon, May 23, 2016 at 10:25 PM, Matthew Witherwax 
>> wrote:
>>
>>> Hi Tinashe,
>>>
>>> Please see my article here http://blog.lemoneerlabs.com/post/BBB-webcams
>>> There is a version of framegrabber.c linked to it that allows you to
>>> specify the frame rate with the command line parameter -I.  If reducing the
>>> frame rate works for you, then the code for framegrabber should provide a
>>> starting point for accomplishing the same thing in your own program.
>>>
>>> On Mon, May 23, 2016 at 2:43 PM, Tinashe Mudavanhu 
>>> wrote:
>>>
 Firstly i would like to say i came across your discussion looking for
 select timeout error solution but as i went through it i didnt notice if
 you found a solution, but if you have it now, i would appreciate it. The
 select timeout error still

Re: [beagleboard] Analog IO with C/C++ code

[Robert Nelson]

On Wed, May 25, 2016 at 7:54 AM, Justin Reina 
wrote:

> Hi John,
>  I hope you know how dang excited I was to brush into your code response
> earlier this week, whilst at work as I browsed my Gmail inbox - sheesh &
> wow I got home though and could not find these search paths!
>
> *Issue:* I cannot find /iio or /device0 on my BBB
>
>
> *Useful Context:*
> root@beaglebone:/# pwd
> /
> root@beaglebone:/# find / -type d -name iio
> /lib/modules/4.4.9-ti-r25/kernel/drivers/iio
> /lib/modules/4.4.9-ti-r25/kernel/drivers/staging/iio
> /usr/src/linux-headers-4.4.9-ti-r25/tools/iio
> /usr/src/linux-headers-4.4.9-ti-r25/drivers/iio
> /usr/src/linux-headers-4.4.9-ti-r25/drivers/staging/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/config/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/config/hid/sensor/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/config/sensors/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/linux/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/dt-bindings/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/uapi/linux/iio
> /opt/source/dtb-4.4-ti/Bindings/iio
> /opt/source/dtb-4.4-ti/Bindings/staging/iio
> /opt/source/dtb-4.4-ti/include/dt-bindings/iio
> root@beaglebone:/# find / -type d -name device0
> root@beaglebone:/# find / -type d -name device0
> root@beaglebone:/# find / -type d -name scan_elements
>
> *Question:* What is the cause here of these paths not showing up? I am
> running Jessie 8.4, grabbed and flashed earlier this week!
>
> Thanks again for your help here John :)
>


in /boot/uEnv.txt, add:

cape_enable=bone_capemgr.enable_partno=BB-ADC

and reboot..

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/CAOCHtYjR0p%2BqoLGQ6agXkqDjkQPjFytDdC%2BLvCe1Tph7c4fsag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Analog IO with C/C++ code

[Justin Reina]

Here is a case where iio was not installed by default -

   - https://gist.github.com/matthewmcneely/bf44655c74096ff96475

thoughts?

-J


On Wednesday, May 25, 2016 at 5:54:39 AM UTC-7, Justin Reina wrote:
>
> Hi John,
>  I hope you know how dang excited I was to brush into your code response 
> earlier this week, whilst at work as I browsed my Gmail inbox - sheesh & 
> wow I got home though and could not find these search paths!
>
> *Issue:* I cannot find /iio or /device0 on my BBB
>
>
> *Useful Context:*
> root@beaglebone:/# pwd
> /
> root@beaglebone:/# find / -type d -name iio
> /lib/modules/4.4.9-ti-r25/kernel/drivers/iio
> /lib/modules/4.4.9-ti-r25/kernel/drivers/staging/iio
> /usr/src/linux-headers-4.4.9-ti-r25/tools/iio
> /usr/src/linux-headers-4.4.9-ti-r25/drivers/iio
> /usr/src/linux-headers-4.4.9-ti-r25/drivers/staging/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/config/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/config/hid/sensor/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/config/sensors/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/linux/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/dt-bindings/iio
> /usr/src/linux-headers-4.4.9-ti-r25/include/uapi/linux/iio
> /opt/source/dtb-4.4-ti/Bindings/iio
> /opt/source/dtb-4.4-ti/Bindings/staging/iio
> /opt/source/dtb-4.4-ti/include/dt-bindings/iio
> root@beaglebone:/# find / -type d -name device0
> root@beaglebone:/# find / -type d -name device0
> root@beaglebone:/# find / -type d -name scan_elements
>
> *Question:* What is the cause here of these paths not showing up? I am 
> running Jessie 8.4, grabbed and flashed earlier this week!
>
> Thanks again for your help here John :)
>
> -Justin
>   justinmre...@gmail.com
>
>
> On Monday, May 23, 2016 at 9:31:13 AM UTC-7, john3909 wrote:
>>
>> See the answer to your posting from yesterday.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On May 22, 2016, at 7:39 PM, justin...@gmail.com wrote:
>>
>> Hi guys,
>>  Alright I submit, I give in and come to you and now ask for help. I am 
>> amiss as to how this has been so magically elusive, but it has!
>>
>>
>> *Question*
>> How can you do Analog Input and Analog Output of discrete values from 
>> either a terminal or C/C++ code?
>>
>>
>> *Specific Hardware*
>> BeagleBone Black Rev. C, Debian Jessie 8.4
>>
>>
>> *Research*
>> I have found discussions claiming AIO support for the BBB, but these both 
>> were greater than 3 years old and referenced non-existant directories in 
>> the file system!
>>
>> I have also found a plethora of Bonescript solutions
>>
>>
>> I am still amiss as to how this is not BBB-101 and the f*irst* example 
>> code you encounter!
>>
>> Please let me know where to look for reference and example, and get this 
>> in action!
>>
>> Thanks :)
>>   Justin Reina
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/b9a4e067-de33-46d1-a3bc-cc9a5d556643%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/14506a4c-2fcc-4f75-bc3b-cd3b87cc6e3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Analog IO with C/C++ code

[Justin Reina]

Hi John,
 I hope you know how dang excited I was to brush into your code response 
earlier this week, whilst at work as I browsed my Gmail inbox - sheesh & 
wow I got home though and could not find these search paths!

*Issue:* I cannot find /iio or /device0 on my BBB


*Useful Context:*
root@beaglebone:/# pwd
/
root@beaglebone:/# find / -type d -name iio
/lib/modules/4.4.9-ti-r25/kernel/drivers/iio
/lib/modules/4.4.9-ti-r25/kernel/drivers/staging/iio
/usr/src/linux-headers-4.4.9-ti-r25/tools/iio
/usr/src/linux-headers-4.4.9-ti-r25/drivers/iio
/usr/src/linux-headers-4.4.9-ti-r25/drivers/staging/iio
/usr/src/linux-headers-4.4.9-ti-r25/include/config/iio
/usr/src/linux-headers-4.4.9-ti-r25/include/config/hid/sensor/iio
/usr/src/linux-headers-4.4.9-ti-r25/include/config/sensors/iio
/usr/src/linux-headers-4.4.9-ti-r25/include/linux/iio
/usr/src/linux-headers-4.4.9-ti-r25/include/dt-bindings/iio
/usr/src/linux-headers-4.4.9-ti-r25/include/uapi/linux/iio
/opt/source/dtb-4.4-ti/Bindings/iio
/opt/source/dtb-4.4-ti/Bindings/staging/iio
/opt/source/dtb-4.4-ti/include/dt-bindings/iio
root@beaglebone:/# find / -type d -name device0
root@beaglebone:/# find / -type d -name device0
root@beaglebone:/# find / -type d -name scan_elements

*Question:* What is the cause here of these paths not showing up? I am 
running Jessie 8.4, grabbed and flashed earlier this week!

Thanks again for your help here John :)

-Justin
  justinmre...@gmail.com


On Monday, May 23, 2016 at 9:31:13 AM UTC-7, john3909 wrote:
>
> See the answer to your posting from yesterday.
>
> Regards,
> John
>
>
>
>
> On May 22, 2016, at 7:39 PM, justin...@gmail.com  wrote:
>
> Hi guys,
>  Alright I submit, I give in and come to you and now ask for help. I am 
> amiss as to how this has been so magically elusive, but it has!
>
>
> *Question*
> How can you do Analog Input and Analog Output of discrete values from 
> either a terminal or C/C++ code?
>
>
> *Specific Hardware*
> BeagleBone Black Rev. C, Debian Jessie 8.4
>
>
> *Research*
> I have found discussions claiming AIO support for the BBB, but these both 
> were greater than 3 years old and referenced non-existant directories in 
> the file system!
>
> I have also found a plethora of Bonescript solutions
>
>
> I am still amiss as to how this is not BBB-101 and the f*irst* example 
> code you encounter!
>
> Please let me know where to look for reference and example, and get this 
> in action!
>
> Thanks :)
>   Justin Reina
>
> -- 
> 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 .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/b9a4e067-de33-46d1-a3bc-cc9a5d556643%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/f1521ac7-a677-44e1-8317-513dd0dc3f62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Http server in Cloud9 autorun

[bchengcong]

Hello, 
I have been creating my http server running in BBB with the standard 
method, create an server and listen in port .. 
*var server = http.createServer(function (req, res) {}).listen()*; And 
it works fine. 

But when i placed the JS file in cloud9/autorun folder, it dosen't work 
anymore. As i understand, the autorun program has already occupied the 
listening port , and caused the conflict of using port .

So i wonder if there is any solution behind this? Can't i use both of 
autorun mecanism and listening port , or i have to give up one of these 
two? Or there is another port number to use to build the http server?   

Thanks,
Chen



-- 
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/fb99adf0-947b-4e6e-b3d0-bbe00308e959%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Flashing the on-board eMMC of the BB Green with new image

[cpe . 3bdalla]

Hello

I got confused reading about this issue so some question came up: 

Can you please tell me the correct way to flash the eMMC with new image? 
And also what is the correct way to boot only from SD-Card without flashing 
on-board eMMC?
Will any pre-built image copied with either Win32DiskImager or Linux dd 
work when flashing the eMMC?
What is the flasher image and what is the difference between it and the 
pre-built image?

Thanks in advance.

-- 
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/474a3a35-3027-4a74-9f23-a1cb3373be5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Missing kernel headers/images, how can I build my own?

[Marcos Scriven]

At the risk of sounding like a sales agent, they serve some pretty large 
OSS projects: https://bintray.com/ 

On Tuesday, May 24, 2016 at 8:17:35 PM UTC+1, RobertCNelson wrote:
>
>
>
> On Tue, May 24, 2016 at 2:14 PM, Marcos Scriven  > wrote:
>
>> Sorry, really I meant BinTray (there's a free tier for OSS project, which 
>> this is obviously. You don't really need Artifactory per se)
>>
>
> They'd probably kick me off pretty quick, right now on average i'm pushing 
> 1.5 TB a month to our users.
>
> I should just pull the trigger and upgrade it, but i'll need to find a 3 
> hour down time slot.. ;)
>
> 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/7396b30c-3657-4f39-a30c-79d4db41755c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Missing kernel headers/images, how can I build my own?

[Marcos Scriven]

One other thing for posterity - the significance of version 4.1.6-bone15 is 
that's the kernel the current Kamikaze image uses.

On Tuesday, May 24, 2016 at 8:17:35 PM UTC+1, RobertCNelson wrote:
>
>
>
> On Tue, May 24, 2016 at 2:14 PM, Marcos Scriven  > wrote:
>
>> Sorry, really I meant BinTray (there's a free tier for OSS project, which 
>> this is obviously. You don't really need Artifactory per se)
>>
>
> They'd probably kick me off pretty quick, right now on average i'm pushing 
> 1.5 TB a month to our users.
>
> I should just pull the trigger and upgrade it, but i'll need to find a 3 
> hour down time slot.. ;)
>
> 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/f7d1cd8c-ff21-4f3b-979f-0da46143d50c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Driver Development : SPI or 4 wire Interface on BBB

[John Syne]

Just Google “am335x pru”

http://processors.wiki.ti.com/index.php/PRU-ICSS 


Regards,
John




> On May 25, 2016, at 12:33 AM, Raul Piper  wrote:
> 
> What is PRU?Can you post a link or keywords related to it.?
> 
> On Tuesday, May 24, 2016 at 11:43:09 PM UTC+5:30, john3909 wrote:
> Best to use the PRU and control the I/O with software.
> 
> Regards,
> John
> 
> 
> 
> 
>> On May 24, 2016, at 6:25 AM, Raul Piper > 
>> wrote:
>> 
>> My Question was Can CS be selectively made High or Low at nth or pth Clock 
>> Pulse while using/writing the SPI driver?
>> 
>> On Monday, May 23, 2016 at 9:59:14 PM UTC+5:30, john3909 wrote:
>> Here are the possible solutions:
>> 
>> 1) Use spidev which allows a user space application to communicate with a 
>> device over SPI
>> 2) Use PRU to communicate with device over SPI
>> 3) Develop a device driver to communicate with device over SPI
>> 4) Adapt an IIO driver that is similar to your device
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On May 23, 2016, at 4:34 AM, Raul Piper > wrote:
>>> 
>>> I am developing a driver for a hardware whose datasheet says it has a 4 
>>> wire Serial interface .DataIN/OUT,Clock,CS .Does it means I can develop a 
>>> full fledged SPI driver on Linux to use it.
>>> To add more when the CLK has n-n+1(say 3-4) rising edge with LE = 1 certain 
>>> control register will be written .Value of n depends on the type of control 
>>> register.
>>> Will it be good to develop a SPI driver for this or this can be achieved 
>>> better by using the GPIOs(setting/resetting the CLK,Data Lines) .
>>> 
>>> experts comments required.
>>> 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...@googlegroups.com <>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/9eef480f-0293-4b4d-99d9-e4527bac1d25%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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/0019f98b-3575-495a-af41-77136c618e96%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/b03fe5ed-c377-4522-b8ed-55bdc2bc235d%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/C7726EF8-9DAD-4C32-A78A-2B00C16D7669%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Driver Development : SPI or 4 wire Interface on BBB

[Raul Piper]

What is PRU?Can you post a link or keywords related to it.?

On Tuesday, May 24, 2016 at 11:43:09 PM UTC+5:30, john3909 wrote:
>
> Best to use the PRU and control the I/O with software.
>
> Regards,
> John
>
>
>
>
> On May 24, 2016, at 6:25 AM, Raul Piper > 
> wrote:
>
>
> *My Question was Can CS be selectively made High or Low at nth or pth 
> Clock Pulse while using/writing the SPI driver?*
> On Monday, May 23, 2016 at 9:59:14 PM UTC+5:30, john3909 wrote:
>>
>> Here are the possible solutions:
>>
>> 1) Use spidev which allows a user space application to communicate with a 
>> device over SPI
>> 2) Use PRU to communicate with device over SPI
>> 3) Develop a device driver to communicate with device over SPI
>> 4) Adapt an IIO driver that is similar to your device
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On May 23, 2016, at 4:34 AM, Raul Piper  wrote:
>>
>> I am developing a driver for a hardware whose datasheet says it has a 4 
>> wire Serial interface .DataIN/OUT,Clock,CS .Does it means I can develop a 
>> full fledged SPI driver on Linux to use it.
>> To add more when the CLK has n-n+1(say 3-4) rising edge with LE = 1 
>> certain control register will be written .Value of n depends on the type of 
>> control register.
>> Will it be good to develop a SPI driver for this or this can be achieved 
>> better by using the GPIOs(setting/resetting the CLK,Data Lines) .
>>
>> experts comments required.
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/9eef480f-0293-4b4d-99d9-e4527bac1d25%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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/0019f98b-3575-495a-af41-77136c618e96%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/b03fe5ed-c377-4522-b8ed-55bdc2bc235d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.