Have a question about the Next-Gen BeagleBone? Ask it here!

shabaz wrote:

 

I've not used Angstrom before, it looks like it is supposed to cater for embedded apps (rather than desktop) and I saw busybox was installed too.

Yep, Angstrom supposedly came from the OpenEmbedded stuff. Busybox presence appears to be a bit of a red-herring here. Run opkg list-installed and you'll see 99% of the desktop stuff, and a good chunk of server-side stuff too. There are a few omissions and a couple of bizarre substitutions along with a load of stuff that doesn't immediately appear to be of any use at all.

I'm going to use a bit of kynar wire to patch a 3.3v supply to one of the blank pins on the serial header (e.g. pin 2) from the underside, so I can just plug the cable in to one port.

I'd pretty much decided on doing exactly that too.

I also forgot to order a micro-HDMI cable, so I currently can't see whatever appears on the display. The Pi wins there by using the more usual connector that people are more likely to have available when they forget to order one.

Mine boots from microSD automagically, no need to press the buttom.  If I want to boot from eMMC I have to pop out the card.  My card has the wheezy demo image on it from the elinux site.

BeagleBoard Blacks are now also available from Digi-Key http://www.digikey.com. Ordered mine on Thus. 2 May, shipped Fri. 3 May. YMMV.

A full description of the PRUSS (250 pages) is given in document SPRUH73C.pdf which is an earlier version of the technical reference for the AM335x. For some reason this

document is not avaialable on the TI website although the current version SPRUH73H.pdf is but it only includes a brief (2 page) description of the PRUSS. It was easy to

find a copy of SPRUH73C.pdf using google.

Barry Mark wrote:

 

Mine boots from microSD automagically, no need to press the buttom.  If I want to boot from eMMC I have to pop out the card.  My card has the wheezy demo image on it from the elinux site.

Not here, it boots u-Boot SPL and then u-boot.img from eMMC unless I press the button. The main u-boot on eMMC then goes and touchy-feelies any microSD and if it doesn't find what it's looking for aborts. No attempt to fallback to eMMC boot.

This isn't so bad if your card has whatever the eMMC version of u-boot is looking for - you can probably arrange for the eMMC u-boot to boot linux off the card and I assume that's what you are seeing.  It's a problem if you don't want that version of u-boot, or if your OS doesn't want u-boot at all.

I may have a go at swapping R68 for R93, but not sure that's going to be easy as R93 is quite close to P8.

A small dip switch for S2 instead of a push button would be an interesting change for a future version.

shabaz wrote:

I'm going to use a bit of kynar wire to patch a 3.3v supply to one of the blank pins on the serial header (e.g. pin 2) from the underside, so I can just plug the cable in to one port.

next is to remove that obnoxious blue heartbeat led

selsinork wrote:

 

next is to remove that obnoxious blue heartbeat led

Don't reach for the soldering iron just yet.  The heartbeat LED on USER0 is controlled by the kernel, so a soft hammer should provide the desired retinal relief.

true, but having removed /etc/default/leds it's still doing it, just at a different frequency. So either the kernel is defaulting usr0 to heartbeat or it's hidden somewhere I've yet to find.

As angstrom is using systemd things are pointlessly complex - you can no longer just chuck a one liner into rc.local to fix stuff like this..

(and after less than a day of using it, the systemd 'journal' is corrupt, so no more log messages.. plus systemd seems to handle the log based on dates rather than simply continually appending to a file... which on a system without a battery backed RTC interleaves the logs from different boots with a "-- Reboot --" line inbetween in places where a reboot obviously didn't happen. Outstanding..)

The iron was hot anyway after adding the wire, so bye bye led...

Barry Mark wrote:

 

Mine boots from microSD automagically, no need to press the buttom.

this turns out to be a known problem

https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/OKuX9iapA78

you are booting from eMMC, it just happens that you have a fat partition on your microSD that has a useful uEnv.txt on it. Without that, current versions of the code leave you in limbo with a hung system, you can't even use the microSD as additional storage while booting from the eMMC due to this.

Ah well, now I have a good excuse to go build my own u-boot for it

For anyone else with one of these, see

https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/G_QjWvBNXvc

you'll probably want to go to http://circuitco.com/support/index.php?title=Updating_The_Software and get the latest software image (2013.05.3 as of now) before trying to do anything with opkg

you'll probably want to go to http://circuitco.com/support/index.php?title=Updating_The_Software and get the latest software image (2013.05.3 as of now) before trying to do anything with opkg

Something must have been wrong with the build.  Looks like they pulled it.  I can see it in the change history so you're not a liar