**** BEGIN LOGGING AT Tue Oct 31 03:00:03 2017 Oct 31 07:04:04 hi, has anyone tried to use the EQEP driver? Oct 31 07:05:27 the reason I ask is that I hooked everything up to a HEDS-5000 encoder, and the position is stuck at -1 or 2 Oct 31 07:06:04 however, if I use /dev/mem to write '0' to 0x00000000483021a8, then it starts counting properly Oct 31 07:06:14 so I suspect it's some ugly initializatrion bug Oct 31 08:03:06 does anyone know how to use a ninja block? Oct 31 13:05:38 didn't they go bust? Oct 31 14:58:50 Hello. Is there anyone who have a not displaying GUI on monitor after installing java and apt-get update? Oct 31 16:20:14 ew, you mean the oracle java runtime? why would you install that? Oct 31 16:40:18 Anyone using the BBGW? Oct 31 16:45:12 tip: doing a poll on what device(s) people use will rarely get you any reply Oct 31 20:56:34 Help Oct 31 20:56:55 I need to add gps to the beaglebone blue Oct 31 20:57:04 whats my option Oct 31 20:58:33 hi Oct 31 20:58:58 i need to add a gps to beaglebone blue Oct 31 21:17:39 seizures? Oct 31 21:19:25 Nobody? Oct 31 21:20:21 What about seizures? Oct 31 21:22:37 After they happen, is the dog suppose act strange like pissing every where & not know where they're at? Oct 31 21:29:25 ?? Oct 31 21:36:00 hah Nov 01 00:22:08 Anybody here familiar with the new method of loading capes? Tried loading the CAN driver putting it in /boot/uEnv.txt in slot4 but checking dmesg the only capemgr line was at 0.00000 Nov 01 00:23:44 Looked at the official documentation and various guides and I'm doing everything in them but not getting results. Nov 01 00:23:50 can you pastebin the contents of your /boot/uEnv.txt ? Nov 01 00:24:01 Yeah one sec Nov 01 00:27:17 https://pastebin.com/JVr005Cf Nov 01 00:27:48 Oh wait Nov 01 00:28:21 uboot_overlay_addr4 was uncommented with the error Nov 01 00:28:30 I commented it out to try another solution which didn't work either Nov 01 00:28:31 yeah I guessed that :) Nov 01 00:28:49 Tried it at addr1 and addr4 and neither showed up in dmesg log Nov 01 00:28:57 so, u-boot overlays mean the overlay is already being applied to the device tree before it is passed to the kernel Nov 01 00:29:24 so as far as the kernel is concerned there isn't any overlay Nov 01 00:29:42 that's why you won't see any messages about it in the kernel log Nov 01 00:29:45 Ah Nov 01 00:30:20 So that isn't the error then I guess... Nov 01 00:30:28 Been fighting with CAN on this thing for weeks now Nov 01 00:30:51 so, is CAN not available via cape-universal? (I've never checked) Nov 01 00:31:24 if it isn't, and an overlay is indeed required, then you may need to disable cape-universal entirely Nov 01 00:31:41 I'll give that a try Nov 01 00:31:54 I think it defaults to a pwm or UART pin Nov 01 00:32:04 all pins default to gpio Nov 01 00:32:55 I meant whether pins can be configured to CAN using config-pin when using cape-universal Nov 01 00:33:59 They're on p9.24/26 which don't appear to be used in cape-universal? I'll try disabling that and see if it works though Nov 01 00:34:48 cape-universal occupies all pins not already used for special functions like eMMC and HDMI (when applicable and enabled) Nov 01 00:35:01 that's why it conflicts with nearly every overlay Nov 01 00:35:20 but it's meant to make overlays unnecessary in most cases since you can select the pin function at runtime Nov 01 00:35:41 Ah Nov 01 00:36:01 I was used to using the slots overlay still. Tried using that for a while but still had errors so decided to try the new kernel Nov 01 00:36:14 And since this is fairly new it's not nearly as well documented as the older method Nov 01 00:37:03 first try leaving cape-universal enabled and see if you can do something like config-pin P9.24 can (and ditto for P9.26) Nov 01 00:41:18 zmatt: that's in the dts file, uEnv or somewhere else? Nov 01 00:41:24 no Nov 01 00:41:27 commandline Nov 01 00:41:31 sudo Nov 01 00:41:41 Oh Nov 01 00:52:32 P9_24 pinmux file not found! Nov 01 00:52:42 bash: /sys/devices/platform/ocp/ocp*P9_24_pinmux/state: No such file or directory Nov 01 00:52:48 Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_24_pinmux/state Nov 01 00:54:09 that's odd, you're sure that you left cape-universal enabled? (and that CAN overlay disabled) Nov 01 00:56:41 Oh Nov 01 00:56:49 The CAN overlay was still enabled Nov 01 01:00:29 [ 77.656743] c_can_platform 481cc000.can can0: setting BTR=1c02 BRPE=0000 Nov 01 01:00:31 So that's new Nov 01 01:05:17 So still having issues with CAN but don't have an oscope to check the other parts of the circuit... Will have to wait until the morning Nov 01 01:05:25 Thanks for your help zmatt though, I really appreciate it. Nov 01 01:05:30 you're welcome :) **** ENDING LOGGING AT Wed Nov 01 03:00:01 2017