**** BEGIN LOGGING AT Mon Feb 15 02:59:59 2016 Feb 15 03:23:36 hey guys Feb 15 03:24:19 i'm stuck on how to get LED's to blink using PRU. Feb 15 03:24:55 I can get the PRU to work in one case (which is to wait 5 secs) and go back to C program then it works Feb 15 03:25:04 but when I try to do with with flashing LEDs it doesn't work Feb 15 06:19:19 i need to reset BBB in factry setting Feb 15 06:52:01 get a flasher SD card image Feb 15 06:53:14 http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03 Feb 15 06:53:27 choose base on which hardware revision you have Feb 15 09:14:31 hello, i am new to open souce and want to contribute.Can anyone help me where to get started Feb 15 09:16:25 anyone here??? Feb 15 09:20:23 can anybody help me please????? Feb 15 09:42:23 Hello. I have question. I am flashing eMMC beagleboard. On monitor i can see beagleboard.org image. and USR0 D is blinking. Is it normal? Feb 15 09:46:22 alexx600: probably. which image are you using? Feb 15 09:52:06 I use angrstrom dist. Only this is available to BeagleBoard Feb 15 10:04:04 so which board are you flashing? Feb 15 10:10:14 BeagleBoard rev C5. It tooks ~40 min already Feb 15 10:14:47 can i factory reset my beagle without having to install a system firmware? Feb 15 10:19:49 ? Feb 15 10:20:01 you can flash a fresh Debian install Feb 15 10:20:06 thats as factory as itgets Feb 15 10:30:03 How can i change my IP Address? Feb 15 10:58:34 dabbaspanda: IP of what? Feb 15 11:00:38 dabbaspanda: you are probably misinterpreting factory reset with your phone factory reset. Doesn't work like that in BB Feb 15 11:09:14 ordered my first beagle yesterday! Feb 15 11:09:16 yay Feb 15 11:09:18 BBB Feb 15 11:09:43 looking forward to playing with it, and just popped in to check out the community :) Feb 15 11:10:04 IP4 address... i want to remotely control my BB by using putty but i cant find it on my domain so i want to change it Feb 15 11:10:59 how can i change my IP4 Address Feb 15 11:16:46 my beagleBoard does't boot yet Feb 15 11:16:46 something is wrong Feb 15 11:55:44 Maybe someone know how proper flash in BeagleBoard should run? onlu USR0 D should blink or something else? Feb 15 11:56:22 bb classic is really old. Feb 15 11:57:11 most people had problems with its NAND. You should consider to just use a SD-card Feb 15 11:58:49 What do you mean exactly ? Feb 15 11:59:49 my sd card is not compatible? Feb 15 12:00:56 another question is ?from wiki http://elinux.org/Beagleboard:BeagleBoard20. Hold the button for 10 seconds and then release it. 21. The SW will automatically flash the NAND. Feb 15 12:01:03 what is SW ? Feb 15 12:02:48 SW stands for SoftWare Feb 15 12:02:54 This wiki shows how to write image on card (trivial), and doesn't say anything aboud diodes that blinks Feb 15 12:05:14 I guess the diode blinking pattern /might/ change Feb 15 12:05:31 also if you have a DVI screen connected you might see something there Feb 15 12:05:50 also if you connect to the debug UART port you might be able to get some information Feb 15 12:06:16 also, I would guess the flashing won't take longer than 15-20min. Feb 15 12:06:36 after that and maybe after waiting a few more minutes, I'd just remove the SD and reboot the board Feb 15 12:08:24 i do not have uart2usb converter. My monitor DVI does't show anything except beaglebone image. No progress bar. Another monitor doesn't show anything Feb 15 12:29:57 the bb classic uses rs232c levels, so a simple serial cable or a usb2serial converter will do. Feb 15 12:30:00 http://elinux.org/BeagleBoardBeginners#Setting_up_serial_connection_between_your_desktop_machine_and_the_BeagleBoard Feb 15 12:30:21 without serial access, I wouldn't want to get into embedded device work Feb 15 13:54:02 found the 4th (or maybe 5th) bbb from embest with problems on uSD. can't boot at all, and cannot mount it if inserted after booting the stock system. anyone else experienced similar problems? Feb 15 13:54:25 (i mean, can't boot from uSD) Feb 15 14:42:53 Jason, are you here? Feb 15 14:44:37 Hello All, I'm trying to apply patch as it shown here: http://processors.wiki.ti.com/index.php/AM437x_Linux_PRU_Driver Feb 15 14:45:32 But after I run "git am , I get the error message sayong that patch file is empty. What is wrong here? Feb 15 14:45:59 What do you get from "file " ? Feb 15 14:47:12 HTML document, ASCII text, with very long lines Feb 15 15:01:27 how do I boot u-boot on qemu ? Feb 15 15:34:41 owl-v-: http://bfy.tw/4Gmc (since you didn't specify any particular hardware to simulate, the first google hit already meets your request) Feb 15 15:34:55 Hello, any suggestions on getting the patch working? Feb 15 15:36:37 Ilya_C: you need to save the raw content of the patch (use "Raw blob data"), not the HTML page Feb 15 15:37:41 pretty dumb they didn't link to the raw patch in the first place Feb 15 15:37:52 I'm using already prepared file *.patch that I downloaded. How can I convert it to raw blob data? Feb 15 15:39:07 the link, even though it ends in .patch, isn't the raw patch but a webpage (just click it) Feb 15 15:39:11 zmatt: I get error -> http://pastebin.com/cQku26Jn Feb 15 15:40:03 owl-v-: there's no qemu version that is able to simulate the am335x Feb 15 15:40:35 zmatt: what about cheetah? it's omap3 Feb 15 15:40:54 according to the first line you compiled u-boot for am335x Feb 15 15:41:22 ok, get it done, thanks Feb 15 15:42:17 owl-v-: also, cheetah is omap1, not omap3 Feb 15 15:42:53 zmatt: sx1 also omap1 ? Feb 15 15:43:10 the linaro branch of qemu apparently supports the beagle (original beagleboard) and beagle-xm Feb 15 15:43:35 again, google, first hit on cheetah + qemu -> https://lists.nongnu.org/archive/html/qemu-devel/2011-05/msg03292.html Feb 15 15:44:18 5 minutes ago i had never heard of the board yet I could easily find that it wasn't omap3... please perform a search yourself first Feb 15 15:46:50 linaro also has a page on booting up a simulated beagle in qemu -> https://wiki.linaro.org/Resources/HowTo/Qemu-beagleboard Feb 15 15:47:28 though it may be outdated Feb 15 15:49:13 (plenty of other helpful pages show up in a search however) Feb 15 15:49:30 zmatt: this is linaro version of emu. I have this error "GLib-WARNING **: gmem.c:482: custom memory allocation vtable not supported" -> http://pastebin.com/q5hJhM8K Feb 15 15:50:27 again, according to the first line you're trying to boot an u-boot compiled for am335x Feb 15 15:50:30 that's the wrong cpu Feb 15 15:50:36 of course it will crash Feb 15 15:51:13 Hi, i have a question about the Beaglebone Black or Green clonning. I hope somebody could help me because I haven't found any solution. I'm working in an internship for a company which need to create is own board because developent board that they currently use have useless features. So, to create this new board, I would like to use the Beaglebone Black or Green schematics to create a kind of clone. My question is: if I use those Feb 15 15:51:50 is designed to be commercialezed, the company could keep the scheme for her or will she be forced to share it ? Feb 15 15:56:26 zmatt: how do I target beagle-bone? I don't see am335x board Feb 15 15:58:29 16:40 < zmatt> owl-v-: there's no qemu version that is able to simulate the am335x Feb 15 15:59:01 am335x support has not been implemented in qemu by anyone as far as I know Feb 15 16:00:00 (although occasionally people who up with a desire for it so maybe someone's given it a try, but it would be a lot of work to simulate it to a sufficient degree to have any hope of being able to run u-boot let alone linux) Feb 15 16:01:25 afk Feb 15 16:44:15 i have trouble flashing the newest img to my bbb. i downloaded the debian 8.3 img. from http://beagleboard.org/latest-images. sha256sum: da97d7794d834ee785265162635aedcca80fd6dc374593dd05473c0a25f0ac73 . then followed the instruction and changed the /boot/uEnv.txt. once the flashing is complete i take out the microSD card. and restarts my BBB, but it is stuck on the screen " staring emmc flasher from microSD card.... " if i insert Feb 15 16:44:36 it is able to boot from my microSD. but i want to write to my eMMC, not my microSD Feb 15 16:45:02 I have a question Feb 15 16:45:09 About beagle bone black Feb 15 16:45:23 we want to do a proyect and do a small Feb 15 16:45:32 modification to the pcb Feb 15 16:45:37 its possible that Feb 15 16:46:42 pablo_: are you asking whether it's possible for you to do a small modification to the PCB? Feb 15 16:47:09 I mean we want to create our own pcb Feb 15 16:47:12 based on BBB Feb 15 16:47:21 pablo_: what is your question? Feb 15 16:47:23 but I am not sure is that is rigth Feb 15 16:47:43 We want to start a new pcb design of a small computer based on the current BBB Feb 15 16:47:58 gl Feb 15 16:48:09 with some additional features and sligthy difference on the debian distribution Feb 15 16:48:18 pablo_: OK, what is your question? Feb 15 16:48:26 my question is about licenses; copyrigths; etc Feb 15 16:48:39 pablo_: OK, what is your question? :-) Feb 15 16:48:49 My question it is aloud to do that? Feb 15 16:49:06 without have problems with licenses and copyrigthd Feb 15 16:50:18 Do you understand me? Feb 15 16:51:39 lifosuck, so the procedure for flashing -> dd *.img to microSD, insert microSD into bbb, let it "flash" the eMMC... PowerOff/Take out microSD, image is now on eMMC... Feb 15 16:51:45 lifosuck, what did you actually do? Feb 15 16:52:25 hello rah Feb 15 16:53:18 someone knows about copyrigths Feb 15 16:53:36 pablo_, debian has a few pages explaining it.. give me a moment.. Feb 15 16:53:42 that's exactly what i did Feb 15 16:54:10 ok; I just want to be sure I am not breacking any law or rule Feb 15 16:54:24 i wrote the img to microSD, inserted microSD to bbb, "let it flash" <-- this part when i held the boot button and plug in power Feb 15 16:54:28 nothing happens Feb 15 16:54:43 using the BBB as a based design Feb 15 16:54:59 so i had to change /boot/uEnv.txt Feb 15 16:55:18 pablo_, the gist, packages have their copyrights, as long as meet those requirements, your fine. (assuming you have your application copyrights correct) Feb 15 16:55:53 but its no about packages; my questions is about the PCB design ... hardware Feb 15 16:56:00 lifosuck, kinda sounds like you changed the /boot/uEnv.txt on the "emmc".. Feb 15 16:56:02 which it already designed Feb 15 16:56:02 hmmmm. maybe because i changed the /boot/uEnv.txt on my BBB, and not on the partition on microSD Feb 15 16:56:07 yes... Feb 15 16:56:08 lol Feb 15 16:56:12 my bad. Feb 15 16:56:32 which means, it will always look for a flasher img on boot up Feb 15 16:56:37 i am guessing.. Feb 15 16:57:19 lifosuck, save you some trouble: https://rcn-ee.net/rootfs/bb.org/testing/2016-01-24/lxqt-4gb/BBB-eMMC-flasher-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz Feb 15 16:57:23 it's really weird. the old way of holding on the boot button and power up won't work. that's why i had to look for this optin and screwed up Feb 15 16:57:27 just dd' that file... Feb 15 16:57:52 rcn I mean I am aloud to use the BBB design as a base for a new PCB board Feb 15 16:57:55 ? Feb 15 16:58:15 k, i'll dd that Feb 15 16:58:52 pablo_, the BBB design has a license, the biggest issues is calling it "BeagleBoard xyz" in which case you have to read: http://beagleboard.org/logo Feb 15 16:59:08 I dont want to call it BBB Feb 15 16:59:10 pablo_, but if you don't call it "BeagleBoard xyz" there's not much to worry about.. Feb 15 16:59:24 ok thanks rcn Feb 15 17:00:25 pablo_, i'm sure you read it, but the license is on the first page of: https://github.com/CircuitCo/BeagleBone-Black/blob/master/BBB_SCH.pdf Feb 15 17:02:21 pablo_: the design is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License Feb 15 17:02:44 https://groups.google.com/d/msg/beagleboard/PZ31jBGEjeU/Qj6_LQjiuIMJ Feb 15 17:03:01 what should i do after i dd the img. insert it into my beaglebone? and restart? Feb 15 17:03:29 lifosuck, yeap.. .make sure you poweroff the bbb.. Feb 15 17:04:00 okay, when i start it, should i hold the boot button Feb 15 17:04:02 (reset doesn't actually do a full reset, so the boot pins are not read in that case) Feb 15 17:04:07 ohhhh Feb 15 17:04:28 on a soft reset, the chip remembers the last boot.. ;) Feb 15 17:04:39 (annoying as heck..) Feb 15 17:04:49 rcn-ee: the SRM does not state the license of the hardware design Feb 15 17:04:51 lol sudo shutdown now will do the trick i guess Feb 15 17:05:36 "sudo systemctl poweroff"... sudo shutdown now doesn't tell the pmic to shut up ;) Feb 15 17:05:48 rcn-ee: neither does that PDF Feb 15 17:06:35 wow. :) Feb 15 17:07:00 rcn-ee: the front page contains a warranty disclaimer but not a license notice Feb 15 17:07:04 i think it's an acpi issue, but systemd works ;) Feb 15 17:07:21 in fact, I can't see a license notice on any of the design files Feb 15 17:07:25 which is a bit worrying Feb 15 17:11:22 rah it's here: http://beagleboard.org/hardware/design Feb 15 17:12:04 panto, upvertor lists it as CC BY-SA 3.0: https://upverter.com/Beagle/afdfe0be7c0bcec5/BeagleBoneBlack/ Feb 15 17:14:04 rcn-ee: I can't see any license there Feb 15 17:14:38 again, there's just a disclaimer, no license Feb 15 17:16:47 rah, there you go even better: http://www.elinux.org/Beagleboard:BeagleBoneBlack#Terms_of_Use " There are no licences involved in the usage of the BeagleBone Black design materials. " Feb 15 17:17:30 rcn-ee, ? Feb 15 17:18:24 rcn-ee: and yet, a few lines down "This work is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License" Feb 15 17:18:40 rcn-ee: and then "You can make changes as needed or use it as is. It is your product when you use these materials. Feb 15 17:18:43 Feel free to build the board yourself at your contract manufacturer of choice. Feb 15 17:18:52 this is a big mess Feb 15 17:18:59 sorry panto was pinging another user... Feb 15 17:19:11 and also: https://groups.google.com/d/msg/beagleboard/PZ31jBGEjeU/Qj6_LQjiuIMJ Feb 15 17:19:48 where Gerald states it's CC licensed again Feb 15 17:20:21 this is very not good Feb 15 17:27:23 I was going to use a beaglebone board in a project and this is making me question that choice Feb 15 17:29:43 rah: that section is vague indeed... fortunately it also says "If you have questions on any of this, you can contact Gerald Coley" Feb 15 17:31:32 hmmm it still says it's debian version 7.9 Feb 15 17:31:37 after flashing Feb 15 17:32:11 zmatt: but that won't help all the people, like pablo who came in here, looking for the license terms Feb 15 17:32:50 zmatt: the license should be stated in the design files themselves Feb 15 17:33:23 that would certainly be more helpful Feb 15 17:44:56 after i dd the img on my microSD, it says the system cannot tell which format it is? is that normal? Feb 15 17:46:24 try file -s /dev/sdb or whatever device your microSD is Feb 15 17:46:45 k Feb 15 17:47:48 sdc1: x86 boot sector Feb 15 17:49:18 eh, did you dd the image to /dev/sdc or /dev/sdc1 ? Feb 15 17:49:36 (it should be written to the whole device, not to a partition thereof) Feb 15 17:49:41 ohhhh Feb 15 17:49:43 k Feb 15 17:49:44 gotcha Feb 15 17:49:46 thanks Feb 15 17:50:14 you could probably diddle the partition map to avoid having the write the whole thing again... Feb 15 17:50:55 ha, no wonder the bbb couldn't read it :| Feb 15 17:52:23 if you check (e.g. sfdisk -l) where your current sdc1 partition starts, then dd the first 1 MB from the image (or from /dev/sdc1 :P) to /dev/sdc, then delete the partition in fdisk and recreate it at a start sector 1 MB further than it was Feb 15 17:52:46 it should then in theory be bootable Feb 15 17:53:12 or you realize that fixing that would take more time than just re-dd'ing the entire image, so you re-dd and go for a coffee, icecream or similar. ;) Feb 15 17:53:28 hehe, yeah it depends on personal preference Feb 15 17:53:30 yea.. i just dd it again lol :P Feb 15 17:55:07 https://settrans.net/~rah/misc/Licensing_terms_for_BeagleBoard_Black__and_other_variants.txt Feb 15 17:55:10 * rah asks Feb 15 17:56:10 lifosuck: I think I might be slightly a "why do it the easy way when there's also an interesting way" person :P Feb 15 17:56:57 "I fucked up, better learn how to fix it" ;) Feb 15 17:58:12 well from the simplest approach and its failure you'd learn that the space between the partition map and the first parition isn't actually empty but quite important ;) Feb 15 18:01:21 Mmm Feb 15 18:01:35 yea. i need to read more into it Feb 15 18:01:41 dd if=/dev/zero of=/dev/sda bs=512 skip=1 count=1 Feb 15 18:01:44 "oups" Feb 15 18:02:04 it's sad my current job is webdevelopment. i want to play more with embedded systems. Feb 15 18:02:15 I remember the first time I fucked up backing up the bootloader on a computer Feb 15 18:02:55 Mixing up if and of and then having a good fun time recovering from having overwritten a booting grub system with a lilo boot loader Feb 15 18:06:09 k 30th time's the charm, it will work! Feb 15 18:06:32 Best of luck! Feb 15 18:10:29 yup. now it's flashing properly... i can't believe i was going in loops. at first i downloaded them image, and dd to sdc1 instead of sdc. then i took that image and try to flash emmc. then of course it won't work. i thought my boot button screwed up. so i was reading. then they say you can change the /boot/uEnv.txt to allow it to boot. then instead of changing the file on the microSD card, i changed it on the emmc. so... i was consta Feb 15 18:10:47 my emmc. then rewriting my microsd to emmc Feb 15 18:10:58 so dumb. lol Feb 15 18:13:34 You've learned to check the basics first :) Feb 15 18:23:26 i am new to open source and want to contribute. Can anybody help me where I should I start Feb 15 18:24:41 Sure. What do you want to contribute _too_ is my question? Do you have a personal itch you want to scratch, something you want to fix, look at , learn? Feb 15 18:26:16 Any bug so that I can get something how organisation works Feb 15 18:26:40 i am aiming for gsoc this year Feb 15 18:28:09 @spidler??? Feb 15 18:30:01 Well, Mostly this channel isn't quite as much about developing software in the traditional FLOSS way. Of course, development happens, but this channel is more about getting things to run on the boards, some driver development etc. Feb 15 18:30:12 Not much of that is, afaik, alive in the issue trackers as such Feb 15 18:30:41 https://www.gnome.org/get-involved/ has a fairly good start though Feb 15 18:31:56 So according to you there is nothing for develepors in this org?? Feb 15 18:33:12 There probably is, but I'm not the correct person to ask Feb 15 18:33:19 I just hack on stuff on top of the BBB. Feb 15 18:33:38 ayush_, gsoc: https://groups.google.com/forum/#!forum/beagleboard-gsoc Feb 15 18:33:48 thanks rcn-ee! Feb 15 18:34:45 @spidler thanks for all the information Feb 15 19:00:50 holy shit Feb 15 19:02:06 https://settrans.net/~rah/misc/Re:_Licensing_terms_for_BeagleBoard_Black__and_other_variants.txt Feb 15 19:02:09 what a dick head Feb 15 19:08:00 cool!; I can see u-boot on terminal (beaglebonewhite); how can I enter interactive prompt? -> http://pastebin.com/NrhPsfaQ Feb 15 19:08:21 currently I'm following this steps -> http://elinux.org/Building_for_BeagleBone Feb 15 19:08:51 owl-v-: where'd you get your u-boot from? Feb 15 19:09:02 github Feb 15 19:09:09 vagrantc: ^ Feb 15 19:09:28 owl-v-, does your fdisk dump look the same? Feb 15 19:09:36 there was a bug in an old version.. Feb 15 19:09:40 no. not github Feb 15 19:09:46 the git repository -> http://git.denx.de/?p=u-boot.git;a=summary Feb 15 19:10:28 owl-v-, look at: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSDcard Feb 15 19:10:49 the dd method is perfered over the old mlo/u-boot.img in the fat partition.. Feb 15 19:12:01 vagrantc, stretch has video on x15 now: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813610 Feb 15 19:13:43 hm.. i did copy mlo & u-boot.img ....; so, i should do like "sudo dd if=mlo of=/mnt" ? Feb 15 19:14:50 rcn-ee: ah, i only got as far as testing framebuffer Feb 15 19:14:50 owl-v-, dd it to the drive, not the mount.. Feb 15 19:15:31 vagrantc, drm framebuffer always worked, for x (can't wait till wayland) we needed a magic number added to the ddx.. Feb 15 19:17:06 rcn-ee: 'drive' as a partition? Feb 15 19:17:27 like /dev/sdb ? Feb 15 19:19:17 rcn-ee: makes sense Feb 15 19:19:18 yeapers... mlo/u-boot.img are essentially in the MBR... Feb 15 19:19:29 rcn-ee: 4.4.x should hit unstable soonish, i think Feb 15 19:19:44 which has some of the configuration options needed for x15 Feb 15 19:20:10 ben just delayed it for 4.4.2 ;) Feb 15 19:20:36 what is a good way to enable user permissions on gpios for the newest kernel w/ jessie? In 3.8.13 it seemed that editing udev was a great way, but i can't find documentation using universaln which appears to come standard and enabled on the latest kernel Feb 15 19:21:02 hi, I'm trying to load the uio_pruss kernel module and I keep getting "Invalid module format" I'm trying to use the pruio library which is freebasic wrapped in C Feb 15 19:21:32 is uio_pruss.ko the correct module? Feb 15 19:21:55 twoten, depends... which kernel? uname -r Feb 15 19:22:23 4.1.15-ti-r40 Feb 15 19:24:47 Do I need to downgrade my kernel to get libpruio working? Feb 15 19:30:27 twoten, nope, you just need a different kernel: sudo apt-get update ; sudo apt-get install linux-image-4.1.17-bone19 ; sudo reboot Feb 15 19:30:54 rcn-ee: 'dd' did not work for me :( Feb 15 19:31:16 twoten, ti's busy trying to replace uio_pruss with remoteproc_pruss, which is in that "4.1.15-ti-r40", the bone kernels has uio_pruss Feb 15 19:31:42 owl-v-, then follow it from the begining: https://eewiki.net/display/linuxonarm/BeagleBone+Black it's step by step.. Feb 15 19:34:07 yes, lsmod reports that pruss_remoteproc is loaded but none of the pruio examples work - so I'll change to the 4.1.17-bone19 kernel Feb 15 19:34:30 twoten, remoteproc/uio are not compatible, that's why. ;) Feb 15 19:35:14 finally the bogeyman has emerged from the mist so now I can shoot him! Feb 15 19:37:37 rcn-ee: ok, so 'dd' is doing 'cp' files Feb 15 19:38:39 is mmc == sd card? Feb 15 19:39:14 yeapers Feb 15 19:40:36 rcn-ee: heh. i just noticed it moved to the debian kernel git branch, i'm guesing you read a ost to the debian kernel list? :) Feb 15 19:41:22 vagrantc, it was in the "Uploading linux (4.4.1-1)" email thread Feb 15 19:46:00 rcn-ee: only a couple more days, then Feb 15 19:46:38 there's a nice rt bump they could also sneak in then too . ;) Feb 15 20:16:36 rcn-ee: does the default u-boot try to boot kernel from MMC without entering u-boot prompt? like "U-Boot#" ? Feb 15 20:17:34 yes, and ^ was a bug in the current *rc cycle.. Feb 15 20:20:35 hello , do you know if the external charger for BBB rev C have a current regulator for more than 5V? Feb 15 20:29:29 linkages: don't use over 5V Feb 15 20:33:30 thanks Feb 15 21:41:36 is there something like a clock tick on the BBB - that I can use as an interrupt to fire off regular functions? Feb 15 21:44:55 i have trouble with the Adafruit_BBIO.GPIO lib. when i setup a pin as input, i can read the value of it. but if i use GPIO.wait_for_edge method, it will not detect the rising or falling edge. Feb 15 21:48:49 twoten: in what environment? linux offers timers, and hardware timers are also available (e.g. for pru) Feb 15 21:50:23 I'm using the libpruio library so a pru timer should probably be strait forward Feb 15 21:50:46 pru has timers in its "IEP" peripheral, see TRM Feb 15 21:50:48 bbl Feb 15 21:50:58 thanks! Feb 15 22:11:01 how can I update the internal u-boot partition with my beaglebone black connected through usb using bbbfls? i seem to be having problems after sucessfully flashing through usb. I can not flash through microsd card as it does not read from the port Feb 15 22:20:10 mistawright: how are you flashing exactly? I hope not with the included scripts since those are pretty broken Feb 15 22:35:30 zmatt, i used the bbblfs to mount and then from there dd'ed an image to the beaglebone black Feb 15 22:37:04 zmatt, when i try to boot this is what happens: http://pastebin.com/cLunQrx9 Feb 15 22:37:49 zmatt, I am not sure how can I fix this or if it can be fixed. this board doesnt read from the microsd card as well. I bought a replacement but still have hope i can fix this issue Feb 15 22:40:49 ah, the usual boot device problem Feb 15 22:41:11 also, very old image? Feb 15 22:41:36 zmatt, ive flashed a recent image to the emmc. so im not sure whats causing this Feb 15 22:43:39 annoyingly it also looks like you may have once upon a time saved u-boot's environment variables... that might complicate things Feb 15 22:44:17 hmm, "Using default environment", okay maybe not Feb 15 22:44:34 I'm used to seeing a CRC error, but I guess "Bad magic" will do too (whatever it may mean) Feb 15 22:45:20 then we're back to boot device... that's an annoying issue that has been fixed in recent images using filesystem UUIDs, but you'll need to manually fix up /boot/uEnv.txt and /etc/fstab if you flash manually to get the same effect Feb 15 22:45:54 you can try it with this install, if it doesn't work I suggest getting the latest jessie image Feb 15 22:46:07 mount it again using BBBlfs Feb 15 22:47:26 I personally randomize the filesystem uuid to be on the safe side (to avoid all BBBs cloned from the same template from having the same uuid) using tune2fs -U random /dev/sdb1 (fill in the BBB's partition) Feb 15 22:48:21 zmatt, perform the random uuid before or after the flash? Feb 15 22:48:36 after, but like I said you try this first on this install you already did Feb 15 22:48:47 it's not misflashed or anything, it's just an annoying known issue Feb 15 22:48:54 *you can try Feb 15 22:49:40 extract the uuid using blkid -c /dev/null -s UUID -o value /dev/sdb1 Feb 15 22:50:03 zmatt, getting things mounted now so i can try Feb 15 22:51:34 zmatt, i dont have /dev/sdb1 but i do have /dev/sdb2 Feb 15 22:51:45 uhh Feb 15 22:52:11 that makes no sense Feb 15 22:52:56 zmatt, lol, thats what i was wondering Feb 15 22:53:01 I've never seen that other than as a result of using the broken scripts included with BBBlfs (instead of just dd) Feb 15 22:53:27 so are you recommending i connect without using bbblfs to mount? Feb 15 22:53:47 no, the utility (bin/usb_flasher) is fine... well, it's brittle, but when it works it's fine Feb 15 22:54:27 it's only the scripts (e.g. flash_script.sh) that should always be avoided Feb 15 22:55:41 echo start=2048,bootable | sfdisk /dev/sdb <-- that should fix the partition map (do make sure /dev/sdb is really your BBB :P ) Feb 15 22:57:22 zmatt, will try Feb 15 23:00:16 zmatt, hmmm it helped with changing the drive to sb1 but trying to boot after running tune2fs Feb 15 23:00:39 no there are more steps Feb 15 23:06:02 http://pastebin.com/YpKDQd59 <-- this shows the desired situation from inside a BBB Feb 15 23:07:15 i.e. you need an entry in /boot/uEnv.txt to let u-boot know about the filesystem uuid (even though in principle it could have extracted that itself, but it doesn't), and identify your root filesystem in fstab by uuid Feb 15 23:08:21 that way you're no longer dependent on whether the eMMC gets called "mmcblk0" or "mmcblk1" by linux (which is the root cause of this problem: linux assigns those numbers in the order it happens to encounter mmc devices, so if a card is inserted then eMMC is mmcblk1 while if it's not then eMMC is mmcblk0) Feb 15 23:09:43 if using blkid immediately after randomizing a filesystem uuid, be sure to pass the "-c /dev/null" option to ensure it doesn't show your outdated cached information Feb 16 00:40:41 on the BBB, GPIO0.20 is CLKOUT2 and goes to the JTAG header. what purpose does it serve, and what in the kernel/os turns it on/off? Feb 16 00:45:20 both 0.19 and 0.20 go to the jtag header actually, although both are double-booked: the former is also used as 24 MHz clock used for hdmi CEC while the latter is also routed to P9.41 Feb 16 00:45:39 the reason they also go to the jtag header is mux option 6: EMU2 / EMU3 Feb 16 00:47:09 which, combined with EMU0, EMU1, and EMU4 gives you 4-bit (+ clock) synchronous trace from the System Trace Module Feb 16 00:52:16 the reason i'm asking is that we are using GPIO0.20 as an out to control one of the inputs to the LE910, ON/OFF*. i am expecting to have control of it in my firmware. is there any change the kernel or a driver is overriding my control of it? and is it an output when used as a jtag function? Feb 16 00:52:34 s/change/chance/ Feb 16 00:53:09 and would that overriding contorl have anything to do with the hardwared network interface being available or not? Feb 16 00:53:46 (eth0?) Feb 16 00:54:22 i might be treeing up the wrong bark... but checking possibilities.. Feb 16 00:54:52 absolutely not. only fancy debuggers will normally enable trace pins, manual configuration will be required anyway since there are several mux options for the trace pins, and you'd easily notice simply by inspecting pinmux Feb 16 00:56:37 i see. thanks man. Feb 16 00:56:57 beware btw that on the BBB that pin is also tied to another one (pin 109, GPIO 3.20), for the purpose of making more options available on the attached expansion header pin (P9.41) Feb 16 00:58:02 yes, i saw that. Feb 16 00:58:12 i need to see what we're doign with 3.20 Feb 16 00:59:21 also, it seems it's very easy to force an usb port to full-speed instead of high-speed: that's a simple matter of *not* setting the HSENAB bit in the POWER register... I don't know if the driver can be convinced to refrain from setting that bit via e.g. sysfs, but if not then it'll probably be an easy patch Feb 16 01:00:30 also, I have a script which can be useful for checking pinmux -> http://gerbil.xs4all.nl/show-pins-v2.pl.gz Feb 16 01:01:13 it's a bit BBB-centric but passing the -v option once/twice shows more/all pins Feb 16 01:06:06 thanks! Feb 16 01:07:47 did i tell you that grounding the UART0_TX signal 100 percent removes the babble interrupt in one scenario? Feb 16 01:08:02 how crazy is that? Feb 16 01:08:26 eww Feb 16 01:08:34 we have also pulled the level translator that was drivign that tx line to the le910, so it's just dangling there. Feb 16 01:08:53 veremit: tell me about it.. Feb 16 01:09:09 ehh, I hope you don't mean grounding the uart0_tx pin of the am335x, while it's configured as that function (i.e. as output) Feb 16 01:09:16 yes, i do Feb 16 01:09:29 aren't they over-current protected? Feb 16 01:09:32 no Feb 16 01:09:53 yeah, well it was worth it to see anyway. Feb 16 01:10:23 I've seen the am335x survive drive conflicts also, but I wouldn't make a habit out of it :P Feb 16 01:10:40 very nice! (your show pins) Feb 16 01:11:02 oh gosh, typographically fancy too, complete with superscripts... Feb 16 01:12:27 "up/down" is the pin state (1/0)? Feb 16 01:12:32 pull Feb 16 01:12:53 ah. Feb 16 01:13:11 I can't easily obtain the pin state from a perl script Feb 16 01:13:36 all this is from the sysfs? Feb 16 01:13:41 yes Feb 16 01:13:52 and a table of data in the script Feb 16 01:13:58 nice, thanks matt. Feb 16 01:14:09 this could help us nail the issue, possibly. Feb 16 01:14:36 and if you think superscripts are fancy, haven't you seen the overbars I use in my spreadsheet? ;) Feb 16 01:14:57 and bottom-sign for ground, stuff like that Feb 16 01:15:00 * zmatt likes his unicode Feb 16 01:17:54 no, haven't noticed Feb 16 01:54:17 zmatt: you need to get out more lol Feb 16 02:00:58 out?! but there's this crazy bright light there (not right now fortunately), and often lots of people, very annoying Feb 16 02:06:04 yeah that bloody crazy ligh thing .. it burns when it shines ... :/ Feb 16 02:09:22 https://what-if.xkcd.com/49/ Feb 16 02:18:19 Are there any downsides to this scenario? Feb 16 02:18:19 We would all freeze and die. Feb 16 02:18:19 So, are there any downsides to this scenario....? Feb 16 02:18:31 :D Feb 16 02:20:08 so, that's all theoretical, but experimentation is what's really needed... **** ENDING LOGGING AT Tue Feb 16 02:59:59 2016