[beagleboard] WeatherCape Shell and SQLite scripts.
I wrote Shell and SQLite scripts for the WeatherCape. There is a succinct README file. You can get it at https://github.com/jaltone/WeatherCape Much thanks to Robert C Nelson for exposing the WeatherCape sensor device files. That was the difficult part. This is licensed the same as the BBB, so feel free to modify it and make it your own. -- 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] Does apt-get upgrade not update BoneScript?
So you are saying I will still need to stay with the 7.9 image series for BoneScript for the foreseeable future? Will the image be 2016-01-31 or something else? I notice the beagleboard.org/latest-images page was last edited Jan 31, 2016 but the latest 8.3 image is 2016-01-24 and the latest 7.9 is the 2015-11-12 I'm currently using. Can I get to 8.3 2016-01-24 from 8.2 2015-12-06 with apt-get updates and installs? or should I download the new image and start over? The node-red I've installed for the 2015-11-12 image appears to use BoneScript for the "Beaglebone" nodes as I had to edit the config file to allow bonescript to get them to work. But there is no PWM node, although the GPIO nodes seem to throw the same errors in the terminal that ran the node-red-pi command to start everything as does the tab in Cloud9 that runs the BoneScript example programs. (I haven't bothered with starting node-red automatically yet). Thanks for explaining the bmap tool, I'd wondered what the *.bmap files were for, when I've downloaded images I'd just figured I didn't need them :) I think the "top level" beaglebone.localhost web page needs some serious updating as the link: http://192.168.7.2/bone101/Support/BoneScript/updates/ is still talking about Angstrom. This is all someone like my friend would likely see if he'd just bought a board and hoped for the best. He'd quickly be terminally dead-in-the-water confused and either just give up on the idea or go back to trying to implement it by wiring up timers and relays. He's in a rural area with only cell-phone service Internet access so hours of Googling and websurfing is just not practical. Books like the "Beaglebone Cookbook" and ""Exploring Beaglebone are great, but they are wrong in ways very disconcerting to a beginner by the time they are published. While the link to beagleboard.org/latest-images is good, there is nothing there to give him a clue as to if he'll need 7.9 8.3 or Angstrom. This is not helped by the fact that boards like the BBG seem to be shipping with completely broken images in the eMMC -- there are other threads here about this. On Saturday, January 30, 2016 at 1:46:45 PM UTC-6, RobertCNelson wrote: > > > On Jan 30, 2016 1:36 PM, "Wally Bkg" > > wrote: > > > > Great! I'll be among the first to download Sunday's new Jessie image! > Do you know if the BoneScript PWM is now working? > > Bonescript is still only written for 3.8, it needs to be ported to the 4.1 > config-pin interface. > > > Most of my hours wasted is re-installing and re-configuring the > non-standard stuff I use, so I'm not sure how bmaptool (which I assume is a > "better" SD card burner) would buy me much. I start dd and do something > else -- the dd is always done by the time I get back to it :) > > bmaptool does things like skipping writing zero's which dd has to write. > For each img.xz on the file server there is a matching .bmap file. > > > I know apt-get upgrade shouldn't break anything, but I'd been using a > Jessie testing image (I think 8.1 from about April or May 2015) on both my > BBW and BBB I upgraded them both (after skipping several other image > releases) before rebooting either, and neither would allow a login > afterwards -- no X on the BBB and no ssh on both. I could recover my files > from the SD cards so it wasn't a total loss. I posted a message about it > shortly after it happened, but I think my Google Groups filters (which I > find less than helpful) put it where nobody seemed to notice it. > > From may 2015, there was a very big upgrade in lxqt, I tried to minimize > the issue (upstream changed there c++ namespace in 0.10.0) I put out a note > to this usergroup on how to upgrade with out the desktop breaking.. > > > I've come to the conclusion I've a hardware USB issue with my A5A BBB, > it sometimes works, more often not :( > > 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Make a backup of contents of one beaglebone black and install said contents on a second BBB
First question, is your system running from an SD card or the eMMC? If running from an SD card, just "clone" or duplicate the card using Windows or Linux tools. If its running from the eMMC (on-board storage). It'll require knowing some Linux commands. For a beginner, I'd suggest downloading an image as close to what is in your eMMC as you can, write it to an SD and then mounting the SD card using a USB to SD card adapter (this gets you the correct partition layout) on the BBB and using rsync or dd to clone (copy) the / (root) and /boot partitions from your eMMC to the SD card. rsync is "easier" in that it uses mount points instead of raw device names for the partitions but could easily run out of space while copying the partitions. dd is problematic if your SD card is smaller than the eMMC (not all 4GB cards are really 4GB), using an 8GB card should fix this, but for rsync you'd have to boot the SD card image on your BBB and run the grow_partition.sh script to make the extra space available before rebooting the eMMC and mounting the SD card over USB. I don't know if you can "hot plug" and SD card into the BBB slot, it could very well depend on your software version which is why I suggest mounting it on the BBB using a USB SD adapter. uname -a will tell you the kernel and cat /etc/dogtag will tell you the image -- something like 2015-03-01 Debian or Angstrom. If Angstrom, docs are pretty scarce :( I'm sure there are other cloning tools, but if its Angstrom you may be limited to dd or rsync. I gave up on Angstrom as soon as the Debian images came out because I was frustrated by the differences from Ubuntu/Debian and its dearth of documentation. Maybe a link to the procedures you've found would clarify what exactly is "over your head". If you have a recent Linux computer, when you plug in the BBB over the USB it should mount the rootfs and boot partitions of the eMMC so you could use rsync, dd or other tools to clone their contents to an SD card. I don't know if tools exist for current Windows versions mounting of Linux partitions, although years ago I mounted Linux ext2 partitions on Windows 2000. Once you succeed with the clone you'll have to edit /etc/hosts and /etc/hostname on one of the systems before plugging them into the same network so they have different names. Unfortunately this is all made more difficult than most anyone is happy with by the rapid evolution of Linux during the Beaglebone's existance. Out of curiosity, I just "hot plugged" an SD card into my BBG booted from the eMMC and dmesg shows mmcblk1: p1 p2 are created, although they don't auto-mount. So if your BBB image is new enough it may be pretty easy to plug in an 8GB SD card and use dd to clone the eMMC to the SD card (no SD card formatting would be required). debian@beaglebone:~$ ls /dev/mmc* /dev/mmcblk0 /dev/mmcblk0boot1 /dev/mmcblk0p2 /dev/mmcblk1p1 /dev/mmcblk0boot0 /dev/mmcblk0p1 /dev/mmcblk1/dev/mmcblk1p2 I'm currently using the "latest" 7.9 image 2015-11-12 so I don't know at what image this started working. On Saturday, January 30, 2016 at 7:37:41 PM UTC-6, canis wrote: > > Hello Beagleboard Forum, > > First time post, thanks so much for this resource. > > I am a complete newbie, trying to copy the contents of one beaglebone > black to a second beagle bone black. The original BBB was part of a 3D > printer kit- I am trying to make a second printer which will be repurposed. > > > Info on-line suggests that the a beaglebone black can be backed up to a > micro SD card, but the procedures I have found to date are over my head. > > Any suggestions would be MOST appreciated. > > Many thanks, > canis > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Will the webcast "Taking the BeagleBone Cookbook recipes beyond BeagleBone Black" be available?
I followed you link and registered, and got redirected to: http://event.on24.com/eventRegistration/console/EventConsoleNG.jsp?uimode=nextgeneration&eventid=1107482&sessionid=1&username=&partnerref=&format=fhaudio&mobile=false&flashsupportedmobiledevice=false&helpcenter=false&key=3FF85FECC68CE9D6CA13256C89404E5A&text_language_id=en&playerwidth=1000&playerheight=650&overwritelobby=y&eventuserid=134426098&contenttype=A&mediametricsessionid=106170746&mediametricid=1630698&usercd=134426098&mode=launch But its just a blank black page. Looks like they are no longer serving up the webcast. I followed Soapy Smith's youtube link and its not there yet, the newest is 4 days old. On Saturday, January 30, 2016 at 7:43:16 AM UTC-6, Specialcomp wrote: > > Watch the webcast: > http://post.oreilly.com/rd/9z1z7717pn7sc30vgj96qr0h1dcanjo9io3bn1ohngg > > Signup for webcast event: > > http://event.on24.com/r.htm?e=1107482&s=1&k=3FF85FECC68CE9D6CA13256C89404E5A > > Other book promotion webcasts: > http://www.oreilly.com/webcasts/ > > > On Fri, Jan 29, 2016 at 4:14 PM, Wally Bkg > wrote: > >> I'm well aware of the no video, but IMHO its a feature, not a bug. If >> you've ever actually tried to use a GUI on the HDMI interface, performance >> over ssh -X is better. Its a lot of GPIO pins to give up for such a lame >> display. >> >> Thanks for the link, I'll check it in a few days as you suggest. >> >> >> >> >> On Friday, January 29, 2016 at 5:03:06 PM UTC-6, Soapy Smith wrote: >>> >>> I missed the webcast as well. I'm not sure if it will show up here, but it looks like the newest video is 2 days old: >>> >>> https://www.youtube.com/user/OreillyMedia/videos >>> >>> So maybe in the next few days the recording will appear. >>> >>> Regarding the BBG, one thing for sure the chip that does HDMI is not >>> there. No video. >>> >>> Regards, >>> Greg >>> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Will the webcast "Taking the BeagleBone Cookbook recipes beyond BeagleBone Black" be available?
Register for Jason's Jan 28 webcast: http://www.oreilly.com/pub/e/3639/ Other book promotion webcasts: http://www.oreilly.com/webcasts/ On Sun, Jan 31, 2016 at 12:36 PM, Wally Bkg wrote: > I followed you link and registered, and got redirected to: > > > http://event.on24.com/eventRegistration/console/EventConsoleNG.jsp?uimode=nextgeneration&eventid=1107482&sessionid=1&username=&partnerref=&format=fhaudio&mobile=false&flashsupportedmobiledevice=false&helpcenter=false&key=3FF85FECC68CE9D6CA13256C89404E5A&text_language_id=en&playerwidth=1000&playerheight=650&overwritelobby=y&eventuserid=134426098&contenttype=A&mediametricsessionid=106170746&mediametricid=1630698&usercd=134426098&mode=launch > > But its just a blank black page. Looks like they are no longer serving up > the webcast. > > > I followed Soapy Smith's youtube link and its not there yet, the newest > is 4 days old. > > > > > On Saturday, January 30, 2016 at 7:43:16 AM UTC-6, Specialcomp wrote: >> >> Watch the webcast: >> http://post.oreilly.com/rd/9z1z7717pn7sc30vgj96qr0h1dcanjo9io3bn1ohngg >> >> Signup for webcast event: >> >> http://event.on24.com/r.htm?e=1107482&s=1&k=3FF85FECC68CE9D6CA13256C89404E5A >> >> Other book promotion webcasts: >> http://www.oreilly.com/webcasts/ >> >> >> On Fri, Jan 29, 2016 at 4:14 PM, Wally Bkg wrote: >> >>> I'm well aware of the no video, but IMHO its a feature, not a bug. If >>> you've ever actually tried to use a GUI on the HDMI interface, performance >>> over ssh -X is better. Its a lot of GPIO pins to give up for such a lame >>> display. >>> >>> Thanks for the link, I'll check it in a few days as you suggest. >>> >>> >>> >>> >>> On Friday, January 29, 2016 at 5:03:06 PM UTC-6, Soapy Smith wrote: I missed the webcast as well. I'm not sure if it will show up here, > but it looks like the newest video is 2 days old: > https://www.youtube.com/user/OreillyMedia/videos So maybe in the next few days the recording will appear. Regarding the BBG, one thing for sure the chip that does HDMI is not there. No video. Regards, Greg >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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] Does apt-get upgrade not update BoneScript?
On Sun, Jan 31, 2016 at 10:42 AM, Wally Bkg wrote: > So you are saying I will still need to stay with the 7.9 image series for > BoneScript for the foreseeable future? or install the 3.8.x based kernel on jessie. > Will the image be 2016-01-31 or something else? I notice the > beagleboard.org/latest-images page was last edited Jan 31, 2016 but the > latest 8.3 image is 2016-01-24 and the latest 7.9 is the 2015-11-12 I'm > currently using. I'm not in control of that page: Watch: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian > Can I get to 8.3 2016-01-24 from 8.2 2015-12-06 with apt-get updates and > installs? or should I download the new image and start over? Yes/No Yes, you will get the same packages.. No, you will not get the "extra" packages/things i added to "2016-01-24"... > The node-red I've installed for the 2015-11-12 image appears to use > BoneScript for the "Beaglebone" nodes as I had to edit the config file to > allow bonescript to get them to work. But there is no PWM node, although > the GPIO nodes seem to throw the same errors in the terminal that ran the > node-red-pi command to start everything as does the tab in Cloud9 that runs > the BoneScript example programs. (I haven't bothered with starting node-red > automatically yet). > > > Thanks for explaining the bmap tool, I'd wondered what the *.bmap files were > for, when I've downloaded images I'd just figured I didn't need them :) > > > I think the "top level" beaglebone.localhost web page needs some serious > updating as the link: > http://192.168.7.2/bone101/Support/BoneScript/updates/ > is still talking about Angstrom. That repo is right here: https://github.com/beagleboard/beaglebone-getting-started go ahead fork it and submit pull requests. > > This is all someone like my friend would likely see if he'd just bought a > board and hoped for the best. He'd quickly be terminally dead-in-the-water > confused and either just give up on the idea or go back to trying to > implement it by wiring up timers and relays. He's in a rural area with only > cell-phone service Internet access so hours of Googling and websurfing is > just not practical. Books like the "Beaglebone Cookbook" and ""Exploring > Beaglebone are great, but they are wrong in ways very disconcerting to a > beginner by the time they are published. > > While the link to beagleboard.org/latest-images is good, there is nothing > there to give him a clue as to if he'll need 7.9 8.3 or Angstrom. This is > not helped by the fact that boards like the BBG seem to be shipping with > completely broken images in the eMMC -- there are other threads here about > this. Angstrom is dead, it's maintainer left for a job at linaro, NO ONE has stepped up since the fall of 2013 to pick up maintenance. 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] Read analog inputs BBB running Debian Jessie
I'm new to the beagle bone and am having difficulty reading the output of a thumb joystick. I'm running Debian Jessie 8.2 Linux kernel 4.1.12-ti-r29 I've connected the thumb joystick as follows vcc - p9_32 gnd - p9_34 hor - p9_36 ver - p9_38 i did not connect the pin for the switch because it is not needed. All the instructions that I can find on the topic suggest that you have to enable the analog inputs on the BBB. The instructions for doing so require using "cape-bone-iio". I've read that cape-bone or bone-cape isn't the way things are done on linux kernels in the "4.x" range. So my question is, how do I get the joystick output on my BBB running Debian 8.2 and Kernel 4.1? Any help is greatly appreciated. Thanks. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Read analog inputs BBB running Debian Jessie
On Sun, Jan 31, 2016 at 6:43 PM, wrote: > I'm new to the beagle bone and am having difficulty reading the output of a > thumb joystick. > > I'm running Debian Jessie 8.2 > Linux kernel 4.1.12-ti-r29 > > I've connected the thumb joystick as follows > > vcc - p9_32 > gnd - p9_34 > hor - p9_36 > ver - p9_38 > > i did not connect the pin for the switch because it is not needed. > > > All the instructions that I can find on the topic suggest that you have to > enable the analog inputs on the BBB. The instructions for doing so require > using "cape-bone-iio". I've read that cape-bone or bone-cape isn't the way > things are done on linux kernels in the "4.x" range. > > So my question is, how do I get the joystick output on my BBB running Debian > 8.2 and Kernel 4.1? sudo sh -c "echo BB-ADC' > /sys/devices/platform/bone_capemgr/slots" 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] Read analog inputs BBB running Debian Jessie
On Sun, Jan 31, 2016 at 6:58 PM, Robert Nelson wrote: > On Sun, Jan 31, 2016 at 6:43 PM, wrote: >> I'm new to the beagle bone and am having difficulty reading the output of a >> thumb joystick. >> >> I'm running Debian Jessie 8.2 >> Linux kernel 4.1.12-ti-r29 >> >> I've connected the thumb joystick as follows >> >> vcc - p9_32 >> gnd - p9_34 >> hor - p9_36 >> ver - p9_38 >> >> i did not connect the pin for the switch because it is not needed. >> >> >> All the instructions that I can find on the topic suggest that you have to >> enable the analog inputs on the BBB. The instructions for doing so require >> using "cape-bone-iio". I've read that cape-bone or bone-cape isn't the way >> things are done on linux kernels in the "4.x" range. >> >> So my question is, how do I get the joystick output on my BBB running Debian >> 8.2 and Kernel 4.1? > > sudo sh -c "echo BB-ADC' > /sys/devices/platform/bone_capemgr/slots" obvious copy/paste error: sudo sh -c "echo 'BB-ADC' > /sys/devices/platform/bone_capemgr/slots" 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] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12
I am trying to get the SPI bus to work, unfortunately it will not change states. Is there something obvious that I am missing. I believe that this ties into my previous post on strace and is the reason that I cannot my LCD to work. Thanks in advance to those that respond to this post. Linux beaglebone 4.1.15-ti-r43 #1 SMP PREEMPT Thu Jan 21 22:33:31 UTC 2016 armv7l GNU/Linux BeagleBoard.org Debian Image 2015-11-12 root@beaglebone:~# . ~/.profile root@beaglebone:~# echo $SLOTS /sys/devices/platform/bone_capemgr/slots root@beaglebone:~# echo $PINS /sys/kernel/debug/pinctrl/44e10800.pinmux/pins root@beaglebone:~# ls DM-SPI-Test-00A0.dtbo DM-SPI-Test.dtbo DM-SPI-Test.dts bb.org-overlays boneDeviceTree exploringBB git root@beaglebone:~# dtc -O dtb -o DM-SPI-Test-00A0.dtbo -b 0 -@ DM-SPI-Test.dts root@beaglebone:~# cp DM-SPI-Test-00A0.dtbo /lib/firmware root@beaglebone:~# cd /lib/firmware root@beaglebone:/lib/firmware# ls ADAFRUIT-SPI0-00A0.dtbo BB-UART3-00A0.dtbo PyBBIO-gpio0_11-00A0.dtbo PyBBIO-gpio1_3-00A0.dtbo PyBBIO-gpio3_19-00A0.dtbo ADAFRUIT-SPI1-00A0.dtbo BB-UART4-00A0.dtbo PyBBIO-gpio0_12-00A0.dtbo PyBBIO-gpio1_30-00A0.dtbo PyBBIO-gpio3_21-00A0.dtbo ADAFRUIT-UART1-00A0.dtbo BB-UART5-00A0.dtbo PyBBIO-gpio0_13-00A0.dtbo PyBBIO-gpio1_31-00A0.dtbo PyBBIO-usr0-00A0.dtbo ADAFRUIT-UART2-00A0.dtbo BB-W1-P9.12-00A0.dtbo PyBBIO-gpio0_14-00A0.dtbo PyBBIO-gpio1_4-00A0.dtbo PyBBIO-usr1-00A0.dtbo ADAFRUIT-UART4-00A0.dtbo DM-SPI-Test-00A0.dtbo PyBBIO-gpio0_15-00A0.dtbo PyBBIO-gpio1_5-00A0.dtbo PyBBIO-usr2-00A0.dtbo ADAFRUIT-UART5-00A0.dtbo DVK530-LCD4-01-00A0.dtbo PyBBIO-gpio0_2-00A0.dtbo PyBBIO-gpio1_6-00A0.dtbo PyBBIO-usr3-00A0.dtbo BB-ADC-00A0.dtbo LICENCE.atheros_firmware PyBBIO-gpio0_20-00A0.dtbo PyBBIO-gpio1_7-00A0.dtbo bone_eqep0-00A0.dtbo BB-BBBMINI-00A0.dtbo LICENCE.broadcom_bcm43xx PyBBIO-gpio0_22-00A0.dtbo PyBBIO-gpio2_1-00A0.dtbo bone_eqep1-00A0.dtbo BB-BONE-AUDI-02-00A0.dtbo LICENCE.rtlwifi_firmware.txt PyBBIO-gpio0_23-00A0.dtbo PyBBIO-gpio2_10-00A0.dtbo bone_eqep2-00A0.dtbo BB-BONE-BACONE-00A0.dtbo LICENCE.ti-connectivity PyBBIO-gpio0_26-00A0.dtbo PyBBIO-gpio2_11-00A0.dtbo bone_eqep2b.dtbo BB-BONE-CRYPTO-00A0.dtbo NL-AB-BBBC-00D0.dtbo PyBBIO-gpio0_27-00A0.dtbo PyBBIO-gpio2_12-00A0.dtbo brcm BB-BONE-DVID-01-00A3.dtbo PyBBIO-ADC-00A0.dtbo PyBBIO-gpio0_3-00A0.dtbo PyBBIO-gpio2_13-00A0.dtbo cape-CBB-Serial-r01.dtbo BB-BONE-LCD3-01-00A2.dtbo PyBBIO-AIN0-00A0.dtbo PyBBIO-gpio0_30-00A0.dtbo PyBBIO-gpio2_14-00A0.dtbo cape-bone-ibb-00A0.dtbo BB-BONE-LCD4-01-00A1.dtbo PyBBIO-AIN1-00A0.dtbo PyBBIO-gpio0_31-00A0.dtbo PyBBIO-gpio2_15-00A0.dtbo cape-univ-audio-00A0.dtbo BB-BONE-LCD7-01-00A3.dtbo PyBBIO-AIN2-00A0.dtbo PyBBIO-gpio0_4-00A0.dtbo PyBBIO-gpio2_16-00A0.dtbo cape-univ-emmc-00A0.dtbo BB-BONE-REPLICAP-00B1.dtbo PyBBIO-AIN3-00A0.dtbo PyBBIO-gpio0_5-00A0.dtbo PyBBIO-gpio2_17-00A0.dtbo cape-univ-hdmi-00A0.dtbo BB-BONE-SERL-03-00A1.dtbo PyBBIO-AIN4-00A0.dtbo PyBBIO-gpio0_7-00A0.dtbo PyBBIO-gpio2_2-00A0.dtbo cape-universal-00A0.dtbo BB-BONE-WTHR-01-00B0.dtbo PyBBIO-AIN5-00A0.dtbo PyBBIO-gpio0_8-00A0.dtbo PyBBIO-gpio2_22-00A0.dtbo cape-universaln-00A0.dtbo BB-CAN1-00A0.dtbo PyBBIO-AIN6-00A0.dtbo PyBBIO-gpio0_9-00A0.dtbo PyBBIO-gpio2_23-00A0.dtbo carl9170-1.fw BB-I2C1-00A0.dtbo PyBBIO-AIN7-00A0.dtbo PyBBIO-gpio1_0-00A0.dtbo PyBBIO-gpio2_24-00A0.dtbo dev-USB-PWR-CTL-00A1.dtbo BB-I2C1-PCA9685-00A0.dtbo PyBBIO-ecap0-00A0.dtbo PyBBIO-gpio1_1-00A0.dtbo PyBBIO-gpio2_25-00A0.dtbo htc_9271.fw BB-I2C2-0A00.dtbo PyBBIO-ecap1-00A0.dtbo PyBBIO-gpio1_12-00A0.dtbo PyBBIO-gpio2_3-00A0.dtbo mt7601u.bin BB-RELAY-4PORT-00A0.dtbo PyBBIO-ehrpwm1-00A0.dtbo PyBBIO-gpio1_13-00A0.dtbo PyBBIO-gpio2_4-00A0.dtbo rtlwifi BB-RTC-01-00A0.dtbo PyBBIO-ehrpwm2-00A0.dtbo PyBBIO-gpio1_14-00A0.dtbo PyBBIO-gpio2_5-00A0.dtbo ti-connectivity BB-SPI0-MCP3008-00A0.dtbo PyBBIO-epwmss0-00A0.dtbo PyBBIO-gpio1_15-00A0.dtbo PyBBIO-gpio2_6-00A0.dtbo univ-all-00A0.dtbo BB-SPI1-01-00A0.dtbo PyBBIO-epwmss1-00A0.dtbo PyBBIO-gpio1_16-00A0.dtbo PyBBIO-gpio2_7-00A0.dtbo univ-emmc-00A0.dtbo BB-SPIDEV1-00A0.dtbo PyBBIO-epwmss2-00A0.dtbo PyBBIO-gpio1_17-00A0.dtbo PyBBIO-gpio2_8-00A0.dtbo univ-hdmi-00A0.dtbo BB-SPIDEV1.dtbo PyBBIO-eqep0-00A0.dtbo PyBBIO-gpio1_18-00A0.dtbo PyBBIO-gpio2_9-00A0.dtbo univ-nhdmi-00A0.dtbo BB-SPIDEV1A1-00A0.dtbo PyBBIO-eqep1-00A0.dtbo PyBBIO-gpio1_19-00A0.dtbo PyBBIO-gpio3_14-00A0.dtbo BB-UART1-00A0.dtbo PyBBIO-eqep2-00A0.dtbo PyBBIO-gpio1_2-00A0.dtbo PyBBIO-gpio3_15-00A0.dtbo BB-UART2-00A0.dtbo PyBBIO-eqep2b-00A0.dtbo PyBBIO-gpio1_28-00A0.dtbo PyBBIO-gpio3_16-00A0.dtbo BB-UART2-RTSCTS-00A0.dtbo PyBBIO-gpio0_10-00A0.dtbo PyBBIO-gpio1_29-00A0.dtbo PyBBIO-gpio3_17-00A0.dtbo root@beaglebone:/lib/firmware# cat $SLOTS 0: PF -1 1: PF -1 2: PF -1 3: PF -1 root@beaglebone:/lib/firmware# cat $PINS|grep 950 pin 84 (44e10950.0) 0037 pinctrl-single root@beaglebone:/lib/firmware# cat $PINS|grep 954 pin 85 (44e10954.0) 0037 pin
Re: [beagleboard] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12
On Sun, Jan 31, 2016 at 7:22 PM, Dean wrote: > I am trying to get the SPI bus to work, unfortunately it will not change > states. Is there something obvious that I am missing. I believe that this > ties into my previous post on strace and is the reason that I cannot my LCD > to work. Thanks in advance to those that respond to this post. > > > > Linux beaglebone 4.1.15-ti-r43 #1 SMP PREEMPT Thu Jan 21 22:33:31 UTC 2016 > armv7l GNU/Linux > > BeagleBoard.org Debian Image 2015-11-12 > > > root@beaglebone:~# . ~/.profile > > > root@beaglebone:~# echo $SLOTS > > /sys/devices/platform/bone_capemgr/slots > > > root@beaglebone:~# echo $PINS > > /sys/kernel/debug/pinctrl/44e10800.pinmux/pins > > > root@beaglebone:~# ls > > DM-SPI-Test-00A0.dtbo DM-SPI-Test.dtbo DM-SPI-Test.dts bb.org-overlays > boneDeviceTree exploringBB git > > > root@beaglebone:~# dtc -O dtb -o DM-SPI-Test-00A0.dtbo -b 0 -@ > DM-SPI-Test.dts > > > root@beaglebone:~# cp DM-SPI-Test-00A0.dtbo /lib/firmware > > > root@beaglebone:~# cd /lib/firmware > > > root@beaglebone:/lib/firmware# ls > > ADAFRUIT-SPI0-00A0.dtbo BB-UART3-00A0.dtbo PyBBIO-gpio0_11-00A0.dtbo > PyBBIO-gpio1_3-00A0.dtbo PyBBIO-gpio3_19-00A0.dtbo > > ADAFRUIT-SPI1-00A0.dtbo BB-UART4-00A0.dtbo PyBBIO-gpio0_12-00A0.dtbo > PyBBIO-gpio1_30-00A0.dtbo PyBBIO-gpio3_21-00A0.dtbo > > ADAFRUIT-UART1-00A0.dtbo BB-UART5-00A0.dtbo PyBBIO-gpio0_13-00A0.dtbo > PyBBIO-gpio1_31-00A0.dtbo PyBBIO-usr0-00A0.dtbo > > ADAFRUIT-UART2-00A0.dtbo BB-W1-P9.12-00A0.dtbo PyBBIO-gpio0_14-00A0.dtbo > PyBBIO-gpio1_4-00A0.dtbo PyBBIO-usr1-00A0.dtbo > > ADAFRUIT-UART4-00A0.dtbo DM-SPI-Test-00A0.dtbo PyBBIO-gpio0_15-00A0.dtbo > PyBBIO-gpio1_5-00A0.dtbo PyBBIO-usr2-00A0.dtbo > > ADAFRUIT-UART5-00A0.dtbo DVK530-LCD4-01-00A0.dtbo PyBBIO-gpio0_2-00A0.dtbo > PyBBIO-gpio1_6-00A0.dtbo PyBBIO-usr3-00A0.dtbo > > BB-ADC-00A0.dtbo LICENCE.atheros_firmware PyBBIO-gpio0_20-00A0.dtbo > PyBBIO-gpio1_7-00A0.dtbo bone_eqep0-00A0.dtbo > > BB-BBBMINI-00A0.dtbo LICENCE.broadcom_bcm43xx PyBBIO-gpio0_22-00A0.dtbo > PyBBIO-gpio2_1-00A0.dtbo bone_eqep1-00A0.dtbo > > BB-BONE-AUDI-02-00A0.dtbo LICENCE.rtlwifi_firmware.txt > PyBBIO-gpio0_23-00A0.dtbo PyBBIO-gpio2_10-00A0.dtbo bone_eqep2-00A0.dtbo > > BB-BONE-BACONE-00A0.dtbo LICENCE.ti-connectivity PyBBIO-gpio0_26-00A0.dtbo > PyBBIO-gpio2_11-00A0.dtbo bone_eqep2b.dtbo > > BB-BONE-CRYPTO-00A0.dtbo NL-AB-BBBC-00D0.dtbo PyBBIO-gpio0_27-00A0.dtbo > PyBBIO-gpio2_12-00A0.dtbo brcm > > BB-BONE-DVID-01-00A3.dtbo PyBBIO-ADC-00A0.dtbo PyBBIO-gpio0_3-00A0.dtbo > PyBBIO-gpio2_13-00A0.dtbo cape-CBB-Serial-r01.dtbo > > BB-BONE-LCD3-01-00A2.dtbo PyBBIO-AIN0-00A0.dtbo PyBBIO-gpio0_30-00A0.dtbo > PyBBIO-gpio2_14-00A0.dtbo cape-bone-ibb-00A0.dtbo > > BB-BONE-LCD4-01-00A1.dtbo PyBBIO-AIN1-00A0.dtbo PyBBIO-gpio0_31-00A0.dtbo > PyBBIO-gpio2_15-00A0.dtbo cape-univ-audio-00A0.dtbo > > BB-BONE-LCD7-01-00A3.dtbo PyBBIO-AIN2-00A0.dtbo PyBBIO-gpio0_4-00A0.dtbo > PyBBIO-gpio2_16-00A0.dtbo cape-univ-emmc-00A0.dtbo > > BB-BONE-REPLICAP-00B1.dtbo PyBBIO-AIN3-00A0.dtbo PyBBIO-gpio0_5-00A0.dtbo > PyBBIO-gpio2_17-00A0.dtbo cape-univ-hdmi-00A0.dtbo > > BB-BONE-SERL-03-00A1.dtbo PyBBIO-AIN4-00A0.dtbo PyBBIO-gpio0_7-00A0.dtbo > PyBBIO-gpio2_2-00A0.dtbo cape-universal-00A0.dtbo > > BB-BONE-WTHR-01-00B0.dtbo PyBBIO-AIN5-00A0.dtbo PyBBIO-gpio0_8-00A0.dtbo > PyBBIO-gpio2_22-00A0.dtbo cape-universaln-00A0.dtbo > > BB-CAN1-00A0.dtbo PyBBIO-AIN6-00A0.dtbo PyBBIO-gpio0_9-00A0.dtbo > PyBBIO-gpio2_23-00A0.dtbo carl9170-1.fw > > BB-I2C1-00A0.dtbo PyBBIO-AIN7-00A0.dtbo PyBBIO-gpio1_0-00A0.dtbo > PyBBIO-gpio2_24-00A0.dtbo dev-USB-PWR-CTL-00A1.dtbo > > BB-I2C1-PCA9685-00A0.dtbo PyBBIO-ecap0-00A0.dtbo PyBBIO-gpio1_1-00A0.dtbo > PyBBIO-gpio2_25-00A0.dtbo htc_9271.fw > > BB-I2C2-0A00.dtbo PyBBIO-ecap1-00A0.dtbo PyBBIO-gpio1_12-00A0.dtbo > PyBBIO-gpio2_3-00A0.dtbo mt7601u.bin > > BB-RELAY-4PORT-00A0.dtbo PyBBIO-ehrpwm1-00A0.dtbo PyBBIO-gpio1_13-00A0.dtbo > PyBBIO-gpio2_4-00A0.dtbo rtlwifi > > BB-RTC-01-00A0.dtbo PyBBIO-ehrpwm2-00A0.dtbo PyBBIO-gpio1_14-00A0.dtbo > PyBBIO-gpio2_5-00A0.dtbo ti-connectivity > > BB-SPI0-MCP3008-00A0.dtbo PyBBIO-epwmss0-00A0.dtbo PyBBIO-gpio1_15-00A0.dtbo > PyBBIO-gpio2_6-00A0.dtbo univ-all-00A0.dtbo > > BB-SPI1-01-00A0.dtbo PyBBIO-epwmss1-00A0.dtbo PyBBIO-gpio1_16-00A0.dtbo > PyBBIO-gpio2_7-00A0.dtbo univ-emmc-00A0.dtbo > > BB-SPIDEV1-00A0.dtbo PyBBIO-epwmss2-00A0.dtbo PyBBIO-gpio1_17-00A0.dtbo > PyBBIO-gpio2_8-00A0.dtbo univ-hdmi-00A0.dtbo > > BB-SPIDEV1.dtbo PyBBIO-eqep0-00A0.dtbo PyBBIO-gpio1_18-00A0.dtbo > PyBBIO-gpio2_9-00A0.dtbo univ-nhdmi-00A0.dtbo > > BB-SPIDEV1A1-00A0.dtbo PyBBIO-eqep1-00A0.dtbo PyBBIO-gpio1_19-00A0.dtbo > PyBBIO-gpio3_14-00A0.dtbo > > BB-UART1-00A0.dtbo PyBBIO-eqep2-00A0.dtbo PyBBIO-gpio1_2-00A0.dtbo > PyBBIO-gpio3_15-00A0.dtbo > > BB-UART2-00A0.dtbo PyBBIO-eqep2b-00A0.dtbo PyBBIO-gpio1_28-00A0.dtbo > PyBBIO-gpio3_16-00A0.dtbo > > BB-UART2-RTSCTS-00A0.dtbo PyBBIO-gpio0_10-00A0.dtbo > PyBBIO-gpio1_29-00A0.dtbo PyBBIO-gpio3_17-00A0.dtbo > > root@beaglebone:/lib/firmware# cat $SLOTS > > 0: PF---
Re: [beagleboard] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12
root@beaglebone:~# dmesg | grep bone [5.093226] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,000C,2715BBBK0795' [5.100609] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4 [5.168530] bone_capemgr bone_capemgr: slot #0: No cape found [5.228522] bone_capemgr bone_capemgr: slot #1: No cape found [5.288522] bone_capemgr bone_capemgr: slot #2: No cape found [5.348521] bone_capemgr bone_capemgr: slot #3: No cape found [5.354392] bone_capemgr bone_capemgr: initialized OK. [6.570208] systemd[1]: Set hostname to . [6.839587] systemd[1]: Configuration file /lib/systemd/system/bonescript.socket is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. [6.860332] systemd[1]: Configuration file /lib/systemd/system/bonescript.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. [6.963418] systemd[1]: Configuration file /lib/systemd/system/bonescript-autorun.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. [ 507.748022] bone_capemgr bone_capemgr: part_number 'DM-SPI-Test', version 'N/A' [ 507.756582] bone_capemgr bone_capemgr: slot #4: override [ 507.770021] bone_capemgr bone_capemgr: Using override eeprom data at slot 4 [ 507.777097] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,DM-SPI-Test' [ 507.801823] bone_capemgr bone_capemgr: slot #4: dtbo 'DM-SPI-Test-00A0.dtbo' loaded; overlay id #0 -- 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] IVerilog: just for info
I've been meaning to check out iverilog written by Stephen Williams for quite some time. I finally got around to it and thought why not install to the BBB in anticipation of the X15 that should be available soon. I did a git install from git clone git://github.com/steveicarus/ivtest.git The only dependency missing was gperf; after installing this the compilation proceeded seamlessly (but took awhile). I haven't had a chance to exercise it yet, but the idea of a whole bunch of BBB's each running verilog and talking to each other strikes me as a bit of fun. Even more fun might be if we could get it to run on C66x's in the imminent X15s (and I pretend to hate acronyms?). Anyone else find this potentially interesting? For info: > ver No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.2 (jessie) Release: 8.2 Codename: jessie > uname -a Linux BBB6 4.1.15-bone17 #1 Wed Dec 16 17:39:16 UTC 2015 armv7l GNU/Linux -- 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] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12
ls -lh /dev/spi*
remember you application was looking for:
open("/dev/spidev2.0", O_RDWR) = -1 ENOENT (No such file or directory)
so make sure you application has the correct port name..
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] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12
I backed away from the previous application this one is not the same. It appears to be okay ... root@beaglebone:~# ls -lh /dev/spi* crw-rw 1 root spi 153, 0 Jan 27 02:43 /dev/spidev1.0 crw-rw 1 root spi 153, 1 Jan 27 02:43 /dev/spidev1.1 -- 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] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12
I ought to qualify what I am saying here. To be clear this application does not appear to be looking for a spidev2.0. All said I am still not getting a change in state. I had a similar problem with GPIO's yet that went away with the latests updates, this however seems to be sticking. No change. Am I missing something here ? On Sunday, January 31, 2016 at 7:12:15 PM UTC-7, Dean wrote: > > > I backed away from the previous application this one is not the same. It > appears to be okay ... > > root@beaglebone:~# ls -lh /dev/spi* > crw-rw 1 root spi 153, 0 Jan 27 02:43 /dev/spidev1.0 > crw-rw 1 root spi 153, 1 Jan 27 02:43 /dev/spidev1.1 > > -- 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] Newbie, need help with joystick/analog input on BBB running Debian jessie
I attempted to post this question earlier but I don't believe the post showed up. If it did I apologize for the duplicate post. I have a BBB running Debian jessie 8.2 and the linux kernel is 4.1.12-ti-r29. I've connected a thumb joystick as follows vcc - P9_32 gnd - P9_34 hor - P9_36 ver - P9_38 I did not connect the switch to anything because it isn't needed. I've attempted to read the output of the joystick using information i found online and have failed miserably. The numerous tutorials/instructions say that you have to enable the analog inputs on the beagle bone. The instructions for doing so involve using bone_cape. My BBB doesn't seem to have bone_cape and further research seems to indicate that bone_cape is the old way of doing things and isn't available for the kernel that i'm running. I have yet to find out how I would enable the analog inputs on my setup. If some one knows of a resource that i've missed that will shed some light on the subject I'd greatly appreciate it. Thanks -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Newbie, need help with joystick/analog input on BBB running Debian jessie
On Sun, Jan 31, 2016 at 9:11 PM, Caveman wrote: > I attempted to post this question earlier but I don't believe the post > showed up. If it did I apologize for the duplicate post. > > I have a BBB running Debian jessie 8.2 and the linux kernel is > 4.1.12-ti-r29. > > I've connected a thumb joystick as follows > > vcc - P9_32 > gnd - P9_34 > hor - P9_36 > ver - P9_38 > > I did not connect the switch to anything because it isn't needed. > > > I've attempted to read the output of the joystick using information i found > online and have failed miserably. The numerous tutorials/instructions say > that you have to enable the analog inputs on the beagle bone. The > instructions for doing so involve using bone_cape. My BBB doesn't seem to > have bone_cape and further research seems to indicate that bone_cape is the > old way of doing things and isn't available for the kernel that i'm running. > > I have yet to find out how I would enable the analog inputs on my setup. If > some one knows of a resource that i've missed that will shed some light on > the subject I'd greatly appreciate it. You should talk to caveman: https://groups.google.com/d/msg/beagleboard/qUvzhp2FhWM/fVbK5PrpAQAJ 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] SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12
I did some experiments and see what appears to be serious errors in dmesg. (not experienced in reading these). I boot, and then look at slots: 0: PF -1 1: PF -1 2: PF -1 3: PF -1 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,univ-emmc This is normal. I'm using a slightly modified version of univ-emmc to connect PRUs. This works as expected. I had not tried additional changes to the slots until now. Remove slot 4: # echo -4 > slots cat slots 0: PF -1 1: PF -1 2: PF -1 3: PF -1 All looks good to this point. Now add a different dtbo: # echo cape-universal > slots Now the ssh connection to the board closes. But it's not a hard crash, I can ssh back in. From dmesg: [ 287.654746] Unable to handle kernel NULL pointer dereference at virtual address 0004 That is at least one problem, I think there are more. I'm sure there are plenty of other clues. dmesg is pretty long, so I attached a file. I'm using 4.1.15-ti-rt-r43 on a Beaglebone Black. Greg -- 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. [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.1.15-ti-rt-r43 (root@a4-imx6q-wandboard-2gb) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT RT Thu Jan 21 20:13:58 UTC 2016 [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine model: TI AM335x BeagleBone Black [0.00] cma: Reserved 24 MiB at 0x9e00 [0.00] Memory policy: Data cache writeback [0.00] On node 0 totalpages: 130560 [0.00] free_area_init_node: node 0, pgdat c0c19b00, node_mem_map df96d000 [0.00] Normal zone: 1152 pages used for memmap [0.00] Normal zone: 0 pages reserved [0.00] Normal zone: 130560 pages, LIFO batch:31 [0.00] CPU: All CPU(s) started in SVC mode. [0.00] AM335X ES2.1 (sgx neon ) [0.00] PERCPU: Embedded 13 pages/cpu @df91 s24128 r8192 d20928 u53248 [0.00] pcpu-alloc: s24128 r8192 d20928 u53248 alloc=13*4096 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129408 [0.00] Kernel command line: console=ttyO0,115200n8 root=UUID=bf6d4cec-84ce-40ee-b81b-cd2860ffc4b0 ro rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Memory: 474228K/522240K available (7201K kernel code, 935K rwdata, 3764K rodata, 560K init, 954K bss, 23436K reserved, 24576K cma-reserved, 0K highmem) [0.00] Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xffc0 - 0xfff0 (3072 kB) vmalloc : 0xe080 - 0xff00 ( 488 MB) lowmem : 0xc000 - 0xe000 ( 512 MB) pkmap : 0xbfe0 - 0xc000 ( 2 MB) modules : 0xbf80 - 0xbfe0 ( 6 MB) .text : 0xc0008000 - 0xc0abd7bc (10966 kB) .init : 0xc0abe000 - 0xc0b4a000 ( 560 kB) .data : 0xc0b4a000 - 0xc0c33f2c ( 936 kB) .bss : 0xc0c36000 - 0xc0d249a0 ( 955 kB) [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [0.00] Preemptible hierarchical RCU implementation. [0.00] RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1. [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 [0.00] NR_IRQS:16 nr_irqs:16 16 [0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128 interrupts [0.00] OMAP clockevent source: timer2 at 2400 Hz [0.12] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [0.24] clocksource timer1: mask: 0x max_cycles: 0x, max_idle_ns: 79635851949 ns [0.32] OMAP clocksource: timer1 at 2400 Hz [0.000223] Console: colour dummy device 80x30 [0.000385] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' [0.000388] This ensures that you still see kernel messages. Please [0.000391] update your kernel commandline. [0.088944] Calibrating delay loop... 996.14 BogoMIPS (lpj=4980736) [0.088950] pid_max: default: 32768 minimum: 301 [0.089090] Security Framework initialized [0.089158] AppArmor: A
[beagleboard] PRU signals on expansion headers of X-15?
Hi, is there already an overview available which signals of the PRU(s) are available at the expansion headers of the X-15? Thanks Karl -- 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.
