Re: [beagleboard] Device Tree Overlay for BeagleBone-AI

[Douglas Conover]

Thanks for the reply Robert! Just a quick update, today I was able to 
configure some spi2 pins to interface with an ENC28J60-H development board 
(SPI to Ethernet) with the following dts file:


*/dts-v1/;/plugin/;*



















































*#include /** Helper to show loaded 
overlays under: /proc/device-tree/chosen/overlays/*/&{/chosen} {
overlays {BONE-SPI2_0 = __TIMESTAMP__;};};/* * Update the 
default pinmux of the pins. * See these files for the phandles (&P9_* & 
&P8_*) * 
BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/am335x-bone-common-univ.dtsi
 * 
BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/am572x-bone-common-univ.dtsi
 */&ocp 
{P9_17_pinmux { pinctrl-0 = <&P9_17_spi_cs_pin>; }; /* CS0 */   
 //P9_23_pinmux { pinctrl-0 = <&P9_23_spi_cs_pin>; }; /* CS1 */
P9_21_pinmux { pinctrl-0 = <&P9_21_spi_pin>; }; /* MOSI */P9_18_pinmux 
{ pinctrl-0 = <&P9_18_spi_pin>; };/* MISO */P9_22_pinmux { 
pinctrl-0 = <&P9_22_spi_sclk_pin>; }; /* CLK */P8_07_pinmux {status = 
"disabled";}; /* gpios reserved for RESET and INTERRUPT pins */
P8_09_pinmux {status = "disabled";};P8_08_pinmux {status = 
"disabled";};P8_10_pinmux {status = "disabled";};};/* * See these files 
for the phandles (&bone_*) and other bone bus nodes * 
BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/bbai-bone-buses.dtsi * 
BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/bbb-bone-buses.dtsi 
*/&bone_spi_0{   
 status = "okay";#address-cells = <1>;#size-cells = <0>;   
 channel@0 {reg = <0>;compatible = 
"microchip,enc28j60";pinctrl-names = "default";pinctrl-0 = 
<&P8_09_default_pin>, <&P8_07_gpio_pin> ;//reg = 
<0x0>;/* Use chip select 0 */
interrupt-parent = <&gpio6>;/* Interrupt on GPIO6[18] */
interrupts = <18 IRQ_TYPE_EDGE_FALLING>;symlink = "bone/spi/2.0";   
 spi-max-frequency = <1600>;//spi-cpha;};};*

I still need to make use of the CS1 pin mode on P9_23. However, I see in 
*BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/am572x-bone-common-univ.dtsi,*
there is no entry for *P9_23_spi_cs_pin. *I tried adding the following 
lines to the bone-common-univ.dtsi:



*P9_23_spi_cs_pin: pinmux_P9_23_spi_cs_pin { pinctrl-single,pins = 
; };/* 
spi2_cs1.spi2_cs1, mcasp1_axr1.off */*

But even after a make clean, make all, the resulting dtbo will brick my 
device..

I was wondering if you had any pointers/ideas as to how I could make this 
work? Eventually, I would like to run both channels with different 
interrupt,chip select and rest pins as defined above.

Thanks again,

Doug


On Wednesday, October 7, 2020 at 2:51:22 PM UTC-4 RobertCNelson wrote:

> On Wed, Oct 7, 2020 at 11:40 AM Douglas Conover
>  wrote:
> >
> > Hi! Thanks for this update! I've been playing around in the device trees 
> for a little while in the AI, basing myself on the 
> ``am5729-beagleboneai-roboticscape.dts`` and the v4.14 kernel iot image. I 
> have a hardware application that requires me to use two ENC28J60 ethernet 
> adapters and the SPI 2 pins (I need two chip selects and due to potential 
> pin conflicts I need to use SPI2). After struggling with the v4.14 
> kernel/image, I decided to try upgrading to the 4.19 kernel/image provided 
> in this discussion. I was wondering if this was possible by modifying some 
> of the overlay files provided in:
> >
> > 
> https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays
> >
> > Inspecting 
> ``BeagleBoard-DeviceTrees/v4.19.x-ti-overlays/src/arm/bbai-bone-buses.dtsi``, 
> I could only find the bone_spi_0 and bone_spi_1 groups. Does anyone have 
> any pointers on enabling spi2?
>
> Here is the mapping:
>
>
> https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v4.19.x-ti-overlays/src/arm/bbai-bone-buses.dtsi#L413-L420
>
> 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/3c9b3378-b3ac-473a-ba90-fe676147d478n%40googlegroups.com.

Re: [beagleboard] creating astable build for a commercial system

[morgan abraham]

  Jim,

  Thanks for the feedback and insight.  That is incredibly valuable to know
your experience. We did separate the hardware and software, but I agree the
next step will be to write the HW server in C/C++.

   Given your experience and feedback, I think you may have saved us
several headaches, so thanks so much for sharing!  Hopefully that sets us
on the right track!

  Cheers,



On Wed, Oct 7, 2020 at 12:47 PM Jim F  wrote:

> We built and delivered over 1000 ocean buoys in a design cycle that lasted
> about 9 months based on the pocketbeagle MCM. The original plan was to
> build a PCA on which the pocketbeagle sat (in order to satisfy some "COTS"
> spec) but the cost of doing so got prohibitive, so we just squished the
> boards into one. Not so much difference. Our initial prototypes used BB
> blue and pocketbeagle, and they worked fine with a tangle of wires
> connecting to different sensors and interfaces. We had no issues flashing
> things, ever; that just worked (but on the PB we used SD cards, obviously).
> I think I'm chiming in with Gwen on some of this here:
>
> In our case we built everything to run on Linux using a mix of python3 and
> C. I definitely regret not doing all in C. It would have been nice to have
> compile-time checking of code, as the linter just can't catch everything we
> threw at that codebase. But python did let us add some fairly complex
> features very quickly compared to C. I would absolutely not field a
> hardware system using JS, but I highly value reliability (says the guy who
> did half of it in python, so take that for what it's worth). One of our
> biggest issues was boot time, which we never got better than 30 seconds
> (but most of the time I had to do that was off the clock anyway).
>
> If I were doing what I guess you're doing, I'd move the hardware
> interfaces into a compiled solution and focus hard on error trapping. A
> system shouldn't lock up because a voltage went out of range (unless it
> went too high and you blew up the input, but that's bad hardware design).
> Realistically almost all of the work we did on that job was learning about
> errors to trap. Python's duck typing is awesome for prototyping but made my
> life hell in a tight delivery schedule. Trapping things like "the logs
> partition is full" seems hard in JS - a bugaboo which made my stuff die in
> 24 days, if I recall correctly.
>
> Anyway, if you separate the UI (in JS, or whatever it has to be) from the
> hardware interface, it would be easier to make the system more robust and
> capable. I would do all the HW interface in C if I had to do it again, and
> it wouldn't have taken much longer to implement, might have cost me 10%
> additional dev time. Define the inputs very well on the hardware side (i.e.
> clamp them), and in the software reject any signal outside the expected
> range. If you can completely eliminate the OS and go to a compiled
> baremetal solution (or a stripped down RTOS like what TI offer for Sitara)
> you will eliminate the linux cruft (you probably don't need chrony, syslog,
> a filesystem, etc.) which makes for a simpler system that is easier to
> debug. Of course then you'll spend a lot more time programming, but your
> yogurt machine won't need to reboot so much.
>
> The biggest issue we have in this type of job is testing. Software guys
> know how to build a nice test framework. It works great all the way up till
> you have to deal with some external piece of hardware that might not always
> do what you expect. In my case, I had a modem which worked well except when
> it failed in a variety of exciting ways; a GPS receiver which occasionally
> reported impossible locations, and a series of different analog- and
> digital-output sensors which all found interesting ways to work wrongly.
> I've built test hardware for jobs, but I've never had to automate testing
> of a system involving so many disparate parts. That's really, really hard
> to automate, and I've yet to find an approach which doesn't require me to
> turn it into a career. As I said above, defining the range of the inputs is
> key, but it's so much easier to do with an analog signal than a digital
> protocol. Even then, should actuator 1 do X when both sensors 1 and 2 are
> at their negative limits - sometimes these things aren't completely obvious
> until you think them through.
>
> Those are just some thoughts from someone who has been there. Good luck
> though.
>
> Jim
>
> On Wed, Oct 7, 2020 at 8:41 AM morgant...@gmail.com <
> morgantabra...@gmail.com> wrote:
>
>>   Hello beaglebone community,
>>
>>   This is my first post.
>>
>>   I used beaglebone to develop a prototype for for a self-cleaning
>> smoothie machine that we plan to commercialize (see video below).  It has
>> multiple sensors and outputs to run motors/solenoids while ensuring user
>> safety.
>>
>> https://www.youtube.com/watch?v=76XDJK5V0PA&feature=share&;
>> ab_channel=PascalKriesche
>>
>>Right now we have. BBB running a linux

[beagleboard] Boot time optimization

[mfar...@gmail.com]

Hi guys,
I boot from SD and it takes to much time (2 min).. is any way to 
optimize this??

This is my */opt/scripts/tools/version.sh*

git:/opt/scripts/:[5fa30ffcf068996ec08e034d2af5c5a133f10709]
eeprom:[A335BNLT000C2006BBBG0129]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[rcn-ee.net Ubuntu Console Image 2020-03-12]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-UIO-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
kernel:[5.4.47-bone30]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/FESTO-PINMUX-SETUP.dtbo]
uboot_overlay_options:[disable_uboot_overlay_emmc=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.14.20200722.0-0~bionic+20200722]
pkg:[bb-wl18xx-firmware]:[1.20200702.0-0~bionic+20200702]
pkg:[kmod]:[24-1ubuntu3.4rcnee0~bionic+20200525]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
groups:[ubuntu : ubuntu adm kmem dialout cdrom floppy audio dip video 
plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc 
admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0 quiet cape_universal=enable]
dmesg | grep remote


and this is  my  *systemd-analyze blame*

  1min 34.446s dev-mmcblk0p2.device
 1min 2.259s generic-board-startup.service
 50.664s dev-loop8.device
 49.671s dev-loop7.device
 49.351s dev-loop6.device
 48.843s dev-loop4.device
 48.804s dev-loop5.device
 48.462s dev-loop3.device
 48.420s dev-loop1.device
 48.392s dev-loop0.device
 48.197s dev-loop2.device
 24.250s snapd.service
 10.326s networkd-dispatcher.service
  5.036s nginx.service
  3.740s systemd-udev-trigger.service
  3.630s apparmor.service
  3.419s systemd-journald.service
  3.058s ssh.service
  2.843s loadcpufreq.service
  2.041s keyboard-setup.service
  1.935s binfmt-support.service
  1.551s grub-common.service
  1.534s snap-core-9995.mount
  1.448s cpufrequtils.service
  1.406s snap-core-9805.mount

thx

-- 
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/d56a7c57-914d-49f5-9f94-68ec12e8521bn%40googlegroups.com.

Re: [beagleboard] ERRNO 9 / Bad File Number after Hours accessing

[Jeremy Trimble]

Alex,

The EBADF may not be your actual problem, because immediately before
exiting the loop you attempt to close an invalid file descriptor:  In the
"then" part of your if statement, you verify in the condition that the
output_fd is less than zero (an invalid file descriptor), then you call
close() on that invalid file descriptor (which also returns an error, but
you don't see it because you're not checking the return value of close()
there).  Once you break out of the loop, errno is set to EBADF from the
close() call, not from the open() call.

You should add the printout as the first line inside of the "then" block of
your if ( output_fd < 0 ) -- that will tell you what errno was returned
from the open() call.

Jeremy Trimble
Principal Research Engineer
Two Six Labs, LLC  *:|:::*
https://twosixlabs.com/


On Thu, Oct 1, 2020 at 6:59 AM  wrote:

>
>
>
> Hi,
>
> the function below ist running for hours but sometimes an error no 9
> occours (which must be "Bad File Number*"). *Does anyone have an idea or
> suggestions for other flags? This is the only function in the whole
> programm that is accessing the ADC. After the exit systemd restarts the
> programm and it runs fine again for hours. The function is called from a
> loop while another file with another fd is open (logfile for the adc-data,
> with a size of about 500bytes then a new logfile is started). The
> read_raw_adc_ch(0); is called every 10 seconds. As you can see I've tried
> to write a workaround with the error_ctr loop, but even the wait for one
> second does not help.
>
> Thanks for any ideas or suggestions.
>
> Alex
>
>
> $ cat /proc/version
> Linux version 4.19.94-ti-r42 (voodoo@x3-am57xx-beagle-x15-2gb) (gcc
> version 8.3.0 (Debian 8.3.0-6)) #1buster SMP PREEMPT Tue Mar 31 19:38:29
> UTC 2020
>
> cat /etc/debian_version
> 10.3
>
> Board: BeagleBoneBlack Rev. C
>
>
>
> 
> uint16_t read_raw_adc_ch(int channel)
> {
>
> uint8_t error_ctr;
> char str[MAX_BUF];
> int output_fd;
> extern int errno;
> error_ctr = 0;
> while (error_ctr < 8)
> {
>
> // oeffnen loest eine messung des adc aus
> if (channel==0) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage0_raw", O_RDONLY |
> O_ASYNC);
> if (channel==1) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage1_raw", O_RDONLY |
> O_ASYNC);
> if (channel==2) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage2_raw", O_RDONLY |
> O_ASYNC);
> if (channel==3) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage3_raw", O_RDONLY |
> O_ASYNC);
> if (channel==4) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage4_raw", O_RDONLY |
> O_ASYNC);
> if (channel==5) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage5_raw", O_RDONLY |
> O_ASYNC);
> if (channel==6) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage6_raw", O_RDONLY |
> O_ASYNC);
> if (channel==7) output_fd =
> open("/sys/bus/iio/devices/iio:device0/in_voltage7_raw", O_RDONLY |
> O_ASYNC);
>
> if (output_fd < 0)
> {
> error_ctr++;
> close(output_fd);
> sleep(1);
> }
> else
> {
> read(output_fd, str, 10);
> close(output_fd);
> return atoi(str);
> }
>
> }
>
>
> printf("ERROR OPEN ADC DEVICE, ERRNO: %d", errno);
> exit(EXIT_FAILURE);
>
> return 0;
> }
>
> 
>
> --
> 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/add6f258-c7f8-48ff-870f-b6f093838902o%40googlegroups.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/CACS14pi-bcm4i1-SvHeBaqwMDJc46UkXAHOAFeJ95MLL7VXiyQ%40mail.gmail.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[jonnymo]

I'm not sure what you did on the host but you need to set the iptables so
the traffic will go from the BB to the Internet from the host.  You could
do something like shown in the following link but for your Ethernet port vs
the USB network connect.
http://jpdelacroix.com/tutorials/sharing-internet-beaglebone-black.html

Connecting directly to a router would be much easier.

Jon

On Thu, Oct 8, 2020 at 12:06 PM jonnymo  wrote:

> For the Ubuntu issue not showing the ethernet port, perhaps this will help:
>
> https://askubuntu.com/questions/1146995/nm-connection-editor-not-showing-the-full-list-of-networks
>
>
> Jon
>
> On Thu, Oct 8, 2020 at 11:56 AM Pavel Yermolenko 
> wrote:
>
>> As I remember, when everything was Ok, I specified "Make available to
>> other users" in wired connection in network settings.
>> Now I don't see wired connection in network settings.
>>
>>
>> On Thursday, October 8, 2020 at 8:22:55 PM UTC+2, jonnymo wrote:
>>>
>>> The 169.x.x.x address on the BB I believe is just the default address
>>> when it can not connect to anything.  You could set it to something else
>>> manually.
>>>
>>> For internet access, you need to configure the routing so the BB will
>>> connect to the internet through the host ethernet port.
>>>
>>> I'm not sure what is causing the issue on the Ubuntu system since I do
>>> not use that tool.
>>>
>>> Jon
>>>
>>>
>>> On Thu, Oct 8, 2020 at 11:14 AM Pavel Yermolenko 
>>> wrote:
>>>
 Another issue appeared !!!
 I cannot get an internet connection - neither using *terminal* nor via
 *ssh*.

 --
 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 beagl...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/beagleboard/e23cc97f-500e-4a59-8ece-98647e24c5f4o%40googlegroups.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/407f028b-8580-40d4-b084-94d6ba8638b1o%40googlegroups.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/CAG99bkqj%3DGkAoLpxnvQZtHwFgn5ZFje6GhXuLzhOVvEYDPtJ_A%40mail.gmail.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[jonnymo]

For the Ubuntu issue not showing the ethernet port, perhaps this will help:
https://askubuntu.com/questions/1146995/nm-connection-editor-not-showing-the-full-list-of-networks


Jon

On Thu, Oct 8, 2020 at 11:56 AM Pavel Yermolenko 
wrote:

> As I remember, when everything was Ok, I specified "Make available to
> other users" in wired connection in network settings.
> Now I don't see wired connection in network settings.
>
>
> On Thursday, October 8, 2020 at 8:22:55 PM UTC+2, jonnymo wrote:
>>
>> The 169.x.x.x address on the BB I believe is just the default address
>> when it can not connect to anything.  You could set it to something else
>> manually.
>>
>> For internet access, you need to configure the routing so the BB will
>> connect to the internet through the host ethernet port.
>>
>> I'm not sure what is causing the issue on the Ubuntu system since I do
>> not use that tool.
>>
>> Jon
>>
>>
>> On Thu, Oct 8, 2020 at 11:14 AM Pavel Yermolenko 
>> wrote:
>>
>>> Another issue appeared !!!
>>> I cannot get an internet connection - neither using *terminal* nor via
>>> *ssh*.
>>>
>>> --
>>> 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 beagl...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/e23cc97f-500e-4a59-8ece-98647e24c5f4o%40googlegroups.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/407f028b-8580-40d4-b084-94d6ba8638b1o%40googlegroups.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/CAG99bkr2cJp9s2T24L4c5RiM23EhPw-cBYQYwTyDvf7g%3DHr5DQ%40mail.gmail.com.

[beagleboard] Re: Can't connet to BBB over Ethernet

[Pavel Yermolenko]

Before this "plague" happened I was able to connect to the Internet either 
by ssh or by terminal. Unfortunately I forgot what the connection 
parameters were on Ubuntu. The parameters of BBB I have not touched since.

On Thursday, October 8, 2020 at 8:54:59 PM UTC+2, Dennis Bieber wrote:
>
> On Thu, 8 Oct 2020 09:11:02 -0700 (PDT), in 
> gmane.comp.hardware.beagleboard.user Pavel Yermolenko 
> > wrote: 
>
>
> >No DHCPOFFERS received. 
> >No working leases in persistent database - sleeping. 
> >pavel@ALABAMA:~$ 
> > 
> >It remains to be seen where the problem comes from - Ubuntu host or BBB ? 
>
> Neither... and Both... 
>
> Based upon those messages, you appear to have no functional DHCP 
> server 
> running on either machine. Since you wired the two machines directly, each 
> is asking the other machine to provide it with an IP #. When they don't 
> get 
> one, they may do anything... 
>
> Your quickest solution would be to wire both machines to a single 
> COMMON router that has a DHCP server running. 
>
>
> -- 
> Dennis L Bieber 
>
>

-- 
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/65c3e74a-cbe2-4f26-9589-a9bccf017fa0o%40googlegroups.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[Pavel Yermolenko]

As I remember, when everything was Ok, I specified "Make available to other 
users" in wired connection in network settings.
Now I don't see wired connection in network settings.


On Thursday, October 8, 2020 at 8:22:55 PM UTC+2, jonnymo wrote:
>
> The 169.x.x.x address on the BB I believe is just the default address when 
> it can not connect to anything.  You could set it to something else 
> manually. 
>
> For internet access, you need to configure the routing so the BB will 
> connect to the internet through the host ethernet port.
>
> I'm not sure what is causing the issue on the Ubuntu system since I do not 
> use that tool. 
>
> Jon  
>
>
> On Thu, Oct 8, 2020 at 11:14 AM Pavel Yermolenko  > wrote:
>
>> Another issue appeared !!!
>> I cannot get an internet connection - neither using *terminal* nor via 
>> *ssh*.
>>
>> -- 
>> 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 beagl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/e23cc97f-500e-4a59-8ece-98647e24c5f4o%40googlegroups.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/407f028b-8580-40d4-b084-94d6ba8638b1o%40googlegroups.com.

[beagleboard] Re: Can't connet to BBB over Ethernet

[Dennis Lee Bieber]

On Thu, 8 Oct 2020 09:11:02 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Pavel Yermolenko
 wrote:


>No DHCPOFFERS received.
>No working leases in persistent database - sleeping.
>pavel@ALABAMA:~$
>
>It remains to be seen where the problem comes from - Ubuntu host or BBB ?

Neither... and Both...

Based upon those messages, you appear to have no functional DHCP server
running on either machine. Since you wired the two machines directly, each
is asking the other machine to provide it with an IP #. When they don't get
one, they may do anything...

Your quickest solution would be to wire both machines to a single
COMMON router that has a DHCP server running.


-- 
Dennis L Bieber

-- 
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/donunfljouuhhf9ud35bboahv57m8dgf2c%404ax.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[jonnymo]

The 169.x.x.x address on the BB I believe is just the default address when
it can not connect to anything.  You could set it to something else
manually.

For internet access, you need to configure the routing so the BB will
connect to the internet through the host ethernet port.

I'm not sure what is causing the issue on the Ubuntu system since I do not
use that tool.

Jon


On Thu, Oct 8, 2020 at 11:14 AM Pavel Yermolenko 
wrote:

> Another issue appeared !!!
> I cannot get an internet connection - neither using *terminal* nor via
> *ssh*.
>
> --
> 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/e23cc97f-500e-4a59-8ece-98647e24c5f4o%40googlegroups.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/CAG99bkpvWD82%2BGCFokqtBaPPTG%2BhfOkDyKsnRq3jRm2RdrS1PQ%40mail.gmail.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[Pavel Yermolenko]

Another issue appeared !!!
I cannot get an internet connection - neither using *terminal* nor via *ssh*
.

-- 
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/e23cc97f-500e-4a59-8ece-98647e24c5f4o%40googlegroups.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[Pavel Yermolenko]

Finally it works.
Thanks.
I specified IP staff manually in *nm-connection-editor* taking into account 
BBB IP:

[image: Screenshot from 2020-10-08 19-58-34.png]
Here is BBB *ifconfig*:
debian@beaglebone:~$ ifconfig
eth0: flags=-28605  mtu 1500
inet *169.254.44.158*  netmask 255.255.0.0  broadcast 
169.254.255.255
inet6 fe80::96e3:6dff:fed4:ae86  prefixlen 64  scopeid 0x20
ether 94:e3:6d:d4:ae:86  txqueuelen 1000  (Ethernet)
RX packets 30  bytes 3658 (3.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 57  bytes 15434 (15.0 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 55  

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 480  bytes 33280 (32.5 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 480  bytes 33280 (32.5 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4099  mtu 1500
inet 192.168.7.2  netmask 255.255.255.0  broadcast 192.168.7.255
ether 94:e3:6d:d4:ae:88  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4099  mtu 1500
inet 192.168.6.2  netmask 255.255.255.0  broadcast 192.168.6.255
ether 94:e3:6d:d4:ae:8c  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

debian@beaglebone:

Then I pinged Ubuntu from BBB and it was Ok.
Then I tried ssh connection and it also worked.
What is strange: the wired connection doesn't appears in main Ubuntu 
settings:

[image: Screenshot from 2020-10-08 20-04-56.png]


Before I encountered these connection issues, I could see a wired 
connection in the networks settings (screenshot above).

-- 
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/32bdcab7-8265-4462-90b6-da52b748d364o%40googlegroups.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[jonnymo]

The interface  enp8s0 is the physical Ethernet port from the Ubuntu host
that is directly connected to the BB, correct?
If this is correct, then enabling DHCP makes no sense unless you have set
up the BB as a DHCP server.  Since you are connecting these two devices
directly, then you need to either hardcode the IP address on the host
without DHCP and then set the IP on the BB.
If you do what I had shown previously, then that will give a clue if the
connection is working.

However, using Network Manager may interfere with any manual changes you
make.

Please look at the link I provided for more detail on how to troubleshoot a
network connection.


Jon

On Thu, Oct 8, 2020 at 9:11 AM Pavel Yermolenko  wrote:

> Here is what happens when I try activate it:
>
> pavel@ALABAMA:~$ sudo ifup enp8s0
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
>
> Listening on LPF/enp8s0/8c:16:45:a9:fe:44
> Sending on   LPF/enp8s0/8c:16:45:a9:fe:44
> Sending on   Socket/fallback
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 3
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 3
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 20
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 7
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 14
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 14
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 7
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 9
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 20
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 17
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 9
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 10
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 15
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13
> (xid=0xdd23072a)
> DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 2
> (xid=0xdd23072a)
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> pavel@ALABAMA:~$
>
> It remains to be seen where the problem comes from - Ubuntu host or BBB ?
>
> --
> 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/e4e06643-8a2c-472e-bf72-d1fa4d714fbdo%40googlegroups.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/CAG99bkpZvqoU5RJ_b2anCHJ8mG4iw%2BOQVRx7g-LfbAJ%2BX-_1Vg%40mail.gmail.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[Pavel Yermolenko]

Here is what happens when I try activate it:

pavel@ALABAMA:~$ sudo ifup enp8s0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp8s0/8c:16:45:a9:fe:44
Sending on   LPF/enp8s0/8c:16:45:a9:fe:44
Sending on   Socket/fallback
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 3 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 3 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 20 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 7 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 14 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 14 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 7 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 9 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 20 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 17 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 9 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 10 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 15 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 11 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 8 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 13 
(xid=0xdd23072a)
DHCPDISCOVER on enp8s0 to 255.255.255.255 port 67 interval 2 
(xid=0xdd23072a)
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
pavel@ALABAMA:~$

It remains to be seen where the problem comes from - Ubuntu host or BBB ?

-- 
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/e4e06643-8a2c-472e-bf72-d1fa4d714fbdo%40googlegroups.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[Pavel Yermolenko]

[image: Screenshot from 2020-10-08 17-49-50.png]
Also this annoying message periodically appears at the top of Ubuntu 
desktop:

-- 
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/3e555cd4-3288-4308-b714-de58ff2f16c0o%40googlegroups.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[Pavel Yermolenko]

I deleted existing wired connection using *nm-connection-editor.*
I couldn't do it in property editor (i.e. Settings/Network) in because it 
was invisible there.
Then I created new one using *nm-connection-editor.*
During creation I leaved default settings, I specified only name*.*
Although new connection is now visible in Settings/Network, the issue 
persists.
*ifconfig *doesn't show IP address of Ethernet connection and ssh 
connection to BBB fails.

-- 
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/28ddb656-f736-4063-830c-390fe9ca2a3bo%40googlegroups.com.

Re: [beagleboard] Re: Beaglebone black connect to Web

[jonnymo]

Are you following the instructions listed at the following link?
https://www.digikey.com/en/maker/blogs/how-to-connect-a-beaglebone-black-to-the-internet-using-usb

Have you set the default router on your BBB?
Ex:
   * sudo /sbin/route add default gw 192.168.7.1  *

Cheers,

Jon

On Thu, Oct 8, 2020 at 6:16 AM Tarmo  wrote:

> On Thursday, October 8, 2020 at 3:16:24 PM UTC+3 dysona...@gmail.com
> wrote:
>
>> I have a beaglebone black and I'm attempting to connect it to the outside
>> world.  I have the latest debian image installed.
>>
>> Here is what I have done:
>>
>> - installed latest windows 64 bit drivers
>> - Configured my wifi network adapter to be shared with the network
>> adapter created through the USB cable connection.
>>
>> When I attempt to ping www.google.com I get the error "Temporary failure
>> in name resolution"
>>
>> Any help would be of benefit.
>>
>
> IIRC the BB-s virtual Ethernet port is not configured to be an uplink to
> the Internet - the Ethernet port is. Changing this is going to be tricky
> (not impossible, but requires in-depth understanding of what you're doing).
>
> The simplest way to solve your problem is to connect the BB to Internet
> using an Ethernet cable and your nearest router.
>
> --
> Kind regards,
> Tarmo
>
> --
> 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/2f1af32f-1814-4d5d-837b-4aea0dc59984n%40googlegroups.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/CAG99bkrhYXDMZ8D1yPZA5uqP6egiTXmFSpDhEf8n%3D-OQx1WEkw%40mail.gmail.com.

[beagleboard] Re: Beaglebone black connect to Web

[Tarmo]

On Thursday, October 8, 2020 at 3:16:24 PM UTC+3 dysona...@gmail.com wrote:

> I have a beaglebone black and I'm attempting to connect it to the outside 
> world.  I have the latest debian image installed.
>
> Here is what I have done:
>
> - installed latest windows 64 bit drivers
> - Configured my wifi network adapter to be shared with the network adapter 
> created through the USB cable connection.
>
> When I attempt to ping www.google.com I get the error "Temporary failure 
> in name resolution"
>
> Any help would be of benefit.
>

IIRC the BB-s virtual Ethernet port is not configured to be an uplink to 
the Internet - the Ethernet port is. Changing this is going to be tricky 
(not impossible, but requires in-depth understanding of what you're doing).

The simplest way to solve your problem is to connect the BB to Internet 
using an Ethernet cable and your nearest router.

--
Kind regards,
Tarmo

-- 
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/2f1af32f-1814-4d5d-837b-4aea0dc59984n%40googlegroups.com.

[beagleboard] Beaglebone black connect to Web

[dysonator619]

Hi,

I have a beaglebone black and I'm attempting to connect it to the outside 
world.  I have the latest debian image installed.

Here is what I have done:

- installed latest windows 64 bit drivers
- Configured my wifi network adapter to be shared with the network adapter 
created through the USB cable connection.

When I attempt to ping www.google.com I get the error "Temporary failure in 
name resolution"

Any help would be of benefit.

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/1de18302-dda3-40ea-bb07-7e16c87e367do%40googlegroups.com.