Mark,

Thank you. However, I just found at solution. I was trying to SSH into the 
192.168.7.2 address which wouldn't work because the virutal adapter didn't 
have an address on the same subnet. However, after reading some other 
threads I switched to the 12-12-2016 image and everything seems to be 
working perfectly now. the 12-05-2016 didn't work after several tries. 

I believe it's probably just an issue with the configuration of that image. 
The factory image worked as well as the 12-12-2016 image. 

To answer your question directly, I was flashing the eMMC and booting from 
eMMC. The boot seams to work, but I don't have a serial connector with me 
to check any settings in the OS. 

Thanks,

Gregg


On Wednesday, December 14, 2016 at 12:02:53 PM UTC-8, Mark wrote:
>
> Hello Gregg --
>
> Sorry to hear you are having problems with your new board.
>
> What do you get when you type 192.168.7.2 into your web browser? These 
> boards prefer Chrome.
>
> Are you booting from the SD card, or flashing the eMMC and booting from 
> there?
>
> Mark
>
>
>
> On Wednesday, December 14, 2016 at 9:31:08 AM UTC-10, Gregg Harrington 
> wrote:
>>
>> Hello,
>>
>> I am having a problem with getting the USB Ethernet bridge working with 
>> the suggestion 12-05-2016 image. When I connect the BBBWL I get the windows 
>> partion to show up, which usually means the virutal ethernet port is 
>> loaded. Which it does load, but it doesn't get a 192.168.7.1 address, 
>> instead it gets a 169.254.244.251 address. Usually a disconnect and 
>> reconnect will fix this problem, but no such luck. I am downloading some of 
>> the latest images to try, but I am curious if this is a known issue?
>>
>> Please note, the driver seems to be working as a my Rev C board is 
>> connecting up correctly. 
>>
>> Cheers,
>>
>> Gregg
>>
>>
>> On Tuesday, December 13, 2016 at 4:40:33 AM UTC-8, Mark wrote:
>>>
>>> Hi Robert --
>>>
>>> So yes, success. Although I will still beg your advice on the eeprom 
>>> problem. I have found that booting from SD card causes some problem with 
>>> dropping my shell connxn, something not encountered if I just flash the 
>>> onboard eMMC. I wonder if this is going to be a problem down the road when 
>>> I want to boot off an 8 or 16 GB card.
>>>
>>> root@beaglebone:~# dmesg | grep wlcore
>>> [   43.191825] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
>>> [   43.272449] wlcore: loaded
>>> [   43.734400] wlcore: PHY firmware version: Rev 8.2.0.0.236
>>> [   43.783333] wlcore: firmware booted (Rev 8.9.0.0.69)
>>> [   48.563112] wlcore: Association completed.
>>> root@beaglebone:~#
>>>
>>> connmanctl> services wifi_my-hash_managed_psk
>>> /net/connman/service/wifi_my-hash_managed_psk
>>>   Type = wifi
>>>   Security = [ psk, wps ]
>>>   State = online
>>>   Strength = 57
>>>   Favorite = True
>>>   Immutable = False
>>>   AutoConnect = True
>>>   Name = SBG6580A9
>>>   Ethernet = [ Method=auto, Interface=wlan0, Address=50:65:83:D6:06:A5, 
>>> MTU=1500 ]
>>>   IPv4 = [ Method=manual, Address=192.168.0.133, Netmask=255.255.255.0, 
>>> Gateway=192.168.0.1 ]
>>>   IPv4.Configuration = [ Method=manual, Address=192.168.0.133, 
>>> Netmask=255.255.255.0, 
>>> Gateway=192.168.0.1 ]
>>>   IPv6 = [  ]
>>>   IPv6.Configuration = [ Method=auto, Privacy=disabled ]
>>>   Nameservers = [ 8.8.8.8, 8.8.4.4 ]
>>>   Nameservers.Configuration = [ 8.8.8.8, 8.8.4.4 ]
>>>   Timeservers = [ 192.168.0.1 ]
>>>   Timeservers.Configuration = [  ]
>>>   Domains = [ www.google.com ]
>>>   Domains.Configuration = [ www.google.com ]
>>>   Proxy = [ Method=direct ]
>>>   Proxy.Configuration = [  ]
>>>   Provider = [  ]
>>> connmanctl> quit
>>> root@beaglebone:~#
>>> root@beaglebone:~# uname -a
>>> Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l 
>>> GNU/Linux
>>> root@beaglebone:~# cat /etc/dogtag
>>> BeagleBoard.org Debian Image 2016-11-06
>>>
>>>
>>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/58dcd7ba-b1ad-41b0-83a6-1bd9bcb4bb63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to