**** BEGIN LOGGING AT Fri Aug 28 02:59:58 2015
Aug 28 03:09:35 <cuongvkt> hi there
Aug 28 03:09:51 <cuongvkt> im new here
Aug 28 03:09:58 <cuongvkt> and i need some help
Aug 28 03:10:25 <cuongvkt> any one can help me please
Aug 28 03:11:17 <cuongvkt> i want to install Serial library on Beagle but i cant do it
Aug 28 03:12:32 <cuongvkt> i can not see GateOne SSh below heading Software in the bone101
Aug 28 03:12:47 <cuongvkt> plz help me
Aug 28 03:12:51 <cuongvkt> thanks so much
Aug 28 08:15:07 <mrpackethead> hello, has anyone got a Beaglebone Green yet?
Aug 28 08:23:07 <Gwak> Hi, i've rewrite the am335x-boneblack.dtb, everything work except for pin P9-16 and P9-17, after booting every pins I configured are in mode 0x37 or 0x27 (gpio I/O) but P9_16/17 are un mode 0x62 i.e i2c1... I can't find what is overwriting my configuration, is it the i2c driver ?
Aug 28 08:23:56 <Gwak> ls
Aug 28 08:24:37 <Gwak> miss *
Aug 28 08:26:33 <Gwak> any idea please ?
Aug 28 08:31:19 <Humpelst1lzchen> Gwak: have you checked uboot?
Aug 28 08:32:57 <tbr> do you load any capes? can you pastebin your rewritten dtb?
Aug 28 08:35:48 <Gwak> i've disabled the cape manager, uboot is loading the correct device tree
Aug 28 08:35:49 <Gwak> http://pastebin.com/9Z7uzaag
Aug 28 08:36:20 <Gwak> (tor means digital I/O in french (torout/torin))
Aug 28 08:36:47 <Gwak> everything is correctly set, except those lines :                 0x15c (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* P9_17 GPIO0[5]  torout4 */                 0x158 (PIN_OUTPUT_PULLDOWN | MUX_MODE7) /* P9_18 GPIO0[4]  torout5 */
Aug 28 08:37:59 <Gwak> I think they are overwritten by some other file ... but i've checked my included file (am33xx.dtsi and am335x-bone-common-no-capemgr.dtsi) no references to any pin 9_17/18
Aug 28 08:38:36 <Humpelst1lzchen> Gwak: P9-16 and P9-17 are Pin 16 and 17 on Header P9 for you? Because the seem unrelated.
Aug 28 08:38:43 <Humpelst1lzchen> aah 17/18
Aug 28 08:38:56 <Gwak> ye sorry did a mistake on first message
Aug 28 08:41:53 <Humpelst1lzchen> Gwak: what I mean with u-boot was: U-Boot might configure the pins, like its does with i2c0
Aug 28 08:42:02 <Gwak> Oh ok
Aug 28 08:42:08 <Gwak> where can I check that ?
Aug 28 08:42:16 <Humpelst1lzchen> u-boot sources
Aug 28 08:42:42 <Humpelst1lzchen> iirc the u-boot shell also have i2c commands you can use
Aug 28 08:43:26 <Gwak> uEnv ? I've boot my kernel with TFTP and NFS server using tftpboot 0x80F80000 am335x-boneblack.dtb && tftpboot 0x80007FC0 uImage, uboot could have changed anything else ??
Aug 28 08:43:33 <Humpelst1lzchen> uhm
Aug 28 08:43:49 <Humpelst1lzchen> Gwak: looking at your pastebin, have you checked am33xx.dtsi?
Aug 28 08:44:18 <Gwak> yup i've checked both include no reference to the pin addr, gpio0 or i2c0
Aug 28 08:45:10 <Humpelst1lzchen> i2c2^
Aug 28 08:45:42 <Gwak> Despite the way i'm booting the kernel uboot can overwrite i2c config ?
Aug 28 08:45:59 <Humpelst1lzchen> uboot is first
Aug 28 08:46:08 <Gwak> p9_17/18 are referencing to i2c1 no ?
Aug 28 08:46:25 <Gwak> I2C1_SCL and I2C1SDA
Aug 28 08:46:42 <Humpelst1lzchen> i2c2 on my bbb srm
Aug 28 08:47:19 <Gwak> oh ye you are right, I think there is a mistake ni my sheet
Aug 28 08:47:41 <Gwak> i'm going to check that with i2c2, thanks :)
Aug 28 08:51:38 <Gwak> Hum, just checked the schematics and P9_17/18 are wired to i2c1_SCL and i2c1_sda
Aug 28 08:53:58 <Gwak> BBB rev C
Aug 28 08:54:25 <Humpelst1lzchen> thats 15/16, or?
Aug 28 08:54:37 <Gwak> 15/16 ?
Aug 28 08:55:27 <Gwak> P9_19 and P9_20 are on i2c2 but P9_17 P9_18 are on i2c1
Aug 28 08:55:56 <Humpelst1lzchen> yes
Aug 28 08:57:15 <Humpelst1lzchen> sorry my fault
Aug 28 08:57:26 <Gwak> np ^^
Aug 28 09:59:25 <Savva_> Hi, I am new to beagleboard, I just got my Beagleboard-xm. When I startup the beagleboard, i can see it in my terminal (uses Angstrom), but there is no GUI interface on my hdmi screen as I see in tutorial videos. Can anyone please tell me how I can get the user interface on my screen? There are also links that say the sd card that came with the beagleboard is only a trial, is this correct?
Aug 28 10:01:03 <Savva_> Hi, I am new to beagleboard, I just got my Beagleboard-xm. When I startup the beagleboard, i can see it in my terminal (uses Angstrom), but there is no GUI interface on my hdmi screen as I see in tutorial videos. Can anyone please tell me how I can get the user interface on my screen? There are also links that say the sd card that came with the beagleboard is only a trial, is this correct?
Aug 28 10:04:46 <av500> Savva_: I would recommend you get the lastest image from the beagleboard.org website
Aug 28 10:05:02 <av500> just to be sure you are running the lastest SW
Aug 28 10:06:40 <Savva_> oky thank you I will do that now. Also is Angstrom better to use with the beagleboard xm, than ubuntu?
Aug 28 10:09:49 <av500> Savva_: it was the supported sw
Aug 28 10:09:59 <av500> XM is quite old
Aug 28 10:10:05 <av500> BBB uses debian by now
Aug 28 10:10:11 <av500> there are ubuntu builds for XM
Aug 28 10:10:18 <av500> but I cannot help you with that much
Aug 28 10:17:41 * tbr suggests to place a +b *@147.200.109.203.static.cust.vf.net.nz until mrpackethead gets his connection under control
Aug 28 10:18:15 * LetoThe2nd agrees
Aug 28 10:19:15 <LetoThe2nd> other OPs please note to remove it if needed.
Aug 28 11:45:21 <Costin> bone-capemgr bone_capemgr.9: slot #10: BB-SPI0DEV conflict P9.17
Aug 28 11:45:24 <Costin> help
Aug 28 11:45:25 <Costin> ?
Aug 28 11:45:37 <Costin> is anyone here ?
Aug 28 12:02:41 <Costin> shit channel....
Aug 28 12:04:42 <teste_> anyone here ?
Aug 28 12:04:48 <teste_> need help
Aug 28 12:05:20 <Gwak> "never ask to ask, just ask"
Aug 28 12:06:24 <teste_> [  331.500729] bone-capemgr bone_capemgr.9: slot #10: BB-SPI0DEV conflict P9.17 (#8:BB-SPI0DEV)
Aug 28 12:06:33 <teste_> i am trying to use SPI0
Aug 28 12:06:37 <teste_> and i can;t
Aug 28 12:07:56 <teste_> i tried to enable it and somehow i did it, it appears in /dev/spidev1.0
Aug 28 12:08:11 <teste_> but on screen i get this error
Aug 28 12:08:22 <teste_> "[  331.500729] bone-capemgr bone_capemgr.9: slot #10: BB-SPI0DEV conflict P9.17 (#8:BB-SPI0DEV)"
Aug 28 12:09:05 <teste_> is my problem so seerious ? nobody can help ?
Aug 28 12:09:28 <Gwak> I'm not sure but it seems that you are trying to load the BB-SPI0DEV but it's already loaded on slot #8, so the error is telling you that the pin P9_17 is already in use by the BB-SPI0DEV on slot 8
Aug 28 12:10:31 <teste_> but it isn't... if i don't do " echo BB-SPI0DEV > /sys/devices/bone_capemgr.9/slots" it doesn't appear in /dev
Aug 28 12:10:49 <teste_> and after i do that, i get the error....
Aug 28 12:11:14 <teste_> is there any other way i can enable spi0 and i don't know it ?
Aug 28 12:12:08 <Gwak> can you pastebin : cat /sys/devices/bone_capemgr.9/slots
Aug 28 12:13:11 <teste_> http://pastebin.com/SBQnyPMH
Aug 28 12:13:37 <Gwak>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0DEV
Aug 28 12:14:00 <teste_> the last slot was added after i followed this procedure: http://en.gnublin.org/index.php/Tutorial_API_BeagleBoneBlack ("use SPI" section)
Aug 28 12:14:05 <Gwak> this means the dto is already loaded
Aug 28 12:14:21 <teste_> i didn;t have it before
Aug 28 12:14:47 <teste_> yes, but after reboot i don't have /ev/spidev*
Aug 28 12:17:15 <teste_> ?
Aug 28 12:17:19 <teste_> any ideas ?
Aug 28 12:18:43 <Gwak> the dto is hear to overwrite the default configuration, setup the pinmux and describe your device, if you don't have the device nodes I think it comes from the API not the device tree overlay
Aug 28 12:18:46 <Gwak> here *
Aug 28 12:22:45 <msvb-lab> Hello folks, anyone have an opinion about programming IoT without SDHC?
Aug 28 12:22:47 <msvb-lab> I mean, booting Beaglebones to eMMC (which OS?) and still having good MQTT or CoAP interfacing?
Aug 28 12:35:17 <SpeedEvil> why?
Aug 28 12:35:30 <SpeedEvil> If you can boot, you can boot, and run.
Aug 28 12:36:34 <msvb-lab> I'm asking without using one before, but we're considering them for instruction.
Aug 28 12:37:10 <msvb-lab> ...and I assume there is some (maybe a lot?) of difference between Angstrom, Debian, Ubuntu Snappy (with an official image) and Minix3.
Aug 28 12:37:40 <msvb-lab> So assuming we can't affort SDHC cards for each student, we'll be limited to using whatever works on eMMC.
Aug 28 12:38:10 <msvb-lab> ...and I don't see too much support for non-Angstrom there.
Aug 28 12:38:28 <SpeedEvil> SD cards are $1 per
Aug 28 12:39:26 <msvb-lab> Do you have a public source to state? For that price we could possibly get SD (we're budget-less at this time.)
Aug 28 12:39:47 <SpeedEvil> http://www.ebuyer.com/230603-verbatim-4gb-class-4-microsdhc-card-44002
Aug 28 12:46:12 <msvb-lab> Okay, thanks for the SD hint. But the deeper question is, how functional would a Beaglebone be without SD? Now I see the latest Angstrom image is late 2013?
Aug 28 12:47:36 <adj> BBB ships with some quite recent debian image on eMMC
Aug 28 12:47:46 <msvb-lab> I guess most people who use Beagleboards without SDHC build Angstrom themselves from current sources?
Aug 28 12:47:55 <msvb-lab> Oh, okay, didn't know that now BBB is shipping with Debian.
Aug 28 12:48:09 <msvb-lab> Somewhere I had read that the default installation was Angstrom.
Aug 28 12:48:20 <adj> yes, I guess pretty much nobody is using Angstrom on BBB
Aug 28 12:49:01 <msvb-lab> Since our syllabus is IoT oriented I had thought Ubuntu Snappy would have been the best choice, but maybe we can make do with Debian on eMMC.
Aug 28 12:49:21 <adj> my personal use case for SD with BBB is to only flash a newer image
Aug 28 12:51:34 <SpeedEvil> The EMMC is simply exactly the same as the SD card from a software point of view once it's mounted.
Aug 28 12:51:56 <SpeedEvil> You can set it up to run entirely from MMC - constrained by the size of course
Aug 28 12:52:31 <SpeedEvil> If there are canned installers to do so is another question
Aug 28 12:53:53 <msvb-lab> I thought the block structure and kernel drivers for SDHC and eMMC differed (and I'm not sure if eMMC on BBB is on the USB bus?) Vendors like Minix and Canonical provide images for BBB clearly stating that they are for SDHC and not for eMMC.
Aug 28 12:54:12 <SpeedEvil> err
Aug 28 12:54:18 <SpeedEvil> I'm not properly awake, apologies.
Aug 28 12:54:39 <msvb-lab> How easy would it be to ignore canned installers and manually install Minix to eMMC, possible with dd(1)?
Aug 28 12:55:13 <msvb-lab> No need to apologize, and hope you get some yummy coffee.
Aug 28 12:55:21 <SpeedEvil> Wait - no - emmc is just MMC embedded - it's nothing special.
Aug 28 12:55:37 <SpeedEvil> The only special bit in the emmc on the beagle is as I understand it simply a boot partition.
Aug 28 12:56:23 <SpeedEvil> You need to setup this boot partition so the processor knows where to get its boot image, then mount from another partition (I am not sure if it supports a normal disk-like partition) on the emmc - and treat it just like you would a SD card
Aug 28 12:56:40 <SpeedEvil> Minix?
Aug 28 12:56:53 <SpeedEvil> ah
Aug 28 12:57:03 <msvb-lab> Well, it's an interesting system and provides an official BBB image.
Aug 28 12:57:08 <msvb-lab> Minix3 I mean.
Aug 28 12:57:36 <SpeedEvil> In principle, yu would simply need to change the device it is expecting to boot off in fstab et al, and you're done.
Aug 28 12:58:08 <SpeedEvil> Anyone leap in if I'm misleading.
Aug 28 12:58:14 <SpeedEvil> I haven't gotten my bbb yet
Aug 28 12:59:31 <msvb-lab> Okay, so I'd boot to SDHC and then use dd(1) to flash a (made for SDHC) image to the non-boot eMMC partition. My gut feeling is that it would work, what do you think?
Aug 28 13:00:04 <msvb-lab> ...it would require unpacking the Ubuntu/Minix3 SDHC image since it is a multipartition image with grub boot and such.
Aug 28 13:00:19 <msvb-lab> ...just using the root then and putting that onto part2 of eMMC.
Aug 28 13:02:05 <msvb-lab> How risky would this be, if I overwrite the eMMC part1 boot for example?
Aug 28 13:02:42 <adj> no worries, you cannot brick BBB with software
Aug 28 13:03:35 <msvb-lab> Okay, nice to know the soft brick feature.
Aug 28 13:04:23 <msvb-lab> By the way, I don't understand how fstab could affect boot, since it's on the root partition which is mounted only during the boot sequence?
Aug 28 13:21:29 <abferm> msvb-lab: your assumtion that the root partition is never remounted is flawed...
Aug 28 13:22:26 <msvb-lab> abferm: The root partition is surely mounted after the boot partition?
Aug 28 13:22:50 <msvb-lab> Oh, maybe I understand.
Aug 28 13:23:10 <abferm> Yes, but it can be remounted later while running
Aug 28 13:23:42 <abferm> You may also need to modify your uEnv.txt that tells uboot where to load things from.
Aug 28 13:23:57 <abferm> should be in /boot/
Aug 28 13:25:24 <msvb-lab> abferm: Okay, it seems this might work with some partition mangling. Maybe the only limitation will be 3 Go storage (enough for Minix3 but Ubuntu?)
Aug 28 13:25:54 <msvb-lab> Our workshop doesn't require much storage in fact.
Aug 28 13:27:28 <abferm> Can you run headless(no GUI)? That helps a lot.
Aug 28 13:28:19 <abferm> I would stick with debian rather than ubuntu if possible.
Aug 28 13:29:29 <msvb-lab> abferm: I think headless is the way to go, just a little risky since I don't know what kind of students will show up.
Aug 28 13:29:47 <abferm> If you are going to try dd-ing your minix on there, make your root partition small for the copy, then resize it.
Aug 28 13:30:08 <msvb-lab> The Ubuntu direction would only be interesting due to the recent developments around Snappy.
Aug 28 13:31:26 <msvb-lab> Right I'll shrink then enlarge root, and remove the Minix boot partition (seems eMMC/uboot would do the trick.)
Aug 28 13:32:02 <msvb-lab> I'm guessing that writing a Minix3 with dd(1) to sdX writes a boot and root partition.
Aug 28 13:32:03 <abferm> I would personally just throw Debian 8.1 on there and call it a day. There are prebuilt flashers, and you can get away with running a small gui like xfce.
Aug 28 13:32:46 <abferm> the mmc should enumerate as something like mmcblk0 not sdx
Aug 28 13:33:26 <msvb-lab> You're probably right about debian but X11 is not needed when teaching IoT. Any human interface will be implemented over the network.
Aug 28 13:33:50 <abferm> or you could just boot from an SD card and have a lot more space.
Aug 28 13:34:20 <msvb-lab> The sdX referred to the typical preparation of an SDHC card, which I would unpack in that way, reprocess (shrink) and the remove sdX1 (boot) before rewriting the real eMMC with whatever came off sdX2.
Aug 28 13:34:31 <msvb-lab> sdX2 == root partition on SDHC.
Aug 28 13:35:04 <abferm> The older BBB images had a boot partition, so you might want to double check before doing away with it.
Aug 28 13:35:06 <msvb-lab> We'll use SD cards if we can buy them but so far there's no sponsorship to do that.
Aug 28 13:36:42 <abferm> Again, I would just use the prebuilt Debian 8.1 flasher. It would be much easier, unless there is something special in minix that you really need.
Aug 28 13:37:21 <msvb-lab> ...or if Snappy offers something appealing to IoT developers.
Aug 28 13:37:40 <msvb-lab> Seems to me that a number of choices are good ones, glad to hear that.
Aug 28 13:38:16 <msvb-lab> I started this thread rather depressed thinking that Debian on eMMC was not possible or at least not standard.
Aug 28 20:07:14 <ajay_> very basic doubt
Aug 28 20:07:39 <ajay_> my laptop cannot constantly connect to the beagle
Aug 28 20:08:08 <ajay_> asks me for the IP address, when I enter it, nothing happens
Aug 28 23:06:31 <mrpackethead_fix> hello is one of the ops here?
Aug 28 23:06:43 <mrpackethead_fix> Deeply sorry for causing all the connections and disconnections
Aug 28 23:06:51 <mrpackethead_fix> but have no discovered and fixed the problem
Aug 28 23:07:03 <mrpackethead_fix> and was wondering if someone can deban me.
Aug 28 23:57:39 <mrpackethead_fix> goodmorning op folks..
Aug 28 23:57:42 <mrpackethead_fix> is anyone awake?
Aug 29 00:07:07 <veremit> oh Finally, mrpackethead_fix :P but bad luck on the ban .. hahaha!
Aug 29 00:35:32 <mrpackethead_fix> veremit: Was pretty tricky to figure out what was going
Aug 29 00:35:35 <mrpackethead_fix> pn/
Aug 29 00:35:38 <mrpackethead_fix> on.
Aug 29 00:36:12 <mrpackethead_fix> when i put my macbook to sleep, it keeps waking up peridically
Aug 29 00:36:15 <veremit> so what was it? it -was- pretty annoying
Aug 29 00:36:46 <mrpackethead_fix> bluetooth connection was waking it up
Aug 29 00:36:59 <veremit> niiiice
Aug 29 00:37:02 <mrpackethead_fix> and then because the IRC client tried to connect
Aug 29 00:37:16 <mrpackethead_fix> then it went back to sleep
Aug 29 00:37:27 <mrpackethead_fix> and the cycle continued.
Aug 29 00:40:41 <mrpackethead_fix> hopefully one of the ops here can help me.
Aug 29 00:40:45 <mrpackethead_fix> and unban me.
Aug 29 00:42:19 <veremit> possibly .. when they're back
**** ENDING LOGGING AT Sat Aug 29 02:59:59 2015