date:20151207

Re: [beagleboard] Re: Internal error messages

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 5:48 PM,   wrote:
> Just in case anyone else runs into this, In my case I was getting this same
> messages and it turns out the system can't access the PMIC on the I2C bus.
>
> i2cdump -y -f 0 0x24
>
> This command shows that it is not communicating properly with the PMIC. Now
> to figure out why

Well, Is it marked with a "UU" then it's under the kernel control..

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

[beagleboard] Re: Internal error messages

2015-12-07 Thread tobster1911

Just in case anyone else runs into this, In my case I was getting this same 
messages and it turns out the system can't access the PMIC on the I2C bus. 

i2cdump -y -f 0 0x24

This command shows that it is not communicating properly with the PMIC. Now 
to figure out why



On Monday, December 15, 2014 at 7:04:48 PM UTC-7, Tommi wrote:
>
> Hey, 
>
> I am running the BBB with btsync and had it running for a while backuping 
> a larger chunk of data. I was away and when I came back I saw the following 
> messages. (line breaks a bit funny)
>
> What are they supposed to mean? The BBB is still running and did probably 
> not restart as the Putty session was still active when I saw the messages. 
>
> Thanks,
> Tommi
>
>
> root@beaglebone:/media/backup#
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.009526] Internal error: : 1028 [#1] SMP THUMB2
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.090532] Process irq/70-44e0b000 (pid: 20, stack limit = 
> 0xdf1862  
> 
> 40)
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.097521] Stack: (0xdf187f08 to 0xdf188000)
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.102154] 7f00:   c036192d df186000 df175360 
> 0 
>  
> 001 df175340 df008840
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.110788] 7f20: c082d37c c007367b  c007355d df071db0 
> 0 
>  
> 000 df175340 c00735dd
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.119416] 7f40:    c0045103 fef30040 
> 0 
>  
> 000 e020 df175340
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.128040] 7f60:   dead4ead   
> df187 
>  
> f74 df187f74 
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.136665] 7f80:  dead4ead   df187f90 
> df187 
>  
> f90  df071db0
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.145290] 7fa0: c0045099   c000c8fd  
> 0 
>  
> 000  
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.153916] 7fc0:      
> 0 
>  
> 000  
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.162545] 7fe0:     0013 
> 0 
>  
> 000 f3f38920 dd7f
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.197442] Code: 7849 fa01 f303 18d3 (8819) 6da0
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.229803] Internal error: Oops: 17 [#2] SMP THUMB2
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.309227] Process irq/70-44e0b000 (pid: 20, stack limit = 
> 0xdf1862  
> 
> 40)
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.316219] Stack: (0xdf187d30 to 0xdf188000)
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.320850] 7d20: c007355d 
> df0f6 
>  
> 4ec  c004323d
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.329475] 7d40:  d39fd39f  df0f6100  
> 0 
>  
> 00b c0831758 c00332e7
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.338101] 7d60: df187de3 0020 df186000 0001 c06e798c 
> d39fd 
>  
> 39f c029d1c5 c0861db4
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.346723] 7d80: df186000 c08ab8d8 df186000 000b c0831758 
> 0 
>  
> 002 df187de3 0020
>
> Message from syslogd@beaglebone at Dec 15 18:50:38 ...
>  kernel:[166531.355350] 7da0: 2193 c000f819 df186240 000b 6193 
> c0361

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 6:21 PM, Matt Maher Peterson
 wrote:
> Yes I could but I have a custom device tree written to work in the old world
> of 3.18.3 Is there a simple way to port that into 4.1.13.ti.r35 ?

Yeap, two options, install 4.1.13.ti.r35

Then use the dtb-rebuilder to build your matching *.dtb and boot with it:

https://github.com/RobertCNelson/dtb-rebuilder/tree/4.1-ti

or use the bb.org-overlays to build a custom *.dtbo overlay

https://github.com/beagleboard/bb.org-overlays

the biggest delta is gpio #'ing but the rest we can help with..

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

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread William Hermans

Anyway, if you apt-get install  linux-image, and it ends up not
working for you, simply change the uname-r variable in /boot/uEnv.txt ( to
point to your 3.8.x kernel ). And problem solved. After that, an apt-get
remove --purge  should get rid of all traces of the newer
4.1.x kernel. *IF* that's what you want.

On Mon, Dec 7, 2015 at 6:08 PM, William Hermans  wrote:

> There is no porting. You simply compile it with the proper device tree
> version. Which is different from the version used for 3.8.x.
>
>
> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/
>
> On Mon, Dec 7, 2015 at 5:21 PM, Matt Maher Peterson <
> matt.maherpeter...@hydro-care.com> wrote:
>
>> Yes I could but I have a custom device tree written to work in the old
>> world of 3.18.3 Is there a simple way to port that into 4.1.13.ti.r35 ?
>>
>> On Monday, December 7, 2015 at 4:19:49 PM UTC-8, RobertCNelson wrote:
>>>
>>> On Mon, Dec 7, 2015 at 6:15 PM, Matt Maher Peterson
>>>  wrote:
>>> > Thanks Robert.
>>> >
>>> > I found the file and everything seams legit.  The real issue I was
>>> trying to
>>> > solve was that when plugging this device in to the USB input I was not
>>> > getting the corresponding /dev/USBX's.
>>> >
>>> > After doing a
>>> > modprobe option
>>> > echo 1bc7 1201 > /sys/bus/usb-serial/drivers/option1/new_id
>>> >
>>> > I now see my /dev/USB1 thru /dev/USB6
>>> >
>>> > Why do I have to do these manual commands?  I guess I can scripts
>>> these on
>>> > boot but is there a better option.
>>>
>>> Well, you don't have to run 3.8.x:
>>>
>>>
>>> https://github.com/beagleboard/linux/blob/4.1.13-ti-r35/drivers/usb/serial/option.c#L266-L274
>>>
>>> Run "4.1.13-ti-r35" and it'll just work. ;)
>>>
>>> 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.
>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread William Hermans

There is no porting. You simply compile it with the proper device tree
version. Which is different from the version used for 3.8.x.

http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/

On Mon, Dec 7, 2015 at 5:21 PM, Matt Maher Peterson <
matt.maherpeter...@hydro-care.com> wrote:

> Yes I could but I have a custom device tree written to work in the old
> world of 3.18.3 Is there a simple way to port that into 4.1.13.ti.r35 ?
>
> On Monday, December 7, 2015 at 4:19:49 PM UTC-8, RobertCNelson wrote:
>>
>> On Mon, Dec 7, 2015 at 6:15 PM, Matt Maher Peterson
>>  wrote:
>> > Thanks Robert.
>> >
>> > I found the file and everything seams legit.  The real issue I was
>> trying to
>> > solve was that when plugging this device in to the USB input I was not
>> > getting the corresponding /dev/USBX's.
>> >
>> > After doing a
>> > modprobe option
>> > echo 1bc7 1201 > /sys/bus/usb-serial/drivers/option1/new_id
>> >
>> > I now see my /dev/USB1 thru /dev/USB6
>> >
>> > Why do I have to do these manual commands?  I guess I can scripts these
>> on
>> > boot but is there a better option.
>>
>> Well, you don't have to run 3.8.x:
>>
>>
>> https://github.com/beagleboard/linux/blob/4.1.13-ti-r35/drivers/usb/serial/option.c#L266-L274
>>
>> Run "4.1.13-ti-r35" and it'll just work. ;)
>>
>> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson

Yes I could but I have a custom device tree written to work in the old 
world of 3.18.3 Is there a simple way to port that into 4.1.13.ti.r35 ?

On Monday, December 7, 2015 at 4:19:49 PM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 7, 2015 at 6:15 PM, Matt Maher Peterson 
> > wrote: 
> > Thanks Robert. 
> > 
> > I found the file and everything seams legit.  The real issue I was 
> trying to 
> > solve was that when plugging this device in to the USB input I was not 
> > getting the corresponding /dev/USBX's. 
> > 
> > After doing a 
> > modprobe option 
> > echo 1bc7 1201 > /sys/bus/usb-serial/drivers/option1/new_id 
> > 
> > I now see my /dev/USB1 thru /dev/USB6 
> > 
> > Why do I have to do these manual commands?  I guess I can scripts these 
> on 
> > boot but is there a better option. 
>
> Well, you don't have to run 3.8.x: 
>
>
> https://github.com/beagleboard/linux/blob/4.1.13-ti-r35/drivers/usb/serial/option.c#L266-L274
>  
>
> Run "4.1.13-ti-r35" and it'll just work. ;) 
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 6:15 PM, Matt Maher Peterson
 wrote:
> Thanks Robert.
>
> I found the file and everything seams legit.  The real issue I was trying to
> solve was that when plugging this device in to the USB input I was not
> getting the corresponding /dev/USBX's.
>
> After doing a
> modprobe option
> echo 1bc7 1201 > /sys/bus/usb-serial/drivers/option1/new_id
>
> I now see my /dev/USB1 thru /dev/USB6
>
> Why do I have to do these manual commands?  I guess I can scripts these on
> boot but is there a better option.

Well, you don't have to run 3.8.x:

https://github.com/beagleboard/linux/blob/4.1.13-ti-r35/drivers/usb/serial/option.c#L266-L274

Run "4.1.13-ti-r35" and it'll just work. ;)

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

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson

Thanks Robert.

I found the file and everything seams legit.  The real issue I was trying 
to solve was that when plugging this device in to the USB input I was not 
getting the corresponding /dev/USBX's.

After doing a
modprobe option
echo 1bc7 1201 > /sys/bus/usb-serial/drivers/option1/new_id

I now see my /dev/USB1 thru /dev/USB6

Why do I have to do these manual commands?  I guess I can scripts these on 
boot but is there a better option.

Kind Regards,

Matt

On Monday, December 7, 2015 at 3:25:19 PM UTC-8, RobertCNelson wrote:
>
>
>
> On Mon, Dec 7, 2015 at 5:13 PM, Matt Maher Peterson  > wrote:
>
>> Thanks for the clarification Rpbert
>>
>>
>> What is the proper way to 'retrieve the appropriate kernel source 
>> code..." for 3.18.3-bone70?
>>
>
>
> git clone https://github.com/RobertCNelson/linux-stable-rcn-ee
> cd ./linux-stable-rcn-ee
> git checkout `uname -r` -b tmp
>
>
> or if you have an existing linus clone:
>
> git clone --reference  
> https://github.com/RobertCNelson/linux-stable-rcn-ee
> cd ./linux-stable-rcn-ee
> git checkout `uname -r` -b tmp
>
> uname -r = 3.18.3-bone70 or whatever version...
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 5:13 PM, Matt Maher Peterson 
wrote:

> Thanks for the clarification Rpbert
>
>
> What is the proper way to 'retrieve the appropriate kernel source code..."
> for 3.18.3-bone70?
>


git clone https://github.com/RobertCNelson/linux-stable-rcn-ee
cd ./linux-stable-rcn-ee
git checkout `uname -r` -b tmp


or if you have an existing linus clone:

git clone --reference 
https://github.com/RobertCNelson/linux-stable-rcn-ee
cd ./linux-stable-rcn-ee
git checkout `uname -r` -b tmp

uname -r = 3.18.3-bone70 or whatever version...

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

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson

Thanks for the clarification Rpbert


What is the proper way to 'retrieve the appropriate kernel source code..." 
for 3.18.3-bone70?



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

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson

Thanks for the clarification Rpbert


What is the proper way to 'retrieve the appropriate kernel source code..."
for 3.18.3-bone70?

Matt Maher Peterson
APANA
w: 360.746.2276x401
c: 360.393.5549

On Mon, Dec 7, 2015 at 3:10 PM, Robert Nelson 
wrote:

>
>
> On Mon, Dec 7, 2015 at 5:07 PM, Matt Maher Peterson <
> matt.maherpeter...@hydro-care.com> wrote:
>
>> Hi,
>>
>> Working with a Telit LE910 Cell Module and am trying to get a driver
>> working for usb connection.
>>
>> I am following the guide provided by Telit
>> 
>>
>> I have loaded the kernel headers and such so that I can see
>>
>> usr/src/linux-headers-3.8.13-bone70/drivers/usb/serial# ls
>> ezusb_convert.pl  Kconfig  Makefile  Makefile-keyspan_pda_f
>>
>>
>> Did so by doing
>> apt-cache search linux-headers-3.8.13-bone70
>> apt-get install linux-headers-3.8.13-bone70
>>
>>
>> My issues is the guide is asking my to looking in
>> /drivers/usb/serial/option.c
>>
>> I cannot find option.c ??
>>
>
>
> https://github.com/beagleboard/linux/blob/3.8/drivers/usb/serial/option.c
>
> It's not a header, so you won't find it in "linux-headers-3.8.13-bone70"
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.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/P4ZzSJ49grk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 5:07 PM, Matt Maher Peterson <
matt.maherpeter...@hydro-care.com> wrote:

> Hi,
>
> Working with a Telit LE910 Cell Module and am trying to get a driver
> working for usb connection.
>
> I am following the guide provided by Telit
> 
>
> I have loaded the kernel headers and such so that I can see
>
> usr/src/linux-headers-3.8.13-bone70/drivers/usb/serial# ls
> ezusb_convert.pl  Kconfig  Makefile  Makefile-keyspan_pda_f
>
>
> Did so by doing
> apt-cache search linux-headers-3.8.13-bone70
> apt-get install linux-headers-3.8.13-bone70
>
>
> My issues is the guide is asking my to looking in
> /drivers/usb/serial/option.c
>
> I cannot find option.c ??
>


https://github.com/beagleboard/linux/blob/3.8/drivers/usb/serial/option.c

It's not a header, so you won't find it in "linux-headers-3.8.13-bone70"

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

[beagleboard] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

2015-12-07 Thread Matt Maher Peterson

Hi,

Working with a Telit LE910 Cell Module and am trying to get a driver 
working for usb connection.

I am following the guide provided by Telit 


I have loaded the kernel headers and such so that I can see

usr/src/linux-headers-3.8.13-bone70/drivers/usb/serial# ls
ezusb_convert.pl  Kconfig  Makefile  Makefile-keyspan_pda_f


Did so by doing
apt-cache search linux-headers-3.8.13-bone70
apt-get install linux-headers-3.8.13-bone70


My issues is the guide is asking my to looking in 
/drivers/usb/serial/option.c

I cannot find option.c ??

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

Re: [beagleboard] who are user UID 110 and group GID 116?

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 3:28 PM, Robert Nelson 
wrote:

>
>
> On Mon, Dec 7, 2015 at 3:13 PM, Robert Nelson 
> wrote:
>
>>
>>
>> On Mon, Dec 7, 2015 at 2:47 PM, Maurice H.  wrote:
>>
>>> I must agree with you that `npm` is not the ideal packagemanager. ;-)
>>> There also seems to be `pip` installed for Python packages...
>>>
>>> Is there a remote possibility that those packages would ever be offered
>>> via `apt-get` ?
>>>
>>
>> i wish...  cloud9 ide has to be installed via npm, then they broke some
>> of the npm packaging, so you have install some npm dependices on target,
>> before you can run the "standalone" package...
>>
>>
>>
>>>
>>> Problem is that even as the root user some things (I forget which)
>>> didn't work off the bat because of those broken ownerships. I ended up
>>> chowning them to root:root (for files in `/etc/`) and debian:debian for
>>> files in `/home/debian`.
>>>
>>
>>
>> debian@beaglebone:~$ sudo cat .npmrc
>> cache = /root/.npm
>> group = 0
>> init-module = /root/.npm-init.js
>> tmp = /root/tmp
>> user = 0
>> userconfig = /root/.npmrc
>>
>> root@beaglebone:~# pwd
>> /root
>> root@beaglebone:~# ls -lha ./
>> total 28K
>> drwx--  5 root root 4.0K Dec  6 21:32 .
>> drwxr-xr-x 21 root root 4.0K Jan  1  2000 ..
>> -rw-r--r--  1 root root  570 Jan 31  2010 .bashrc
>> drwxr-xr-x  9 root root 4.0K Dec  6 21:23 .c9
>> drwxr-xr-x  3 root root 4.0K Dec  6 21:23 .cache
>> drwxr-xr-x  3 root root 4.0K Dec  6 21:24 .node-gyp
>> -rw-r--r--  1 root root  140 Nov 19  2007 .profile
>>
>> Well that's broken, so we can drop /home/debian/.npmrc
>>
>>
>> https://github.com/RobertCNelson/omap-image-builder/commit/5dfed9a2703c4013f9577b2e04f65e18568bd409
>>
>
>
> and the rest are mine..
>
> drwxr-xr-x  2 rootroot  4.0K Dec  6 21:04 bluetooth
> -rw-r--r--  1 polkitd bluetooth   40 Dec  6 21:06 dogtag
> -rw-r--r--  1 polkitd bluetooth   11 Dec  6 23:11 hostname
> -rw-r--r--  1 polkitd bluetooth  213 Dec  6 23:11 hosts
> -rw-r--r--  1 polkitd bluetooth  263 Dec  7 19:05 issue
> -rw-r--r--  1 polkitd bluetooth  175 Dec  6 21:29 issue.net
> -rw-r--r--  1 polkitd bluetooth   86 Dec  6 21:06 rcn-ee.conf
>
> those should all be root:root
>

This should fix the rest, please let me know if you find more:

https://github.com/RobertCNelson/omap-image-builder/commit/586c447e85ffbac762ce4d2b0b3b33434eaf4adf

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

Re: [beagleboard] who are user UID 110 and group GID 116?

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 3:13 PM, Robert Nelson 
wrote:

>
>
> On Mon, Dec 7, 2015 at 2:47 PM, Maurice H.  wrote:
>
>> I must agree with you that `npm` is not the ideal packagemanager. ;-)
>> There also seems to be `pip` installed for Python packages...
>>
>> Is there a remote possibility that those packages would ever be offered
>> via `apt-get` ?
>>
>
> i wish...  cloud9 ide has to be installed via npm, then they broke some of
> the npm packaging, so you have install some npm dependices on target,
> before you can run the "standalone" package...
>
>
>
>>
>> Problem is that even as the root user some things (I forget which) didn't
>> work off the bat because of those broken ownerships. I ended up chowning
>> them to root:root (for files in `/etc/`) and debian:debian for files in
>> `/home/debian`.
>>
>
>
> debian@beaglebone:~$ sudo cat .npmrc
> cache = /root/.npm
> group = 0
> init-module = /root/.npm-init.js
> tmp = /root/tmp
> user = 0
> userconfig = /root/.npmrc
>
> root@beaglebone:~# pwd
> /root
> root@beaglebone:~# ls -lha ./
> total 28K
> drwx--  5 root root 4.0K Dec  6 21:32 .
> drwxr-xr-x 21 root root 4.0K Jan  1  2000 ..
> -rw-r--r--  1 root root  570 Jan 31  2010 .bashrc
> drwxr-xr-x  9 root root 4.0K Dec  6 21:23 .c9
> drwxr-xr-x  3 root root 4.0K Dec  6 21:23 .cache
> drwxr-xr-x  3 root root 4.0K Dec  6 21:24 .node-gyp
> -rw-r--r--  1 root root  140 Nov 19  2007 .profile
>
> Well that's broken, so we can drop /home/debian/.npmrc
>
>
> https://github.com/RobertCNelson/omap-image-builder/commit/5dfed9a2703c4013f9577b2e04f65e18568bd409
>


and the rest are mine..

drwxr-xr-x  2 rootroot  4.0K Dec  6 21:04 bluetooth
-rw-r--r--  1 polkitd bluetooth   40 Dec  6 21:06 dogtag
-rw-r--r--  1 polkitd bluetooth   11 Dec  6 23:11 hostname
-rw-r--r--  1 polkitd bluetooth  213 Dec  6 23:11 hosts
-rw-r--r--  1 polkitd bluetooth  263 Dec  7 19:05 issue
-rw-r--r--  1 polkitd bluetooth  175 Dec  6 21:29 issue.net
-rw-r--r--  1 polkitd bluetooth   86 Dec  6 21:06 rcn-ee.conf

those should all be root:root

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

[beagleboard] 1080p/720p USB Cameras

2015-12-07 Thread SWiT

I'm trying to record a USB 1080p 30fps USB webcam but I can't get much over 
10fps at 1080p or 720p. The resolution change from 1920x1080 to 1280x720 
does not seem to effect the fps at all.

I've tried 2 cameras, a generic winbook 1080p webcam and a very nice 
Logitech c930e. I am using MJPEG compression. Both work at 30fps in Ubuntu 
14.04 with cheese and avconv (libav-tools).

On the BBB I ran top and iotop and they indicated the CPU never got above 
10% and the bandwidth writing to disk was <4,000KBps. I got the same low 
fps when running on the debian 7.5 (2015-03-01) and 7.9 (2015-11-12) 
releases.  I couldn't get 8.2 (2015-11-12) to boot but I'll rewrite the SD 
card and try again if someone thinks it might help.


The kicker is the Logitech c930e worked at 1080p@30fps on the RaspberryPi2, 
but the cheap generic camera would only run at 1080p@10fps on the RPi2.



Should I be building the UVC drivers from the latest source or something 
like that? Is there a newer Kernel I should be using? Am I hitting some 
kind of USB bottleneck?

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

Re: [beagleboard] who are user UID 110 and group GID 116?

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 2:47 PM, Maurice H.  wrote:

> I must agree with you that `npm` is not the ideal packagemanager. ;-)
> There also seems to be `pip` installed for Python packages...
>
> Is there a remote possibility that those packages would ever be offered
> via `apt-get` ?
>

i wish...  cloud9 ide has to be installed via npm, then they broke some of
the npm packaging, so you have install some npm dependices on target,
before you can run the "standalone" package...



>
> Problem is that even as the root user some things (I forget which) didn't
> work off the bat because of those broken ownerships. I ended up chowning
> them to root:root (for files in `/etc/`) and debian:debian for files in
> `/home/debian`.
>


debian@beaglebone:~$ sudo cat .npmrc
cache = /root/.npm
group = 0
init-module = /root/.npm-init.js
tmp = /root/tmp
user = 0
userconfig = /root/.npmrc

root@beaglebone:~# pwd
/root
root@beaglebone:~# ls -lha ./
total 28K
drwx--  5 root root 4.0K Dec  6 21:32 .
drwxr-xr-x 21 root root 4.0K Jan  1  2000 ..
-rw-r--r--  1 root root  570 Jan 31  2010 .bashrc
drwxr-xr-x  9 root root 4.0K Dec  6 21:23 .c9
drwxr-xr-x  3 root root 4.0K Dec  6 21:23 .cache
drwxr-xr-x  3 root root 4.0K Dec  6 21:24 .node-gyp
-rw-r--r--  1 root root  140 Nov 19  2007 .profile

Well that's broken, so we can drop /home/debian/.npmrc

https://github.com/RobertCNelson/omap-image-builder/commit/5dfed9a2703c4013f9577b2e04f65e18568bd409

 ;)

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

Re: [beagleboard] who are user UID 110 and group GID 116?

2015-12-07 Thread Maurice H.

I must agree with you that `npm` is not the ideal packagemanager. ;-) 
There also seems to be `pip` installed for Python packages...

Is there a remote possibility that those packages would ever be offered via 
`apt-get` ?

Problem is that even as the root user some things (I forget which) didn't 
work off the bat because of those broken ownerships. I ended up chowning 
them to root:root (for files in `/etc/`) and debian:debian for files in 
`/home/debian`. 

On Monday, 7 December 2015 21:26:58 UTC+1, RobertCNelson wrote:
>
>
>
> On Mon, Dec 7, 2015 at 2:14 PM, Maurice H.  > wrote:
>
>> I have found in the `/home/debian` folder and in the `/etc` tree a couple 
>> of files that have a UID of 110 and GID of 116.
>> Notably `/home/debian/.npmrc`
>>
>> `/etc/passwd` doesn't contain a user with that UID and `/etc/group` 
>> doesn't have the GID listed.
>>
>> Who are they supposed to be?
>>
>
> as root user we install a few packages via "npm install xyz"
>
>
> https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org-wheezy.sh#L244
>
> It's one of the worst package systems i've seen, doing random things to 
> all over the rootfs..
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] who are user UID 110 and group GID 116?

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 2:14 PM, Maurice H.  wrote:

> I have found in the `/home/debian` folder and in the `/etc` tree a couple
> of files that have a UID of 110 and GID of 116.
> Notably `/home/debian/.npmrc`
>
> `/etc/passwd` doesn't contain a user with that UID and `/etc/group`
> doesn't have the GID listed.
>
> Who are they supposed to be?
>

as root user we install a few packages via "npm install xyz"

https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org-wheezy.sh#L244

It's one of the worst package systems i've seen, doing random things to all
over the rootfs..

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

Re: [beagleboard] why eSATA in X-15?

2015-12-07 Thread John Syne

In u-boot, “scsi scan” doesn’t show anything. even “scsi reset” doesn’t find 
any devices.

Regards,
John




> On Dec 7, 2015, at 11:45 AM, Robert Nelson  wrote:
> 
> 
> 
> On Mon, Dec 7, 2015 at 1:39 PM, Robert Nelson  > wrote:
> 
> 
> On Mon, Dec 7, 2015 at 1:33 PM, John Syne  > wrote:
> Hi Robert,
> 
> I bought this cable and connected a 240GB SSD. I dd a 32GB SDCard image to 
> the SSD. I can mount /dev/sda1 and see rootfs. I changed the jumpers to 
> select SATA as shown the the quick start guide (J3 1-2, j4 2-3, j6 2-3) and 
> removed the SDCard. After powering down, I push the power button (s1), I see 
> the power led (D3) light for a few seconds and goes out. I see nothing on the 
> console. I also tried setting the jumpers per the PCB legend (J3 2-3, J4 1.2 
> J6 2-3) and I get the same results.
> 
> Oh, don't change the jumpers. The production x15's isn't going to have them, 
> only the am57xx evm's.
> 
> (and i haven't spent any time figuring out how to raw boot from a scsi 
> device, probably need a custom u-boot setting... ;) )
> 
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] who are user UID 110 and group GID 116?

2015-12-07 Thread Maurice H.

I have found in the `/home/debian` folder and in the `/etc` tree a couple 
of files that have a UID of 110 and GID of 116.
Notably `/home/debian/.npmrc`

`/etc/passwd` doesn't contain a user with that UID and `/etc/group` doesn't 
have the GID listed.

Who are they supposed to be?

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

Re: [beagleboard] why eSATA in X-15?

2015-12-07 Thread John Syne

Yeah, that was what I was trying to do. When I saw the jumper settings, I 
though this was possible.

Regards,
John




> On Dec 7, 2015, at 11:45 AM, Robert Nelson  wrote:
> 
> 
> 
> On Mon, Dec 7, 2015 at 1:39 PM, Robert Nelson  > wrote:
> 
> 
> On Mon, Dec 7, 2015 at 1:33 PM, John Syne  > wrote:
> Hi Robert,
> 
> I bought this cable and connected a 240GB SSD. I dd a 32GB SDCard image to 
> the SSD. I can mount /dev/sda1 and see rootfs. I changed the jumpers to 
> select SATA as shown the the quick start guide (J3 1-2, j4 2-3, j6 2-3) and 
> removed the SDCard. After powering down, I push the power button (s1), I see 
> the power led (D3) light for a few seconds and goes out. I see nothing on the 
> console. I also tried setting the jumpers per the PCB legend (J3 2-3, J4 1.2 
> J6 2-3) and I get the same results.
> 
> Oh, don't change the jumpers. The production x15's isn't going to have them, 
> only the am57xx evm's.
> 
> (and i haven't spent any time figuring out how to raw boot from a scsi 
> device, probably need a custom u-boot setting... ;) )
> 
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] why eSATA in X-15?

2015-12-07 Thread John Syne

U-Boot SPL 2015.07-00129-g645e7d3 (Oct 08 2015 - 16:41:20)  

   
DRA752 ES1.1

   


   


   
U-Boot 2015.07-00129-g645e7d3 (Oct 08 2015 - 16:41:20 -0500), Build: 
jenkins-github_Bootloader-Builder-245   
  


   
CPU  : DRA752 ES1.1 

   
Board: BeagleBoard x15  

   
I2C:   ready

   
DRAM:  2 GiB

   
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1   

   


   
** Unable to use mmc 0:1 for loading the env ** 

   
Using default environment   

   


   
SATA link 0 timeout.

   
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode   

   
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst

   
SCSI:  SATA link 0 timeout. 

   
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode   

   
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst

   
scanning bus for devices... 

   
Found 0 device(s).  

   
Net:not set. Validating first E-fuse MAC   

   
cpsw

   
Hit any key to stop autoboot:  0

   
resetting USB...

   
USB0:   Register 2000140 NbrPorts 2 

   
Starting the controller

Re: [beagleboard] why eSATA in X-15?

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 1:39 PM, Robert Nelson 
wrote:

>
>
> On Mon, Dec 7, 2015 at 1:33 PM, John Syne  wrote:
>
>> Hi Robert,
>>
>> I bought this cable and connected a 240GB SSD. I dd a 32GB SDCard image
>> to the SSD. I can mount /dev/sda1 and see rootfs. I changed the jumpers to
>> select SATA as shown the the quick start guide (J3 1-2, j4 2-3, j6 2-3) and
>> removed the SDCard. After powering down, I push the power button (s1), I
>> see the power led (D3) light for a few seconds and goes out. I see nothing
>> on the console. I also tried setting the jumpers per the PCB legend (J3
>> 2-3, J4 1.2 J6 2-3) and I get the same results.
>>
>
> Oh, don't change the jumpers. The production x15's isn't going to have
> them, only the am57xx evm's.
>

(and i haven't spent any time figuring out how to raw boot from a scsi
device, probably need a custom u-boot setting... ;) )

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

Re: [beagleboard] why eSATA in X-15?

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 1:33 PM, John Syne  wrote:

> Hi Robert,
>
> I bought this cable and connected a 240GB SSD. I dd a 32GB SDCard image to
> the SSD. I can mount /dev/sda1 and see rootfs. I changed the jumpers to
> select SATA as shown the the quick start guide (J3 1-2, j4 2-3, j6 2-3) and
> removed the SDCard. After powering down, I push the power button (s1), I
> see the power led (D3) light for a few seconds and goes out. I see nothing
> on the console. I also tried setting the jumpers per the PCB legend (J3
> 2-3, J4 1.2 J6 2-3) and I get the same results.
>

Oh, don't change the jumpers. The production x15's isn't going to have
them, only the am57xx evm's.

I've configured u-boot on the microSD to look at the drives like so:

usb : (search first 4 partitions) (usb enables scsi power rail in u-boot,
hence first)
scsi: (search first 4 partitions)
eMMC: (search first 8 partitions)
microSD: (search first 8 partitions)

To setup boot from sata, return the jumpers to eMMC/microsd

boot into debian

cd /opt/scripts/
git pull

WARNING only have sata or usb plugged in, not both.. (script is hardcoded
for /dev/sda)

cd /opt/scripts/tools/non-mmc-rootfs
sudo ./mv_rootfs_dev_sda.sh

reboot..

microSD/eMMC (u-boot) searches scsi and boots from it. ;)

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

Re: [beagleboard] why eSATA in X-15?

2015-12-07 Thread John Syne

Hi Robert,

I bought this cable and connected a 240GB SSD. I dd a 32GB SDCard image to the 
SSD. I can mount /dev/sda1 and see rootfs. I changed the jumpers to select SATA 
as shown the the quick start guide (J3 1-2, j4 2-3, j6 2-3) and removed the 
SDCard. After powering down, I push the power button (s1), I see the power led 
(D3) light for a few seconds and goes out. I see nothing on the console. I also 
tried setting the jumpers per the PCB legend (J3 2-3, J4 1.2 J6 2-3) and I get 
the same results.

Regards,
John




> On Dec 1, 2015, at 1:43 PM, Robert Nelson  wrote:
> 
> On Tue, Dec 1, 2015 at 3:41 PM, William Hermans  wrote:
>> Or, how about using an eSATA enclosure ? they're not that expensive . .
>> .http://www.amazon.com/Anker%C2%AE-Aluminum-External-Enclosure-12-5mm/dp/B005B5G4S6
>> 
>> eSATA enclosures also usually double as an USB enclosure as well. While on
>> the subject. eSATA is usually more performant when compared to USB, but that
>> can depend on the host controller as well.
> 
> Or these:
> 
> http://www.amazon.com/gp/product/B002MKKTWA
> 
> pair up with an ssd, perfect for the x15..
> 
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

no. still, the host gets not assigned an ip address. if I assign one 
manually, doesn't change the fact, that somehow messages don't get through 
to the bone...

on host:
eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa  
  inet addr:192.168.7.1  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:44 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2 errors:174 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:7511 (7.5 KB)  TX bytes:520 (520.0 B)
fdalbert@edge ~/beaglebone/kernel4-1-new/ti-linux-kernel-dev $ sudo tcpdump 
-i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
19:46:52.116552 IP 192.168.7.1.netbios-ns > 192.168.7.3.netbios-ns: NBT UDP 
PACKET(137): REGISTRATION; REQUEST; BROADCAST
19:46:52.116593 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui 
Unknown), length 28
19:46:52.116595 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, 
Request from 84:eb:18:ae:cb:aa (oui Unknown), length 300
19:46:52.116606 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui 
Unknown), length 28
19:46:52.116608 IP 192.168.7.1.netbios-ns > 192.168.7.3.netbios-ns: NBT UDP 
PACKET(137): REGISTRATION; REQUEST; BROADCAST
19:46:52.116658 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui 
Unknown), length 28
19:46:52.238846 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 28
19:46:52.238866 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui 
Unknown), length 28
19:46:53.238687 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 28
19:46:53.238711 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui 
Unknown), length 28
19:46:53.741673 IP 192.168.7.1.mdns > 224.0.0.251.mdns: 0 [2q] PTR (QM)? 
_ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
19:46:54.247896 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 28
19:46:54.247917 ARP, Reply 192.168.7.1 is-at 84:eb:18:ae:cb:aa (oui 
Unknown), length 28
19:46:54.941595 IP 192.168.7.1.1534 > 192.168.7.3.1534: UDP, length 8

on the bone:
usb0  Link encap:Ethernet  HWaddr da:3d:72:a2:b3:7a  
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::d83d:72ff:fea2:b37a/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1 errors:0 dropped:0 overruns:0 frame:0
  TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:76 (76.0 B)  TX bytes:9547 (9.3 KiB)

root@beaglebone:~# ping 192.168.7.1
PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
>From 192.168.7.2 icmp_seq=1 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=2 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=3 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=4 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=5 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=6 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=7 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=8 Destination Host Unreachable
>From 192.168.7.2 icmp_seq=9 Destination Host Unreachable

I'm stuck

On Monday, December 7, 2015 at 7:15:24 PM UTC+1, William Hermans wrote:
>
> SO is the hardware detected on both sides now or what ? If its just a dhcp 
> thing, you can always just use static IPs. Which is exactly what I always 
> do . . .
>
> On Mon, Dec 7, 2015 at 11:06 AM, Fabian Dalbert  > wrote:
>
>> I restarted from a backup, updated /opt/scripts/ with kernel 3.8 and 
>> installed the new kernel using dpkg as William suggested. No luck.
>>
>> usb0  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:a0  
>>   inet addr:192.168.7.2  Bcast:192.168.7.255  Mask:255.255.255.0
>>   inet6 addr: fe80::86eb:18ff:feae:cba0/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000 
>>   RX bytes:76 (76.0 B)  TX bytes:9563 (9.3 KiB)
>>
>> root@beaglebone:~# systemd-journalctl | grep usb
>> Mar 01 21:02:39 beaglebone udhcpd[772]: is interface usb0 up and 
>> configured?...e
>> Mar 01 21:02:45 beaglebone avahi-daemon[692]: New relevant interface 
>> usb0.IP
>> Mar 01 21:02:46 beaglebone ntpd[1133]: Listen normally on 4 usb0 
>> 192.168.723
>> Mar 01 21:02:46 beaglebone avahi-daemon[692]: New relevant interface 
>> usb0.IP
>> Mar 01 21:02:48 beaglebone ntpd[1133]: Listen normally on 5 usb0 
>> fe80::86eb...23
>>
>> restarting udhcpd also does not do the trick. Any ideas?
>>
>> Thanks for your help!
>>
>>
>> On Monday, December 7, 2015 at 5:55:23 PM UTC+1, Fabian Dalbert wrote:
>>>
>>> it should be now. however I don't currently ha

Re: [beagleboard] BeagleBone Black is dead !!! PWR led blinks for aprox <15ms and then nothing happens. HELP !

2015-12-07 Thread Gerald Coley

BeagleBone Black is dead.

http://www.elinux.org/Beagleboard:BeagleBoneBlack#RMA_Support

Gerald


On Mon, Dec 7, 2015 at 11:02 AM,  wrote:

> Hello folkx,
>
> As mentioned in the topic head lines, I have been developing projects on
> my beaglebone black, powered through AC adaptor (5V and 2Amp) and it was
> running all fine. But now it doesn't gets on. when I try to turn it on, its
> PWR led beeps for aprox < 15 ms and then nothing happens. Its completely
> dead now. What can be the possible reason for that? have anyone else
> experienced this issue ? Is its power IC damaged or what ?. I am very
> tensed now...
>
> I will highly appreciate someone's help.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

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

[beagleboard] BeagleBone Black is dead !!! PWR led blinks for aprox <15ms and then nothing happens. HELP !

2015-12-07 Thread anumsheraz166

Hello folkx, 

As mentioned in the topic head lines, I have been developing projects on my 
beaglebone black, powered through AC adaptor (5V and 2Amp) and it was 
running all fine. But now it doesn't gets on. when I try to turn it on, its 
PWR led beeps for aprox < 15 ms and then nothing happens. Its completely 
dead now. What can be the possible reason for that? have anyone else 
experienced this issue ? Is its power IC damaged or what ?. I am very 
tensed now...

I will highly appreciate someone's help. 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Enabling MMC2 for 4 bit SDIO Wifi Card

2015-12-07 Thread Gerald Coley

The pins are on the expansion connector. The determination as to how they
work and if it is adequate for whatever purpose is dictated by the
processor itself and the SW support.

I do not know of anyone hat has used these pins for SDIO. But per the
documentation from TI, they should be able to do it.

Gerald



On Mon, Dec 7, 2015 at 11:19 AM,  wrote:

> Looking at those files I see that the wl1835 utilizes the MMC1 pins. I
> want to try and keep the MMC1 for the eMMC and only use the MMC2.
>
> Does the Beaglebone Black support this from a HW point of view? I have not
> found any example of someone using the MMC2 bus.
>
> Cheers,
> Danny
>
> P.S. Thank you Robert for all your effort and time you put into the
> Beaglebone project!
> On Monday, December 7, 2015 at 10:53:47 AM UTC-6, RobertCNelson wrote:
>>
>>
>>
>> On Mon, Dec 7, 2015 at 10:41 AM,  wrote:
>>
>>> Hi Ya'll,
>>>
>>>
>>> I am trying to interface a LSR TIWi-BLE wifi card with my Beaglebone
>>> Black. I would like to keep the on board eMMC functional so I cannot use
>>> MMC1.
>>>
>>> Looking at the Sitara datasheet and the Beaglebone black schematic it
>>> seems that all 6 wires needed for 4 bit SDIO SDIO are available on the
>>> header.
>>>
>>> MMC2_CLK -> 8.18
>>> MMC2_CMD -> 9.15 (also attached to another input, would need to remove
>>> R160?)
>>> MMC2_DAT0 -> 8.12
>>> MMC2_DAT1 -> 8.11
>>> MMC2_DAT2 -> 8.16
>>> MMC2_DAT3 -> 8.15
>>>
>>> Do I just need to write an overlay to enable these pins for mmc function
>>> in the cape manager?
>>>
>>
>> the mmc layer in v4.1.x wasn't happy as an overlay, take a look at the
>> wl1835mod cape/board example:
>>
>>
>> https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod.dts
>>
>> https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod-cape.dtsi
>>
>> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

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

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread William Hermans

SO is the hardware detected on both sides now or what ? If its just a dhcp
thing, you can always just use static IPs. Which is exactly what I always
do . . .

On Mon, Dec 7, 2015 at 11:06 AM, Fabian Dalbert  wrote:

> I restarted from a backup, updated /opt/scripts/ with kernel 3.8 and
> installed the new kernel using dpkg as William suggested. No luck.
>
> usb0  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:a0
>   inet addr:192.168.7.2  Bcast:192.168.7.255  Mask:255.255.255.0
>   inet6 addr: fe80::86eb:18ff:feae:cba0/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:76 (76.0 B)  TX bytes:9563 (9.3 KiB)
>
> root@beaglebone:~# systemd-journalctl | grep usb
> Mar 01 21:02:39 beaglebone udhcpd[772]: is interface usb0 up and
> configured?...e
> Mar 01 21:02:45 beaglebone avahi-daemon[692]: New relevant interface
> usb0.IP
> Mar 01 21:02:46 beaglebone ntpd[1133]: Listen normally on 4 usb0
> 192.168.723
> Mar 01 21:02:46 beaglebone avahi-daemon[692]: New relevant interface
> usb0.IP
> Mar 01 21:02:48 beaglebone ntpd[1133]: Listen normally on 5 usb0
> fe80::86eb...23
>
> restarting udhcpd also does not do the trick. Any ideas?
>
> Thanks for your help!
>
>
> On Monday, December 7, 2015 at 5:55:23 PM UTC+1, Fabian Dalbert wrote:
>>
>> it should be now. however I don't currently have network access on the
>> beaglebone, I therefore cloned
>> https://github.com/RobertCNelson/boot-scripts to my desktop and copied
>> it over.
>>
>> On Monday, December 7, 2015 at 5:26:11 PM UTC+1, RobertCNelson wrote:
>>
>> ahh, looks like a race between usb0 & udhcpd..
>>>
>>> is /opt/scripts/ up to date?
>>>
>>> cd /opt/scripts/
>>> git pull
>>>
>>> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

I restarted from a backup, updated /opt/scripts/ with kernel 3.8 and 
installed the new kernel using dpkg as William suggested. No luck.

usb0  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:a0  
  inet addr:192.168.7.2  Bcast:192.168.7.255  Mask:255.255.255.0
  inet6 addr: fe80::86eb:18ff:feae:cba0/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1 errors:0 dropped:0 overruns:0 frame:0
  TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:76 (76.0 B)  TX bytes:9563 (9.3 KiB)

root@beaglebone:~# systemd-journalctl | grep usb
Mar 01 21:02:39 beaglebone udhcpd[772]: is interface usb0 up and 
configured?...e
Mar 01 21:02:45 beaglebone avahi-daemon[692]: New relevant interface 
usb0.IP
Mar 01 21:02:46 beaglebone ntpd[1133]: Listen normally on 4 usb0 
192.168.723
Mar 01 21:02:46 beaglebone avahi-daemon[692]: New relevant interface 
usb0.IP
Mar 01 21:02:48 beaglebone ntpd[1133]: Listen normally on 5 usb0 
fe80::86eb...23

restarting udhcpd also does not do the trick. Any ideas?

Thanks for your help!

On Monday, December 7, 2015 at 5:55:23 PM UTC+1, Fabian Dalbert wrote:
>
> it should be now. however I don't currently have network access on the 
> beaglebone, I therefore cloned 
> https://github.com/RobertCNelson/boot-scripts to my desktop and copied it 
> over.
>
> On Monday, December 7, 2015 at 5:26:11 PM UTC+1, RobertCNelson wrote:
>
> ahh, looks like a race between usb0 & udhcpd..
>>
>> is /opt/scripts/ up to date?
>>
>> cd /opt/scripts/
>> git pull
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: Private message regarding: [beagleboard] BBB Data Aggregation Unit using external ADC

2015-12-07 Thread John Syne

I have found these references to be the most helpful.

The Linux Programming Interface 

 by Michael Kerrisk
Linux Kernel Development, Third Edition 

 by Robert Love
Linux Device Drivers, 3rd Edition 

 by Jonathan Corbet ...

Regards,
John

> On Dec 7, 2015, at 7:01 AM, Chelsea Orefice  wrote:
> 
> Hi John,
> 
> These are very helpful links. I was wondering if there was an online document 
> on all functions that I can code BBB in either in C, C++, python, etc.
> 
> Thanks,
> Chelsea
> 
> On Thu, Dec 3, 2015 at 11:12 PM, John Syne  > wrote:
> Hi Chelsea,
> 
> Here are some reference I have found helpful:
> 
> http://www.analog.com/library/analogdialogue/archives/39-05/op_amp_applications_handbook.html
>  
> 
> http://www.analog.com/library/analogDialogue/archives/39-06/data_conversion_handbook.html
>  
> 
> 
> Regards,
> John
> 
> 
> 
> 
>> On Dec 3, 2015, at 5:57 PM, Chelsea Orefice > > wrote:
>> 
>> Hi John, 
>> 
>> Just wanted to say thank you for really helping me with this. It has been a 
>> struggle for me and my team to get help from different resources at school 
>> as well as our liaisons where we are getting our design requirements from. 
>> (This is our senior engineering project.) 
>> 
>> I am having still a little difficulty in understanding how the circuitry I 
>> shared with you may give me a single input instead of differential that the 
>> ADC requires.I attached the actual design of the system, so if you could 
>> help me understand how it won't work it'd be much appreciated.
>> 
>> Also, may you tell me your background in relation to all of this? You are 
>> very knowledgeable in this area, and when I relay some of this information 
>> to my team I would like to share from whom I received this information from. 
>> 
>> 
>> Sincerely,
>> Chelsea
>> 
>> On Thu, Dec 3, 2015 at 7:01 PM, John Syne > > wrote:
>> Hi Chelsea,
>> 
>> I have cc beagleboard because someone else might learn from this discussion. 
>> Looking at the link you provided, it won’t work because ADS1278 requires a 
>> differential input. Look at page 39 for circuits that will work for you.
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On Dec 3, 2015, at 3:52 PM, Chelsea Orefice >> > wrote:
>>> 
>>> My apologies. Please let me know if this link works. (You will need to just 
>>> copy and paste in search bar). If that doesn't work I will send it as an 
>>> attachment. Will also look at the diagram as well.
>>> 
>>> http://cnx.org/resou 
>>> rces/72628d36f0c24bc80ff94e5c0bf6df2b27a86751/opamp4.png
>>> 
>>> Thanks again,
>>> Chelsea
>>> 
>>> On Thursday, December 3, 2015 at 6:46:49 PM UTC-5, john3909 wrote:
>>> Look at page 39 for a suitable input circuit. 
>>> 
>>> Regards,
>>> John
>>> 
>>> 
>>> 
>>> 
 On Dec 3, 2015, at 3:03 PM, Chelsea Orefice > wrote:

 Hi John,

 Thanks for getting back to me. I was actually looking at that same ADC 
 converter as you posted in your reply. Just looking for some clarification 
 on a few things. What type of error would a simple resistor divider 
 introduce into the system? I am currently using a cascaded inverting op 
 amp system. Not really sure if this will scale the input voltage to a 
 level that is compatible with my ADC.

 The circuit diagram looks like this: 

 Looking forward to your reply,
 Chels

 On Thursday, December 3, 2015 at 5:07:41 PM UTC-5, Chelsea Orefice wrote:
 Hi everyone,

 I am new to the world of using MCUs and am looking for some assistance on 
 a project that I am currently working on. To sum things up quickly, I am 
 building a data aggregation unit that can convert analog voltage readings 
 to digital values that is to be stored on a USB or SD card. The DAU will 
 collect 3 types of signals, a buffer signal, clipped signal, and a signal 
 passed through a LPF. In the end, the data should be stored as either a 
 MatLab file or .xml file. However, I am facing a few road blocks relating 
 to my design. 

 1.) I need to use a 24 bit ADC for high resolution purposes based on 
 design requirements that were just given to me as I will be collecting 
 data from .1mV to 50V and it has to have a high sample speed rate. Has 
 anyone connected an external ADC to the BBB? If so, what was the brand of 
 your external ADC? How did you connect the ADC to the BBB? (It'd be

Re: [beagleboard] Enabling MMC2 for 4 bit SDIO Wifi Card

2015-12-07 Thread c . danny . salzman

Looking at those files I see that the wl1835 utilizes the MMC1 pins. I want 
to try and keep the MMC1 for the eMMC and only use the MMC2.

Does the Beaglebone Black support this from a HW point of view? I have not 
found any example of someone using the MMC2 bus.

Cheers,
Danny

P.S. Thank you Robert for all your effort and time you put into the 
Beaglebone project!
On Monday, December 7, 2015 at 10:53:47 AM UTC-6, RobertCNelson wrote:
>
>
>
> On Mon, Dec 7, 2015 at 10:41 AM, > 
> wrote:
>
>> Hi Ya'll,
>>
>>
>> I am trying to interface a LSR TIWi-BLE wifi card with my Beaglebone 
>> Black. I would like to keep the on board eMMC functional so I cannot use 
>> MMC1. 
>>
>> Looking at the Sitara datasheet and the Beaglebone black schematic it 
>> seems that all 6 wires needed for 4 bit SDIO SDIO are available on the 
>> header.
>>
>> MMC2_CLK -> 8.18
>> MMC2_CMD -> 9.15 (also attached to another input, would need to remove 
>> R160?)
>> MMC2_DAT0 -> 8.12
>> MMC2_DAT1 -> 8.11
>> MMC2_DAT2 -> 8.16
>> MMC2_DAT3 -> 8.15
>>
>> Do I just need to write an overlay to enable these pins for mmc function 
>> in the cape manager?
>>
>
> the mmc layer in v4.1.x wasn't happy as an overlay, take a look at the 
> wl1835mod cape/board example:
>
>
> https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod.dts
>
> https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod-cape.dtsi
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

it should be now. however I don't currently have network access on the 
beaglebone, I therefore cloned 
https://github.com/RobertCNelson/boot-scripts to my desktop and copied it 
over.

On Monday, December 7, 2015 at 5:26:11 PM UTC+1, RobertCNelson wrote:

ahh, looks like a race between usb0 & udhcpd..
>
> is /opt/scripts/ up to date?
>
> cd /opt/scripts/
> git pull
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Enabling MMC2 for 4 bit SDIO Wifi Card

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 10:41 AM,  wrote:

> Hi Ya'll,
>
>
> I am trying to interface a LSR TIWi-BLE wifi card with my Beaglebone
> Black. I would like to keep the on board eMMC functional so I cannot use
> MMC1.
>
> Looking at the Sitara datasheet and the Beaglebone black schematic it
> seems that all 6 wires needed for 4 bit SDIO SDIO are available on the
> header.
>
> MMC2_CLK -> 8.18
> MMC2_CMD -> 9.15 (also attached to another input, would need to remove
> R160?)
> MMC2_DAT0 -> 8.12
> MMC2_DAT1 -> 8.11
> MMC2_DAT2 -> 8.16
> MMC2_DAT3 -> 8.15
>
> Do I just need to write an overlay to enable these pins for mmc function
> in the cape manager?
>

the mmc layer in v4.1.x wasn't happy as an overlay, take a look at the
wl1835mod cape/board example:

https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod.dts
https://github.com/beagleboard/linux/blob/4.1/arch/arm/boot/dts/am335x-boneblack-wl1835mod-cape.dtsi

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

[beagleboard] Re: Clear CPU caches for reading system timer on beaglebone

2015-12-07 Thread anand2083

Hi 

I too am working on the timer4 and trying to access the registers using 
dev/mem. However I get bus error when trying to read the address. Can you 
let me know how you did this using dev/mem.

My code is posted below:

#include #include #include #include 
#include#include#include 
#define TIMER4_START_addr 0x48044000#define TIDR 0x00#define TIOCP_CFG 0x10
int main(){
   unsigned int reg;

   char *timer_addr = NULL;

   printf("\n Start Pgm");

int mem, integer;

if ((mem = open ("/dev/mem", O_RDWR | O_SYNC)) < 0)
{
printf("Cannot open /dev/mem\n");

return 1;
}

printf("Opened /dev/mem\n");

timer_addr = mmap(0, 4096, PROT_READ | PROT_WRITE, MAP_SHARED, mem, 
TIMER4_START_addr);

printf("GPIO mapped to %p\n", timer_addr);

reg =  *((int*) timer_addr);

printf("GPIO1 configuration: %x\n", reg);

return 0;}

Regards
Anand




On Wednesday, 14 May 2014 00:26:47 UTC+5:30, fis@gmail.com wrote:
>
> Hi,
>
> I am using TI AM335x BeagleBone. My aim is to get fast and reliable time 
> values from user-space using dmtimer.
>
> When I I read (and print) tick values of DMTimer2 though /dev/mem, I have 
> the following:
>
> 2703519715
> 2703525474
> 2703527633
> 2703529333
> 2703530952
> 2703532576
> 2703538448
> 2703541914
> 2703543656
> 2703545281
> 2703546900
>
> However, when I invoke device driver with mmap operation and then in user 
> space interact with this device, I have a strange behaviour. 
> Ticks are repeated periodically: 
>
> 1287902680
> 1287911282
> 1287911282
> 1287911282
> 1287911282
> 1287911282
> 1287925948
> 1287925948
> 1287925948
> 1287935869
> 1287935869
> 1287935869
> 1287944825
> 1287944825
> 1287950109
> 1287950109
> 1287959332
>
> I am not sure, but it looks like L1/L2 caches are overflowed. My question is 
> what can cause this behaviour. And if it is CPU caches, how they can be 
> cleared. 
> I found this answer 
> http://stackoverflow.com/questions/3446138/how-to-clear-cpu-l1-and-l2-cache, 
> but I doubt how I can apply this method.
> Do you have any suggestions? I will appreciate any help.
>
>
> If it is necessary, I post here briefly the way how I obtaine these ticks vs 
> driver.
>
> 1. remapping of a specific region in kernel space (0x4804 - DMTIMER2 
> register start address):
>
> static int simple_remap_mmap(struct file *filp, struct vm_area_struct *vma) 
> {
>   unsigned long off = vma->vm_pgoff << PAGE_SHIFT; 
>   // generate the correct page frame number
>   unsigned long pfn = (0x4804 + off) >> PAGE_SHIFT; 
>   // vsize is the requested size of virtual memory  
>   unsigned long vsize = vma->vm_end - vma->vm_start; 
>   // psize is the physical I/O size that is left after the offset has been 
> specified 
>   unsigned long psize = 0x4804 + 32 - off; 
>   // refuses to map addresses that extend beyond the allowed memory range
>   if (vsize > psize)
>   {
> return -EINVAL;
>   }
>   if (remap_pfn_range(vma, vma->vm_start, pfn, vsize, vma->vm_page_prot))
>   {
> return
>   -EAGAIN; 
>   }
>   vma->vm_ops = &simple_remap_vm_ops; 
>   simple_vma_open(vma); 
>   return 0; 
> }
>
> 2. in user space I do it approximately in the following way:
>
> volatile unsigned char* dmt2_regs;
> dmt2_regs = (unsigned char*) mmap(NULL, 0x1000, PROT_READ|PROT_WRITE, 
> MAP_SHARED, fd, 0); 
> while (true) 
> { 
>   uint32_t t0 = * (uint32_t*) ( dmt2_regs + 0x3c ); 
>   std::cout << t0 << std::endl; 
> } 
>
>

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

[beagleboard] Re: Configure Beaglebone to access usb0 from host PC. (Cannot ssh to beaglebone through USB)

2015-12-07 Thread rojjaas

I have the same too. I echieved to work on Eclipse for work in Java. But 
next day, when I turn on the laptop, I have tried to connect with psftp or 
putty (open 192.168.7.2 ) neither Eclipse, and I don't have achieved it. I 
have failed. What can I do? Thanks. Note: The connection by browser works 
well. (Mozilla Firefox 192.168.7.2 and 192.168.7.2:3000 0K).

El viernes, 30 de octubre de 2015, 12:13:55 (UTC-5), Alex escribió:
>
> Hi,
>
> I am using ubuntu 14.04 (from Robert Nelson ) with a 
> custom 3.15.10-bone8 kernel on Beaglebone Black. HDMI is disabled. 
> When I plug the board to a PC, Beaglebone powers up but the PC does not 
> recognize that a USB device is connected to it. I have installed the 
> drivers for network-over-USB which is recommended on 
> Beagleboard.org/getting-started too. Moreover, I cannot ssh into it using 
> 192.168.7.2 eventhough I have set up my /etc/network/interfaces. 
> ubuntu@arm $ ifconfig usb0
> usb0  Link encap:Ethernet  HWaddr d2:56:2f:23:1d:e2
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
> Is there some modules that I need to run or compile to Kernel to bring the 
> client USB up? How should I configure the linux to be seen by PC when 
> connected from mini USB?
> Thanks for any help. 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Enabling MMC2 for 4 bit SDIO Wifi Card

2015-12-07 Thread c . danny . salzman

Hi Ya'll,


I am trying to interface a LSR TIWi-BLE wifi card with my Beaglebone Black. 
I would like to keep the on board eMMC functional so I cannot use MMC1. 

Looking at the Sitara datasheet and the Beaglebone black schematic it seems 
that all 6 wires needed for 4 bit SDIO SDIO are available on the header.

MMC2_CLK -> 8.18
MMC2_CMD -> 9.15 (also attached to another input, would need to remove 
R160?)
MMC2_DAT0 -> 8.12
MMC2_DAT1 -> 8.11
MMC2_DAT2 -> 8.16
MMC2_DAT3 -> 8.15

Do I just need to write an overlay to enable these pins for mmc function in 
the cape manager?

I'm currently waiting for the device to begin testing, but I am surprised 
to see that I could not find any resources or documentation of someone 
interfacing with a 4 bit SDIO device on MMC2 while maintaining eMMC func on 
MMC1

Would love to hear if anyone has accomplished this already and how they 
went about solving this problem.

Cheers,
Danny Salzman

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

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

Sorry for the cutoff on the beaglebone output, I'm currently using 
minicom...

@William: that's actually a very good idea, thanks! I'll try installing the 
kernel like that from now on.
I tried to turn off systemd, following your instructions in another thread. 
Didn't help though.

On Monday, December 7, 2015 at 5:17:38 PM UTC+1, Fabian Dalbert wrote:
>
> Here's what I see:
>
> Host: (sadly no journalctl as linux mint is still based on ubuntu 14.04)
> [78574.911519] usb 2-1.7: new high-speed USB device number 15 using 
> ehci-pci
> [78575.004301] usb 2-1.7: New USB device found, idVendor=1d6b, 
> idProduct=0104
> [78575.004305] usb 2-1.7: New USB device strings: Mfr=3, Product=4, 
> SerialNumber=5
> [78575.004307] usb 2-1.7: Product: BeagleBone
> [78575.004309] usb 2-1.7: Manufacturer: Circuitco
> [78575.004310] usb 2-1.7: SerialNumber: -
> [78575.007074] rndis_host 2-1.7:1.0 eth1: register 'rndis_host' at 
> usb-:00:1d.0-1.7, RNDIS device, 84:eb:18:ae:cb:aa
> [78575.007451] cdc_acm 2-1.7:1.2: This device cannot do calls on its own. 
> It is not a modem.
> [78575.007474] cdc_acm 2-1.7:1.2: ttyACM0: USB ACM device
> [78575.008073] usb-storage 2-1.7:1.4: USB Mass Storage device detected
> [78575.008368] scsi24 : usb-storage 2-1.7:1.4
> [78576.007089] scsi 24:0:0:0: Direct-Access LinuxFile-Stor Gadget 
> 0401 PQ: 0 ANSI: 2
> [78576.007323] sd 24:0:0:0: Attached scsi generic sg2 type 0
> [78576.015073] sd 24:0:0:0: [sdb] 196608 512-byte logical blocks: (100 
> MB/96.0 MiB)
> [78576.015778] sd 24:0:0:0: [sdb] Write Protect is off
> [78576.015782] sd 24:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> [78576.016443] sd 24:0:0:0: [sdb] Write cache: enabled, read cache: 
> enabled, doesn't support DPO or FUA
> [78576.019831]  sdb:
> [78576.023439] sd 24:0:0:0: [sdb] Attached SCSI removable disk
>
> fdalbert@edge ~ $ sudo ifconfig -a
>
> eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa  
>   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:41 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2 errors:522 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:7554 (7.5 KB)  TX bytes:520 (520.0 B)
>
> fdalbert@edge ~ $ sudo dhclient -v eth1
> Internet Systems Consortium DHCP Client 4.2.4
> Copyright 2004-2012 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
>
> Listening on LPF/eth1/84:eb:18:ae:cb:aa
> Sending on   LPF/eth1/84:eb:18:ae:cb:aa
> Sending on   Socket/fallback
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0xfe901674)
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0xfe901674)
> .
> .
> .
> nothing
>
> Beaglebone:
> root@beaglebone:~# systemd-journalctl | grep usb0
> Jan 01 00:00:09 beaglebone udhcpd[629]: is interface usb0 up and 
> configured?...e
> Mar 01 20:46:05 beaglebone udhcpd[1056]: is interface usb0 up and 
> configured...s
> Mar 01 20:46:05 beaglebone avahi-daemon[569]: New relevant interface 
> usb0.IP
> Mar 01 20:46:05 beaglebone avahi-daemon[569]: Interface usb0.IPv4 no 
> longer 
> Mar 01 20:46:05 beaglebone avahi-daemon[569]: New relevant interface 
> usb0.IP
> Mar 01 20:46:06 beaglebone avahi-daemon[569]: New relevant interface 
> usb0.IP
> Mar 01 20:46:08 beaglebone ntpd[734]: Listen normally on 4 usb0 
> 192.168.7.2...23
> Mar 01 20:46:08 beaglebone ntpd[734]: Listen normally on 5 usb0 
> fe80::507b:...23
> root@beaglebone:~# dmesg | grep 
> usb0  
>
>
> [   15.723970] usb0: HOST MAC 84:eb:18:ae:cb:aa
> [   15.728147] usb0: MAC 52:7b:9c:b8:2a:20
>
>
> On Monday, December 7, 2015 at 4:49:45 PM UTC+1, RobertCNelson wrote:
>>
>>
>>
>> On Mon, Dec 7, 2015 at 9:22 AM, Fabian Dalbert  wrote:
>>
>>> journal as in journalctl? doesn't seem to be included. but here's what I 
>>> found in dmesg that seemed relevant:
>>>
>>
>> In wheezy it's systemd-journalctl
>>  
>>
>>>
>>>
>>> [2.976012] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk 
 combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
 [2.976031] musb-hdrc: MHDRC RTL version 2.0 
 [2.976039] musb-hdrc: setup fifo_mode 4
 [2.976056] musb-hdrc: 28/31 max ep, 16384/16384 memory
 [2.977348] 47401b00.usb-phy supply vcc not found, using dummy 
 regulator
 [3.005848] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk 
 combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
 [3.005863] musb-hdrc: MHDRC RTL version 2.0 
 [3.005871] musb-hdrc: setup fifo_mode 4
 [3.005885] musb-hdrc: 28/31 max ep, 16384/16384 memory
 [3.006170] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
 [3.006461] musb-hdrc musb-hdrc.1.auto: new USB bus registered, 
 assigned bus number 1
 [3.006690] usb usb1: New USB device

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 10:17 AM, Fabian Dalbert  wrote:

> Here's what I see:
>
> Host: (sadly no journalctl as linux mint is still based on ubuntu 14.04)
> [78574.911519] usb 2-1.7: new high-speed USB device number 15 using
> ehci-pci
> [78575.004301] usb 2-1.7: New USB device found, idVendor=1d6b,
> idProduct=0104
> [78575.004305] usb 2-1.7: New USB device strings: Mfr=3, Product=4,
> SerialNumber=5
> [78575.004307] usb 2-1.7: Product: BeagleBone
> [78575.004309] usb 2-1.7: Manufacturer: Circuitco
> [78575.004310] usb 2-1.7: SerialNumber: -
> [78575.007074] rndis_host 2-1.7:1.0 eth1: register 'rndis_host' at
> usb-:00:1d.0-1.7, RNDIS device, 84:eb:18:ae:cb:aa
> [78575.007451] cdc_acm 2-1.7:1.2: This device cannot do calls on its own.
> It is not a modem.
> [78575.007474] cdc_acm 2-1.7:1.2: ttyACM0: USB ACM device
> [78575.008073] usb-storage 2-1.7:1.4: USB Mass Storage device detected
> [78575.008368] scsi24 : usb-storage 2-1.7:1.4
> [78576.007089] scsi 24:0:0:0: Direct-Access LinuxFile-Stor Gadget
> 0401 PQ: 0 ANSI: 2
> [78576.007323] sd 24:0:0:0: Attached scsi generic sg2 type 0
> [78576.015073] sd 24:0:0:0: [sdb] 196608 512-byte logical blocks: (100
> MB/96.0 MiB)
> [78576.015778] sd 24:0:0:0: [sdb] Write Protect is off
> [78576.015782] sd 24:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> [78576.016443] sd 24:0:0:0: [sdb] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [78576.019831]  sdb:
> [78576.023439] sd 24:0:0:0: [sdb] Attached SCSI removable disk
>
> fdalbert@edge ~ $ sudo ifconfig -a
>
> eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa
>   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:41 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2 errors:522 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:7554 (7.5 KB)  TX bytes:520 (520.0 B)
>
> fdalbert@edge ~ $ sudo dhclient -v eth1
> Internet Systems Consortium DHCP Client 4.2.4
> Copyright 2004-2012 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
>
> Listening on LPF/eth1/84:eb:18:ae:cb:aa
> Sending on   LPF/eth1/84:eb:18:ae:cb:aa
> Sending on   Socket/fallback
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0xfe901674)
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0xfe901674)
> .
> .
> .
> nothing
>
> Beaglebone:
> root@beaglebone:~# systemd-journalctl | grep usb0
> Jan 01 00:00:09 beaglebone udhcpd[629]: is interface usb0 up and
> configured?...e
> Mar 01 20:46:05 beaglebone udhcpd[1056]: is interface usb0 up and
> configured...s
> Mar 01 20:46:05 beaglebone avahi-daemon[569]: New relevant interface
> usb0.IP
> Mar 01 20:46:05 beaglebone avahi-daemon[569]: Interface usb0.IPv4 no
> longer 
> Mar 01 20:46:05 beaglebone avahi-daemon[569]: New relevant interface
> usb0.IP
> Mar 01 20:46:06 beaglebone avahi-daemon[569]: New relevant interface
> usb0.IP
> Mar 01 20:46:08 beaglebone ntpd[734]: Listen normally on 4 usb0
> 192.168.7.2...23
> Mar 01 20:46:08 beaglebone ntpd[734]: Listen normally on 5 usb0
> fe80::507b:...23
> root@beaglebone:~# dmesg | grep
> usb0
>
> [   15.723970] usb0: HOST MAC 84:eb:18:ae:cb:aa
> [   15.728147] usb0: MAC 52:7b:9c:b8:2a:20
>

ahh, looks like a race between usb0 & udhcpd..

is /opt/scripts/ up to date?

cd /opt/scripts/
git pull

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

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

Here's what I see:

Host: (sadly no journalctl as linux mint is still based on ubuntu 14.04)
[78574.911519] usb 2-1.7: new high-speed USB device number 15 using ehci-pci
[78575.004301] usb 2-1.7: New USB device found, idVendor=1d6b, 
idProduct=0104
[78575.004305] usb 2-1.7: New USB device strings: Mfr=3, Product=4, 
SerialNumber=5
[78575.004307] usb 2-1.7: Product: BeagleBone
[78575.004309] usb 2-1.7: Manufacturer: Circuitco
[78575.004310] usb 2-1.7: SerialNumber: -
[78575.007074] rndis_host 2-1.7:1.0 eth1: register 'rndis_host' at 
usb-:00:1d.0-1.7, RNDIS device, 84:eb:18:ae:cb:aa
[78575.007451] cdc_acm 2-1.7:1.2: This device cannot do calls on its own. 
It is not a modem.
[78575.007474] cdc_acm 2-1.7:1.2: ttyACM0: USB ACM device
[78575.008073] usb-storage 2-1.7:1.4: USB Mass Storage device detected
[78575.008368] scsi24 : usb-storage 2-1.7:1.4
[78576.007089] scsi 24:0:0:0: Direct-Access LinuxFile-Stor Gadget 
0401 PQ: 0 ANSI: 2
[78576.007323] sd 24:0:0:0: Attached scsi generic sg2 type 0
[78576.015073] sd 24:0:0:0: [sdb] 196608 512-byte logical blocks: (100 
MB/96.0 MiB)
[78576.015778] sd 24:0:0:0: [sdb] Write Protect is off
[78576.015782] sd 24:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[78576.016443] sd 24:0:0:0: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
[78576.019831]  sdb:
[78576.023439] sd 24:0:0:0: [sdb] Attached SCSI removable disk

fdalbert@edge ~ $ sudo ifconfig -a

eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa  
  inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:41 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2 errors:522 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:7554 (7.5 KB)  TX bytes:520 (520.0 B)

fdalbert@edge ~ $ sudo dhclient -v eth1
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth1/84:eb:18:ae:cb:aa
Sending on   LPF/eth1/84:eb:18:ae:cb:aa
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 (xid=0xfe901674)
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 (xid=0xfe901674)
.
.
.
nothing

Beaglebone:
root@beaglebone:~# systemd-journalctl | grep usb0
Jan 01 00:00:09 beaglebone udhcpd[629]: is interface usb0 up and 
configured?...e
Mar 01 20:46:05 beaglebone udhcpd[1056]: is interface usb0 up and 
configured...s
Mar 01 20:46:05 beaglebone avahi-daemon[569]: New relevant interface 
usb0.IP
Mar 01 20:46:05 beaglebone avahi-daemon[569]: Interface usb0.IPv4 no longer 

Mar 01 20:46:05 beaglebone avahi-daemon[569]: New relevant interface 
usb0.IP
Mar 01 20:46:06 beaglebone avahi-daemon[569]: New relevant interface 
usb0.IP
Mar 01 20:46:08 beaglebone ntpd[734]: Listen normally on 4 usb0 
192.168.7.2...23
Mar 01 20:46:08 beaglebone ntpd[734]: Listen normally on 5 usb0 
fe80::507b:...23
root@beaglebone:~# dmesg | grep 
usb0
 

[   15.723970] usb0: HOST MAC 84:eb:18:ae:cb:aa
[   15.728147] usb0: MAC 52:7b:9c:b8:2a:20


On Monday, December 7, 2015 at 4:49:45 PM UTC+1, RobertCNelson wrote:
>
>
>
> On Mon, Dec 7, 2015 at 9:22 AM, Fabian Dalbert  > wrote:
>
>> journal as in journalctl? doesn't seem to be included. but here's what I 
>> found in dmesg that seemed relevant:
>>
>
> In wheezy it's systemd-journalctl
>  
>
>>
>>
>> [2.976012] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk 
>>> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
>>> [2.976031] musb-hdrc: MHDRC RTL version 2.0 
>>> [2.976039] musb-hdrc: setup fifo_mode 4
>>> [2.976056] musb-hdrc: 28/31 max ep, 16384/16384 memory
>>> [2.977348] 47401b00.usb-phy supply vcc not found, using dummy 
>>> regulator
>>> [3.005848] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk 
>>> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
>>> [3.005863] musb-hdrc: MHDRC RTL version 2.0 
>>> [3.005871] musb-hdrc: setup fifo_mode 4
>>> [3.005885] musb-hdrc: 28/31 max ep, 16384/16384 memory
>>> [3.006170] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
>>> [3.006461] musb-hdrc musb-hdrc.1.auto: new USB bus registered, 
>>> assigned bus number 1
>>> [3.006690] usb usb1: New USB device found, idVendor=1d6b, 
>>> idProduct=0002
>>> [3.006703] usb usb1: New USB device strings: Mfr=3, Product=2, 
>>> SerialNumber=1
>>> [3.006712] usb usb1: Product: MUSB HDRC host driver
>>> [3.006721] usb usb1: Manufacturer: Linux 4.1.13-bone-rt-r17 musb-hcd
>>> [3.006730] usb usb1: SerialNumber: musb-hdrc.1.auto
>>> [3.007420] hub 1-0:1.0: USB hub found
>>> [3.007470] hub 1-0:1.0: 1 port detected 
>>>
>>  
>>
>>> [   21.101221] using random self ethernet address
>>> [   21.101247] using random host ethernet address

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 9:57 AM, William Hermans  wrote:

> I should also add, that I tested USB read / write speeds a couple years
> ago. Reads were actually slower than NFS, but write were around 20MB/s.
>
> Anyway, we're talking ancient 3.8.x, so perhaps with the newer 4.1.x
> kernels that's been improved ?
>


I don't have a direct apples to apples comparison.

The default eMMC flashers use rsync to copy a 'ro' microSD image to the eMMC

I did implement a usb based, but that boots off of a microSD, mounts the
usb and flashes the eMMC via bmap-tools, however it's a *.xz compressed
image on the usb drive..  Which slows it down.

With Jessie, the current 4gb images take about 18:30-ish, with this change
we are back to 11:30-ish

https://github.com/RobertCNelson/boot-scripts/commit/ff8719e152f4464ffc695af3f820883cea29d543

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

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

2015-12-07 Thread Lee Armstrong

Wow that is a sizeable difference, I will create some new SD cards later to 
speed things up! :-)

On Monday, December 7, 2015 at 4:07:57 PM UTC, RobertCNelson wrote:
>
>
>
> On Mon, Dec 7, 2015 at 9:57 AM, William Hermans  > wrote:
>
>> I should also add, that I tested USB read / write speeds a couple years 
>> ago. Reads were actually slower than NFS, but write were around 20MB/s.
>>
>> Anyway, we're talking ancient 3.8.x, so perhaps with the newer 4.1.x 
>> kernels that's been improved ?
>>
>
>
> I don't have a direct apples to apples comparison.
>
> The default eMMC flashers use rsync to copy a 'ro' microSD image to the 
> eMMC
>
> I did implement a usb based, but that boots off of a microSD, mounts the 
> usb and flashes the eMMC via bmap-tools, however it's a *.xz compressed 
> image on the usb drive..  Which slows it down.
>
> With Jessie, the current 4gb images take about 18:30-ish, with this change 
> we are back to 11:30-ish
>
>
> https://github.com/RobertCNelson/boot-scripts/commit/ff8719e152f4464ffc695af3f820883cea29d543
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Bus Error: Dev/mem Timer4 Beagle Bone Black

2015-12-07 Thread anand2083

I am working on Beagle Bone Black TIMER4. I wanted to access the registers 
directly from user space and so opted for dev/mem. But I end up getting bus 
error when I try to read the contents in a memory address. The code is 
posted below:

#include #include #include #include 
#include#include#include 
#define TIMER4_START_addr 0x48044000#define TIDR 0x00#define TIOCP_CFG 0x10
int main(){
   unsigned int reg;

   char *timer_addr = NULL;

   printf("\n Start Pgm");

int mem, integer;

if ((mem = open ("/dev/mem", O_RDWR | O_SYNC)) < 0)
{
printf("Cannot open /dev/mem\n");

return 1;
}

printf("Opened /dev/mem\n");

timer_addr = mmap(0, 4096, PROT_READ | PROT_WRITE, MAP_SHARED, mem, 
TIMER4_START_addr);

printf("GPIO mapped to %p\n", timer_addr);

reg =  *((int*) timer_addr);

printf("GPIO1 configuration: %x\n", reg);

return 0;}

The output that I get is :
Start 
PgmOpened /dev/mem 
GPIO mapped to 0xb6fb7000 
Bus error 


Please let me know how to overcome this problem.

Regards Anand



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

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

2015-12-07 Thread William Hermans

I should also add, that I tested USB read / write speeds a couple years
ago. Reads were actually slower than NFS, but write were around 20MB/s.

Anyway, we're talking ancient 3.8.x, so perhaps with the newer 4.1.x
kernels that's been improved ?

On Mon, Dec 7, 2015 at 8:55 AM, Lee Armstrong  wrote:

> Yeah thanks William, I was hoping there was a serial method but thinking
> that through I think it would be slower than an SD card!
>
>
> On Mon, Dec 7, 2015 at 3:53 PM, William Hermans  wrote:
>
>> One other option not mentioned. Which is "burning" from USB.
>>
>> Pretty much, all methods requires an sdcard, period. So, just using a
>> large sdcard, with a small boot / rootfs, and a larger partition mounted,
>> where every with all the data needed to be "burned" to eMMC. Thats all
>> that's needed.
>>
>> So the data partition can be anything, then it's just a matter of
>> mounting that media, and using it exactly how an sdcard would be used in
>> it's stead. network mount, sdcard, USB media, whatever. It all the same at
>> this point.
>>
>> I do recall something about "serial boot", but meh that sounds like a
>> huge hassle . . . but also note that an NFS mount will be slower than both
>> USB, or using the sdcard directly. In fact, for reads, I do not think
>> anything will be faster than sdcard . . . in this context.
>>
>> On Mon, Dec 7, 2015 at 8:46 AM, Lee Armstrong  wrote:
>>
>>> Thanks for all of your experiences.  Interesting you use the SD in
>>> production.  That is similar to what I am doing now.
>>>
>>> Günter, that is much quicker than the 5 minutes I have it down to at the
>>> moment so may invest some time in that process.
>>>
>>> Lee
>>>
>>>
>>> On Monday, December 7, 2015 at 2:56:56 PM UTC, dl4mea wrote:

 Hello Lee,

 my process is that I have a running Linux on a bootable SD card.
 As a autostart service, there is a scripted executed, which performs

 1) partitioning of the eMMC card
 2) copy u-boot.bin and MLO to the first sectors of the eMMC
 3) format the 1st (and only) partition with ext4 file system
 4) unzip/untar a master tar.gz from the boot media to the data partition
 5) patch the extracted uEnv.txt with the actual UUID of the partition
 on eMMC
 6) initiate regeneration of ssh host keys (touch
 /etc/ssh/ssh.regenerate)
 7) sync
 8) power off

 That takes about 1min to flash one Beaglebone. It takes somewhat longer
 if the BBB is not connected to a network, because then it needs a network
 timeout to proceed

 cheers, Günter (dl4mea)



 --
>>> 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.
>>> 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 a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/n6a7J_Tby4w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

2015-12-07 Thread Lee Armstrong

Yeah thanks William, I was hoping there was a serial method but thinking that 
through I think it would be slower than an SD card!

On Mon, Dec 7, 2015 at 3:53 PM, William Hermans  wrote:

> One other option not mentioned. Which is "burning" from USB.
> Pretty much, all methods requires an sdcard, period. So, just using a large
> sdcard, with a small boot / rootfs, and a larger partition mounted, where
> every with all the data needed to be "burned" to eMMC. Thats all that's
> needed.
> So the data partition can be anything, then it's just a matter of mounting
> that media, and using it exactly how an sdcard would be used in it's stead.
> network mount, sdcard, USB media, whatever. It all the same at this point.
> I do recall something about "serial boot", but meh that sounds like a huge
> hassle . . . but also note that an NFS mount will be slower than both USB,
> or using the sdcard directly. In fact, for reads, I do not think anything
> will be faster than sdcard . . . in this context.
> On Mon, Dec 7, 2015 at 8:46 AM, Lee Armstrong  wrote:
>> Thanks for all of your experiences.  Interesting you use the SD in
>> production.  That is similar to what I am doing now.
>>
>> Günter, that is much quicker than the 5 minutes I have it down to at the
>> moment so may invest some time in that process.
>>
>> Lee
>>
>>
>> On Monday, December 7, 2015 at 2:56:56 PM UTC, dl4mea wrote:
>>>
>>> Hello Lee,
>>>
>>> my process is that I have a running Linux on a bootable SD card.
>>> As a autostart service, there is a scripted executed, which performs
>>>
>>> 1) partitioning of the eMMC card
>>> 2) copy u-boot.bin and MLO to the first sectors of the eMMC
>>> 3) format the 1st (and only) partition with ext4 file system
>>> 4) unzip/untar a master tar.gz from the boot media to the data partition
>>> 5) patch the extracted uEnv.txt with the actual UUID of the partition on
>>> eMMC
>>> 6) initiate regeneration of ssh host keys (touch /etc/ssh/ssh.regenerate)
>>> 7) sync
>>> 8) power off
>>>
>>> That takes about 1min to flash one Beaglebone. It takes somewhat longer
>>> if the BBB is not connected to a network, because then it needs a network
>>> timeout to proceed
>>>
>>> cheers, Günter (dl4mea)
>>>
>>>
>>>
>>> --
>> 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.
>> 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 a topic in the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/beagleboard/n6a7J_Tby4w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

2015-12-07 Thread William Hermans

One other option not mentioned. Which is "burning" from USB.

Pretty much, all methods requires an sdcard, period. So, just using a large
sdcard, with a small boot / rootfs, and a larger partition mounted, where
every with all the data needed to be "burned" to eMMC. Thats all that's
needed.

So the data partition can be anything, then it's just a matter of mounting
that media, and using it exactly how an sdcard would be used in it's stead.
network mount, sdcard, USB media, whatever. It all the same at this point.

I do recall something about "serial boot", but meh that sounds like a huge
hassle . . . but also note that an NFS mount will be slower than both USB,
or using the sdcard directly. In fact, for reads, I do not think anything
will be faster than sdcard . . . in this context.

On Mon, Dec 7, 2015 at 8:46 AM, Lee Armstrong  wrote:

> Thanks for all of your experiences.  Interesting you use the SD in
> production.  That is similar to what I am doing now.
>
> Günter, that is much quicker than the 5 minutes I have it down to at the
> moment so may invest some time in that process.
>
> Lee
>
>
> On Monday, December 7, 2015 at 2:56:56 PM UTC, dl4mea wrote:
>>
>> Hello Lee,
>>
>> my process is that I have a running Linux on a bootable SD card.
>> As a autostart service, there is a scripted executed, which performs
>>
>> 1) partitioning of the eMMC card
>> 2) copy u-boot.bin and MLO to the first sectors of the eMMC
>> 3) format the 1st (and only) partition with ext4 file system
>> 4) unzip/untar a master tar.gz from the boot media to the data partition
>> 5) patch the extracted uEnv.txt with the actual UUID of the partition on
>> eMMC
>> 6) initiate regeneration of ssh host keys (touch /etc/ssh/ssh.regenerate)
>> 7) sync
>> 8) power off
>>
>> That takes about 1min to flash one Beaglebone. It takes somewhat longer
>> if the BBB is not connected to a network, because then it needs a network
>> timeout to proceed
>>
>> cheers, Günter (dl4mea)
>>
>>
>>
>> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 9:22 AM, Fabian Dalbert  wrote:

> journal as in journalctl? doesn't seem to be included. but here's what I
> found in dmesg that seemed relevant:
>

In wheezy it's systemd-journalctl


>
>
> [2.976012] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk
>> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
>> [2.976031] musb-hdrc: MHDRC RTL version 2.0
>> [2.976039] musb-hdrc: setup fifo_mode 4
>> [2.976056] musb-hdrc: 28/31 max ep, 16384/16384 memory
>> [2.977348] 47401b00.usb-phy supply vcc not found, using dummy
>> regulator
>> [3.005848] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk
>> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
>> [3.005863] musb-hdrc: MHDRC RTL version 2.0
>> [3.005871] musb-hdrc: setup fifo_mode 4
>> [3.005885] musb-hdrc: 28/31 max ep, 16384/16384 memory
>> [3.006170] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
>> [3.006461] musb-hdrc musb-hdrc.1.auto: new USB bus registered,
>> assigned bus number 1
>> [3.006690] usb usb1: New USB device found, idVendor=1d6b,
>> idProduct=0002
>> [3.006703] usb usb1: New USB device strings: Mfr=3, Product=2,
>> SerialNumber=1
>> [3.006712] usb usb1: Product: MUSB HDRC host driver
>> [3.006721] usb usb1: Manufacturer: Linux 4.1.13-bone-rt-r17 musb-hcd
>> [3.006730] usb usb1: SerialNumber: musb-hdrc.1.auto
>> [3.007420] hub 1-0:1.0: USB hub found
>> [3.007470] hub 1-0:1.0: 1 port detected
>>
>
>
>> [   21.101221] using random self ethernet address
>> [   21.101247] using random host ethernet address
>> [   21.101265] using host ethernet address: 84:EB:18:AE:CB:AA
>> [   21.160643] Mass Storage Function, version: 2009/09/11
>> [   21.160672] LUN: removable file: (no medium)
>> [   21.160867] LUN: removable file: /dev/mmcblk0p1
>> [   21.160878] Number of LUNs=1
>> [   21.162626] usb0: HOST MAC 84:eb:18:ae:cb:aa
>> [   21.162973] usb0: MAC a2:29:c5:ee:bf:e6
>> [   21.163029] Number of LUNs=1
>> [   21.166695] g_multi gadget: Multifunction Composite Gadget
>> [   21.166721] g_multi gadget: g_multi ready
>> [   21.767642] g_multi gadget: high-speed config #1: Multifunction with
>> RNDIS
>> [   33.184926] net eth0: initializing cpsw version 1.12 (0)
>> [   33.187423] net eth0: phy found : id is : 0x7c0f1
>> [   33.187492] libphy: PHY 4a101000.mdio:01 not found
>> [   33.192436] net eth0: phy 4a101000.mdio:01 not found on slave 1
>> [   33.218457] net eth0: BQL enabled
>> [   33.228304] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [  132.378851] device usb0 entered promiscuous mode
>> [  153.177973] device usb0 left promiscuous mode
>> [ 1555.067418] device usb0 entered promiscuous mode
>> [ 1570.862790] device usb0 left promiscuous mode
>>
>

Here's what you should see:

Host:
[ 4310.886819] usb 5-1.4: new high-speed USB device number 5 using xhci_hcd
[ 4310.977656] usb 5-1.4: New USB device found, idVendor=1d6b,
idProduct=0104
[ 4310.977663] usb 5-1.4: New USB device strings: Mfr=3, Product=4,
SerialNumber=5
[ 4310.977667] usb 5-1.4: Product: BeagleBoneBlack
[ 4310.977670] usb 5-1.4: Manufacturer: Circuitco
[ 4310.977673] usb 5-1.4: SerialNumber: -BBG115081143
[ 4310.982450] usb-storage 5-1.4:1.4: USB Mass Storage device detected
[ 4310.982579] scsi host11: usb-storage 5-1.4:1.4
[ 4311.003239] cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device
[ 4311.003873] usbcore: registered new interface driver cdc_acm
[ 4311.003874] cdc_acm: USB Abstract Control Model driver for USB modems
and ISDN adapters
[ 4311.008181] usbcore: registered new interface driver cdc_ether
[ 4311.012262] cfg80211: World regulatory domain updated:
[ 4311.012266] cfg80211:  DFS Master region: unset
[ 4311.012268] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 4311.012270] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A,
2000 mBm), (N/A)
[ 4311.012272] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A,
2000 mBm), (N/A)
[ 4311.012274] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A,
2000 mBm), (N/A)
[ 4311.012276] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16
KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 4311.012278] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16
KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 4311.012280] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A,
2000 mBm), (0 s)
[ 4311.012281] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A,
2000 mBm), (N/A)
[ 4311.012283] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz),
(N/A, 0 mBm), (N/A)
[ 4311.013968] rndis_host 5-1.4:1.0 eth0: register 'rndis_host' at
usb-:00:10.1-1.4, RNDIS device, 84:eb:18:af:f5:e8
[ 4311.014010] usbcore: registered new interface driver rndis_host
[ 4311.015133] usbcore: registered new interface driver rndis_wlan
[ 4311.019341] rndis_host 5-1.4:1.0 enx84eb18aff5e8: renamed from eth0
[ 4311.052121] IPv6: ADDRCONF(NETDEV_UP): enx84eb18aff5e8: link is not ready
[ 4311.982606] scsi 11

[beagleboard] Re: Bulk flashing of BBB eMMC

2015-12-07 Thread Lee Armstrong

Thanks for all of your experiences.  Interesting you use the SD in 
production.  That is similar to what I am doing now.

Günter, that is much quicker than the 5 minutes I have it down to at the 
moment so may invest some time in that process.

Lee

On Monday, December 7, 2015 at 2:56:56 PM UTC, dl4mea wrote:
>
> Hello Lee,
>
> my process is that I have a running Linux on a bootable SD card.
> As a autostart service, there is a scripted executed, which performs
>
> 1) partitioning of the eMMC card
> 2) copy u-boot.bin and MLO to the first sectors of the eMMC 
> 3) format the 1st (and only) partition with ext4 file system
> 4) unzip/untar a master tar.gz from the boot media to the data partition
> 5) patch the extracted uEnv.txt with the actual UUID of the partition on 
> eMMC
> 6) initiate regeneration of ssh host keys (touch /etc/ssh/ssh.regenerate)
> 7) sync
> 8) power off
>
> That takes about 1min to flash one Beaglebone. It takes somewhat longer if 
> the BBB is not connected to a network, because then it needs a network 
> timeout to proceed
>
> cheers, Günter (dl4mea)
>
>
>
>

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

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread William Hermans

It always just worked for me. g_ether that is. Of course, I do not use
systemd . . . no idea if systemd requires any special voodoo to get g_ether
working, or not.

One thing to note though Fabian. You can use ./build_deb next time you
build a new kernel, copy the deb over, and just *sudo dpkg -i
linux-image*.deb*.

I only mention that in case you were unaware of that. . . but this way has
the added benefit of being easier, and installing everything you need. Once
you get a base rootfs running. It'll work on all the base images too, of
course.

On Mon, Dec 7, 2015 at 8:22 AM, Fabian Dalbert  wrote:

> journal as in journalctl? doesn't seem to be included. but here's what I
> found in dmesg that seemed relevant:
>
>
> [2.976012] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk
>> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
>> [2.976031] musb-hdrc: MHDRC RTL version 2.0
>> [2.976039] musb-hdrc: setup fifo_mode 4
>> [2.976056] musb-hdrc: 28/31 max ep, 16384/16384 memory
>> [2.977348] 47401b00.usb-phy supply vcc not found, using dummy
>> regulator
>> [3.005848] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk
>> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
>> [3.005863] musb-hdrc: MHDRC RTL version 2.0
>> [3.005871] musb-hdrc: setup fifo_mode 4
>> [3.005885] musb-hdrc: 28/31 max ep, 16384/16384 memory
>> [3.006170] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
>> [3.006461] musb-hdrc musb-hdrc.1.auto: new USB bus registered,
>> assigned bus number 1
>> [3.006690] usb usb1: New USB device found, idVendor=1d6b,
>> idProduct=0002
>> [3.006703] usb usb1: New USB device strings: Mfr=3, Product=2,
>> SerialNumber=1
>> [3.006712] usb usb1: Product: MUSB HDRC host driver
>> [3.006721] usb usb1: Manufacturer: Linux 4.1.13-bone-rt-r17 musb-hcd
>> [3.006730] usb usb1: SerialNumber: musb-hdrc.1.auto
>> [3.007420] hub 1-0:1.0: USB hub found
>> [3.007470] hub 1-0:1.0: 1 port detected
>>
>
>
>> [   21.101221] using random self ethernet address
>> [   21.101247] using random host ethernet address
>> [   21.101265] using host ethernet address: 84:EB:18:AE:CB:AA
>> [   21.160643] Mass Storage Function, version: 2009/09/11
>> [   21.160672] LUN: removable file: (no medium)
>> [   21.160867] LUN: removable file: /dev/mmcblk0p1
>> [   21.160878] Number of LUNs=1
>> [   21.162626] usb0: HOST MAC 84:eb:18:ae:cb:aa
>> [   21.162973] usb0: MAC a2:29:c5:ee:bf:e6
>> [   21.163029] Number of LUNs=1
>> [   21.166695] g_multi gadget: Multifunction Composite Gadget
>> [   21.166721] g_multi gadget: g_multi ready
>> [   21.767642] g_multi gadget: high-speed config #1: Multifunction with
>> RNDIS
>> [   33.184926] net eth0: initializing cpsw version 1.12 (0)
>> [   33.187423] net eth0: phy found : id is : 0x7c0f1
>> [   33.187492] libphy: PHY 4a101000.mdio:01 not found
>> [   33.192436] net eth0: phy 4a101000.mdio:01 not found on slave 1
>> [   33.218457] net eth0: BQL enabled
>> [   33.228304] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [  132.378851] device usb0 entered promiscuous mode
>> [  153.177973] device usb0 left promiscuous mode
>> [ 1555.067418] device usb0 entered promiscuous mode
>> [ 1570.862790] device usb0 left promiscuous mode
>>
>
> On Monday, December 7, 2015 at 4:05:37 PM UTC+1, RobertCNelson wrote:
>>
>> Sorry missed the "bone"
>>
>> r17 has that fix too:
>>
>>
>> https://github.com/RobertCNelson/bb-kernel/blob/am33x-rt-v4.1/patches/defconfig#L4305
>>
>> Now i'm not sure..
>>
>> What shows up on the beagle's journal?
>>
>> On Mon, Dec 7, 2015 at 9:03 AM, Fabian Dalbert  wrote:
>>
>>> I actually thought, it were a problem with g_ether and spent hours
>>> trying to fix that. However as I used Robert Nelsons patches, everything
>>> was fine there. I'll try the updated kernel.
>>>
>>> On Monday, December 7, 2015 at 3:36:23 PM UTC+1, William Hermans wrote:

 Have you loaded the g_ether kernel module on the beaglebone ? When
 building your own kernel, this is something you have to take care of
 yourself .

 On Mon, Dec 7, 2015 at 7:21 AM, Fabian Dalbert 
 wrote:

> Hi
>
> I'm trying to write a module for a real-time kernel. Following the
> instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black,
> I compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a
> Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.
>
> Before, with kernel 3.8.13-bone70, everything was working perfectly
> fine. However after upgrading the kernel, my desktop (running Linux Mint)
> no longer receives an ip address.
>
> ifconfig beaglebone:
>
> usb0  Link encap:Ethernet  HWaddr a2:29:c5:ee:bf:e6
>>   inet addr:192.168.7.2  Bcast:192.168.7.3
>> Mask:255.255.255.252
>>   inet6 addr: fe80::a029:c5ff:feee:bfe6/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>

Re: [beagleboard] Re: X11VNC fighting me tooth and nail. Would really appreciate some help.

2015-12-07 Thread William Hermans

$ dmesg | tail

On Mon, Dec 7, 2015 at 8:36 AM, Bill Dussault 
wrote:

> How do I get into the logfile? I did not know about that
> Thanks
>
>
> On Sunday, December 6, 2015 at 7:29:06 PM UTC-6, Bill Dussault wrote:
>>
>> Greetings,
>>
>> I am trying to install X11VNC and log into it via my laptop and I am
>> having some tough luck
>>
>> Here is what I have done..
>>
>> I have changed my IP address to a 192.168.1.XX
>> My router for some reason still thinks it is the old IP address even when
>> I refresh it.
>>
>> I have turned on VNC on the firewall  on my 2wire router
>>
>> Next I installed VNC:
>>
>>- Debian:   sudo apt-get install x11vnc
>>
>> 3. Enter the below command
>>
>>
>>
>> -Debian:
>>
>> x11vnc -bg -o %HOME/.x11vnc.log.%VNCDISPLAY -auth
>> /var/run/lightdm/root/:0 -forever
>>
>>
>> (I'm not sure if I turned it on)
>>
>>
>> I can ping the beaglebone from my computer
>>
>>
>> C:\Users\William>ping 192.168.1.XX
>>
>>
>> Pinging 192.168.1.XX with 32 bytes of data:
>>
>> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64
>>
>> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64
>>
>> Reply from 192.168.1.XX: bytes=32 time=5ms TTL=64
>>
>> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64
>>
>>
>> Ping statistics for 192.168.1.XX:
>>
>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>>
>> Approximate round trip times in milli-seconds:
>>
>> Minimum = 3ms, Maximum = 5ms, Average = 3ms
>>
>>
>> So I can See it.
>>
>>
>> I start  tightVNC on my laptop
>>
>>
>> 192.168.1.XX:5901
>>
>>
>> I get connection has been gracefully closed.  Or  Connection
>> was actively Refused...
>>
>>
>> X11VNC has a few configurations when opened on the desktop I am
>> unfamiliar with. No passwords in use as of yet (I was warned when I started)
>>
>>
>> Does anyone see anything out of whack?
>>
>>
>> Thanks!
>>
>>
>> Bill
>>
>>
>> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: Private message regarding: [beagleboard] BBB Data Aggregation Unit using external ADC

2015-12-07 Thread William Hermans

Chelsea,

Basically, you have access to any libc library function, and any library
function you care to import personally. So, for the most part. You can get
a good book on Linux programming, and just follow along.

One thing I'm personally unclear on, is that if these libc headers are
already installed as base, or through the *build-essential* package. I
could probably find out, but never bothered because in order to write C /
C++ code you should install that package anyway. As it installs the GNU
Compiler Collection, and everything else needed to get started with C/C++
development.

Python, I could not say exactly, but I'm fairly certain it's roughly the
same. Just *apt-get install *

On Mon, Dec 7, 2015 at 8:01 AM, Chelsea Orefice  wrote:

> Hi John,
>
> These are very helpful links. I was wondering if there was an online
> document on all functions that I can code BBB in either in C, C++, python,
> etc.
>
> Thanks,
> Chelsea
>
> On Thu, Dec 3, 2015 at 11:12 PM, John Syne  wrote:
>
>> Hi Chelsea,
>>
>> Here are some reference I have found helpful:
>>
>>
>> http://www.analog.com/library/analogdialogue/archives/39-05/op_amp_applications_handbook.html
>>
>> http://www.analog.com/library/analogDialogue/archives/39-06/data_conversion_handbook.html
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Dec 3, 2015, at 5:57 PM, Chelsea Orefice  wrote:
>>
>> Hi John,
>>
>> Just wanted to say thank you for really helping me with this. It has been
>> a struggle for me and my team to get help from different resources at
>> school as well as our liaisons where we are getting our design requirements
>> from. (This is our senior engineering project.)
>>
>> I am having still a little difficulty in understanding how the circuitry
>> I shared with you may give me a single input instead of differential that
>> the ADC requires.I attached the actual design of the system, so if you
>> could help me understand how it won't work it'd be much appreciated.
>>
>> Also, may you tell me your background in relation to all of this? You are
>> very knowledgeable in this area, and when I relay some of this information
>> to my team I would like to share from whom I received this information
>> from.
>>
>>
>> Sincerely,
>> Chelsea
>>
>> On Thu, Dec 3, 2015 at 7:01 PM, John Syne  wrote:
>>
>>> Hi Chelsea,
>>>
>>> I have cc beagleboard because someone else might learn from this
>>> discussion. Looking at the link you provided, it won’t work because ADS1278
>>> requires a differential input. Look at page 39 for circuits that will work
>>> for you.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>>
>>> On Dec 3, 2015, at 3:52 PM, Chelsea Orefice  wrote:
>>>
>>> My apologies. Please let me know if this link works. (You will need to
>>> just copy and paste in search bar). If that doesn't work I will send it as
>>> an attachment. Will also look at the diagram as well.
>>>
>>> http://cnx.org/resources/72628d36f0c24bc80ff94e5c0bf6df2b27a
>>> 86751/opamp4.png
>>>
>>> Thanks again,
>>> Chelsea
>>>
>>> On Thursday, December 3, 2015 at 6:46:49 PM UTC-5, john3909 wrote:

 Look at page 39 for a suitable input circuit.

 Regards,
 John




 On Dec 3, 2015, at 3:03 PM, Chelsea Orefice  wrote:

 Hi John,

 Thanks for getting back to me. I was actually looking at that same ADC
 converter as you posted in your reply. Just looking for some clarification
 on a few things. What type of error would a simple resistor divider
 introduce into the system? I am currently using a cascaded inverting
 op amp system. Not really sure if this will scale the input voltage to a
 level that is compatible with my ADC.

 The circuit diagram looks like this:
 [image: Inline image 1]

 Looking forward to your reply,
 Chels

 On Thursday, December 3, 2015 at 5:07:41 PM UTC-5, Chelsea Orefice
 wrote:
>
> Hi everyone,
>
> I am new to the world of using MCUs and am looking for some assistance
> on a project that I am currently working on. To sum things up quickly, I 
> am
> building a data aggregation unit that can convert analog voltage readings
> to digital values that is to be stored on a USB or SD card. The DAU will
> collect 3 types of signals, a buffer signal, clipped signal, and a signal
> passed through a LPF. In the end, the data should be stored as either a
> MatLab file or .xml file. However, I am facing a few road blocks relating
> to my design.
>
> 1.) I need to use a 24 bit ADC for high resolution purposes based on
> design requirements that were just given to me as I will be collecting 
> data
> from .1mV to 50V and it has to have a high sample speed rate. Has anyone
> connected an external ADC to the BBB? If so, what was the brand of your
> external ADC? How did you connect the ADC to the BBB? (It'd be greatly
> appreciated to be able to see a design).
>
> 2.) If you have had a similar proj

[beagleboard] Re: X11VNC fighting me tooth and nail. Would really appreciate some help.

2015-12-07 Thread Bill Dussault

How do I get into the logfile? I did not know about that
Thanks 


On Sunday, December 6, 2015 at 7:29:06 PM UTC-6, Bill Dussault wrote:
>
> Greetings,
>
> I am trying to install X11VNC and log into it via my laptop and I am 
> having some tough luck 
>
> Here is what I have done..
>
> I have changed my IP address to a 192.168.1.XX
> My router for some reason still thinks it is the old IP address even when 
> I refresh it. 
>
> I have turned on VNC on the firewall  on my 2wire router
>
> Next I installed VNC: 
>
>- Debian:   sudo apt-get install x11vnc
>
> 3. Enter the below command
>
>  
>
> -Debian:
>
> x11vnc -bg -o %HOME/.x11vnc.log.%VNCDISPLAY -auth 
> /var/run/lightdm/root/:0 -forever
>
>
> (I'm not sure if I turned it on)
>
>
> I can ping the beaglebone from my computer
>
>
> C:\Users\William>ping 192.168.1.XX
>
>
> Pinging 192.168.1.XX with 32 bytes of data:
>
> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64
>
> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64
>
> Reply from 192.168.1.XX: bytes=32 time=5ms TTL=64
>
> Reply from 192.168.1.XX: bytes=32 time=3ms TTL=64
>
>
> Ping statistics for 192.168.1.XX:
>
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>
> Approximate round trip times in milli-seconds:
>
> Minimum = 3ms, Maximum = 5ms, Average = 3ms
>
>
> So I can See it. 
>
>
> I start  tightVNC on my laptop
>
>
> 192.168.1.XX:5901  
>
>
> I get connection has been gracefully closed.  Or  Connection 
> was actively Refused...
>
>
> X11VNC has a few configurations when opened on the desktop I am unfamiliar 
> with. No passwords in use as of yet (I was warned when I started)
>
>
> Does anyone see anything out of whack?
>
>
> Thanks! 
>
>
> Bill
>
>
>

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

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

journal as in journalctl? doesn't seem to be included. but here's what I 
found in dmesg that seemed relevant:


[2.976012] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, 
> bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
> [2.976031] musb-hdrc: MHDRC RTL version 2.0 
> [2.976039] musb-hdrc: setup fifo_mode 4
> [2.976056] musb-hdrc: 28/31 max ep, 16384/16384 memory
> [2.977348] 47401b00.usb-phy supply vcc not found, using dummy regulator
> [3.005848] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk 
> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftCo)
> [3.005863] musb-hdrc: MHDRC RTL version 2.0 
> [3.005871] musb-hdrc: setup fifo_mode 4
> [3.005885] musb-hdrc: 28/31 max ep, 16384/16384 memory
> [3.006170] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
> [3.006461] musb-hdrc musb-hdrc.1.auto: new USB bus registered, 
> assigned bus number 1
> [3.006690] usb usb1: New USB device found, idVendor=1d6b, 
> idProduct=0002
> [3.006703] usb usb1: New USB device strings: Mfr=3, Product=2, 
> SerialNumber=1
> [3.006712] usb usb1: Product: MUSB HDRC host driver
> [3.006721] usb usb1: Manufacturer: Linux 4.1.13-bone-rt-r17 musb-hcd
> [3.006730] usb usb1: SerialNumber: musb-hdrc.1.auto
> [3.007420] hub 1-0:1.0: USB hub found
> [3.007470] hub 1-0:1.0: 1 port detected 
>
 

> [   21.101221] using random self ethernet address
> [   21.101247] using random host ethernet address
> [   21.101265] using host ethernet address: 84:EB:18:AE:CB:AA
> [   21.160643] Mass Storage Function, version: 2009/09/11
> [   21.160672] LUN: removable file: (no medium)
> [   21.160867] LUN: removable file: /dev/mmcblk0p1
> [   21.160878] Number of LUNs=1
> [   21.162626] usb0: HOST MAC 84:eb:18:ae:cb:aa
> [   21.162973] usb0: MAC a2:29:c5:ee:bf:e6
> [   21.163029] Number of LUNs=1
> [   21.166695] g_multi gadget: Multifunction Composite Gadget
> [   21.166721] g_multi gadget: g_multi ready
> [   21.767642] g_multi gadget: high-speed config #1: Multifunction with 
> RNDIS
> [   33.184926] net eth0: initializing cpsw version 1.12 (0)
> [   33.187423] net eth0: phy found : id is : 0x7c0f1
> [   33.187492] libphy: PHY 4a101000.mdio:01 not found
> [   33.192436] net eth0: phy 4a101000.mdio:01 not found on slave 1
> [   33.218457] net eth0: BQL enabled
> [   33.228304] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [  132.378851] device usb0 entered promiscuous mode
> [  153.177973] device usb0 left promiscuous mode
> [ 1555.067418] device usb0 entered promiscuous mode
> [ 1570.862790] device usb0 left promiscuous mode
>

On Monday, December 7, 2015 at 4:05:37 PM UTC+1, RobertCNelson wrote:
>
> Sorry missed the "bone"
>
> r17 has that fix too:
>
>
> https://github.com/RobertCNelson/bb-kernel/blob/am33x-rt-v4.1/patches/defconfig#L4305
>
> Now i'm not sure..
>
> What shows up on the beagle's journal?
>
> On Mon, Dec 7, 2015 at 9:03 AM, Fabian Dalbert  > wrote:
>
>> I actually thought, it were a problem with g_ether and spent hours trying 
>> to fix that. However as I used Robert Nelsons patches, everything was fine 
>> there. I'll try the updated kernel.
>>
>> On Monday, December 7, 2015 at 3:36:23 PM UTC+1, William Hermans wrote:
>>>
>>> Have you loaded the g_ether kernel module on the beaglebone ? When 
>>> building your own kernel, this is something you have to take care of 
>>> yourself . 
>>>
>>> On Mon, Dec 7, 2015 at 7:21 AM, Fabian Dalbert  wrote:
>>>
 Hi

 I'm trying to write a module for a real-time kernel. Following the 
 instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, 
 I compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a 
 Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.

 Before, with kernel 3.8.13-bone70, everything was working perfectly 
 fine. However after upgrading the kernel, my desktop (running Linux Mint) 
 no longer receives an ip address.

 ifconfig beaglebone:

 usb0  Link encap:Ethernet  HWaddr a2:29:c5:ee:bf:e6  
>   inet addr:192.168.7.2  Bcast:192.168.7.3  
> Mask:255.255.255.252
>   inet6 addr: fe80::a029:c5ff:feee:bfe6/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:76 (76.0 B)  TX bytes:9408 (9.1 KiB)
>

 ifconfig desktop:

  eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa  
>   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:37 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:7262 (7.2 KB

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Robert Nelson

Sorry missed the "bone"

r17 has that fix too:

https://github.com/RobertCNelson/bb-kernel/blob/am33x-rt-v4.1/patches/defconfig#L4305

Now i'm not sure..

What shows up on the beagle's journal?

On Mon, Dec 7, 2015 at 9:03 AM, Fabian Dalbert  wrote:

> I actually thought, it were a problem with g_ether and spent hours trying
> to fix that. However as I used Robert Nelsons patches, everything was fine
> there. I'll try the updated kernel.
>
> On Monday, December 7, 2015 at 3:36:23 PM UTC+1, William Hermans wrote:
>>
>> Have you loaded the g_ether kernel module on the beaglebone ? When
>> building your own kernel, this is something you have to take care of
>> yourself .
>>
>> On Mon, Dec 7, 2015 at 7:21 AM, Fabian Dalbert  wrote:
>>
>>> Hi
>>>
>>> I'm trying to write a module for a real-time kernel. Following the
>>> instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black,
>>> I compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a
>>> Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.
>>>
>>> Before, with kernel 3.8.13-bone70, everything was working perfectly
>>> fine. However after upgrading the kernel, my desktop (running Linux Mint)
>>> no longer receives an ip address.
>>>
>>> ifconfig beaglebone:
>>>
>>> usb0  Link encap:Ethernet  HWaddr a2:29:c5:ee:bf:e6
   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
   inet6 addr: fe80::a029:c5ff:feee:bfe6/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
   TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:76 (76.0 B)  TX bytes:9408 (9.1 KiB)

>>>
>>> ifconfig desktop:
>>>
>>>  eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa
   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:37 errors:0 dropped:0 overruns:0 frame:0
   TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:7262 (7.2 KB)  TX bytes:268 (268.0 B)

>>>
>>> manually assigning an ip does not do the trick. When pinging the desktop
>>> from the beaglebone (with or without manually assigning an ip), i can catch
>>> the requests using tcpdump. The beaglebone does however not receive
>>> anything, no answers to pings, nothing showing up in tcpdump.
>>>
>>> fdalbert@edge ~ $ sudo tcpdump -i eth1
 tcpdump: WARNING: eth1: no IPv4 address assigned
 tcpdump: verbose output suppressed, use -v or -vv for full protocol
 decode
 listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
 15:01:10.597986 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:11.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:12.588895 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:13.597976 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:14.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:15.588772 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:16.597983 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:17.588936 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 15:01:18.588919 ARP, Request who-has 192.168.7.1 tell 192.168.7.2,
 length 28
 ^C
 9 packets captured
 9 packets received by filter
 0 packets dropped by kernel

>>>
>>>  root@beaglebone:~# ping 192.168.7.1
 PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
 From 192.168.7.2 icmp_seq=1 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=2 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=3 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=4 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=5 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=6 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=7 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=8 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=9 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=10 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=11 Destination Host Unreachable
 From 192.168.7.2 icmp_seq=12 Destination Host Unreachable
 ^C
 --- 192.168.7.1 ping statistics ---
 14 packets transmitted, 0 received, +12 errors, 100% packet loss, time
 13001ms
 pipe 3
 root@beaglebone:~# tcpdump -i usb0
 tcpdump: verbose output suppressed, use -v or -vv for full protocol
 decode
 listening on usb0, link-type EN10MB (Ethernet), capture size 65535 bytes
 ^C
 0 packets captured
 0 packets received by filter
 0 packets dropped by ker

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

I actually thought, it were a problem with g_ether and spent hours trying 
to fix that. However as I used Robert Nelsons patches, everything was fine 
there. I'll try the updated kernel.

On Monday, December 7, 2015 at 3:36:23 PM UTC+1, William Hermans wrote:
>
> Have you loaded the g_ether kernel module on the beaglebone ? When 
> building your own kernel, this is something you have to take care of 
> yourself . 
>
> On Mon, Dec 7, 2015 at 7:21 AM, Fabian Dalbert  > wrote:
>
>> Hi
>>
>> I'm trying to write a module for a real-time kernel. Following the 
>> instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, 
>> I compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a 
>> Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.
>>
>> Before, with kernel 3.8.13-bone70, everything was working perfectly fine. 
>> However after upgrading the kernel, my desktop (running Linux Mint) no 
>> longer receives an ip address.
>>
>> ifconfig beaglebone:
>>
>> usb0  Link encap:Ethernet  HWaddr a2:29:c5:ee:bf:e6  
>>>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>>>   inet6 addr: fe80::a029:c5ff:feee:bfe6/64 Scope:Link
>>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>>>   TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
>>>   collisions:0 txqueuelen:1000 
>>>   RX bytes:76 (76.0 B)  TX bytes:9408 (9.1 KiB)
>>>
>>
>> ifconfig desktop:
>>
>>  eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa  
>>>   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
>>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>   RX packets:37 errors:0 dropped:0 overruns:0 frame:0
>>>   TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>>>   collisions:0 txqueuelen:1000 
>>>   RX bytes:7262 (7.2 KB)  TX bytes:268 (268.0 B)
>>>
>>
>> manually assigning an ip does not do the trick. When pinging the desktop 
>> from the beaglebone (with or without manually assigning an ip), i can catch 
>> the requests using tcpdump. The beaglebone does however not receive 
>> anything, no answers to pings, nothing showing up in tcpdump.
>>
>> fdalbert@edge ~ $ sudo tcpdump -i eth1
>>> tcpdump: WARNING: eth1: no IPv4 address assigned
>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol 
>>> decode
>>> listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
>>> 15:01:10.597986 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:11.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:12.588895 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:13.597976 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:14.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:15.588772 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:16.597983 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:17.588936 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> 15:01:18.588919 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, 
>>> length 28
>>> ^C
>>> 9 packets captured
>>> 9 packets received by filter
>>> 0 packets dropped by kernel
>>>
>>
>>  root@beaglebone:~# ping 192.168.7.1
>>> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
>>> From 192.168.7.2 icmp_seq=1 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=2 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=3 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=4 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=5 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=6 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=7 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=8 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=9 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=10 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=11 Destination Host Unreachable
>>> From 192.168.7.2 icmp_seq=12 Destination Host Unreachable
>>> ^C
>>> --- 192.168.7.1 ping statistics ---
>>> 14 packets transmitted, 0 received, +12 errors, 100% packet loss, time 
>>> 13001ms
>>> pipe 3
>>> root@beaglebone:~# tcpdump -i usb0
>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol 
>>> decode
>>> listening on usb0, link-type EN10MB (Ethernet), capture size 65535 bytes
>>> ^C
>>> 0 packets captured
>>> 0 packets received by filter
>>> 0 packets dropped by kernel
>>>
>>
>> I already spent hours trying to figure out the problem here, any help is 
>> greatly appreciated! 
>>
>> -- 
>> 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

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

Thanks, I'll try that.

On Monday, December 7, 2015 at 3:36:14 PM UTC+1, RobertCNelson wrote:
>
>
>
> On Mon, Dec 7, 2015 at 8:21 AM, Fabian Dalbert  > wrote:
>
>> Hi
>>
>> I'm trying to write a module for a real-time kernel. Following the 
>> instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, 
>> I compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a 
>> Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.
>>
>> Before, with kernel 3.8.13-bone70, everything was working perfectly fine. 
>> However after upgrading the kernel, my desktop (running Linux Mint) no 
>> longer receives an ip address.
>>
>
>
> Fixed in:
>
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/1d9085bfb11e9e35ab0f4262799c8c801219a84f
>
> r24.3
>
> feel free to upgrade to:
>
> 4.1.13-ti-rt-r35
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: Private message regarding: [beagleboard] BBB Data Aggregation Unit using external ADC

2015-12-07 Thread Chelsea Orefice

Hi John,

These are very helpful links. I was wondering if there was an online
document on all functions that I can code BBB in either in C, C++, python,
etc.

Thanks,
Chelsea

On Thu, Dec 3, 2015 at 11:12 PM, John Syne  wrote:

> Hi Chelsea,
>
> Here are some reference I have found helpful:
>
>
> http://www.analog.com/library/analogdialogue/archives/39-05/op_amp_applications_handbook.html
>
> http://www.analog.com/library/analogDialogue/archives/39-06/data_conversion_handbook.html
>
> Regards,
> John
>
>
>
>
> On Dec 3, 2015, at 5:57 PM, Chelsea Orefice  wrote:
>
> Hi John,
>
> Just wanted to say thank you for really helping me with this. It has been
> a struggle for me and my team to get help from different resources at
> school as well as our liaisons where we are getting our design requirements
> from. (This is our senior engineering project.)
>
> I am having still a little difficulty in understanding how the circuitry I
> shared with you may give me a single input instead of differential that the
> ADC requires.I attached the actual design of the system, so if you could
> help me understand how it won't work it'd be much appreciated.
>
> Also, may you tell me your background in relation to all of this? You are
> very knowledgeable in this area, and when I relay some of this information
> to my team I would like to share from whom I received this information
> from.
>
>
> Sincerely,
> Chelsea
>
> On Thu, Dec 3, 2015 at 7:01 PM, John Syne  wrote:
>
>> Hi Chelsea,
>>
>> I have cc beagleboard because someone else might learn from this
>> discussion. Looking at the link you provided, it won’t work because ADS1278
>> requires a differential input. Look at page 39 for circuits that will work
>> for you.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Dec 3, 2015, at 3:52 PM, Chelsea Orefice  wrote:
>>
>> My apologies. Please let me know if this link works. (You will need to
>> just copy and paste in search bar). If that doesn't work I will send it as
>> an attachment. Will also look at the diagram as well.
>>
>> http://cnx.org/resources/72628d36f0c24bc80ff94e5c0bf6df2b27a
>> 86751/opamp4.png
>>
>> Thanks again,
>> Chelsea
>>
>> On Thursday, December 3, 2015 at 6:46:49 PM UTC-5, john3909 wrote:
>>>
>>> Look at page 39 for a suitable input circuit.
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>>
>>> On Dec 3, 2015, at 3:03 PM, Chelsea Orefice  wrote:
>>>
>>> Hi John,
>>>
>>> Thanks for getting back to me. I was actually looking at that same ADC
>>> converter as you posted in your reply. Just looking for some clarification
>>> on a few things. What type of error would a simple resistor divider
>>> introduce into the system? I am currently using a cascaded inverting op
>>> amp system. Not really sure if this will scale the input voltage to a level
>>> that is compatible with my ADC.
>>>
>>> The circuit diagram looks like this:
>>> [image: Inline image 1]
>>>
>>> Looking forward to your reply,
>>> Chels
>>>
>>> On Thursday, December 3, 2015 at 5:07:41 PM UTC-5, Chelsea Orefice wrote:

 Hi everyone,

 I am new to the world of using MCUs and am looking for some assistance
 on a project that I am currently working on. To sum things up quickly, I am
 building a data aggregation unit that can convert analog voltage readings
 to digital values that is to be stored on a USB or SD card. The DAU will
 collect 3 types of signals, a buffer signal, clipped signal, and a signal
 passed through a LPF. In the end, the data should be stored as either a
 MatLab file or .xml file. However, I am facing a few road blocks relating
 to my design.

 1.) I need to use a 24 bit ADC for high resolution purposes based on
 design requirements that were just given to me as I will be collecting data
 from .1mV to 50V and it has to have a high sample speed rate. Has anyone
 connected an external ADC to the BBB? If so, what was the brand of your
 external ADC? How did you connect the ADC to the BBB? (It'd be greatly
 appreciated to be able to see a design).

 2.) If you have had a similar project to this, was wondering how you
 went about it. Any advice would be greatly appreciated.


 As I said before, all of this is very new to me. So thank you for
 taking the time to help me out.

 Chelsea



>>> --
>>> 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.
>>> 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..

[beagleboard] Re: Bulk flashing of BBB eMMC

2015-12-07 Thread 'dl4mea' via BeagleBoard

Hello Lee,

my process is that I have a running Linux on a bootable SD card.
As a autostart service, there is a scripted executed, which performs

1) partitioning of the eMMC card
2) copy u-boot.bin and MLO to the first sectors of the eMMC 
3) format the 1st (and only) partition with ext4 file system
4) unzip/untar a master tar.gz from the boot media to the data partition
5) patch the extracted uEnv.txt with the actual UUID of the partition on 
eMMC
6) initiate regeneration of ssh host keys (touch /etc/ssh/ssh.regenerate)
7) sync
8) power off

That takes about 1min to flash one Beaglebone. It takes somewhat longer if 
the BBB is not connected to a network, because then it needs a network 
timeout to proceed

cheers, Günter (dl4mea)



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

Re: [beagleboard] Ethernet-over-USB not working with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 8:02 AM,  wrote:

> Hi
>
> I'm trying to write a kernel module for a real-time kernel. Following the
> instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, I
> compiled and installed the 4.1.13-bone-rt-r17 kernel on my sd card with a
> BeagleBoard.org Debian Image 2015-03-01.
>
> Previously, with kernel 3.8.13-bone70, my desktop (running linux mint)
> connected automatically to the beaglebone through ethernet-over-usb, after
> the kernel update, my desktop does not get assigned an IP address.
>

Fixed in:

https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/1d9085bfb11e9e35ab0f4262799c8c801219a84f

r24.3

feel free to upgrade to:

4.1.13-ti-rt-r35

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

Re: [beagleboard] Bulk flashing of BBB eMMC

2015-12-07 Thread William Hermans

You could boot over network, load rootfs over NFS, but in the end, you till
need an sdcard for the bootloaders . ..

On Mon, Dec 7, 2015 at 7:33 AM, Gerald Coley  wrote:

> I know of no other way. That is why that is the way we do it in
> production. It works out fine for use. We use the duplicator to crate a
> bunch of card sand we use them to flash the boards during burn in.
>
> Gerald
>
>
> On Mon, Dec 7, 2015 at 6:43 AM, Lee Armstrong  wrote:
>
>> Thanks Gerald,
>>
>> That wasn’t really the issue as I can do that part no problem.  Was
>> curious if there was another way of flashing BBB’s en masse via another
>> means other than SD cards.
>>
>>
>> On Mon, Dec 7, 2015 at 12:42 PM, Gerald Coley 
>> wrote:
>>
>>> A bulk SD card copier.
>>>
>>> Gerald
>>>
>>>
>>> On Mon, Dec 7, 2015 at 12:38 AM, Lee Armstrong 
>>> wrote:
>>>
 What is the quickest way to bulk flash say 10 BBB's eMMC?

 At the moment I have 10 Micro SD Card with a custom flasher image on
 and this works but wondered if there was a more slick solution out there at
 all?


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

>>>
>>>
>>>
>>> --
>>> Gerald
>>>
>>> ger...@beagleboard.org
>>> http://beagleboard.org/
>>>
>>> --
>>> 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/n6a7J_Tby4w/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Gerald
>
> ger...@beagleboard.org
> http://beagleboard.org/
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Robert Nelson

On Mon, Dec 7, 2015 at 8:21 AM, Fabian Dalbert  wrote:

> Hi
>
> I'm trying to write a module for a real-time kernel. Following the
> instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, I
> compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a
> Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.
>
> Before, with kernel 3.8.13-bone70, everything was working perfectly fine.
> However after upgrading the kernel, my desktop (running Linux Mint) no
> longer receives an ip address.
>


Fixed in:

https://github.com/RobertCNelson/ti-linux-kernel-dev/commit/1d9085bfb11e9e35ab0f4262799c8c801219a84f

r24.3

feel free to upgrade to:

4.1.13-ti-rt-r35

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

Re: [beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread William Hermans

Have you loaded the g_ether kernel module on the beaglebone ? When building
your own kernel, this is something you have to take care of yourself .

On Mon, Dec 7, 2015 at 7:21 AM, Fabian Dalbert  wrote:

> Hi
>
> I'm trying to write a module for a real-time kernel. Following the
> instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, I
> compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a
> Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.
>
> Before, with kernel 3.8.13-bone70, everything was working perfectly fine.
> However after upgrading the kernel, my desktop (running Linux Mint) no
> longer receives an ip address.
>
> ifconfig beaglebone:
>
> usb0  Link encap:Ethernet  HWaddr a2:29:c5:ee:bf:e6
>>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>>   inet6 addr: fe80::a029:c5ff:feee:bfe6/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:76 (76.0 B)  TX bytes:9408 (9.1 KiB)
>>
>
> ifconfig desktop:
>
>  eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa
>>   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>   RX packets:37 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:7262 (7.2 KB)  TX bytes:268 (268.0 B)
>>
>
> manually assigning an ip does not do the trick. When pinging the desktop
> from the beaglebone (with or without manually assigning an ip), i can catch
> the requests using tcpdump. The beaglebone does however not receive
> anything, no answers to pings, nothing showing up in tcpdump.
>
> fdalbert@edge ~ $ sudo tcpdump -i eth1
>> tcpdump: WARNING: eth1: no IPv4 address assigned
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
>> 15:01:10.597986 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:11.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:12.588895 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:13.597976 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:14.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:15.588772 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:16.597983 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:17.588936 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> 15:01:18.588919 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length
>> 28
>> ^C
>> 9 packets captured
>> 9 packets received by filter
>> 0 packets dropped by kernel
>>
>
>  root@beaglebone:~# ping 192.168.7.1
>> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
>> From 192.168.7.2 icmp_seq=1 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=2 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=3 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=4 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=5 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=6 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=7 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=8 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=9 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=10 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=11 Destination Host Unreachable
>> From 192.168.7.2 icmp_seq=12 Destination Host Unreachable
>> ^C
>> --- 192.168.7.1 ping statistics ---
>> 14 packets transmitted, 0 received, +12 errors, 100% packet loss, time
>> 13001ms
>> pipe 3
>> root@beaglebone:~# tcpdump -i usb0
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on usb0, link-type EN10MB (Ethernet), capture size 65535 bytes
>> ^C
>> 0 packets captured
>> 0 packets received by filter
>> 0 packets dropped by kernel
>>
>
> I already spent hours trying to figure out the problem here, any help is
> greatly appreciated!
>
> --
> 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.
> 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+unsubsc

[beagleboard] Ethernet-over-USB not working with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread fab . dal

Hi

I'm trying to write a kernel module for a real-time kernel. Following the 
instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, I 
compiled and installed the 4.1.13-bone-rt-r17 kernel on my sd card with a 
BeagleBoard.org Debian Image 2015-03-01.

Previously, with kernel 3.8.13-bone70, my desktop (running linux mint) 
connected automatically to the beaglebone through ethernet-over-usb, after 
the kernel update, my desktop does not get assigned an IP address.
 
ifconfig desktop side:

eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa  
>   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:37 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:7262 (7.2 KB)  TX bytes:268 (268.0 B)
>
 

ifconfig beaglebone:

usb0  Link encap:Ethernet  HWaddr a2:29:c5:ee:bf:e6  
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   inet6 addr: fe80::a029:c5ff:feee:bfe6/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:76 (76.0 B)  TX bytes:9408 (9.1 KiB)
>

I can manually assign an IP address to eth1, this has no effect however.
Pings from the beaglebone to the desktop can be seen with tcpdump on the 
desktop (and get answered in case I manually assign an IP, the answer 
doesn't get through though), but not the other way round.


root@beaglebone:~# ping 192.168.7.1
> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
> From 192.168.7.2 icmp_seq=1 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=2 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=3 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=4 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=5 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=6 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=7 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=8 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=9 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=10 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=11 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=12 Destination Host Unreachable
> ^C
> --- 192.168.7.1 ping statistics ---
> 14 packets transmitted, 0 received, +12 errors, 100% packet loss, time 
> 13001ms
> pipe 3
>


fdalbert@edge ~ $ sudo tcpdump -i eth1
> tcpdump: WARNING: eth1: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
> 15:01:10.597986 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:11.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:12.588895 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:13.597976 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:14.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:15.588772 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:16.597983 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:17.588936 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:18.588919 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> ^C
> 9 packets captured
> 9 packets received by filter
> 0 packets dropped by kernel



I have spent hours trying to figure out what's going wrong here, any help 
is greatly appreciated! 

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

Re: [beagleboard] Bulk flashing of BBB eMMC

2015-12-07 Thread Gerald Coley

I know of no other way. That is why that is the way we do it in production.
It works out fine for use. We use the duplicator to crate a bunch of card
sand we use them to flash the boards during burn in.

Gerald


On Mon, Dec 7, 2015 at 6:43 AM, Lee Armstrong  wrote:

> Thanks Gerald,
>
> That wasn’t really the issue as I can do that part no problem.  Was
> curious if there was another way of flashing BBB’s en masse via another
> means other than SD cards.
>
>
> On Mon, Dec 7, 2015 at 12:42 PM, Gerald Coley 
> wrote:
>
>> A bulk SD card copier.
>>
>> Gerald
>>
>>
>> On Mon, Dec 7, 2015 at 12:38 AM, Lee Armstrong  wrote:
>>
>>> What is the quickest way to bulk flash say 10 BBB's eMMC?
>>>
>>> At the moment I have 10 Micro SD Card with a custom flasher image on and
>>> this works but wondered if there was a more slick solution out there at all?
>>>
>>>
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Gerald
>>
>> ger...@beagleboard.org
>> http://beagleboard.org/
>>
>> --
>> 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/n6a7J_Tby4w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

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

[beagleboard] Ethernet-over-USB: no ip assigned with kernel 4.1.13-bone-rt-r17

2015-12-07 Thread Fabian Dalbert

Hi

I'm trying to write a module for a real-time kernel. Following the 
instructions on https://eewiki.net/display/linuxonarm/BeagleBone+Black, I 
compiled and deployed a 4.1.13-bone-rt-r17 kernel to an sd card with a 
Debian GNU/Linux 7 BeagleBoard.org Debian Image 2015-03-01.

Before, with kernel 3.8.13-bone70, everything was working perfectly fine. 
However after upgrading the kernel, my desktop (running Linux Mint) no 
longer receives an ip address.

ifconfig beaglebone:

usb0  Link encap:Ethernet  HWaddr a2:29:c5:ee:bf:e6  
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   inet6 addr: fe80::a029:c5ff:feee:bfe6/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:76 (76.0 B)  TX bytes:9408 (9.1 KiB)
>

ifconfig desktop:

 eth1  Link encap:Ethernet  HWaddr 84:eb:18:ae:cb:aa  
>   inet6 addr: fe80::86eb:18ff:feae:cbaa/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:37 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:7262 (7.2 KB)  TX bytes:268 (268.0 B)
>

manually assigning an ip does not do the trick. When pinging the desktop 
from the beaglebone (with or without manually assigning an ip), i can catch 
the requests using tcpdump. The beaglebone does however not receive 
anything, no answers to pings, nothing showing up in tcpdump.

fdalbert@edge ~ $ sudo tcpdump -i eth1
> tcpdump: WARNING: eth1: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
> 15:01:10.597986 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:11.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:12.588895 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:13.597976 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:14.588800 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:15.588772 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:16.597983 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:17.588936 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> 15:01:18.588919 ARP, Request who-has 192.168.7.1 tell 192.168.7.2, length 
> 28
> ^C
> 9 packets captured
> 9 packets received by filter
> 0 packets dropped by kernel
>

 root@beaglebone:~# ping 192.168.7.1
> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
> From 192.168.7.2 icmp_seq=1 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=2 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=3 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=4 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=5 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=6 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=7 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=8 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=9 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=10 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=11 Destination Host Unreachable
> From 192.168.7.2 icmp_seq=12 Destination Host Unreachable
> ^C
> --- 192.168.7.1 ping statistics ---
> 14 packets transmitted, 0 received, +12 errors, 100% packet loss, time 
> 13001ms
> pipe 3
> root@beaglebone:~# tcpdump -i usb0
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on usb0, link-type EN10MB (Ethernet), capture size 65535 bytes
> ^C
> 0 packets captured
> 0 packets received by filter
> 0 packets dropped by kernel
>

I already spent hours trying to figure out the problem here, any help is 
greatly appreciated! 

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

Re: [beagleboard] Bulk flashing of BBB eMMC

2015-12-07 Thread Lee Armstrong

Thanks Gerald,




That wasn’t really the issue as I can do that part no problem.  Was curious if 
there was another way of flashing BBB’s en masse via another means other than 
SD cards.

On Mon, Dec 7, 2015 at 12:42 PM, Gerald Coley 
wrote:

> A bulk SD card copier.
> Gerald
> On Mon, Dec 7, 2015 at 12:38 AM, Lee Armstrong  wrote:
>> What is the quickest way to bulk flash say 10 BBB's eMMC?
>>
>> At the moment I have 10 Micro SD Card with a custom flasher image on and
>> this works but wondered if there was a more slick solution out there at all?
>>
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Gerald
> ger...@beagleboard.org
> http://beagleboard.org/
> -- 
> 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/n6a7J_Tby4w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Bulk flashing of BBB eMMC

2015-12-07 Thread Gerald Coley

A bulk SD card copier.

Gerald


On Mon, Dec 7, 2015 at 12:38 AM, Lee Armstrong  wrote:

> What is the quickest way to bulk flash say 10 BBB's eMMC?
>
> At the moment I have 10 Micro SD Card with a custom flasher image on and
> this works but wondered if there was a more slick solution out there at all?
>
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

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

Re: [beagleboard] Re: Configure Beaglebone to access usb0 from host PC. (Cannot ssh to beaglebone through USB)

2015-12-07 Thread Jason Kridner

Find the modprobe here:
https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh

You've got to have it serve up an IP address if you don't want to
manually configure:
https://github.com/RobertCNelson/boot-scripts/blob/master/boot/autoconfigure_usb0.sh

On Mon, Dec 7, 2015 at 2:42 AM, Mehmet Kurnaz  wrote:
> You need g_ether.ko module. You can check it is loaded.
>
> On Sun, Dec 6, 2015 at 7:44 PM, hllpc  wrote:
>>
>> Same Issue here.
>>
>> Il giorno venerdì 30 ottobre 2015 18:13:55 UTC+1, Alex ha scritto:
>>>
>>> Hi,
>>>
>>> I am using ubuntu 14.04 (from Robert Nelson) with a custom 3.15.10-bone8
>>> kernel on Beaglebone Black. HDMI is disabled.
>>> When I plug the board to a PC, Beaglebone powers up but the PC does not
>>> recognize that a USB device is connected to it. I have installed the drivers
>>> for network-over-USB which is recommended on Beagleboard.org/getting-started
>>> too. Moreover, I cannot ssh into it using 192.168.7.2 eventhough I have set
>>> up my /etc/network/interfaces.
>>> ubuntu@arm $ ifconfig usb0
>>> usb0  Link encap:Ethernet  HWaddr d2:56:2f:23:1d:e2
>>>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>>>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>   collisions:0 txqueuelen:1000
>>>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>>
>>>
>>> Is there some modules that I need to run or compile to Kernel to bring
>>> the client USB up? How should I configure the linux to be seen by PC when
>>> connected from mini USB?
>>> Thanks for any help.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Kernel Module access problem

2015-12-07 Thread Mehmet Aydogan


>
> I read that source but they selected <*> at menuconfig so driver built 
> into the kernel. But I try to use "Loadable Kernel Module".
>
If I look the given path at this website, there is no iio:device. 

* root@beaglebone:/sys/bus/iio/devices# ls*
* iio_sysfs_trigger*

According to me, I should make device node with "mknode".
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Kernel Module access problem

2015-12-07 Thread William Hermans

https://wiki.analog.com/resources/tools-software/linux-drivers/iio-adc/ad7192

On Mon, Dec 7, 2015 at 1:18 AM, Mehmet Aydogan 
wrote:

> Hi, I install kernel module named as ad7192 (adc driver) via modprobe.
>
> After running "modprobe ad7192", "lsmod" will give this output:
> root@beaglebone:/var# lsmod
> Module   Size  Used by
> ad7192   5700  0
> ad_sigma_delta  5105  1 ad7192
> g_multi50407  2
> libcomposite   15028  1 g_multi
> omap_rng   4062  0
> mt7601Usta458758  0
>
> After that, I should run "mknode" command with major number in order
> to access the device from userspace.
> At this point I can not find "major device number" of ad7192 driver.
> How can I find the major number ? or How can I access this driver from
> userspace ?
>
> Thanks
> Mehmet
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Set priority of network interfaces wlan0 rather than eth0

2015-12-07 Thread William Hermans

https://www.thomas-krenn.com/en/wiki/Two_Default_Gateways_on_One_System

On Sun, Dec 6, 2015 at 9:37 PM, Felipe ordoñez 
wrote:

> Hi guys,
>
> I am pretty new using a BBB, and I am trying to use it with two network
> interfaces, one, wlan0 to get internet through usb wifi dongle, two a local
> connection via eth0 to another network.
>
> I configured the /etc/network/interfaces   wlan0 as a  inet with dhcp,
>  eth0 with inet.. static,  an every works fine, because of I ping to the
> local network and it gaves me a anwer,  I ping google and I have internet.
>
> Since booting I start with my networks fine, but The REAL PROBLEM is after
> a few seconds, when the BBB put eth0 as a default interface, so my internet
> is down (wlan0) , so I lose every contact with the world.
>
> I try to do ifdown, ifup,  but the internet is gone, only when I unpluged
> the RJ45 (eth0), I get internet again.   BUT I want to work with the two
> networks at the same time.
>
> How I set up forever my wlan0 as a default connection (interface),
>  because I use IFMETRIC,  so in my file /etc/network/interfaces   I use
>  metric 1 (wlan0), metric 10 (eth0),  but the BBB does not care any metric.
>
>
> with route -nthe system mounts a iface with eth0 and  metric 0 , and
> the other parameters on Zero, too.
>
>
> Any help??
>
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Kernel Module access problem

2015-12-07 Thread Mehmet Aydogan

Hi, I install kernel module named as ad7192 (adc driver) via modprobe.

After running "modprobe ad7192", "lsmod" will give this output: 
root@beaglebone:/var# lsmod
Module   Size  Used by
ad7192   5700  0 
ad_sigma_delta  5105  1 ad7192
g_multi50407  2 
libcomposite   15028  1 g_multi
omap_rng   4062  0 
mt7601Usta458758  0 

After that, I should run "mknode" command with major number in order 
to access the device from userspace.
At this point I can not find "major device number" of ad7192 driver. 
How can I find the major number ? or How can I access this driver from 
userspace ?

Thanks 
Mehmet

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

74 matches

Mail list logo