**** BEGIN LOGGING AT Mon Jan 26 02:59:59 2015
Jan 26 03:17:13 <RangerGeek> Evening folks.  I made a booboo and i think borked by beaglebone by putting a bad line in my /etc/fstab.  When i open the micro in my ubuntu box I'm seeing 1 folder 'System Volume Information'.... which is clearly wrong. :/  Any way i can recover my boot?
Jan 26 03:55:03 <RangerGeek> when in doubt - reflash with a new distro to play with i guess. lol
Jan 26 03:58:16 <karki> ;)
Jan 26 04:35:01 <JamesJRH> Hi. Can anyone recommend me an open hardware cape or USB device capable of tuning into (at least) FM radio broadcasting?
Jan 26 04:36:09 <JamesJRH> Should I go the software defined radio route such as with the HackRF One? SDR sounds cool.
Jan 26 04:39:38 <JamesJRH> That will also open other possibilities such as tuning into television broadcast and perhaps being an open hardware celluar data modem which sounds fun. :-D
Jan 26 04:39:57 <JamesJRH> So versatile. :-D
Jan 26 04:48:25 <JamesJRH> I know that the HackRF One is open hardware. How easy is it to set it up for FM radio reception? Is it the only open hardware SDR available?
Jan 26 04:48:43 <JamesJRH> I've seen this: https://labs.mwrinfosecurity.com/blog/2014/06/18/beaglebone-black-gnu-radio-and-hackrf-one/
Jan 26 05:53:42 <tbr> JamesJRH: a simple realtek based dvb-t dongle would be sufficient. I think someone has done this on a beagle before.
Jan 26 05:54:00 <tbr> those can be used as wide band sdr
Jan 26 06:48:19 <JamesJRH> tbr: Are they open hardware? I'm only interested in supporting open hardware.
Jan 26 06:59:02 <tbr> JamesJRH: not sure if there are designs around the RTL chip that are OSHW
Jan 26 06:59:17 <tbr> JamesJRH: that would be an exercise for you to find one
Jan 26 07:00:15 <JamesJRH> What does RTL stand for? RealTek something?
Jan 26 07:00:37 <JamesJRH> What is HackRF based on?
Jan 26 07:00:57 <JamesJRH> s/HackRF/the HackRF One/
Jan 26 07:01:38 <kiran4399> Hello can anybody direct me to Victor Mayarolov or Siddarth Barath purohit ??
Jan 26 07:03:34 * tbr has no idea who those persons are
Jan 26 07:04:11 <tbr> JamesJRH: rtl-2832u is the chip
Jan 26 07:05:09 <JamesJRH> The chip for the HackRF One?
Jan 26 07:05:52 <tbr> no the chip that I mentioned earlier
Jan 26 07:10:32 <JamesJRH> I'm not sure what the L stands for.
Jan 26 07:12:11 <Humpelst1lzchen> thr rtl chip only costs 15 euro ;)
Jan 26 07:24:35 <JamesJRH> It appears that the HackRF One isn't based on a Realtek chipset: https://github.com/mossmann/hackrf/wiki/Hardware-Components
Jan 26 07:24:52 <JamesJRH> This looks interesting: http://openhpsdr.org/
Jan 26 07:28:02 * tbr never claimed that either
Jan 26 07:33:31 <JamesJRH> I didn't say you did. I'm just exploring. I'm not familiar with SDR.
Jan 26 07:34:22 <JamesJRH> Aah, GPL-like hardware licences: http://tapr.org/ohl.html
Jan 26 07:35:12 <JamesJRH> This is a great find; I will probably use these for my own designs.
Jan 26 16:04:24 <DiegoTc> hi av500, do you know if JKrinder has plans for the GSOC 2015 this year?
Jan 26 16:04:52 <Rotti> hi
Jan 26 16:08:54 <av500> DiegoTc: yes, he has
Jan 26 16:09:51 <DiegoTc> av500: I will like to help as a mentor, well if jkrinder thinks I will be good help
Jan 26 16:10:01 <DiegoTc> should talk with him then
Jan 26 16:13:54 <av500> DiegoTc: thx for the offer to help
Jan 26 16:15:45 <DiegoTc> do you know if there is page idea for the gsoc 2015?
Jan 26 16:17:38 <av500> DiegoTc: I dont think there is one yet
Jan 26 16:22:00 <DiegoTc> thabks av500, I will asked him when he is On
Jan 26 17:42:42 <ocamlman> Hello everyone - I'm having some trouble using GPIO from the PRU. I am using the BB-BONE-PRU-01 which uses p9_27 -- the code TODO:\n QBBS TODO, r31, 5 does not loop infinitely as I expect, whether p9_27 is attached to 3.3v or gnd
Jan 26 18:45:46 <Abhishek_> hi jkridner
Jan 26 18:51:58 <Humpelst1lzchen> Any recommendation for a fs to store the logs on an otherwise ro filesystem? Of course it should survive powerfailures...
Jan 26 19:16:07 <_av500_> Humpelst1lzchen: log partition
Jan 26 19:16:17 <_av500_> or cloud
Jan 26 19:16:50 <Humpelst1lzchen> network failures is what I want to log ;)
Jan 26 19:17:02 <_av500_> dot matrix printer?
Jan 26 19:17:11 <_av500_> 2nd BBB
Jan 26 19:17:55 <Humpelst1lzchen> thought about it, but usbstick with a log partition sounded cheaper ;)
Jan 26 19:20:47 <ocamlman> This GPIO/PRU issue is driving me crazy :p
Jan 26 19:20:56 <ocamlman> because I'm sure its a silly oversight
Jan 26 20:13:55 <Abhishek_> karki: Leaving a ping for you
Jan 26 22:31:39 <paul175> hi, does anyone know if the U-Boot source code at https://github.com/beagleboard/u-boot/tree/bone-bringup  is the correct U-Boot code that is shipped on the board?
Jan 26 22:42:48 <thurgood_> black or white?
Jan 26 22:43:11 <thurgood_> based on the date it looks like what was probably shipped with the white
Jan 26 22:44:15 <thurgood_> I /think/ you'll be better off looking at the denx version
Jan 26 22:44:54 <rcn-ee> paul175, that's way old..  use u-boot's git tree, you'll fine a patch under: /opt/source/
Jan 26 22:52:00 <paul175> oh this is for black
Jan 26 22:58:34 <ds2> why can't we as the beagle community get our act together and stop depending on specifics in u-boot?! it is a bootloader and that's all it is.
Jan 26 22:59:58 <rcn-ee> based on his info, he's probally building something and just needs the full source for certifcation..
Jan 26 23:00:46 <ds2> it is not just him...see too many problems being resolve with "gosh, that U-boot is too old". it is just a boot loader
Jan 26 23:01:04 <ds2> if a kernel gets into memory, that's it. its job is done. no more
Jan 26 23:01:13 <thurgood_> I've built stuff based on the xM that required u-boot modification... it happens
Jan 26 23:01:22 <ds2> fix the kernel
Jan 26 23:01:32 <ds2> there is absolutely no reason for that other then a broken kernel.
Jan 26 23:01:35 <rcn-ee> ds2, except with v2015.01, we can mount the eMMC over usb.. ;) so you don't even need a microSD card anymore. ;)
Jan 26 23:01:54 <thurgood_> the memory size and initial timings had to be set properly in uboot
Jan 26 23:02:00 <ds2> i.e. gigE on most newer u-boot for am335x is broken cuz of that very reason.
Jan 26 23:02:02 <paul175> well, I'm having a problem with getting the kernel to load where it gets an unrecognized machine ID
Jan 26 23:02:19 <ds2> thurgood_: that falls into - bootloader getting things into memory.
Jan 26 23:02:34 <ds2> paul175: that by defnition is a kernel problem.
Jan 26 23:02:35 <rcn-ee> paul175, in which case, your aren't loading the dtb.. your trying to load a 'board' file on a 'device tree' kernel..
Jan 26 23:02:51 <ds2> the bootloader should provide a proper and unique (per hw) machine ID
Jan 26 23:03:03 <ds2> duplicating it for derivative works is wrong.
Jan 26 23:03:09 <rcn-ee> unless the kernel guys deleted it.. aka board files..
Jan 26 23:03:28 <ds2> that is a kernel problem
Jan 26 23:03:28 <rcn-ee> and the user didn't enable append dtb config option, in which case, they need to laod the dtb binary..
Jan 26 23:03:53 <ds2> u-boot should be something that is romable
Jan 26 23:04:12 <rcn-ee> it's like systemd... u-boot keeps growing..
Jan 26 23:04:26 <paul175> is append dtb config option a u-boot or kernel option?
Jan 26 23:04:31 <ds2> that's a userland problem ;)
Jan 26 23:04:36 <rcn-ee> kernel option.
Jan 26 23:05:44 <paul175> so if  I have a dtb binary on my card, I don't use that option, I think that is where I'm at now
Jan 26 23:11:59 <rcn-ee> paul175, if you have the dtb, just use it, load it after the zImage and then use bootz to boot it: bootz 0x82000000 - 0x88000000
Jan 26 23:12:11 <rcn-ee> or just use the bootm/uImage instead of bootz/zImage...
Jan 26 23:12:38 <paul175> the bootz thing is what I'm trying to do now and I get some error about the machine ID
Jan 26 23:12:51 <paul175> Starting kernel ...
Jan 26 23:12:51 <paul175> Error: unrecognized/unsupported machine ID (r1 = 0x00000e05).
Jan 26 23:12:51 <paul175> Available machine support:
Jan 26 23:12:51 <paul175> ID (hex)        NAME
Jan 26 23:12:51 <paul175> ffffffff        Generic DT based system
Jan 26 23:12:52 <paul175> ffffffff        Generic DRA72X (Flattened Device Tree)
Jan 26 23:12:52 <paul175> ffffffff        Generic DRA74X (Flattened Device Tree)
Jan 26 23:12:53 <paul175> ffffffff        Generic AM43 (Flattened Device Tree)
Jan 26 23:12:53 <paul175> ffffffff        Generic OMAP5 (Flattened Device Tree)
Jan 26 23:12:54 <paul175> ffffffff        Generic AM33XX (Flattened Device Tree)
Jan 26 23:12:54 <paul175> Please check your kernel config and/or bootloader.
Jan 26 23:13:22 <rcn-ee> yeap... you just did: "bootz kernel_addr".. you need "bootz kernel_addr - ftd_addr"...
Jan 26 23:13:29 <rcn-ee> ftd/dtb....
Jan 26 23:17:04 <veremit> so you load kernel dtbs in uboot too, yes?
Jan 26 23:17:27 <veremit> rings a bell...
Jan 26 23:19:00 <paul175> yeah I have the address for the dtb in there, I think the address may have been incorrect though, checking
Jan 26 23:19:27 <veremit> it should match the previous lines in your boot script/config :p
Jan 26 23:24:33 <paul175> I had the device tree in memory lower than the kernel, not sure if that matters
Jan 26 23:25:08 <veremit> as long as neither overwrites :p
Jan 26 23:25:30 <paul175> changed it around and now I don't get any error message but it doesn't start, just freezes on starting kernel...
Jan 26 23:25:34 <veremit> but check the syntax of the bootm in case it makes some assumption
Jan 26 23:25:46 <veremit> well thats different
Jan 26 23:30:32 <ds2> sure the kernel isn't being relocated on top of your DT?
Jan 26 23:31:06 <ds2> mostly OT question - buy a robot mechanical platform or build one from scratch?
Jan 26 23:31:22 <veremit> build it ofc :P
Jan 26 23:31:57 <veremit> unless you just wanna use it .. then buy one :p
Jan 26 23:32:06 <ds2> the real debate is - recurse into yet another project or not
Jan 26 23:32:16 <ds2> it'd be a motion platform to experiment with some algs
Jan 26 23:32:37 <ds2> vision algs are more interesting when it does something physical with it
Jan 26 23:37:37 <paul175> thanks for your help
Jan 26 23:38:07 <veremit> nailed it?
Jan 26 23:38:24 <paul175> no, just taking a break
Jan 26 23:38:40 <veremit> ok :)
Jan 27 01:15:16 <jimi_hendrix> hey guys, i am trying to flash my BBB with ubuntu and i am getting some weird behavior
Jan 27 01:15:46 <jimi_hendrix> the lights wil blink for about 5 minutes and then all four go solid
Jan 27 01:16:00 <jimi_hendrix> i should expect tht should occur after 20-25 minutes
Jan 27 01:16:29 <jimi_hendrix> err
Jan 27 01:16:34 <jimi_hendrix> 25-45 minutes
Jan 27 01:17:25 <jimi_hendrix> then, when i reset the BBB, the lights continue to do the flashing thing for another 5 minutes then the same thing happens
Jan 27 01:17:28 <jimi_hendrix> is this ok?
Jan 27 01:17:33 <jimi_hendrix> or is something horribly wrong?
Jan 27 01:17:49 <veremit> something's wrong .. they should keep flickering if the board is alive
Jan 27 01:19:10 <jimi_hendrix> :/
Jan 27 01:20:25 <jimi_hendrix> veremit: any tips for figuring out what's up?
Jan 27 01:21:11 <veremit> ah with flashing, however, the four leds going solid .. usually means its complete
Jan 27 01:21:34 <veremit> you need to take the uSD out when you reboot to allow the board to boot .. else it will continue re0flashing
Jan 27 01:21:48 <veremit> which sounds like what's happening
Jan 27 01:22:42 <jimi_hendrix> hmm ok
Jan 27 01:22:48 <jimi_hendrix> so did the install just tae 5 minutes?
Jan 27 01:23:00 <jimi_hendrix> i removed the SD card and the usr lights are going like mad
Jan 27 01:23:25 <veremit> shouldn't take too long
Jan 27 01:23:37 <veremit> enough time to make a coffee :)
Jan 27 01:24:48 <jimi_hendrix> ok, well i have it hooked up to my computer again and am trying to run: ssh 192.168.7.2
Jan 27 01:24:55 <jimi_hendrix> and the terminal just hangs
Jan 27 01:26:24 <veremit> have you got a serial cable?
Jan 27 01:27:00 <jimi_hendrix> USB
Jan 27 01:27:01 <veremit> I'm not 100% sure the stock ubuntu has the same net config/etc as the standard .. but someone else can probably confirm/deny
Jan 27 01:27:21 <veremit> otherwise you to plug it into a router, check the router/s dhcp table for its IP
Jan 27 01:29:37 <veremit> gotta hit the hay .. good luck though .. should be something simple !
Jan 27 01:33:38 <RangerGeek> ok guys i'm pulling my hair out here.  my bb running kali REFUSES to connect via wpa_supplicant.
Jan 27 01:34:33 <RangerGeek> it keeps alternating between wlan0: associated and wlan0: disassociating from xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 27 01:50:26 <veremit> enable lots of debugging RangerGeek ..
Jan 27 01:50:44 <veremit> sounds like wirless authentication is going wrong
Jan 27 01:51:41 <veremit> and .. gone .. nite all I-)
Jan 27 01:51:58 <RangerGeek> veremit - sometimes i get blips of wlan0: authenticated though, it just keeps getting deauthed somehow.  no one else on my home network to be doing shenanigans.
**** ENDING LOGGING AT Tue Jan 27 02:59:58 2015