Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...

[Matt Maher Peterson]

Sorry about that.  

So am I interpreting your response right that I need to go back to 4.1.21 
that I am trying to clone, connect it to the network and run the make uSD 
from emmc again to create a new image?

On Tuesday, May 31, 2016 at 9:06:49 AM UTC-7, RobertCNelson wrote:
>
>
>
> On Tue, May 31, 2016 at 11:00 AM, Matt99eo  > wrote:
>
>> Bump.
>>
>>
>> Still trying to solve this.  Any help appreciated.
>>
>> Is there another method I should use to clone my 4.1.21 Debian Jessie BBB?
>>
>
> Well this had already been answered:
>
> https://groups.google.com/forum/#!category-topic/beagleboard/UIXhMlNXgh0
>
> but then you changed the message "topic" after google groups had already 
> sent the emails out..
>
> Thus losing the reply...
>
> Regards,
>
> -- 
> Robert Nelson
> https://rcn-ee.com/
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6c2ffa6f-dc6d-4085-8b96-a7203c4cafeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Flashin BBB with new image I built from RC guide

[Matt Maher Peterson]

Hi again,

Trying to flash another device with the uSD that worked great before and 
gettting a bunch of odd stuff out the serial debugger port, ending in cylon 
LEDS :/

c: deleted inode referenced: 6031
dules/rusha/rusha.js") failed: Input/output error (5)
rsync: re[  176.707788] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: 
inode #3485: comm rsync: deleted inode referenced: 6040
adlink_stat("/opt/cloud9/build/s[  176.722007] EXT4-fs error (device 
mmcblk1p2): ext4_lookup:1416: inode #3485: comm rsync: deleted inode 
referenced: 6039
tandalonebuild/node_modules/rusha/rusha.sweet.js[  176.737121] EXT4-fs 
error (device mmcblk1p2): ext4_lookup:1416: inode #3486: comm rsync: 
deleted inode referenced: 6043
") failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/rusha/node_modules")
 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/rusha/Gruntfile.js")
 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/rusha/LICENSE") 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/rusha/rusha.js.map")
 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/send/node_modules")
 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/send/lib") 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/simplefunc/test") 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/simplefunc/lib") 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/source-map/node_modules")
 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/source-map/lib") 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/node_modules/systemd/example") 
failed: Input/output error (5)
[  182.934944] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode 
#3391: comm rsync: deleted inode referenced: 6057
rsync: readlink_stat("/opt/cloud9/build/standalo[  182.951614] EXT4-fs 
error (device mmcblk1p2): ext4_lookup:1416: inode #3391: comm rsync: 
deleted inode referenced: 6051
nebuild/plugins/c9.ide.closeconfirmation") failed: Input/output [  
182.969373] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode 
#3391: comm rsync: deleted inode referenced: 6046
error (5)
rsync: readlink_stat("/opt/cloud9/bui[  182.985178] EXT4-fs error (device 
mmcblk1p2): ext4_lookup:1416: inode #3391: comm rsync: deleted inode 
referenced: 6047
ld/standalonebuild/plugins/c9.ide.ace.keymaps") failed: Input/output error 
(5)
[  183.003398] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode 
#3391: comm rsync: deleted inode referenced: 6058
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/plugins/c9.connect.favic[  
183.021934] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode 
#3391: comm rsync: deleted inode referenced: 6055
on") failed: Input/output error (5)
rsync: readlink_stat("/opt/cloud9/build/standalonebuild/plugins/c9.core") 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/plugins/c9.ide.collab") 
failed: Input/output error (5)
rsync: readlink_s[  183.057445] EXT4-fs error (device mmcblk1p2): 
ext4_lookup:1416: inode #3391: comm rsync: deleted inode referenced: 6060
tat("/opt/cloud9/build/standalonebuild/plugins/c9.ide.ace") failed: 
Input/output error (5)
rsync: readlink_stat("/opt/cloud9/build/standalonebuild/plugins/[  
183.085578] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode 
#3391: comm rsync: deleted inode referenced: 6050
c9.ide.dialog.wizard") failed: Input/output error (5)
rsync: re[  183.102634] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: 
inode #3391: comm rsync: deleted inode referenced: 6059
adlink_stat("/opt/cloud9/build/standalonebuild/p[  183.118903] EXT4-fs 
error (device mmcblk1p2): ext4_lookup:1416: inode #3391: comm rsync: 
deleted inode referenced: 6052
lugins/c9.ide.ace.gotoline") failed: Input/outpu[  183.134504] EXT4-fs 
error (device mmcblk1p2): ext4_lookup:1416: inode #3391: comm rsync: 
deleted inode referenced: 6053
t error (5)
rsync: readlink_stat("/opt/cloud9/build/standaloneb[  183.151302] EXT4-fs 
error (device mmcblk1p2): ext4_lookup:1416: inode #3391: comm rsync: 
deleted inode referenced: 6048
uild/plugins/c9.ide.configuration") failed: Inpu[  183.168058] EXT4-fs 
error (device mmcblk1p2): ext4_lookup:1416: inode #3391: comm rsync: 
deleted inode referenced: 6049
t/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/plugins/c9.ide.ace.repl") 
failed: Input/output error (5)
rsync: 
readlink_stat("/opt/cloud9/build/standalonebuild/plugins/c9.ide.ace.statusbar") 
failed: Input/outpu[  183.199729] EXT4-fs error 

Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70

[Matt Maher Peterson]

HI William,

I am in over my head here :)  I don't really know how it works.

All I know at this point is that I see the system seeing and registereing
the device but I cannot get it to bring it live on the BBB.

But on my desktop machine running ubuntu 3.16.0-70-generic
#90~14.04.1-Ubuntu   it simply registers and then brings and then bring it
up.  It just works. However on my BBB it doesn't  ever list it in ifconfig.


Matt Maher Peterson
APANA
w: 360.746.2276x401
c: 360.393.5549

On Wed, Apr 20, 2016 at 4:00 PM, William Hermans <yyrk...@gmail.com> wrote:

> Do you know how a cdc_ether device works ? Because according to the text
> you've got there, and the output from dmesg, you should be able to run sudo
> ifconfig, and see it listed.
>
> On Wed, Apr 20, 2016 at 3:31 PM, Matt99eo <mattmaherpeter...@gmail.com>
> wrote:
>
>> Still working on this and really not sure what my next step is.
>>
>> When I plug the module into both my old device running 3.8 and now a new
>> device (just compiled 4.1.21-bone-rt-r20)  I do am not getting a
>> connection.  Tailing the syslog it gets up the poingt of declaring it
>> ttyACM0: USB ACM device but then nothing happens:
>>
>>
>> [12990.725461] cdc_ether 1-1:1.0 usb0: unregister 'cdc_ether'
>> usb-musb-hdrc.1.auto-1, CDC Ethernet Device
>> Apr 20 21:28:05 arm kernel: [12990.719975] usb 1-1: USB disconnect,
>> device number 4
>> Apr 20 21:28:05 arm kernel: [12990.725461] cdc_ether 1-1:1.0 usb0:
>> unregister 'cdc_ether' usb-musb-hdrc.1.auto-1, CDC Ethernet Device
>> [12993.532521] usb 1-1: new high-speed USB device number 6 using musb-hdrc
>> Apr 20 21:28:08 arm kernel: [12993.532521] usb 1-1: new high-speed USB
>> device number 6 using musb-hdrc
>> [12993.823315] usb 1-1: New USB device found, idVendor=1e2d,
>> idProduct=00a0
>> [12993.830122] usb 1-1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=3
>> [12993.837381] usb 1-1: Product: SQN
>> [12993.840731] usb 1-1: Manufacturer: Sequans Communications
>> [12993.846221] usb 1-1: SerialNumber: 700400708002
>> Apr 20 21:28:08 arm kernel: [12993.823315] usb 1-1: New USB device found,
>> idVendor=1e2d, idProduct=00a0
>> Apr 20 21:28:08 arm kernel: [12993.830122] usb 1-1: New USB device
>> strings: Mfr=1, Product=2, SerialNumber=3
>> Apr 20 21:28:08 arm kernel: [12993.837381] usb 1-1: Product: SQN
>> Apr 20 21:28:08 arm kernel: [12993.840731] usb 1-1: Manufacturer: Sequans
>> Communications
>> Apr 20 21:28:08 arm kernel: [12993.846221] usb 1-1: SerialNumber:
>> 700400708002
>> [12993.922298] cdc_ether 1-1:1.0 usb0: register 'cdc_ether' at
>> usb-musb-hdrc.1.auto-1, CDC Ethernet Device, 02:80:70:00:04:70
>> [12993.942669] cdc_acm 1-1:1.2: ttyACM0: USB ACM device
>>
>>
>> I have also now taken this module and plugged it hot into my dev desktop
>> computer running ubuntu ( 3.16.0-70-generic #90~14.04.1-Ubuntu )  and it
>> just fires up all the way!  Auto detects and I instantly have an
>> established connection thru the module.
>>
>> I attached my syslog from when I did this and you see much more going on
>> after ~ line 11 where we have the same ttyACM0: USB ACM device.
>>
>>
>> On Monday, April 18, 2016 at 10:37:20 AM UTC-7, Matt99eo wrote:
>>>
>>> Ok I see it now with lsusb:
>>>
>>> lsusb
>>> Bus 001 Device 004: ID 1e2d:00a0
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>
>>> And in my dmesg log I see it registering:
>>>
>>> dmesg |grep cdc_ether
>>> [0.709427] usbcore: registered new interface driver cdc_ether
>>> [1.859965] cdc_ether 1-1:1.0: usb_probe_interface
>>> [1.859981] cdc_ether 1-1:1.0: usb_probe_interface - got id
>>> [1.885585] cdc_ether 1-1:1.0 usb0: register 'cdc_ether' at
>>> usb-musb-hdrc.1.auto-1, CDC Ethernet Device, 02:80:70:00:04:70
>>>
>>> What am I missing to establish the Ethernet over USB connection?
>>>
>>>
>>> On Monday, April 18, 2016 at 9:03:22 AM UTC-7, RobertCNelson wrote:
>>>>
>>>>
>>>>
>>>> On Mon, Apr 18, 2016 at 10:57 AM, Matt99eo <mattmahe...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi RC,
>>>>>
>>>>> Sorry for the limited information. Just got word the document I am
>>>>> working with is public (attached)
>>>>>
>>>>> The device I am working with is a Skywire LTE CAT1 Module (Gemalto
>>>>> ELS35).
&g

Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70

[Matt Maher Peterson]

Ok so I built 4.1 with ./build_kernel.sh and now I see the file for the 4.1 
kernel

Am I looking in the cdc_ether.c file for my specific device?

On Friday, April 15, 2016 at 5:18:17 PM UTC-7, Matt99eo wrote:
>
> So I check out each kernel with 
>
> git checkout origin/am33x-v4.1 -b tmp_v4.1
>
> Then how do I find the file?  Again sorry for the hand holding...
>
>
> On Friday, April 15, 2016 at 5:12:09 PM UTC-7, RobertCNelson wrote:
>>
>>
>>
>> On Fri, Apr 15, 2016 at 7:07 PM, Matt99eo  wrote:
>>
>>> Sorry for the hand holding but what files am I comparing?
>>>
>>
>> Well, for "cellular module"...
>>
>> ./drivers/net/usb/
>>
>> 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

[Matt Maher Peterson]

Thanks that worked to adafruit library working.


Still having an issues getting the device tree to load on boot.  

Is there a better way to do this than in /boot/uEnv.txt ?  I have this line 
in there now but it does not seam to do the job as I do not see the overlay 
loaded after boot in .../slots
cape_enable=capemgr.enable_partno=BB-APA-01




I can manually load it:

root@mmpTestBox:/sys/class/gpio# cat 
/sys/devices/platform/bone_capemgr/slots

 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1

root@mmpTestBox:/sys/class/gpio# sh -c "echo 'BB-APA-01' > 
/sys/devices/platform/bone_capemgr/slots"
root@mmpTestBox:/sys/class/gpio# cat 
/sys/devices/platform/bone_capemgr/slots

 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1

 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-APA-01

I believe in the old kernel 3.8.x I fuound a way to bake the overlay 
kernel.  Is this possible in 4.1.x?

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

[Matt Maher Peterson]

Ah k.  lol that makessense now.

Have that done but still not loading my overlay on boot...

On Wednesday, December 9, 2015 at 11:52:21 AM UTC-8, William Hermans wrote:
>
> In other words. if the file */usr/share/initramfs-tools/hooks/dtbo *is 
> not already executable run chmod +x on it. *OR* You could create a bash 
> script, drop that code into it. Make the script executable, then run it. 
> And it'd do it for you. Pick your poison.
>
> On Wed, Dec 9, 2015 at 12:48 PM, William Hermans <yyr...@gmail.com 
> > wrote:
>
>>
>>>
>>> *Now do I add this to the file?*
>>>
>>>
>>>
>>> *if [ ! -x /usr/share/initramfs-tools/hooks/dtbo ] ; then sudo chmod 
>>> +x /usr/share/initramfs-tools/hooks/dtbo fi *
>>>
>>
>> That's bash script programmer speak for making that file executable, if 
>> it's not already ;)
>>
>>
>> On Wed, Dec 9, 2015 at 10:13 AM, Matt Maher Peterson <
>> matt.mahe...@hydro-care.com > wrote:
>>
>>> Thanks for bearing with me here.
>>>
>>> I did a wget  
>>> https://github.com/rcn-ee/repos/blob/master/bb-bb-customizations/suite/jessie/debian/dtbo
>>>  
>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Frcn-ee%2Frepos%2Fblob%2Fmaster%2Fbb-bb-customizations%2Fsuite%2Fjessie%2Fdebian%2Fdtbo=D=1=AFQjCNEcV4pgfY8pNlN-kjZBtGGz-F4pgg>
>>>
>>> Now do I add this to the file?
>>>
>>> if [ ! -x /usr/share/initramfs-tools/
>>> hooks/dtbo ] ; then 
>>> sudo chmod +x /usr/share/initramfs-tools/hooks/dtbo 
>>> fi 
>>>
>>> and then 
>>> sudo update-initramfs -u -k $(uname -r) 
>>>
>>> Just to confirm my BB-APA-01-00A0.dtbo is in /lib/firmware and loads 
>>> manually.
>>>
>>> I can see that usr/share/initramfs-tools/hooks/dtbo file matches what 
>>> you have in the repo
>>>
>>> On Wednesday, December 9, 2015 at 8:51:48 AM UTC-8, RobertCNelson wrote:
>>>>
>>>> On Wed, Dec 9, 2015 at 10:42 AM, Matt Maher Peterson 
>>>> <matt.mahe...@hydro-care.com> wrote: 
>>>> > Thanks that worked to adafruit library working. 
>>>> > 
>>>> > 
>>>> > Still having an issues getting the device tree to load on boot. 
>>>> > 
>>>> > Is there a better way to do this than in /boot/uEnv.txt ?  I have 
>>>> this line 
>>>> > in there now but it does not seam to do the job as I do not see the 
>>>> overlay 
>>>> > loaded after boot in .../slots 
>>>> > cape_enable=capemgr.enable_partno=BB-APA-01 
>>>> > 
>>>> > 
>>>> > 
>>>> > 
>>>> > I can manually load it: 
>>>> > 
>>>> > root@mmpTestBox:/sys/class/gpio# cat 
>>>> > /sys/devices/platform/bone_capemgr/slots 
>>>> > 
>>>> >  0: PF  -1 
>>>> >  1: PF  -1 
>>>> >  2: PF  -1 
>>>> >  3: PF  -1 
>>>> > 
>>>> > root@mmpTestBox:/sys/class/gpio# sh -c "echo 'BB-APA-01' > 
>>>> > /sys/devices/platform/bone_capemgr/slots" 
>>>> > root@mmpTestBox:/sys/class/gpio# cat 
>>>> > /sys/devices/platform/bone_capemgr/slots 
>>>> > 
>>>> >  0: PF  -1 
>>>> >  1: PF  -1 
>>>> >  2: PF  -1 
>>>> >  3: PF  -1 
>>>> > 
>>>> >  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-APA-01 
>>>> > 
>>>> > I believe in the old kernel 3.8.x I fuound a way to bake the overlay 
>>>> kernel. 
>>>> > Is this possible in 4.1.x? 
>>>>
>>>> The trick is in the "bb-customizations" package: 
>>>>
>>>> Encase you don't have it installed: 
>>>>
>>>>
>>>> https://github.com/rcn-ee/repos/blob/master/bb-bb-customizations/suite/jessie/debian/dtbo
>>>>  
>>>>
>>>> if [ ! -x /usr/share/initramfs-tools/hooks/dtbo ] ; then 
>>>> sudo chmod +x /usr/share/initramfs-tools/hooks/dtbo 
>>>> fi 
>>>>
>>>> then just: 
>>>>
>>>> sudo update-initramfs -u -k $(uname -r) 
>>>>
>>>> and it'll be in your initrd. 
>>>>
>>>> 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...@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

[Matt Maher Peterson]

Thanks for bearing with me here.

I did a wget  
https://github.com/rcn-ee/repos/blob/master/bb-bb-customizations/suite/jessie/debian/dtbo
 
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Frcn-ee%2Frepos%2Fblob%2Fmaster%2Fbb-bb-customizations%2Fsuite%2Fjessie%2Fdebian%2Fdtbo=D=1=AFQjCNEcV4pgfY8pNlN-kjZBtGGz-F4pgg>

Now do I add this to the file?

if [ ! -x /usr/share/initramfs-tools/
hooks/dtbo ] ; then 
sudo chmod +x /usr/share/initramfs-tools/hooks/dtbo 
fi 

and then 
sudo update-initramfs -u -k $(uname -r) 

Just to confirm my BB-APA-01-00A0.dtbo is in /lib/firmware and loads 
manually.

I can see that usr/share/initramfs-tools/hooks/dtbo file matches what you 
have in the repo

On Wednesday, December 9, 2015 at 8:51:48 AM UTC-8, RobertCNelson wrote:
>
> On Wed, Dec 9, 2015 at 10:42 AM, Matt Maher Peterson 
> <matt.mahe...@hydro-care.com > wrote: 
> > Thanks that worked to adafruit library working. 
> > 
> > 
> > Still having an issues getting the device tree to load on boot. 
> > 
> > Is there a better way to do this than in /boot/uEnv.txt ?  I have this 
> line 
> > in there now but it does not seam to do the job as I do not see the 
> overlay 
> > loaded after boot in .../slots 
> > cape_enable=capemgr.enable_partno=BB-APA-01 
> > 
> > 
> > 
> > 
> > I can manually load it: 
> > 
> > root@mmpTestBox:/sys/class/gpio# cat 
> > /sys/devices/platform/bone_capemgr/slots 
> > 
> >  0: PF  -1 
> >  1: PF  -1 
> >  2: PF  -1 
> >  3: PF  -1 
> > 
> > root@mmpTestBox:/sys/class/gpio# sh -c "echo 'BB-APA-01' > 
> > /sys/devices/platform/bone_capemgr/slots" 
> > root@mmpTestBox:/sys/class/gpio# cat 
> > /sys/devices/platform/bone_capemgr/slots 
> > 
> >  0: PF  -1 
> >  1: PF  -1 
> >  2: PF  -1 
> >  3: PF  -1 
> > 
> >  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-APA-01 
> > 
> > I believe in the old kernel 3.8.x I fuound a way to bake the overlay 
> kernel. 
> > Is this possible in 4.1.x? 
>
> The trick is in the "bb-customizations" package: 
>
> Encase you don't have it installed: 
>
>
> https://github.com/rcn-ee/repos/blob/master/bb-bb-customizations/suite/jessie/debian/dtbo
>  
>
> if [ ! -x /usr/share/initramfs-tools/hooks/dtbo ] ; then 
> sudo chmod +x /usr/share/initramfs-tools/hooks/dtbo 
> fi 
>
> then just: 
>
> sudo update-initramfs -u -k $(uname -r) 
>
> and it'll be in your initrd. 
>
> 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

[Matt Maher Peterson]

OK so I upgraded to 4.1.13.ti.r35

How do I use this rebuilder?

Just to confirm I have a custom .dtbo name BB-APA-01 that loaded on boot 
where I had it baked into the kernel.  I did not add it uEnv.txt but it 
still loaded.  

Here is what I tried to get cape loaded:

root@mmpTestBox:~# dmesg | grep BB-APA
[0.00] Kernel command line: console=ttyO0,115200n8 
capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
capemgr.enable_partno=BB-APA-01 
root=UUID=38808bbf-7f2e-469d-8ff6-e5eec3303fc9 ro rootfstype=ext4 rootwait 
fixrtc quiet init=/lib/systemd/systemd
root@mmpTestBox:~# cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
root@mmpTestBox:~# sh -c "echo 'BB-APA-01' > 
/sys/devices/platform/bone_capemgr/slots"
root@mmpTestBox:~# cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
root@mmpTestBox:~# dmesg | grep BB-APA-01
[0.00] Kernel command line: console=ttyO0,115200n8 
capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
capemgr.enable_partno=BB-APA-01 
root=UUID=38808bbf-7f2e-469d-8ff6-e5eec3303fc9 ro rootfstype=ext4 rootwait 
fixrtc quiet init=/lib/systemd/systemd
[  224.61] bone_capemgr bone_capemgr: part_number 'BB-APA-01', version 
'N/A'
[  224.000251] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,BB-APA-01'


On Monday, December 7, 2015 at 5:33:19 PM UTC-8, RobertCNelson wrote:
>
> On Mon, Dec 7, 2015 at 6:21 PM, Matt Maher Peterson 
> <matt.mahe...@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 ? 
>
> 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

[Matt Maher Peterson]

How do I apply this patch?

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

[Matt Maher Peterson]

How do I apply this patch?

Matt Maher Peterson
APANA
w: 360.746.2276x401
c: 360.393.5549

On Tue, Dec 8, 2015 at 4:45 PM, Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Tue, Dec 8, 2015 at 6:01 PM, Matt Maher Peterson
> <matt.maherpeter...@hydro-care.com> wrote:
> > So I was able to to get the custom dtbo loaded after recompiling it with:
> >
> > dtc -O dtb -o BB-APA-01-00A0.dtbo -b 0 -@ BB-APA-02-00A0.dts
> >
> > Did the UARTS get renamed? I also had to remove this from the dts to get
> it
> > to comiple:
> >
> >  fragment@4 {
> >target = <>;
> >__overlay__ {
> >pinctrl-names = "default";
> >pinctrl-0 = <_pins>;
> >status = "okay";
> >};
> >};
>
> Yeap:
>
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART5-00A0.dts#L44
>
>
> >
> > Doesn't seam to be loading on boot despite having entered it in
> > /boot/uEnv.txt:
> >
> > cape_enable=capemgr.enable_partno=BB-APA-01
>
> cape_enable=bone_capemgr.enable_partno=BB-APA-01
>
> >
> >
> >
> >
> > I can manually load it:
> >
> > root@mmpTestBox:/sys/class/gpio# cat
> > /sys/devices/platform/bone_capemgr/slots
> >  0: PF  -1
> >  1: PF  -1
> >  2: PF  -1
> >  3: PF  -1
> > root@mmpTestBox:/sys/class/gpio# sh -c "echo 'BB-APA-01' >
> > /sys/devices/platform/bone_capemgr/slots"
> > root@mmpTestBox:/sys/class/gpio# cat
> > /sys/devices/platform/bone_capemgr/slots
> >  0: PF  -1
> >  1: PF  -1
> >  2: PF  -1
> >  3: PF  -1
> >  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-APA-01
> >
> > After manually loading it:
> >
> > Now I have an issued with ADC.setup() from the adafruit library.  Wasn't
> an
> > issue before I update:
> >
> > /powerMGMT.py", line 46, in shorePowerCheck
> > ADC.setup()
> > RuntimeError: Unable to setup ADC system. Possible causes are:
> >   - A cape with a conflicting pin mapping is loaded
> >   - A device tree object is loaded that uses the same name for a
> fragment:
> > helper
>
> There's a patch in this thread:
>
>
> https://github.com/adafruit/adafruit-beaglebone-io-python/issues/80#issuecomment-161431164
>
> 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

[Matt Maher Peterson]

So I was able to to get the custom dtbo loaded after recompiling it with:

dtc -O dtb -o BB-APA-01-00A0.dtbo -b 0 -@ BB-APA-02-00A0.dts 

Did the UARTS get renamed? I also had to remove this from the dts to get it 
to comiple:

 fragment@4 {
   target = <>;
   __overlay__ {
   pinctrl-names = "default";
   pinctrl-0 = <_pins>;
   status = "okay";
   };
   };

Doesn't seam to be loading on boot despite having entered it in 
/boot/uEnv.txt:

cape_enable=capemgr.enable_partno=BB-APA-01




I can manually load it:

root@mmpTestBox:/sys/class/gpio# cat 
/sys/devices/platform/bone_capemgr/slots
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
root@mmpTestBox:/sys/class/gpio# sh -c "echo 'BB-APA-01' > 
/sys/devices/platform/bone_capemgr/slots"
root@mmpTestBox:/sys/class/gpio# cat 
/sys/devices/platform/bone_capemgr/slots
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-APA-01

After manually loading it:

Now I have an issued with ADC.setup() from the adafruit library.  Wasn't an 
issue before I update:

/powerMGMT.py", line 46, in shorePowerCheck
ADC.setup()
RuntimeError: Unable to setup ADC system. Possible causes are: 
  - A cape with a conflicting pin mapping is loaded 
  - A device tree object is loaded that uses the same name for a fragment: 
helper


Any ideas?



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

[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] Debian 3.18.13-bone70 /drivers/usb/serial/option.c doesn't exist : add support for qmi_wwan

[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 <robertcnel...@gmail.com>
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
>> <https://www.google.com/search?client=ubuntu=fs=Linux+USB+Driver+Software+User+Guide=utf-8=utf-8>
>>
>> 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

[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

[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 <mat...@apana.com 
> > 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

[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 
> <matt.mahe...@hydro-care.com > 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] ppp establish connection on boot debian beaglebone black

[Matt Maher Peterson]

Solved the issue.

Removed updetatch from the ppp/peers/provider file.

>From the pppd daemon maual:

*updetach* With this option, pppd will detach from its controlling terminal
once it has successfully established the ppp connection (to the point where
the first network control protocol, usually the IP control protocol, has
come up).

Can anyone explain why this fixed my problem :)?  Solved it but not 100%
sure why this worked.


Matt Maher Peterson
APANA
w: 360.746.2276x401
c: 360.393.5549

On Wed, Dec 2, 2015 at 2:17 PM, Matt Maher Peterson <
matt.maherpeter...@hydro-care.com> wrote:

> Hi,
>
> I am using a Skywire LE910-SVG cellular modem
> <http://nimbelink.com/skywire-cellular-modem-lte/>with a BBB.
>
> I have writting chatscripts and PPP/peers provider scripts that are
> working well.  If I let the BBB boot up normally I can ssh to the device
> and 'pon verizon' to establish a ppp connection manully.  Everything works
> great.
>
> The issue I am trying to resolve is automating this on boot.  What is the
> best way to do this?
>
> Tried adding it to /etc/network/interfaces with:
>
> auto verizon
> iface verizon inet ppp0
>   provider verizon
>
> Does not seam to do anything.
>
> Have also tried to running a simple bash script to do this after the BBB
> boots
>
> #!/bin/bash
> pon verizon
>
> When I execute the script I can see everything connect but I it
> immediately terminates the connection as I can see in the output with
> Hangup (SIGHUP)
>
>  pppd[1846]: PAP authentication succeeded
>  pppd[1846]: Could not determine remote IP address: defaulting to
> 10.64.64.64
>  pppd[1846]: local  IP address 166.154.48.36
>  pppd[1846]: remote IP address 10.64.64.64
>  pppd[1846]: primary   DNS address 198.224.173.135
>  pppd[1846]: secondary DNS address 198.224.174.135
>  pppd[1860]: *Hangup (SIGHUP)*
>  pppd[1860]: Modem hangup
>  pppd[1860]: Connect time 0.0 minutes.
>  pppd[1860]: Sent 0 bytes, received 0 bytes.
>  pppd[1860]: Connection terminated.
>
>
> Any solutions out there?
>
> Kind Regards,
>
> Matt
>
> --
> 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/w5xpEcd7yOk/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.

[beagleboard] Re: Establish and maintain PPP connection on boot, BBB Debian 3.8.13-bone70

[Matt Maher Peterson]

Another not here is that when if I simply put the pon verizon command in a 
shell script:

#!/bin/bash
pon verizon

and execute the script see everthing connect but I it immediately 
terminates the connection as I can see in /var/messages after it gets its 
IP with a Hangup (SIGHUP)

 pppd[1846]: PAP authentication succeeded
 pppd[1846]: Could not determine remote IP address: defaulting to 
10.64.64.64
 pppd[1846]: local  IP address 166.154.48.36
 pppd[1846]: remote IP address 10.64.64.64
 pppd[1846]: primary   DNS address 198.224.173.135
 pppd[1846]: secondary DNS address 198.224.174.135
 pppd[1860]: Hangup (SIGHUP)
 pppd[1860]: Modem hangup
 pppd[1860]: Connect time 0.0 minutes.
 pppd[1860]: Sent 0 bytes, received 0 bytes.
 pppd[1860]: Connection terminated.


On Tuesday, November 24, 2015 at 8:17:19 AM UTC-8, Matt Maher Peterson 
wrote:
>
> Hi,
>
> I am using a Skywire LE910-SVG cellular modem   
> <http://nimbelink.com/skywire-cellular-modem-lte/>with a BBB.
>
> I have writting chatscripts and PPP/peers provider scripts that are 
> working well.  If I let the BBB boot up normaly I can ssh to the device and 
> 'pon verizon' to establish a ppp connection manully.  Everything works 
> great.
>
> The issue I am trying to resolve is automating this on boot.  What is the 
> best way to do this?
>
> Tried adding it to /etc/network/interfaces with:
>
> auto verizon
> iface verizon inet ppp0
>   provider verizon
>
> Does not seam to do anything.
>
> Any solutions out there?
>
> Kind Regards,
>
> Matt
>

-- 
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] ppp establish connection on boot debian beaglebone black

[Matt Maher Peterson]

Hi,

I am using a Skywire LE910-SVG cellular modem   
with a BBB.

I have writting chatscripts and PPP/peers provider scripts that are working 
well.  If I let the BBB boot up normally I can ssh to the device and 'pon 
verizon' to establish a ppp connection manully.  Everything works great.

The issue I am trying to resolve is automating this on boot.  What is the 
best way to do this?

Tried adding it to /etc/network/interfaces with:

auto verizon
iface verizon inet ppp0
  provider verizon

Does not seam to do anything.

Have also tried to running a simple bash script to do this after the BBB 
boots

#!/bin/bash
pon verizon

When I execute the script I can see everything connect but I it immediately 
terminates the connection as I can see in the output with Hangup (SIGHUP)

 pppd[1846]: PAP authentication succeeded
 pppd[1846]: Could not determine remote IP address: defaulting to 
10.64.64.64
 pppd[1846]: local  IP address 166.154.48.36
 pppd[1846]: remote IP address 10.64.64.64
 pppd[1846]: primary   DNS address 198.224.173.135
 pppd[1846]: secondary DNS address 198.224.174.135
 pppd[1860]: *Hangup (SIGHUP)*
 pppd[1860]: Modem hangup
 pppd[1860]: Connect time 0.0 minutes.
 pppd[1860]: Sent 0 bytes, received 0 bytes.
 pppd[1860]: Connection terminated.


Any solutions out there?

Kind Regards,

Matt

-- 
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] Establish and maintain PPP connection on boot, BBB Debian 3.8.13-bone70

[Matt Maher Peterson]

Hi,

I am using a Skywire LE910-SVG cellular modem   
with a BBB.

I have writting chatscripts and PPP/peers provider scripts that are working 
well.  If I let the BBB boot up normaly I can ssh to the device and 'pon 
verizon' to establish a ppp connection manully.  Everything works great.

The issue I am trying to resolve is automating this on boot.  What is the 
best way to do this?

Tried adding it to /etc/network/interfaces with:

auto verizon
iface verizon inet ppp0
  provider verizon

Does not seam to do anything.

Any solutions out there?

Kind Regards,

Matt

-- 
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] REV C Beagleone image flash: Won't take on different rev C boards?

[Matt Maher Peterson]

Hi Robert,

I am attempting this process again but now am getting:

/opt/scripts/tools# ./beaglebone-black-eMMC-flasher.sh 
Error: script halting, system unrecognized...

How do I fix this?


On Thursday, September 10, 2015 at 1:33:00 PM UTC-7, Matt Maher Peterson 
wrote:
>
> Thanks that worked very well.
>
> Owe you a beer! 
>
> Kind Regards.
>
> On Thursday, September 10, 2015 at 11:15:40 AM UTC-7, RobertCNelson wrote:
>>
>> On Thu, Sep 10, 2015 at 12:58 PM, Matt Maher Peterson 
>> <matt.mahe...@hydro-care.com> wrote: 
>> > Sorry I should have been more clear. 
>> > 
>> > So on a known good beaglebone that I have my custom debian installed on 
>> how 
>> > do I make a copy of this on uSD card such that I flash another BBB with 
>> a 
>> > different emmc chip. 
>> > 
>> > Is the workflow like this: 
>> > 1. Boot up known good Kingston BBB with custom image. 
>> > 2. Insert a uSD card => 4GB 
>> > 3. execute  /opt/scripts/tools/ 
>> git pull 
>> > 4. execute  /opt/scripts/tools/eMMC# 
>> > ./beaglebone-black-make-microSD-flasher-from-eMMC.sh 
>> > 5. Insert this card into a new BBB that needs to be flashed? 
>> > 
>> > Am I understanding this properly? 
>>
>> Correct ;) 
>>
>> 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] REV C Beagleone image flash: Won't take on different rev C boards?

[Matt Maher Peterson]

Not sure I am following are you saying run a different script?

Sorry I am noob...

I tried the init-eMMC-flasher.sh and get the same result.

On Tuesday, October 6, 2015 at 1:43:46 PM UTC-7, RobertCNelson wrote:
>
> On Tue, Oct 6, 2015 at 3:36 PM, Matt Maher Peterson 
> <matt.mahe...@hydro-care.com > wrote: 
> > Hi Robert, 
> > 
> > I am attempting this process again but now am getting: 
> > 
> > /opt/scripts/tools# ./beaglebone-black-eMMC-flasher.sh 
> > Error: script halting, system unrecognized... 
> > 
> > How do I fix this? 
>
> that one is eol... 
>
> look at the previous emails.. 
>
> 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] REV C Beagleone image flash: Won't take on different rev C boards?

[Matt Maher Peterson]

Ok I see now.  Use the script that is /opt/scripts/tools/emmc.

One more question.  The reason I was trying this tool again is that my 
custom debian image stopped auto connecting to my computer via usb.
I am running Ubuntu on my desktop and the little network icon just seams to 
be cycling thru trying to establish a connection.  It never seams to quite 
get there.

Any ideas?

On Tuesday, October 6, 2015 at 2:06:55 PM UTC-7, RobertCNelson wrote:
>
> On Tue, Oct 6, 2015 at 4:02 PM, Matt Maher Peterson 
> <matt.mahe...@hydro-care.com > wrote: 
> > Not sure I am following are you saying run a different script? 
> > 
> > Sorry I am noob... 
> > 
> > I tried the init-eMMC-flasher.sh and get the same result. 
>
> We went over this a month ago... look in the "eMMC" directory above.. 
>
> and read the readme.md (git pull) to get the latest.. 
>
> 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] REV C Beagleone image flash: Won't take on different rev C boards?

[Matt Maher Peterson]

Hi,

I have a debian image I built with custom device tree and code that I have 
created.  I have copied and flashed this onto new beaglebones using this 
tool:

http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents

This worked great untill a recent shipment of BBB REV C from element 14.  I 
can see a difference a between the two boards where the emmc chips are 
different the 'old rev c' has a kingston chip whereas the 'new rev c' has a 
different one with a number 4LA18 JWA06 and M with a circle.

When I use the tool mentioned above I get the proper led sequence tell me 
the emmc is being flashed (blinking once a second, then goes solid when 
finished).  On these new board the LED sequence starts off right but goes 
solids very quickly and seemingly no image has been copied?

What am I missing here??

Cheers,

Matt

-- 
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] REV C Beagleone image flash: Won't take on different rev C boards?

[Matt Maher Peterson]

rsync flashers?  could you provide more info or link?

Thanks

On Thursday, September 10, 2015 at 9:46:05 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Sep 10, 2015 at 11:41 AM, Matt Maher Peterson 
> <matt.mahe...@hydro-care.com > wrote: 
> > Hi, 
> > 
> > I have a debian image I built with custom device tree and code that I 
> have 
> > created.  I have copied and flashed this onto new beaglebones using this 
> > tool: 
> > 
> > http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents 
> > 
> > This worked great untill a recent shipment of BBB REV C from element 14. 
>  I 
> > can see a difference a between the two boards where the emmc chips are 
> > different the 'old rev c' has a kingston chip whereas the 'new rev c' 
> has a 
> > different one with a number 4LA18 JWA06 and M with a circle. 
> > 
> > When I use the tool mentioned above I get the proper led sequence tell 
> me 
> > the emmc is being flashed (blinking once a second, then goes solid when 
> > finished).  On these new board the LED sequence starts off right but 
> goes 
> > solids very quickly and seemingly no image has been copied? 
> > 
> > What am I missing here?? 
>
> Nand/eMMC vary in size, the current eMMC's being used range in sizes: 
>
> #Micron 3744MB (bbb): 3925868544 bytes -> 3925.86 Megabyte 
> #Kingston 3688MB (bbb): 3867148288 bytes -> 3867.15 Megabyte 
> #Kingston 3648MB (bbb): 3825205248 bytes -> 3825.21 Megabyte 
>
> dd based image tools can't handle this. Use the rsync "flashers"... 
>
> 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] REV C Beagleone image flash: Won't take on different rev C boards?

[Matt Maher Peterson]

Sorry I should have been more clear.

So on a known good beaglebone that I have my custom debian installed on how 
do I make a copy of this on uSD card such that I flash another BBB with a 
different emmc chip.

Is the workflow like this:
1. Boot up known good Kingston BBB with custom image.
2. Insert a uSD card => 4GB
3. execute  /opt/scripts/tools/eMMC# 
./beaglebone-black-make-microSD-flasher-from-eMMC.sh 
4. Insert this card into a new BBB that needs to be flashed?

Am I understanding this properly?


On Thursday, September 10, 2015 at 10:46:25 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Sep 10, 2015 at 11:58 AM, Matt Maher Peterson 
> <matt.mahe...@hydro-care.com > wrote: 
> > rsync flashers?  could you provide more info or link? 
>
> For this flasher image: 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29 
>
> This rsync based script is what runs behind the scenes.. 
>
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh
>  
>
> 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] REV C Beagleone image flash: Won't take on different rev C boards?

[Matt Maher Peterson]

Thanks that worked very well.

Owe you a beer! 

Kind Regards.

On Thursday, September 10, 2015 at 11:15:40 AM UTC-7, RobertCNelson wrote:
>
> On Thu, Sep 10, 2015 at 12:58 PM, Matt Maher Peterson 
> <matt.mahe...@hydro-care.com > wrote: 
> > Sorry I should have been more clear. 
> > 
> > So on a known good beaglebone that I have my custom debian installed on 
> how 
> > do I make a copy of this on uSD card such that I flash another BBB with 
> a 
> > different emmc chip. 
> > 
> > Is the workflow like this: 
> > 1. Boot up known good Kingston BBB with custom image. 
> > 2. Insert a uSD card => 4GB 
> > 3. execute  /opt/scripts/tools/ 
> git pull 
> > 4. execute  /opt/scripts/tools/eMMC# 
> > ./beaglebone-black-make-microSD-flasher-from-eMMC.sh 
> > 5. Insert this card into a new BBB that needs to be flashed? 
> > 
> > Am I understanding this properly? 
>
> Correct ;) 
>
> 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] Choosing linux distro for IoT on Beaglebone Black

[Matt Maher Peterson]

I am working on an IoT application for the Beaglebone Black that monitors a 
number of sensors.

Having worked with a number of different linux images I am having trouble 
choosing the best fit for my use.

Requriements are:

   - stable
   - easy to manage GPIO


   - I am familiar with device tree overlays in the older 3.8.x distros but 
   not with how to manage custom cape GPIO on the newer distros

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

[beagleboard] Powering down a Beaglebone black that is being powered from a LiPo battery

[Matt Maher Peterson]

Hi,

Working a beaglebone black that I am trying to power both with a wall wart 
and with LiPo battery thru the TPS functionality.  I have all the power 
working well except that I cannot get the damn thing to power down from the 
power switch on the board.  Holding the switch down for 8 seconds causes 
the thing to power down momentarily but then it power back up.  Any idea 
how to work around this?

One piece of information I found with respect to this issue was on this 
forum where someone said:

...
Regarding the lithium battery pack idea, it's a good one 


*except for one little issue with the bone where a rework is required in 
order to power down into TPS65217 OFF or SLEEP modes when a battery is 
connected due to SYS voltage staying present and the way 3.3V_EXP is 
generated.* So
long as you don't want to power off with the battery still connected
there's no issue, though.

Anyone know what this workaround is or where I could find info on it? 

Cheers!

MMP

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