Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
Thank you!! You are so helpful. I really appreciate it John On Thursday, January 30, 2014 5:48:04 PM UTC-8, RobertCNelson wrote: On Thu, Jan 30, 2014 at 6:29 PM, vermi...@gmail.com javascript: wrote: Robert: Sorry to bug you again, but I've been hunting and hunting and can't figure out where two things concerning apache2 in this testing image: 1) where is the very generic default webpage that I see when go to http://my BBB's URL:8080 located in the file system? It's not in /var/www It's /var/www in 2014-01-29 2) where does the default port for the apache3 server get changed to :8080 from the normal :80? I don't use bone script and would like to have apache2 use port 80 sudo systemctl disable bonescript.socket sudo sed -i -e 's:8080:80:g' /etc/apache2/ports.conf sudo sed -i -e 's:8080:80:g' /etc/apache2/sites-enabled/000-default sudo /etc/init.d/apache2 restart Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
I've been having fun playing with the new images. So far things have
worked well, but something new has popped up on the latest image that
wasn't there before.
I'm using bonescript and I get a failure if I try to use certain pins
(P9_42 and P9_21) that worked in the earlier images.
On the first call to bonescript, via node, the following appears in dmesg
[ 189.216738] bone-capemgr bone_capemgr.9: part_number 'bspm_P9_41_27',
version 'N/A'
[ 189.216916] bone-capemgr bone_capemgr.9: slot #8: generic override
[ 189.216935] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data at slot 8
[ 189.216953] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
Name,00A0,Override Manuf,bspm_P9_41_27'
[ 189.217067] bone-capemgr bone_capemgr.9: slot #8: Requesting part
number/version based 'bspm_P9_41_27-00A0.dtbo
[ 189.217085] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
'bspm_P9_41_27-00A0.dtbo' for board-name 'Override Board Name', version
'00A0'
[ 189.219961] bone-capemgr bone_capemgr.9: slot #8: dtbo
'bspm_P9_41_27-00A0.dtbo' loaded; converting to live tree
[ 189.220349] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
[ 189.225997] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
bonescript appears to work fine unless I do something like:
b.pinMode('P9_42', b.INPUT);
Then it fails.
Any idea what's changed, or how to fix it?
--Mark
--
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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Fri, Jan 31, 2014 at 1:08 PM, Mark A. Yoder mark.a.yo...@gmail.com wrote:
I've been having fun playing with the new images. So far things have worked
well, but something new has popped up on the latest image that wasn't there
before.
I'm using bonescript and I get a failure if I try to use certain pins (P9_42
and P9_21) that worked in the earlier images.
On the first call to bonescript, via node, the following appears in dmesg
[ 189.216738] bone-capemgr bone_capemgr.9: part_number 'bspm_P9_41_27',
version 'N/A'
[ 189.216916] bone-capemgr bone_capemgr.9: slot #8: generic override
[ 189.216935] bone-capemgr bone_capemgr.9: bone: Using override eeprom data
at slot 8
[ 189.216953] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
Name,00A0,Override Manuf,bspm_P9_41_27'
[ 189.217067] bone-capemgr bone_capemgr.9: slot #8: Requesting part
number/version based 'bspm_P9_41_27-00A0.dtbo
[ 189.217085] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
'bspm_P9_41_27-00A0.dtbo' for board-name 'Override Board Name', version
'00A0'
[ 189.219961] bone-capemgr bone_capemgr.9: slot #8: dtbo
'bspm_P9_41_27-00A0.dtbo' loaded; converting to live tree
[ 189.220349] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
[ 189.225997] bone-capemgr bone_capemgr.9: slot #8: Applied #2 overlays.
bonescript appears to work fine unless I do something like:
b.pinMode('P9_42', b.INPUT);
Then it fails.
Any idea what's changed, or how to fix it?
It was requested by bb.org to enable a new default pinmux:
http://elinux.org/CircuitCo:Basic_Proto_Cape
So, P9.42 P9.21 are now used by default.
For compatibity sake, i just set this up in a new overlay.. So it's
easy to disable..
sudo sed -i -e 's:CAPE=cape-bone-proto:#CAPE=cape-bone-proto:g'
/etc/default/capemgr
sudo reboot
Regards,
--
Robert Nelson
http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
Robert, thanks for the quick response, that did it.
Two more questions:
1. Do you have an idea when cloud9 will be back?
2. Do you have a guess as to when the image will be stable? I'm
scheduled to give a BeagleWorkshop to some faculty on 7-March and am
wondering if I should plan on using the new Debian image.
--Mark
On Friday, January 31, 2014 2:22:33 PM UTC-5, RobertCNelson wrote:
On Fri, Jan 31, 2014 at 1:08 PM, Mark A. Yoder
mark.a...@gmail.comjavascript:
wrote:
I've been having fun playing with the new images. So far things have
worked
well, but something new has popped up on the latest image that wasn't
there
before.
I'm using bonescript and I get a failure if I try to use certain pins
(P9_42
and P9_21) that worked in the earlier images.
On the first call to bonescript, via node, the following appears in
dmesg
[ 189.216738] bone-capemgr bone_capemgr.9: part_number 'bspm_P9_41_27',
version 'N/A'
[ 189.216916] bone-capemgr bone_capemgr.9: slot #8: generic override
[ 189.216935] bone-capemgr bone_capemgr.9: bone: Using override eeprom
data
at slot 8
[ 189.216953] bone-capemgr bone_capemgr.9: slot #8: 'Override Board
Name,00A0,Override Manuf,bspm_P9_41_27'
[ 189.217067] bone-capemgr bone_capemgr.9: slot #8: Requesting part
number/version based 'bspm_P9_41_27-00A0.dtbo
[ 189.217085] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware
'bspm_P9_41_27-00A0.dtbo' for board-name 'Override Board Name', version
'00A0'
[ 189.219961] bone-capemgr bone_capemgr.9: slot #8: dtbo
'bspm_P9_41_27-00A0.dtbo' loaded; converting to live tree
[ 189.220349] bone-capemgr bone_capemgr.9: slot #8: #2 overlays
[ 189.225997] bone-capemgr bone_capemgr.9: slot #8: Applied #2
overlays.
bonescript appears to work fine unless I do something like:
b.pinMode('P9_42', b.INPUT);
Then it fails.
Any idea what's changed, or how to fix it?
It was requested by bb.org to enable a new default pinmux:
http://elinux.org/CircuitCo:Basic_Proto_Cape
So, P9.42 P9.21 are now used by default.
For compatibity sake, i just set this up in a new overlay.. So it's
easy to disable..
sudo sed -i -e 's:CAPE=cape-bone-proto:#CAPE=cape-bone-proto:g'
/etc/default/capemgr
sudo reboot
Regards,
--
Robert Nelson
http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Fri, Jan 31, 2014 at 1:32 PM, Mark A. Yoder mark.a.yo...@gmail.com wrote: Robert, thanks for the quick response, that did it. Two more questions: Do you have an idea when cloud9 will be back? I'm hoping pretty soon.. Just waiting for the version compatible with the node v0.10.x to be pushed to github. Do you have a guess as to when the image will be stable? After cloud9 gets added.. I believe that was the last major blocker for 1 to 1 compatibility with the old Angstrom image. Other then doc's.. There was one kernel fix (usb-gadget stuff filling /var/log/) just update via cd /opt/scripts git pull ./tools/update_kernel.sh I'm scheduled to give a BeagleWorkshop to some faculty on 7-March and am wondering if I should plan on using the new Debian image. Oh definitely before that timeframe.. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
Another question (perhaps request) Since systems is now functional as well as the older style init.d scripts, and systemctl, where is journalctl? It is so useful and convenient... Thanks On Friday, January 31, 2014 11:51:00 AM UTC-8, RobertCNelson wrote: On Fri, Jan 31, 2014 at 1:32 PM, Mark A. Yoder mark.a...@gmail.comjavascript: wrote: Robert, thanks for the quick response, that did it. Two more questions: Do you have an idea when cloud9 will be back? I'm hoping pretty soon.. Just waiting for the version compatible with the node v0.10.x to be pushed to github. Do you have a guess as to when the image will be stable? After cloud9 gets added.. I believe that was the last major blocker for 1 to 1 compatibility with the old Angstrom image. Other then doc's.. There was one kernel fix (usb-gadget stuff filling /var/log/) just update via cd /opt/scripts git pull ./tools/update_kernel.sh I'm scheduled to give a BeagleWorkshop to some faculty on 7-March and am wondering if I should plan on using the new Debian image. Oh definitely before that timeframe.. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Fri, Jan 31, 2014 at 4:34 PM, vermins...@gmail.com wrote: Another question (perhaps request) Since systems is now functional as well as the older style init.d scripts, and systemctl, where is journalctl? It is so useful and convenient... systemd-journalctl Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Wed, Jan 29, 2014 at 10:50 PM, vermins...@gmail.com wrote: Robert: Thanks for putting this up. I have the 2GB SD Image working and, thanks to your easy script, was able to expand it to use my entire 8Gb SD card. I'm sorry, but I'm still fairly new to this, so forgive me if I'm perplexed by simple things:) On my older Debian install, based on your eewiki from a few months ago, I was able to add both Dallas 1wire support and also enable the ADC's by adding the following line to uEnv.txt optargs=capemgr.enable_partno=BB-ADC,BB-W1 I already had compiled the BB-W1-00A0.dtbo based on HipsterCircuits blog example, and copied it to /lib/firmware This worked fine on the older Debian SD version But on today's new one, only the BB-ADC gets loaded into slot. I also tried only loading BB-W1, and only BB-ADC, and again, only BB-ADC works. The thing that confuses me is that if instead, after loading BB-ADC via uEnv.txt, I am in /lib/firmware and issue: echo BB-W1:00A0 /sys/devices/bone_capemgr.9/slots I then see that the BB-W1 overlay has been loaded and the one-wire temp sensor works as expected. Any clues? Thanks I'm not sure why, capemgr.enable_partno hasn't been as reliable.. Just edit /etc/default/capemgr and replace the one define to BB-W1 * and reboot.. it should load your BB-W1 on the next boot.. * Only one cape is support at this point, it was a quick hack.. See: https://github.com/beagleboard/image-builder/blob/master/target/init_scripts/capemgr-debian.sh https://github.com/beagleboard/image-builder/blob/master/target/init_scripts/capemgr Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Thu, Jan 30, 2014 at 4:48 AM, iustinian.in...@gmail.com wrote: Which init script is enabled by default ? The ones i enable.. Do we have a choice of what init system to use ? systemd: unless you disable it.. Is this image also coming with a X server and desktop manager or it can be used as a minimal console only ? It includes lxde, but you could remove it easily.. But I think your missing the point of this Image, so go read: http://beagleboard.org/blog/2014-01-04-happy-new-year/ The purpose of this image is to TEST what the next default image will be on the boards shipped. If your doing something custom, take a look here: http://elinux.org/BeagleBoardDebian#Demo_Image For a more minimal image.. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
So presumably, this isn't detecting capes via EEPROM; it's effectively the equivalent of doing: echo cape-bone-proto /sys/devices/bone_capemgr.9/slots In a startup script? Yeap. Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Thursday, January 30, 2014 1:29:30 PM UTC-5, RobertCNelson wrote: So presumably, this isn't detecting capes via EEPROM; it's effectively the equivalent of doing: echo cape-bone-proto /sys/devices/bone_capemgr.9/slots In a startup script? Yeap. Ok, so I'm still interested in getting my overlay loaded at boot time via EEPROM. Could you elaborate on your ideas about using initrd.img to store the .dtbo files? 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
Robert: Sorry to bug you again, but I've been hunting and hunting and can't figure out where two things concerning apache2 in this testing image: 1) where is the very generic default webpage that I see when go to http://my BBB's URL:8080 located in the file system? It's not in /var/www 2) where does the default port for the apache3 server get changed to :8080 from the normal :80? I don't use bone script and would like to have apache2 use port 80 Thanks John On Thursday, January 30, 2014 2:17:52 PM UTC-8, smith.wi...@gmail.com wrote: On Thursday, January 30, 2014 1:29:30 PM UTC-5, RobertCNelson wrote: So presumably, this isn't detecting capes via EEPROM; it's effectively the equivalent of doing: echo cape-bone-proto /sys/devices/bone_capemgr.9/slots In a startup script? Yeap. Ok, so I'm still interested in getting my overlay loaded at boot time via EEPROM. Could you elaborate on your ideas about using initrd.img to store the .dtbo files? 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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Thu, Jan 30, 2014 at 6:29 PM, vermins...@gmail.com wrote: Robert: Sorry to bug you again, but I've been hunting and hunting and can't figure out where two things concerning apache2 in this testing image: 1) where is the very generic default webpage that I see when go to http://my BBB's URL:8080 located in the file system? It's not in /var/www It's /var/www in 2014-01-29 2) where does the default port for the apache3 server get changed to :8080 from the normal :80? I don't use bone script and would like to have apache2 use port 80 sudo systemctl disable bonescript.socket sudo sed -i -e 's:8080:80:g' /etc/apache2/ports.conf sudo sed -i -e 's:8080:80:g' /etc/apache2/sites-enabled/000-default sudo /etc/init.d/apache2 restart Regards, -- Robert Nelson http://www.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/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-29) (resend with correct topic..)
On Wed, Jan 29, 2014 at 8:03 PM, smith.winston@gmail.com wrote: On Wednesday, January 29, 2014 4:25:22 PM UTC-5, RobertCNelson wrote: Lets keep this going, round 4... This is great, thanks again for your hard work. I'll take a look tonight. You had previously mentioned adding .dtbo scripts to the /boot partition (or was it initrd.img) to allow overlays to be detected via EEPROM and loaded without blocking waiting for the emmc cape. Were you able to get that to work? That thread was mostly me talking about ways to make it work.. I did add a very trivial load cape at boot time (without modifing uEnv.txt) script.. https://github.com/beagleboard/image-builder/blob/master/target/init_scripts/capemgr-debian.sh https://github.com/beagleboard/image-builder/blob/master/target/init_scripts/capemgr So i just: echo CAPE=cape-bone-proto /etc/default/capemgr and it's autoloaded on the next reboot.. Regards, -- Robert Nelson http://www.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/groups/opt_out.
