Re: [beagleboard] UARTS in kernel 4.4: no /dev/ttO* ?
Don't think the ttyS's are it. I know for sure in 3.18 you use the /ttyO2 or whatever number uart you enable. On Thursday, August 18, 2016 at 3:18:43 PM UTC-7, Mike Bell wrote: > > On 08/18/2016 05:57 PM, Matt wrote: > > Hi, > > > > Working in kernel 4.4.16-bone-rt-r11 and am not seeing the > > corresponding entries in /dev/ for the enabled UARTS. > > > > /dev/tty13 /dev/tty24/dev/tty35 /dev/tty46/dev/tty57 > /dev/ttyS0 > > /dev/tty14 /dev/tty25/dev/tty36 /dev/tty47/dev/tty58 > /dev/ttyS1 > > /dev/tty15 /dev/tty26/dev/tty37 /dev/tty48/dev/tty59 > /dev/ttyS2 > > /dev/tty16 /dev/tty27/dev/tty38 /dev/tty49/dev/tty6 /dev/ttyS3 > > /dev/tty17 /dev/tty28/dev/tty39 /dev/tty5/dev/tty60 /dev/ttyS4 > > /dev/tty18 /dev/tty29/dev/tty4 /dev/tty50/dev/tty61 > /dev/ttyS5 > > > > > > What am I missing here? When a UART is loaded into slots should it > > then be labeld ttyOX in /dev just as in 3.18? > > -- > > /dev/ttyS? > > Mike > -- 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/e2e3640a-cb58-4d8a-b648-75424dab7c5c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] ADC in kernel 4.4
Thanks! For those that have custom dtbo's to load in addition, comma seperate their names in /boot/uEnv.txt: cape_enable=bone_capemgr.enable_partno=BB-ADC,*your-cape-name-here* On Thursday, August 4, 2016 at 1:56:20 PM UTC-7, RobertCNelson wrote: > > On Thu, Aug 4, 2016 at 3:48 PM, Matt99eo > > wrote: > > What is the latest on using ADC in kernel 4.4? > > > > I see their is is not BB-ADC in /lib/firmware. > > sudo apt-get update ; sudo apt-get install bb-cape-overlays > > > How do I get this rolling in 4.4? > > /boot/uEnv.txt > > cape_enable=bone_capemgr.enable_partno=BB-ADC > > reboot.. > > debian@beaglebone:~$ dmesg | grep cape > [0.00] Kernel command line: console=ttyO0,115200n8 > bone_capemgr.enable_partno=BB-ADC root=/dev/mmcblk0p1 ro > rootfstype=ext4 rootwait coherent_pool=1M cape_universal=enable > [4.331469] bone_capemgr bone_capemgr: Baseboard: > 'A335BNLT,BBG1,BBG116043766' > [4.338743] bone_capemgr bone_capemgr: > compatible-baseboard=ti,beaglebone-black - #slots=4 > [4.404125] bone_capemgr bone_capemgr: slot #0: No cape found > [4.464122] bone_capemgr bone_capemgr: slot #1: No cape found > [4.524122] bone_capemgr bone_capemgr: slot #2: No cape found > [4.584122] bone_capemgr bone_capemgr: slot #3: No cape found > [4.589903] bone_capemgr bone_capemgr: enabled_partno PARTNO > 'BB-ADC' VER 'N/A' PR '0' > [4.597857] bone_capemgr bone_capemgr: slot #4: override > [4.603196] bone_capemgr bone_capemgr: Using override eeprom data at > slot 4 > [4.610192] bone_capemgr bone_capemgr: slot #4: 'Override Board > Name,00A0,Override Manuf,BB-ADC' > [4.619302] bone_capemgr bone_capemgr: initialized OK. > [5.646166] bone_capemgr bone_capemgr: slot #4: dtbo > 'BB-ADC-00A0.dtbo' loaded; overlay id #0 > > > debian@beaglebone:/sys/bus/iio/devices/iio:device0$ tail in_* > ==> in_voltage0_raw <== > 3903 > > ==> in_voltage1_raw <== > 3562 > > ==> in_voltage2_raw <== > 3815 > > ==> in_voltage3_raw <== > 2611 > > ==> in_voltage4_raw <== > 2381 > > ==> in_voltage5_raw <== > 2728 > > ==> in_voltage6_raw <== > 2810 > > 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/1ae2ff5a-cac2-46fc-9a1d-5482e7c5d9ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] ADC in kernel 4.4
What is the latest on using ADC in kernel 4.4? I see their is is not BB-ADC in /lib/firmware. How do I get this rolling in 4.4? -- 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/b5e81d43-6775-4676-9082-fd5b3bc51715%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] 4.1.21 pause during boot: A start job is running for LSB: Raise network interf...
Did that. All lines in /etc/network/interfaces are commented out. Still getting the LSB Here is a screenshot: <https://lh3.googleusercontent.com/-zsnvV_cekKg/V6JYuB8nCKI/BF8/hInYEKI4xgIt_I3JwJuzZGpSh_rFyGZpgCLcB/s1600/LSB.png> Is it because the it because it find the eth0 phy but and is trying to give a IPv6? On Wednesday, August 3, 2016 at 11:57:18 AM UTC-7, RobertCNelson wrote: > > On Wed, Aug 3, 2016 at 1:46 PM, Matt99eo > > wrote: > > Bump. > > > > Anybody found a good fix for this? I am now in 4.4 land and it seams to > > hang even longer Quite annoying. I don't use eth0 as my devices > talk > > over a cellular network... > > make sure eth0 is not defined in /etc/network/interfaces > > 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/5fcf50e4-c115-4249-ae4a-ef1bab810d61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] 4.1.21 pause during boot: A start job is running for LSB: Raise network interf...
Bump. Anybody found a good fix for this? I am now in 4.4 land and it seams to hang even longer Quite annoying. I don't use eth0 as my devices talk over a cellular network... On Thursday, May 26, 2016 at 4:26:54 PM UTC-7, Rick M wrote: > > > On May 26, 2016, at 08:47 , Matt99eo > wrote: > > > > Why does the kernel pause for a will (10s) while booting. I see the > pause in line noted in red below. Something to to with phy 4a101000? > > > > r 10.287710] net eth0: initializing cpsw version 1.12 (0) > > [ 10.295460] net eth0: phy found : id is : 0x7c0f1 > > [ 10.300245] libphy: PHY 4a101000.mdio:01 not found > > [ 10.305086] net eth0: phy 4a101000.mdio:01 not found on slave 1 > > [ 10.315002] net eth0: BQL enabled > > [ 10.322353] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > > [] A start job is running for LSB: Raise network interf...31s / > limit)[ 37.822466] random: nonblocking pool is initialized > > If there's no Ethernet connected, it will pause there for a long time. I > think it's looking for DHCP. It's possible to configure this to skip this > at boot and support hot-plug, but the distro is (IMHO unfortunately) not > configured this way. > > > > -- > Rick Mann > rm...@latencyzero.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/5e600e98-bde2-406f-8626-82197f338311%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] 4.1 or 4.4 kernel for best stability and feature support on BBB
Thanks Robert. Was just typing a reply that I found that on on line 200 of the script: https://github.com/RobertCNelson/boot-scripts/blob/master/tools/update_kernel.sh#L200 Its running now and just completed. reboot shows that it worked. Most appreciated once again! On Wednesday, August 3, 2016 at 10:56:25 AM UTC-7, RobertCNelson wrote: > > On Wed, Aug 3, 2016 at 12:29 PM, Matt99eo > > wrote: > > Thanks for confirming my suspicion... > > > > To update kernel should I use /opt/scripts/tools/./update_kernel.sh ? > > > > Tried that and it looks it went for the latest 4.6.5 > > > > Questions: > > - Can I tell this script to use 4.4.16-bone-rt-r11 > > ./update_kernel.sh --lts-4_4 > > I've updated the script to be more vocal about options: > > > https://github.com/RobertCNelson/boot-scripts/commit/f79a2f90e3cbffc0c5243e646e728dacf2f51e82 > > > With no cmdline options it defaults to "--stable"... > > > - Is this the best way to update or should I recompile using > > 4.4.16-bone-rt-r11 and port all my stuff into it? > > > - What does the 'is currently unavailable on [rcn-ee.com/repos] means > in > > output below? > > That's just to prevent race conditions, in the past my cable modem > hasn't been the fastest network connection.. > > It's there now: > > > http://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/linux-image-4.6.5-bone-rt-r3_1jessie_armhf.deb > > > 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/cc242446-ea03-45b3-875f-c82a00361675%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] 4.1 or 4.4 kernel for best stability and feature support on BBB
Thanks for confirming my suspicion... To update kernel should I use /opt/scripts/tools/./update_kernel.sh ? Tried that and it looks it went for the latest 4.6.5 Questions: - Can I tell this script to use 4.4.16-bone-rt-r11 - Is this the best way to update or should I recompile using 4.4.16-bone-rt-r11 and port all my stuff into it? - What does the 'is currently unavailable on [rcn-ee.com/repos] means in output below? Here is the output of the update_kernel.sh root@arm:/opt/scripts/tools# ./update_kernel.sh info: checking archive 2016-08-03 17:13:26 URL:https://rcn-ee.com/repos/latest/jessie-armhf/LATEST-bone-rt [92/92] -> "LATEST-bone-rt" [1] - Kernel Options: ABI:1 LTS41 4.1.28-bone-rt-r22 ABI:1 LTS44 4.4.16-bone-rt-r11 ABI:1 STABLE 4.6.5-bone-rt-r3 - info: you are running: [4.1.21-bone-rt-r20], latest is: [4.6.5-bone-rt-r3] updating... Hit http://security.debian.org jessie/updates InRelease Hit http://repos.rcn-ee.com jessie InRelease Ign http://httpredir.debian.org jessie InRelease Get:1 http://security.debian.org jessie/updates/main armhf Packages [359 kB] Hit http://httpredir.debian.org jessie-updates InRelease Get:2 http://repos.rcn-ee.com jessie/main armhf Packages [552 kB] Hit http://httpredir.debian.org jessie Release.gpg Get:3 http://security.debian.org jessie/updates/contrib armhf Packages [994 B] Get:4 http://security.debian.org jessie/updates/non-free armhf Packages [20 B] Hit http://httpredir.debian.org jessie Release Get:5 http://httpredir.debian.org jessie-updates/main armhf Packages [17.6 kB] Get:6 http://httpredir.debian.org jessie-updates/contrib armhf Packages [20 B] Get:7 http://httpredir.debian.org jessie-updates/non-free armhf Packages [450 B] Get:8 http://httpredir.debian.org jessie/main armhf Packages [8,832 kB] Get:9 http://httpredir.debian.org jessie/non-free armhf Packages [74.6 kB] Get:10 http://httpredir.debian.org jessie/contrib armhf Packages [44.7 kB] Fetched 9,881 kB in 12s (821 kB/s) Reading package lists... Done Checking dpkg... Checking apt-cache... info: [linux-image-4.6.5-bone-rt-r3] (latest) is currently unavailable on [rcn-ee.com/repos] -- 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/4c8e912a-9aae-4927-afe3-775c4f1ba1e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: kernel panic when cloning a BBB using beaglebone-black-make-microSD-flasher-from-eMMC.sh
Hi there, This has been solved by RC Nelson. If you encounter this bug simply git the latest version of beaglebone-black-make-microSD-flasher-from-eMMC.sh by executing a git pull command while in /opt/scripts/tools Thanks again RC! On Wednesday, July 27, 2016 at 2:26:45 PM UTC-7, Matt99eo wrote: > > Hi, > > Been trying to clone a debian 8.4 running kernel 4.1.x using the RC Nelson > script beaglebone-black-make-microSD-flasher-from-eMMC.sh > > I have ensured that I have the latest script (git pull when in > /opt/scripts/tools) > I have ensured the BBB I am cloning has a network connection during the > process. > > > When I insert he new uSD card into a new BBB to flash it it ends quickly > with a kernel panic. > > Here is the serial debug output: > > Starting eMMC Flasher from microSD media > Version: [1.20160718: mkfs.ext4 1.43...] > - > Checking for Valid bbb-eeprom header > Valid bbb-eeprom header found [335] > - > copying: [/dev/mmcblk0] -> [/dev/mmcblk1] > lsblk: > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > mmcblk1boot0 179:16 01M 1 disk > mmcblk1boot1 179:24 01M 1 disk > mmcblk0 179:00 7.2G 0 disk > `-mmcblk0p1 179:10 7.2G 0 part / > mmcblk1 179:80 3.7G 0 disk > - > df -h | grep rootfs: > - > Erasing: /dev/mmcblk1 > 108+0 records in > 108+0 records out > 113246208 bytes (113 MB) copied, 17.7061 s, 6.4 MB/s > [ 34.099130] random: nonblocking pool is initialized > 108+0 records in > 108+0 records out > 113246208 bytes (113 MB) copied, 4.35786 s, 26.0 MB/s > Erasing: /dev/mmcblk1 complete > - > Writing bootloader to [/dev/mmcblk1] > dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k > - > dd: failed to open '': No such file or directory[ 35.897114] Kernel > panic - not syncing: Attempted to kill init! exitcode=0x0100 > [ 35.897114] > [ 35.911129] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted > 4.1.21-bone-rt-r20 #1 > [ 35.918639] Hardware name: Generic AM33XX (Flattened Device Tree) > [ 35.924801] [] (unwind_backtrace) from [] > (show_stack+0x11/0x14) > [ 35.932590] [] (show_stack) from [] > (panic+0x6d/0x188) > [ 35.939500] [] (panic) from [] > (complete_and_exit+0x1/0x18) > [ 35.946844] [] (complete_and_exit) from [] > (sigprocmask+0x59/0x88) > [ 35.954801] [] (sigprocmask) from [<0001>] (0x1) > [ 35.960665] ---[ end Kernel panic - not syncing: Attempted to kill > init! exitcode=0x0100 > [ 35.960665] > > The line I've highlighed in yellow seams to be the problem. > Why is the cloning script getting a bootloader in here? > > Any help much 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/122f63a2-d5ce-4300-8ef1-3473e1f07cf1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] kernel panic when cloning a BBB using beaglebone-black-make-microSD-flasher-from-eMMC.sh
I am noob+ so I'll give'r it a whirl :) On Wednesday, July 27, 2016 at 3:36:26 PM UTC-7, William Hermans wrote: > > One thing that does come to mind that you can try. Would be to get one of > the latest Jessie flasher images. Then flash that to eMMC. Afterwords, wipe > the rootfs, create a tar backup of the rootfs you want on the eMMC, then > tar that over to the eMMC. But as a Linux newb that might be easier said > than done. > > Perhaps I'll experiment with that sometime this evening if I find the > time. > > On Wed, Jul 27, 2016 at 3:31 PM, William Hermans > wrote: > >> Same method you're using, but if= needs to point to a suitable MLO file. >> That is: I'm guessing based on the count and bs of that particular dd line. >> I only say I would probably never use Robert's script to do this as I do >> not know what he script does, and I am very particular in how my >> beaglebones are setup. SO instead of reading through his script, I would >> write my own script. Since I know what needs being done. >> >> As to other methods I'd use. Well technically I've never written to an >> eMMC yet. Others here probably have more hands on than I in regards to the >> eMMC. However, as I mention above. I know what needs doing, and how to do >> it. Which is something really too complex to just tell someone without >> experience how to do. Unless I've tested it first. Which won't happen any >> time soon. >> >> So we're back to square 1. >> >> On Wed, Jul 27, 2016 at 3:23 PM, Matt99eo > > wrote: >> >>> OK could could you reccomend another way to accomplish my objective that >>> does work? >>> >>> Thanks for your input! >>> >>> On Wednesday, July 27, 2016 at 3:18:19 PM UTC-7, William Hermans wrote: >>>> >>>> I know nothing of Robert's eMMC flasher script. I would probably never >>>> use it. But thus far have not used it. However, the reason why dd error'd >>>> out is as I said in my last post. It needs an input file in order to work. >>>> >>>> On Wed, Jul 27, 2016 at 3:13 PM, Matt99eo >>>> wrote: >>>> >>>>> But isn't the script >>>>> -- beaglebone-black-make-microSD-flasher-from-eMMC.sh -- supposed do do >>>>> that? >>>>> >>>>> Do I need to manually add this in? Sorry noob here I don't >>>>> understand. I see the problem. But I don't know how to solve it, hence >>>>> asking for help :) >>>>> >>>>> On Wednesday, July 27, 2016 at 3:10:48 PM UTC-7, William Hermans wrote: >>>>>> >>>>>> dd: failed to open '': No such file or directory[ 35.897114] Kernel >>>>>>> panic - not syncing: Attempted to kill init! exitcode=0x0100 >>>>>>> >>>>>> >>>>>> That's why. It can't find a file or directory. And here is why: >>>>>> >>>>>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k >>>>>>> >>>>>> >>>>>> See the problem ? Where's the input file ? " " ? >>>>>> >>>>>> On Wed, Jul 27, 2016 at 2:51 PM, Matt99eo < >>>>>> matt.mahe...@hydro-care.com> wrote: >>>>>> >>>>>>> I mean why isn't the boot loader getting on the uSD I've created >>>>>>> using the script? I know why it needs to be there... >>>>>>> >>>>>>> How do I solve this such that I can slam the created uSD into a new >>>>>>> BBB and have flash eMMC? >>>>>>> >>>>>>> On Wednesday, July 27, 2016 at 2:46:30 PM UTC-7, William Hermans >>>>>>> wrote: >>>>>>>> >>>>>>>> The line I've highlighed in yellow seams to be the problem. >>>>>>>>> Why is the cloning script getting a bootloader in here? >>>>>>>>> >>>>>>>>> Any help much appreciated! >>>>>>>>> >>>>>>>> >>>>>>>> What do you mean "why?" ? Short answer is that a bootloader( >>>>>>>> actually two - first and second stage ) is required to boot from eMMC. >>>>>>>> >>>>>>>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k is i
Re: [beagleboard] kernel panic when cloning a BBB using beaglebone-black-make-microSD-flasher-from-eMMC.sh
OK could could you reccomend another way to accomplish my objective that does work? Thanks for your input! On Wednesday, July 27, 2016 at 3:18:19 PM UTC-7, William Hermans wrote: > > I know nothing of Robert's eMMC flasher script. I would probably never use > it. But thus far have not used it. However, the reason why dd error'd out > is as I said in my last post. It needs an input file in order to work. > > On Wed, Jul 27, 2016 at 3:13 PM, Matt99eo > wrote: > >> But isn't the script >> -- beaglebone-black-make-microSD-flasher-from-eMMC.sh -- supposed do do >> that? >> >> Do I need to manually add this in? Sorry noob here I don't understand. >> I see the problem. But I don't know how to solve it, hence asking for help >> :) >> >> On Wednesday, July 27, 2016 at 3:10:48 PM UTC-7, William Hermans wrote: >>> >>> dd: failed to open '': No such file or directory[ 35.897114] Kernel >>>> panic - not syncing: Attempted to kill init! exitcode=0x0100 >>>> >>> >>> That's why. It can't find a file or directory. And here is why: >>> >>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k >>>> >>> >>> See the problem ? Where's the input file ? " " ? >>> >>> On Wed, Jul 27, 2016 at 2:51 PM, Matt99eo >>> wrote: >>> >>>> I mean why isn't the boot loader getting on the uSD I've created using >>>> the script? I know why it needs to be there... >>>> >>>> How do I solve this such that I can slam the created uSD into a new BBB >>>> and have flash eMMC? >>>> >>>> On Wednesday, July 27, 2016 at 2:46:30 PM UTC-7, William Hermans wrote: >>>>> >>>>> The line I've highlighed in yellow seams to be the problem. >>>>>> Why is the cloning script getting a bootloader in here? >>>>>> >>>>>> Any help much appreciated! >>>>>> >>>>> >>>>> What do you mean "why?" ? Short answer is that a bootloader( actually >>>>> two - first and second stage ) is required to boot from eMMC. >>>>> >>>>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k is in reference to MLO >>>>> I believe. uboot.img is roughly 348k as I recall. >>>>> >>>>> On Wed, Jul 27, 2016 at 2:26 PM, Matt99eo >>>> > wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Been trying to clone a debian 8.4 running kernel 4.1.x using the RC >>>>>> Nelson script beaglebone-black-make-microSD-flasher-from-eMMC.sh >>>>>> >>>>>> I have ensured that I have the latest script (git pull when in >>>>>> /opt/scripts/tools) >>>>>> I have ensured the BBB I am cloning has a network connection during >>>>>> the process. >>>>>> >>>>>> >>>>>> When I insert he new uSD card into a new BBB to flash it it ends >>>>>> quickly with a kernel panic. >>>>>> >>>>>> Here is the serial debug output: >>>>>> >>>>>> Starting eMMC Flasher from microSD media >>>>>> Version: [1.20160718: mkfs.ext4 1.43...] >>>>>> - >>>>>> Checking for Valid bbb-eeprom header >>>>>> Valid bbb-eeprom header found [335] >>>>>> - >>>>>> copying: [/dev/mmcblk0] -> [/dev/mmcblk1] >>>>>> lsblk: >>>>>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>>>>> mmcblk1boot0 179:16 01M 1 disk >>>>>> mmcblk1boot1 179:24 01M 1 disk >>>>>> mmcblk0 179:00 7.2G 0 disk >>>>>> `-mmcblk0p1 179:10 7.2G 0 part / >>>>>> mmcblk1 179:80 3.7G 0 disk >>>>>> - >>>>>> df -h | grep rootfs: >>>>>> - >>>>>> Erasing: /dev/mmcblk1 >>>>>> 108+0 records in >>>>>> 108+0 records out >>>>>> 113246208 bytes (113 MB) copied, 17.7061 s, 6.4 MB/s >>>>>> [ 34.099130] random: nonblocking pool is initialized >>>>>> 108+0 records in >>>>>> 108+0 records out >>>>>&
Re: [beagleboard] kernel panic when cloning a BBB using beaglebone-black-make-microSD-flasher-from-eMMC.sh
But isn't the script -- beaglebone-black-make-microSD-flasher-from-eMMC.sh -- supposed do do that? Do I need to manually add this in? Sorry noob here I don't understand. I see the problem. But I don't know how to solve it, hence asking for help :) On Wednesday, July 27, 2016 at 3:10:48 PM UTC-7, William Hermans wrote: > > dd: failed to open '': No such file or directory[ 35.897114] Kernel >> panic - not syncing: Attempted to kill init! exitcode=0x0100 >> > > That's why. It can't find a file or directory. And here is why: > > dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k >> > > See the problem ? Where's the input file ? " " ? > > On Wed, Jul 27, 2016 at 2:51 PM, Matt99eo > wrote: > >> I mean why isn't the boot loader getting on the uSD I've created using >> the script? I know why it needs to be there... >> >> How do I solve this such that I can slam the created uSD into a new BBB >> and have flash eMMC? >> >> On Wednesday, July 27, 2016 at 2:46:30 PM UTC-7, William Hermans wrote: >>> >>> The line I've highlighed in yellow seams to be the problem. >>>> Why is the cloning script getting a bootloader in here? >>>> >>>> Any help much appreciated! >>>> >>> >>> What do you mean "why?" ? Short answer is that a bootloader( actually >>> two - first and second stage ) is required to boot from eMMC. >>> >>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k is in reference to MLO I >>> believe. uboot.img is roughly 348k as I recall. >>> >>> On Wed, Jul 27, 2016 at 2:26 PM, Matt99eo >>> wrote: >>> >>>> Hi, >>>> >>>> Been trying to clone a debian 8.4 running kernel 4.1.x using the RC >>>> Nelson script beaglebone-black-make-microSD-flasher-from-eMMC.sh >>>> >>>> I have ensured that I have the latest script (git pull when in >>>> /opt/scripts/tools) >>>> I have ensured the BBB I am cloning has a network connection during the >>>> process. >>>> >>>> >>>> When I insert he new uSD card into a new BBB to flash it it ends >>>> quickly with a kernel panic. >>>> >>>> Here is the serial debug output: >>>> >>>> Starting eMMC Flasher from microSD media >>>> Version: [1.20160718: mkfs.ext4 1.43...] >>>> - >>>> Checking for Valid bbb-eeprom header >>>> Valid bbb-eeprom header found [335] >>>> - >>>> copying: [/dev/mmcblk0] -> [/dev/mmcblk1] >>>> lsblk: >>>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >>>> mmcblk1boot0 179:16 01M 1 disk >>>> mmcblk1boot1 179:24 01M 1 disk >>>> mmcblk0 179:00 7.2G 0 disk >>>> `-mmcblk0p1 179:10 7.2G 0 part / >>>> mmcblk1 179:80 3.7G 0 disk >>>> - >>>> df -h | grep rootfs: >>>> - >>>> Erasing: /dev/mmcblk1 >>>> 108+0 records in >>>> 108+0 records out >>>> 113246208 bytes (113 MB) copied, 17.7061 s, 6.4 MB/s >>>> [ 34.099130] random: nonblocking pool is initialized >>>> 108+0 records in >>>> 108+0 records out >>>> 113246208 bytes (113 MB) copied, 4.35786 s, 26.0 MB/s >>>> Erasing: /dev/mmcblk1 complete >>>> - >>>> Writing bootloader to [/dev/mmcblk1] >>>> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k >>>> - >>>> dd: failed to open '': No such file or directory[ 35.897114] Kernel >>>> panic - not syncing: Attempted to kill init! exitcode=0x0100 >>>> [ 35.897114] >>>> [ 35.911129] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted >>>> 4.1.21-bone-rt-r20 #1 >>>> [ 35.918639] Hardware name: Generic AM33XX (Flattened Device Tree) >>>> [ 35.924801] [] (unwind_backtrace) from [] >>>> (show_stack+0x11/0x14) >>>> [ 35.932590] [] (show_stack) from [] >>>> (panic+0x6d/0x188) >>>> [ 35.939500] [] (panic) from [] >>>> (complete_and_exit+0x1/0x18) >>>> [ 35.946844] [] (complete_and_exit) from [] >>>> (sigprocmask+0x59/0x88) >>>> [ 35.954801] [] (sigprocmask) from [<0001>] (0x1) >
Re: [beagleboard] kernel panic when cloning a BBB using beaglebone-black-make-microSD-flasher-from-eMMC.sh
I mean why isn't the boot loader getting on the uSD I've created using the script? I know why it needs to be there... How do I solve this such that I can slam the created uSD into a new BBB and have flash eMMC? On Wednesday, July 27, 2016 at 2:46:30 PM UTC-7, William Hermans wrote: > > The line I've highlighed in yellow seams to be the problem. >> Why is the cloning script getting a bootloader in here? >> >> Any help much appreciated! >> > > What do you mean "why?" ? Short answer is that a bootloader( actually two > - first and second stage ) is required to boot from eMMC. > > dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k is in reference to MLO I > believe. uboot.img is roughly 348k as I recall. > > On Wed, Jul 27, 2016 at 2:26 PM, Matt99eo > wrote: > >> Hi, >> >> Been trying to clone a debian 8.4 running kernel 4.1.x using the RC >> Nelson script beaglebone-black-make-microSD-flasher-from-eMMC.sh >> >> I have ensured that I have the latest script (git pull when in >> /opt/scripts/tools) >> I have ensured the BBB I am cloning has a network connection during the >> process. >> >> >> When I insert he new uSD card into a new BBB to flash it it ends quickly >> with a kernel panic. >> >> Here is the serial debug output: >> >> Starting eMMC Flasher from microSD media >> Version: [1.20160718: mkfs.ext4 1.43...] >> - >> Checking for Valid bbb-eeprom header >> Valid bbb-eeprom header found [335] >> - >> copying: [/dev/mmcblk0] -> [/dev/mmcblk1] >> lsblk: >> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >> mmcblk1boot0 179:16 01M 1 disk >> mmcblk1boot1 179:24 01M 1 disk >> mmcblk0 179:00 7.2G 0 disk >> `-mmcblk0p1 179:10 7.2G 0 part / >> mmcblk1 179:80 3.7G 0 disk >> - >> df -h | grep rootfs: >> - >> Erasing: /dev/mmcblk1 >> 108+0 records in >> 108+0 records out >> 113246208 bytes (113 MB) copied, 17.7061 s, 6.4 MB/s >> [ 34.099130] random: nonblocking pool is initialized >> 108+0 records in >> 108+0 records out >> 113246208 bytes (113 MB) copied, 4.35786 s, 26.0 MB/s >> Erasing: /dev/mmcblk1 complete >> - >> Writing bootloader to [/dev/mmcblk1] >> dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k >> - >> dd: failed to open '': No such file or directory[ 35.897114] Kernel >> panic - not syncing: Attempted to kill init! exitcode=0x0100 >> [ 35.897114] >> [ 35.911129] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted >> 4.1.21-bone-rt-r20 #1 >> [ 35.918639] Hardware name: Generic AM33XX (Flattened Device Tree) >> [ 35.924801] [] (unwind_backtrace) from [] >> (show_stack+0x11/0x14) >> [ 35.932590] [] (show_stack) from [] >> (panic+0x6d/0x188) >> [ 35.939500] [] (panic) from [] >> (complete_and_exit+0x1/0x18) >> [ 35.946844] [] (complete_and_exit) from [] >> (sigprocmask+0x59/0x88) >> [ 35.954801] [] (sigprocmask) from [<0001>] (0x1) >> [ 35.960665] ---[ end Kernel panic - not syncing: Attempted to kill >> init! exitcode=0x0100 >> [ 35.960665] >> >> The line I've highlighed in yellow seams to be the problem. >> Why is the cloning script getting a bootloader in here? >> >> Any help much 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...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/f7f021f7-98e5-4ae8-88d7-311f83b8d32b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/f7f021f7-98e5-4ae8-88d7-311f83b8d32b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3acf56a9-1173-4ca1-a8e5-38e86c62c21e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] kernel panic when cloning a BBB using beaglebone-black-make-microSD-flasher-from-eMMC.sh
Hi, Been trying to clone a debian 8.4 running kernel 4.1.x using the RC Nelson script beaglebone-black-make-microSD-flasher-from-eMMC.sh I have ensured that I have the latest script (git pull when in /opt/scripts/tools) I have ensured the BBB I am cloning has a network connection during the process. When I insert he new uSD card into a new BBB to flash it it ends quickly with a kernel panic. Here is the serial debug output: Starting eMMC Flasher from microSD media Version: [1.20160718: mkfs.ext4 1.43...] - Checking for Valid bbb-eeprom header Valid bbb-eeprom header found [335] - copying: [/dev/mmcblk0] -> [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 01M 1 disk mmcblk1boot1 179:24 01M 1 disk mmcblk0 179:00 7.2G 0 disk `-mmcblk0p1 179:10 7.2G 0 part / mmcblk1 179:80 3.7G 0 disk - df -h | grep rootfs: - Erasing: /dev/mmcblk1 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 17.7061 s, 6.4 MB/s [ 34.099130] random: nonblocking pool is initialized 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 4.35786 s, 26.0 MB/s Erasing: /dev/mmcblk1 complete - Writing bootloader to [/dev/mmcblk1] dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k - dd: failed to open '': No such file or directory[ 35.897114] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 35.897114] [ 35.911129] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 4.1.21-bone-rt-r20 #1 [ 35.918639] Hardware name: Generic AM33XX (Flattened Device Tree) [ 35.924801] [] (unwind_backtrace) from [] (show_stack+0x11/0x14) [ 35.932590] [] (show_stack) from [] (panic+0x6d/0x188) [ 35.939500] [] (panic) from [] (complete_and_exit+0x1/0x18) [ 35.946844] [] (complete_and_exit) from [] (sigprocmask+0x59/0x88) [ 35.954801] [] (sigprocmask) from [<0001>] (0x1) [ 35.960665] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 35.960665] The line I've highlighed in yellow seams to be the problem. Why is the cloning script getting a bootloader in here? Any help much 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f7f021f7-98e5-4ae8-88d7-311f83b8d32b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...
> > Hi RC, > Still trying to make this work. I have attached a wired network cable and can ping outside word. I then reran the beaglebone-black-make-microSD-flasher-from-eMMC.sh Card makes and when I start the flash on a new device I am getting the same result: Starting eMMC Flasher from microSD media Version: [1.20160718: mkfs.ext4 1.43...] - Checking for Valid bbb-eeprom header Valid bbb-eeprom header found [335] - copying: [/dev/mmcblk0] -> [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 01M 1 disk mmcblk1boot1 179:24 01M 1 disk mmcblk0 179:00 7.4G 0 disk `-mmcblk0p1 179:10 7.4G 0 part / mmcblk1 179:80 3.7G 0 disk - df -h | grep rootfs: - Erasing: /dev/mmcblk1 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 17.217 s, 6.6 MB/s [ 32.568856] random: nonblocking pool is initialized 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 4.352 s, 26.0 MB/s Erasing: /dev/mmcblk1 complete - Writing bootloader to [/dev/mmcblk1] dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k - dd: failed to open '': No such file or directory [ 34.346790] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 34.346790] [ 34.358792] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 4.1.21-bone-rt-r20 #1 [ 34.366303] Hardware name: Generic AM33XX (Flattened Device Tree) [ 34.372465] [] (unwind_backtrace) from [] (show_stack+0x11/0x14) [ 34.380254] [] (show_stack) from [] (panic+0x6d/0x188) [ 34.387165] [] (panic) from [] (complete_and_exit+0x1/0x18) [ 34.394509] [] (complete_and_exit) from [] (sigprocmask+0x59/0x88) [ 34.402465] [] (sigprocmask) from [<0001>] (0x1) [ 34.408330] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 34.408330] [ 509.671 For some reason I am still not getting the boot loader. On board I am cloning I do see MLO root@arm:/opt/backup/uboot# ls index.html MLO u-boot.img Next steps? -- 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/e062470d-fa57-42e3-bc34-09a5cef1f766%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] apt-get -y install ntp gives error Failed to fetch http://security...
Hi, I am trying to reinstall ntp on some BBB running 3.8.13-bone70 debian wheezy. When I run apt-get -y install --reinstall ntp I get: apt-get install --reinstall ntp Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 81 not upgraded. Need to get 494 kB of archives. After this operation, 0 B of additional disk space will be used. Err http://security.debian.org/ wheezy/updates/main ntp armhf 1:4.2.6.p5+dfsg-2+deb7u4 404 Not Found [IP: 128.101.240.215 80] Failed to fetch http://security.debian.org/pool/updates/main/n/ntp/ntp_4.2.6.p5+dfsg-2+deb7u4_armhf.deb 404 Not Found [IP: 128.101.240.215 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? I don't want to run apt-get update -- as this device is running remotely off a 2G slow connection. How can I fix this without having to run apt-get update? Did my sources.list get too old? Here is what is in there now: cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free #deb-src http://ftp.us.debian.org/debian/ wheezy main contrib non-free deb http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free #deb-src http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free #deb-src http://security.debian.org/ wheezy/updates main contrib non-free #deb http://ftp.debian.org/debian wheezy-backports main contrib non-free ##deb-src http://ftp.debian.org/debian wheezy-backports main contrib non-free #Kernel source (repos.rcn-ee.net) : https://github.com/RobertCNelson/linux-stable-rcn-ee # #git clone https://github.com/RobertCNelson/linux-stable-rcn-ee #cd ./linux-stable-rcn-ee #git checkout `uname -r` -b tmp # deb [arch=armhf] http://repos.rcn-ee.net/debian/ wheezy main #deb-src [arch=armhf] http://repos.rcn-ee.net/debian/ wheezy main 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/dbb2a627-d631-426e-b6b1-615b22515eff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...
Ok did that and still having there same error. Validated network connection and reran script. Below is the output of creating the image and then what I am getting when trying to use the image: Creating uSD: root@arm:/opt/scripts/tools/eMMC# ./beaglebone-black-make-microSD-flasher-from-eMMC.sh Unmounting Partitions - [3;J - Version: [1.20160322: upgrade backup u-boot: v2016.03-r6...] - copying: [/dev/mmcblk0] -> [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0boot0 179:801M 1 disk mmcblk0boot1 179:16 01M 1 disk mmcblk0 179:00 3.7G 0 disk └─mmcblk0p1 179:10 3.7G 0 part / mmcblk1 179:24 0 3.7G 0 disk └─mmcblk1p1 179:25 0 3.7G 0 part - df -h | grep rootfs: - update-initramfs: Generating /boot/initrd.img-4.1.21-bone-rt-r20 Erasing: /dev/mmcblk1 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 10.8226 s, 10.5 MB/s 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 5.8479 s, 19.4 MB/s Erasing: /dev/mmcblk1 complete - Writing bootloader to [/dev/mmcblk1] dd if=/opt/backup/uboot/MLO of=/dev/mmcblk1 count=1 seek=1 bs=128k - 0+1 records in 0+1 records out 65708 bytes (66 kB) copied, 0.0937003 s, 701 kB/s - dd if=/opt/backup/uboot/u-boot.img of=/dev/mmcblk1 count=2 seek=1 bs=384k - 0+1 records in 0+1 records out 350020 bytes (350 kB) copied, 0.104779 s, 3.3 MB/s - Formatting: /dev/mmcblk1 sfdisk: [sfdisk from util-linux 2.25.2] sfdisk: [sfdisk --force --Linux --in-order --unit M /dev/mmcblk1] sfdisk: [1,,L,*] sfdisk: Checking that no-one is using this disk right now ... sfdisk: OK Disk /dev/mmcblk1: 121472 cylinders, 4 heads, 16 sectors/track sfdisk: /dev/mmcblk1: unrecognized partition table type Old situation: sfdisk: No partitions found New situation: Units: 1MiB = 1024*1024 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start EndMiB#blocks Id System /dev/mmcblk1p1 * 1 3795 37953886080 83 Linux /dev/mmcblk1p2 0 - 0 00 Empty /dev/mmcblk1p3 0 - 0 00 Empty /dev/mmcblk1p4 0 - 0 00 Empty Successfully wrote the new partition table Re-reading the partition table ... sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1 (See fdisk(8).) mkfs.ext4 /dev/mmcblk1p1 -L BEAGLEBONE - mke2fs 1.42.12 (29-Aug-2014) Discarding device blocks: done Creating filesystem with 971520 4k blocks and 242880 inodes Filesystem UUID: 11b1347f-86bb-46e0-8779-764f298bcd3e Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 Allocating group tables: done Writing inode tables: done Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done - Formatting: /dev/mmcblk1 complete - Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1 rsync: / -> /tmp/rootfs/ rsync: note the % column is useless... 691.19M 99%4.05MB/s0:02:42 (xfr#25078, to-chk=0/31857) Copying: Kernel modules rsync: /lib/modules/4.1.21-bone-rt-r20/ -> /tmp/rootfs/lib/modules/4.1.21-bone-rt-r20/ rsync: note the % column is useless... 55.61M 99%4.04MB/s0:00:13 (xfr#2266, to-chk=0/2652) Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1 complete - Final System Tweaks: UUID=11b1347f-86bb-46e0-8779-764f298bcd3e Generating: /etc/fstab # /etc/fstab: static file system information. # UUID=11b1347f-86bb-46e0-8779-764f298bcd3e / ext4 noatime,errors=remount-ro 0 1 debugfs /sys/kernel/debug debugfs defaults 0 0 /boot/uEnv.txt: enabling eMMC flasher script uname_r=4.1.21-bone-rt-r20 #uuid=81b9a3e8-1ff6-4797-b2eb-f4517ab96628 cape_enable=bone_capemgr.enable_partno=BB-APA-01 uuid=11b1347f-86bb-46e0-8779-764f298bcd3e cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh - Syncing: /dev/mmcblk1 ./beaglebone-black-make-microSD-flasher-from-eMMC.sh: line 309: 6860 Terminated cylon_leds 10+0 records in 10+0 records out 5120 bytes (51 MB) copied, 2.56244 s, 20.0 MB/s Syncing: /dev/mmcblk1 complete - umount: /tmp: not mounted umount: /tmp: not mounted And here is the serial output when tyring to use the uSD: U-Boot SPL 2016.03-dirty (Apr 19 2016 - 15:43:26) Trying to boot from MMC bad magic U-Boot 2016.03-dirty (Apr 19 2016 - 15:43:26 -0700) Watchdog enabled
[beagleboard] Re: kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...
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? On Wednesday, May 25, 2016 at 5:51:56 PM UTC-7, Matt99eo wrote: > > Trying to clone a Debian Jesse distro (4.1.21) > I made a uSD using the beaglebone-black-make-microSD-flasher-from-eMMC.sh > > What am I missing here? > > When I insert this into another BBB it crashes before flashing > completion. Here is what I see when a serial debug cable is connected: > > > Starting eMMC Flasher from microSD media > Version: [1.20160222: deal with v4.4.x+ back to old eeprom location...] > - > Checking for Valid bbb-eeprom header > Valid bbb-eeprom header found [335] > - > copying: [/dev/mmcblk0] -> [/dev/mmcblk1] > lsblk: > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > mmcblk1boot0 179:16 01M 1 disk > mmcblk1boot1 179:24 01M 1 disk > mmcblk0 179:00 3.7G 0 disk > `-mmcblk0p1 179:10 3.7G 0 part / > mmcblk1 179:80 3.7G 0 disk > - > df -h | grep rootfs: > - > Erasing: /dev/mmcblk1 > 108+0 records in > 108+0 records out > 113246208 bytes (113 MB) copied, 16.1838 s, 7.0 MB/s > [ 31.654940] random: nonblocking pool is initialized > 108+0 records in > 108+0 records out > 113246208 bytes (113 MB) copied, 4.25127 s, 26.6 MB/s > Erasing: /dev/mmcblk1 complete > - > Writing bootloader to [/dev/mmcblk1] > dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k > - > dd: failed to open '': No such file or directory[ 33.281227] Kernel > panic - not syncing: Attempted to kill init! exitcode=0x0100 > [ 33.281227] > [ 33.295345] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted > 4.1.21-bone-rt-r20 #1 > [ 33.302856] Hardware name: Generic AM33XX (Flattened Device Tree) > [ 33.309018] [] (unwind_backtrace) from [] > (show_stack+0x11/0x14) > [ 33.316808] [] (show_stack) from [] > (panic+0x6d/0x188) > [ 33.323719] [] (panic) from [] > (complete_and_exit+0x1/0x18) > [ 33.331063] [] (complete_and_exit) from [] > (sigprocmask+0x59/0x88) > [ 33.339019] [] (sigprocmask) from [<0001>] (0x1) > [ 33.344883] ---[ end Kernel panic - not syncing: Attempted to kill > init! exitcode=0x0100 > [ 33.344883] > -- 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/9270cbfe-e1b2-454d-aaec-2848577d3f19%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] 4.1.21 pause during boot: A start job is running for LSB: Raise network interf...
Why does the kernel pause for a will (10s) while booting. I see the pause in line noted in red below. Something to to with phy 4a101000? r 10.287710] net eth0: initializing cpsw version 1.12 (0) [ 10.295460] net eth0: phy found : id is : 0x7c0f1 [ 10.300245] libphy: PHY 4a101000.mdio:01 not found [ 10.305086] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 10.315002] net eth0: BQL enabled [ 10.322353] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [] A start job is running for LSB: Raise network interf...31s / limit)[ 37.822466] random: nonblocking pool is initialized -- 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/83b7d2bf-18e6-4e60-ae5f-9aed4ff5467b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] kernel panic when flashing eMMC from uSD made from /opt/scripts/tools/beaglebon...
Trying to clone a Debian Jesse distro (4.1.21) I made a uSD using the beaglebone-black-make-microSD-flasher-from-eMMC.sh What am I missing here? When I insert this into another BBB it crashes before flashing completion. Here is what I see when a serial debug cable is connected: Starting eMMC Flasher from microSD media Version: [1.20160222: deal with v4.4.x+ back to old eeprom location...] - Checking for Valid bbb-eeprom header Valid bbb-eeprom header found [335] - copying: [/dev/mmcblk0] -> [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 01M 1 disk mmcblk1boot1 179:24 01M 1 disk mmcblk0 179:00 3.7G 0 disk `-mmcblk0p1 179:10 3.7G 0 part / mmcblk1 179:80 3.7G 0 disk - df -h | grep rootfs: - Erasing: /dev/mmcblk1 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 16.1838 s, 7.0 MB/s [ 31.654940] random: nonblocking pool is initialized 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 4.25127 s, 26.6 MB/s Erasing: /dev/mmcblk1 complete - Writing bootloader to [/dev/mmcblk1] dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k - dd: failed to open '': No such file or directory[ 33.281227] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 33.281227] [ 33.295345] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 4.1.21-bone-rt-r20 #1 [ 33.302856] Hardware name: Generic AM33XX (Flattened Device Tree) [ 33.309018] [] (unwind_backtrace) from [] (show_stack+0x11/0x14) [ 33.316808] [] (show_stack) from [] (panic+0x6d/0x188) [ 33.323719] [] (panic) from [] (complete_and_exit+0x1/0x18) [ 33.331063] [] (complete_and_exit) from [] (sigprocmask+0x59/0x88) [ 33.339019] [] (sigprocmask) from [<0001>] (0x1) [ 33.344883] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 33.344883] -- 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/7470bec3-23df-487f-a559-9ae6e3967726%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] flashing BBB with image made from /opt/scripts/tools/beag.... and getting kernel panic
Trying to clone a Debian Jesse distro (4.1.21) I made a uSD using the beaglebone-black-make-microSD-flasher-from-eMMC.sh What am I missing here? When I insert this into another BBB it crashes before flashing completion. Here is what I see when a serial debug cable is connected: Starting eMMC Flasher from microSD media Version: [1.20160222: deal with v4.4.x+ back to old eeprom location...] - Checking for Valid bbb-eeprom header Valid bbb-eeprom header found [335] - copying: [/dev/mmcblk0] -> [/dev/mmcblk1] lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 01M 1 disk mmcblk1boot1 179:24 01M 1 disk mmcblk0 179:00 3.7G 0 disk `-mmcblk0p1 179:10 3.7G 0 part / mmcblk1 179:80 3.7G 0 disk - df -h | grep rootfs: - Erasing: /dev/mmcblk1 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 16.1838 s, 7.0 MB/s [ 31.654940] random: nonblocking pool is initialized 108+0 records in 108+0 records out 113246208 bytes (113 MB) copied, 4.25127 s, 26.6 MB/s Erasing: /dev/mmcblk1 complete - Writing bootloader to [/dev/mmcblk1] dd if= of=/dev/mmcblk1 count=1 seek=1 bs=128k - dd: failed to open '': No such file or directory[ 33.281227] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 33.281227] [ 33.295345] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 4.1.21-bone-rt-r20 #1 [ 33.302856] Hardware name: Generic AM33XX (Flattened Device Tree) [ 33.309018] [] (unwind_backtrace) from [] (show_stack+0x11/0x14) [ 33.316808] [] (show_stack) from [] (panic+0x6d/0x188) [ 33.323719] [] (panic) from [] (complete_and_exit+0x1/0x18) [ 33.331063] [] (complete_and_exit) from [] (sigprocmask+0x59/0x88) [ 33.339019] [] (sigprocmask) from [<0001>] (0x1) [ 33.344883] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 33.344883] -- 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/f5347472-b83a-4560-871f-851b3647accb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Flashin BBB with new image I built from RC guide
4-fs error (device mmcblk1p2): ext4_lookup:1416: inode
#6776: comm rsync: deleted inode referenced: 8084
rsync: readlink_stat("/usr/bin/xscreensaver-demo") failed: Input/output
error (5)
[ 224.820246] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode
#6776: comm rsync: deleted inode referenced: 8081
rsync: readlink_stat("/usr/bin/xrefresh") failed: Input/output error (5)
[ 224.857912] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode
#6776: comm rsync: deleted inode referenced: 8093
rsync: readlink_stat("/usr/bin/xsetwacom") failed: Input/output error (5)
[ 224.906092] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode
#6776: comm rsync: deleted inode referenced: 8096
rsync: readlink_stat("/usr/bin/xvidtune") failed: Input/output error (5)
[ 224.944966] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode
#6776: comm rsync: deleted inode referenced: 8094
rsync: readlink_stat("/usr/bin/xstdcmap") failed: Input/output error (5)
[ 224.964793] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode
#6776: comm rsync: deleted inode referenced: 8085
rsync: readlink_stat("/usr/bin/xscreensaver-geti[ 224.981610] EXT4-fs
error (device mmcblk1p2): ext4_lookup:1416: inode #6776: comm rsync:
deleted inode referenced: 8100
mage") failed: Input/output error (5)
rsync: readlink_stat("/usr/bin/xz") faile[ 225.000312] EXT4-fs error
(device mmcblk1p2): ext4_lookup:1416: inode #6776: comm rsync: deleted
inode referenced: 8107
d: Input/output error (5)
rsync: readlink_stat("/usr/bin/zsoelim") failed: Input/output error (5)
[ 225.608124] EXT4-fs error (device mmcblk1p2): ext4_lookup:1416: inode
#6776: comm rsync: deleted inode referenced: 8092
rsync: readlink_stat("/usr/bin/xsetroot") failed: Input/output error (5)
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]:
Broken pipe (32)
rsync: write failed on
"/tmp/rootfs/opt/source/pru-software-support-package/examples/PRU_access_const_table/Debug/makefile":
No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9]
rsync: connection unexpectedly closed (117763 bytes received so far)
[sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605)
[sender=3.0.9]
writing to [/dev/mmcblk1] failed...
-
./bbb-eMMC-flasher-eewiki-ext4.sh: line 41: 3337 Terminated
cylon_leds
Any ideas?
On Wednesday, April 20, 2016 at 3:56:47 PM UTC-7, RobertCNelson wrote:
>
>
>
> On Wed, Apr 20, 2016 at 5:40 PM, Matt99eo > wrote:
>
>> Yes I saw this stuff and used the
>>
>> /dev/sdX options to get it all on the uSD card.
>>
>> Now that it is on there and I am booted into the serial consol on the bbb
>> running I built do I do all this again but with /mmblk0 option?
>>
>
> No... If you actually click on the link..
>
> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-eMMC
>
> It says:
> eMMC
>
> Script to copy your microSD card to eMMC: (this will need these packages
> installed: initramfs-tools dosfstools rsync)
> wget https://
> raw.githubusercontent.com/RobertCNelson/boot-scripts/master/tools/eMMC/bbb-eMMC-flasher-eewiki-ext4.sh
> chmod +x bbb-eMMC-flasher-eewiki-ext4.sh
> sudo /bin/bash ./bbb-eMMC-flasher-eewiki-ext4.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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/81a9ce03-b6f2-4e5d-be72-95bae04bcfeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Device tree load in 4.1 when migrating from 3.8.x
As always thanks for the help Robert! That solved it! On Monday, May 9, 2016 at 5:09:22 PM UTC-7, RobertCNelson wrote: > > > > On Mon, May 9, 2016 at 6:59 PM, Matt99eo > wrote: > >> >> Got the command to go but don't quite follow you on the >> >> then add BB-APA-01 into /boot/uEnv.txt under the v4.1.x kernel section on >> loading overlays.. >> >> My uEnv.txt looks like this right now: >> cat /boot/uEnv.txt >> uname_r=4.1.23-ti-rt-r60 >> uuid=8b83ed28-d947-4fda-b607-d5c5faf3dbe5 >> dtb=am335x-boneblack-emmc-overlay.dtb >> >> Am I missing something here in uEnv.txt? >> >> Do I simply add this to /boot/uEnv.txt: >> > > cape_enable=bone_capemgr.enable_partno=BB-APA-01 > > 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/88315782-3c84-4798-ac16-ed29414b5dbd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Device tree load in 4.1 when migrating from 3.8.x
Got the command to go but don't quite follow you on the then add BB-APA-01 into /boot/uEnv.txt under the v4.1.x kernel section on loading overlays.. My uEnv.txt looks like this right now: cat /boot/uEnv.txt uname_r=4.1.23-ti-rt-r60 uuid=8b83ed28-d947-4fda-b607-d5c5faf3dbe5 dtb=am335x-boneblack-emmc-overlay.dtb Am I missing something here in uEnv.txt? Do I simply add this to /boot/uEnv.txt: bone_capemgr.enable_partno=BB-APA-01 On Monday, May 9, 2016 at 4:36:59 PM UTC-7, RobertCNelson wrote: > > > > On Mon, May 9, 2016 at 6:25 PM, Matt99eo > wrote: > >> Fixed this issue -- was a <&uart*> number I missed changing... doh >> >> >> I can now manually add the device tree : >> >> 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-00A0,Override Manuf,BB-APA-01 >> >> How do I bake this into my kernel such that it loads at boot? >> > > sudo update-initramfs -uk `uname -r` > > *.dtbo's from /lib/firmware/ get copied to the initramfs.. > > then add BB-APA-01 into /boot/uEnv.txt under the v4.1.x kernel section on > loading overlays.. > > 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/64a2602d-8ba6-4b4f-a390-44d725f738e4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Device tree load in 4.1 when migrating from 3.8.x
Fixed this issue -- was a <&uart*> number I missed changing... doh I can now manually add the device tree : 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-00A0,Override Manuf,BB-APA-01 How do I bake this into my kernel such that it loads at boot? On Monday, May 9, 2016 at 12:33:35 PM UTC-7, Matt99eo wrote: > > Yes I do believe I have the right version -- as I followed your > instructions in bb.org-overlays > > here is the result of a version check: > root@arm:/lib/firmware# dtc --version > Version: DTC 1.4.1-g1e75ebc9 > > To compile an overlay I did > dtc -O dtb -o BB-APA-01-00A0.dtbo -b 0 -@ BB-APA-01-00A0.dts > > Then I placed the output in /lib/firmware > > > Referring to > https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fbeagleboard%2Fbb.org-overlays%2Fblob%2Fmaster%2Freadme.md&sa=D&sntz=1&usg=AFQjCNHG_Smv0Zbgg2uyvPI361SZH1-vgg> > I changed my uEnv.txt to contain > dtb=am335x-boneblack-emmc-overlay.dtb > > > Stll getting this: > [ 229.625505] bone_capemgr bone_capemgr: part_number 'BB-APA-01', version > 'N/A' > [ 229.633234] bone_capemgr bone_capemgr: slot #4: override > [ 229.638620] bone_capemgr bone_capemgr: Using override eeprom data at > slot 4 > [ 229.655322] bone_capemgr bone_capemgr: slot #4: 'Override Board > Name,00A0,Override Manuf,BB-APA-01' > [ 229.676441] __of_changeset_entry_apply: add_property failed > @/ocp/serial@481aa000/pinctrl-names > [ 229.676462] of_changeset_apply: Error applying changeset (-17) > [ 229.695456] __of_overlay_create: of_changeset_apply() failed for tree@/ > [ 229.702544] bone_capemgr bone_capemgr: slot #4: Failed to create overlay > sh: echo: I/O error > > > > On Monday, May 9, 2016 at 11:16:50 AM UTC-7, RobertCNelson wrote: >> >> >> >> On Mon, May 9, 2016 at 1:12 PM, Matt99eo wrote: >> >>> Hi, >>> >>> In the process of migrating from 3.8.x to 4.1.21 and trying to get my >>> device tree to load manually (eventually to load on boot). >>> >>> As I understand it device trees are supported in 4.1.x -- yes? >>> >>> I the the .dts compiles with out errors however when I go to load the >>> device tree I get the following: >>> >>> echo BB-APA-01 > slots >>> [ 8122.326385] bone_capemgr bone_capemgr: part_number 'BB-APA-01', >>> version 'N/A' >>> [ 8122.333614] bone_capemgr bone_capemgr: slot #5: override >>> [ 8122.339116] bone_capemgr bone_capemgr: Using override eeprom data at >>> slot 5 >>> [ 8122.346184] bone_capemgr bone_capemgr: slot #5: 'Override Board >>> Name,00A0,Override Manuf,BB-APA-01' >>> [ 8122.369433] __of_changeset_entry_apply: add_property failed >>> @/ocp/serial@481aa000/pinctrl-names >>> [ 8122.378353] of_changeset_apply: Error applying changeset (-17) >>> [ 8122.384609] __of_overlay_create: of_changeset_apply() failed for >>> tree@/ >>> [ 8122.391429] bone_capemgr bone_capemgr: slot #5: Failed to create >>> overlay >>> -bash: echo: write error: File exists >>> >> >> This also could me you used the wrong dtc compiler.. >> >> Use the one this one builds: >> >> https://github.com/beagleboard/bb.org-overlays/blob/master/dtc-overlay.sh >> >> >>> >>> >>> My dts file is essentially the same as I had it in 3.8.x except for >>> changing uart numbers to index from 0 instead of 1 as I've read that >>> changed. >>> >>> This custom device tree uses pins reserved for HDMI so I did added teh >>> disable option to /boot/uEnv.txt: >>> >>> cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN >>> >> >> this ^ doesn't do anything.. >> >> Read, section: BBB compatibility issues: >> >> https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md >> >> 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/a15fed79-d713-4ab2-821a-3bfd640409ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Device tree load in 4.1 when migrating from 3.8.x
Yes I do believe I have the right version -- as I followed your instructions in bb.org-overlays here is the result of a version check: root@arm:/lib/firmware# dtc --version Version: DTC 1.4.1-g1e75ebc9 To compile an overlay I did dtc -O dtb -o BB-APA-01-00A0.dtbo -b 0 -@ BB-APA-01-00A0.dts Then I placed the output in /lib/firmware Referring to https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fbeagleboard%2Fbb.org-overlays%2Fblob%2Fmaster%2Freadme.md&sa=D&sntz=1&usg=AFQjCNHG_Smv0Zbgg2uyvPI361SZH1-vgg> I changed my uEnv.txt to contain dtb=am335x-boneblack-emmc-overlay.dtb Stll getting this: [ 229.625505] bone_capemgr bone_capemgr: part_number 'BB-APA-01', version 'N/A' [ 229.633234] bone_capemgr bone_capemgr: slot #4: override [ 229.638620] bone_capemgr bone_capemgr: Using override eeprom data at slot 4 [ 229.655322] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-APA-01' [ 229.676441] __of_changeset_entry_apply: add_property failed @/ocp/serial@481aa000/pinctrl-names [ 229.676462] of_changeset_apply: Error applying changeset (-17) [ 229.695456] __of_overlay_create: of_changeset_apply() failed for tree@/ [ 229.702544] bone_capemgr bone_capemgr: slot #4: Failed to create overlay sh: echo: I/O error On Monday, May 9, 2016 at 11:16:50 AM UTC-7, RobertCNelson wrote: > > > > On Mon, May 9, 2016 at 1:12 PM, Matt99eo > wrote: > >> Hi, >> >> In the process of migrating from 3.8.x to 4.1.21 and trying to get my >> device tree to load manually (eventually to load on boot). >> >> As I understand it device trees are supported in 4.1.x -- yes? >> >> I the the .dts compiles with out errors however when I go to load the >> device tree I get the following: >> >> echo BB-APA-01 > slots >> [ 8122.326385] bone_capemgr bone_capemgr: part_number 'BB-APA-01', >> version 'N/A' >> [ 8122.333614] bone_capemgr bone_capemgr: slot #5: override >> [ 8122.339116] bone_capemgr bone_capemgr: Using override eeprom data at >> slot 5 >> [ 8122.346184] bone_capemgr bone_capemgr: slot #5: 'Override Board >> Name,00A0,Override Manuf,BB-APA-01' >> [ 8122.369433] __of_changeset_entry_apply: add_property failed >> @/ocp/serial@481aa000/pinctrl-names >> [ 8122.378353] of_changeset_apply: Error applying changeset (-17) >> [ 8122.384609] __of_overlay_create: of_changeset_apply() failed for tree@/ >> [ 8122.391429] bone_capemgr bone_capemgr: slot #5: Failed to create >> overlay >> -bash: echo: write error: File exists >> > > This also could me you used the wrong dtc compiler.. > > Use the one this one builds: > > https://github.com/beagleboard/bb.org-overlays/blob/master/dtc-overlay.sh > > >> >> >> My dts file is essentially the same as I had it in 3.8.x except for >> changing uart numbers to index from 0 instead of 1 as I've read that >> changed. >> >> This custom device tree uses pins reserved for HDMI so I did added teh >> disable option to /boot/uEnv.txt: >> >> cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN >> > > this ^ doesn't do anything.. > > Read, section: BBB compatibility issues: > > https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md > > 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/e9bba5bf-d0bc-4566-8d25-bc8a272b50a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Device tree load in 4.1 when migrating from 3.8.x
Hi, In the process of migrating from 3.8.x to 4.1.21 and trying to get my device tree to load manually (eventually to load on boot). As I understand it device trees are supported in 4.1.x -- yes? I the the .dts compiles with out errors however when I go to load the device tree I get the following: echo BB-APA-01 > slots [ 8122.326385] bone_capemgr bone_capemgr: part_number 'BB-APA-01', version 'N/A' [ 8122.333614] bone_capemgr bone_capemgr: slot #5: override [ 8122.339116] bone_capemgr bone_capemgr: Using override eeprom data at slot 5 [ 8122.346184] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,BB-APA-01' [ 8122.369433] __of_changeset_entry_apply: add_property failed @/ocp/serial@481aa000/pinctrl-names [ 8122.378353] of_changeset_apply: Error applying changeset (-17) [ 8122.384609] __of_overlay_create: of_changeset_apply() failed for tree@/ [ 8122.391429] bone_capemgr bone_capemgr: slot #5: Failed to create overlay -bash: echo: write error: File exists My dts file is essentially the same as I had it in 3.8.x except for changing uart numbers to index from 0 instead of 1 as I've read that changed. This custom device tree uses pins reserved for HDMI so I did added teh disable option to /boot/uEnv.txt: cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN What else do I need to update in my .dts or do to get a custom device tree to load? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/87aa2b45-ab0b-43f7-9ee6-3f8c0682b94e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: CCCCCCC's Debug serial port output on unsuccessful boot
Ok Thanks guys, Identified and fixed the effected pin and now getting consistent boots. Cheers, On Monday, May 2, 2016 at 2:33:54 PM UTC-7, CEinTX wrote: > > I have seen this too. > It is as Gerald says. Your cape is loading one or more of the boot pins. > I did a cape - even though all the connections were high impedance inputs, > it was still enough to twitch the boot pins. Anyway, I ended up adjusting > a couple > of the pullup resistors to adjust for it on the pins I was using - > changed from 100k to > 33k. Only had to do this for the pullups - so apparently stealing even a > little from the > 33uA max source was enough to impact the boot read of the pins. > Hope that helps. > > GL > Matt > > On Monday, May 2, 2016 at 3:43:34 PM UTC-5, Matt99eo wrote: >> >> Working with a BBB that has a custom hardware cape on it. >> >> Sometimes I get an unsuccessful boot out of it where when connected to >> the serial debug part I see the letter C printed indefinitely. >> >> I'd say 90% of the boot attempts work (serial debug looks normal) and 10% >> I get the infinite C printout and no successful boot. >> >> >> 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a5c4e0bb-cda3-42cb-9ef7-37944b8a330a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] CCCCCCC's Debug serial port output on unsuccessful boot
Working with a BBB that has a custom hardware cape on it. Sometimes I get an unsuccessful boot out of it where when connected to the serial debug part I see the letter C printed indefinitely. I'd say 90% of the boot attempts work (serial debug looks normal) and 10% I get the infinite C printout and no successful boot. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/965be62d-660c-432e-887f-9f92ff671d44%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
Got the device to give me a connection to the outside world on the new kernel (4.1.21-bone-rt-r20, running Debian 8) Had to add auto usb0 iface usb0 inet dhcp I now have a connection out. This modem in effect now is acting like a router. I have LAN address and not a WAN so I can't ssh back to device from outside world. Working on that now. On Thursday, April 21, 2016 at 8:36:51 AM UTC-7, Matt99eo wrote: > > Yep I read that and here is my /network/interfaces > > root@arm:~# cat /etc/network/interfaces > # interfaces(5) file used by ifup(8) and ifdown(8) > # Include files from /etc/network/interfaces.d: > source-directory /etc/network/interfaces.d > > auto lo > iface lo inet loopback > > #auto eth0 > #iface eth0 inet dhcp > > On Wednesday, April 20, 2016 at 6:11:14 PM UTC-7, William Hermans wrote: >> >> well according to this: >> http://nimbelink.com/appnotes/CAT1CDC-ECM-Application_Note.pdf >> >> You need to comment out the USB0 lines in /etc/network/interfaces, and >> then the device will automatically come up >> >> On Wed, Apr 20, 2016 at 5:07 PM, Matt99eo wrote: >> >>> Yes it is a modem >>> >>> http://nimbelink.com/skywire-4g-lte-cat-1/ >>> >>> They do not have firmware yet that supports pppd. I use ppp for other >>> modems that do support it and that works this guys is just different (until >>> firmware is baked). >>> >>> >>> >>> On Wednesday, April 20, 2016 at 4:53:41 PM UTC-7, William Hermans wrote: >>>> >>>> usb1 is probably your external device. But you can find out via dmesg >>>> by issuing . . >>>> >>>> $ dmesg | grep usb1 >>>> >>>> And using deductive reasoning. But also, once you get your cdc device >>>> working, I do not know how it's meant to be used. Robert Suggested pppd >>>> which suggests to me it's meant to be used a some sort of modem ? >>>> >>>> On Wed, Apr 20, 2016 at 4:50 PM, Matt99eo >>>> wrote: >>>> >>>>> I was wondering about multiple usb connections... >>>>> >>>>> So here is thing though. I am now ssh'd into the device over >>>>> ethernet. I see the usbo with ifconfig: >>>>> >>>>> ifconfig >>>>> eth0 Link encap:Ethernet HWaddr 78:a5:04:f8:61:5e >>>>> inet addr:10.1.2.169 Bcast:10.1.2.255 Mask:255.255.255.0 >>>>> inet6 addr: fe80::7aa5:4ff:fef8:615e/64 Scope:Link >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>>> RX packets:881 errors:0 dropped:9 overruns:0 frame:0 >>>>> TX packets:282 errors:0 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 txqueuelen:1000 >>>>> RX bytes:87981 (85.9 KiB) TX bytes:37544 (36.6 KiB) >>>>> Interrupt:40 >>>>> >>>>> loLink encap:Local Loopback >>>>> inet addr:127.0.0.1 Mask:255.0.0.0 >>>>> inet6 addr: ::1/128 Scope:Host >>>>> UP LOOPBACK RUNNING MTU:65536 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:0 >>>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>>>> >>>>> usb0 Link encap:Ethernet HWaddr 02:80:70:00:04:70 >>>>> inet addr:192.168.7.2 Bcast:192.168.7.255 >>>>> Mask:255.255.255.0 >>>>> inet6 addr: fe80::80:70ff:fe00:470/64 Scope:Link >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>>>> TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 >>>>> collisions:0 txqueuelen:1000 >>>>> RX bytes:0 (0.0 B) TX bytes:5387 (5.2 KiB) >>>>> >>>>> >>>>> But now how do I test I am connected out that way instead of over the >>>>> ethernet cable lol? >>>>> >>>>> At the end of the day I want these devices to talk out the cell module >>>>> to cloud servers and be able to acess them in the field via ssh. I have >>>>> statically provisioned SIM cards so I can get to them. >>>>> >>>>> O
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
Yep I read that and here is my /network/interfaces root@arm:~# cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto lo iface lo inet loopback #auto eth0 #iface eth0 inet dhcp On Wednesday, April 20, 2016 at 6:11:14 PM UTC-7, William Hermans wrote: > > well according to this: > http://nimbelink.com/appnotes/CAT1CDC-ECM-Application_Note.pdf > > You need to comment out the USB0 lines in /etc/network/interfaces, and > then the device will automatically come up > > On Wed, Apr 20, 2016 at 5:07 PM, Matt99eo > wrote: > >> Yes it is a modem >> >> http://nimbelink.com/skywire-4g-lte-cat-1/ >> >> They do not have firmware yet that supports pppd. I use ppp for other >> modems that do support it and that works this guys is just different (until >> firmware is baked). >> >> >> >> On Wednesday, April 20, 2016 at 4:53:41 PM UTC-7, William Hermans wrote: >>> >>> usb1 is probably your external device. But you can find out via dmesg by >>> issuing . . >>> >>> $ dmesg | grep usb1 >>> >>> And using deductive reasoning. But also, once you get your cdc device >>> working, I do not know how it's meant to be used. Robert Suggested pppd >>> which suggests to me it's meant to be used a some sort of modem ? >>> >>> On Wed, Apr 20, 2016 at 4:50 PM, Matt99eo wrote: >>> >>>> I was wondering about multiple usb connections... >>>> >>>> So here is thing though. I am now ssh'd into the device over ethernet. >>>> I see the usbo with ifconfig: >>>> >>>> ifconfig >>>> eth0 Link encap:Ethernet HWaddr 78:a5:04:f8:61:5e >>>> inet addr:10.1.2.169 Bcast:10.1.2.255 Mask:255.255.255.0 >>>> inet6 addr: fe80::7aa5:4ff:fef8:615e/64 Scope:Link >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:881 errors:0 dropped:9 overruns:0 frame:0 >>>> TX packets:282 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:1000 >>>> RX bytes:87981 (85.9 KiB) TX bytes:37544 (36.6 KiB) >>>> Interrupt:40 >>>> >>>> loLink encap:Local Loopback >>>> inet addr:127.0.0.1 Mask:255.0.0.0 >>>> inet6 addr: ::1/128 Scope:Host >>>> UP LOOPBACK RUNNING MTU:65536 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:0 >>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>>> >>>> usb0 Link encap:Ethernet HWaddr 02:80:70:00:04:70 >>>> inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0 >>>> inet6 addr: fe80::80:70ff:fe00:470/64 Scope:Link >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:1000 >>>> RX bytes:0 (0.0 B) TX bytes:5387 (5.2 KiB) >>>> >>>> >>>> But now how do I test I am connected out that way instead of over the >>>> ethernet cable lol? >>>> >>>> At the end of the day I want these devices to talk out the cell module >>>> to cloud servers and be able to acess them in the field via ssh. I have >>>> statically provisioned SIM cards so I can get to them. >>>> >>>> On Wednesday, April 20, 2016 at 4:41:40 PM UTC-7, William Hermans wrote: >>>>> >>>>> And sorry . . >>>>> >>>>> william@beaglebone:~$ sudo ifconfig usb0 192.168.7.2 >>>>> THEN >>>>> william@beaglebone:~$ sudo ifconfig >>>>> . . . >>>>> >>>>> usb0 Link encap:Ethernet HWaddr 7e:68:32:bc:58:89 >>>>> inet addr:192.168.7.2 Bcast:192.168.7.255 >>>>> Mask:255.255.255.0 >>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>>> RX packets:1 errors:0 dropped:1 overruns:0 frame:0 >>>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>>>>
Re: [beagleboard] Flashin BBB with new image I built from RC guide
Doh thank you that did it Thanks again for the hand holding. On Wednesday, April 20, 2016 at 3:56:47 PM UTC-7, RobertCNelson wrote: > > > > On Wed, Apr 20, 2016 at 5:40 PM, Matt99eo > wrote: > >> Yes I saw this stuff and used the >> >> /dev/sdX options to get it all on the uSD card. >> >> Now that it is on there and I am booted into the serial consol on the bbb >> running I built do I do all this again but with /mmblk0 option? >> > > No... If you actually click on the link.. > > https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-eMMC > > It says: > eMMC > > Script to copy your microSD card to eMMC: (this will need these packages > installed: initramfs-tools dosfstools rsync) > wget https:// > raw.githubusercontent.com/RobertCNelson/boot-scripts/master/tools/eMMC/bbb-eMMC-flasher-eewiki-ext4.sh > chmod +x bbb-eMMC-flasher-eewiki-ext4.sh > sudo /bin/bash ./bbb-eMMC-flasher-eewiki-ext4.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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a7b03f5d-4bc5-4cb1-8f47-26d13e43a2a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
Yes it is a modem http://nimbelink.com/skywire-4g-lte-cat-1/ They do not have firmware yet that supports pppd. I use ppp for other modems that do support it and that works this guys is just different (until firmware is baked). On Wednesday, April 20, 2016 at 4:53:41 PM UTC-7, William Hermans wrote: > > usb1 is probably your external device. But you can find out via dmesg by > issuing . . > > $ dmesg | grep usb1 > > And using deductive reasoning. But also, once you get your cdc device > working, I do not know how it's meant to be used. Robert Suggested pppd > which suggests to me it's meant to be used a some sort of modem ? > > On Wed, Apr 20, 2016 at 4:50 PM, Matt99eo > wrote: > >> I was wondering about multiple usb connections... >> >> So here is thing though. I am now ssh'd into the device over ethernet. I >> see the usbo with ifconfig: >> >> ifconfig >> eth0 Link encap:Ethernet HWaddr 78:a5:04:f8:61:5e >> inet addr:10.1.2.169 Bcast:10.1.2.255 Mask:255.255.255.0 >> inet6 addr: fe80::7aa5:4ff:fef8:615e/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:881 errors:0 dropped:9 overruns:0 frame:0 >> TX packets:282 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:87981 (85.9 KiB) TX bytes:37544 (36.6 KiB) >> Interrupt:40 >> >> loLink encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:65536 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:0 >> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >> >> usb0 Link encap:Ethernet HWaddr 02:80:70:00:04:70 >> inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0 >> inet6 addr: fe80::80:70ff:fe00:470/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 B) TX bytes:5387 (5.2 KiB) >> >> >> But now how do I test I am connected out that way instead of over the >> ethernet cable lol? >> >> At the end of the day I want these devices to talk out the cell module to >> cloud servers and be able to acess them in the field via ssh. I have >> statically provisioned SIM cards so I can get to them. >> >> On Wednesday, April 20, 2016 at 4:41:40 PM UTC-7, William Hermans wrote: >>> >>> And sorry . . >>> >>> william@beaglebone:~$ sudo ifconfig usb0 192.168.7.2 >>> THEN >>> william@beaglebone:~$ sudo ifconfig >>> . . . >>> >>> usb0 Link encap:Ethernet HWaddr 7e:68:32:bc:58:89 >>> inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:1 errors:0 dropped:1 overruns:0 frame:0 >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:76 (76.0 B) TX bytes:0 (0.0 B) >>> >>> >>> >>> >>> On Wed, Apr 20, 2016 at 4:39 PM, William Hermans >>> wrote: >>> >>>> For instance: >>>> >>>> william@beaglebone:~$ ls /sys/class/net >>>> eth0 lo >>>> william@beaglebone:~$ sudo modprobe g_ether >>>> >>>> william@beaglebone:~$ ls /sys/class/net >>>> eth0 lo usb0 >>>> >>>> william@beaglebone:~$ sudo ifconfig >>>> . . . >>>> usb0 Link encap:Ethernet HWaddr 7e:68:32:bc:58:89 >>>> inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0 >>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>>> RX packets:1 errors:0 dropped:1 overruns:0 frame:0 >>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:1000 >>>> RX bytes:76 (76.0 B) TX bytes:0 (0.0 B) >>>> >>>> However, I've no idea how your device is meant to be used once it's >>>> connected a an USBNET device. And now you've j
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
I can see thru route that I am getting out over my wired LAN: route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default my.meraki.net 0.0.0.0 UG0 00 eth0 10.1.2.0* 255.255.255.0 U 0 00 eth0 192.168.7.0 * 255.255.255.0 U 0 00 usb0 -- 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/55506e5f-a647-4f0c-bcd1-cb785ba28df4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
I was wondering about multiple usb connections... So here is thing though. I am now ssh'd into the device over ethernet. I see the usbo with ifconfig: ifconfig eth0 Link encap:Ethernet HWaddr 78:a5:04:f8:61:5e inet addr:10.1.2.169 Bcast:10.1.2.255 Mask:255.255.255.0 inet6 addr: fe80::7aa5:4ff:fef8:615e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:881 errors:0 dropped:9 overruns:0 frame:0 TX packets:282 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:87981 (85.9 KiB) TX bytes:37544 (36.6 KiB) Interrupt:40 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) usb0 Link encap:Ethernet HWaddr 02:80:70:00:04:70 inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0 inet6 addr: fe80::80:70ff:fe00:470/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:5387 (5.2 KiB) But now how do I test I am connected out that way instead of over the ethernet cable lol? At the end of the day I want these devices to talk out the cell module to cloud servers and be able to acess them in the field via ssh. I have statically provisioned SIM cards so I can get to them. On Wednesday, April 20, 2016 at 4:41:40 PM UTC-7, William Hermans wrote: > > And sorry . . > > william@beaglebone:~$ sudo ifconfig usb0 192.168.7.2 > THEN > william@beaglebone:~$ sudo ifconfig > . . . > > usb0 Link encap:Ethernet HWaddr 7e:68:32:bc:58:89 > inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1 errors:0 dropped:1 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:76 (76.0 B) TX bytes:0 (0.0 B) > > > > > On Wed, Apr 20, 2016 at 4:39 PM, William Hermans > wrote: > >> For instance: >> >> william@beaglebone:~$ ls /sys/class/net >> eth0 lo >> william@beaglebone:~$ sudo modprobe g_ether >> >> william@beaglebone:~$ ls /sys/class/net >> eth0 lo usb0 >> >> william@beaglebone:~$ sudo ifconfig >> . . . >> usb0 Link encap:Ethernet HWaddr 7e:68:32:bc:58:89 >> inet addr:192.168.7.2 Bcast:192.168.7.255 Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:1 errors:0 dropped:1 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:76 (76.0 B) TX bytes:0 (0.0 B) >> >> However, I've no idea how your device is meant to be used once it's >> connected a an USBNET device. And now you've just posted, and you've got a >> problem. >> >> You're connected to your beaglebone via USB too which may cause problems. >> You're only allowed to use one instance of a gadget driver, total. So you >> can not use USB serial, or USB networkign to the beaglebone in order for >> your device to work. You're going power via barrel jack, connect to the >> beaglebone over the ethernet port. *OR* if you want to still power via USB, >> you're going to have to figure out how to disable the USB gadget drivers >> for the beaglebone, while still having it available for your external >> device. I did notice you had TTYACM0 enabled so that'll definitely have to >> go away. >> >> >> >> On Wed, Apr 20, 2016 at 4:27 PM, William Hermans > > wrote: >> >>> What output do you get from: >>> >>> $ ls /sys/class/net >>> >>> ? >>> >>> >>> On Wed, Apr 20, 2016 at 4:22 PM, Matt99eo >> > wrote: >>> >>>> PPP currently not supported the modem MFR. Hopefully a firmware update >>>> coming soon. In the meantime they have pointed me at cdc_ether. >>>> >>>> >>>> >>>> On Wednesday, April 20, 2016 at 4:19:27 PM UTC-7, RobertCNelson wrote: >>>>> >>>>> >>>
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
ls /sys/class/net/ eth0 lo usb0 usb1 usb0 is usb connection to from host dev machine to BBB USB1 is the module On Wednesday, April 20, 2016 at 4:27:56 PM UTC-7, William Hermans wrote: > > What output do you get from: > > $ ls /sys/class/net > > ? > > > On Wed, Apr 20, 2016 at 4:22 PM, Matt99eo > wrote: > >> PPP currently not supported the modem MFR. Hopefully a firmware update >> coming soon. In the meantime they have pointed me at cdc_ether. >> >> >> >> On Wednesday, April 20, 2016 at 4:19:27 PM UTC-7, RobertCNelson wrote: >>> >>> >>> >>> On Wed, Apr 20, 2016 at 6:15 PM, Matt99eo wrote: >>> >>>> So how do I get the BBB to take the reins and do configure this bad >>>> boy!? >>>> >>> >>> pppd >>> >>> https://wiki.archlinux.org/index.php/3G_and_GPRS_modems_with_pppd >>> >>> 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 . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/a8f290c9-e1ec-4bfb-b0a8-0472a72b9590%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/a8f290c9-e1ec-4bfb-b0a8-0472a72b9590%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/149e054f-5bb9-4752-bcfd-8f67090f1f73%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
PPP currently not supported the modem MFR. Hopefully a firmware update coming soon. In the meantime they have pointed me at cdc_ether. On Wednesday, April 20, 2016 at 4:19:27 PM UTC-7, RobertCNelson wrote: > > > > On Wed, Apr 20, 2016 at 6:15 PM, Matt99eo > wrote: > >> So how do I get the BBB to take the reins and do configure this bad boy!? >> > > pppd > > https://wiki.archlinux.org/index.php/3G_and_GPRS_modems_with_pppd > > 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/a8f290c9-e1ec-4bfb-b0a8-0472a72b9590%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
So how do I get the BBB to take the reins and do configure this bad boy!? On Wednesday, April 20, 2016 at 4:10:30 PM UTC-7, RobertCNelson wrote: > > > > On Wed, Apr 20, 2016 at 6:05 PM, Matt Maher Peterson > wrote: > >> 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. >> > > On the desktop, it's the network-manager that's usually doing the auto > configuration behind the scenes.. > > 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/0e37854f-27aa-48f5-b84c-ac3970b90ff1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Flashin BBB with new image I built from RC guide
Yes I saw this stuff and used the /dev/sdX options to get it all on the uSD card. Now that it is on there and I am booted into the serial consol on the bbb running I built do I do all this again but with /mmblk0 option? On Wednesday, April 20, 2016 at 3:09:43 PM UTC-7, RobertCNelson wrote: > > > > On Wed, Apr 20, 2016 at 4:59 PM, Matt99eo > wrote: > >> Hi, >> >> I've followed the guide >> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-RemovemicroSD/SDcard >> >> on compiling a kernel and choosing a root file system in a attempt to build >> a working debian 8 4.1.21 image. >> >> When I insert the sd card into the BBB i get the heart beat LED and can >> access the BBB thru the serial debug console thru my dev machine. >> >> How do I flash what I have built to the eMMC. >> > > Scroll a little bit farther on that page, and that is explained right here: > > https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-eMMC > > > >> >> I tried using /opt/scripts/tools/./beaglebone-black-eMMC-flasher.sh >> >> but I get an error: >> >> root@arm:/opt/scripts/tools# ./beaglebone-black-eMMC-flasher.sh >> Error: script halting, system unrecognized... >> > > That script is not used, explanation is here: > > https://github.com/RobertCNelson/boot-scripts/blob/master/tools/readme.txt > > 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/a5c2a77a-d6c5-4bf3-99ad-fbc8b4911397%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
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 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). >>> >>> Here is what the helpful support is telling me: >>> >>> >>> CDC_ETH is a device support class that allows for the modem to act as >>> LAN connection over USB. There isn't a VIP/PID that needs to be added for >>> the kernel to support it, the Kernel needs to be built to support the >>> CDC_ETH class. >>> >>> When the device is loaded as a CDC_ETH device you will see it enumerate >>> in your system as something like this: >>> >>> [ 17.90] cdc_ether 1-1:1.0 usb0: register 'cdc_ether' at >>> usb-ehci-platform-1, CDC Ethernet Device, 02:10:81:64:89:60 >>> _ >>> >>> When I use lsusb I don't see the device listed (believe I should see Bus >>> 001 Device 001: ID 1d6b:0002) >>> >> >> That's the root hub: http://www.linux-usb.org/usb.ids >> >> 1d6b Linux Foundation >> >> 0001 1.1 root hub >> 0002 2.0 root hub >> 0003 3.0 root hub >> 0100 PTP Gadget >> 0101 Audio Gadget >> 0102 EEM Gadget >> 0103 NCM (Ethernet) Gadget >> 0104 Multifunction Composite Gadget >> 0105 FunctionFS Gadget >> 0200 Qemu Audio Device >> >> run "lsusb" again. ;) >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com
[beagleboard] Flashin BBB with new image I built from RC guide
Hi, I've followed the guide https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-RemovemicroSD/SDcard on compiling a kernel and choosing a root file system in a attempt to build a working debian 8 4.1.21 image. When I insert the sd card into the BBB i get the heart beat LED and can access the BBB thru the serial debug console thru my dev machine. How do I flash what I have built to the eMMC. I tried using /opt/scripts/tools/./beaglebone-black-eMMC-flasher.sh but I get an error: root@arm:/opt/scripts/tools# ./beaglebone-black-eMMC-flasher.sh Error: script halting, system unrecognized... What am I missing here? Kind Regards, -- 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/bfb2d401-621e-43be-8775-60fe2056ddd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
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 > 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). >> >> Here is what the helpful support is telling me: >> >> >> CDC_ETH is a device support class that allows for the modem to act as LAN >> connection over USB. There isn't a VIP/PID that needs to be added for the >> kernel to support it, the Kernel needs to be built to support the CDC_ETH >> class. >> >> When the device is loaded as a CDC_ETH device you will see it enumerate >> in your system as something like this: >> >> [ 17.90] cdc_ether 1-1:1.0 usb0: register 'cdc_ether' at >> usb-ehci-platform-1, CDC Ethernet Device, 02:10:81:64:89:60 >> _ >> >> When I use lsusb I don't see the device listed (believe I should see Bus >> 001 Device 001: ID 1d6b:0002) >> > > That's the root hub: http://www.linux-usb.org/usb.ids > > 1d6b Linux Foundation > > 0001 1.1 root hub > 0002 2.0 root hub > 0003 3.0 root hub > 0100 PTP Gadget > 0101 Audio Gadget > 0102 EEM Gadget > 0103 NCM (Ethernet) Gadget > 0104 Multifunction Composite Gadget > 0105 FunctionFS Gadget > 0200 Qemu Audio Device > > run "lsusb" again. ;) > > 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/39d5ea0a-120b-44e1-a200-c090a166505d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] CDC_ETHER in Debian 3.8.13-bone70
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] CDC_ETHER in Debian 3.8.13-bone70
Sorry for the hand holding but what files am I comparing? On Friday, April 15, 2016 at 3:06:42 PM UTC-7, RobertCNelson wrote: > > > > On Fri, Apr 15, 2016 at 5:00 PM, Matt99eo > wrote: > >> Hi RC, >> >> I'll check if it is. >> >> Looking at your reply does this mean that CDCETHER is enabled in my >> kernel version (assuming you are saying it is in there as I see =y)? Is >> CDC_ETHER and CDCETHER the same thing? >> If it is, why would I not see the device? >> >> The document for the module I am looking claims that it will simply >> appear when connected on boot in Debian 8.3 (kernel 4.1.15) but is not >> supported in Debian 7.x (kernel 3.8.x) >> > > Sounds more like, this device's vid/pid has been added to at-least > v4.1.15, thus it works out of the box.. > > git checkout both kernel's and use meld to compare the two drivers.. it's > probally just a vid/pid addition.. > > 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] CDC_ETHER in Debian 3.8.13-bone70
Hi RC, I'll check if it is. Looking at your reply does this mean that CDCETHER is enabled in my kernel version (assuming you are saying it is in there as I see =y)? Is CDC_ETHER and CDCETHER the same thing? If it is, why would I not see the device? The document for the module I am looking claims that it will simply appear when connected on boot in Debian 8.3 (kernel 4.1.15) but is not supported in Debian 7.x (kernel 3.8.x) On Friday, April 15, 2016 at 2:50:51 PM UTC-7, RobertCNelson wrote: > > > > On Fri, Apr 15, 2016 at 4:47 PM, Matt99eo > wrote: > >> Hi, >> >> I am working with a cellular module that requires the linux kernel to >> have support for theCDC_ETHER USB device class. >> >> My current kernel version is 3.8.13 (Debian Wheezy verion 7) (I know, its >> old... but too much invested to change right now). >> >> I believe CDC_ETHER is not supported but I do not know how to tell. >> > > CONFIG_USB_NET_CDCETHER=y > CONFIG_USB_NET_CDC_EEM=m > CONFIG_USB_NET_CDC_NCM=y > CONFIG_USB_NET_CDC_MBIM=m > > > > https://github.com/beagleboard/linux/blob/dc982e80db34b0448c91ae1597ef38a3f4a95e35/arch/arm/configs/bb.org_defconfig#L1739-L1742 > > Is that requirement documentation public? > > > 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] CDC_ETHER in Debian 3.8.13-bone70
Hi, I am working with a cellular module that requires the linux kernel to have support for theCDC_ETHER USB device class. My current kernel version is 3.8.13 (Debian Wheezy verion 7) (I know, its old... but too much invested to change right now). I believe CDC_ETHER is not supported but I do not know how to tell. How do I go about patching this into the kernel? Thanks in advance -- 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 a linux image for IoT on the Beaglebone Black
Hi, There are so many different flavors linux out there for the BBB I am having a difficulty choosing one for my application. The application is remote monitoring of sensors in the IoT realm. I am at odds with some of the newer releases that have done away with device tree overlays as I seam not get how to manage custom GPIO pin assignments outside of the old 3.8.x device trees. If you were to start fresh what distro would you choose and why for this type of application? -- 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.
