**** BEGIN LOGGING AT Sun Feb 14 02:59:58 2016 Feb 14 03:01:35 yates: maybe I'm wrong about the vbus being strictly required, but that was my impression and I have seen ports go down due to vbus dipping Feb 14 04:06:10 zmatt: i was wrong - we do. Feb 14 04:06:25 it was on another schematic page instead of the one with the rest of the usb signals. Feb 14 06:31:21 Adding this "optargs=capemgr.enable_partno=BB-SPI0" in the uEnv.txt not loading SPI0 device tree when BBB reboots. Any suggestions? Feb 14 06:31:54 which image are you using? Feb 14 06:32:08 debian wheezy 7 Feb 14 06:32:24 which kernel version does your image have? Feb 14 06:33:11 let me cross check. brb Feb 14 06:36:20 Its 3.8.13-bone70 Feb 14 06:36:38 Debian GNU/Linux 7.9 (wheezy) Feb 14 06:40:54 then that stuff should work Feb 14 06:40:59 make sure you follow instructions Feb 14 06:43:32 K kool. Il look into it Feb 14 08:09:21 how to use urat Feb 14 08:17:39 Im in the early stages of designing capes for the X15. Are there any guidelines for that yet, like EEPROM needs to be on these pins, etc? Feb 14 09:21:16 zmatt: it's working, no more babble interrupts Feb 14 09:21:27 what did i change? NOTHING!!!!! Feb 14 09:21:46 * yates gets gagged and bound for the asylum Feb 14 09:57:16 hi Feb 14 09:57:33 can anyone answer my question? Feb 14 09:58:20 you haven't asked yet, so no. Feb 14 10:02:43 ok.. what's the difference/relationship between omap3 and am335x? Feb 14 10:03:46 both are made by TI Feb 14 10:04:10 so is a beaglebone black using omap3 or am335x? Feb 14 10:04:20 am335x Feb 14 10:04:45 also both have an ARMv7 core at their heart Feb 14 10:05:10 but peripherals and auxiliaries are quite different Feb 14 10:05:45 when i read tutorials about u-boot, they tell me to build config with omap3. Do you know why? Feb 14 10:06:13 as far as u-boot is concerned, they are probably fairly similar Feb 14 10:08:35 an older version of beaglebone used omap3? Feb 14 11:12:06 can anyone help me to u-boot? I have a MLO and u-boot.img in a sdcard but LEDs don't flash Feb 14 12:08:11 jay_: do you have access to the debug UART? Feb 14 12:12:06 no i have only rs232-to-usb so cant debug using uart.. Feb 14 12:15:23 I wouldn't attempt to do any boot-loader work without UART access Feb 14 12:15:33 get one, they are really cheap Feb 14 12:18:47 okay ill. does default uboot for beaglebone init hdmi? Feb 14 12:18:55 no Feb 14 12:20:56 so i have to code them to init? Feb 14 12:21:22 or is there a config setting? Feb 14 12:22:25 the linux kernel does set up HDMI Feb 14 12:23:32 what are you trying to do anyway? Feb 14 14:25:27 yates: don't worry, it'll probably be back at some inconvenient moment Feb 14 14:27:08 tbr: "as far as u-boot is concerned, they are probably fairly similar" -> no. Feb 14 14:28:46 zmatt: k Feb 14 14:30:31 different interconnects, control module, prcm registers, clock tree, memory controller Feb 14 14:32:02 apart from both having a cortex-a8 and a couple of similar peripherals they really have little in common Feb 14 15:02:41 what does this kernel message mean? Feb 14 08:56:40 arm kernel: [ 4.456712] 47401300.usb-phy supply vcc not found, using dummy regulator Feb 14 15:03:04 kernel being unduly fussy Feb 14 15:03:21 to be ignored? Feb 14 15:04:03 yup. it can also be quenched by conjuring up a bullshit fixed-regulator to specify in DT Feb 14 15:06:31 for some reason the kernel demands to know the power supply topology and complains about not knowing it in various cases even though there may not be anything useful it can do with that info Feb 14 15:08:39 interesting. Feb 14 15:28:17 Hi all :) Feb 14 15:28:39 Is somebody easy with PRU ? Feb 14 17:21:31 Should /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux.pins reflect any overlays added via cape manager? (/sys/devices/platform/bone_capemgr/slots) Feb 14 17:38:13 yes Feb 14 17:39:20 I also wrote a script that formats the data more legibly http://gerbil.xs4all.nl/show-pins-v2.pl.gz (I think rcn-ee also includes it in the latest images but I'm not sure where) Feb 14 17:54:24 Thanks. Not having any luck with getting encoders registering movement and even tho the dts compiles and loads fine, I'm not seeing a change in the pin voltage when inverted, so I suspect something else is up. The pins do not seem to be updated. Thanks for the script too. Feb 14 18:00:48 you're welcome. the script isn't heavily tested against different kernels or in the face of overlays, though I've written it to fail hard if it encounters anything it can't parse (to avoid displaying nonsense), so if you run into any trouble with it let me know so I can fix it :) Feb 14 18:29:30 @zmatt: superfancy colors and all. Definitely nothing appearing to be assigned to eqep/pwm. Thanks again. Feb 15 00:18:20 the "1" here means usb1, right? Feb 14 23:33:48 arm kernel: [ 90.966211] musb-hdrc musb-hdrc.1.auto: Babble Feb 15 00:30:08 yates: that would be my guess as well, though the next question would be whether it's 0-based or 1-based :P Feb 15 01:03:18 yeah. Feb 15 01:38:23 ???: Feb 14 23:32:43 arm kernel: [ 0.089359] Yama: becoming mindful. Feb 15 01:39:41 of what? Feb 15 01:45:26 lmao Feb 15 01:52:50 is there a way for a process running as root to emit messages into the kernel log (/var/log/kern.log)? Feb 15 01:53:18 i saw echo msg > /dev/kmsg, but that seems only to output to dmesg and not /var/log/kern.log Feb 15 01:53:44 it can be a C function call as well, not just echo. Feb 15 01:54:00 i need to mark the time my process is doing something. Feb 15 01:57:40 abuse syslog?! :P Feb 15 01:58:22 yates: normally you'd log to joural (e.g. use systemd-cat or run your process as service and write to stdout/stderr) Feb 15 02:00:26 ah ofc .. everythingd .. forgot .. >< Feb 15 02:01:23 sysctl enable systemd-pour-my-tea-and-bring-it-here Feb 15 02:01:30 ahh Feb 15 02:02:13 note my deliberate mistake :D Feb 15 02:08:47 zmatt: i want to see when things happen relative to, e.g., the kernel network messages, during systemd init Feb 15 02:08:50 * zmatt generally purges rsyslog and configures journald to keep journal in ram only Feb 15 02:09:01 yates: both end up in journal Feb 15 02:09:17 meh. Feb 15 02:09:24 zmatt: and when it locks up?! Feb 15 02:09:28 i don't like the journal. Feb 15 02:09:41 jtag the ram I assume ;P Feb 15 02:09:45 you mean the systemd journal? Feb 15 02:10:01 veremit: then generally the problem wouldn't be written to eMMC either :P Feb 15 02:10:18 zmatt: heh Feb 15 02:11:13 veremit: of course if necessary it's easy enough to enable logging to eMMC, some other storage, or network Feb 15 02:12:06 it would be even more useful to take advantage of the fact that if you configure the am335x right then external RAM stays intact across resets (except POR) Feb 15 02:12:46 so in-ram journal or log could actually be the most reliable way to preserve the last messages before the watchdog kicks in Feb 15 02:12:56 alas such a thing has not (yet) been implemented Feb 15 02:13:29 hmm Feb 15 02:14:02 externam ram - does it keep getting clocks or whatever it needs .. its not sram is it? Feb 15 02:15:04 when a warm reset is asserted PRCM first notifies EMIF which then puts the RAM into self-refresh mode before notifying PRCM it can go ahead and reset the chip Feb 15 02:15:27 while in self-refresh no clock is required Feb 15 02:17:23 it does mean you have to suppress the reset signal to the RAM by setting a particular (reset-insensitive) bit in the control module, and you need to be a bit careful with the procedure to reenable RAM... I don't think u-boot does either Feb 15 02:17:51 hmm interesting .. you should try that some time ;P Feb 15 02:17:59 I probably will **** ENDING LOGGING AT Mon Feb 15 02:59:59 2016