**** BEGIN LOGGING AT Mon May 04 02:59:59 2015 May 04 08:51:28 hmm, that's odd... May 04 10:26:37 has anyone gotten ofono to work ? May 04 10:34:14 that is such a broad question, I have no other recourse than just answer: May 04 10:34:17 "yes" May 04 10:41:45 hehe tbr May 04 10:41:52 I am sitting with a sim900 on ttyO1 May 04 10:42:04 I just wonder how I set it up to work with TCP May 04 10:42:39 ah, suddenly it boils down to a more refined issue May 04 10:42:51 does the module only have one UART? May 04 10:43:15 yes May 04 10:43:28 I made it work with AT commands and so on May 04 10:43:40 but that doesn't work well if you plan to run tcp services etc May 04 10:44:06 I added /etc/ofono/modem.config May 04 10:44:35 and to udev rules KERNEL=="ttyO1", ENV{OFONO_DRIVER}="sim900" May 04 10:44:53 it shows up in list-modems May 04 10:45:06 so I wonder where I go from there May 04 10:54:23 ah May 04 10:55:14 well now you need to control ofono. usually via dbus. but I think there are command line tools too May 04 10:55:57 yeah but it times out :-| May 04 10:56:00 when trying to enable May 04 10:56:08 so it seems like it doesn't manage to actually communicate May 04 11:48:32 ok, so RTC-only made actually still worked prior to revision A6 May 04 11:48:35 *mode May 04 12:07:52 rcn-ee.com/rootfs/bb.org/testing/2015-04-26/console/bone-debian-8.0-console-armhf-2015-04-26-2gb.img.xz May 04 12:07:53 rcn-ee.com/rootfs/2015-04-09/microsd/bone-debian-jessie-console-armhf-2015-04-09-2gb.img.xz May 04 12:08:00 What is the difference of the bb.org image? May 04 12:13:06 the date? May 04 12:18:24 the path and name is not the same, beside the date, so that is why I'm asking... May 04 13:03:32 Good day all,after attempting to install the latest Debian release to my BeagleBone Black it now refuses to boot normally. Upon statup LED's USR 0 and stays on and that is where she sits. Any help will be apprecited May 04 13:07:13 That is LED's USR 0 and 1 stays on May 04 13:19:25 woo, got rtc-only mode working on a rev C (with two hardware patches :P ) May 04 13:20:04 Archie: maybe incompatible u-boot ? May 04 13:20:44 check console output May 04 13:21:08 zmatt i have no idea,was working perfectly until i tried to install latest image May 04 13:21:31 Archie: define "latest image", and how did you install it? May 04 13:22:01 i have a cable attached to uart1 can send you the uboot console output May 04 13:22:43 wrote image to sd card, powered up pressing s2 and waited May 04 13:23:16 ah, sd-flasher... never used those May 04 13:23:35 just, use pastebin for the console output May 04 13:23:44 and again, what image exactly do you mean? May 04 13:23:52 is there a way i can recover it May 04 13:24:05 numerous May 04 13:26:09 the latest debian bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img May 04 13:26:47 Zmatt i am new to this could you please explain the use of pastebin, thank you May 04 13:28:32 it's a place where you can paste text to share with others May 04 13:28:37 http://pastebin.com/ May 04 13:29:54 okay i posted it May 04 13:30:29 now paste here the link :) May 04 13:31:34 http://pastebin.com/mw7mcBCg May 04 13:39:03 Archie: it found no bootable partition May 04 13:40:06 okay it also does not want to boot from the SD card either, any idea how i can fix this,it is a A5C bone with 2GB May 04 13:40:11 luckily as it mentioned it falls back to USB mass storage mode in this case, so if you connect it to usb it'll appear as a HD May 04 13:40:20 and inspect the problem May 04 13:41:03 starting with why you have two partitions, since I'm pretty sure current images have only one May 04 13:41:12 (at least all my beagles do) May 04 13:41:21 how do I know if the BB is being flashed? May 04 13:41:31 can I log in and check progress? :) May 04 13:41:36 i really have no idea, my first time using BBB May 04 13:43:13 is this not maybe because the image was a 4Gb image whilst the BBB only has 2GB? May 04 13:43:58 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 May 04 13:44:03 Archie: ...... May 04 13:44:23 Archie: if you have a 2GB BBB, obviously you cannot use a 4GB image May 04 13:44:28 use one of the 2GB images May 04 13:44:50 Yes Matt? May 04 13:45:08 i just realised that May 04 13:46:09 it helps talking to someone, let me give it a go and see if it works, thanks for listening and looking May 04 13:47:30 do a df -h May 04 13:47:33 and you'll see May 04 13:48:15 by the way if you interested i am in my stupidity building a cape that uses GPS and is centimeter accurate for autopilots used on drones May 04 13:52:55 pearl_: you wrote perl wrong May 04 14:06:40 hah, it works! I now have a beagle which turns itself off and on in an endless cycle (20 seconds on, 10 seconds off) using the RTC May 04 14:07:10 awesome May 04 14:07:13 free energy? May 04 14:07:24 powered with 3.6V May 04 14:08:36 zmatt: hurry, i think you can sell that to boeing! May 04 14:08:44 +111 May 04 14:08:56 make that 200days on May 04 14:09:21 and 100days off ;) May 04 14:09:38 boing might not like that part May 04 14:09:47 what I mean to say is: cool, rtc-only mode works, including timed power-on May 04 14:09:51 10s off mid-flight is funny enough May 04 14:10:06 zmatt: blog post? May 04 14:10:27 I'm not sure I entirely trust the current measurement, but it seems to be roughly 50 μA May 04 14:10:30 zmatt: who cares about what you want to say, when misinterpreting it is so much more funny? May 04 14:10:35 May 04 14:15:49 is there some way to disable the bbb on-board rtc clock without having to rebuild my own kernel? May 04 14:16:11 zmatt: ^^^ rtc question May 04 14:16:46 samael: why disable it rather than just not use it? May 04 14:19:26 because i have my own which is battery backed-up, and i need timedatectl (and the kernel automatic hctosys) to use it instead of the built-in one May 04 14:22:55 the udev way is not feasible because it cannot change the device name, and both timedatectl and the kernel relies on CONFIG_RTC_HCTOSYS_DEVICE which is set to rtc0 May 04 14:23:00 doesn't seem like it wants to flash at all... May 04 14:32:17 samael: disable it in device tree I guess? May 04 14:40:18 zmatt: i can try. but where can i find the device tree it is declared in? May 04 14:54:43 sorry I'm a bit distracted atm May 04 15:51:10 zmatt: +1 May 04 16:04:43 kotH: haha no. I meant pearl only May 04 17:18:25 Hi May 04 19:29:18 anyone running fc21 (3.18.9-200.fc21.armv7hl) on a bbb? or: what's the solution for: [ 111.823361] libphy: PHY 4a101000.mdio:00 not found May 04 19:29:50 /etc/udev/rules.d/ is emptt May 04 19:29:52 empty May 04 19:40:37 idwer generally speaking you're more likely to get help if you run the debian builds that more people are using (not a requirement but more eyes on it and all that) May 04 19:47:44 right May 04 19:48:17 that's the build from elinux.org you're referring to? May 04 19:57:15 oh now it came up :| May 04 19:57:18 bbb login: [ 31.386649] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off May 04 20:25:56 Hey, I’m trying to drive one of the UARTs with the PRU. Is there a way to set up the pinmuxing w/ devicetree without the kernel taking over and using it as a tty? May 04 20:26:02 sorry, new to systems programming May 04 20:35:10 AFAIK if you pinmux it as a serial port the main core is going to try to make it a serial port, available to the kernel, not the pru May 04 20:46:34 thurgood_: you don't happen to run debian on bbb, do you? May 04 20:47:25 when I use the bbb, yes... I use a beagleboard based board mostly though May 04 20:47:57 my bbb distro is a bit behind the times :/ May 04 20:48:11 is CONFIG_USB_G_DBGP used in /boot/config-* ? May 04 20:49:38 thurgood_ so there’s no way to connect up the output pins without the kernel trying to grab it? May 04 21:39:50 bummer, mk_mmc.sh doesn't yet seem to run on archlinux May 04 21:42:56 idwer, patches welcome, you'll need mkimage/dpkg.. ;) May 04 21:44:43 luckily there is an aur for dpkg :) May 04 21:45:51 much of the script also checks version, so as long as you have the packages installed it should work.. May 04 21:46:13 iirc there was a prebuilt .xz image somewhere May 04 21:46:51 are you looking for a specific build? May 04 21:47:17 any build that has CONFIG_USB_G_DBGP listed in in /boot/config-* May 04 21:47:59 http://www.coreboot.org/EHCI_Gadget_Debug#Tested_hardware May 04 21:48:15 anything soon-ish has that by default so... http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases May 04 21:49:07 3.8.13-bone69 was the first v3.8.x with that config enabled.. May 04 21:49:29 So anything after Jan 1st, pretty much as that config enabled.. May 04 22:09:12 rcn-ee: earlier I wiped the emmc, are there post-installation steps involved? "Bad Linux ARM zImage magic!" May 04 22:12:21 bad uboot for zimage .. May 04 22:12:35 probably expecting a uimage .. May 04 22:12:57 idwer, just factory reflash the eMMC... May 04 22:14:25 rcn-ee: i finally figured out how to wipe the u-boot env from the eMMC from the u-boot prompt May 04 22:15:05 vagrantc, did u-boot grow dd? ;) May 04 22:15:12 rcn-ee: mmc erase May 04 22:15:28 ah, yeah that should work. ;) May 04 22:15:45 i was never able to do it from linux, as i couldn't write to the /dev/mmcblk*boot* devices May 04 22:15:53 writing to /dev/mmcblk0 didn't do anything May 04 22:16:15 weird, as we shouldn't be using the *boot* device.... May 04 22:16:19 so linux represents them as read-only devices May 04 22:16:50 well, reading the u-boot sources, i finally figured out what to write to using mmc erase May 04 22:17:08 only been trying to figure that out for the past 13 months or so May 04 22:17:39 nice! Don't you hate those bugs/missing docs. ;) May 04 22:17:59 rcn-ee: you've just disabled the saveenv functionality on your u-boot builds? May 04 22:19:08 vagrantc, i think we can bring it back, there was a weird bug in one of the previous u-boot versions, where with that enabled, it wouldn't boot off eMMC... May 04 22:20:07 haven't had problems with that with the u-boot builds in debian on the BBB as long as I can recall May 04 22:20:27 which maybe goes back to u-boot 2013.10 or so? May 04 22:20:48 looking at my notes, it was in: v2015.01 May 04 22:23:21 ah, i think i pretty much skipped that version May 04 22:24:52 oh you missed all the -rc fun in that one.. ;) .04 was boring.. ;) May 04 22:26:00 i'll remove #define CONFIG_ENV_IS_NOWHERE and give .04 a workout tomorrow on the bbb, it should be fine as your using it. ;) May 04 22:27:06 of course, i find saveenv is mostly a tool to shoot myself in the foot, since i almost exclusively want to test the default environment May 04 22:27:19 (the bug i saw with v2015.01: on bootup, with just u-boot dd'ed to eMMC, it would hard lockup looking for the enviorment..) May 04 22:31:53 rcn-ee: clueless question, but can you do that from uboot? May 04 22:34:21 idwer, depends.... with v2015.01 you can.. just need the usb-slave port connected to your pc and run: ums 0 mmc 1 May 04 22:34:25 it's about 2x slower... May 04 22:35:21 yeah - this is 2015.01-00001-gb2412df ;) May 04 22:35:42 with uart attached May 04 22:35:53 give it a shot.. your bbb should show up as a flash drive when you run that.. May 04 22:36:32 \running home, back later May 04 22:43:05 not sure what that should show: May 04 22:43:08 U-Boot# ums 0 mmc 1 May 04 22:43:08 UMS: disk start sector: 0x0, count: 0x394000 May 04 22:43:08 \ May 04 22:43:16 still spinning May 04 22:46:02 if you plug a computer into the otg port it should show up as a disk now. May 04 22:49:24 it's there May 04 23:12:10 looks like this image, bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz, doesn't ship scripts/tools/eMMC/init-eMMC-flasher-v3.sh May 04 23:12:20 yes, it was handled with xz :) May 04 23:12:52 tools/ is not there May 04 23:39:37 should probably get BBB-eMMC-flasher-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz instead **** ENDING LOGGING AT Tue May 05 02:59:59 2015