[04:52] ogra yes, i decompresses with xz -d then dd if=... of=/dev/mmcblk0 bs=1M [04:55] ogra xzcat ubuntu-15.04-snappy-armhf-rpi2.img.xz | md5sum [04:56] how does one get a serial interface on the rpi2? do i need a breakout board for the 40-pin headers or can i do it over usb? [04:56] dc2715982039ebc63e5febc17fbae78d - [05:04] ogra: digests check out fine against the web listing [09:01] sabdfl, serial is by default on the outside row of the 40 pin header on pin 6, 8 and 10 (pin 1 is at the corner of the PCB near the power LED) http://www.element14.com/community/docs/DOC-73950/l/raspberry-pi-2-model-b-gpio-40-pin-block-pinout. i use a cable like http://www.amazon.de/gp/product/B00KVUSI30 [09:01] my GPS hats use that, unfortunately [09:01] (any other FTDI cable should do as well) [09:01] is there a way to do TTY over USB? [09:01] right, then we need to disable it in /boot/uboot/config.txt [09:02] on the rpi sd card? [09:03] yes, boot without the hat, then you can edit it [09:03] do you have make and modle of the hat, i bet there are instructions how to set up the config.txt [09:03] *model [09:04] can i edit it while mounted? [09:05] there is indeed a way to do serial over USB ... but only from a kernel module ... (i.e. it would only provide output after boot) we were pondering to enable that by default (like the BBB has) [09:05] yes, indeed its a normal file on a filesystem ... you can just edit away and reboot to test the change [09:08] you can even do kernel console on cdc-acm [09:08] but it's a bit tricky [09:08] tbr, right, but not bootloader [09:08] correct [09:08] although [09:08] the question is if we could live with disabled bootloader console by default [09:09] would need to ask Tartarus if uboot can do cdc-acm too [09:09] ogra, gps hat instructions are at https://learn.adafruit.com/adafruit-ultimate-gps-hat-for-raspberry-pi/pi-setup [09:09] but nothing there seems to map to system-boot partition [09:09] would depend on the usb controller [09:10] uboot.env seems to have some ttyAMA stuff [09:10] sabdfl, oh, it changes the cmdline ... thats a bit more tricky than config.txt because snappy assembles it from multiple vars and places [09:10] yeah, one sec [09:12] sabdfl, on the booted board run: sudo fw_setenv mmcargs 'setenv bootargs "${args} console=tty0 root=${mmcroot}"' [09:12] fw_printenv is the command to show all config optios [09:12] (if you want tro check before and after) [09:13] so boot without the hat then do this? [09:13] yeah [09:13] on snappy? [09:13] right [09:13] (RaspberryPi2)ubuntu@localhost:~$ fw_printenv |grep console [09:13] mmcargs=setenv bootargs "${args} console=tty0 console=ttyAMA0 root=${mmcroot}" [09:13] thats the default ... [09:14] ok will try that [09:15] ah, the board seems to also need 9600 baud [09:15] that might need further changes [09:20] * ogra_ guesses we should move all console options by default to the cmdline.txt file, seems all documentation expects it there [09:28] sabdfl, bug 1500164 :) [09:28] hmm, no bot ? [09:28] https://bugs.launchpad.net/snappy/+bug/1500164 [09:28] bug 1500164 in Snappy "console= cmdline options on the RPi2 should be moved from uboot.env to cmdline.txt" [Undecided,New] https://launchpad.net/bugs/1500164 [09:29] ah [10:07] ogra_ in a similar vein, we should call our new kernel "rpi2" not "rasp2" [10:11] well, thats something the kernel team decided [10:11] we'll have to talk to them [10:14] there is a community guy who make a linux-image-rpi2 [10:14] we should sync with him and have one kernel [10:15] ah, i didnt know ... i'll carry that forward to ppisati ... [10:16] thank you [10:16] Woah, look who's here [10:17] Just going to say; I'm a huge fan. Thanks for all the work you have done. :) [10:25] many folks on this channel qualify for that :) [10:27] ogra, i still see dots :( [10:27] damn [10:27] it's probbly the GPS chatting away on ttyAMA and interfering with uboot [10:28] well, or just the wrong baud rate .... [10:28] i think uboot says "press a key to interrupt" and the GPS presses a key for me :) [10:28] first of all, drop the two "dtparam=" lines from config.txt [10:29] oh [10:29] hmm [10:32] thats tricky ... the stdout setting for uboot is hardcoded, we could only override it from uboot.env which is actually loaded after the prompt [10:32] (RaspberryPi2)ubuntu@localhost:~$ fw_printenv |grep stdout [10:32] stdout=serial,lcd [10:33] droppin serial from that would help for any later stuff but not for the prompt itself [10:33] lets see if the binary bootloader offers something to forcefully disble serial [10:35] i know there is a second serial port somewhere on these headers, perhaps we can force switch to that one [10:51] hmm, using the uart1 DT overlay makes my board hang on boot [10:52] oh, no, only the output :P [10:52] i can actually ssh in [10:58] sabdfl, so is there a chance to re-wire your gps hat to other pins ? [10:59] via the uart1 DT overlay we should be able to force the second serial port on ... [11:01] which can be configured for pin 32/33 instead of 14/15 [11:12] oh, wait ! [11:12] sabdfl, i just see we are actually loading uboot.env early enough for overriding the serial input ... [11:12] * ogra_ tries it out [11:27] sabdfl, try if: sudo fw_setenv bootdelay 0 [11:27] helps in any way [11:28] that should make it not listen to key presses (or other input) during boot [12:19] sabdfl, did you get my last messages ... ? "sudo fw_setenv bootdelay 0" should turn off the listening for input during boot, if your borad actually stops because the GPS sends chars that might solve it [12:20] hi ogra_ i missed that message but will try it when i am in budapest :) [12:20] safe flight :) [12:20] i hope so! [12:20] should be a good week, everyone seems well prepared [12:21] yeah, curious what you guys bring home :) [12:22] * ogra_ will have a joyful jaw surgery instead of enjoying hungarian beer :) === fginther` is now known as fginther [20:12] beuno: fyi, something weird is happening with the store: https://myapps.developer.ubuntu.com/dev/click-apps/3560/ [20:12] beuno: look at the feedback, there are two errors but its because the server traced back [20:13] beuno: the app itself is showing 'Pending review' still [20:18] jdstrand, right, the review failed and I guess it got stuck in pending review [20:18] pindonga, matiasb, ^^ [20:18] * beuno is off to bed [22:01] pindonga, matiasb (and beuno): fyi, the review failed, but not for the appropriate reasons-- ie, the scripts traced back for some weird reason (running the scripts locally, that doesn't happen) [22:51] beuno, if i do "snappy search oem" that doesnt find the pi2 oem snap, does the search not include types ? [22:52] (snappy search pi2 finds it ...)