Re: [beagleboard] How use SGX / PowerVR on BBB in 2019 ?

[Robert Nelson]

Hi Rémi,

On Sun, Mar 17, 2019 at 10:22 PM  wrote:
>
> I detail how use the new SGX drivers, the link is here:
> https://elinux.org/BeagleBoneBlack/SGX_%2B_Qt_EGLFS_%2B_Weston
>
> What do you think Robert? Do you think that the SGX drivers /GBM and Weston 
> patched can appear in an official version of the BeagleBone?
>
> I think it's important to have these tools especially with the arrival of the 
> next generation of BeagleBone. Many people need the GUI.
>
> I hope this will help some people.

This is awesome, what you've done!

I'll start packing some of the bits you utilized, so we can get this
out into the apt repo..

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

Re: [beagleboard] pocket beagle not clean shutdown?

[Robert Nelson]

On Tue, Mar 19, 2019 at 3:09 PM Kristian Bertram
 wrote:
>
> No, i just have to use kernel 4.9 because og some legacy code unfortunately, 
> so the issues is still there for me

Well it's a two part fix.

1: u-boot has to set the correct rtc bit:

https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2018.09/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L173-L195

2: the kernel has to have the correct bit set:

https://github.com/beagleboard/linux/blob/4.9/arch/arm/boot/dts/am335x-pocketbeagle-common.dtsi#L1127-L1129

When those two are set, it'll properly shutdown.

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

[beagleboard] Re: BBG PRU DMA - rproc and DMA driver

[dine909]

Digging deeper, in `modules.dep` 

kernel/drivers/remoteproc/pru_rproc.ko: 
kernel/drivers/remoteproc/pru_dma.ko 
kernel/drivers/remoteproc/pruss_intc.ko kernel/drivers/remoteproc/pruss.ko
kernel/drivers/remoteproc/pru_dma.ko: 
kernel/drivers/remoteproc/pruss_intc.ko kernel/drivers/remoteproc/pruss.ko
and lsmod results:

pru_rproc  15930  0
pru_dma 7646  1 pru_rproc
pruss_intc  8964  2 pru_dma,pru_rproc
pruss  10826  2 pru_dma,pru_rproc

It does appear there is a circular dependancy issue.. 

-- 
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/495a91c0-6569-4d13-9541-335dfe061e01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBG PRU DMA - rproc and DMA driver

[dine909]

Digging deeper, in `modules.dep` 

kernel/drivers/remoteproc/pru_rproc.ko: kernel/drivers/remoteproc/pru_dma.ko 
kernel/drivers/remoteproc/pruss_intc.ko kernel/drivers/remoteproc/pruss.ko

and lsmod results:

pru_rproc  15930  0
pru_dma 7646  1 pru_rproc
pruss_intc  8964  2 pru_dma,pru_rproc
pruss  10826  2 pru_dma,pru_rproc

It does appear there is a circular dependancy issue.. 

-- 
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/776546b7-2592-434c-a932-4a4e8c26a560%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] pocket beagle not clean shutdown?

[Robert Nelson]

On Tue, Mar 19, 2019 at 1:23 PM  wrote:
>
> How exactly do i change the value of the register? I have no idea which file 
> to look for

The default BeagleBoard images already take care of this issue now..

Are you trying to modify that register in a non-u-boot, non-linux OS?

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

Re: [beagleboard] pocket beagle not clean shutdown?

[kristianbertramlarsen]

How exactly do i change the value of the register? I have no idea which 
file to look for 

onsdag den 4. april 2018 kl. 15.55.41 UTC+2 skrev beatb...@gmail.com:
>
> The problem seems to be, that the rtc has no active oscillator:
> If I set RTC_OSC_REG to 0x40 (internal oscillator) shutdown works normal.
> But I'm not sure whether this is the correct way to solve this issue.
>
> Regards
> Beat Bieler
>
>

-- 
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/62d71d5d-559c-4e84-a704-8e1be43cc507%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: how to disable HDMI / eMMc pins in BeagleBone Black

[Hugo Casal]

Thank you very much
Hugo

El lun., 18 de mar. de 2019 07:18,  escribió:

> Hello Hugo,
>
> you can disable with editing the file* /boot/uEnv.txt*
> Check your kernel version before ( *uname -r *)
>
> For *v3.8.x* kernel:
> #Disable HDMI/eMMC
>
> cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
> #Disable HDMI
> cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> #Disable eMMC
> cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G
>
>
> For *v4.1.x* kernel:
> #HDMI (Audio/Video) disabled:
> dtb=am335x-boneblack-emmc-overlay.dtb
> #eMMC disabled:
> dtb=am335x-boneblack-hdmi-overlay.dtb
> #HDMI Audio/eMMC disabled:
> dtb=am335x-boneblack-nhdmi-overlay.dtb
> #HDMI (Audio/Video)/eMMC disabled:
> dtb=am335x-boneblack-overlay.dtb
>
>
> For *v4.4.x, v4.9.x, v4.14.x and higher* kernel:
> ##Disable auto loading of virtual capes (emmc/video/wireless/adc)
> #Disable eMMC
> disable_uboot_overlay_emmc=1
> #Disable HDMI
> disable_uboot_overlay_video=1
> #Disable Audio
> disable_uboot_overlay_audio=1
> #Disable Wireless
> disable_uboot_overlay_wireless=1
> #Disable ADC
> disable_uboot_overlay_adc=1
>
>
>
>
> Le dimanche 17 mars 2019 14:57:30 UTC+1, hcasalnc...@gmail.com a écrit :
>>
>>
>> Hello
>>
>> In my project I am needing  to use 30  pins of  the P8 expansion header
>>  and 6 pins of  the P9 expansion header as GPIO only, also I will use all
>> analog pins(P9). I do not  need  to use the HDMI neither eMMc pins . I have
>> been reading information about this  and I believe is necessary to
>> configure the BBB to operate in mode 7.
>>
>> How can I do it?
>>
>> Thanks
>>
>> Hugo
>>
>>
>>
>>
>>
> --
> 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/5dfd71c1-a390-486e-a02f-9138be583f89%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/CAGvkCdWJTVBDaX%2B3ugi%2BKv-sQXbA9AgSLZPQkwwncK0eatPJUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Cannot ping google in BBB even after sharing internet

[LuminousShadow]

I've had a similar issue when trying to share my internet to my BBBW. I had 
the system going and working. I then wanted to try another OS and installed 
a new one. When I tried to ping 8.8.8.8 after modifying resolv I wasn't 
getting any comm outside.
But, I've pinged internal local host (worked) so I figured it had to do 
with the fact that my host system still had settings listed for the old OS.

What I've found to work for me is remove the shared internet connection and 
restart both systems. Then set up the connection sharing again and changing 
the RNDIS adapter's setting to Dynamic.

After that I logged into my BBBW and tried to ping 8.8.8.8 and 
www.google.com, both worked without issues.

Hope something there helps.

On Saturday, January 17, 2015 at 6:47:24 AM UTC-5, Raj_RB wrote:
>
> Hi,
>
> 1) I downloaded 'bone-debian-7.5-2014-05-14-2gb' (BBB eMMC flasher) from '
> http://beagleboard.org/latest-images' and the website given MD5 checksum 
> matched with my downloaded zip file. Then used Win32 Disk Imager (since 
> windows 7), for image writing 4GB microSD.
>
> 2) Inserted microSD into BBB and pressed the boot button and then applied 
> power using the power adapter. (Please note that I have not connected 
> Ethernet and USB cable for power during the whole flashing process). But 
> only power supply LED got lit and not the user LEDs for around 5 seconds. 
> Then I removed the power supply and while pressing the boot button, I 
> provided the power supply and then all LEDs got lit for an instance and 
> then the LEDs started to glow erratically. Within 20 mins all the User 
> LED were off and did not ON again as against the standard procedure in 
> which all LEDs must glow after successful flashing of eMMC.
>
> 3) So, I thought to see if this works and I removed the microSD and power. 
> Then I connected BBB with my PC (by USB) using putty (SSH). I was able to 
> login successfully into debian but I was not able to ping google after 
> adding new gateway (192.168.7.1) and changing nameserver to 8.8.8.8 in 
> '/etc/resolv.conf' file.
>
> Please note that before SSH-ing, I shared my wifi internet with BBB in 
> Network settings(Windows 7) and also I changed the IP address of my BBB to 
> 192.168.7.1. All this worked earlier for me by following this youtube link: 
> (https://www.youtube.com/watch?v=D-NEPiZDSx8). 
>
> Also, BBB (Linux USB ethernet/ RNDIS gadget) in Network settings shows 'No 
> Internet access' eventhough I have shared internet and changed my ip 
> address to 192.168.7.1 with subnet mask 255.255.255.0 leaving the DNS 
> server addresses blank as in the youtube video.
>
> But now it doesn't work eventhough I have already done the same procedure 
> (flashing) many times now with the same result and feeling really 
> frustrated now. Please let me know if I am missing anything here. Is it due 
> to the flashing issue? 
> Waiting for all your inputs! Thank you!!
>
>
> Output:
>
> BeagleBoard.org BeagleBone Debian Image 2014-05-14
> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
> deb...@192.168.7.2 's password:
> Last login: Thu May 15 02:19:40 2014 from 192.168.7.1
> debian@beaglebone:~$ sudo su
> root@beaglebone:/home/debian# route add default gw 192.168.7.1
> root@beaglebone:/home/debian# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 192.168.7.1 0.0.0.0 UG 0 0 0 usb0
> 192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0
> root@beaglebone:/home/debian# cat /etc/resolv.conf
> domain localdomain
> search localdomain
> nameserver 192.168.1.1
> root@beaglebone:/home/debian# vim /etc/resolv.conf
> root@beaglebone:/home/debian# cat /etc/resolv.conf
> domain localdomain
> search localdomain
> nameserver 8.8.8.8
> root@beaglebone:/home/debian# ping http://www.google.com
> ping: unknown host http://www.google.com
> root@beaglebone:/home/debian#
>
>

-- 
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/199676fc-9f1c-494f-ac8b-b5b5abe2f4f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Sudoers File get Corrupted.

[Jim F]

Do you have the root password? If so you can su and then fix it. If not you
should look up how to break in to a Linux system, which is usually a mod to
the boot command. Search for single user mode. Probably you'll need a
serial to USB cable for your board. If you messed up the image on the mmc
instead you can boot off an SD card and then chroot to the emmc image and
reset the root pass.

Next time you edit your sudoers file use the command visudo which will
check that the file is valid prior to saving.

Jim

On Tue, Mar 19, 2019, 7:42 AM  Hi,
>   I did a some change in sudoers file, so i can not be root , i can not
> use sudo or su
> debian@beaglebone: sudo su -
> sudo: >>> /etc/sudoers: syntax error near line 23 <<<
> sudo: parse error in /etc/sudoers near line 23
> sudo: no valid sudoers sources found, quitting
> sudo: unable to initialize policy plugin
>
> How can I correct this file ?
> Thank You
>
> --
> 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/88e3e3b5-2619-4c3c-865a-30179b1ab62f%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/CAGS%2B2h8JV8Fk7R1dgSnht08MX5k8mCGEOCKkL2FtgCmTh7KzcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBG PRU DMA - rproc and DMA driver

[dine909]

Further info, i have attempted to force the module load order using 
MODULE_SOFTDEP in the pru_dma module code:

MODULE_SOFTDEP("post: pru_rproc")
MODULE_SOFTDEP("post: pruss_soc_bus")
MODULE_SOFTDEP("post: pruss")

https://github.com/dine909/beaglebone-pru-dma/blob/master/kernel-patch/rcn-ee-tree-patch/0001-Add-pru-dma-patches.patch#L133

but this has had no effect.

-- 
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/01bc84e5-619a-4c68-8d23-8e34d8025252%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone Sudoers File get Corrupted.

[sayalikutwal07]

Hi, 
  I did a some change in sudoers file, so i can not be root , i can not use 
sudo or su 
debian@beaglebone: sudo su -
sudo: >>> /etc/sudoers: syntax error near line 23 <<<
sudo: parse error in /etc/sudoers near line 23
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin

How can I correct this file ?
Thank You

-- 
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/88e3e3b5-2619-4c3c-865a-30179b1ab62f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone AI

[Andrew117]

среда, 6 марта 2019 г., 1:00:15 UTC+2 пользователь Graham написал:
>
>
> https://beagleboard.org/ai
>
> Hmm.
>
> --- Graham
>
> ==
>


Fitting 4 PRUs into the same BBB connector... probably it's a difficult 
tradeoff with other IO lines. 

-- 
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/7f9e4359-a44b-44a3-8568-2382f38cd355%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to use GPIO as spi chipselect.

[graham]

You can not have the SPI hardware manage one of the SPI chip select lines, 
and you bit-bang the other.
Either you let the SPI hardware manage both of them, which you can not do 
in this case, because of assignment conflict, or you must bit-bang both of 
the CS lines.
So, set it up as a single generic SPI driver, and pick any two GPIO pins 
for chip-select lines.
One of them could be the same pin as CS0, just configured as a GPIO pin.
You will need to write a little wrapper for the SPI call, that drops the 
appropriate CS line, before you write to the SPI hardware.
You will need to raise the appropriate CS line when the SPI hardware is 
done sending.
DO NOT send your last data to the SPI hardware and immediately raise the CS 
line.
The SPI hardware is a parallel to serial device, and will still be sending 
data for some time after the data is written to it to send.
--- Graham

==

On Saturday, March 16, 2019 at 11:18:57 PM UTC-5, Dave wrote:
>
> I am working on a board that is derived from a Pocket Beagle. 
>
> It has two max81355 SPI Thermocouples on SPI0. 
>
> The first uses spi0_cs0 as a chip select. 
>
> spi0_cs1 is used for mmc.cd so that can not be used for the second. 
>
> The hardware designer used spio_d1(MOSI) set as a GPIO for the 2nd chip 
> select. 
>
> I have no clue how to set the device tree entry for that.
>
> This is what I have - which I do not think can work.  
>
> fragment@1 {
> target = <_pinmux>;
> __overlay__ {
> pb_spi0_pins: pinmux_pb_spi0_pins {
> pinctrl-single,pins = <
> /* SPI0_SCLK STATUS:WORKS ??? */  
> AM33XX_IOPAD(0x0950, PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE0 )  /* A13 
> P1.08  SPI0_SCLK 0x150 GPIO2 GPIO0_2 SCLK */
> /* SPI0_DO STATUS:WORKS ??? */  
> AM33XX_IOPAD(0x0954, PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE0 )  /* B13 
> P1.10  SPI0_D0   0x154 GPIO3 GPIO0_3 MISO */
> /* SPI0_D1 STATUS:UNKNOWN */  
> AM33XX_IOPAD(0x0958, PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE7 ) /* B14 
> P1.12  SPI0_D1   0x158 GPIO4 GPIO0_4 TC1 */
> /* SPI0_CS0 STATUS:WORKS ??? */  
> AM33XX_IOPAD(0x095c, PIN_OUTPUT_PULLUP | INPUT_EN | MUX_MODE0 ) /* A14 
> P1.06  SPI0_CS   0x15c GPIO5 GPIO0_5 TC0 */
> >;
> };
> };
> };
> fragment@2 {
> target = <>;
> __overlay__ {
> #address-cells = <1>;
> #size-cells = <0>;
>
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <_spi0_pins>;
> ti,pio-mode; /* disable dma when used as an overlay, dma gets stuck at 160 
> bits... */
>
> channel@0 {
> #address-cells = <1>;
> #size-cells = <0>;
> compatible = "spidev";
> reg = <0>;
> spi-max-frequency = <430>;
> spi-cpha;
> };
>
> channel@1 {
> #address-cells = <1>;
> #size-cells = <0>;
> compatible = "spidev";
> reg = <1>;
> spi-max-frequency = <430>;
> };
> };
> };
>
>
>
>
>
>

-- 
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/ce3cba45-0bf3-48fe-9fc7-ff2c0d41f61f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Cannot ping google in BBB even after sharing internet

[cjohnweb]

This is a domain name resolution issue.

You can verify that you can ping IP Addresses, ie 8.8.8.8
But you can't ping domain names, ie google.com

Does this sound like you?

On Beaglebone running Debian, setting the nameserver or dns-nameservers 
directives 
in /etc/network/interfaces does NOT solve this problem.
Writing nameserver 8.8.8.8 directive to /etc/resolv.conf does NOT solve 
this problem.
Can't apt-get update (uses domain names, right), so you can't just 
reinstall a new DNS resolver.
Reinstalling apt-get install resolvconf, if it successfully installs, still 
doesn't fix the problem.
Setting the default gateway (/sbin/route add default gw 192.168.7.1) 
doesn't help...


Here is the problem. dhclient needs to be running. Ensure you have at least 
one valid name server in your /etc/resolv.conf ie nameserver 8.8.8.8

Then run dhclient

Then try to ping google.com

root@sg1:~# ping google.com
>
> ping: unknown host google.com
>
> root@sg1:~# pico /etc/resolv.conf
>
> root@sg1:~# dhclient
>
> root@sg1:~# ping google.com
>
> PING google.com (172.217.0.46) 56(84) bytes of data.
>
> 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=1 ttl=55 
> time=8.62 ms
>
> 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=2 ttl=55 
> time=8.24 ms
>
> 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=3 ttl=55 
> time=8.21 ms
>
> 64 bytes from lga15s43-in-f46.1e100.net (172.217.0.46): icmp_req=4 ttl=55 
> time=8.35 ms
>
> ^C
>
> --- google.com ping statistics ---
>
> 4 packets transmitted, 4 received, 0% packet loss, time 5531ms
>
> rtt min/avg/max/mdev = 8.214/8.360/8.625/0.161 ms
>
> root@sg1:~# 
>
>
>

If this doesn't work for you, if you go back and check your 
/etc/resolv.conf file, you may notice that it's contents have changed. 
These settings are written to this file automatically from dhclient, often 
based upon what the DHCP server gives. And these settings come from your 
/etc/network/interfaces values. Verify that your networks DHCP server is 
serving the correct name server IP's and repeat your dhclient command.




On Saturday, January 17, 2015 at 3:47:24 AM UTC-8, Raj_RB wrote:
>
> Hi,
>
> 1) I downloaded 'bone-debian-7.5-2014-05-14-2gb' (BBB eMMC flasher) from '
> http://beagleboard.org/latest-images' and the website given MD5 checksum 
> matched with my downloaded zip file. Then used Win32 Disk Imager (since 
> windows 7), for image writing 4GB microSD.
>
> 2) Inserted microSD into BBB and pressed the boot button and then applied 
> power using the power adapter. (Please note that I have not connected 
> Ethernet and USB cable for power during the whole flashing process). But 
> only power supply LED got lit and not the user LEDs for around 5 seconds. 
> Then I removed the power supply and while pressing the boot button, I 
> provided the power supply and then all LEDs got lit for an instance and 
> then the LEDs started to glow erratically. Within 20 mins all the User 
> LED were off and did not ON again as against the standard procedure in 
> which all LEDs must glow after successful flashing of eMMC.
>
> 3) So, I thought to see if this works and I removed the microSD and power. 
> Then I connected BBB with my PC (by USB) using putty (SSH). I was able to 
> login successfully into debian but I was not able to ping google after 
> adding new gateway (192.168.7.1) and changing nameserver to 8.8.8.8 in 
> '/etc/resolv.conf' file.
>
> Please note that before SSH-ing, I shared my wifi internet with BBB in 
> Network settings(Windows 7) and also I changed the IP address of my BBB to 
> 192.168.7.1. All this worked earlier for me by following this youtube link: 
> (https://www.youtube.com/watch?v=D-NEPiZDSx8). 
>
> Also, BBB (Linux USB ethernet/ RNDIS gadget) in Network settings shows 'No 
> Internet access' eventhough I have shared internet and changed my ip 
> address to 192.168.7.1 with subnet mask 255.255.255.0 leaving the DNS 
> server addresses blank as in the youtube video.
>
> But now it doesn't work eventhough I have already done the same procedure 
> (flashing) many times now with the same result and feeling really 
> frustrated now. Please let me know if I am missing anything here. Is it due 
> to the flashing issue? 
> Waiting for all your inputs! Thank you!!
>
>
> Output:
>
> BeagleBoard.org BeagleBone Debian Image 2014-05-14
> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
> deb...@192.168.7.2 's password:
> Last login: Thu May 15 02:19:40 2014 from 192.168.7.1
> debian@beaglebone:~$ sudo su
> root@beaglebone:/home/debian# route add default gw 192.168.7.1
> root@beaglebone:/home/debian# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 192.168.7.1 0.0.0.0 UG 0 0 0 usb0
> 192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0
> root@beaglebone:/home/debian# cat /etc/resolv.conf
> domain localdomain
> search localdomain
> nameserver 192.168.1.1
> root@beaglebone:/home/debian# vim