**** BEGIN LOGGING AT Wed May 03 03:00:01 2017 May 03 04:44:01 hi May 03 04:44:40 hi May 03 06:13:13 Goodmorning May 03 06:26:42 Is there anyone who could help me out with edge detection gpio? May 03 06:38:46 hello guys May 03 06:39:41 Anyone experiented with interrupt beaglebone? May 03 06:51:16 zmatt !!! Found my interrupt problem!!!! Software hasnt seek() after poll() May 03 06:51:29 Thats why I get thousends of interrerupts on all pins May 03 06:51:45 Older imgs hasnt this problem, but recent has May 03 07:19:15 that's odd, I don't seek after poll either (I implicitly seek before reading by using pread()) and I haven't seen the problem May 03 07:19:28 I use epoll rather than poll though May 03 07:20:27 maybe that makes a difference since epoll is stateful (remembers which events of which file descriptors to watch) while poll is not May 03 07:22:09 ohh, you didn't read at all after getting the event? May 03 07:24:48 when polling sysfs attributes, you're expected to start polling it after having read the attribute May 03 07:26:19 when you get POLLPRI you're supposed to read it again (seek to 0 and read, or combine the two by using pread) before polling again May 03 07:30:31 the documentation for the sysfs gpio interface ( https://www.kernel.org/doc/Documentation/gpio/sysfs.txt ) documents this explicitly May 03 08:13:12 zmatt Yes I did read May 03 08:13:33 Piece of code I got from a formal colleague May 03 08:14:01 But strange fact is that the same software hasnt problems running on a 3.8 Amstrong image May 03 08:14:14 But it does on the new 8.6 Debian image from bb.org May 03 08:14:37 Is epoll a better option over poll then? May 03 08:15:36 I've now an stable version where 6inputs has a testpuls_count:detected ratio = 1.00 :):) May 03 08:16:01 Now cloned eMMC to SD ... so all newer bb's get an updated IMG with working config May 03 08:16:26 which one is better (poll vs epoll) depends on the application I guess, and might be a matter of taste May 03 08:16:38 poll is simpler to use May 03 08:17:02 anyway, no idea why it worked on 3.8, that might simply have been a bug May 03 08:17:41 Yes I think... because I did a lot of software updates except the ISR / POL part... May 03 08:21:09 open; loop { read; ...do stuff..; wait for POLLPRI; seek to 0; } is the outline of using sysfs notification May 03 08:21:34 optionally the seek might be moved to the front of the loop instead May 03 08:21:49 or simpler, May 03 08:21:58 open; loop { pread; ...do stuff..; wait for POLLPRI; } May 03 08:22:19 at least I think that's equivalent May 03 08:22:34 it works for me anyway :P May 03 08:23:49 hmm, okay, now that I think about it I'm actually not sure anymore... separate seek and read is the safe option May 03 08:23:59 anyway, I'm off May 03 08:24:02 I'm a beginner for BBB May 03 08:24:14 and I need some help May 03 08:24:18 who can help me? May 03 08:35:35 noone if you don't actually ask a question May 03 08:36:02 (and have patience since people are in different timezones and often only occasionally glance at the chat) May 03 09:14:21 my user leds are not flashing stable May 03 09:16:21 I wrote an uSD card with the latest eMMC flash images. And when I started my bbb with the uSD my some leds are flashing but not frequently and stable. After 2 or 3 mins LED 1 and LED 2 stay steady position. May 03 09:20:58 have you had a look at the serial console? May 03 10:22:31 *sigh* May 03 10:33:52 ? May 03 11:01:12 hello May 03 11:01:18 I've a problem with my BBB May 03 11:02:27 I'm a beginner and I want to use the latest images with my BBB. When I tried to flashing from uSD card, my leds are flashing unstable. After 3 or 4 minutes LED 1 and LED 2 stay solid. May 03 11:02:47 tuna: which image are you using for this? May 03 11:02:47 After that I power off my BBB and remove SD card and Power on May 03 11:03:29 Debian 7.5 (BeagleBone Black - 2GB eMMC) 2014-05-14 - May 03 11:03:31 this onr May 03 11:03:46 that's rather ancient May 03 11:04:32 My BBB is also ancient May 03 11:04:40 http://beagleboard.org/latest-images May 03 11:04:46 I've bought it two years ago May 03 11:05:49 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#microSD.2FStandalone:_.28lxqt-2gb.29_.28All_BeagleBone_Variants.29 May 03 11:15:01 I'm trying with the latest image at the moment May 03 11:15:07 I'm preparing my uSD card May 03 11:15:19 for Debian 8.7 2017-03-19 4GB SD IoT image May 03 11:18:26 which revision BBB do you have? May 03 11:18:35 B4 May 03 11:18:36 4GB will only work with a RevC model! May 03 11:18:42 ok, that will not work May 03 11:18:53 you must use a 2GB or smaller image May 03 11:19:28 why not https://rcn-ee.com/rootfs/bb.org/testing/2017-04-30/lxqt-2gb/bone-debian-8.7-lxqt-2gb-armhf-2017-04-30-2gb.img.xz ? May 03 11:20:23 ok, i can try it May 03 11:20:35 I'm downloading at the moment May 03 11:20:56 is it an eMMC flash image? May 03 11:20:59 4GB in an image name means it might not work on your device. May 03 11:21:13 no. there are instructions how to enable that here: http://beagleboard.org/latest-images May 03 11:21:32 ok, but can it work over uSD card May 03 11:21:33 "To turn these images into eMMC flasher images, edit the /boot/uEnv.txt file on the Linux partition on the microSD card and remove the '#' on the line with 'cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh'. Enabling this will cause booting the microSD card to flash the eMMC. Images are no longer provided here for this to avoid people accidentally overwriting their eMMC flash." May 03 11:22:35 or, just download a flasher image May 03 11:22:51 no i can do it, it's not a problem May 03 11:23:13 B4 ? there's no such revision afaik? May 03 11:23:53 there's definitely no such board revision May 03 11:24:45 B4 can be the PCB Rev May 03 11:25:04 hmm May 03 11:25:43 I've found only the rev on my board May 03 11:27:02 I can't find how pcb revs correspond to bbb revs, except that the latest pcb revision is apparently B6, so yours is not-latest, therefore not 4GB May 03 11:28:02 thanks for the useful info. I've been searching my real rev. number :D May 03 11:28:18 you can read it from eeprom May 03 11:28:32 how can i acces to eeprom? May 03 11:28:36 over serial port May 03 11:29:17 I think it might be in an u-boot env var, or if not then there's an u-boot command to read eeprom May 03 11:30:23 but i can't connect to my bbb at the moment May 03 11:30:46 but you have a serial cable right? May 03 11:31:17 or, just wait until you've reflashed it, then you can simply read it via sysfs May 03 11:31:31 yes i have a serial cable May 03 11:34:00 tuna: it's rude to private message people without being asked to May 03 11:34:55 if for some reason you want to know the bbb revision without booting into linux, you can just break into u-boot and use... I think: i2c md 50 0c 4 May 03 11:35:46 actually it might be i2c md 50.2 0c 4 May 03 11:35:58 something like that May 03 11:36:11 tuna: also, how would me make fun of you struggling when you hide it all in private msg :-) May 03 11:37:18 btw, I'm pretty sure you can shrink the IoT images to fit 2GB... I really don't understand why rcn makes those 4GB May 03 11:46:50 thank you so much zmatt and tbr May 03 15:44:21 hi.. May 03 15:49:52 hi guys May 03 15:52:13 hi rthille May 03 16:03:08 Iam not able to make a bootable sd card for beaglebone blue. The sd card is not turning into bootable for debian 8.6 IOT & LXQT images. After burn the sd card using win32 disk it is showing FAT32 but not the beaglebone dog image. I have tried debian 8.6 iot,lxqt and 8.7 iot &lxqt. For debian 7.5 it is changing into bootable. Is that FAT32 means the sd card is ready to boot? but that is also not happening.. I struck in this pro May 03 18:57:34 what instructions are you following? can you post the link? May 03 19:08:49 . May 03 19:11:27 . May 04 00:59:12 If I needed to switch the NODE_PATH=/ to another section and I cannot use export, does mv take its place on the BBB? May 04 01:04:58 I know it does not. I tried. Forget that question. May 04 01:05:01 Just forget it. May 04 01:05:06 << on break! **** ENDING LOGGING AT Thu May 04 03:00:03 2017