**** BEGIN LOGGING AT Sat Mar 05 02:59:58 2016 Mar 05 06:57:56 Hi good morning all !! Mar 05 06:59:34 I have one query on qt5 applications running with yocto project with default kernel. If i change the kernel version qt5 demos are not running in rootfs Mar 05 07:00:16 is there any depency from the kernel ? Mar 05 07:26:00 zmatt: ok, i figured out all the PRU stuff. you *can* use the jtag header/XDS100v2 to step through PRU code as well as see registers, etc Mar 05 07:26:30 zmatt: https://github.com/beagleboard/am335x_pru_package/raw/master/Documentation/04-CCS_PRU_Debugger-training.pdf Mar 05 08:11:24 hey zmatt! Mar 05 08:11:38 we found and fixed our usb babble problem. Mar 05 08:11:59 (really, this time we did.) Mar 05 11:53:55 Hi there. Mar 05 11:54:54 tbr: I flashed my bbb with fresh debian image, like you suggested Mar 05 11:55:01 but still can not connect to it Mar 05 11:55:31 trying 192.168.7.2 as in the documentation, no reply from there Mar 05 11:56:16 can the problem be with the macbook I'm using? it has no ethernet by itself, only wifi Mar 05 12:02:55 so many people on this chan and no one active? Mar 05 12:04:03 join man Mar 05 12:04:11 untitled: you didn't mention last time that you have a mac Mar 05 12:05:00 untitled: the serial console driver should work. If you need the usb network. There should be software for it for OSX Mar 05 12:05:54 untitled: http://beagleboard.org/getting-started#step2 Mar 05 12:06:22 untitled: and as to the "why doesn't someone respond instantly" I can recommend the following: Mar 05 12:06:25 http://www.catb.org/esr/faqs/smart-questions.html Mar 05 12:07:13 I installed the drivers on mac, nothing happened Mar 05 12:07:18 and I'm using linux on it Mar 05 12:07:30 (dualboot), tried both systems Mar 05 12:07:48 which system do you have booted right now? Mar 05 12:07:53 debian Mar 05 12:07:56 ok Mar 05 12:08:11 are you sure the flashing was successful? Mar 05 12:08:18 how did the LEDs behave? Mar 05 12:09:31 according to documentation, yes. I pressed s2, connected usb, leds started to blink in a row, released s2, they blinked for a while, then they went still and finally shut down Mar 05 12:09:50 then I removed sd card, pressed s3 and the board booted Mar 05 12:10:00 now it's blinking heartbeat Mar 05 12:10:20 but no indication of processor activity whatsoever Mar 05 12:11:15 usr2 led should show that, as I understand Mar 05 12:11:34 btw, I'm using bbb rev a5a, if it's important Mar 05 12:12:35 and you used a 2GB flasher image? Mar 05 12:12:57 because the 4GB flasher images obviously won't work Mar 05 12:14:19 and flashed it with this https://rcn-ee.com/rootfs/2016-02-11/flasher/BBB-eMMC-flasher-debian-8.3-console-armhf-2016-02-11-2gb.img.xz Mar 05 12:14:45 http://elinux.org/BeagleBoardDebian#Flasher Mar 05 12:20:02 that says 2GB Mar 05 12:20:17 yep Mar 05 12:20:26 how long did you leave it on when you rebooted it after flashing? Mar 05 12:20:43 it takes about 5-10min to configure itself and doesn't show up on usb during that time Mar 05 12:20:50 if you interrupt that, you need to reflash Mar 05 12:21:04 hm Mar 05 12:21:13 I'm not sure Mar 05 12:21:28 well, the usb was plugged in all the time Mar 05 12:21:29 so Mar 05 12:22:27 btw, I'm not getting any indications, that the board was plugged in Mar 05 12:22:41 not in dmesg, not in /dev, not anywhere Mar 05 12:23:16 lines appear in dmesg when I plug in another development board from TI Mar 05 12:23:31 and it's just a bare metal thing, there is nothing on it Mar 05 12:23:39 maybe this one is just broken... Mar 05 12:24:42 bbb uart 1,2,3,4 are not working Mar 05 12:32:38 untitled: maybe try a different USB cable, just in case? Mar 05 12:33:04 untitled: do you have a USB-to-UART adapter? if not, get one, they are dirt cheap Mar 05 12:36:12 no I don't, ok I'll get one Mar 05 12:43:04 tbr: silly quistion: what do I do with usb-to-uart cable? :) Mar 05 12:43:19 or adapter... Mar 05 12:44:22 untitled: you plug it into the debug UART port on the BBB and then have direct console level access to the board Mar 05 12:44:29 very helpful for trouble-shooting Mar 05 12:44:48 mm alright Mar 05 16:04:16 kremlin: I mentioned that of course you *can* ... but PRU's core/debug controls are just memory-mapped registers (that afaik do not take special meaning to the MReqDebug-bit of interconnect messages) so the debugger would effectively just be doing memory accesses similar to (but much much much slower) than what a debugger running on the cortex-a8 could do Mar 05 16:06:34 yates: do tell! Mar 05 16:09:17 kremlin: the PRU cores do have core control registers in ICEPick, but I'm not sure what purpose they serve since TI did a really shoddy job at integrating ICEPick and PRCM on the AM335x Mar 05 16:38:22 how to reduce interrupt latency in beaglebone black ? Mar 05 17:10:11 by increasing your patience to wait for an answer :P Mar 05 17:27:22 hi, how I can check if original debian distro for beaglebone blk rev. c see my lcd 2x16 lcm1602 ? Mar 05 17:27:47 I'm issueing i2cdetect -r 0,1 and I doesn't see 0x27 address Mar 05 17:28:58 what addresses are seen on the i2c bus? Mar 05 17:29:54 GenTooMan: http://pastebin.com/YqCg1Db1 Mar 05 17:30:26 sda,scl P.9 11, P.9 12 Mar 05 17:44:29 ok, now works. I should have connected to the correct ports 19,20 Mar 05 17:59:32 Hello, does anyone know if there are plans for a newer BBB? Mar 05 22:10:43 hey folks, we found our usb babble interrupt problem. Mar 05 22:11:58 zmatt: i really wanted to get back to you on this and get closure since you spent so much time with me on it. Mar 05 22:12:17 as well as others.. Mar 05 22:12:51 ah - just saw "Do tell!" Mar 05 22:12:55 a few hours back. Mar 05 22:13:41 i'm goign to write it up and post a link Mar 05 22:17:30 in a nutshell, it was hardware. Mar 05 22:18:05 there was a regulator generating a lot of noise in certain scenarios. Mar 05 22:18:21 i'll post the link in awhile which will have more details. Mar 06 02:47:53 http://galois.digitalsignallabs.com/babble-solution.htm Mar 06 02:55:58 zmatt: you there? **** ENDING LOGGING AT Sun Mar 06 02:59:57 2016