[beagleboard] Re: Online training update
Hello, I saw the resolution and I would like in on learning objectives. The books seem to have ceased in the BeagleBoard.org world, i.e. for obvious reasons. Once something is put on paper, someone else has already changed something else to the point where what is on paper is "old" news. Anyway, I want in too! Seth On Thursday, March 19, 2020 at 2:40:46 PM UTC-5, Jason Kridner wrote: > > https://beagleboard.org/blog/2020-03-18-online-training-update > > As mentioned in my New Year’s resolution > <https://beagleboard.org/blog/2020-01-05-jasons-new-years-resolutions>, > I’m going to launch some online training for embedded Linux development. > > > Yes, this training will happen. Interest continues to build. At this > point, I’m delaying until the first of our triannual image releases > <https://beagleboard.org/blog/2020-03-09-new-beagleboard-debian-image-release-cycle> > comes > out next month to align with the latest software release. I’m also fixing > an issue with the TechLab boards being improperly classified for export, > preventing shipments to some countries. I’m also working on getting a few > more of these into distribution as I expect we’ll run out with everyone > looking to do this training. > > > To make sure you don’t miss out, subscribe to the blog at > beagleboard.org/blog. > > > Here’s a bit more on the format: > • It will be done as YouTube “premieres” > <https://www.youtube.com/user/jadonk> of 30 minute videos with live chat > • There will be an extra 30 minutes of live chat on beagleboard.org/chat > • On-going discussion on beagleboard.org/discuss under “Training” > • First session built on PocketBeagle TechLab > <https://beagleboard.org/Capes/TechLab> materials > from e-ALE workshops > [image: ➡] Kits will be available via a Digi-Key shopping cart > <https://www.digikey.com/short/p01cj1> > PocketBeagle® and TechLab Workshop Setup > > Feel free to get kits now, but I’ll try to include time to acquire kits > after the first video. The first video will be more of an introduction to > the concept and BeagleBoard.org. I’ll announce here on this blog when the > first video is scheduled to premiere and will give at least a week’s notice. > > > As of now, some topics to be covered include: > [image: ➡] Use Linux command-line and explore file system > [image: ➡] Program basic Linux interfaces in JavaScript/Node-RED and > Python > [image: ➡] Program PRUs using C > [image: ➡] Start writing kernel drivers in C > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/522ed974-8b9b-4977-b588-9c24a7247713o%40googlegroups.com.
Re: [beagleboard] Re: BBAI and Updating to Stop the Heat Transfer at https://beagleboard.org/upgrade
Hello, Just an update, if you run the temp. sensors onboard the AI and run the fan, on my end, you will receive a 38c or below temp. for the board chips and surrounding area. Seth P.S. Nice! Fans! On Thursday, January 2, 2020 at 1:18:29 AM UTC-6, Mala Dies wrote: > > Hello, > > Thank you for this update. I did update the board already as the link > suggested. My fan was a 24v fan. I need to get another fan. > > Seth > > P.S. I might get the digikey.com fan you have listed. Anyway, if anyone > has any other ideas, shoot! > > On Sunday, December 29, 2019 at 5:30:02 PM UTC-6, jonnymo wrote: >> >> Jason recently posted an update regarding the Fan Cape he is working on. >> In the mean time, he recommended the Coolerguys USB fan that is listed in >> the BBAI FAQ: >> >> https://github.com/beagleboard/beaglebone-ai/wiki/Frequently-Asked-Questions#fans >> >> https://www.coolerguys.com/collections/usb-fans/products/25mm-25x25x10-usb-fan >> >> Previously, the X15FANKIT was suggested but it requires wiring to 5v and >> grnd on the BBAI. I am using this and it seems to work fine for my BBAI. >> This does fit perfectly on the BBAI heat-sink and the provided screws work >> just fine. >> >> https://github.com/beagleboard/beaglebone-ai/wiki/System-Reference-Manual#3-1-2-fans >> >> https://www.digikey.com/product-detail/en/digi-key-electronics/X15FANKIT/X15FANKIT-ND/5822502 >> >> >> Cheers, >> >> Jon >> >> On Sun, Dec 29, 2019 at 10:03 PM Mala Dies wrote: >> >>> Hello, >>> >>> Thank you for the idea. USB powered fans. I guess they make everything >>> these days. >>> >>> Seth >>> >>> P.S. I was just going to power it from the sys_5v pin and GND on the >>> BBAI. I guess there are many more ways to go about making things work than >>> once thought. >>> >>> On Sunday, December 29, 2019 at 8:56:07 AM UTC-6, Stephen Johnson wrote: >>>> >>>> I bought a USB powered fan which gives a very low airflow, but has kept >>>> everything cool to the touch. >>>> I just have the BBAI on my engineering workbench anyhow, so I just >>>> wanted something simple and quiet. >>>> >>>> >>>> [image: IMG_1873.jpeg] >>>> >>>> >>>> >>>> On Saturday, December 28, 2019 at 7:17:02 PM UTC-6, Mala Dies wrote: >>>>> >>>>> Hello, >>>>> >>>>> I was reluctant to purchase the BBAI at first b/c I have heard of >>>>> issues w/ heat dissipation on the board and the chip. Anyway... >>>>> >>>>> Long story, short. I bought it against my better judgement b/c I know >>>>> everyone, in the BBB world, is supportive w/ nice ideas. >>>>> >>>>> ... >>>>> >>>>> So: >>>>> >>>>> >>>>>- I went to: https://beagleboard.org/upgrade. >>>>>- I upgraded the board and adjusted things. >>>>>- I rebooted the board and found the board to be just as hot. >>>>> >>>>> >>>>> Has anyone else come across an issue w/ heat or a fix to the heat >>>>> issue? >>>>> >>>>> Seth >>>>> >>>>> P.S. I might get rid of some of the extras that comes with this board >>>>> but I purchased it for its functionality. I want to use the M4, TIDL, >>>>> EVEs, >>>>> and other >>>>> more complicated chips for fun! I was thinking I would finally learn >>>>> to program the PRUs too. I am going to try to get rid of node-red, >>>>> chromium, and >>>>> some other sockets and ports on the board. I think that these may >>>>> cause services that I will not use ever. >>>>> >>>>> ... >>>>> >>>>> If you are using the board, the BBAI, and you have had some similar >>>>> issues and came up w/ a nice fix, please let me know. I would like to try >>>>> all >>>>> or any relative sources of ideas to support the heat consumption on >>>>> the board. >>>>> >>>> >>> On Sunday, December 29, 2019 at 8:56:07 AM UTC-6, Stephen Johnson wrote: >>>> >>>> I bought a USB powered fan which gives a very low airflow, but has kept >>>> everything cool to the touch. >>>> I just have th
[beagleboard] Enable Bluetooth?
I just got a new AI board and wanted to play around with the bluetooth, but when I launch bluetoothctl, the list command says no controllers found. Is there any information out there on setting up bluetooth on this board? I have google'd everything I could think of with no avail. I have run systemctl status bluetooth and there are no issues, am I missing something? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/566d708f-3420-491f-a708-548e39292427%40googlegroups.com.
[beagleboard] Boot failure No lights
my rev C was running for weeks plugged in via usb To an iPhone charger. I had a wifi dongle attached, but Was using Ethernet for network as I hadn't gotten the wifi working. The other day I noticed it was off yet still plugged into usb. I tried connecting it to 5v ax adapter without wifi dongle attached. I get a brief led light Next to the 5v port that quickly shuts off. No other leds come on ever. It acts like a dead unit. This was running Debian that shipped with The rev c. Should I try to get a mini sdmc with Debian image and insert That in the sdmc slot?? I've tried all variables I can think of including known good ac adapters. Should I get an rma process going? Appreciating all responses on this topic, Seth -- 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] Purpose of the GND_OSC zero ohm resistors?
Thanks for the info, John. I thought it might have something to do with that. If I get a chance I'll have to pick up that book - thanks for the suggestion! I see in the earlier BBB designs the GND_OSC wasn't connected to the main DGND. Only later were they connected (via those zero ohm resistors), and that apparently helped the BBB function better. To me it seems that would introduce more switching noise (as John put it) than leaving them not connected to DGND. I guess I'm a little confused about John's use of the word isolated (If you don’t isolate the OSC gnd...) - were you suggesting the zero ohm resistors acted as isolation from digital ground in this case? Gerald - do you mean that I could connect the GND_OSC net to the DGND net directly, or were you saying that I didn't need to connect those two at all (as in the earlier versions of the BBB)? What's the reason for having the resistors on the BBB if they're not needed? I was speculating that maybe you weren't initially sure if connecting the ground nets together would solve the ground bounce problem or maybe introduce worse problems, so you used those resistors to allow yourself the ability to leave them unpopulated in the event that it caused more issues than it solved (rather than re-spin new boards without the connection at all). -- 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] Purpose of the GND_OSC zero ohm resistors?
I'm looking at making my own version of the BBB for a custom project. I see a note on Revision A6: Noise issues were observed in other designs where the clock oscillator was getting hit due to a suspected issue in ground bounce. A zero ohm resistor was added to connect the OSC_GND to the system ground. A second resistor was added in the next revision to the 32kHz crystal circuit. Could the GND_OSC nets be tied directly to DGND without zero ohm resistors? Was the resistor used just in case the change caused problems and could be left unpopulated if so? I see no issues in further revisions so I'd assume that these changes fixed the issue, is that right? I'm asking because I suspect there might be another reason why resistors were used instead of just direct traces (like needing a 'single connection point' type of thing). Some clarification would be helpful indeed. Thanks, -Seth -- 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: What's the size of blue LEDs on BBB?
The hardware files for the BBB are available here http://elinux.org/Beagleboard:BeagleBoneBlack#LATEST_PRODUCTION_FILES_.28C.29. On page 6 of the schematic, the part number listed for the four user LEDs is *LTST-C191TBKT*. Digikey has those available here http://www.digikey.com/product-detail/en/LTST-C191TBKT/160-1647-6-ND/1888679. As Bas mentioned, they are indeed *0603*. On Monday, November 24, 2014 11:52:28 AM UTC-6, Energia wrote: What's the size of those blue SMD LEDs that are on BBB? 1206? 0805? -- 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: Power off current consumption
Thanks Shawn. I only used a simple multimeter to measure current. It'd be nice to have the equipment to make nice plots like the ones you made. However I think in my case that much detail wasn't necessary to draw a conclusion that current consumption increases after *poweroff* had completed. I think I remember reading someone saying that when being halted the CPU goes into a while(1) loop or something - which may explain why the current goes up, but I'm not sure. Using freeze was the only power state that did anything, but it unfortunately didn't lower the draw any. I have considered adding a microcontroller to the design to cut power to the overall system. However, it seems like that complication could be avoided with some software work. I'd much rather let the professionals work on the software than try it myself since I have much less experience with this sort of thing. If there is no current solution, it would at least be nice to get an estimated timeframe for when, if ever, it may be looked into. So I don't go designing a microcontroller, etc into my design only to have the software fixed afterwords and my efforts be rendered unnecessary before I even get it finished :). Anyway, thanks for your input Shawn. Always good to know I'm not the only one experiencing a problem. Glad you got it figured out for your project! Regards, -Seth -- 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: kernel v3.16 + PWM
All the instructions that I can find are for the Cape Manager, so pre v3.14 (I think). From what I gather, Robert Nelson is currently in the process of getting all capes working for v3.14 and then forward-porting to v3.16 - is that correct? If so, then I suppose my best course of action is to simply wait for the PWM cape to work its way up Robert's cape list and eventually a *am335x-bone-pwm* DTB file should show up in the */boot/dtbs* directory after updating my BBB, correct? Robert if you read this, do you have a general order of which capes you're working on first? I'd guess the ones you have on-hand? Of course there's no rush - I'm just curious and I can wait until later to implement PWM in my project anyway. Without Robert I'd be much farther behind in my progress than I am due to his continued help. Keep up the excellent work! P.S. - will getting PWM working for capes also mean the LCD backlight can be adjusted again vs just on or off? -- 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] Power off current consumption
I measured the current (DC jack powered) my BBB (rev C, kernel v3.16.3) draws at idle: ~200mA. Then I issued a *poweroff* (or *shutdown now*) command, and after the system had halted I measured current draw at ~240mA. This is a bare BBB with nothing attached (besides the serial debug cable). This isn't what I expected to happen. Holding the power button for 8 seconds does power off the BBB (1mA). However, I find the method of hold for =8 seconds, but not =8.5 seconds or else it power cycles to be kind of user-unfriendly. Is there a way to programmatically put the BBB into the same state as holding the power button for 8 seconds? I've done a bit of searching and it looks like there were problems (from earlier in the year) with the PMIC/RTC and bringing the board down to a low-power state from software alone. I just wanted to ask if those problems had been resolved. I tried doing a *echo mem /sys/power/state* which returned Invalid argument. Note that I'd like to try both methods: software command the BBB to power down as if the power button had been held for 8 seconds, as well as a memory-saving/restoring state. -- 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] kernel v3.16 + PWM
It seems as though PWM does not work in v3.16 as in earlier kernels. Am I overlooking something or does PWM not work yet in the more recent kernel versions? 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.
[beagleboard] Re: PWM howto for BBB linux 3.16.x?
Bump, as I have the same question. Any updates? 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.
[beagleboard] kernel v3.16 + bluetooth
I'm using v3.16.2-1-ARCH. I've followed these steps to connect a bluetooth
headset:
[put headset into pairing mode]
*pulseaudio --start*
*bluetoothctlpower ondevicesagent on*
*trust *[device address]
*pair *[device address]
*connect *[device address]
After which a Connection successful message is displayed, and I can hear
the headset beep indicating that it has connected.
Then I run:
*mplayer -ao alsa:device=bt /usr/share/sounds/alsa/Front_Right.wav*
but it fails with this message:
[AO_ALSA] alsa-lib: dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared
library /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so
[AO_ALSA] Playback open error: No such device or address
Failed to initialize audio driver 'alsa:device=bt'
Could not open/initialize audio device - no sound.
Note that I have configured */etc/asound.conf* as follows:
pcm.bt {
type plug
slave {
pcm {
type bluetooth
device [device address]
profile auto
}
}
hint {
show on
description BT Headset
}
}
ctl.bt {
type bluetooth
}
I have read various comments stating that bluez5 does not work with alsa
and bluetooth. It was suggested to use bluez4 and alsa for full
compatibility (Bluez5 is only supported by Pulseaudio and not by ALSA. If
you do not want to use Pulseaudio, you need to install an older Bluez
version from AUR.). I don't know if the issue has been resolved or if I
need to try something else. Googling for
libasound_module_pcm_bluetooth.so doesn't return much help, which leads
me to believe my problem is a unique one and why I've elected to ask for
help here. I am using alsa for standard headphone playback just fine, so it
would be preferred to not need to deal with pulseaudio as well. However, if
that is required then I'll give that a try.
Any suggestions would be appreciated!
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] New kernel + old audio cape
Thanks for the info. I always appreciate your kindness and willingness to help everyone - especially those like me who often struggle with the 'little stuff'. I'm looking forward to seeing if you could get your original audio cape working. There's also, of course, a possibility I've messed something up too far in my setup. I have also been mucking around with getting bluetooth audio to work. I've read there were apparently issues with compatibility between alsa and bluez5, and that pulseaudio was needed instead. I tried many different things but couldn't get that working either. I may very well have messed something else up in that trial and error process. If you get your audio rev A board working without problems, I'll probably install a fresh image on my BBB and start again. Regards, -Seth -- 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] New kernel + old audio cape
It works! What did you have to change to get it working? Thank you very much for your continued help! -Seth -- 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] 3.16 Cape not working
Ahh, I mistakenly thought the rebuilder put them in the right place to begin with. All I had to do was move the new *am335x-boneblack.dtb* up one folder to */boot/dtbs* and now it works. 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] Re: Qt5 on Debian BBB
Thanks don. That's cool Qt is all ready to go on ALARM. Is there also an easy way to change the splash screen to something custom, like what Plymouth seems to offer? I didn't get there yet but it seemed like Debian had a few guides around that I could use. -- 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: Qt5 on Debian BBB
Well that sounds really nice! Thanks for your help don - I'll give that splash update process a shot. -- 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] Qt5 on Debian BBB
I've been following this guide http://embedded.von-kannen.net/2014/05/21/qt-4-8-6-on-beaglebone-black/. However, I am attempting to use Qt 5.3 instead of 4.8.6 as in the guide. I'm using this Qt source for 5.3.1 http://download.qt-project.org/official_releases/qt/5.3/5.3.1/single/qt-everywhere-opensource-src-5.3.1.tar.gz. The differences start at the *mkdir mkspecs/qws/linux-am335x-g++ *line of the guide. In the Qt 5.3 source, there is already a directory: *qt-everywhere-opensource-src-5.3.1/qtbase/mkspecs/devices/linux-beagleboard-g++* which already has a premade qmake.conf file (the guide explains that this directory and file don't exist in Qt 4.8). I would like to use the touchscreen and therefore I followed the guide's instructions for building tslib. It says to add these two lines to the *qmake* file to enable the touchscreen support: *QMAKE_INCDIR += /home/user/qt-bbb/downloads/tslib/src* *QMAKE_LIBDIR += /home/user/qt-bbb/tslib/lib*(user in my case is just seth) The premade file does not include these lines. It's easy enough to add, but one of my questions is: Do I need to still do this for Qt 5.3 or is that somehow included already? I'd rather ask for help here first than to do it wrong and have to re-do it (I remember this process causing me headaches when I had to do it before on the BBW). I did try running the configure command with the *-qt-mouse-tslib* switch, but it complained that it wasn't a valid switch so I would guess I no longer need to do this? My last question (for now) is regarding the configure command. I've tried the following: *./configure -v -opensource -confirm-license -no-pch -no-opengl -make libs -device linux-beagleboard-g++ -xplatform linux-arm-gnueabihf-g++ -no-accessibility -qt-zlib -qt-libpng -qt-libjpeg -device-option CROSS_COMPILE=/home/seth/qt-bbb/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux/bin/arm-linux-gnueabihf- -prefix /opt/qt5* As this is similar to this post https://qt-project.org/forums/viewthread/45054. However, upon running I get: *The specified system/compiler is not supported: /home/seth/qt-bbb/qt-everywhere-opensource-src-5.3.1/qtbase/mkspecs/linux-arm-gnueabihf-g++* Sometimes the error gives enough info for me to figure out myself but I don't know about this one. I never gave it */home/seth/qt-bbb/qt-everywhere...* in the configure line so I don't know where that is coming from. In fact, I thought the CROSS_COMPILE option I gave it would be the one used, but apparently not? Note: I am using Ubuntu 14.04 for doing this. I got the toolchain from here http://releases.linaro.org/14.04/components/toolchain/binaries where *gcc-linaro-arm-linux-gnueabihf-**4.8* is the latest. If you think I could get more help by posting these questions on the qt-project.org forums I will do so. Thanks for any guidance! -Seth -- 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: Qt5 on Debian BBB
I may have figured it out. I simply changed *-xplatform linux-arm-gnueabihf-g++ * to *-xplatform **devices/linux-beagleboard-g++* and it got past the error I was having. I'll post again here if I run into any more issues. -- 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: Debian Image Change Log?
Thanks for the help, Robert. That clears things up a bit. I've flashed my BBB with the https://rcn-ee.net/deb/testing/2014-08-19/console/BBB-eMMC-flasher-debian-7.6-console-armhf-2014-08-19-2gb.img.xz image found on the page you gave. However, now there is no drive when I plug in the BBB to my PC using the BBB client port. Normally a drive shows up on my computer with *uEnv.txt* and other files, but there is no drive this time. I tried searching around a bit but couldn't find anything to help me troubleshoot. Is this an expected behavior for the newer image or might something be wrong? Is this a result of me choosing the console image this time around? I'd like to start small and install the things I need as I go. How else would I edit the *uEnv.txt* file? Also, I'll be needing Qt4 (or maybe 5 if that is available), but *libqtguie4 *is not found in the built-in repositories when I use *apt-get install *(I did do* apt-get update *first). I've tried looking around a bit but haven't found a solution to this either. Do you know if there is a prebuilt package in another repository somewhere? Or do I need to build it myself? This package was included in the Angstrom default repos so it was a quick easy install process. 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/d/optout.
Re: [beagleboard] Re: Debian Image Change Log?
Thanks, I'll try modifying the uEnv.txt at /boot then. I do have a debug cable and have access that way. As for Qt - I have a prebuilt application which worked with Angstrom on the BBB. I wish to simply move the file over to the BBB and run it. I don't need the ability to compile or create new Qt applications on the BBB itself. When I try to run my application on the BBB, it says either No such file or directory or command not found, depending on which directory I'm working from and if I prepend a ./. I can see the file in the proper place, with executable permission, and I've tried using the whole path as well as going into the folder where the application resides and running it from there, but the BBB just can't find it. I assume that is because I need to install more than just libqt4-core, but I have no idea which other packages to install to get it working. I could install them all and try again, but if it didn't work I'd be back at square one and if it DID run then I'd have no idea which packages were actually necessary. I have gone through the process of building Qt from source way back with the BBW a long time ago and it was quite a lengthy process. Then when BBB first came out all I had to do was *opkg install libqtguie4 qt4-embedded-fonts* and my application worked. In summary, can I just install prebuilt packages with apt-get and if so, which ones (since *libqtguie4 *doesn't exist in the pre-loaded repos)? If not, will I need to go through the process of building Qt from source again? Thanks again, -Seth -- 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: Debian Image Change Log?
Alright I'll give it a shot. Thanks for your help! -- 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] Debian Image Change Log?
I'm just getting around to playing with my new Rev C BBB. This is my first time with Debian on a BBB. I'm having trouble finding the change log or update notes on the releases of the Debian images. For instance, the ID.txt from the stock image shows *Debian Image 2014-04-23*, but I've just downloaded a version from *5-14*. Usually I like to keep things up-to-date as I have occasionally bumped into a bug that was fixed in later image builds. However, I also don't want to break my current setup when updating. A Change Log would be very helpful. I found the log for the Angstrom images but I haven't had much luck finding one for the newer Debian images. Is there a maintained Change Log for the new Debian images? In particular, what are the changes from the shipped 04-23 version to the newest 5-14 image? Is there a better place to find images than http://beagleboard.org/latest-images? === With more searching I've found http://elinux.org/BeagleBoardDebian#BeagleBone.2FBeagleBone_Black. Why doesn't the *beagleboard.org* page have this latest image from *8-13*? Which should I use? That leads me to https://github.com/RobertCNelson/bb-kernel/releases, which leaves me even more confused. I see kernel versions 3.8, 3.14, 3.15, 3.16 and 3.17-rc1, with boneXX codes following. These don't seem to be necessarily updated in a chronological order. Which main kernel version is recommended and what are the main differences, as far as Debian on BBB is concerned, between 8, 14, 15, 16 and 17? From what I can remember, 8 is the most stable version, with the others being sort-of beta with more possible bugs? I haven't kept up-to-date with this for several months so I apologize if this has been covered elsewhere. For now I will plan to use a prebuilt image from https://rcn-ee.net/deb/microsd/wheezy/bone-debian-7.6-console-armhf-2014-08-13-2gb.img.xz. 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.
[beagleboard] Re: Beaglebone Black Audio Cape LCD7 == Flashing (HDMI/eMMC disabled by uEnv.txt
Not that it helps any, but I'm also running into this with a similar setup (LCD7 A3 though and the default Angstrom distribution on a BBB A5C as well. Still investigating - let me know if you've found any resolution since you posted this. On Tuesday, August 13, 2013 1:58:56 PM UTC-4, meino@gmx.de wrote: Hi, Following setup: LCD7 A2 Audio Cape Beaglebone Black A5C Linux kernel 3.8.13 (Robert Nelson) Gentoo Linux In the uEnv.txt I have removed the '#' in front of the line, which disables eMMC and HDMI. Booting the Beaglebone Black with the LCD7 works. Adding the Audio Cape and boot again results in an crazy flashing LCD right after Tux appears and the kernel starts. The compatibilty table on the web (was it at beagleboardtoys?...sorry cant remember in the moment) it is said, that the Audio Cape works in case of disabled eMMC and HDMI. Is there a way to make this combo working? Thank you very much in advance for any help! Best regards, mcc -- 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] Knee Brace Project planted with 6 Accelerometers and BBB
That code actually works with the ADXL345? You've tested it and it gives the right result? -- 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] Knee Brace Project planted with 6 Accelerometers and BBB
I wouldn't try testing with that code - I found it herehttps://gist.github.com/grodtron/4751014, and by the looks of the commenting it is meant to work with a LSM303DLHhttp://www.pololu.com/product/1250/, not a ADXL345. I found thishttps://github.com/jenschr/Arduino-libraries/blob/master/ADXL345/examples/ADXL345_no_library/BareBones_ADXL345.pde, however, which looks like demo code for the device you have, although it is written for Arduino and not in Python but it should get you on the right path. -- 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: Cape Device Tree Overlay fails to load during boot?
I just read this thread and thought wow, this is the same set of experiences I've had over the last couple months. OK, I have read this threadhttps://groups.google.com/forum/#%21msg/beagleboard/Iem_mHknIUM/buwAqagYukwJtwice now, and I still fail to see any real solution in between the discussion of various patches. - me too. As can be seen I also appear in that thread asking questions. I have made a Cape PCB...- me too (basically). I have disabled the loading of all HDMI overlay features in uEnv.txt. - me too. Yes it seems lots of people are in the same situation. - looks that way to me too. OK, so despite all the halabaloo about Device Tree Overlays you still need to build a custom kernel to add a new cape at boot, is that so? I kind of thought the whole point was getting rid of that ;-) - my thoughts exactly (...I thought the nice thing about the 'cape' concept was that you were supposed to be able to basically plug them in...and they would workhttps://groups.google.com/forum/#%21topic/beagleboard/DfdVNS_ubnA ). OK, I bit the bullet and went through the custom kernel build process. - me too, after waiting patiently for a fix or other solutions. Robert, after much headscratching at the various Angstrom download and instruction pages, which seem to be in various stages of bit-rot... - Agreed. It's difficult to find instructions online that are up-to-date. Spending hours traveling down the wrong path becomes frustrating after you do it multiple times. ...I switched my attention to your stuff, which seems a lot more well maintained. - me too at first (especially after I found a post where Robert said he had taken over pushing changes to the beaglebone fork or something along those lines, and of course I can't find it now, but it made me think that was the best way to keep up-to-date), although I got stuck and am back to using the angstrom-distribution setup-scripts method (which seems to be working so far). I am still unsure when a person is supposed to use Robert's instructions versus the angstrom-distribution method. Just today I think I've made progress in this area after trying for several days over the last couple months. I think I have to figure out how to title my questions on Google Groups so people are more likely to answer them. I tried changing my question-asking strategy to a higher-level question (most recent examplehttps://groups.google.com/forum/#%21topic/beagleboard/jMNaPu00JA8) so more people would feel they could answer, but not even that seems to work. Or maybe it's just the weekend, I'm not sure. At any rate, I just wanted to chime in to make it known that there are definitely others with very similar issues regarding capes. I continue to appreciate the help the forums and lists provide and the work and support of the professionals currently involved with the development of the Beaglebone. I hope we all can get our projects working without too much additional struggle. Cheers! -- 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: Compile Angstrom for Beagle Bone black.
I'm following the instructions posted above, but when I run *bitbake console-image*, I immediately get a No such file or directory error for setup-scripts/sources/meta-angstrom/conf/layer.conf. I should note that I've recently tried other methods for building the kernel. For this new attempt I made a new directory. Simple fix? -- 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] Best way to build Angstrom kernel
I would like advice on the best way to rebuild the Angstrom kernel for the BBB. I need to do this because I do not want HDMI support, but DO want Audio cape support. I have read (last post herehttps://groups.google.com/forum/#!topic/beagleboard/ZJGwxA7BG4E) that disabling HDMI patches and rebuilding will do that. I have rebuilt kernels for embedded Linux before (for the BBW as well as the FriendlyArm years ago), and I remember it being a complete pain in the neck. Many days of troubleshooting errors, setting up build environments and such. I should say that I am still relatively new when it comes to Linux and I was probably doing things the hard way. I have been occasionally checking in this group and reading how others solved their problems which is encouraging. However, I'd like the most up-to-date instructions to use, if possible. I have been using BBB flasher images from this linkhttp://dominion.thruhere.net/koen/angstrom/beaglebone/since they seem to upload new images pretty often. I can't seem to find a change log for those images, however (I see the log on the official Software Update page but that doesn't cover all the mini-updated images). I have also read that the patch developers were working on a way for both HDMI and Audio capes to work at the same time without need to rebuild the kernel, but I have not seen any news about that lately. I was hoping to wait until they had those compatibility issues worked out in a new release so I didn't have to bother with the rebuild, but I've been waiting several months and am ready to try fixing it myself. I would like the kernel that I build to be as updated as possible. For example, the latest flasher image from the link I posted above was from yesterday, the 8th. I don't know if that's even necessary since I cannot seem to find the change logs for those images. I have found (again from the first link I gave) this page http://derekmolloy.ie/custom-kernel-and-angstrom-distribution-recipe/and this page http://derekmolloy.ie/building-angstrom-for-beaglebone-from-source/which seem to have a pretty good list of instructions. Would you recommend I follow those or is there a better set of instructions elsewhere that I could use? Normally I would just jump right in and try it, but I have been burned before by following out-of-date instructions, wasting lots of time only to get nowhere. This is especially bad due to the fast-changing nature of Linux. I also don't want to spend time doing this process only to find that a newer image has been released, requiring me to do the whole thing again. I can't seem to find any predicted new BBB image release schedule anywhere. Does anyone know if any major updates are planned to be released soon? I thank you in advance for your time and advice. -- 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.
