**** BEGIN LOGGING AT Fri Apr 29 02:59:58 2016
Apr 29 11:05:00 <Spidler> Ugh
Apr 29 11:05:12 <Spidler> Tons of USB rx errors now, on new hardware. :-(
Apr 29 11:10:37 <hhe> hi
Apr 29 11:10:55 <hhe> I have problem qtserialport on bbb
Apr 29 11:11:46 <hhe> I follow https://wiki.qt.io/Qt_Serial_Port
Apr 29 11:31:43 <Unee0x> Hey, does anyone know to check if there is a file that tells if anything is plugged into any of the gpio pinholes ?
Apr 29 12:00:28 <hhe> how can I install qtserialport on bbb
Apr 29 12:01:09 <hhe> http://pastebin.com/5DTMt8pY
Apr 29 12:01:14 <hhe> error
Apr 29 12:22:41 <Ionakka> <hhe> http://pastebin.com/5DTMt8pY   <--- looks like errors in .pro or Makefile generation
Apr 29 12:23:17 <Ionakka> ie would check your qt (-dev) and gcc installation first
Apr 29 13:00:28 <hhe> @ionakka it is working when I crosscompile on ubuntu
Apr 29 13:00:50 <hhe> my qt ver 4.8.1 on bbb
Apr 29 13:01:54 <hhe> gcc version 4.7.3 20130205 (prerelease) (Linaro GCC 4.7-2013.02-01)
Apr 29 13:13:45 <RVR_> Hi! Has anyone tried installing qt packages?
Apr 29 13:24:08 <Ionakka> hhe: the qmake specs are worth looking at on bbb
Apr 29 13:24:28 <Ionakka> for qt4 they should be in package qt4-qmake
Apr 29 13:24:54 <Ionakka> <hhe> @ionakka it is working when I crosscompile on ubuntu   <--- it looks like you have right one on ubuntu qemu chroot
Apr 29 13:25:13 <Ionakka> or what is you cross-compilation environment
Apr 29 13:28:30 <hhe> qt working on ubuntu and on bbb
Apr 29 13:28:59 <Ionakka> what you had to fix?
Apr 29 13:29:00 <hhe> only problem with qtserialport
Apr 29 13:29:12 <RVR_> What if I need to complile natively on bbb
Apr 29 13:29:56 <hhe> am I upgrade qt version ?
Apr 29 13:30:06 <hhe> maybe 5
Apr 29 13:30:09 <RVR_> I want to install qt4-default.
Apr 29 13:31:29 <RVR_> It says 'Unable to locate'. What could be the issue
Apr 29 13:32:05 <RVR_> Same thing with qt5-default. 'Unable to locate'.
Apr 29 13:34:31 <hhe> are you using Debian or Angstrom ?
Apr 29 13:35:57 <hhe> on angstrom you can write "opkg install qt4-embedded"
Apr 29 13:47:00 <Raiz> anyone using the BBB as a full desktop computer?
Apr 29 13:50:35 <dirkk> Raiz: what do you mean by full desktop ? I struggle with 4Gb of the emmc ;)
Apr 29 13:51:04 <Raiz> external storage would work with it
Apr 29 13:52:27 <Raiz> I'm just wondering how will it work if I plugged a VGA monitor via a VGA2HDMI adapter then HDMI2MicroHDMI adapter, like... will VGA damage the board?
Apr 29 13:56:01 <dirkk> Raiz: don't know. Did you read the wiki about HW issues  ?
Apr 29 13:56:17 <dirkk> You might start by this
Apr 29 14:03:43 <Raiz> lemme do that..
Apr 29 14:04:20 * Spidler holds his head
Apr 29 14:04:23 <Spidler> Just an FYU
Apr 29 14:04:34 <Spidler> Beagles don't really like life when they get 4.2 Volts
Apr 29 14:05:02 <Spidler> 4.6 seems to be okayish and doesn't seem to cause obvious problems, 4.2  is not happy.
Apr 29 16:33:20 <rvs> hello, I have been trying to enable Timer4 for the beagle bone black using yocto but I have not been successful.  I tried modifying the device tree, enable it in U-boot and nothing.  I have been googling too but it seems that it hasn't been done.  Is anybody of you have been able to work with timers in the beagle bone under linux?
Apr 29 20:08:17 <serailchiller> does anybody know if I can set up a ssh server of my beagleboard so that it can be accessed from outside my network?
Apr 29 20:12:00 <vagrantc> definitely possible, yes.
Apr 29 20:12:40 <serailchiller> i dont have a beagleboard with a ethernet connection
Apr 29 20:12:45 <serailchiller> just an usb
Apr 29 20:12:46 <vagrantc> you'll probably need to configure port forwarding on your router
Apr 29 20:12:53 <vagrantc> and your laptop
Apr 29 20:14:42 <serailchiller> router is done. i have forwarden port 22 to my laptop
Apr 29 20:15:26 <serailchiller> then just forwarding to the beagle adres 192.168.0.202?
Apr 29 20:17:04 <vagrantc> in your laptop's firewall, yes.
Apr 29 20:18:28 <serailchiller> dont have a firewall and running ubuntu
Apr 29 20:20:19 <serailchiller> does it mean adding entry in iptable?
Apr 29 20:23:34 <Eupher1> I can't download the images. I get a note saying there was an error.
Apr 29 20:24:58 <Eupher1> I'm using 7-zip.
Apr 29 20:31:22 <Eupher1> Hello
Apr 29 21:03:15 <zmatt> rvs: I use ePWM... timer should be similar and simpler
Apr 29 21:05:52 <rvs> Hi Zmatt, I tried to enabled it using  timer4_pins: pinmux_timer4_pins {
Apr 29 21:05:52 <rvs>       pinctrl-single,pins = <
Apr 29 21:05:52 <rvs>         0x90 0x12  /* gpmc_advn_ale as TIMER4, OUTPUT_PULLUP | MODE2 */ and then   &timer4 {
Apr 29 21:05:52 <rvs>     pinctrl-names = "default";
Apr 29 21:05:52 <rvs>     pinctrl-0 = <&timer4_pins>;
Apr 29 21:05:53 <rvs>     status = "okay";
Apr 29 21:05:55 <rvs>   }; but it does not work
Apr 29 21:06:07 <zmatt> please don't paste stuff in the channel, use e.g. pastebin
Apr 29 21:09:01 <zmatt> I don't see any  status = "disabled";  property on the timers, so it would appear they are enabled by default
Apr 29 21:09:15 <zmatt> please don't just start private-messaging me
Apr 29 21:10:16 <rvs> sorry for both, pasting and the private, new on this chat stuff
Apr 29 21:10:44 <rvs> thanks for the note, I'll give a try
Apr 29 21:11:04 <zmatt> I'm not sure actually then how you configure them to pwm mode
Apr 29 21:12:36 <rvs> I couldn't find examples on how to use the timer, other than what I got from couple links in the web
Apr 29 21:12:48 <zmatt> if you have a moment, I'm fiddling with device tree myself right now but I can take a quick look in a moment to see how you're supposed to configure timer4-7
Apr 29 21:13:18 <rvs> thanks, this will be very helpful
Apr 29 21:17:15 <ds2> the device tree needs a good chain saw
Apr 29 21:17:31 <zmatt> ds2: then there's ti's hwmods -.-
Apr 29 21:17:59 <ds2> the old hwmod stuff or the new dt interacting ones?
Apr 29 21:18:04 <zmatt> afaict it knows eqep0 etc depend on epwmss0 for their reachability
Apr 29 21:18:17 <zmatt> yet opening eqep0 doesn't automatically seem to enable epwmss0
Apr 29 21:18:18 <will4g> Hi guys! If anyone has already compiled the BBB kernel from source, is there any tutorial you guys recommend following?
Apr 29 21:18:46 <zmatt> making eqep0 a child node of a simple-bus tagged with ti,hwmods = "epwmss0" doesn't work either
Apr 29 21:18:53 <ds2> there is nothing special about compiling the kernel on the BBB
Apr 29 21:19:01 <ds2> it compiles exactly like any other kernels
Apr 29 21:19:42 <zmatt> will4g: git clone https://github.com/RobertCNelson/bb-kernel
Apr 29 21:19:59 <will4g> Thx zmatt
Apr 29 21:20:13 <zmatt> will4g: check out the desired branch (e.g. am33xx-4.1 and -4.4 are the LTS branches I think)
Apr 29 21:20:33 <zmatt> copy system.sh.sample to system.sh and modify it to taste
Apr 29 21:20:37 <zmatt> ./build_deb.sh
Apr 29 21:20:41 <zmatt> grab a coffee
Apr 29 21:20:50 <zmatt> voila, your very own debian package of a kernel
Apr 29 21:21:05 <zmatt> if you don't want it debian-packaged, there's also just ./build_kernel.sh
Apr 29 21:21:48 <will4g> zmatt: I'll go with the second one
Apr 29 21:22:00 <zmatt> there are also newer branches
Apr 29 21:22:05 <zmatt> and -rt variants
Apr 29 21:22:15 <ds2> RCN a nice kernel builder wrapper that will do all that
Apr 29 21:23:13 <zmatt> ds2: aha, I can just tag ecap0/eqep0/epwm0 all with hwmod epwmss0 ... it's okay with that :D
Apr 29 21:23:23 <zmatt> it doesn't have any real understanding of the submodules anyway
Apr 29 21:23:29 <will4g> zmatt: Actually, I need a somewhat ancient version of the kernel (3.0.x to be exact). I haven't found it in any of the branches
Apr 29 21:23:39 <zmatt> "somewhat" ancient
Apr 29 21:23:46 <zmatt> lol
Apr 29 21:24:01 <zmatt> that's more like archeology
Apr 29 21:24:29 <Vestax> zmatt, you told me yesterday that you had a way to debug the SD card slot. Do you have time to share your knowledge now?
Apr 29 21:24:58 <zmatt> Vestax: get in queue
Apr 29 21:24:59 <zmatt> :)
Apr 29 21:25:16 <zmatt> nm, rvs left apparently
Apr 29 21:25:35 <zmatt> well, you're at the front of queue now, but I was stil checking something first
Apr 29 21:25:52 <Vestax> Sure just let me know whenever you have time
Apr 29 21:29:42 <rvs-m> zmatt: switched machine and tried your suggestion, not working
Apr 29 21:37:53 <zmatt> I haven't made any suggestion yet
Apr 29 21:39:55 <rvs> The status= "disable" i just gave a try
Apr 29 21:53:49 <zmatt> Vestax: you'll need a linux system running first though, have that?
Apr 29 21:53:59 <zmatt> Vestax: (not-too-ancient preferably)
Apr 29 21:59:15 <zmatt> rvs: lol, this situation is weird
Apr 29 21:59:25 <zmatt> DT actually has a property to describe the fact the timer supports pwm
Apr 29 21:59:35 <zmatt> but afaict it's not used for anything
Apr 29 22:00:11 <zmatt> "FYI this timer supports pwm.  We don't, but the hardware does, just so you know."
Apr 29 22:00:23 <zmatt> time for uio I guess
Apr 29 22:01:43 <zmatt> hmm, that would make a nice simple example
Apr 29 22:01:46 <zmatt> hold on :)
Apr 29 22:03:12 <rvs> :)
Apr 29 22:08:06 <Vestax> Yes my bbb boots debian 7.9
Apr 29 22:09:28 <zmatt> Vestax: at least install a recent kernel (from 4.4-bone series preferably) since you'll need a custom DTB and it's probably easier for me to fix one for you then to explain how to do it
Apr 29 22:13:46 <zmatt> crap I need to hurry for last train, but I'll be back in an hour or so
Apr 29 22:42:35 <Vestax> zmatt: We seem to be in different time zones. It's time for me to get some sleep again.
Apr 29 22:43:53 <Vestax> I won't be here for the next 10 hours or so, but send me instructions on what to do so that I can do as much as possible before having to catch you again
Apr 29 23:05:49 <zmatt> Vestax: I don't really have a particularly fixed sleeping schedule ;)
Apr 29 23:08:30 <zmatt> Vestax: actually, *maybe* it doesn't even need an overlay
Apr 29 23:08:59 <zmatt> you may be able to unbind the mmc driver from the sd card slot pins via sysfs
Apr 29 23:09:27 <zmatt> and then load an overlay to reconfigure them for gpio
Apr 29 23:09:49 <zmatt> but please make sure you have at least kernel 4.1 since I'm not really into archeology
Apr 29 23:10:19 <zmatt> I'll try whether the unbind thing actually works when I'm home (currently still in train)
Apr 29 23:21:54 <Vestax> Well I fucked up something now.
Apr 29 23:22:15 <Vestax> I did sudo apt-get install linux-image-4.4.8-bone10
Apr 29 23:22:20 <Vestax> then reboot
Apr 29 23:22:41 <dsockwell> idk why but those packages don't work too good
Apr 29 23:23:00 <dsockwell> i get the same behavior, i gave up and use the kernel that comes with whatever image
Apr 29 23:23:24 <zmatt> I've never had trouble installing an image like that
Apr 29 23:23:24 <Vestax> I now get /scripts/init-top/udev: line 14: can't create /sys/kernel/uevent_helper: Permission denied
Apr 29 23:23:27 <dsockwell> i suspect that /boot/uEnv.txt is wrong
Apr 29 23:23:28 <zmatt> also on older systems
Apr 29 23:23:32 <zmatt> but brb
Apr 29 23:23:35 <dsockwell> oh
Apr 29 23:23:53 <Vestax> Then I get ALERT!  /dev/disk/by-uuid/53ecdae3-0b2d-422b-980b-cd411c737d3a does not exist.  Dropping to a shell!
Apr 29 23:23:56 <dsockwell> Vestax: disregard what i said please
Apr 29 23:24:18 <dsockwell> although maybe looking in /boot/uEnv.txt for that uuid would be smart
Apr 29 23:24:34 <Vestax> Does anyone know what happened?
Apr 29 23:25:51 <Vestax> When I do ls from initramfs there is no /boot ?
Apr 29 23:26:14 <dsockwell> initramfs does not typically have a /boot
Apr 29 23:26:25 <dsockwell> until after it mounts the root filesystem, and it mounts /boot under that
Apr 29 23:27:13 <dsockwell> you can mount your /boot partition to initramfs if you know the device name, but that's only really good for modifying the files there, it doesn't help your system boot
Apr 29 23:31:05 <Vestax> Can I make the system boot the old kernel from initramfs?
Apr 29 23:42:47 <zmatt> Vestax: just hold on, I just got home
Apr 29 23:43:06 <zmatt> I'm familiar with the situation you've arrived in, it's fixable
Apr 29 23:45:28 <zmatt> Vestax: is the image you installed still old enough to use a boot partition? ls /dev/mmcblk0p*
Apr 29 23:48:01 <zmatt> the error you get indicates a mismatch between your actual filesystem uuid and the one configured in /boot/uEnv.txt and/or /etc/fstab
Apr 29 23:48:40 <zmatt> normally the flasher should make sure those match, but...
Apr 29 23:48:59 <zmatt> (why this suddenly became an issue with upgrading your kernel, I have absolutey no idea)
Apr 29 23:49:52 <dsockwell> possibly my fault, sorry
Apr 29 23:50:34 <zmatt> it's easy enough to fix though, even from initramfs
Apr 29 23:57:22 <Vestax> Yes
Apr 29 23:57:41 <Vestax> ls /dev/mmcblk0*
Apr 29 23:57:41 <Vestax> /dev/mmcblk0       /dev/mmcblk0boot1  /dev/mmcblk0p2
Apr 29 23:57:43 <Vestax> /dev/mmcblk0boot0  /dev/mmcblk0p1
Apr 30 00:04:17 <zmatt>  http://pastebin.com/PsdfceT8  <-- so this is for newer systems that no longer have a boot partition
Apr 30 00:05:36 <zmatt> so I don't reallly have experience with those, but you'll want probably need to grab the uuid of mmcblk0p2 and you'll need to mount /dev/mmcblk0p2 at /mnt and then /dev/mmcblk0p1 at /mnt/boot
Apr 30 00:06:49 <Vestax> How do I get the uuid from initramfs?
Apr 30 00:08:24 <zmatt> I show the command in my pastebin
Apr 30 00:08:52 <zauslande> X15?
Apr 30 00:08:58 <zmatt> bbb
Apr 30 00:09:27 <zauslande> Just wondering if a Mars Landing will predate the Beaglebone X15 release.
Apr 30 00:09:53 <zmatt> Vestax: to verify how to fix it I actually just deliberately mucked up my /boot/uEnv.txt and then made a transcript of me fixing it again ;)
Apr 30 00:10:49 <zmatt> you can probably also just remove/comment the uuid line in uEnv.txt and use /dev/mmcblk0p2 in fstab
Apr 30 00:11:29 <zmatt> that should work fine as long as your sd card slot isn't working anyway
Apr 30 00:13:38 <Vestax> I don't have a uEnv.txt
Apr 30 00:13:52 <Vestax> That seems to be the problem here
Apr 30 00:14:11 <zmatt> you do, somewhere
Apr 30 00:14:26 <zmatt> what's in your fstab?
Apr 30 00:15:28 <Vestax> UUID=53ecdae3-0b2d-422b-980b-cd411c737d3a  /  ext4  noatime,errors=remount-ro  0  1
Apr 30 00:15:40 <Vestax> debugfs  /sys/kernel/debug  debugfs  defaults  0  0
Apr 30 00:16:06 <zmatt> huh, you have a boot partition but no mention of it in your fstab?
Apr 30 00:16:28 <Vestax> seems like it yes
Apr 30 00:16:53 <zmatt> dd skip=256 count=1 if=/dev/mmcblk0 | hexdump -C
Apr 30 00:17:04 <zmatt> does that show something involving CHSETTINGS ?
Apr 30 00:18:17 <zmatt> http://pastebin.com/prvyp2fc  <-- that
Apr 30 00:20:11 <Vestax> Yes exactly like that
Apr 30 00:20:25 <zmatt> you're not using that boot partition at all.
Apr 30 00:20:30 <zmatt> it's dead weight
Apr 30 00:20:41 <Vestax> ok
Apr 30 00:20:54 <Vestax> where is my uEnv.txt then?
Apr 30 00:20:59 <zmatt> if you mounted it, umount it, check again whether you have /boot/uEnv.txt
Apr 30 00:21:08 <Vestax> I just got this board like this from china ;-)
Apr 30 00:21:20 <zmatt> uboot also loads /uEnv.txt but normally there's just backwards compat stuff there
Apr 30 00:22:16 <zmatt> consider reflashing it via usb?
Apr 30 00:23:10 <zmatt> because it looks like you have a really wonky systenm
Apr 30 00:24:45 <Vestax> I umounted eveything and mounted it again
Apr 30 00:24:48 <Vestax> now it's there
Apr 30 00:24:58 <Vestax> I don't know what it was before
Apr 30 00:26:32 <Vestax> According to blkid the id is very short
Apr 30 00:26:37 <Vestax> Is this normal?
Apr 30 00:26:51 <zmatt> no, did you do it on the partition?
Apr 30 00:26:52 <Vestax> UUID="395B-4AC7"
Apr 30 00:26:58 <zmatt> that's more like a FAT thing
Apr 30 00:27:08 <zmatt> try the other partition
Apr 30 00:28:08 <Vestax> Yes you are correct
Apr 30 00:28:20 <Vestax> I just did copy paste from your example
Apr 30 00:28:50 <Vestax> fstab looks ok
Apr 30 00:29:33 <Vestax> and so does uEnv.txt
Apr 30 00:30:45 <Vestax> There is the same UUID in all three places
Apr 30 00:31:01 <Vestax> I really need to go to sleep
Apr 30 00:31:22 <zmatt> but still doesn't boot you mean>?
Apr 30 00:31:29 <Vestax> I will be hanging around here and try to fix this thing tomorrow
Apr 30 00:31:33 <zmatt> maybe that FAT partition is messing up u-boot somehow
Apr 30 00:31:35 <zmatt> but really
Apr 30 00:31:39 <zmatt> reflashing would have been faster
Apr 30 00:32:02 <Vestax> I think I will try and reflash tomorrow
Apr 30 00:32:14 <Vestax> I have the instructions that you gave me yesterday
Apr 30 00:32:21 <zmatt> I just tried unbinding the mmc driver from mmc0 ... that seemed to go okay
Apr 30 00:33:00 <Vestax> I will mount the bbb through usb using the tool I got yesterday and dd a new image to it
Apr 30 00:33:10 <zmatt> and I can export the pins as gpio :D
Apr 30 00:33:21 <Vestax> cool
Apr 30 00:33:42 <Vestax> Good night for now
Apr 30 00:34:15 <zmatt> nite
Apr 30 00:34:43 <zmatt> my show-pins util seems to get slightly confused by it though
Apr 30 00:35:09 <zmatt> still showing it as used by mmc
Apr 30 00:36:41 <zmatt> oh right, I still need to mux 'em over
Apr 30 00:36:45 <zmatt> overlay time
Apr 30 00:40:21 <Soup4you2> finished flashing ubuntu 16.10 to the BBB, must say it's running quite well so far, certainly less bloated than the prefered debian distro.
Apr 30 01:02:22 <rvs> zmatt: I have been digging more about the timer4 and it seems that is a driver problem.  Seee https://e2e.ti.com/support/arm/sitara_arm/f/791/p/421917/1504440
Apr 30 01:03:05 <zmatt> rvs: yes, the absence of a driver... I mean, there's a driver but afaict it only provides timer service internal to the kernel (I didn't inspect in detail though)
Apr 30 01:03:19 <zmatt> it'll make a nice and simple uio example :P
Apr 30 01:04:37 <rvs> zmatt: internal to kernel, like timer1, correct?
Apr 30 01:05:52 <zmatt> yeah, although I doubt the kernel has use for more than four hw timers
Apr 30 01:06:49 <zmatt> my suggestion would be to use the timer directly from userspace ("uio")
Apr 30 01:06:59 <zmatt> and I had already started on an example :)
Apr 30 01:07:36 <rvs> zmatt: wow
Apr 30 01:07:51 <zmatt> I was already working on uio examples
Apr 30 01:08:07 <zmatt> but I never realized the timers had no userspace API
Apr 30 01:08:24 <zmatt> those make an even simpler example than the previous thing I had in mind
Apr 30 01:10:14 <rvs> zmatt: It seems to. As we know, the bbb is a very nice platform and having the ability to use these timers is very desirable.
Apr 30 01:10:45 <zmatt> as well as many other features
Apr 30 01:11:05 <zmatt> like pulse counting / frequency measurement / pulse timestamping
Apr 30 01:11:12 <ds2> do it in the kernel!
Apr 30 01:11:19 <zmatt> ds2: do it yourself!
Apr 30 01:11:25 <zmatt> ds2: nobody did, clearly
Apr 30 01:11:27 <zmatt> for years
Apr 30 01:11:44 <rvs> zmatt: oh yes, the pulse counting is a nice feature for distance sensors, like sonars
Apr 30 01:12:01 <ds2> I do all sorts of stuff in the kernel myself
Apr 30 01:12:24 <zmatt> rvs: for that you probably want pulse timestamping... e.g. sync two eCAP modules and have one generate the pulse and have the other timestamp the response
Apr 30 01:13:29 <rvs> zmatt: That's a good suggestion, thanks!
Apr 30 01:14:19 <rvs> ds2: that's also possible, but would you loose the ability to use PRU ?
Apr 30 01:14:32 <ds2> the McASP/McBSP can do trick like that
Apr 30 01:14:42 <ds2> rvs: nope. I use the PRU too
Apr 30 01:14:49 <zmatt> there are lots of ways to do things
Apr 30 01:14:58 <zmatt> ds2: but PRU bypasses the kernel!!!
Apr 30 01:15:02 <zmatt> how dare you!
Apr 30 01:15:08 <zmatt> :P
Apr 30 01:15:17 <ds2> I'd suggest writing a simple character driver
Apr 30 01:15:22 <ds2> zmatt: not the way I use it :P
Apr 30 01:15:48 <ds2> zmatt: some of the GSoC projects this year are to generate examples on using the PRU from the kernel
Apr 30 01:16:45 <zmatt> well, whatever floats their boat
Apr 30 01:32:43 <zmatt> ok, something is wonky with my kernel or my DT... lots of things keep producing could not find pctldev for node /interrupt-controller@48200000, deferring probe
**** ENDING LOGGING AT Sat Apr 30 02:59:58 2016