Re: [beagleboard] BBG cannot connect via ethernet

[William Hermans]

By the way, on a stock debian image on the beaglebones. DHCP will be
enabled. So unless your laptop has a DHCP server running on it ( not very
likely or easy to setup on Windows ). You're going to need a router between
the laptop and a beaglebone. *IF* You want to use ethernet, and if you do
not have other means to connect to the beaglebone, to change some
configuration files. Like a serial debug cable, have g_serial setup and
running properly, or booting from an sdcard, then mounting the eMMC long
enough to edit files.

On Fri, Nov 11, 2016 at 6:16 PM, William Hermans  wrote:

> So . . .
>
> # Ethernet/RNDIS gadget (g_ether)
> # ... or on host side, usbnet and random hwaddr
> iface usb0 inet static
> address 192.168.7.2
> netmask 255.255.255.252
> network 192.168.7.0
> gateway 192.168.7.1
>
> This is what a stock system should be setup as for USB ethernet. So, on
> the Windows host under "Network Connections" for the RDNIS gadget driver
> should set the IP address as 192.168.7.1. Then the same netmask as above.
> Which Windows calls "Subnet mask".
>
> Additionally, I've experienced problems in the past with variosu version
> of Windows where you'll need to do a manual Windows update to pull in a
> driver for the RNDIS software device. Don't ask me why, because I do not
> know why. But I would not worry about this unless it still does not work as
> I described above.
>
>
> On Fri, Nov 11, 2016 at 2:27 PM, Petr Šefara  wrote:
>
>> Hello everybody.
>>
>> Just got my BBG and I'm not able to connect to the internal server via
>> eth.
>>
>> PC is laptop with Win10, on BBG is power LED shining and USR LEDs are
>> blinking. BBG is directly connect to laptom via eth cable. This laptom is
>> older one (HP ProBook4530s) after complete reinstal.
>>
>> In network setting I assigned static adres in IPv4 protocol (
>> 192.168.7.254/255.255.255.0) and the result is still the same:
>>
>> Pinging 192.168.7.2 with 32 bytes of data:
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Request timed out.
>>
>> Ping statistics for 192.168.7.2:
>> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
>>
>> LEDs on both eth connector are "dead" so there is no communication but in
>> device manager there is Linux USB Ethernet/RNDIS Gadget and in properties
>> it says that device is working properly.
>>
>> I've also tried to instal new FTDI drivers, eject BBG, turn off firewall
>> but without any succes.
>>
>> Thank you for any suggestion
>>
>> BR
>>
>> Petr
>>
>> --
>> 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/ms
>> gid/beagleboard/7c6e74a9-f7fb-4e84-a6cb-aa15aaedf2f3%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/CALHSORobcCKWZ4MAN8cyy-eB7fxgpCY3X-ow3DfNrY6f02rO4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBG cannot connect via ethernet

[William Hermans]

So . . .

# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1

This is what a stock system should be setup as for USB ethernet. So, on the
Windows host under "Network Connections" for the RDNIS gadget driver should
set the IP address as 192.168.7.1. Then the same netmask as above. Which
Windows calls "Subnet mask".

Additionally, I've experienced problems in the past with variosu version of
Windows where you'll need to do a manual Windows update to pull in a driver
for the RNDIS software device. Don't ask me why, because I do not know why.
But I would not worry about this unless it still does not work as I
described above.


On Fri, Nov 11, 2016 at 2:27 PM, Petr Šefara  wrote:

> Hello everybody.
>
> Just got my BBG and I'm not able to connect to the internal server via
> eth.
>
> PC is laptop with Win10, on BBG is power LED shining and USR LEDs are
> blinking. BBG is directly connect to laptom via eth cable. This laptom is
> older one (HP ProBook4530s) after complete reinstal.
>
> In network setting I assigned static adres in IPv4 protocol (
> 192.168.7.254/255.255.255.0) and the result is still the same:
>
> Pinging 192.168.7.2 with 32 bytes of data:
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.168.7.2:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
>
> LEDs on both eth connector are "dead" so there is no communication but in
> device manager there is Linux USB Ethernet/RNDIS Gadget and in properties
> it says that device is working properly.
>
> I've also tried to instal new FTDI drivers, eject BBG, turn off firewall
> but without any succes.
>
> Thank you for any suggestion
>
> BR
>
> Petr
>
> --
> 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/7c6e74a9-f7fb-4e84-a6cb-aa15aaedf2f3%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/CALHSORoPjs5us_YfVJrh%3DsJvusJ_1mra_Nmn6Z943T%3DScXxMSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[William Hermans]

On Fri, Nov 11, 2016 at 12:45 PM, Robert Nelson 
wrote:

> >> univ-emmc is the userspace overlay we automatically load on bootup
> >>
> >> open /boot/uEnv.txt
> >>
> >> you'll notice a cape_universal=enable
> >>
> >> remove that and reboot
> >>
> >> Regards,
> >>
> >
> > What does that actually do Robert ? I've done this myself in the past,
> and
> > haven't noticed a difference one way or another. Granted, I am using a
> > heavily modified universal overlay. . . but with only specific pins muxed
> > the way I need it, and everything else stripped out.
>
> It's the hint to load it on bootup:
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.
> sh#L442-L531
>
> Regards,
>

Thanks Robert,

I just kind of glanced at the script and saw towards the end of the
highlighted code where is chooses the file to load. Didn't see where or or
even if it does not load  one based on if another overlay was chosen or
not. But that's not really all that important to me. . . I'll just disable
it in the future.

-- 
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/CALHSORo61526jUR%3DPHuoQ%3DnyuXwU2bG5g5FMZ1%2BkvjfWkxPyJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[William Hermans]

Hi Zach,

So, first of all. Yes removing the line , commenting it out in uEnv.txt
will keep from loading the overlay at boot. As for removing it from the
initramfs, I would assume if you reversed the process. e.g. remove the line
from uEnv.txt. then remove the file from /lib/firmware, that the script
would also remove it from the initramfs. However, I have not looked through
the script in that great of detail, and have not tested it personally.

The only real issue here is that the initramfs could get much larger than
you needed, in some cases. But otherwise it should be fine. So long as you
do not create too many overlays, and "inject" them into the initramfs. In
dire cases, where you do need to remove much fromm the initramfs, you could
copy the initramfs, extract the file system, modify the file system,
re-archive it, then move the old initramfs out of the way, and replace it
with the new initial ram disk. It is a rather complex operation, and that
would be assuming Roberts script is not already capable of removing files
as well.

On Fri, Nov 11, 2016 at 2:01 PM, Zach B  wrote:

> Great, thanks! And not to be a pest but I assume in order to undo that
> change I simply comment the line that I add to the uEnv.txt and that's it?
> Should I worry about removing the *.dtbo object from the initrd?
>
> On Friday, November 11, 2016 at 3:22:17 PM UTC-5, RobertCNelson wrote:
>
>> On Fri, Nov 11, 2016 at 2:14 PM, Zach B  wrote:
>> > Thanks Robert! That solved the problem I have been having. The overlay
>> > loaded and everything looks to be working. One follow up question I do
>> have
>> > is what is the proper way to load a custom overlay on startup? Is there
>> a
>> > way to enable multiple overlays as long as they don't try to use the
>> same
>> > pins?
>>
>> Add it /boot/uEnv.txt:
>>
>> ##Example v4.1.x
>> #cape_disable=bone_capemgr.disable_partno=
>> #cape_enable=bone_capemgr.enable_partno=
>>
>> ##Example v4.1.x
>> #cape_disable=bone_capemgr.disable_partno=
>> cape_enable=bone_capemgr.enable_partno=PRU-GPIO-BLINK
>>
>> You'll need to copy PRU-GPIO-BLINK-00A0.dtbo to /lib/firmware/
>>
>> then run:
>>
>> sudo /opt/scripts/tools/developers/update_initrd.sh
>>
>> To copy the new *.dtbo object into the initrd..
>>
>> Then just reboot, and you should see your overlay loaded..
>>
>> 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/18dbb804-b0c2-495f-bd95-14a933c84022%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/CALHSORp9AS-PO6d9rkfwoPdWPAM4VF%2BUa14wV7JZoQDKbUXjfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBG cannot connect via ethernet

[Petr Šefara]

Hello everybody.

Just got my BBG and I'm not able to connect to the internal server via eth. 

PC is laptop with Win10, on BBG is power LED shining and USR LEDs are 
blinking. BBG is directly connect to laptom via eth cable. This laptom is 
older one (HP ProBook4530s) after complete reinstal.

In network setting I assigned static adres in IPv4 protocol 
(192.168.7.254/255.255.255.0) and the result is still the same:

Pinging 192.168.7.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.7.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

LEDs on both eth connector are "dead" so there is no communication but in 
device manager there is Linux USB Ethernet/RNDIS Gadget and in properties 
it says that device is working properly.

I've also tried to instal new FTDI drivers, eject BBG, turn off firewall 
but without any succes.

Thank you for any suggestion

BR

Petr

-- 
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/7c6e74a9-f7fb-4e84-a6cb-aa15aaedf2f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Zach B]

Great, thanks! And not to be a pest but I assume in order to undo that 
change I simply comment the line that I add to the uEnv.txt and that's it? 
Should I worry about removing the *.dtbo object from the initrd?

On Friday, November 11, 2016 at 3:22:17 PM UTC-5, RobertCNelson wrote:
>
> On Fri, Nov 11, 2016 at 2:14 PM, Zach B > 
> wrote: 
> > Thanks Robert! That solved the problem I have been having. The overlay 
> > loaded and everything looks to be working. One follow up question I do 
> have 
> > is what is the proper way to load a custom overlay on startup? Is there 
> a 
> > way to enable multiple overlays as long as they don't try to use the 
> same 
> > pins? 
>
> Add it /boot/uEnv.txt: 
>
> ##Example v4.1.x 
> #cape_disable=bone_capemgr.disable_partno= 
> #cape_enable=bone_capemgr.enable_partno= 
>
> ##Example v4.1.x 
> #cape_disable=bone_capemgr.disable_partno= 
> cape_enable=bone_capemgr.enable_partno=PRU-GPIO-BLINK 
>
> You'll need to copy PRU-GPIO-BLINK-00A0.dtbo to /lib/firmware/ 
>
> then run: 
>
> sudo /opt/scripts/tools/developers/update_initrd.sh 
>
> To copy the new *.dtbo object into the initrd.. 
>
> Then just reboot, and you should see your overlay loaded.. 
>
> 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/18dbb804-b0c2-495f-bd95-14a933c84022%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Robert Nelson]

On Fri, Nov 11, 2016 at 2:14 PM, Zach B  wrote:
> Thanks Robert! That solved the problem I have been having. The overlay
> loaded and everything looks to be working. One follow up question I do have
> is what is the proper way to load a custom overlay on startup? Is there a
> way to enable multiple overlays as long as they don't try to use the same
> pins?

Add it /boot/uEnv.txt:

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

##Example v4.1.x
#cape_disable=bone_capemgr.disable_partno=
cape_enable=bone_capemgr.enable_partno=PRU-GPIO-BLINK

You'll need to copy PRU-GPIO-BLINK-00A0.dtbo to /lib/firmware/

then run:

sudo /opt/scripts/tools/developers/update_initrd.sh

To copy the new *.dtbo object into the initrd..

Then just reboot, and you should see your overlay loaded..

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

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Zach B]

Thanks Robert! That solved the problem I have been having. The overlay 
loaded and everything looks to be working. One follow up question I do have 
is what is the proper way to load a custom overlay on startup? Is there a 
way to enable multiple overlays as long as they don't try to use the same 
pins?


On Friday, November 11, 2016 at 2:46:26 PM UTC-5, RobertCNelson wrote:
>
> >> univ-emmc is the userspace overlay we automatically load on bootup 
> >> 
> >> open /boot/uEnv.txt 
> >> 
> >> you'll notice a cape_universal=enable 
> >> 
> >> remove that and reboot 
> >> 
> >> Regards, 
> >> 
> > 
> > What does that actually do Robert ? I've done this myself in the past, 
> and 
> > haven't noticed a difference one way or another. Granted, I am using a 
> > heavily modified universal overlay. . . but with only specific pins 
> muxed 
> > the way I need it, and everything else stripped out. 
>
> It's the hint to load it on bootup: 
>
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L442-L531
>  
>
> 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/3a202d8a-10b0-418f-a954-c0d29844f7ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Robert Nelson]

>> univ-emmc is the userspace overlay we automatically load on bootup
>>
>> open /boot/uEnv.txt
>>
>> you'll notice a cape_universal=enable
>>
>> remove that and reboot
>>
>> Regards,
>>
>
> What does that actually do Robert ? I've done this myself in the past, and
> haven't noticed a difference one way or another. Granted, I am using a
> heavily modified universal overlay. . . but with only specific pins muxed
> the way I need it, and everything else stripped out.

It's the hint to load it on bootup:

https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L442-L531

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

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[William Hermans]

On Fri, Nov 11, 2016 at 12:26 PM, Robert Nelson 
wrote:

> On Fri, Nov 11, 2016 at 12:53 PM, Zach B  wrote:
> > wow that is incredible useful, I didn't even realize that is what dmesg
> did.
> > Here is the output I got:
> > [ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK',
> > version 'N/A'
> > [ 2117.571876] bone_capemgr bone_capemgr: slot #10: override
> > [ 2117.571920] bone_capemgr bone_capemgr: Using override eeprom data at
> slot
> > 10
> > [ 2117.571967] bone_capemgr bone_capemgr: slot #10: 'Override Board
> > Name,00A0,Override Manuf,PRU-GPIO-BLINK'
> > [ 2117.573674] bone_capemgr bone_capemgr: slot #10: PRU-GPIO-BLINK
> conflict
> > P8.11 (#4:univ-emmc)
> > [ 2117.582657] bone_capemgr bone_capemgr: slot #10: Failed verification
>
> univ-emmc is the userspace overlay we automatically load on bootup
>
> open /boot/uEnv.txt
>
> you'll notice a cape_universal=enable
>
> remove that and reboot
>
> Regards,
>
>
What does that actually do Robert ? I've done this myself in the past, and
haven't noticed a difference one way or another. Granted, I am using a
heavily modified universal overlay. . . but with only specific pins muxed
the way I need it, and everything else stripped out.

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

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Robert Nelson]

On Fri, Nov 11, 2016 at 12:53 PM, Zach B  wrote:
> wow that is incredible useful, I didn't even realize that is what dmesg did.
> Here is the output I got:
> [ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK',
> version 'N/A'
> [ 2117.571876] bone_capemgr bone_capemgr: slot #10: override
> [ 2117.571920] bone_capemgr bone_capemgr: Using override eeprom data at slot
> 10
> [ 2117.571967] bone_capemgr bone_capemgr: slot #10: 'Override Board
> Name,00A0,Override Manuf,PRU-GPIO-BLINK'
> [ 2117.573674] bone_capemgr bone_capemgr: slot #10: PRU-GPIO-BLINK conflict
> P8.11 (#4:univ-emmc)
> [ 2117.582657] bone_capemgr bone_capemgr: slot #10: Failed verification

univ-emmc is the userspace overlay we automatically load on bootup

open /boot/uEnv.txt

you'll notice a cape_universal=enable

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

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Zach B]

I just tried the various combinations of enabling and disabling the HDMI, 
emmc, both and neither and regardless of what it is set to I get a conflict 
on P8.11 every time. Is there a key component that I am missing somewhere 
or a different way I should be going about this?

On Friday, November 11, 2016 at 1:53:16 PM UTC-5, Zach B wrote:
>
> wow that is incredible useful, I didn't even realize that is what dmesg 
> did. Here is the output I got:
> [ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK', 
> version 'N/A'
> [ 2117.571876] bone_capemgr bone_capemgr: slot #10: override
> [ 2117.571920] bone_capemgr bone_capemgr: Using override eeprom data at 
> slot 10
> [ 2117.571967] bone_capemgr bone_capemgr: slot #10: 'Override Board 
> Name,00A0,Override Manuf,PRU-GPIO-BLINK'
> [ 2117.573674] bone_capemgr bone_capemgr: slot #10: PRU-GPIO-BLINK 
> conflict P8.11 (#4:univ-emmc)
> [ 2117.582657] bone_capemgr bone_capemgr: slot #10: Failed verification
>
> It looks like I am having a conflict with the emmc on the beaglebone, so I 
> assumes that means I should disable the emmc in my uEnv.txt? Also I am a 
> bit confused as to why it says the version is 'N/A' when I have it set to 
> '00A0' in my dts file.
>
>
> On Friday, November 11, 2016 at 1:44:22 PM UTC-5, RobertCNelson wrote:
>>
>> On Fri, Nov 11, 2016 at 12:42 PM, Zach B  wrote: 
>> > I wanted to add on to this that when I switch the Device Tree Blob file 
>> > extension to ".dtbo" instead of ".dtb" I get the error: 
>> > -bash: echo: write error: File exists 
>> > instead of the file not found error I was getting previously. 
>>
>> if you type "dmesg" after that, the kernel should give you a hint of 
>> what happend.. 
>>
>> 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/9a7d2b4e-992a-4ca3-beab-7b1af55b48de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Zach B]

wow that is incredible useful, I didn't even realize that is what dmesg 
did. Here is the output I got:
[ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK', 
version 'N/A'
[ 2117.571876] bone_capemgr bone_capemgr: slot #10: override
[ 2117.571920] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 10
[ 2117.571967] bone_capemgr bone_capemgr: slot #10: 'Override Board 
Name,00A0,Override Manuf,PRU-GPIO-BLINK'
[ 2117.573674] bone_capemgr bone_capemgr: slot #10: PRU-GPIO-BLINK conflict 
P8.11 (#4:univ-emmc)
[ 2117.582657] bone_capemgr bone_capemgr: slot #10: Failed verification

It looks like I am having a conflict with the emmc on the beaglebone, so I 
assumes that means I should disable the emmc in my uEnv.txt? Also I am a 
bit confused as to why it says the version is 'N/A' when I have it set to 
'00A0' in my dts file.


On Friday, November 11, 2016 at 1:44:22 PM UTC-5, RobertCNelson wrote:
>
> On Fri, Nov 11, 2016 at 12:42 PM, Zach B > 
> wrote: 
> > I wanted to add on to this that when I switch the Device Tree Blob file 
> > extension to ".dtbo" instead of ".dtb" I get the error: 
> > -bash: echo: write error: File exists 
> > instead of the file not found error I was getting previously. 
>
> if you type "dmesg" after that, the kernel should give you a hint of 
> what happend.. 
>
> 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/0a17f9e6-2f91-4894-a3f6-3e77945aeea9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Beaglebone Black PRU Troubles

[Robert Nelson]

On Fri, Nov 11, 2016 at 12:42 PM, Zach B  wrote:
> I wanted to add on to this that when I switch the Device Tree Blob file
> extension to ".dtbo" instead of ".dtb" I get the error:
> -bash: echo: write error: File exists
> instead of the file not found error I was getting previously.

if you type "dmesg" after that, the kernel should give you a hint of
what happend..

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/CAOCHtYhV%3D%3Dm%3DSa%2BTfdMqNGWheF_AH4ayJJYoJBPnZ2iZGbAfLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Black PRU Troubles

[Zach B]

I wanted to add on to this that when I switch the Device Tree Blob file 
extension to ".dtbo" instead of ".dtb" I get the error:
-bash: echo: write error: File exists
instead of the file not found error I was getting previously.


On Friday, November 11, 2016 at 1:27:22 PM UTC-5, Zach B wrote:
>
> Hi everyone,
>
> So I messed around with my beaglebone a little bit last night. I worked 
> out the issues in my device tree source file so it is now compiled but I 
> can't seem to get anything to echo properly to "slots"
> I compile my ".dtb" file but when I go to call the comman: 
> echo PRU-GPIO-BLINK > /sys/devices/platform/bone_capemgr/slots
> I continually get the error:
> -bash: echo: write error: No such file or directory
> Is there are a different way to enable my device overlay or set the pins 
> to the correct mode for the PRU? I have even tried copying, compiling and 
> attempting to export the device tree overlay example from adafruit and 
> still no luck.
>
> The names of my files in /lib/firmware are as follows:
> PRU-GPIO-BLINK.dts
> PRU-GPIO-BLINK-00A0.dtb
> The part-number name in the .dts file is "PRU-GPIO-BLINK". Am I still 
> missing something? I can post the updated ".dts" file if it would help.
>
> P.S. I have two questions since I am still relatively new at this:
> 1) What is a blacklist and why was it necessary to export to the .conf 
> file to enable the remote_proc?
> 2) What is dmesg and where do I check them? Are you referring to 
> "/var/log/syslog"?
>
> Zach
>
>
> On Thursday, November 10, 2016 at 9:27:47 AM UTC-5, Greg wrote:
>>
>> Once you get everything solid, please take a look at dmesg after boot.
>> I'm curious to see if you get successful PRU firmware start-up.
>>
>> Greg
>>
>> On Thursday, November 10, 2016 at 8:28:23 AM UTC-5, Zach B wrote:
>>>
>>> Hey everyone, I wanted to give an update. I got the remote_proc to turn 
>>> on last night. It was as simple as updating my repo like Robert had 
>>> mentioned. I also made the correction that Brett mentioned about the pins. 
>>> There is still something wrong in my device overlay file that is causing an 
>>> "invalid arguement" error but I am going to try and sort that out tonight. 
>>> I'll post again with the corrected version once I get it working and can 
>>> use the PRU.
>>>
>>> Thanks again for your help.
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/88569e41-83bc-41f0-ab19-e3e1e59ecb01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Black PRU Troubles

[Zach B]

Hi everyone,

So I messed around with my beaglebone a little bit last night. I worked out 
the issues in my device tree source file so it is now compiled but I can't 
seem to get anything to echo properly to "slots"
I compile my ".dtb" file but when I go to call the comman: 
echo PRU-GPIO-BLINK > /sys/devices/platform/bone_capemgr/slots
I continually get the error:
-bash: echo: write error: No such file or directory
Is there are a different way to enable my device overlay or set the pins to 
the correct mode for the PRU? I have even tried copying, compiling and 
attempting to export the device tree overlay example from adafruit and 
still no luck.

The names of my files in /lib/firmware are as follows:
PRU-GPIO-BLINK.dts
PRU-GPIO-BLINK-00A0.dtb
The part-number name in the .dts file is "PRU-GPIO-BLINK". Am I still 
missing something? I can post the updated ".dts" file if it would help.

P.S. I have two questions since I am still relatively new at this:
1) What is a blacklist and why was it necessary to export to the .conf file 
to enable the remote_proc?
2) What is dmesg and where do I check them? Are you referring to 
"/var/log/syslog"?

Zach


On Thursday, November 10, 2016 at 9:27:47 AM UTC-5, Greg wrote:
>
> Once you get everything solid, please take a look at dmesg after boot.
> I'm curious to see if you get successful PRU firmware start-up.
>
> Greg
>
> On Thursday, November 10, 2016 at 8:28:23 AM UTC-5, Zach B wrote:
>>
>> Hey everyone, I wanted to give an update. I got the remote_proc to turn 
>> on last night. It was as simple as updating my repo like Robert had 
>> mentioned. I also made the correction that Brett mentioned about the pins. 
>> There is still something wrong in my device overlay file that is causing an 
>> "invalid arguement" error but I am going to try and sort that out tonight. 
>> I'll post again with the corrected version once I get it working and can 
>> use the PRU.
>>
>> Thanks again for your help.
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ea0f79ef-abee-4d95-b9e9-f81f1d78df0e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Removal of Components from BBBW for Custom PCB.

[Stephane Charette]

>
> I'm making a custom BBBW for a school project. I'm adding a few 
> peripherals but would like to strip down what is unnecessary in order to 
> save on BOM costs. The first to go is the large HDMI chip.
>

HDMI and the barrel connector was already removed from BBG and BBGW.  Out 
of curiosity, why not start with that instead?

Stéphane

-- 
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/b7e3627c-3773-4cd9-8ab0-13996ad82147%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Do I really need a USB-to-FTDI cable to see the U-boot prompt? Will it not work on micro-HDMI?

[Stephane Charette]

On Thursday, November 10, 2016 at 12:36:07 PM UTC-8, William Hermans wrote:
>
> You do not have to buy a FTDI cable. It could be any decent cable, that 
> does not necessarily cost as much as FTDI. For example my buddy and I 
> ordered a couple of PL2303HX cables off ebay for like $5-6 usd shipped.
>

The ones I found with shipping (to Canada) were in the $40-50 range, which 
was discouraging -- more expensive than buying a new BeagleBone! 
 Eventually found this one on Amazon for $3, including shipping, and it 
works great:

https://www.amazon.ca/gp/product/B00F167PWE

Stéphane

-- 
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/7726319f-98ac-4dff-8800-187e324270e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Flashing a BBB's EMC from uSD Card - problems

['Ian Watts' via BeagleBoard]

Update:

I 'located' the uSD card - in the //dev (devices, I guess) folder; I simply 
by noted what changed as I inserted the uSD card and looking at the folder 
contents before ('ls dev' command) and after) In my case (pretty standard, 
I guess) I saw 'mmcblk1p1' was added as I inserted the card (for others 
having similar issue to myself : mmc=multimedia card, 'blk1' = block device 
1 (the eMMC is, I think 'blk0') and the 'p1' = partition 1)

I then created a folder in //dev to 'house' the folder & file contents of 
the uSD. In fact I created a folder called 'card' in 'media' which was 
already within the root folder. So, I now have a folder : //media/card. 
Just for my future reference (and because it made me feel good to 'own' :-) 
the folder), I then created a realm.txt file within my new folder to remind 
me when and why I created the folder...

I then 'mounted' the uSD card and 'linked' its contents to my new folder 
with :
mount /dev/mmcblk1p1 on /media.card
Terminal responded with :
mount: you didn't specify a filesystem type for /dev/mmcblk1p1 
I will try ext4
/dev/mmcblk1p1 on /media/card type ext4 (rw)

When I then listed the contents of the uSD card with 'ls /media/card', 
Terminal returned the folders and files within the uSD card root folder - 
Yahaay !

OK... so far so good...

I then located the uEnv.txt file again (BUT, now on the uSD card) and 
opened it with a view to editing the required 'flash the eMMC' line. I was, 
however, confronted with :

  GNU nano 2.2.6 File: 
uEnv.txt
Modified  



loadximage=echo debug: [/boot/vmlinuz-${uname_r}] ... ; load mmc 0:1 
${loadaddr} /boot/vmlinuz-${uname_r}

loadxfdt=echo debug: [/boot/dtbs/${uname_r}/${fdtfile}] ... ;load mmc 0:1 
${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}

loadxrd=echo debug: [/boot/initrd.img-${uname_r}] ... ; load mmc 0:1 
${rdaddr} /boot/initrd.img-${uname_r}; setenv rdsize ${filesize}

loaduEnvtxt=load mmc 0:1 ${loadaddr} /boot/uEnv.txt ; env import -t 
${loadaddr} ${filesize};

check_dtb=if test -n ${dtb}; then setenv fdtfile ${dtb};fi;

loadall=run loaduEnvtxt; run check_dtb; run loadximage; run loadxrd; run 
loadxfdt;


mmcargs=setenv bootargs console=tty0 console=${console} ${optargs} 
${cape_disable} ${cape_enable} root=/dev/mmcblk0p1 
rootfstype=${mmcrootfstype} ${cmdline}


uenvcmd=run loadall; run mmcargs; echo debug: [${bootargs}] ... ; echo 
debug: [bootz ${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr}] ... ; bootz 
${loadaddr} ${rdaddr}:${rdsize} ${fdtaddr};


cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh


As you'll see, the line was already un-remmed...


Anyways, I powered down the BBB with the 'Boot' button depressed and, still 
depressed, fired it back up again. When I saw all 4 Usr LEDs light up I 
removed my finger from the 'Boot' button. Nothing very different happen... 
same old heartbeat and sporadic others... no flashing occurred. After 45-60 
seconds I'm confronted with 'just' the heartbeat LET and nothing else...


Ideas please ?


-- 
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/c1e19e45-08ca-47fc-9217-6ab3dd934cba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: debian: release candidate: 2014-12-11

[Mrudula Chougule]

Hi,

I am using repository and steps for building the same mentioned in below 
link;
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-HDMI

1) I have flashed U-boot Image to internal Flash of Beagle Bone Black. When 
I try to boot-up from internal flash without having kernel image in flash 
and without connecting SD card, it gives me BOOTP messages, which I want to 
disable and want to display some message on LCD screen like "Please Insert 
SD Card" Can I do this in U-boot code.
 
2) When I connect LCD Monitor to Beagle Bone Black once it is booted with 
images built using above steps, it is taking time to turn ON display and 
after some time giving memory errors. But When I run Beagle Bine Black 
Debian image it works fine. Please suggest how to configure this as it 
works in Debian case.


Kindly let me know your feedback / Suggestions on the same.

  

On Saturday, December 13, 2014 at 2:46:23 AM UTC+5:30, RobertCNelson wrote:
>
> Happy Holidays! 
>
> I just pushed out another round of images for testing.  I know Jason & 
> bb.org really wants an offical new image, so please test the last 
> Debian 7 (wheezy) release for bb.org (1) 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-12-11 
>
> Upgrades over "2014-05-14" 
>
> U-boot: v2015.01-rc3 
> Kernel: 3.8.13-bone68 
>
> Simpler Kernel Upgrades: 
>  sudo apt-get install linux-image-3.8.13-bone68 ; sudo reboot 
>
> Kernel Headers included: 
>  sudo apt-get install linux-headers-3.8.13-bone68 
>
> 3rd party module list: 
>  sudo apt-get install mt7601u-modules-3.8.13-bone68 
>
> 3rd party repo added: https://github.com/rcn-ee/repos (2) 
>  am335x-pru-package 
>  ap-hotspot 
>  dart-1.8 (stable 1.8 branch) 
>  dart-edge (git master branch) 
>  oracle-java8-installer 
>  ti-pru-cgt-installer 
>  xenomai-runtime 
>
> 1: Debian 8 (Jessie): 
> At the rate things are going, it might be released mid Feb: 
> https://udd.debian.org/cgi-bin/rcblog.cgi 
>
> 2: This is open to more users, if you need something packaged and 
> distributed that is open source, ping us. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a1e034ab-3be3-41d6-b4e9-affa5fd93b3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beagle Bone Black - uboot

[Mrudula Chougule]

Hi, 

I am working on Beagle Bone Black AM335x platform and started porting 
U-boot for the same.

I have followed steps for building U-boot, Kernel and rootfs on below 
mentioned link,

https://eewiki.net/display/linuxonarm/BeagleBone+Black

I am able to compile it successfully but when I try to load my kernel image 
using u-boot mentioned on this link is not able to load.

I have below quires on this git repo:

1) Why this u-boot has been patched?
2) How this rootfs is built?

Once I get my board up after loading images mentioned on this link i am 
trying to connect HDMI to LCD Monitor. It is taking 2mins to start and it 
is not quick though. 
Could you please share which window manager is good to use as i can see 
there is a lot of difference when i boot with built images and one with 
default flashed image which has come beagle bone black board.

Kindly let me know your suggestions/ feedback.

Your suggestions are highly appreciated.

Thanks
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/114f5b95-7919-4097-a1d5-e5acfa92075e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Not able to ping the router or google from my beagleboard-xm running ubuntu

[anuj . gupta]

Hi i am working on beagleboard-xm running ubuntu , when i connected my 
ethernet cable then i am not able to ping anything it shows network 
unreachable.
I changed the /etc/network/interfaces and added the static ip details even 
the problem was not resolved 
Thanks

-- 
 

This message contains confidential information and is intended only for the 
individual(s) named. If you are not the intended recipient, you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this mail and attached file/s is strictly 
prohibited. Please notify the sender immediately and delete this e-mail 
from your system. E-mail transmission cannot be guaranteed to be secured or 
error-free as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses. The sender therefore does 
not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission.

-- 
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/9378490e-4688-4d05-91fd-aae2c1305591%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Flashing a BBB's EMC from uSD Card - problems

['Ian Watts' via BeagleBoard]

Hi Dennis,

Thanks for your response (don't know what happened the first time - I 
responded to you just before I did to Stephane... wierd - too late in the 
day I guess ! )

Firstly I thanked you.
Then I confirmed my BBB is a Rev C / 4GB.
Then I wrote about a new (but associated) issue I have and asked a question 
:
My BBB fires up just fine (presents itself to Network Services - the 
Network pane in System Preferences - just fine with 192.168.7.2, and allows 
me to SSH in via tTerminal). All good there !
However, when I power down, insert my 4GB uSD card (I made two identical 
flares of Debian 8.4 one after the other the other night) and power back up 
again ('expecting' to boot off the uSD card with the new 8.4 Distro on it I 
get :
-1- the BBB presents itself to Network Services - the Network pane in 
System Preferences - incorrectly with a 'Self-Assigned IP' of 
169.254.137.203 and a Subnet Mack of 255.255.0.0 (in lieu of the, 'more 
normal', 192.168.7.2 / 255.255.255.255) and sits there with an orange LED 
(as opposed to the green one)
-2- 

I guess, in my 'fiddling about' of the past few days/nights I've corrupted 
something but, for the life of me I can't think what. As far as I recall I 
only 'played' with the uEnv.text file in /boot/uBoot on the eMMC - not 
knowing or thinking about mounting the uSD card ! ;-(

Any ideas as to where I should start to focus my attention now please ?

I do (NOW, after your initial response) see that I should be aiming my 
attention at the uEnv.txt file on the uSD card not on the eMMC (Oops !) but 
I now don't have ace to the BBB when the uSD card is inserted arrggghhh 
!

What am I, as a noobie - but not too dumb, be likely to have done to cause 
this please ? It's difficult for me because I really don't have a good 
enough appreciation of HOW this could occur and, therefore, have almost no 
idea as to where to even begin looking. To boot, I'm even more worried that 
that more 'playing' could make the situation even worse.
For now, I will re-blow the two uSD cards with the same Debian 8.4 image 
(just in case, although I have a feeling Ive managed to screw up the uEnv 
file somehow... so I'll also go take another look at that...

2nd Q (while it occurs to me) is there a way to mount the uSD card from my 
Mac (I'm thinking I could update the uEnv.txt file from there !!

Regards,
IAN
On Friday, 11 November 2016 02:20:33 UTC+1, Dennis Lee Bieber wrote:
>
> On Thu, 10 Nov 2016 13:51:10 -0800 (PST), "'Ian Watts' via BeagleBoard" 
> > declaimed the 
> following: 
>
> > 
> > 
> >On Thursday, 10 November 2016 14:28:18 UTC+1, Dennis Lee Bieber wrote: 
> >> 
> >> On Wed, 9 Nov 2016 15:16:44 -0800 (PST), "'Ian Watts' via BeagleBoard" 
> >> > declaimed the 
> >> following: 
> >> 
>  
> >> 
> >> -- 
> >> Wulfraed Dennis Lee Bieber AF6VN 
> >> wlf...@ix.netcom.com 
> HTTP://wlfraed.home.netcom.com/ 
> >> 
> >> 
>
> Did you have any additional comment? All that I saw is a quote of 
> my 
> response. 
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.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/35289aeb-6877-4036-abaf-668fc6c25609%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.