Re: [beagleboard] Where is asoundlib.h?
Thanks, that does look cleaner. I hope this works for mbelg... Personally I am happy that I moved my BBBk to Debian, but locally I have updated my readme with the information, in case I need to do this again (will update on my github soon). Also looks like good general purpose advice so again thanks. On Wednesday, April 16, 2014 8:41:24 PM UTC-7, john3909 wrote: > > > From: KurtE > > Reply-To: > > Date: Wednesday, April 16, 2014 at 5:45 PM > To: > > Subject: Re: [beagleboard] Where is asoundlib.h? > > I could be wrong, but when I was trying to do this awhile ago on Angstrom, > I did not find it. I ended up downloading and building the stuff on the > BBBk. Now with Debian, I can now do like I did on the Raspberry Pi and and > do the apt-get install libasound2-dev > > More details on what I do is up on my Readme file of my github Raspberry > Pi project(Bad name, but was first linux box): > https://github.com/KurtE/Raspberry_Pi > > From that readme: > > I did not find any valid packages to install the ALSA, so I did it > manually: > > wget ftp://ftp.alsa-project.org/pub/lib/a...1.0.25.tar.bz2 > tar jxf alsa-lib-1.0.25.tar.bz2 > cd alsa-lib-1.0.25 > ./configure > make install > > Try this instead, > > apt-get source libasound2 > cd alsa-lib-1.0.25 > // if you want debug symbols > export DEB_BUILD_OPTION=nostrip noopt debug > dpkg-buildpackage -rfakeroot -uc -us -j8 -aarmhf > > // The dpkg-buildpackage uses the settings a patches in the debian folder > and builds the library as intended > // This commands creates Debian packages in the parent folder. > > cd .. > sudo dpkg -i libasound2* deb > > Regards, > John > > > This did not set the USB device to be default sound device, I used the > command: aplay -L to list the nodes. From which I created the configuration > file: /etc/asound.conf pcm.!default sysdefault:Device > > Again there may be easier ways, but that is what I did. Note: I am using > a USB sound adapter... > > -- > 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] Where is asoundlib.h?
I could be wrong, but when I was trying to do this awhile ago on Angstrom, I did not find it. I ended up downloading and building the stuff on the BBBk. Now with Debian, I can now do like I did on the Raspberry Pi and and do the apt-get install libasound2-dev More details on what I do is up on my Readme file of my github Raspberry Pi project(Bad name, but was first linux box): https://github.com/KurtE/Raspberry_Pi >From that readme: I did not find any valid packages to install the ALSA, so I did it manually: wget ftp://ftp.alsa-project.org/pub/lib/a...1.0.25.tar.bz2 tar jxf alsa-lib-1.0.25.tar.bz2 cd alsa-lib-1.0.25 ./configure make install This did not set the USB device to be default sound device, I used the command: aplay -L to list the nodes. From which I created the configuration file: /etc/asound.conf pcm.!default sysdefault:Device Again there may be easier ways, but that is what I did. Note: I am using a USB sound adapter... -- 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: Here is the BeagleBone Debian (beta) image you want to test
Question: For the fun of it, I updated my system to the latest build (3/31) Also updated the kernel using the script you mentioned. Then thought I would test out building and running my Hexapod code. As part of my code base I have some Sound output including Tones (beeps) using Alsa as well as Espeak... I git cloned the stuff down from my github project: https://github.com/KurtE/Raspberry_Pi (Sorry about the project name) and did the stuff in my Readme file that included sudo apt-get of the stuff for ALSA and Espeak and got everything to build. I use an external USB sound adapter. With previous builds I was able to get the sound to work by creating a sound configuration file: /etc/asound.conf pcm. with the content of: !default sysdefault:Device So far when I try it with this build I am not having much luck: Still investigating. Suggestions? Seeing messages like: kurt@beaglebone:~$ cat /etc/asound.conf !default sysdefault:Device kurt@beaglebone:~$ espeak "Hi There" ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM sysdefault ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM sysdefault ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM front ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM surround40 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory ALSA lib conf.c:4720:(snd_config_expand) Evaluate error: No such file or directory ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM surround41 ALSA lib confmisc.c:768:(parse_card) cannot find card '0' ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib conf.c:4241:(_snd_config_evaluate) function snd_func_conc
Re: [beagleboard] Re: Playing sound using with my BBB using a piezo buzzer (beeper)
For what it is worth, I also wanted sounds and the like to my BBBk, I like to have some form of Audio notification, when I do something lets say with a remote control, to let me know that it was received. More details on how (readme.md) I set it up, plus code are up on my Raspberry Pi project (https://github.com/KurtE/Raspberry_Pi) Since there is no Sound output plug on the BBBk, I used a real cheap USB sound adapter, plus a cheap powered speaker. I then installed PCM (on RPI and now Debian can just do sudo apt-get ... earlier on BBBk had to download and build sources. Once you have PCM installed, need to configure to output to the device instead of the default of HDMI. I then have a function(https://github.com/KurtE/Raspberry_Pi/blob/master/library/msound.cpp) , that I can pass in how many notes to play, followed by the notes, with a call like: MSound(3, 60, 2000, 80, 2250, 100, 2500); (play 3 notes, first one 60ms with 200hz...) The code creates a sound buffer with the sine wave for that hz and repeats it so many times... Probably not the greatest approach, but it has worked for me. Kurt -- 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: espeak in beaglebone black
Earlier when I was using Angstrom, I ended up having to download and build Espeak, but when I converted to the Debian versions, I could install it as you mentioned. However the PCM I believe is always defaulting to output to the HDMI sound. To get it to work with a USB sound card I plugged in, I found I needed to edit a sound configuration file: Here is what I have: kurt@BeagleBone:~$ cat /etc/asound.conf pcm.!default sysdefault:Device On Sunday, January 26, 2014 6:35:46 AM UTC-8, ss sefat wrote: > > i want to use espeak on beaglebone black . i simply did "opkg install > espeak" to install espeak . bt when i write command in command prompt to > speak something it produced no sound . i used 'espeak "hello espeak" '. how > can i make espeak to work on beaglebone black.plz help me. 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/groups/opt_out.
[beagleboard] Re: Wifi Adapter Recommendations
Monday, January 6, 2014 12:54:18 PM UTC-8, KurtE wrote: > , I ordered one of the tl-wn722n devices which hopefully will arrive > tomorrow. Sometimes it is easier to punt. Quick update, I have been using this now for 2 days, and no drops and no random messages showing up in debug terminal :) -- 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: Which build would you recommend?
On Wednesday, January 8, 2014 10:18:22 AM UTC-8, RobertCNelson wrote: > > > But if I do, should I stick with the 3.8 kernel? Or 3.12 or 3.13? > > If you want 'full' cape support stick with 3.8.. If you are just using > usb/ethernet with simple capes* (usart/i2c/spi) use 3.13 (i'm working > on adding most capes to 3.13 at the moment..) ignore 3.12.. ;) > Sounds good, I only have one of the breadboard capes which I have enabled two USARTS on. so 3.13 sounds like where I should start playing. > > My assumption is the build scripts assume I am running linux. Can dual > boot > > to this on my main dev machine to Linux Mint, or could use my NUC which > I > > think right now I have running Ubuntu 13.04. > > The scripts assume linux, mostly tested on debian jessie, but works in > ubuntu.. > > Note the "image-builder" works best native on arm hardware.. (qemu is > too bit rotten for 100% reliably between distro versions) > So to build for my one BBBk, I would be better off doing the build on another ARM based machine running Debian. Probably my best option would be to use my Odroid U2? It has a 16gb emmc on it and i can plug in a microsd... I am currently running Ubuntu on it, but can install Debian. > > > > A few more things to investigate: > > 1) If I build an image and write it to an SD card, can I try it out > (boot > > off of it) without it overwriting the EMMC? > > There will be a traditional "flasher" which will overwrite the eMMC > and a secondary "4gb img" which you can dump to your microSD and it'll > run on that. > So if I am reading this correct, Each time will overwrite the eMMC... I was hoping to be able to maybe have the ability to choose either boot emmc or boot SD. I am probably missing something. Thanks again -- 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: Which build would you recommend?
Yes, it is working good for me. :) But after reading the happy new year message, I have also been wondering that if the standard release will be Debian, should I try building my own images from the links that were listed there for both the actual image and kernel? But if I do, should I stick with the 3.8 kernel? Or 3.12 or 3.13? My assumption is the build scripts assume I am running linux. Can dual boot to this on my main dev machine to Linux Mint, or could use my NUC which I think right now I have running Ubuntu 13.04. A few more things to investigate: 1) If I build an image and write it to an SD card, can I try it out (boot off of it) without it overwriting the EMMC? 2) I am trying to learn ROS and convert my code of at least one of my robots to use it. I tried building it on my BBBk, but don't think 2gb is enough storage to build even the minimal install from sources. Some options to look at: a) Is there some place to apt-get install from? I saw a posting for downloading on Angstrom and maybe Ubuntu... More to look at. b) Run off of SD card with more storage? ... 3) Boot off of EMMC, but have more storage external. SD or USB thumb??? Sorry about the rambling, just thoughts about things for me to try out -- 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.
[beagleboard] Re: Wifi Adapter Recommendations
Again thanks, FYI - Looking through me cheat sheet (readme.md) up on my github project, I found where I got the information back in june: Not sure if it will help anyone, but this was how I did it then. http://www.codealpha.net/864/how-to-set-up-a-rtl8192cu-on-the-beaglebone-black-bbb/ Note: my notes mention that it was missing a step of: cd /usr/src/kernel make scripts But it looks like the page was updated to include this. Again 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.
[beagleboard] Re: Wifi Adapter Recommendations
Thanks guys, Yep the steps, mentioned look familiar. Although back then, I believe I edited the Makefile differently. That is, I turned off windows turned on the Arm... But it looks like I still have the earlier built 8192cu.ko file, so tomorrow will try running with it and see how well it works. If not will try rebuilding from the new instructions. William, yep I totally agree, which is why I purchased my first edimax when I purchased my first RPI. I did not see any particular one when BBBk was released so though another ones of these would work. WHen I ordered Odroid U2 I ordered one of their adapter and likewise when I purchased an Intel NUC... Still having fun playing and learning. -- 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.
[beagleboard] Re: Wifi Adapter Recommendations
It has been quite a few months since I looked at this as well. I remember back then (June?), that I did find some sources to build the driver for the 8192cu, which back then worked quite well. I think I still have the sources sitting on my PC, but it has been awhile since I figured out how to build and install it. I installed his Debian build, which I really like, but the edimax adapter has dropped a reasonable number of times now. So may try to see if I kept my notes for installing the patched driver, but in the mean time, I ordered one of the *tl-wn722n devices which hopefully will arrive tomorrow. *Sometimes it is easier to punt. On Monday, January 6, 2014 7:28:40 AM UTC-8, David Marquart wrote: > > building a driver from > > https://github.com/pvaret/rtl8192cu-fixes.git > for the little one from adafruit seems to be working quite well. ran since > thursday on 3.12.5 kernel without any issues that i could find so far. > > > On Thursday, December 26, 2013 3:37:50 PM UTC-6, David Marquart wrote: >> >> Does anyone have a recommendation for a wifi adapter that works with >> Robert Nelson's Ubuntu images? I have rtl8188cus and mt7601 and I can not >> get either to work. At this point I would rather just order one that works >> rather than waste more time trying to fight with either of these two. I >> have building the kernel working and have tried several times to build a >> new driver for both of these adapters but the mt7601 will not show up with >> iwconfig and the rtl8188cus will show up see my access point but will not >> connect to it. I am editing /etc/network/interfaces to try and get >> connected to our WEP "protected" network. I have no control over the type >> of encryption used. I was able to get everything working on Angstrom with >> connman so I know it is possible. >> >> Sorry if this became a little bit of a rant but I have spent a lot of >> time trying everything I could google up and now I just want to throw money >> at the problem. >> > -- 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: Which build would you recommend?
I will answer my own question, on the off chance someone else is wanting to
do the same. Actually I did it two ways:Another thing.
One example /etc/udev/rules.d/99-tty-serial.rules Looks like:
SUBSYSTEM=="tty", KERNEL=="ttyO1", SYMLINK+="ttyXBEE"
SUBSYSTEM=="tty", KERNEL=="ttyO2", SYMLINK+="ttySSC-32"
I also was able to do it like:
SUBSYSTEM=="tty", ATTRS{port}=="0x0", ATTRS{line}=="1", SYMLINK+="ttyXBEE"
SUBSYSTEM=="tty", ATTRS{port}=="0x0", ATTRS{line}=="2", SYMLINK+="ttyRCLAW"
Earlier I was using a Roboclaw motor controller on this.
Kurt
--
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: Which build would you recommend?
Just thought I would mention, I am making more progress :)
Using the debian release is nice as like when compiling on the RPI, I could
install PCM and espeak, by simply doing apt-get install and the packages
were installed. On Angstrom I had to find sources build and install. No
big deal but it is nice.
Next up is to start connecting it up to hardware. XBee will be easy,
connect to TTL usart like before, as it is 3.3v. But not sure which way I
will go to talk to SSC-32. Could USB to serial adapter or could connect to
another USART through level shifter. The SSC-32 is a 5v ATmega based
board.
Another thing I want to investigate more is in my code, I like to reference
devices by a name such as: /dev/ttyXBee instead of by some actual hardware
name. When it is /dev/ttyUSBn it also had the complication that if you
rearrange things and/or add devices your device may change names. ttyUSB0
today may be ttyUSB1 tomorrow... So I used UDEV rules to do the mapping.
Something like:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
ATTRS{serial}=="A800fclo", SYMLINK+="ttyXBEE"
But at the time was not sure of the best way to simply map ttyO1 to
ttyXBee. When I tried it the last time was not sure, so I simply added a
line to my .profile file that did something like: ln -s /dev/ttyO1
/dev/ttyXBee
But my gut tells me there is a cleaner way. So will probably play a little
with this, before I simply fall back to doing what I did before.
Again having fun
Kurt
P.S - the Wifi has stopped twice now. Could be related that I am powering
board through USB (1 amp wall wart) instead of DC power input. Will
change soon
--
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: Which build would you recommend?
> darn, i know it works for some devices.. I usually just run Atheros > chipsets... > > I am trying to remember which wireless I was using back earlier... I remember it took me a long time to get one working then. I believe I had to build the driver for it. Right now I have one of those cheep Edimax plugs, which appeared to work right out of the box. Could try different ones if this becomes an issue. > There's a hint here, "/boot/uboot/uEnv.txt" > > root@beaglebone:~# cat /boot/uboot/uEnv.txt | grep cape > #optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G > > > > Thanks for hint, yep edited the file added the capemgr.enable_partno= the two usarts and rebooted and the devices showed up in the /dev directory so making progress. Now to try to build my Phoenix hexapod code base again. I see I need to either disable some of my code in this or need to install (and or build) a few more things like alsa and potentially espeak. luckily I still have notes on how I did this before on both RPI and BBBk. Before on BBBk ahd to build and install ALSA, but maybe this time will get lucky and can simply install. I also should update my readme.md file on my github project with notes from setting this up on Debian. Again thanks a lot! -- 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: Which build would you recommend?
> sudo iwconfig wlan0 power off > > Thanks, it appears this device does not support that: kurt@arm:~/Raspberry_Pi/Phoenix$ sudo iwconfig wlan0 power off Error for wireless request "Set Power Management" (8B2C) : SET failed on device wlan0 ; Operation not supported. On other note, looking back up where I used to get information about setting up ttyO1... http://blog.pignology.net/2013/05/getting-uart2-devttyo1-working-on.html It looks like since I last did this, there was another way (Angstrom), by adding the info to: "just add you BB-UART2 to /media/BEAGLEBONE/uEnv.txt, with the key capemgr.enable_partno." with This Debian build my /media directory is empty. Should creating this directory and file work here as well? The only place on my machine I found uEnv.txt is in the /boot/uboot directory. Or should I try the way I was doing before, something like: *echo uart2pinmux > $SLOTS*where $slots was defined earlier on as *: * export PINS=/sys/kernel/debug/pinctrl/44e10800.pinmux/pins export SLOTS=/sys/devices/bone_capemgr.9/slots (the .9 sometimes changes, earlier I had .8) Probably the easiest thing for me to do is to try it out and see what happens. -- 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: Which build would you recommend?
Thanks, forgot to look in /sbin Making some progress, found my 3.3v FTDI cable so have the debug setup. Am now downloading source and the like to the board and installing build-esentials. Next up see if using same steps as before (need to find them) to setup for the ttyOn devices. Just ran into having the WLAN dropping me and then reconnecting a few minutes later. I remember these issues from from before, maybe something like it powers itself down... Need to investigate. After that, at the end of dmesg I see: [ 2039.185393] wlan0: deauthenticated from 30:46:9a:02:49:a8 (Reason: 2) [ 2039.231769] cfg80211: Calling CRDA for country: US [ 2040.111858] hub 1-1:1.0: transfer --> -71 [ 2040.125075] wlan0: authenticate with 30:46:9a:02:49:a8 [ 2040.150919] wlan0: send auth to 30:46:9a:02:49:a8 (try 1/3) [ 2040.178916] wlan0: authenticated [ 2040.186600] wlan0: associate with 30:46:9a:02:49:a8 (try 1/3) [ 2040.198275] wlan0: RX AssocResp from 30:46:9a:02:49:a8 (capab=0x431 status=0 aid=6) [ 2040.208995] wlan0: associated In case anyone looks, from earlier on in dmesg: [7.302088] RTL8192cu 1-1.2:1.0: usb_probe_interface [7.302117] rtl8192cu 1-1.2:1.0: usb_probe_interface - got id [7.330628] rtl8192cu: Chip version 0x10 [7.664443] rtl8192cu: MAC address: 80:1f:02:9a:9b:e6 [7.669813] rtl8192cu: Board Type 0 [7.696119] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1 [7.724885] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw.bin [7.757493] usbcore: registered new interface driver rtl8192cu Kurt -- 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.
[beagleboard] Re: Which build would you recommend?
Thanks, I know asking for which OS to use is a loaded question, that usually has the simple answer, of which ever one works for you... So after reading through the Angstrom/Rants thread, plus some others, decided to also try out Debian Wheezy, which I installed off of: http://elinux.org/BeagleBoardDebian. I installed the EMMC version, which is great. Now starting to fumble my way through to get the system configured up. I now have the wifi working, which is great. Yep driver just worked. Only thing I needed to do was to figure out how to configure it for my WPA... Now working. Took me a few minutes to figure out what IP address it has, as did not see anything in the dmesg output. Also dont have ifconfig... But found it looking at my DHCP servers log output. Next up: find where I put my 3.3v FTDI cable and look at seeing what I need to do again (if anything), to enable the usarts through the device maps. Was using a couple before for XBee and the like. Again thanks, Kurt -- 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.
[beagleboard] Which build would you recommend?
It has been awhile since I have done much with my BBBk. Over the last several months I have been playing around with some other boards such as the Odroid U2 (have a U3 on order) as well as an Intel NUC. But am thinking about moving the BBBk that I was starting to use on a Rover to a 4DOF hexapod. Should be straight forward as I have 2 RPIs running my Phoenix port. One is on a 3DOF Lynxmotion T-Hex and another is on a Trossen PhantomX Hexapod. But I have not tested my 4dof support in the port, so am thinking of trying my Lynxmotion 4DOF round hex out on the BBBk. My question is, which distribution/build would you recommend at this point. I believe the emmc has an Angstrom build dated back to 2013 06 20. I know around this time I was having issues that if you do something like an apt-get update/upgrade at times it would corrupt the image. I am not using any shields (other than the prototype shield). I have been using a few of the usarts for XBee and before to talk to motor controller. But for Hex will probably want to talk to SSC-32 (Atmega chip) so I will either use USB to serial converter or probably would need to use a TTL level shifter. So again would like to know if you would recommend sticking with Angstrom on the EMMC or go to a different distribution? Do any others fit on the EMMC? Thanks in advance Kurt P.S - Do wish the BBBk came with a larger 4 or 8 gb emmc. (I have an 16 on ODroid, 128 on NUC) Would have easily paid more for it -- 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.
