[beagleboard] Re: PRU C Project - from device tree to program execution

2015-12-18 Thread Super Twang
Hi Robert, I'm trying to follow your recipe but am getting the following error: (NOTE: I called the PRU code file template.c instead of source.c): Any idea what I'm doing wrong? I'm on kernel 3.8.13 (Debian Wheezy). Fwiw, I do see the symbol __PRU_CREG_CFG defined in the template.map file,

[beagleboard] How to figure out the minimal set of services for an embedded Beaglebone Black app on Debian Wheezy

2016-01-25 Thread Super Twang
Hello all, Is there a good resource (besides this list! :) that would help me understand what to remove/disable from the stock Debian Wheezy distro, on a BeagleBone Black, to arrive at a barest-minimum/rock-solid setup to run a dedicated app, as an embedded device? Background: I've developed

[beagleboard] Re: Reading BeagleBone Serial Number

2016-02-01 Thread Super Twang
Hi all, FWIW, based on the answers in this thread, and a little messing around with an element14 BBB rev C, the following command produces a result which seems to match the serial number printed on the bottom of the bar code sticker, attached to the left-most, outside edge of the P8 header.

[beagleboard] Re: How to figure out the minimal set of services for an embedded Beaglebone Black app on Debian Wheezy

2016-05-15 Thread Super Twang
@Mark I've done what you said and started with a console image. That was a huge boost towards a minimal setup... thanks for the tip!!! That said, even with a console image though I'm seeing lots of stuff I wouldn't think I'd need ( using dpkg --list, and systemctl list-units --all ). These a

Re: [beagleboard] Hardware watchdog for BBB

2016-05-15 Thread Super Twang
I've just come across this conversation in my own search for a rock-solid, embeddable configuration for the BeagleBone Black. I’m trying to develop an embedded controller device that needs to live behind walls, in ceilings and in other inaccessible places. ( It is for the automation of art &

Re: [beagleboard] How to figure out the minimal set of services for an embedded Beaglebone Black app on Debian Wheezy

2016-05-15 Thread Super Twang
@Taceant | https://buildroot.org That looks VERY promising and definitely along the lines of the way I'd like to think; Build up from nothing, ie additive rather than subtractive. Also, as a real bonus, it would seem to automate the creation of a cross-compilation toolchain (I've been doing a

Re: [beagleboard] Re: How to figure out the minimal set of services for an embedded Beaglebone Black app on Debian Wheezy

2016-05-15 Thread Super Twang
> > @Robert > Thanks for the tip. Are the '*fs' filesystem packages actually functionally complete OS's? Does your barefs boot the BBB into a state into which I can ssh? In my local network setup, I believe I'd need a dhcp client on the ethernet port (I don't control the router). Oh wait,

Re: [beagleboard] Re: How to figure out the minimal set of services for an embedded Beaglebone Black app on Debian Wheezy

2016-05-15 Thread Super Twang
@Robert [Preamble: Thank you for prepping the various images/flavors/recipes/etc I know you're generous enough to design/maintain/share, as well as your willingness to help folks like me] Ok good. Your clarification definitely helps! So an 'image' == kernel + bootloader + filesystem. Good.

Re: [beagleboard] Re: How to figure out the minimal set of services for an embedded Beaglebone Black app on Debian Wheezy

2016-05-15 Thread Super Twang
@William [Preamble: Thanks also for your clarifications here, and, all over this forum. I think I've learned about 90% of what I know from conversations between you, RobertCNelson, John3909 and a handful of others.] Is there a source you'd recommend for: | find a kernel and driver modules al

Re: [beagleboard] Hardware watchdog for BBB

2016-05-15 Thread Super Twang
Sorry guys. I might be confusing my terms here, or misusing the phrase 'watchdog timer'. Would 'hardware watchdog circuit' fit? "Intelligent power switch?" I'm not quite sure what to search for! The circuit I'm looking for is what John3909 is describing; something to address the corner-cas

[beagleboard] BUG? device tree overlay strange persistence using rcn's 8.4_console_4/7/2016 + 4.4.9-bone-rt-r10

2016-05-16 Thread Super Twang
I'm seeing some strange persistent/erroneous behavior with a device tree overlay that I wanted to ask about. Specifically, I'm seeing startup errors in 'dmesg' which reference symbols in a device tree overlay (.dtbo) that no longer exist. [ 11.591461] pinctrl-single 44e10800.pinmux: bad data

[beagleboard] device tree overlay strange persistence using rcn's 8.4_console_4/7/2016 + 4.4.9-bone-rt-r10

2016-05-16 Thread Super Twang
I'm seeing some strange persistent/erroneous behavior with a device tree overlay that I wanted to ask about. Specifically, I'm seeing startup errors in 'dmesg' which reference symbols in a device tree overlay (.dtbo) that no longer exist. [ 11.591461] pinctrl-single 44e10800.pinmux: bad data

Re: [beagleboard] Re: Hardware watchdog for BBB

2016-05-16 Thread Super Twang
Hey y'all (yes, I'm in Texas), I have really appreciated all of the good ideas and thoughtful design ideas here. There are some apples and oranges being discussed at times because the problem of BBB reliability is not single-fold. In the hopes of providing a clearer "Big picture" of the iss

Re: [beagleboard] Hardware watchdog for BBB

2016-05-16 Thread Super Twang
@Gerald I’m a bit new on this forum; forgive me if you’re not the right person to ask… (please, anyone else, respond if you are) Its just that I’ve heard other people request and defer to your opinion on things, and, well, you have a pretty official looking email address! :) I understand the

Re: [beagleboard] Hardware watchdog for BBB

2016-05-16 Thread Super Twang
@Graham Wow! I hadn’t yet thought of Ethernet as a point of failure. Apart from the (“It doesn’t always soft-reset" issue — see outline I.B.1.b) I’d guess you could solve this with the onboard watchdog timer. Run some kind of daemon that periodically “Checks for good ethernet” (a bit vague, I

Re: [beagleboard] Hardware watchdog for BBB

2016-05-17 Thread Super Twang
f 5V was present, and they > had not heard from the BBB lately. > > More appropriate monitoring for a server, than watching some GPIO wiggle. > > --- Graham > > > On Monday, May 16, 2016 at 8:08:01 PM UTC-5, Super Twang wrote: > @Graham > Wow! I hadn’t yet thought

Re: [beagleboard] Hardware watchdog for BBB

2016-05-17 Thread Super Twang
@Lachlan Thank you for sharing your design. I’m definitely learning from it and I’m sure others will too. ST -- 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 gr

Re: [beagleboard] Hardware watchdog for BBB

2016-05-17 Thread Super Twang
Hi y’all, Below is a snippet of an offline email exchange between myself and Gerald of Beagleboard.org … I’m reposting it here because I think it further clarifies some of the subtleties of what is being discussed here, specifically how brown-outs are what throw the wre

Re: [beagleboard] Hardware watchdog for BBB

2016-05-17 Thread Super Twang
winding down so this channel will probably quiet down. Again, thanks for the help. Best, ST > On May 17, 2016, at 2:30 PM, William Hermans wrote: > > Super twang, > > I honestly think you're over thinking the situation. It's good to try and > cover all poss

Re: [beagleboard] Hardware watchdog for BBB

2016-05-19 Thread Super Twang
@Lachlan Thanks for the info Lachlan. Re: Supercap reliability… My basic understanding is that if you design with supercaps for a “Everyday” (ie not too hardcore) indoor use case, and keep them within some pretty obtainable operating conditions they effectively last forever. Obviously there’

[beagleboard] spontaneous reboot issues bbb, jessie 8.4 console image of 4/7/2016, 4.4.9 -bone-rt-r10 LTS kernel

2016-05-19 Thread Super Twang
PS. Is this the best place to put bug/issue reports? I believe this relates to the core image & kernel of a Jessie LTS release. --- I'm seeing semi-regular spontaneous reboots on the BBB. Here's what I'm seeing: Running 'top', the "Mem Buffers" field, (4th line, far right), is steadily inc

[beagleboard] Best (most-stable) console image to start from?

2016-05-19 Thread Super Twang
Can anyone recommend the most stable version of RCN's console images on which to base an embedded device that uses the PRU (uio_pruss)? >From what I understand there was incompatibility with the PRU somewhere between 3.8 - 4.1. I'd like to go back in time (probably to a Wheezy install) to a po

Re: [beagleboard] spontaneous reboot issues bbb, jessie 8.4 console image of 4/7/2016, 4.4.9 -bone-rt-r10 LTS kernel

2016-05-19 Thread Super Twang
:81/farm/uptime/test-bbb-6.log > <http://rcn-ee.homeip.net:81/farm/uptime/test-bbb-6.log> > Double check your power supply.. > > On May 19, 2016 11:34 AM, "Super Twang" <mailto:supertw...@gmail.com>> wrote: > > > > > > PS. Is this the be

Re: [beagleboard] Best (most-stable) console image to start from?

2016-05-19 Thread Super Twang
> On May 19, 2016, at 12:39 PM, William Hermans wrote: > No one can make this determination for you. As there is no "one size fits > all" image. @William I understand. I’m not asking for that. I’m already doing a fair bit of add and subtract, even starting from a console image, to come up wi

Re: [beagleboard] Best (most-stable) console image to start from?

2016-05-19 Thread Super Twang
@William Thank you! I really appreciate you sharing your approach. Your clarification that the uio_pruss/remote_proc issue lies in the choice of kernel, not the version is a subtlety that was escaping me, despite having found my way to the bone-rt kernels. I also hadn’t realized that a 4.1.x

Re: [beagleboard] Hardware watchdog for BBB

2016-05-19 Thread Super Twang
I’m currently looking for low-hanging fruit solutions to improve the BBB’s reliability at the moment and came across this. This open source project aims to provide a generic API to many off-the-shelf UPS systems, usually via a serial/usb/ether connection. I haven’t investigated this in depth y

Re: [beagleboard] Power button and /dev/input/event0 on 4.1.10-bone16

2016-12-01 Thread Super Twang
I think I'm missing something, and I wonder if Robert C. Nelson would chime in. I'm trying to EN-able (not disable) the power button to run a custom script when pressed. I've searched online and have found a lot of related questions but not an approach that I can get to work... I'm running ke

[beagleboard] how to check sleep/hibernate/suspend settings in BBB console images

2016-12-21 Thread Super Twang
I've got a server running on one of Robert Nelson's console images ( 2015-11-03, with kernel 4.1.34-bone-rt-r24 #1 PREEMPT RT). It seems to become unresponsive after several hours, and I'm wondering if there is some kind of powersaving mechanism at play. Does anyone know how to figure out whet

[beagleboard] Re: how to check sleep/hibernate/suspend settings in BBB console images

2016-12-26 Thread Super Twang
Note... even a quick pointer to what I can run at the command line to check these would be most 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

Re: [beagleboard] bone_capemgr bone_capemgr: loader: failed to load slot-4 (prio 0)

2018-11-23 Thread Super Twang
William, THANK YOU for doing this! :) I am finding this in Nov 2018 and your solution is exactly what I'm looking for. I really appreciate you documenting this. But yeah, Google Groups... lol. TBH I'm really surprised I was able to find this! Thanks again. ST -- For more options, visit h

Re: [beagleboard] Re: how to check sleep/hibernate/suspend settings in BBB console images

2017-01-16 Thread Super Twang
Robert, Thank you for clarifying -- this is very useful to know. :) Dave -- 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