**** BEGIN LOGGING AT Wed May 24 03:00:05 2017 May 24 07:12:15 Hi, I'm currently trying to build custom device tree overlays for my beaglebone (Debian Jessie March 2017, Kernel 4.4) and I can't get it to work correctly. I can use the overlays to enable e.g. BB-PWM1 but I need other Pins aswell and I cannot load an Overlay for each Pin. Does someone maybe have an current tutorial/example where they got it with an up-to-date debian version to work? May 24 07:14:06 BeagleRookie: there are a bunch of examples in the bb.org-overlays repo. May 24 07:14:23 https://github.com/beagleboard/bb.org-overlays May 24 07:14:39 (also, installed in /opt/source/bb.org-overlays May 24 08:56:32 Hi jkridner, thanks for your reply, I have already looked into that repo and did so again now but I still cannot figure out how I can build my overlay the way I want it to be. E.g. when I enable P9_14 for PWM that he automatically configures the folders so that my programm doesn't have to do it(echo to export, duty_cycle, period and enable). I have overlays on other websites who seem to use that but I can't get their overlays t May 24 12:05:39 hii May 24 12:06:12 i am FPGA based R&D engineer May 24 12:06:30 want to work as freelancer for beagleboard. May 24 15:53:17 can recommend how to battery power beaglebone green wireless ? May 24 15:53:30 does someone sell a kit ? May 24 15:53:35 a USB battery works nicely. May 24 15:53:53 swayzie: Andice has a cape I suspect should work... haven't tried it on a Green Wireless though. May 24 15:54:32 Don't know if that cape relies on getting power in from the 5VDC or has its own connector. It would need its own connector to work with Green Wireless. May 24 15:55:07 http://andicelabs.com/beaglebone-powercape/ lists Green, but not Green Wireless specifically. May 24 15:55:29 also i have grove base cape v2 with gps on uart May 24 15:55:42 the mechanical cut-out might be a bit of an issue on the Green Wireless due to the additional USB connectors. May 24 15:56:52 wonder if i can find usb battery small enough to fit in my enclosure :) May 24 15:57:22 thanks for the link ! :) May 24 17:28:36 Hi. What have I to do when modprobe uio_pruss fails on BBG with Linux beaglebone 4.4.9-ti-r25 image? May 24 18:00:34 NTQ: pastebin the output of dmesg May 24 18:12:22 jkridner: https://pastebin.com/f5AR4g7k May 24 18:13:23 NTQ: looks like you didn't disable the remoteproc driver in /boot/uEnv.txt. May 24 18:14:31 NTQ: since you have a PRUDAQ cape, looks like you'll also want to disable the univ-emmc (disable cape-universal entirely, most likely) May 24 18:16:43 jkridner: I don't know if I need univ-emmc. This is my uEnv.txt: https://pastebin.com/RDe4Cq2X May 24 18:17:07 At the moment the system runs from flash instead of the sdcard. May 24 18:20:45 I found this google groups thread: https://groups.google.com/forum/#!topic/beagleboard/1rIV-mR8wYw . Then I tried the solution from Greg but I am not able to compile because make throws errors. May 24 18:21:01 And maybe this is just overkill. I don't know :-( May 24 18:42:59 jkridner: What exactly have I to change in the uEnv.txt? May 24 19:51:19 NTQ: you'd have to read the notes inside of it. May 24 19:52:04 NTQ: you want to disable universal as you shouldn't need it for PRUDAQ. May 24 19:52:29 beagleslackbot: It seems to work know. I made a "git pull" in /opt/scripts/tools and then executed update-kernel.sh --bone-kernel --lts-4_4 May 24 19:52:43 Great! May 24 19:53:33 I guess that added support for PRUDAQ then, overriding the need to edit the uEnv.txt? May 24 19:53:55 beagleslackbot: yes May 24 19:54:32 You also enabled uio by switching from a kernel that defaults to remoteproc to one that defaults to uio. May 24 19:54:49 (TI vs Bone kernel) May 24 20:03:04 beagleslackbot: Maybe you can also help me with something different. I want to reduce the size of the filesystem and I guess there are plenty of packages installed I don't need. For example opengl and vesa drivers, sound, drm, whatever... At some point I will run out of space. 94% of 3.6 GB were used. May 24 20:38:33 I apt-get purged some packages and now only 78% are used. May 24 21:42:56 NTQ: if you don't use graphics, I'd suggest starting with an iot or even a console image and then install stuff as needed, that's typically easier than trying to strip a system that's stuffed with crap May 24 21:44:39 to trim down the amount of packages, two tips that might be useful: May 24 21:45:39 1. to prevent packages from remaining installed merely because they're "recommended" (not *required*) by some installed package, you can use a config file like this: https://hastebin.com/orupunatet.conf May 24 21:47:17 2. examine the list of packages that are "manually installed" and see if they are of direct importance to you, if not use "apt-mark auto" to mark them as "automatically installed" May 24 21:48:17 especially libraries almost never have a reason to be set "manually installed", except for -dev packages of libraries you're using for your own software development May 24 21:49:00 "apt-get autoremove" can then be used to get rid of packages that no longer have a reason to be installed May 24 21:50:12 3. If you know what you are doing, you can use rm and dpkg filters to get rid of /usr/share/doc, locales, manpages etc. May 24 21:51:08 I've never felt a need to go that far myself May 24 21:52:22 on development beagles we generally hover beween 1.5G and 2.5G used... they tend to get encrusted with cruft over time and cleaned up occasionally ;) May 24 21:53:00 deployment beaglebones have around 400M used May 24 21:53:27 (these don't have development tools or such) May 24 22:31:22 zmatt: Thank you **** ENDING LOGGING AT Thu May 25 03:00:02 2017