Re: [beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Niresh]

Is there a way to access the beagle-bone using SSH or something like that
without registering the device to another server?
This is for commercial purposes and data protection is very important.
Right now, it is connected to the AWS cloud server where our web
application is running.


Thanks and regards,
NK

On Thu, Oct 15, 2020 at 10:57 AM Shafeek Ashraf 
wrote:

> Hi,
> You can use pi tunnel for beaglebone also if you have a debian os running
> in the bbb. Just follow the steps in the pitunnel page, create an account
> and add device, while adding device they will ask you to download and
> install pitunnel files, ie that will be running in background in the bbb.
>
> On Thu, 15 Oct 2020, 10:43 Niresh,  wrote:
>
>> Hi,
>> I googled and understand pitunnel is for raspberry pi, what is the
>> similar thing for beagle bone. Please share a good link to understand the
>> process in a better way.
>> Do I need to register on a server for remote access?
>> How do I differentiate multiple beagle-bones for remote access?
>> What is the limitation on the number of beagle-bones?
>>
>> Regards,
>> NK
>>
>> On Thu, Oct 15, 2020 at 10:27 AM Shafeek Ashraf <
>> shafeekashra...@gmail.com> wrote:
>>
>>> Hi,
>>> You can use services like Pitunnel for accesing and modifying beaglebone
>>> through remote acess
>>>
>>> On Thu, 15 Oct 2020, 09:58 Niresh,  wrote:
>>>
 Hi,
 Could you please help me the best utility to implement this and
 procedure to do so, and also how to use a static IP address in
 beagle-bone-black?

 Thanks and regards,
 NK

 On Thu, Oct 15, 2020 at 9:24 AM Atique Rehman 
 wrote:

> You need some sort of client application running on the beaglebone
> which can receive new apps from server.
> To access to beagle-bone remotely you should have its static IP
> address.
>
> On Thursday, October 15, 2020 at 2:38:23 PM UTC+11 Niresh wrote:
>
>> Hi,
>> I am using Beagle Bone Black with Debian image and kernel version
>> 4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black
>> remotely. Let me explain the requirement, I have an application running 
>> on
>> BBB and connected to AWS cloud server through web socket. Now, just in 
>> case
>> want to upgrade the application remotely from cloud server, how do I do
>> that?
>>
>> Thanks and regards,
>> NK
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/a5da3147-9939-448a-b89e-8e1f32bfed18n%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/CAF7-PaSkswyoUsWWpfHm%3DezHURqLT1kEsLdrihmZ12y-EDVPVg%40mail.gmail.com
 
 .

>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/CANSAWx-gohG-CEGmoC7gWcm5qevBdZ3NWRwKRHtnEzCdayZ7uQ%40mail.gmail.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/CAF7-PaQU62H5j

Re: [beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Shafeek Ashraf]

Hi,
You can use pi tunnel for beaglebone also if you have a debian os running
in the bbb. Just follow the steps in the pitunnel page, create an account
and add device, while adding device they will ask you to download and
install pitunnel files, ie that will be running in background in the bbb.

On Thu, 15 Oct 2020, 10:43 Niresh,  wrote:

> Hi,
> I googled and understand pitunnel is for raspberry pi, what is the similar
> thing for beagle bone. Please share a good link to understand the process
> in a better way.
> Do I need to register on a server for remote access?
> How do I differentiate multiple beagle-bones for remote access?
> What is the limitation on the number of beagle-bones?
>
> Regards,
> NK
>
> On Thu, Oct 15, 2020 at 10:27 AM Shafeek Ashraf 
> wrote:
>
>> Hi,
>> You can use services like Pitunnel for accesing and modifying beaglebone
>> through remote acess
>>
>> On Thu, 15 Oct 2020, 09:58 Niresh,  wrote:
>>
>>> Hi,
>>> Could you please help me the best utility to implement this and
>>> procedure to do so, and also how to use a static IP address in
>>> beagle-bone-black?
>>>
>>> Thanks and regards,
>>> NK
>>>
>>> On Thu, Oct 15, 2020 at 9:24 AM Atique Rehman 
>>> wrote:
>>>
 You need some sort of client application running on the beaglebone
 which can receive new apps from server.
 To access to beagle-bone remotely you should have its static IP address.

 On Thursday, October 15, 2020 at 2:38:23 PM UTC+11 Niresh wrote:

> Hi,
> I am using Beagle Bone Black with Debian image and kernel version
> 4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black
> remotely. Let me explain the requirement, I have an application running on
> BBB and connected to AWS cloud server through web socket. Now, just in 
> case
> want to upgrade the application remotely from cloud server, how do I do
> that?
>
> Thanks and regards,
> NK
>
 --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups "BeagleBoard" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/beagleboard/a5da3147-9939-448a-b89e-8e1f32bfed18n%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/CAF7-PaSkswyoUsWWpfHm%3DezHURqLT1kEsLdrihmZ12y-EDVPVg%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CANSAWx-gohG-CEGmoC7gWcm5qevBdZ3NWRwKRHtnEzCdayZ7uQ%40mail.gmail.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/CAF7-PaQU62H5jM-N_mms61-X5YVhvv4y-Uwa7jWn%3DRmdhkJ7Pg%40mail.gmail.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 di

Re: [beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Atique Rehman]

If you can put some effort here is an most common solution for remote 
access OpenVPN
https://wiki.debian.org/OpenVPN#Debian_Server_with_Android_.2F_iOS_devices

On Thursday, October 15, 2020 at 4:13:33 PM UTC+11 Niresh wrote:

> Hi,
> I googled and understand pitunnel is for raspberry pi, what is the similar 
> thing for beagle bone. Please share a good link to understand the process 
> in a better way.
> Do I need to register on a server for remote access? 
> How do I differentiate multiple beagle-bones for remote access?
> What is the limitation on the number of beagle-bones?  
>
> Regards,
> NK
>
> On Thu, Oct 15, 2020 at 10:27 AM Shafeek Ashraf  
> wrote:
>
>> Hi,
>> You can use services like Pitunnel for accesing and modifying beaglebone 
>> through remote acess
>>
>> On Thu, 15 Oct 2020, 09:58 Niresh,  wrote:
>>
>>> Hi,
>>> Could you please help me the best utility to implement this and 
>>> procedure to do so, and also how to use a static IP address in 
>>> beagle-bone-black?
>>>
>>> Thanks and regards,
>>> NK
>>>
>>> On Thu, Oct 15, 2020 at 9:24 AM Atique Rehman  
>>> wrote:
>>>
 You need some sort of client application running on the beaglebone 
 which can receive new apps from server. 
 To access to beagle-bone remotely you should have its static IP address.

 On Thursday, October 15, 2020 at 2:38:23 PM UTC+11 Niresh wrote:

> Hi,
> I am using Beagle Bone Black with Debian image and kernel version 
> 4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black 
> remotely. Let me explain the requirement, I have an application running 
> on 
> BBB and connected to AWS cloud server through web socket. Now, just in 
> case 
> want to upgrade the application remotely from cloud server, how do I do 
> that?
>
> Thanks and regards,
> NK
>
 -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "BeagleBoard" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 beagleboard...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/beagleboard/a5da3147-9939-448a-b89e-8e1f32bfed18n%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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/CAF7-PaSkswyoUsWWpfHm%3DezHURqLT1kEsLdrihmZ12y-EDVPVg%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CANSAWx-gohG-CEGmoC7gWcm5qevBdZ3NWRwKRHtnEzCdayZ7uQ%40mail.gmail.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/b2f4cdc5-7053-4c58-96bd-154cc3b5c418n%40googlegroups.com.

Re: [beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Niresh]

Hi,
I googled and understand pitunnel is for raspberry pi, what is the similar
thing for beagle bone. Please share a good link to understand the process
in a better way.
Do I need to register on a server for remote access?
How do I differentiate multiple beagle-bones for remote access?
What is the limitation on the number of beagle-bones?

Regards,
NK

On Thu, Oct 15, 2020 at 10:27 AM Shafeek Ashraf 
wrote:

> Hi,
> You can use services like Pitunnel for accesing and modifying beaglebone
> through remote acess
>
> On Thu, 15 Oct 2020, 09:58 Niresh,  wrote:
>
>> Hi,
>> Could you please help me the best utility to implement this and procedure
>> to do so, and also how to use a static IP address in beagle-bone-black?
>>
>> Thanks and regards,
>> NK
>>
>> On Thu, Oct 15, 2020 at 9:24 AM Atique Rehman 
>> wrote:
>>
>>> You need some sort of client application running on the beaglebone which
>>> can receive new apps from server.
>>> To access to beagle-bone remotely you should have its static IP address.
>>>
>>> On Thursday, October 15, 2020 at 2:38:23 PM UTC+11 Niresh wrote:
>>>
 Hi,
 I am using Beagle Bone Black with Debian image and kernel version
 4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black
 remotely. Let me explain the requirement, I have an application running on
 BBB and connected to AWS cloud server through web socket. Now, just in case
 want to upgrade the application remotely from cloud server, how do I do
 that?

 Thanks and regards,
 NK

>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/a5da3147-9939-448a-b89e-8e1f32bfed18n%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/CAF7-PaSkswyoUsWWpfHm%3DezHURqLT1kEsLdrihmZ12y-EDVPVg%40mail.gmail.com
>> 
>> .
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CANSAWx-gohG-CEGmoC7gWcm5qevBdZ3NWRwKRHtnEzCdayZ7uQ%40mail.gmail.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/CAF7-PaQU62H5jM-N_mms61-X5YVhvv4y-Uwa7jWn%3DRmdhkJ7Pg%40mail.gmail.com.

Re: [beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Shafeek Ashraf]

Hi,
You can use services like Pitunnel for accesing and modifying beaglebone
through remote acess

On Thu, 15 Oct 2020, 09:58 Niresh,  wrote:

> Hi,
> Could you please help me the best utility to implement this and procedure
> to do so, and also how to use a static IP address in beagle-bone-black?
>
> Thanks and regards,
> NK
>
> On Thu, Oct 15, 2020 at 9:24 AM Atique Rehman 
> wrote:
>
>> You need some sort of client application running on the beaglebone which
>> can receive new apps from server.
>> To access to beagle-bone remotely you should have its static IP address.
>>
>> On Thursday, October 15, 2020 at 2:38:23 PM UTC+11 Niresh wrote:
>>
>>> Hi,
>>> I am using Beagle Bone Black with Debian image and kernel version
>>> 4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black
>>> remotely. Let me explain the requirement, I have an application running on
>>> BBB and connected to AWS cloud server through web socket. Now, just in case
>>> want to upgrade the application remotely from cloud server, how do I do
>>> that?
>>>
>>> Thanks and regards,
>>> NK
>>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/a5da3147-9939-448a-b89e-8e1f32bfed18n%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/CAF7-PaSkswyoUsWWpfHm%3DezHURqLT1kEsLdrihmZ12y-EDVPVg%40mail.gmail.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/CANSAWx-gohG-CEGmoC7gWcm5qevBdZ3NWRwKRHtnEzCdayZ7uQ%40mail.gmail.com.

Re: [beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Niresh]

Hi,
Could you please help me the best utility to implement this and procedure
to do so, and also how to use a static IP address in beagle-bone-black?

Thanks and regards,
NK

On Thu, Oct 15, 2020 at 9:24 AM Atique Rehman  wrote:

> You need some sort of client application running on the beaglebone which
> can receive new apps from server.
> To access to beagle-bone remotely you should have its static IP address.
>
> On Thursday, October 15, 2020 at 2:38:23 PM UTC+11 Niresh wrote:
>
>> Hi,
>> I am using Beagle Bone Black with Debian image and kernel version
>> 4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black
>> remotely. Let me explain the requirement, I have an application running on
>> BBB and connected to AWS cloud server through web socket. Now, just in case
>> want to upgrade the application remotely from cloud server, how do I do
>> that?
>>
>> Thanks and regards,
>> NK
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/a5da3147-9939-448a-b89e-8e1f32bfed18n%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/CAF7-PaSkswyoUsWWpfHm%3DezHURqLT1kEsLdrihmZ12y-EDVPVg%40mail.gmail.com.

[beagleboard] Re: Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Atique Rehman]

You need some sort of client application running on the beaglebone which 
can receive new apps from server. 
To access to beagle-bone remotely you should have its static IP address.

On Thursday, October 15, 2020 at 2:38:23 PM UTC+11 Niresh wrote:

> Hi,
> I am using Beagle Bone Black with Debian image and kernel version 
> 4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black 
> remotely. Let me explain the requirement, I have an application running on 
> BBB and connected to AWS cloud server through web socket. Now, just in case 
> want to upgrade the application remotely from cloud server, how do I do 
> that?
>
> Thanks and regards,
> NK
>

-- 
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/a5da3147-9939-448a-b89e-8e1f32bfed18n%40googlegroups.com.

[beagleboard] Remote access for the beagle bone black (BBB) to modify /upgrade file from cloud server

[Niresh]

Hi,
I am using Beagle Bone Black with Debian image and kernel version 
4.4.30-ti-r64. Please anyone suggest how to access the beagle bone black 
remotely. Let me explain the requirement, I have an application running on 
BBB and connected to AWS cloud server through web socket. Now, just in case 
want to upgrade the application remotely from cloud server, how do I do 
that?

Thanks and regards,
NK

-- 
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/70bc9759-86fb-4284-8de9-6a73657bea38n%40googlegroups.com.

[beagleboard] GPIO Device tree BeagleBone AI, 4.19 Kernel image

[Douglas Conover]

Hi all,

In the last few days, I've been working on updating my device tree files to 
be compatible with the 4.19 kernel image:

https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-
iot/am57xx-debian-10.5-iot-armhf-2020-09-07-4gb.img.xz 

using the device tree files at:

https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-
overlays/src/arm/overlays



I haven't been able to figure out how to properly set the default values 
(on or off) of my gpios on bootup. in *bbai-bone-buses.dtsi*, I found the 
group "*leds*" and thought I could configure these pins in a similar 
fashion to the older *am5729-beagleboneai-roboticscape.dts.* However, I've 
only been able to set the pins as gpios, and not choose whether they output 
on or off at boot. Here is my dts:



















*/dts-v1/;/plugin/;/** Helper to show loaded overlays under: 
/proc/device-tree/chosen/overlays/*/&{/chosen} {overlays {
VENTION-GPIO = __TIMESTAMP__;};};&ocp {P8_11_pinmux { 
pinctrl-0 = <&P8_11_gpio_pin>; }; /*  */P8_13_pinmux { pinctrl-0 = 
<&P8_13_gpio_pin>; }; /*  */*




















*P8_14_pinmux { pinctrl-0 = <&P8_14_gpio_pin>; }; /*  */
P8_15_pinmux { pinctrl-0 = <&P8_15_gpio_pin>; }; /*  */P9_15_pinmux { 
pinctrl-0 = <&P9_15_gpio_pin>; }; /*  */P8_16_pinmux { pinctrl-0 = 
<&P8_16_gpio_pin>; }; /*  */P8_17_pinmux { pinctrl-0 = 
<&P8_17_gpio_pin>; }; /*  */P8_19_pinmux { pinctrl-0 = 
<&P8_19_gpio_pin>; }; /*  */P9_12_pinmux { pinctrl-0 = 
<&P9_12_gpio_pin>; }; /*  */P9_14_pinmux { pinctrl-0 = 
<&P9_14_gpio_pin>; }; /*  */};&leds{pinctrl-names = "default";   
 compatible = "gpio-leds";led_P8_11{status="enabled" 
;default-state="on";};};*

I would eventually like to configure the default state of all of these 
pins.This dts compiles, but will brick my device. Any ideas about how I can 
set the boot states with this framework?

Thanks,

Doug

-- 
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/b246dba0-623b-4bfb-a259-b98403c9a0ban%40googlegroups.com.

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

[jonnymo]

For the resolv.conf permission issue, you either need to login as root,
"sudo su -" or as I do just make a copy of the "/etc/resolv.conf" in a
local folder, edit it, and then copy over as such:

 sudo cp resolv.conf /etc/resolv.conf

Cheers,

Jon

On Wed, Oct 14, 2020 at 8:16 AM Dennis Lee Bieber 
wrote:

> On Wed, 14 Oct 2020 01:01:42 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user John Dyson
>  wrote:
>
> >Hi,
> >
> >Following these instructions:
> >
> >I have connected the USB Cable and nothing else from the beaglebone to
> the
> >PC. All of thwe windows 64 bit drivers have been successfully installed.
> >
>
> Just to follow along on this part, I've pulled the CAT-5 from my
> BBB.
>
> debian@beaglebone:~$ ifconfig
> eth0: flags=-28669  mtu 1500
> ether d0:39:72:18:3e:e5  txqueuelen 1000  (Ethernet)
> RX packets 164  bytes 13701 (13.3 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 95  bytes 15719 (15.3 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 153  bytes 11380 (11.1 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 153  bytes 11380 (11.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> usb0: flags=4163  mtu 1500
> inet 192.168.7.2  netmask 255.255.255.0  broadcast 192.168.7.255
> inet6 fe80::d239:72ff:fe18:3ee7  prefixlen 64  scopeid 0x20
> ether d0:39:72:18:3e:e7  txqueuelen 1000  (Ethernet)
> RX packets 193  bytes 35656 (34.8 KiB)
> RX errors 0  dropped 4  overruns 0  frame 0
> TX packets 84  bytes 18613 (18.1 KiB)
> 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 d0:39:72:18:3e:eb  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
>
> No IP address on eth0, expected address on usb0.
>
> >
> >The initial ping to the gateway 192.168.7.1 fails when I SSH into the
> >beaglebone (Figure 3)
> >
> WHY a screen grab? You are using a text console, aren't you -- just
> select/copy/paste the TEXT...
>
> debian@beaglebone:~$ route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 192.168.6.0 0.0.0.0 255.255.255.0   U 0  00
> usb1
> 192.168.7.0 0.0.0.0 255.255.255.0   U 0  00
> usb0
> debian@beaglebone:~$ ping 192.168.7.1
> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
> 64 bytes from 192.168.7.1: icmp_seq=1 ttl=128 time=0.368 ms
> 64 bytes from 192.168.7.1: icmp_seq=2 ttl=128 time=0.475 ms
> 64 bytes from 192.168.7.1: icmp_seq=3 ttl=128 time=0.501 ms
> 64 bytes from 192.168.7.1: icmp_seq=4 ttl=128 time=0.491 ms
> ^C
> --- 192.168.7.1 ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 9ms
> rtt min/avg/max/mdev = 0.368/0.458/0.501/0.059 ms
> debian@beaglebone:~$
>
> Pinging the host computer works, even without a gateway setting
> (since
> 192.168.7.1 and 192.168.7.2 are the same network, and likely it is presumed
> that all hosts on that network can be reached using the adapter [usb0] that
> is itself on the network).
>
>
>
> If that simple step is failing, you might have to check whatever
> firewall you have running on Windows.
>
>
>
> NEXT action I tried was opening the Windows "Network Connections"
> control panel. BRIDGING "Ethernet" (remember -- My systems are normally
> cable connection) and "Ethernet 2" (the RNDIS gadget) is not the correct
> action, as it kills the Internet access on "Ethernet" (and there is an
> advisory that one cannot bridge an ICS adapter).
>
> So... remove bridge, open "Ethernet" and enable Sharing, specifying
> "Ethernet 2" as the private network side.
>
> With ICS active, Windows assigned 192.168.137.1 to the RNDIS
> adapter! I
> just edited that to use a manual IP address 192.168.7.1, length 24, and
> gateway is set to my router (192.168.1.1). (I used the "WiFi" section as
> that was the control panel type I had open)
> https://pureinfotech.com/set-static-ip-address-windows-10/
>
> SSH back into the BBB at 192.168.7.2.
>
> Lastly, I added a gateway on the BBB...
>
> debian@beaglebone:~$ route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 192.168.6.0 0.0.0.0 255.255.255.0   U 0  00
> usb1
> 192.168.7.0 0.0.0.0 255.255.255.0  

[beagleboard] Re: Beaglebone black connect to Web

[Dennis Lee Bieber]

On Wed, 14 Oct 2020 01:01:42 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user John Dyson
 wrote:

>Hi,
>
>Following these instructions:
>
>I have connected the USB Cable and nothing else from the beaglebone to the 
>PC. All of thwe windows 64 bit drivers have been successfully installed.
>

Just to follow along on this part, I've pulled the CAT-5 from my BBB.

debian@beaglebone:~$ ifconfig
eth0: flags=-28669  mtu 1500
ether d0:39:72:18:3e:e5  txqueuelen 1000  (Ethernet)
RX packets 164  bytes 13701 (13.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 95  bytes 15719 (15.3 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 153  bytes 11380 (11.1 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 153  bytes 11380 (11.1 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163  mtu 1500
inet 192.168.7.2  netmask 255.255.255.0  broadcast 192.168.7.255
inet6 fe80::d239:72ff:fe18:3ee7  prefixlen 64  scopeid 0x20
ether d0:39:72:18:3e:e7  txqueuelen 1000  (Ethernet)
RX packets 193  bytes 35656 (34.8 KiB)
RX errors 0  dropped 4  overruns 0  frame 0
TX packets 84  bytes 18613 (18.1 KiB)
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 d0:39:72:18:3e:eb  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

No IP address on eth0, expected address on usb0.

>
>The initial ping to the gateway 192.168.7.1 fails when I SSH into the 
>beaglebone (Figure 3)
>
WHY a screen grab? You are using a text console, aren't you -- just
select/copy/paste the TEXT...

debian@beaglebone:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.6.0 0.0.0.0 255.255.255.0   U 0  00
usb1
192.168.7.0 0.0.0.0 255.255.255.0   U 0  00
usb0
debian@beaglebone:~$ ping 192.168.7.1
PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
64 bytes from 192.168.7.1: icmp_seq=1 ttl=128 time=0.368 ms
64 bytes from 192.168.7.1: icmp_seq=2 ttl=128 time=0.475 ms
64 bytes from 192.168.7.1: icmp_seq=3 ttl=128 time=0.501 ms
64 bytes from 192.168.7.1: icmp_seq=4 ttl=128 time=0.491 ms
^C
--- 192.168.7.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 9ms
rtt min/avg/max/mdev = 0.368/0.458/0.501/0.059 ms
debian@beaglebone:~$

Pinging the host computer works, even without a gateway setting (since
192.168.7.1 and 192.168.7.2 are the same network, and likely it is presumed
that all hosts on that network can be reached using the adapter [usb0] that
is itself on the network).



If that simple step is failing, you might have to check whatever
firewall you have running on Windows.



NEXT action I tried was opening the Windows "Network Connections"
control panel. BRIDGING "Ethernet" (remember -- My systems are normally
cable connection) and "Ethernet 2" (the RNDIS gadget) is not the correct
action, as it kills the Internet access on "Ethernet" (and there is an
advisory that one cannot bridge an ICS adapter).

So... remove bridge, open "Ethernet" and enable Sharing, specifying
"Ethernet 2" as the private network side.

With ICS active, Windows assigned 192.168.137.1 to the RNDIS adapter! I
just edited that to use a manual IP address 192.168.7.1, length 24, and
gateway is set to my router (192.168.1.1). (I used the "WiFi" section as
that was the control panel type I had open)
https://pureinfotech.com/set-static-ip-address-windows-10/ 

SSH back into the BBB at 192.168.7.2.

Lastly, I added a gateway on the BBB...

debian@beaglebone:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
192.168.6.0 0.0.0.0 255.255.255.0   U 0  00
usb1
192.168.7.0 0.0.0.0 255.255.255.0   U 0  00
usb0
debian@beaglebone:~$ sudo route add default gw 192.168.7.1 usb0
[sudo] password for debian:
debian@beaglebone:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
default 192.168.7.1 0.0.0.0 UG0  00
usb0
192.168.6.0 0.0.0.0 255.255.255.0   U 0  00
usb1
192.168.7.0 0.0.0.0 255.255.255.0   U 0  00
usb0
debian@beaglebone:~$ ping 192.168.7.1
PING 19

[beagleboard] Re: Configure CAN BeagleBone AI, Kernel v4.19

[Douglas Conover]

Thanks, that did the trick. "*ifconfig -a*" showed the can0 interface and 
the following two lines brought it up:

  
*sudo ip link set can0 type can bitrate 125000 *
*  sudo ip link set up can0*

On Wednesday, October 14, 2020 at 7:07:46 AM UTC-4 jose...@gmail.com wrote:

> CAN interfaces are down by default. If you type "*ifconfig -a*" you 
> should see them...
>
> A quarta-feira, 14 de outubro de 2020 à(s) 11:45:01 UTC+1, Douglas Conover 
> escreveu:
>
>>
>> Hi all, I have been working on updating some of my device tree files to 
>> the newer image found at:
>>
>>
>> https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-iot/am57xx-debian-10.5-iot-armhf-2020-09-07-4gb.img.xz
>>  
>>
>> using the device tree files at:
>>
>>
>> https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays
>>
>> I would like to use pins P9.26 and P9.24 for can bus communication. In 
>> the previous version of the image (the latest IOT image found at 
>> https://beagleboard.org/latest-images), I was able to configure them 
>> using a modified version of a sample dts. Looking at the 4.19.x-ti-overlays 
>> branch of the device tree overlay repo, I found the BONE-CAN1.dts file, 
>> which seemed to do almost exactly the same thing. I built the dtbo and 
>> copied it to /boot/dtbs. This is my uEnv.txt:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *uname_r=4.19.94-ti-r50#uuid=#dtb=###U-Boot Overlays##Documentation: 
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
>> ###Master
>>  
>> Enableenable_uboot_overlays=1##Overide capes with 
>> eepromuboot_overlay_addr0=/boot/dtbs/BONE-CAN1.dtbo#uboot_overlay_addr2=.dtbo#uboot_overlay_addr3=.dtbo##Additional
>>  
>> custom 
>> capes#uboot_overlay_addr4=.dtbo#uboot_overlay_addr5=.dtbo#uboot_overlay_addr6=.dtbo#uboot_overlay_addr7=.dtbo##Custom
>>  
>> Cape#dtb_overlay=.dtbo##Debug: disable uboot autoload of 
>> Cape#disable_uboot_overlay_addr0=1#disable_uboot_overlay_addr1=1#disable_uboot_overlay_addr2=1#disable_uboot_overlay_addr3=1##U-Boot
>>  
>> fdt tweaks... (6 = 384KB)#uboot_fdt_buffer=0x6###U-Boot 
>> Overlays###cmdline=coherent_pool=1M net.ifnames=0 
>> rng_core.default_quality=100 quiet#In the event of edid real failures, 
>> uncomment this next line:#cmdline=coherent_pool=1M net.ifnames=0 
>> rng_core.default_quality=100 quiet video=HDMI-A-1:1024x768@60e##enable x15: 
>> eMMC Flasher:##make sure, these tools are installed: dosfstools rsync*
>>
>> On reboot, the show-pins utility (https://github.com/mvduin/bbb-pin-utils) 
>> shows that the pins are in the correct mux modes:
>>
>>
>>
>>
>>
>> *debian@beaglebone:/var/lib/cloud9$ show-pins | grep canCaution: Uses 
>> peripheral names from >. See 
>> README there for details.P9.26b81 
>> fast 15 unused   ocp@4400/P9_26_pinmux 
>> (pinmux_P9_26_can_pin)P9.26a   162 fast 
>> up   2 can 1 tx ocp@4400/P9_26_pinmux 
>> (pinmux_P9_26_can_pin)P9.24163 fast rx  
>> up   2 can 1 rx ocp@4400/P9_24_pinmux (pinmux_P9_24_can_pin)*
>>  
>> but ifconfig does not reveal a can interface:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *SoftAp0: flags=4163  mtu 1500
>> inet 192.168.8.1  netmask 255.255.255.0  broadcast 192.168.8.255
>> inet6 fe80::200:ff:fe00:0  prefixlen 64  scopeid 0x20ether 
>> 00:00:00:00:00:00  txqueuelen 1000  (Ethernet)RX packets 0  bytes 0 
>> (0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX 
>> packets 35  bytes 6868 (6.7 KiB)TX errors 0  dropped 0 overruns 0  
>> carrier 0  collisions 0eth0: 
>> flags=-28605  mtu 1500inet 
>> 169.254.25.128  netmask 255.255.0.0  broadcast 169.254.255.255inet6 
>> fe80::2aec:9aff:feeb:54d6  prefixlen 64  scopeid 0x20ether 
>> 28:ec:9a:eb:54:d6  txqueuelen 1000  (Ethernet)RX packets 72  bytes 
>> 16296 (15.9 KiB)RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 114  bytes 31416 (30.6 KiB)TX errors 0  dropped 0 
>> overruns 0  carrier 0  collisions 0device interrupt 128lo: 
>> flags=73  mtu 65536inet 127.0.0.1  netmask 
>> 255.0.0.0inet6 ::1  prefixlen 128  scopeid 0x10loop  
>> txqueuelen 1000  (Local Loopback)RX packets 1040  bytes 70800 (69.1 
>> KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 
>> 1040  bytes 70800 (69.1 KiB)TX errors 0  dropped 0 overruns 0  
>> carrier 0  collisions 0usb0: flags=4163  
>> mtu 1500inet

[beagleboard] Re: Configure CAN BeagleBone AI, Kernel v4.19

[jose...@gmail.com]

CAN interfaces are down by default. If you type "*ifconfig -a*" you should 
see them...

A quarta-feira, 14 de outubro de 2020 à(s) 11:45:01 UTC+1, Douglas Conover 
escreveu:

>
> Hi all, I have been working on updating some of my device tree files to 
> the newer image found at:
>
>
> https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-iot/am57xx-debian-10.5-iot-armhf-2020-09-07-4gb.img.xz
>  
>
> using the device tree files at:
>
>
> https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays
>
> I would like to use pins P9.26 and P9.24 for can bus communication. In the 
> previous version of the image (the latest IOT image found at 
> https://beagleboard.org/latest-images), I was able to configure them 
> using a modified version of a sample dts. Looking at the 4.19.x-ti-overlays 
> branch of the device tree overlay repo, I found the BONE-CAN1.dts file, 
> which seemed to do almost exactly the same thing. I built the dtbo and 
> copied it to /boot/dtbs. This is my uEnv.txt:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *uname_r=4.19.94-ti-r50#uuid=#dtb=###U-Boot Overlays##Documentation: 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
> ###Master
>  
> Enableenable_uboot_overlays=1##Overide capes with 
> eepromuboot_overlay_addr0=/boot/dtbs/BONE-CAN1.dtbo#uboot_overlay_addr2=.dtbo#uboot_overlay_addr3=.dtbo##Additional
>  
> custom 
> capes#uboot_overlay_addr4=.dtbo#uboot_overlay_addr5=.dtbo#uboot_overlay_addr6=.dtbo#uboot_overlay_addr7=.dtbo##Custom
>  
> Cape#dtb_overlay=.dtbo##Debug: disable uboot autoload of 
> Cape#disable_uboot_overlay_addr0=1#disable_uboot_overlay_addr1=1#disable_uboot_overlay_addr2=1#disable_uboot_overlay_addr3=1##U-Boot
>  
> fdt tweaks... (6 = 384KB)#uboot_fdt_buffer=0x6###U-Boot 
> Overlays###cmdline=coherent_pool=1M net.ifnames=0 
> rng_core.default_quality=100 quiet#In the event of edid real failures, 
> uncomment this next line:#cmdline=coherent_pool=1M net.ifnames=0 
> rng_core.default_quality=100 quiet video=HDMI-A-1:1024x768@60e##enable x15: 
> eMMC Flasher:##make sure, these tools are installed: dosfstools rsync*
>
> On reboot, the show-pins utility (https://github.com/mvduin/bbb-pin-utils) 
> shows that the pins are in the correct mux modes:
>
>
>
>
>
> *debian@beaglebone:/var/lib/cloud9$ show-pins | grep canCaution: Uses 
> peripheral names from >. See 
> README there for details.P9.26b81 
> fast 15 unused   ocp@4400/P9_26_pinmux 
> (pinmux_P9_26_can_pin)P9.26a   162 fast 
> up   2 can 1 tx ocp@4400/P9_26_pinmux 
> (pinmux_P9_26_can_pin)P9.24163 fast rx  
> up   2 can 1 rx ocp@4400/P9_24_pinmux (pinmux_P9_24_can_pin)*
>  
> but ifconfig does not reveal a can interface:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *SoftAp0: flags=4163  mtu 1500inet 
> 192.168.8.1  netmask 255.255.255.0  broadcast 192.168.8.255inet6 
> fe80::200:ff:fe00:0  prefixlen 64  scopeid 0x20ether 
> 00:00:00:00:00:00  txqueuelen 1000  (Ethernet)RX packets 0  bytes 0 
> (0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX 
> packets 35  bytes 6868 (6.7 KiB)TX errors 0  dropped 0 overruns 0  
> carrier 0  collisions 0eth0: 
> flags=-28605  mtu 1500inet 
> 169.254.25.128  netmask 255.255.0.0  broadcast 169.254.255.255inet6 
> fe80::2aec:9aff:feeb:54d6  prefixlen 64  scopeid 0x20ether 
> 28:ec:9a:eb:54:d6  txqueuelen 1000  (Ethernet)RX packets 72  bytes 
> 16296 (15.9 KiB)RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 114  bytes 31416 (30.6 KiB)TX errors 0  dropped 0 
> overruns 0  carrier 0  collisions 0device interrupt 128lo: 
> flags=73  mtu 65536inet 127.0.0.1  netmask 
> 255.0.0.0inet6 ::1  prefixlen 128  scopeid 0x10loop  
> txqueuelen 1000  (Local Loopback)RX packets 1040  bytes 70800 (69.1 
> KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 
> 1040  bytes 70800 (69.1 KiB)TX errors 0  dropped 0 overruns 0  
> carrier 0  collisions 0usb0: flags=4163  
> mtu 1500inet 192.168.7.2  netmask 255.255.255.0  broadcast 
> 192.168.7.255inet6 fe80::1eba:8cff:fea2:ed6b  prefixlen 64  scopeid 
> 0x20ether 1c:ba:8c:a2:ed:6b  txqueuelen 1000  
> (Ethernet)RX packets 418  bytes 63986 (62.4 KiB)RX errors 
> 0  dropped 0  overruns 0  frame 0TX packets 355  bytes 84899 (82.9 
> KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0usb1: 
> flags=4163  mtu 1500inet 

[beagleboard] Re: Beaglebone black connect to Web

[John Dyson]

Hi,

Following these instructions:

I have connected the USB Cable and nothing else from the beaglebone to the 
PC. All of thwe windows 64 bit drivers have been successfully installed.

https://www.digikey.com/en/maker/blogs/how-to-connect-a-beaglebone-black-to-the-internet-using-usb

The initial ping to the gateway 192.168.7.1 fails when I SSH into the 
beaglebone (Figure 3)

Before this I have configured the "created" network adapter when I connect 
the USB cable named as Ethernet 3 Uidentified network "Remote NDIS 
Compatible Device" as 

Internet Protocol Version 4 (TCP/IPv4) Properties

IP address 192.168.7.1
Subnet Mask: 255.255.255.0
Preferred DNS server: 8.8.8.8
Alternate DNS Server: 8.8.4.4

I've setup the Wifi Network Adapter from the PC as shared with "Ethernet 3" 
detailed above.

tried this command "sudo /sbin/route add default gw 192.168.7.1"

The ping still doesn't work.

attempting this even which sudo "echo "nameserver 8.8.8.8" >> 
/etc/resolv.conf  "

Gives permission denied however this is a step later on the process as the 
initial ping should work.

Thanks in advance for all your help :-)

On Monday, 12 October 2020 at 18:23:34 UTC+1 Dennis Bieber wrote:

> On Sun, 11 Oct 2020 02:46:28 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user John Dyson
>  wrote:
>
> >Hi,
> >
> >I think the problem is with the network adapter not working correctly in 
> >windows. The network adapter shown is "Remote NDIS compatible Device".
> >
>
> That adapter is the norm for the BBB USB "ethernet" emulation.
>
> How are you powering the BBB? Using USB from the host computer? If so,
> you also have the USB ethernet gadget active.
>
> In either case, you need the BBB configured to /route/ packets to the
> next node in your network. Normally that would be an internet router --
> even though I've powered this BBB using the USB (and hence have the
> 192.168.7.x IPs active) it is also connected to my router over a CAT-5
> cable. Note that the router issued the BBB 192.168.1.69, and also that the
> default destination for packets is the router (ATT U-Verse service).
>
> debian@beaglebone:~$ ifconfig
> eth0: flags=-28605 mtu 1500
> inet 192.168.1.69 netmask 255.255.255.0 broadcast 192.168.1.255
> inet6 2600:1700:e630:890:d239:72ff:fe18:3ee5 prefixlen 64 scopeid
> 0x0
> inet6 fe80::d239:72ff:fe18:3ee5 prefixlen 64 scopeid 0x20
> inet6 2600:1700:e630:890::31 prefixlen 64 scopeid 0x0
> ether d0:39:72:18:3e:e5 txqueuelen 1000 (Ethernet)
> RX packets 111 bytes 13355 (13.0 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 139 bytes 23120 (22.5 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 81 bytes 6556 (6.4 KiB)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 81 bytes 6556 (6.4 KiB)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>
> usb0: flags=4163 mtu 1500
> inet 192.168.7.2 netmask 255.255.255.0 broadcast 192.168.7.255
> inet6 fe80::d239:72ff:fe18:3ee7 prefixlen 64 scopeid 0x20
> ether d0:39:72:18:3e:e7 txqueuelen 1000 (Ethernet)
> RX packets 118 bytes 27503 (26.8 KiB)
> RX errors 0 dropped 4 overruns 0 frame 0
> TX packets 46 bytes 10444 (10.1 KiB)
> 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 d0:39:72:18:3e:eb 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:~$ route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> default dsldevice.attlo 0.0.0.0 UG 0 0 0
> eth0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> dsldevice.attlo 0.0.0.0 255.255.255.255 UH 0 0 0
> eth0
> 192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0
> usb1
> 192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0
> usb0
>
> If you are connecting to an ethernet port on your computer, your host
> computer has to also be configured to act as a router -- that is, it has to
> accept packets from the BBB, and pass them on to whatever node the host has
> defined as a gateway.
>
> THIS ACTION is not automatic for Windows! In some versions it is known
> as Internet Connection Sharing (ICS), and requires configuration to "link"
> the (to-be-shared) network with the devices connected to the host computer.
> cf:
>
> https://answers.microsoft.com/en-us/windows/forum/windows_10-networking-winpc/internet-connection-sharing-in-windows-10/f6dcac4b-5203-4c98-8cf2-dcac86d98fb9
>
> I have never done this, and have no desire to experiment with it
>
> debian@beaglebone:~$ traceroute 8.8.8.8
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> 1 dsldevice.attlocal.net (192.168.1.254) 0.741 ms 0.966 ms 0.868 ms
> 2 76-255-152-1.lightspee

[beagleboard] Re: Make Micro SD card bootable in windows

[John Dyson]

Hi,

I have managed to resolve this using virtualbox and GPartedin ubuntu.

thanks

On Monday, 12 October 2020 at 18:26:10 UTC+1 Dennis Bieber wrote:

> On Sun, 11 Oct 2020 02:48:35 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user John Dyson
>  wrote:
>
> >Is there a tool in windows that reliably marks the SD card as bootable to 
> >change the MLO? Or would it better to do it from virtual box ubuntu?
>
> There is, to my knowledge, nothing in Windows that understands EXTn
> file systems/partitions.
>
>
> -- 
> 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/ac5e61a0-5d62-43c0-9765-64e38c3bf43bn%40googlegroups.com.

[beagleboard] Configure CAN BeagleBone AI, Kernel v4.19

[Douglas Conover]

Hi all, I have been working on updating some of my device tree files to the 
newer image found at:

https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-iot/am57xx-debian-10.5-iot-armhf-2020-09-07-4gb.img.xz
 

using the device tree files at:

https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays

I would like to use pins P9.26 and P9.24 for can bus communication. In the 
previous version of the image (the latest IOT image found at 
https://beagleboard.org/latest-images), I was able to configure them using 
a modified version of a sample dts. Looking at the 4.19.x-ti-overlays 
branch of the device tree overlay repo, I found the BONE-CAN1.dts file, 
which seemed to do almost exactly the same thing. I built the dtbo and 
copied it to /boot/dtbs. This is my uEnv.txt:








































*uname_r=4.19.94-ti-r50#uuid=#dtb=###U-Boot Overlays##Documentation: 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays###Master 
Enableenable_uboot_overlays=1##Overide capes with 
eepromuboot_overlay_addr0=/boot/dtbs/BONE-CAN1.dtbo#uboot_overlay_addr2=.dtbo#uboot_overlay_addr3=.dtbo##Additional
 
custom 
capes#uboot_overlay_addr4=.dtbo#uboot_overlay_addr5=.dtbo#uboot_overlay_addr6=.dtbo#uboot_overlay_addr7=.dtbo##Custom
 
Cape#dtb_overlay=.dtbo##Debug: disable uboot autoload of 
Cape#disable_uboot_overlay_addr0=1#disable_uboot_overlay_addr1=1#disable_uboot_overlay_addr2=1#disable_uboot_overlay_addr3=1##U-Boot
 
fdt tweaks... (6 = 384KB)#uboot_fdt_buffer=0x6###U-Boot 
Overlays###cmdline=coherent_pool=1M net.ifnames=0 
rng_core.default_quality=100 quiet#In the event of edid real failures, 
uncomment this next line:#cmdline=coherent_pool=1M net.ifnames=0 
rng_core.default_quality=100 quiet video=HDMI-A-1:1024x768@60e##enable x15: 
eMMC Flasher:##make sure, these tools are installed: dosfstools rsync*

On reboot, the show-pins utility (https://github.com/mvduin/bbb-pin-utils) 
shows that the pins are in the correct mux modes:





*debian@beaglebone:/var/lib/cloud9$ show-pins | grep canCaution: Uses 
peripheral names from . See README there for 
details.P9.26b81 fast 15 
unused   ocp@4400/P9_26_pinmux 
(pinmux_P9_26_can_pin)P9.26a   162 fast 
up   2 can 1 tx ocp@4400/P9_26_pinmux 
(pinmux_P9_26_can_pin)P9.24163 fast rx  
up   2 can 1 rx ocp@4400/P9_24_pinmux (pinmux_P9_24_can_pin)*
 
but ifconfig does not reveal a can interface:




















































*SoftAp0: flags=4163  mtu 1500inet 
192.168.8.1  netmask 255.255.255.0  broadcast 192.168.8.255inet6 
fe80::200:ff:fe00:0  prefixlen 64  scopeid 0x20ether 
00:00:00:00:00:00  txqueuelen 1000  (Ethernet)RX packets 0  bytes 0 
(0.0 B)RX errors 0  dropped 0  overruns 0  frame 0TX 
packets 35  bytes 6868 (6.7 KiB)TX errors 0  dropped 0 overruns 0  
carrier 0  collisions 0eth0: 
flags=-28605  mtu 1500inet 
169.254.25.128  netmask 255.255.0.0  broadcast 169.254.255.255inet6 
fe80::2aec:9aff:feeb:54d6  prefixlen 64  scopeid 0x20ether 
28:ec:9a:eb:54:d6  txqueuelen 1000  (Ethernet)RX packets 72  bytes 
16296 (15.9 KiB)RX errors 0  dropped 0  overruns 0  frame 0
TX packets 114  bytes 31416 (30.6 KiB)TX errors 0  dropped 0 
overruns 0  carrier 0  collisions 0device interrupt 128lo: 
flags=73  mtu 65536inet 127.0.0.1  netmask 
255.0.0.0inet6 ::1  prefixlen 128  scopeid 0x10loop  
txqueuelen 1000  (Local Loopback)RX packets 1040  bytes 70800 (69.1 
KiB)RX errors 0  dropped 0  overruns 0  frame 0TX packets 
1040  bytes 70800 (69.1 KiB)TX errors 0  dropped 0 overruns 0  
carrier 0  collisions 0usb0: flags=4163  
mtu 1500inet 192.168.7.2  netmask 255.255.255.0  broadcast 
192.168.7.255inet6 fe80::1eba:8cff:fea2:ed6b  prefixlen 64  scopeid 
0x20ether 1c:ba:8c:a2:ed:6b  txqueuelen 1000  
(Ethernet)RX packets 418  bytes 63986 (62.4 KiB)RX errors 
0  dropped 0  overruns 0  frame 0TX packets 355  bytes 84899 (82.9 
KiB)TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0usb1: 
flags=4163  mtu 1500inet 
192.168.6.2  netmask 255.255.255.0  broadcast 192.168.6.255inet6 
fe80::1eba:8cff:fea2:ed6d  prefixlen 64  scopeid 0x20ether 
1c:ba:8c:a2:ed:6d  txqueuelen 1000  (Ethernet)RX packets 45  bytes 
5611 (5.4 KiB)RX errors 0  dropped 0  overruns 0  frame 0TX 
packets 43  bytes 9016 (8.8 KiB)TX errors 0  dropped 0 overruns 0  
carrier 0  collisions 0wlan0: flags=-28669  
mtu 1500ether 80:91:33:4a:49:11  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)