On 24-12-2013 9:27, Bas de Bruijn wrote: > Hi Bas and Charles > Thanks again for your patience and trying to solve my problems. I have no > doubt that I do something simply wrong by my lack of experience. Probably > something very normal in the linux world but not (yet) for me. > > This morning I made sure I have a fresh system. I have taken the > debian-7.1-machinekit-armhf-2013-09-02.tar.xz from Charles his blog and > followed the installation of the SD image via my Ubuntu VM on parallels for > my Mac. > > I have not connected the BeBoPr+ to the BBB. > > I have done a “dmesg" and a "dmesg grep | capemgr" and put this on pastebin > as Bas proposes. > > Now this is as fresh an installation as I can get (and i didn’t knowingly > screw up the previous one). > > If I understand correctly then: > [1] I need to be sure the "cape-bebopr-brdg” overlay _is not_ loaded > [2] I need to make sure BB-LCNC-BEBOPRBR-00A0 overlay _is_ loaded > > now what I need to know is if I load the BB-LCNC-BEBOPRBR-00A0 via the > /boot/uboot/uEnv.txt like > "optargs=capemgr.enable_partno=BB-LCNC-BEBOPRBR-00A0" > > here is the pastebin link of my freshly installation > http://pastebin.com/6LKVhCpe
Thanks Bas, Nothing strange in the bootlog as far as I can see. What puzzles me is why you have disabled the HDMI and eMMC devices and not the HDMIN. Since you have a BeBoPr+ configuration, you're able to use the HDMI and eMMC normally. Is there a specific you to disable these two devices? Now the boot log doesn't show any loading of a BeBoPr overlay, so you have a 'clean' system. I would like to find out if we can load the original BeBoPr overlay (cape-bebopr-brdg) on your Xenomai kernel. If that fails you have to remove the SD card and boot Angstrom. (BTW: do you have a serial console cable for the BBB? A proper console makes diagnosing problems a lot easier). Now after booting, issue the command echo cape-bebopr-brdg:R2 > /sys/devices/bone.capemgr*/slots After that, what output do the following two commands give?: dmesg | grep capemgr cat /sys/devices/bone.capemgr*/slots -- Bas > > On 24 Dec 2013, at 00:19, Bas Laarhoven <s...@xs4all.nl> wrote: > >> Bas, >> >> Note that you're using a unix system and not windows, so don't expect a >> pop-up window or blue screen if something fails! You'll have to check >> the results yourself. So after writing to the slots file, read it back >> to see if it was successful (cat /sys/devices/bone.capemgr.8/slots) >> >> Can you post the entire bootlog on pastebin.com so we can see what your >> system is doing and whether the overlay is loaded properly? >> Use dmesg to show the log. You can redirect it to a textfile (dmesg >>> /tmp/killme.txt) or use your terminal emulator to capture the text. >> -- Bas >> >> On 23-12-2013 19:15, Bas de Bruijn wrote: >>> On 23 Dec 2013, at 13:13, Bas Laarhoven <s...@xs4all.nl> wrote: >>> >>>> On 23-12-2013 10:24, Bas de Bruijn wrote: >>>>> Yes, as i understood correctly that’s because I use the bebopr+ bridge >>>>> and there is a pin mixup. I looked in /lib/firmwares and there doesn’t >>>>> seem to be a cape-bebopr-brdg. but a cape-bebopr-brdg-R2 is there so I >>>>> now have changed the uEnv.txt to >>>> Good, the cape-bebopr-brdg is the one I know about ;-) >>>> You don't need to load it from uEnv.txt, at least not for testing. Try >>>> "echo cape-bebopr-brdg:R2 > /sys/devices/bone.capemgr*/slots" (or >>>> something very close to that). This overlay also configures the ADC, so >>>> no need for a separate overlay! >>>> >>>> The cape-bebopr-brdg overlay might not work with LinuxCNC, but at least >>>> you should be able to test the ADC. >>> every results with the ‘0’ are with the jumper on J8, the last ones >>> (without the ‘0’ were with jumper on J7 and last 4 with jumper on J6 >>> Ik krijg zo langzamerhand een langere sik als de Sint :) >>> I get the feeling we’re running in circles and I propose to do one step >>> back and make my configuration of BBB with BeBoPr+ the same as yours >>> >>> root@arm:/sys/devices# echo cape-bebopr-brdg:R2 > >>> /sys/devices/bone_capemgr.8/slots >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1226 >>> 0 >>> 1133 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1265 >>> 0 >>> 824 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1310 >>> 0 >>> 748 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1227 >>> 0 >>> 748 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1227 >>> 0 >>> 1132 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1270 >>> 0 >>> 832 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1325 >>> 0 >>> 747 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1269 >>> 4064 >>> 3689 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1268 >>> 4077 >>> 3169 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1355 >>> 4075 >>> 3533 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1412 >>> 4079 >>> 3697 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1267 >>> 4070 >>> 3723 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1268 >>> 4070 >>> 3218 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1358 >>> 4073 >>> 3552 >>> root@arm:/sys/devices# cat `find /sys/devices/ -name in_voltage[456]_raw` >>> 1415 >>> 4070 >>> 3714 >>> root@arm:/sys/devices# >>> >>> ------------------------------------------------------------------------------ >>> Rapidly troubleshoot problems before they affect your business. Most IT >>> organizations don't have a clear picture of how application performance >>> affects their revenue. With AppDynamics, you get 100% visibility into your >>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics >>> Pro! >>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Emc-users mailing list >>> Emc-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/emc-users >> >> ------------------------------------------------------------------------------ >> Rapidly troubleshoot problems before they affect your business. Most IT >> organizations don't have a clear picture of how application performance >> affects their revenue. With AppDynamics, you get 100% visibility into your >> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics >> Pro! >> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk >> _______________________________________________ >> Emc-users mailing list >> Emc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
