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

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

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

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

Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70

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

Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70

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

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

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

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

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

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

rmware 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 &g

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Re: [beagleboard] ppp establish connection on boot debian beaglebone black

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

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

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 Skywi

[beagleboard] ppp establish connection on boot debian beaglebone black

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

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

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

Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?

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

Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?

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

Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?

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 followi

[beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?

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

Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?

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

Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?

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

Re: [beagleboard] REV C Beagleone image flash: Won't take on different rev C boards?

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 mor

[beagleboard] Choosing linux distro for IoT on Beaglebone Black

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

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

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