**** BEGIN LOGGING AT Sun Nov 08 02:59:58 2015
Nov 08 03:23:47 <Set_> Hello...
Nov 08 03:24:32 <Set_> I was working out of the Make: Getting Started with Beaglebone book.
Nov 08 03:24:40 <Set_> I came to...scratch that.
Nov 08 03:24:56 <Set_> I am working out of a book, "Beaglebone Robotic Projects."
Nov 08 03:25:08 <Set_> It is published from packtpub.com.
Nov 08 03:25:49 <Set_> I am on a section. I need to set up my mic and speaker.
Nov 08 03:26:12 <Set_> I cannot get this mic or speaker to understand that it is attached. I tried multiple times.
Nov 08 03:26:25 <Set_> Besides that...Geaux Beaglebone Black.
Nov 08 03:28:13 <Set_> p. 72 on "Beaglebone Robotic Projects" describes what to do. I have followed instruction.
Nov 08 03:29:05 <Set_> So...I kept trying. I kept up the "good effort." I am using nano to produce scripts for now. I have a model with Angstrom and a model with Debian.
Nov 08 03:29:33 <Set_> I am updating the package of Angstrom to Debian now, i.e. I will have two with Debian.
Nov 08 03:29:48 <Set_> Okay...so! Does anyone follow this book?
Nov 08 03:32:54 <Set_> The book is about a Robot with the BBB brain/MCU. Does anyone follow or use, "Beaglebone Robotic Projects?"
Nov 08 03:39:15 <Set_> Oh and I forgot. I had to use the Debian BBB to work on this book. My Angstrom BBB does not do it for this book.
Nov 08 03:48:03 <veremit> Set_ .. the software is evolving quite quickly .. what are you having problems with?
Nov 08 03:48:12 <Set_> I use "alsamixer" to command via "aplay" in the command line. I have not been able to play a .wav file.
Nov 08 03:49:05 <Set_> I have to play the .wav file to move on. The played .wav file gives me an idea on what will be the output when I give it commands.
Nov 08 03:50:17 <Set_> I am going to command this robot with talk and it will give me an ouput to let me know what it will do.
Nov 08 03:50:37 <veremit> what error message if any are you getting? or just no sound?
Nov 08 03:50:47 <Set_> Just no sound.
Nov 08 03:51:14 <Set_> I can hear feedback but no sound.
Nov 08 03:51:22 <veremit> feedback?!
Nov 08 03:51:40 <Set_> Yea...the feedback is when I put my hands too close to the device/speaker.
Nov 08 03:52:28 <Set_> I have a chipset device that I can plug into my bone via USB. The device has output/speaker and input/mic.
Nov 08 03:52:28 <veremit> interesting
Nov 08 03:52:54 <Set_> Yep.
Nov 08 03:53:41 <Set_> So...I get to alsamixer and configure it. I then click aplay and the .wav file to play it.
Nov 08 03:53:47 <veremit> what do you get from "aplay -l" and "aplay -L"
Nov 08 03:53:58 <veremit> do you see the right card selected as 'sysdefault' ?
Nov 08 03:54:15 <Set_> Um...dang it.
Nov 08 03:54:29 <veremit> alsa requires a fair bit of manual configuration .. and I would suspect it wants to send sound down the HDMI ( as for some reason, everything does...)
Nov 08 03:54:33 <Set_> I am using my Angstrom to get it  updated to Debian now.
Nov 08 03:54:56 <Set_> I can see what happens later and get back on here.
Nov 08 03:55:07 <Set_> But...what was supposed to happen did happen.
Nov 08 03:55:21 <Set_> I have the exact same thing for output that is described.
Nov 08 03:55:48 <Set_> The page in the book has a picture. My output from the terminal and command line are the same.
Nov 08 03:56:02 <veremit> eg. for my desktop I have "aplay -l" gives .. http://pastebin.com/2B9zicbc
Nov 08 03:56:12 <veremit> just apt-get alsaplayer on my beagle .. hold on ..
Nov 08 03:56:29 <Set_> Okay...hold on. I am going to connect my other bone real quick.
Nov 08 03:56:52 <veremit> bugger .. wrong package set ..
Nov 08 03:56:54 <veremit> lol
Nov 08 03:57:21 <veremit> fyi .. aplay is part of 'alsa-utils' package :D
Nov 08 03:57:38 <Set_> Yep...I have been trying to upgrade my Angstrom too. It has not worked in the last three tries.
Nov 08 03:57:53 <veremit> Unless you really want to persevere with Angstrom, I'd ditch it.
Nov 08 03:58:03 <GrumpeiYokoi> As in, opkg upgrade?
Nov 08 03:58:07 <GrumpeiYokoi> I wouldn't recommend it
Nov 08 03:58:10 <Set_> I am...I am ditching it as we speak.
Nov 08 03:58:36 <GrumpeiYokoi> Depending on the device rev, it takes forever and you usually run out of space on eMMC
Nov 08 03:58:44 <veremit> I'd recommend downloading a fresh image from http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03 .. write a uSD card, update the flash to latest debian
Nov 08 03:58:48 <Set_> Okay...I signed into my Debian image BBB with PuTTY. now.
Nov 08 03:58:49 <GrumpeiYokoi> Haven't used Angstrom on a Rev C
Nov 08 03:59:01 <Set_> Nope.
Nov 08 03:59:02 <veremit> not forgetting to hold the BOOT button whilst applying power to boot the new image :D
Nov 08 03:59:10 <Set_> I remembered.
Nov 08 03:59:14 <veremit> [ 3:58am] root@beagleblack ~ # aplay -l
Nov 08 03:59:15 <veremit> aplay: device_list:252: no soundcards found...
Nov 08 03:59:19 <veremit> well .. that's really helpful
Nov 08 03:59:33 <Set_> Okay...I will go to aplay -l
Nov 08 03:59:35 <veremit> but then mine is a bare console image lol
Nov 08 03:59:39 <Set_> I will let you know what I find.
Nov 08 04:00:12 <Set_> card 0: Black [TI BeagleBone Black], device 0: HDMI nxp-hdmi-hifi-0 []   Subdevices: 1/1   Subdevice #0: subdevice #0
Nov 08 04:00:41 <Set_> That is with nothing plugged in. Let plug in what I need and play alsamixer real quick.
Nov 08 04:02:39 <Set_> card 0: Black [TI BeagleBone Black], device 0: HDMI nxp-hdmi-hifi-0 []   Subdevices: 1/1   Subdevice #0: subdevice #0 card 1: Set [C-Media USB Headphone Set], device 0: USB Audio [USB Audio]   Subdevices: 1/1   Subdevice #0: subdevice #0
Nov 08 04:03:03 <Set_> ...that is with the device plugged in and the alsamixer updated and configured.
Nov 08 04:04:05 <veremit> ok .. alsamixer won't set your default alsa device
Nov 08 04:04:23 <veremit> now .. it depends whether the usb is going to override the on-board hdmi that you can see .. or not.
Nov 08 04:04:35 <Set_> Oh.
Nov 08 04:04:49 <Set_> The power LED shows on the USB device.
Nov 08 04:04:59 <veremit> otherwise, you will get the problem as you seee .. no audio from the usb .. and you'll probably find its out on the hdmi if you have it :)
Nov 08 04:05:31 <Set_> Dang it. So...I should get a micro-HDMI dongle?
Nov 08 04:05:44 <Set_> Well...micro-HDMI to USB?
Nov 08 04:06:06 <veremit> From the alsa docs .. http://alsa.opensrc.org/Hotplugging_USB_audio_devices_%28Howto%29
Nov 08 04:06:12 <veremit> but that looks moderately horrible
Nov 08 04:06:21 <Set_> Awesome...
Nov 08 04:06:29 <Set_> I am going to go to the site later.
Nov 08 04:06:34 <Set_> I will read up.
Nov 08 04:08:09 <Set_> Hey...how did you know of the alsa.oprnsrc.org site?
Nov 08 04:09:07 <Set_> Anyway...let me undock this BBB. I will be back at Set_ later.
Nov 08 04:09:29 <veremit> google is a powerful tool :)
Nov 08 04:09:40 <veremit> this page is quite good .. but a bit complicated and lengthy .. https://hifiduino.wordpress.com/2014/03/27/beaglebone-black-navigating-the-audio-maze/
Nov 08 04:09:57 <Set_> I have to see if the reason for it not downloading the Debian image is the chat I am in.
Nov 08 04:10:03 <Set_> Okay...I will be right back.
Nov 08 04:10:06 <veremit> k
Nov 08 04:25:10 <zmatt> morning
Nov 08 04:25:14 <zmatt> an, audio
Nov 08 04:25:58 <zmatt> I recently added McASP's IOsets to my pins spreadsheet... they're really weird
Nov 08 04:32:41 <veremit> yo zmatt... got audio in your io thingy?
Nov 08 04:32:51 <veremit> not the sheet .. the other driver doo-dah
Nov 08 05:22:32 <zmatt> sorry, briefly fell asleep again
Nov 08 05:22:37 <zmatt> other driver doo-dah?
Nov 08 05:42:34 * zmatt pokes veremit 
Nov 08 05:42:51 <veremit> that io thingy driver .. damnt I need cofee ..
Nov 08 05:43:06 <veremit> interface code
Nov 08 05:43:18 <veremit> gawd I'm bein thick today
Nov 08 05:45:08 * zmatt gropes around in the space of meaning
Nov 08 05:45:22 <zmatt> you mean whether I have a header file for McASP ?
Nov 08 05:46:48 * zmatt uses a straw to blow some caffeine powder into veremit's nose
Nov 08 05:46:49 <zmatt> :P
Nov 08 05:47:14 <veremit> intravenous drip would be good right now I think
Nov 08 05:49:03 <zmatt> caffeine is well-enough absorbed by the more usual routes
Nov 08 05:50:08 <zmatt> (it has the benefit of actually being absorbed in the stomach already instead of having to wait till the upper intestine as most amines do)
Nov 08 05:50:49 <veremit> lol ok ok
Nov 08 05:50:58 <veremit> just workin on a boost threading headache :(
Nov 08 05:51:17 <zmatt> boost... threading....
Nov 08 05:51:19 <veremit> somehow there is a gotcha in a simple function called 'sleep' :(
Nov 08 05:51:37 <zmatt> I don't think any amount of caffeine is going to help you with that
Nov 08 05:51:41 <veremit> but they were obviously in a transition period when this code was written .. into the Chronos lib
Nov 08 05:51:49 * veremit grumbles
Nov 08 05:52:19 <veremit> but I'm truely no good at classes in c++
Nov 08 05:52:35 <zmatt> I'm not even sure if sleep() is thread-safe, portably
Nov 08 05:52:45 <veremit> hence I suspect no amount of caffeine will help me
Nov 08 05:52:54 <veremit> well .. I think this was the objective ..
Nov 08 05:53:14 <veremit> clearly there were some changes going on in v1.52
Nov 08 05:53:36 <zmatt> oh wait, you mean boost has a sleep function? (rather than the POSIX sleep function)
Nov 08 05:53:45 <veremit> well .. 1.5->1.52 .. I think it was all fixed by 1.53 .. but this build is mostly broken for upgrading
Nov 08 05:53:47 <veremit> zmatt.. yes
Nov 08 05:53:56 <zmatt> then I don't know
Nov 08 05:54:00 <zmatt> threads are evil anyway
Nov 08 05:54:44 <zmatt> but you still haven't clarified the meaning of your mcasp-related inquiry... you left my last guess without confirmation
Nov 08 05:55:09 <veremit> http://www.boost.org/doc/libs/1_52_0/doc/html/thread/thread_management.html#thread.thread_management.thread.sleep
Nov 08 05:55:14 <veremit> yeah threading is a nightmare
Nov 08 05:55:25 <veremit> oh .. scratch that .. it wasn't important anyway lol
Nov 08 05:56:12 <veremit> its a linker error that's floored me .. just cannot figure out why
Nov 08 05:56:19 <veremit> the makefile -looks- right
Nov 08 05:56:22 <zmatt> since yes I do have one, but it's covered in a layer of dust since I last used it on the C674x DSP present on the DM8148
Nov 08 05:57:15 <zmatt> does contain nice comments like
Nov 08 05:57:20 <zmatt> // ... don't look at me like that, I didn't make this shit up ↑
Nov 08 05:58:53 <veremit> bugger .. who's inadvertently triggering my ignores today :/
Nov 08 05:59:54 <zmatt> when? (and how do you know?)
Nov 08 06:00:25 <zmatt> the two of us are the only ones who have spoken here since your conversaion with Set_
Nov 08 06:00:43 <veremit> oh good :p
Nov 08 06:02:49 <zmatt> also you can't just say "scratch that" ... making an unclear inquiry and then revoking it leaves unresolved tension
Nov 08 06:02:53 <zmatt> :P
Nov 08 06:03:18 <zmatt> the linker errors are probably due to the universe punishing you for that
Nov 08 06:04:21 <veremit> the universe is a cruel place .. and I Just Did [scratch that] :p
Nov 08 06:05:22 <veremit> to return to that topic, then ... we were talking about an interface you'd created to am335x peripherals that linked the DT and not /dev/mem .. mapping registers if I recall
Nov 08 06:05:48 <veremit> my brain will not recall the missing chunks :(
Nov 08 06:05:56 <veremit> /dev/mem corruption I say
Nov 08 06:05:57 <zmatt> well I created two things
Nov 08 06:06:15 <zmatt> which you may be confusing, and in fact need to be merged (but this hasn't been done yet)
Nov 08 06:07:56 <zmatt> I made libsubarctic that lets me use baremetal headers in userspace by using /dev/mem to mmap() the peripherals used in the application during early initialization before main is called, thus allowing exactly the same code to work on baremetal and in userspace linux (as long as no irqs are involved)
Nov 08 06:09:21 <zmatt> and I use uio to make peripherals show up as shiny /dev/uio/* devices that avoid the need for /dev/mem (hence root perms) and also let you receive irqs in userspace
Nov 08 06:10:11 <veremit> yes, the uio .. it has a 'u' in it damnit
Nov 08 06:10:22 <zmatt> (also makes the kernel automagically enable the module clock for you when you open the device etc)
Nov 08 06:10:39 <veremit> the libsubarctic I didn't know .. and sounds cool too
Nov 08 06:11:51 <veremit> uhoh .. is it a limit on my gcc .. noo.. can't be.
Nov 08 06:12:13 <zmatt> libsubarctic is used in https://github.com/dutchanddutch/jbang
Nov 08 06:12:24 <zmatt> though with a limited set of headers
Nov 08 06:12:47 <veremit> ok not gcc .. c++11 was gcc-4.7
Nov 08 06:13:37 <zmatt> (jbang needs at least 4.9, or possibly I may already depends on 5 ... I never test with 4.9 anymore, don't have it installed even)
Nov 08 06:13:51 <zmatt> *it may already depend
Nov 08 06:15:02 <zmatt> for c++ you generally don't want to use an old gcc version, c++ has been on the move pretty fast and a lot of stuff introduced that's actually _useful_
Nov 08 06:16:39 <zmatt> especially metaprogramming has been made a lot saner with 'constexpr' letting you write stuff to be evaluated at compile-time in plain c++ instead of having to abuse the template engine as some sort of half-baked dialect of prolog as was previously done :P
Nov 08 06:18:39 <zmatt> gcc 4.7 did not have full c++11 support
Nov 08 06:19:26 <zmatt> you need 4.8.1 for that
Nov 08 06:24:00 <zmatt> especially a lot of concurrency-related c++11 stuff is still missing in 4.7
Nov 08 06:24:32 <zmatt> didn't your problems involve threading? :P
Nov 08 06:30:19 * zmatt pokes veremit 
Nov 08 06:30:56 <zmatt> just don't use ancient compilers.... I think 4.7 was released shortly after God said Let There Be Light or something
Nov 08 06:31:39 <GrumpeiYokoi> 4.7 seemed new and spiffy to me at one time <__<
Nov 08 06:31:40 <GrumpeiYokoi> >______>
Nov 08 06:32:00 <zmatt> hehe
Nov 08 06:32:02 <GrumpeiYokoi> But it was frustrating because you'd see some shiny C++11 feature somewhere and it wouldn't work
Nov 08 06:32:15 <zmatt> yeah same with c++14 and 4.9
Nov 08 06:32:19 <veremit> GRRr wrong bloody makefile :(
Nov 08 06:32:47 <veremit> 4.8.4 is going here
Nov 08 06:32:50 <veremit> gcc that is
Nov 08 06:33:05 <GrumpeiYokoi> If c++ continues to evolve well maybe someday we won't ever need a Boost library
Nov 08 06:33:23 <GrumpeiYokoi> j/k
Nov 08 06:33:46 <GrumpeiYokoi> It completely exists to push the limits of sane things you should do with C++ :(
Nov 08 06:34:16 <zmatt> c++ is still a depraved... vile... language, and I really wish for a better alternative
Nov 08 06:34:28 <GrumpeiYokoi> I have a bit of dislike for Boost, but mainly because I think their documentation has a lot of breadth but very little depth.
Nov 08 06:34:30 <zmatt> but for now it seems I'm stuck with it
Nov 08 06:35:17 <GrumpeiYokoi> I was trying to figure out how to use the Spirit parsing library, among other things. Their tutorials explain pretty well how to use it if you have the *exact same use cases that they thought of in the tutorial*
Nov 08 06:35:22 <zmatt> I only once briefly looked at boost to avoid writing my own invasive containers, but the lib was too verbose and messy and it ended up being simpler just implementing what I actually needed
Nov 08 06:35:24 <GrumpeiYokoi> Otherwise it seemed to me like you were out of luck
Nov 08 06:35:57 <GrumpeiYokoi> And I wasn't about to wade through the miles of template code to figure out what I was  doing wrong in my use cases
Nov 08 06:37:01 <GrumpeiYokoi> And I didn't just give up in an afternoon. It took 3 or 4 weeks for me to say the hell with it.
Nov 08 06:37:35 <GrumpeiYokoi> And... rolled my own like you did XD
Nov 08 06:37:55 <zmatt> with metaprogramming moving more from templates to plain c++, perhaps some day we'll actually be able interact with the compiler as a service at compile-time
Nov 08 06:38:06 <zmatt> that would be nice
Nov 08 06:38:19 <GrumpeiYokoi> Totally, yeah
Nov 08 06:38:24 <GrumpeiYokoi> Or even run time, in some cases
Nov 08 06:38:34 <zmatt> that pulls in some heavy dependencies though
Nov 08 06:38:40 <GrumpeiYokoi> (with the understanding that you'd take a hefty performance hit)
Nov 08 06:39:03 <Set_> Hello...
Nov 08 06:39:30 <Set_> How are people...heh?
Nov 08 06:39:32 <veremit> HELL YEAH
Nov 08 06:39:37 <veremit> Top level makefile fail ..
Nov 08 06:39:43 <veremit> feckin qt apps
Nov 08 06:40:08 <Set_> I got nowhere so far.
Nov 08 06:40:14 <zmatt> GrumpeiYokoi: it will help a lot of you don't have to parse at runtime, but e.g. hand over a lambda and get it to constant-fold the captured values and reoptimize
Nov 08 06:40:41 <zmatt> GrumpeiYokoi: but you're still looking at pulling in a BIG library
Nov 08 06:40:46 <Set_> I did research the idea. I got the idea that USB is not liked in alsamixer.
Nov 08 06:40:51 <GrumpeiYokoi> Certainly
Nov 08 06:41:00 <zmatt> Set_: should work
Nov 08 06:41:02 <GrumpeiYokoi> You wouldn't want to do something like willy nilly
Nov 08 06:41:14 <zmatt> GrumpeiYokoi: C++ parser is horror though
Nov 08 06:41:41 <veremit> zmatt .. we had a problem with getting alsa to default to a usb sound device
Nov 08 06:41:42 <GrumpeiYokoi> Yeah, probably better off embedding Python I guess
Nov 08 06:42:12 <Set_> Um...is upgrading to Debian while online frowned upon or can I upgrade to Debian while plugged in via USB?
Nov 08 06:42:15 <zmatt> GrumpeiYokoi: well then you're in a different application domain than C++ though
Nov 08 06:42:37 <veremit> Set_ .. define "upgrading to debian"
Nov 08 06:42:53 <Set_> I am just flashing via MicroSD to my BBB.
Nov 08 06:43:31 <Set_> It is like my eighth write and deploy. That damn system does not like my BBB.
Nov 08 06:43:52 <zmatt> GrumpeiYokoi: like, my baremetal tests are often just a few KB of compiled code
Nov 08 06:44:05 <Set_> The write is successful. I follow the "hold down the boot" button instruction.
Nov 08 06:44:09 <GrumpeiYokoi> Okay then Lua XD
Nov 08 06:44:12 <Set_> Yes...Boo!
Nov 08 06:44:18 <GrumpeiYokoi> That certainly compiles down much smaller than Python
Nov 08 06:44:22 <zmatt> GrumpeiYokoi: and my baremetal codebase currently does not define any heap (any direct or indirect calls to malloc() or operator new would result in a link error)
Nov 08 06:44:54 <GrumpeiYokoi> you clearly have a much different set of requirements than what I normally program under
Nov 08 06:44:56 <veremit> not sure flashing emmc whilst on usb power is optimal .. <shudder>
Nov 08 06:45:04 <GrumpeiYokoi> You have a kernel in there right zmatt?
Nov 08 06:45:24 <Set_> Yep...I know now. I got it powered via 5V now.
Nov 08 06:45:40 <zmatt> veremit: its max consumption is ~100 mA
Nov 08 06:45:41 <GrumpeiYokoi> *there, right, ...
Nov 08 06:45:41 <Set_> I have to wait about 45 minutes again (again, again, again). Yikes.
Nov 08 06:46:00 <zmatt> 45 minutes? to flash a system? o.O
Nov 08 06:46:10 <veremit> no...
Nov 08 06:46:16 <Set_> I got the oldest, maybe the second one.
Nov 08 06:46:29 <Set_> It says the number two on it.
Nov 08 06:46:30 <veremit> 2gb version
Nov 08 06:46:31 <veremit> should be fine
Nov 08 06:46:43 <Set_> I guess.
Nov 08 06:46:44 <GrumpeiYokoi> I think some of the old docs said it took 45 minutes
Nov 08 06:46:45 <zmatt> GrumpeiYokoi: nothing worthy of that name
Nov 08 06:46:46 <veremit> which revision?? should be on a sticker on the side ...
Nov 08 06:47:00 <GrumpeiYokoi> zmatt: hardcore
Nov 08 06:47:01 <zmatt> GrumpeiYokoi: just irq dispatching
Nov 08 06:47:04 <Set_> It is the oldest.
Nov 08 06:47:13 <Set_> I think it was A.
Nov 08 06:47:21 <GrumpeiYokoi> Show me how you do that sometime
Nov 08 06:47:42 <GrumpeiYokoi> I've flashed emmc numerous times and I don't think it ever really took that long
Nov 08 06:47:42 <Set_> Oh...I tried to get an e-mail server running.
Nov 08 06:47:46 <GrumpeiYokoi> Maybe 10 to 20 minutes
Nov 08 06:47:57 <Set_> On the BBB.
Nov 08 06:48:14 <Set_> I got that script and a bunch of seconds later...nothing.
Nov 08 06:48:17 <Set_> No e-mail. Boo!
Nov 08 06:48:18 <GrumpeiYokoi> Don't quote me on that. Usually I'd put a flasher image in, go get some coffee, do some emails, then check back on it at some point later
Nov 08 06:48:25 <GrumpeiYokoi> Sometimes the system would crash though
Nov 08 06:48:35 <Set_> Yikes.
Nov 08 06:48:36 <GrumpeiYokoi> So maybe factoring in the crashes when writing it's 45 minutes?
Nov 08 06:48:41 <zmatt> if I reflash I do so using BBBlfs
Nov 08 06:49:48 <Set_> My flash is still running.
Nov 08 06:49:57 <Set_> It has been about 20 minutes.
Nov 08 06:50:01 <zmatt> also excellent for recovery, especially since I discovered you can easily "enter" the system using systemd-nspawn (or even just chroot though you'll want to mount /proc and such)
Nov 08 06:50:45 <zmatt> just need to install qemu-user-static and copy /usr/bin/qemu-arm-static to usr/bin of the target fs
Nov 08 06:51:04 <zmatt> binfmt will do the rest for you
Nov 08 06:52:08 <Set_> Um...I can just flash the eMMC with a new image without updating past images right?
Nov 08 06:52:30 <Set_> Like...I can skip Angstrom.xxx to go to Debian, right?
Nov 08 06:52:35 <GrumpeiYokoi> It compltely overwrites the eMMC
Nov 08 06:52:39 <GrumpeiYokoi> afaik
Nov 08 06:52:45 <Set_> Yep.
Nov 08 06:52:52 <Set_> That is the idea.
Nov 08 06:52:57 <GrumpeiYokoi> So it would be irrelevant
Nov 08 06:52:59 <GrumpeiYokoi> So yes
Nov 08 06:53:04 <Set_> It has not worked.
Nov 08 06:53:19 <Set_> Those lights are still blinking.
Nov 08 06:53:27 <GrumpeiYokoi> In what fashion are they blinking?
Nov 08 06:53:44 <Set_> Heart rate pulses or something like that.
Nov 08 06:53:56 <veremit> do you have a serial debug cable?
Nov 08 06:54:01 <Set_> Yep.
Nov 08 06:54:02 <GrumpeiYokoi> The most recent flasher image I used when it was running scrolled the LEDs side to side
Nov 08 06:54:11 <Set_> Hmmm.
Nov 08 06:54:12 <veremit> the flashing process will complete once all are on/off or ... That...
Nov 08 06:54:21 <GrumpeiYokoi> like, 1, 2, 3, 4, 3, 2, 1 (repeat)
Nov 08 06:54:32 <GrumpeiYokoi> That seemed different from the previous ones, but I'm not sure
Nov 08 06:54:37 <veremit> I like flashing over bbblfs :D
Nov 08 06:54:40 <GrumpeiYokoi> And all the lights were off after it was complete
Nov 08 06:54:49 <Set_> I think they are supposedly supposed to all be on.
Nov 08 06:54:54 <Set_> Dang it.
Nov 08 06:54:59 <Set_> I will just wai.t
Nov 08 06:55:00 <zmatt> GrumpeiYokoi: btw, I once made a really really trivial irq-driven example in pure assembly -> https://e2e.ti.com/support/arm/sitara_arm/f/791/p/360758/1655101#1655101
Nov 08 06:55:03 <GrumpeiYokoi> I think the old images did that Set_
Nov 08 06:55:13 <Set_> oh.
Nov 08 06:55:51 <Set_> Dang it man. I am freekin' out over this new image.
Nov 08 06:56:01 <Set_> Can you e-mail yourself with your BBB?
Nov 08 06:56:15 <Set_> in nano?
Nov 08 06:56:18 <GrumpeiYokoi> I'm just telling you what the July 2015 debian flasher image did when i was using it recently
Nov 08 06:56:18 <Set_> Hhaahah.
Nov 08 06:56:21 <zmatt> GrumpeiYokoi: if you use the old makefile that's still included (mv old/* .) it will also build an MLO you can put on an sd card to boot from
Nov 08 06:56:26 <Set_> Okay.
Nov 08 06:56:55 <GrumpeiYokoi> zmatt: As an SNES enthusiast, I've been meaning to look at that BeagleSNES project
Nov 08 06:57:03 <Set_> I am a new person in the Linux era, i.e. I know you know.
Nov 08 06:57:06 <Set_> Cool.
Nov 08 06:57:21 <GrumpeiYokoi> I was going to look at whether it was a custom baremetal-ish OS
Nov 08 06:57:30 <GrumpeiYokoi> But mainly I work with BBBs at work
Nov 08 06:57:42 <GrumpeiYokoi> I have a few of the older ones they just let me have for home though
Nov 08 06:58:08 <Set_> Cool...they are nice when trying out new software and making things stop and start.
Nov 08 06:58:10 <zmatt> GrumpeiYokoi: the demo.bin generated (by either old or simplified new Makefile) is for peripheral booting: I normally have ROM netboot the image
Nov 08 06:58:11 <veremit> I *LOVE* how the official BBB updating guide is from 2013 .. angstrom .. and completely irrelevant
Nov 08 06:58:18 <GrumpeiYokoi> Set_: I would say if you're seeing the double heart beat signature then it is likely not flashing the eMMC
Nov 08 06:58:25 <veremit> http://elinux.org/Beagleboard:Updating_The_Software .. its a classic
Nov 08 06:58:41 <Set_> Yea...you are probably right.
Nov 08 06:58:59 <GrumpeiYokoi> Which usually indicates you didn't hold the boot button down properly
Nov 08 06:59:14 <Set_> I wonder though...what did I do wrong. The .img file was written correctly.
Nov 08 06:59:16 <GrumpeiYokoi> I've found that it is sometimes a finnicky button and you have to try a few times to get it to notice you were holding it down
Nov 08 06:59:26 <GrumpeiYokoi> Oh, i thought you said it wasn't written correctly
Nov 08 06:59:26 <veremit> from http://beagleboard.org/latest-images .. as edited last by jkdridner March 2015 .. he REALLY needs to fix that shit
Nov 08 06:59:29 <GrumpeiYokoi> if so, disregard my ramblings
Nov 08 06:59:32 <Set_> Okay...
Nov 08 06:59:35 <Set_> I will try that.
Nov 08 06:59:42 <Set_> No...it was.
Nov 08 07:00:00 <zmatt> you can also a resistor between P8.43 and ground
Nov 08 07:00:03 <zmatt> *also put
Nov 08 07:00:13 <zmatt> equivalent to holding the boot button
Nov 08 07:00:28 <Set_> Augh...
Nov 08 07:00:35 <GrumpeiYokoi> I'd rather have a gun I could just shoot at the beaglebone that brainwashes it
Nov 08 07:00:43 <veremit> GrumpeiYokoi +1
Nov 08 07:00:50 <Set_> I should have more control over it.
Nov 08 07:00:57 <veremit> emmc 'gun' I like it
Nov 08 07:01:03 <veremit> that Zaps it
Nov 08 07:01:04 <veremit> :D
Nov 08 07:01:09 <GrumpeiYokoi> Though I guess if it netboots that would be feasible with a local wifi network 'gun'
Nov 08 07:01:17 <GrumpeiYokoi> *shrug*
Nov 08 07:01:21 <zmatt> you could make a reflashing station
Nov 08 07:01:34 <Set_> You would be rich.
Nov 08 07:01:34 <veremit> zmatt .. with bbvlfs :D
Nov 08 07:01:39 <Set_> Yep.
Nov 08 07:01:44 <zmatt> veremit: no, its expansion headers
Nov 08 07:02:02 <veremit> how would it ... oh I suppose sdio
Nov 08 07:02:02 <GrumpeiYokoi> Now I have to look up BBBlfs b/c I'm clearly behind the ball
Nov 08 07:02:10 <zmatt> power the BBB via P9.5 + P9.6, keep nRESET tied low
Nov 08 07:02:25 <zmatt> reprogram eMMC directly via the pins on P8
Nov 08 07:02:35 <veremit> emmc pins are on p8 .. eww eww
Nov 08 07:02:47 <veremit> well .. erm .. I suppose so .. since they can be disabled.
Nov 08 07:02:49 <GrumpeiYokoi> Just wondering, does any one know what happened to all the install-me.sh scripts on RCN's site?
Nov 08 07:03:07 <veremit> GrumpeiYokoi .. probably hiding there still
Nov 08 07:03:15 <GrumpeiYokoi> I looked extensively and couldn't find any of them for any kernel version
Nov 08 07:03:18 <Set_> 10 more minutes.
Nov 08 07:03:25 <Set_> Then...I pull the plug.
Nov 08 07:03:38 <veremit> possibly deprecated by 'apt-get install linux-image-blah'
Nov 08 07:03:39 <GrumpeiYokoi> The scripts in /opt are borked because of it
Nov 08 07:03:48 <GrumpeiYokoi> veremit: Yeah, ain't complaining
Nov 08 07:03:58 <GrumpeiYokoi> They're just conspicuously missing
Nov 08 07:04:07 <zmatt> veremit: you didn't realize the emmc pins are available via P8 ?
Nov 08 07:04:13 <veremit> zmatt.. no.
Nov 08 07:04:13 <GrumpeiYokoi> From the starting point of when I was trying to learn how to migrate kernel versions they were still visible
Nov 08 07:04:30 <veremit> GrumpeiYokoi .. ask RN himself monday if he's here ..
Nov 08 07:04:32 <GrumpeiYokoi> zmatt: I did, I bricked a BBB that way on accident
Nov 08 07:04:54 <veremit> zmatt.. GrumpeiYokoi .. I would have imagined not for this precise reason :D
Nov 08 07:04:54 <Set_> That is why I am being so careful.
Nov 08 07:05:03 <veremit> but .. afaik .. its not unrecoverable
Nov 08 07:05:18 <GrumpeiYokoi> Well, I meant to say temp-bricked
Nov 08 07:05:34 <Set_> I am not desoldering anything.
Nov 08 07:05:44 <zmatt> you never need to desolder anything
Nov 08 07:05:47 <GrumpeiYokoi> But it clearly messed up the image at the time.
Nov 08 07:05:48 <Set_> Oh.
Nov 08 07:05:49 <veremit> zmatt.. what method would you store the new image then? and to use to program the emmc if not through the am335x ?
Nov 08 07:06:13 <Set_> If you brick it, why is it not forever bricked?
Nov 08 07:06:21 <Set_> Heh?
Nov 08 07:06:31 <GrumpeiYokoi> By bricked I meant that the emmc image was corrupted
Nov 08 07:06:31 <veremit> Set_ .. you can only brick it by frying the processor or PMIC
Nov 08 07:06:33 <GrumpeiYokoi> that's all
Nov 08 07:06:37 <zmatt> Set_: you can't hard-brick the BBB other than by destroying a hardware  component
Nov 08 07:06:48 <GrumpeiYokoi> We have permanently killed one, but that was another adventure
Nov 08 07:06:55 <veremit> like .. magic smoke destroy
Nov 08 07:07:01 <Set_> Yep. I figured if one thing went Poof, the whole thing stopped.
Nov 08 07:07:11 <zmatt> yeah we have one with the deaded Power LED Blip of Doom
Nov 08 07:07:22 <zmatt> *dreaded
Nov 08 07:07:32 <Set_> Two minutes!
Nov 08 07:07:37 <Set_> Hhahaha.
Nov 08 07:08:01 <Set_> Those books I have been reading on Python are difficult.
Nov 08 07:08:03 <GrumpeiYokoi> Well on this one all the LEDs were all dead no matter what I did
Nov 08 07:08:12 <Set_> Luckily, BBB accepts it and likes it.
Nov 08 07:08:41 <Set_> Four spaces here and this goes in that...sheesh.
Nov 08 07:08:58 <GrumpeiYokoi> I wonder if I would have found Python hard as a first language
Nov 08 07:09:07 <Set_> What did you learn first?
Nov 08 07:09:10 <GrumpeiYokoi> It took me forever to grasp pointers with C/C++
Nov 08 07:09:14 <Set_> Augh.
Nov 08 07:09:16 <GrumpeiYokoi> C/C++
Nov 08 07:09:35 <GrumpeiYokoi> I think the explanations sucked though in the books I read though
Nov 08 07:09:36 <Set_> Yep. I got it. I like Python because it is "easier."
Nov 08 07:09:49 <GrumpeiYokoi> Sometimes concrete experience trumps abstract explanations
Nov 08 07:10:10 <GrumpeiYokoi> When i started learning assembly pointers suddenly clicked a lot more
Nov 08 07:10:11 <zmatt> veremit: one idea would be a CAPE-like board with a usb-to-SD/MMC chip... and something to affix is well to your desk so you can easily pull the BBB off again
Nov 08 07:10:12 <Set_> Same here. I have had a very difficult time finding books on hardware and Python that are lengthy.
Nov 08 07:10:52 <Set_> They give a short recommendation on ideas.
Nov 08 07:11:35 <Set_> I would like to test out hardware with my notions. I am finding where to start as a difficulty.
Nov 08 07:11:59 <veremit> zmatt .. with a convenient lever to prise it off ;)
Nov 08 07:12:00 <zmatt> veremit: or alternatively have it "mate" two BBBs... one to be reflashed and the other to reflash it (mmc 2 is still available via the cape headers with full 8-bit data)
Nov 08 07:12:21 <Set_> Should I fire a rocket that has GPS or just sit and cry with Python?
Nov 08 07:12:24 <veremit> zmatt .. NOT with back-to-back headers ;) lol
Nov 08 07:12:30 <zmatt> no, lol
Nov 08 07:12:47 <veremit> you'd need a PCB .. but I s'pose thats feasible
Nov 08 07:12:54 <GrumpeiYokoi> Set_: The Python modules are almost certainly wrapped C code, so I'd blame whoever wrote the C code
Nov 08 07:12:59 <zmatt> though you could make it look like that if you can find surface-mount versions of those big headers, but dunno how long before they'd break odd
Nov 08 07:13:02 <zmatt> *off
Nov 08 07:13:13 <veremit> zmatt .. pretty good if they'r properly soldered
Nov 08 07:13:25 <veremit> back-to-back to avoid ethernet port nuisance
Nov 08 07:13:27 <GrumpeiYokoi> I found Adafruit's Python IO library for the BBB to be pretty decent
Nov 08 07:13:43 <GrumpeiYokoi> Might not be best for all use cases, but certainly was fun to dick around with
Nov 08 07:13:52 <Set_> Yea...I tried it with my Debian image. I got nowhere.
Nov 08 07:14:12 <Set_> I was goofing with it and could not get my e-mail to send.
Nov 08 07:14:23 <Set_> I checked my code and nothing.
Nov 08 07:15:02 <Set_> it was something like "python email_this.py"
Nov 08 07:15:03 <GrumpeiYokoi> I don't know much of anything about coding email servers / clients, so good luck with that :0
Nov 08 07:15:16 <Set_> I am just learning.
Nov 08 07:15:26 <veremit> python email takes an AGE to send
Nov 08 07:15:30 <Set_> It seems fun. I am not good at it.
Nov 08 07:15:35 <Set_> I could get it last year.
Nov 08 07:15:36 <Set_> ha.
Nov 08 07:15:50 <veremit> like .. nearly a minutes
Nov 08 07:15:54 <zmatt> veremit: well then you could make them line up, but the problem is the ethernet connectors would end up snogging each other
Nov 08 07:15:55 <Set_> My date is off. It will not send it.
Nov 08 07:15:55 <veremit> minute*
Nov 08 07:15:58 <GrumpeiYokoi> D:
Nov 08 07:16:06 <veremit> ntpdate
Nov 08 07:16:16 <zmatt> systemd-timesyncd
Nov 08 07:16:20 <Set_> I tried. my ntpdate will not work correctly.
Nov 08 07:16:22 <veremit> antispam measures are good .. keeps the eejuts out/off
Nov 08 07:16:29 <zmatt> you need network though
Nov 08 07:16:33 <GrumpeiYokoi> The debian images seem to be good about setting time
Nov 08 07:16:39 <veremit> ah yeah .. usb net should be fine
Nov 08 07:16:49 <GrumpeiYokoi> However, they don't set timezone
Nov 08 07:16:55 <GrumpeiYokoi> you'll have to set that yourself
Nov 08 07:17:00 <zmatt> duh
Nov 08 07:17:24 <veremit> no need .. UTC :P lol
Nov 08 07:17:39 <Set_> I got that Adafruit_BBIO package and wrote the script. I followed instruction and learned.
Nov 08 07:17:55 <GrumpeiYokoi> Don't know why the date be off unless it was off by one day
Nov 08 07:17:55 <Set_> Then...I remembered. Date!
Nov 08 07:18:07 <Set_> My states it is 2014.
Nov 08 07:18:08 <GrumpeiYokoi> (due to timezone)
Nov 08 07:18:09 <zmatt> veremit: anyhow, I marked the eMMC pins with eye-penetrating purple on the P8 tab of my pins spreadsheet ( https://goo.gl/Jkcg0w ) for tha reason
Nov 08 07:18:14 <zmatt> *that
Nov 08 07:18:19 <GrumpeiYokoi> Huh... well that's new on me
Nov 08 07:18:36 <GrumpeiYokoi> The Angstrom images would always read like 1999 or 2000, I can't remember which
Nov 08 07:18:38 <Set_> Yep...I am working on it.
Nov 08 07:18:40 <veremit> zmatt: lol
Nov 08 07:18:42 <Set_> Yep.
Nov 08 07:18:56 <Set_> '99
Nov 08 07:19:04 <veremit> no rtc on the BBB
Nov 08 07:19:06 <veremit> nor the Pi
Nov 08 07:19:08 <zmatt> veremit: look at the insane IOSets for McASP btw o.O  (IOSets tab)
Nov 08 07:19:09 <veremit> bloody shite
Nov 08 07:19:15 <zmatt> well, there's an RTC
Nov 08 07:19:21 <veremit> there's only 2 mcasp's I thought?
Nov 08 07:19:25 <zmatt> there are
Nov 08 07:19:38 <zmatt> mcasp 0 and 1
Nov 08 07:19:45 <Set_> Okay...I am done for now. I will check back later. I need to test out to see if my image "done wroted."
Nov 08 07:19:45 <veremit> and how many processor pins? so many choices! :P lol
Nov 08 07:19:57 <Set_> Later for now.
Nov 08 07:20:04 <veremit> Set_.. reset if (via switch) and see if the web page omes up
Nov 08 07:20:06 <veremit> simple
Nov 08 07:20:08 <GrumpeiYokoi> Lata
Nov 08 07:20:32 <zmatt> veremit: based on a quick glance at the table it seems up to 4 mux options per pin
Nov 08 07:20:34 <veremit> you can do 98% whilst connected over usb
Nov 08 07:20:49 <veremit> 100 if you bypass the uSD step :D
Nov 08 07:21:01 <zmatt> veremit: but you're officially only allowed to use them in specific combinations... that's what the IOSets are
Nov 08 07:21:17 <veremit> zmatt .. of course
Nov 08 07:21:23 <zmatt> although I've already caught the IOSets containing pure bullshit, so...
Nov 08 07:21:29 <veremit> lol
Nov 08 07:22:02 <zmatt> like, they defined IOSets for UARTs... I actually started typing those in before I realized all those pins are asynchronous and their relative timing is absolutely irrelevant
Nov 08 07:22:54 <veremit> so bodging them around won't matter .. and Will Work?!
Nov 08 07:23:11 <zmatt> iosets have absolutely no meaning for a uart
Nov 08 07:23:22 <veremit> it depends I gues whether RTS/CTS timing is sufficiently in-margin
Nov 08 07:24:49 <zmatt> iirc the uart can take several characters to react to CTS anyhow
Nov 08 07:25:16 <zmatt> you set your thresholds appropriately
Nov 08 07:25:47 <zmatt> violating an ioset gets you misalignment of signals on the order of nanoseconds at most afaik
Nov 08 07:27:00 <veremit> fair enuf
Nov 08 07:27:54 <zmatt> given that they didn't document them (my spreadsheet is the first public documentation) they're probably violated all the time by people :P
Nov 08 07:28:06 <zmatt> (you're expected to use their lovely pinmux tool)
Nov 08 07:28:30 <veremit> ah that thaing
Nov 08 07:28:41 <veremit> doens't run on liniux does it?
Nov 08 07:28:53 <zmatt> no, though there's now also a cloud-based version
Nov 08 07:29:34 <zmatt> so you either need windows or setup a TI account
Nov 08 07:31:33 <zmatt> or look at my spreadsheet, though I haven't entered all ioset data yet
Nov 08 07:32:57 <zmatt> of course you should also look at the application and ask whether it matters... e.g. the iosets for pwm outputs only matter if the A/B outputs need to be phase-synchronized at high frequency
Nov 08 07:33:28 <zmatt> which is relevant for a few applications, but not in general
Nov 08 07:34:15 <zmatt> more annoyingly they don't define any iosets that span multiple pwmss instances, even though they're designed to allow running them in sync
Nov 08 07:37:04 <zmatt> and I still don't know what the "micro-edge positioning" step size is for the pwm outputs... it's ~200 ps on the omap-L13x, but those are produced on 65nm process; it may very well be less than that on the 45nm am335x
Nov 08 07:39:45 <zmatt> "micro edge-positioning" I mean
Nov 08 07:41:23 <zmatt> GrumpeiYokoi: note btw that the baremetal example I linked to is really bare... my main codebase does include things like MMU/cache setup and such of course
Nov 08 07:42:25 <zmatt> I still need to convince employer to let me release an example based on it
Nov 08 07:42:43 <zmatt> there's really a lack of decent baremetal examples for am335x
Nov 08 07:43:18 <GrumpeiYokoi> Yeah, I've really had to gloss over the low level stuff for lack of easily consumable information
Nov 08 07:43:34 <zmatt> even though it's not that hard and not much code, but unless you know the right things to do it's hard to have any idea where to even begin
Nov 08 07:43:49 <GrumpeiYokoi> There is a huge manual for the BBB and the aam35x, but it is freaking.... huge
Nov 08 07:44:14 <zmatt> and it doesn't include the info you need for initialization
Nov 08 07:44:21 <GrumpeiYokoi> No? That's a shame
Nov 08 07:44:44 <zmatt> you also need the ARM Architecture v7 Reference Manual
Nov 08 07:44:46 <GrumpeiYokoi> Like, even the svg file in the topic is more than I knew yesterday
Nov 08 07:44:49 <zmatt> and the Cortex-A8 TRM
Nov 08 07:45:02 <zmatt> the svg file in the topic?
Nov 08 07:45:13 <GrumpeiYokoi> http://ahsoftware.de/Beaglebone_Black_Boot_explained.svg
Nov 08 07:45:34 <GrumpeiYokoi> I had vague, wobbly notions of what was going on, but it demystified them
Nov 08 07:45:46 <zmatt> GrumpeiYokoi: it's not quite right though
Nov 08 07:46:01 <GrumpeiYokoi> How so?
Nov 08 07:47:02 <GrumpeiYokoi> The only experience I've had that would seem to contradict this was when we had a customer that wanted to use the armhf Angstrom builds
Nov 08 07:47:07 <zmatt> 1. MLO is the name given to a memory boot image, which on GP am335x devices is just a naked code image with a two-word header prepended
Nov 08 07:47:27 <zmatt> USB and UART are peripheral booting and don't use MLO but a naked image
Nov 08 07:47:30 <GrumpeiYokoi> I found that if the non-armhf (soft float abi or whatever) were present on eMMC, and I tried to boot of the SD Card, I would almost always crash
Nov 08 07:47:47 <GrumpeiYokoi> never fully understood why, but I just renamed the MLO on the eMMC to something else and it seemed to work
Nov 08 07:47:53 <zmatt> 2. it completely skips over raw MMC booting
Nov 08 07:48:05 <zmatt> which is used by all current eMMC images
Nov 08 07:48:21 <zmatt> there's no boot partition anymore, no MLO file
Nov 08 07:48:42 <GrumpeiYokoi> Since debian, you mean?
Nov 08 07:48:50 <zmatt> dunno since when exactly
Nov 08 07:49:00 <zmatt> I think debian may have used a boot partition for a while also
Nov 08 07:49:16 <GrumpeiYokoi> I had a notion that the the two partitions were one, but again it was a fuzzy feeling
Nov 08 07:50:20 <zmatt> for eMMC (not SD) ROM looks for a specific header at offset i*0x20000 for i=0..3
Nov 08 07:50:59 <zmatt> only if not found it'll proceed to look for a FAT partition same as on SD
Nov 08 07:51:31 <zmatt> however if the special header is present, then it expects the MLO to be located at the next sector and loads it from there
Nov 08 07:52:05 <GrumpeiYokoi> This is more complicated than my relationship status
Nov 08 07:52:12 <zmatt> in case of the MLO being the u-boot SPL, it'll proceed to load the full u-boot.img from a fixed offset from eMMC
Nov 08 07:52:19 <zmatt> all this is outside the partition table
Nov 08 07:53:00 <zmatt> dd if=/dev/mmcblk0 skip=$(( 0x20000 / 512 )) count=1 | hexdump -C
Nov 08 07:53:56 <zmatt> if you see something involving CHSETTINGS, that's the magic header
Nov 08 07:55:33 <zmatt> GrumpeiYokoi: I also think the diagram make it look more complicated than it is
Nov 08 07:56:10 <zmatt> the notion of trying a list of boot devices in order isn't exactly unusual, every PC does that too
Nov 08 07:56:17 <veremit> hmm not on mine .. just a bunch of zeros here ..
Nov 08 07:56:24 <GrumpeiYokoi> Yeah, I was  confused by it at first, had the same reaction
Nov 08 07:57:14 <zmatt> GrumpeiYokoi: on the am335x the list of boot devices is determined by strapping inputs sampled at power-on-reset
Nov 08 07:57:37 <zmatt> you can actually see the row of resistors for that on the PCB
Nov 08 07:58:14 <zmatt> 16 resistors on a row, some of them not-placed, and on the other side of the PCB is a complementary row of resistors (i.e. if placed on one side it's not-placed on the other side)
Nov 08 07:58:31 <zmatt> pull-up vs pull-down
Nov 08 07:58:39 <veremit> zmatt .. http://pastebin.com/0XVSfgDu
Nov 08 07:58:42 <Set_> Hey...
Nov 08 07:58:47 <Set_> That damn thing.
Nov 08 07:58:50 <Set_> No go.
Nov 08 07:59:05 <GrumpeiYokoi> That's vague
Nov 08 07:59:17 <Set_> I just tried to clone Angstrom's new version and it will not allow me.
Nov 08 07:59:25 <veremit> Set_... you're not doing some part of the process right
Nov 08 07:59:26 <Set_> It says and I quote, "Fatal."
Nov 08 07:59:34 <Set_> I know.
Nov 08 07:59:37 <Set_> I quit.
Nov 08 07:59:40 <veremit> or worse still .. several parts :P
Nov 08 07:59:42 <Set_> Dang it...I hate to say it.
Nov 08 07:59:44 <zmatt> veremit: then you still have a FAT boot partition
Nov 08 07:59:50 <tbr> just use the debian image?
Nov 08 07:59:59 <tbr> unless you want to build angstrom from scratch
Nov 08 08:00:00 <veremit> zmat ..
Nov 08 08:00:00 <Set_> I did over and over.
Nov 08 08:00:07 <tbr> then get the new thing for it
Nov 08 08:00:10 <veremit> mmcblk0
Nov 08 08:00:10 <veremit> ├─mmcblk0p1  vfat   boot        /boot/uboot
Nov 08 08:00:10 <veremit> └─mmcblk0p2  ext4   rootfs      /
Nov 08 08:00:11 <Set_> I want to build Angstrom from scratch.
Nov 08 08:00:14 <veremit> so I do !
Nov 08 08:00:20 <tbr> ok, sec, let me find the tool
Nov 08 08:00:37 <GrumpeiYokoi> ... Angstrom has a new version out?
Nov 08 08:00:37 <Set_> Cool.
Nov 08 08:00:39 <zmatt> veremit: i.e. your filesystem is ancient (or based on something ancient and repeatedly upgraded)
Nov 08 08:00:43 <Set_> Yea...this year.
Nov 08 08:00:52 <veremit> zmatt .. probably a year or two old now
Nov 08 08:01:05 <zmatt> veremit: which is the world of BBB qualifies as ancient
Nov 08 08:01:07 <veremit> [ 7:59am] root@beagleblack ~ # cat /etc/dogtag
Nov 08 08:01:07 <veremit> cat: /etc/dogtag: No such file or directory
Nov 08 08:01:10 <zmatt> yeah that
Nov 08 08:01:25 <veremit> it was, ofc a manual build from RN's web pages
Nov 08 08:01:30 <veremit> none of this 'official' bullshit :D
Nov 08 08:01:35 <Set_> I checked mine. It says some date in 2014.
Nov 08 08:01:37 <veremit> its a 3.12 kernel or 3.13 iirc ..
Nov 08 08:01:50 <veremit> [ 8:01am] root@beagleblack ~ # uname -a
Nov 08 08:01:50 <veremit> Linux beagleblack 3.13.6-bone7.2 #1 SMP Fri Mar 21 03:59:54 GMT 2014 armv7l GNU/Linux
Nov 08 08:01:55 <veremit> there ye go :D
Nov 08 08:01:57 <tbr> Set_: try with this https://github.com/Angstrom-distribution/angstrom-manifest/tree/angstrom-v2015.06-yocto1.8
Nov 08 08:02:02 <GrumpeiYokoi> a customer provided me with an armhf version sometime in 2014, but it was busted
Nov 08 08:02:07 <Set_> I got A5C for my BBB.
Nov 08 08:02:09 <Set_> Okay.
Nov 08 08:02:13 <zmatt> veremit: ... why?
Nov 08 08:02:14 <GrumpeiYokoi> opkg couldn't locate anything, it as missing cloud9 and all the webserver stuff
Nov 08 08:02:21 <GrumpeiYokoi> So I assume they had built it themselves
Nov 08 08:02:25 <Set_> I only noticed that they were Yocto 1.7 comp.
Nov 08 08:02:30 <veremit> zmatt .. cos I wasn't f*ng around with angstrom at the time lol
Nov 08 08:02:53 <zmatt> veremit: but why on earth haven't you upgraded since then? :P
Nov 08 08:02:54 <Set_> tbr...thank you.
Nov 08 08:03:06 <veremit> zmatt .. cos its running Essential Servics ..
Nov 08 08:03:12 <veremit> I bought another to 'play' with ;P
Nov 08 08:03:37 <zmatt> oh well
Nov 08 08:03:41 <veremit> it has a testing lxqt on it
Nov 08 08:03:53 <veremit> but I need a uHDMI to see it .. then I'll play :)
Nov 08 08:04:03 <zmatt> why did you run my command, as root, on a BBB running "essential services" instead of your play-BBB ?
Nov 08 08:04:04 <veremit> stupid bloody connector
Nov 08 08:04:15 <veremit> cos I got open ssh on this one :D
Nov 08 08:04:18 <zmatt> lol
Nov 08 08:04:32 <veremit> for ''maintenance'' lol
Nov 08 08:04:34 <veremit> and for poking
Nov 08 08:05:03 <zmatt> I actually configured our BBBs (and servers) with timeouts on idle root shells
Nov 08 08:05:17 <veremit> yeah I got another debian box running wheez I need to migrate to jessie
Nov 08 08:05:29 <veremit> sensible plan tbh
Nov 08 08:05:32 <Set_> <tbr> do I need to clone it, "git clone git://" and then proceed with the address?
Nov 08 08:05:48 * zmatt uses stretch on production hardware and sid on personal hardware
Nov 08 08:06:14 <tbr> Set_: the readme on that page provides #exactsteps
Nov 08 08:06:24 <Set_> Okay...I will go to it again.
Nov 08 08:06:35 <veremit> zmatt .. would never use debian for any production system lol
Nov 08 08:06:37 <Set_> I do not know how you found that. I looked at git and found a 2014 version.
Nov 08 08:06:46 <zmatt> GrumpeiYokoi: why Vague ?
Nov 08 08:07:00 <zmatt> veremit: habit, I'm used to it, know where to find shit
Nov 08 08:07:07 <zmatt> veremit: I don't actually *like* it
Nov 08 08:07:16 <veremit> zmatt .. its reasonably simple .. its the same reason I use it on arm
Nov 08 08:07:27 <tbr> Set_: I was pointed at it by one of the Ångström maintainers, when I asked nicely
Nov 08 08:07:32 <GrumpeiYokoi> zmatt: Anytime someone says "It didn't work" or "It's broken". That isn't vague to you?
Nov 08 08:07:35 <Set_> Cool!
Nov 08 08:07:43 <veremit> I'll live with it bein out-of-date until I get gentoo cross-compiling nailed properly
Nov 08 08:07:46 <tbr> also there were g+ posts and such on the topic
Nov 08 08:07:50 <zmatt> GrumpeiYokoi: ah I thought it was a reply to the boot stuff, sorry
Nov 08 08:08:00 <GrumpeiYokoi> ah
Nov 08 08:08:13 <Set_> Oh....Grump. You are right. The boot did not work.
Nov 08 08:08:17 <veremit> ctng ftw .. just gotta roll a couple of toolchains
Nov 08 08:08:21 <Set_> I am in Angstrom still.
Nov 08 08:08:30 <zmatt> GrumpeiYokoi: the sysboot pins are also known as lcd_data0-15 btw
Nov 08 08:08:39 <zmatt> GrumpeiYokoi: so you can change the boot mode using resistors on P8
Nov 08 08:08:45 <GrumpeiYokoi> Is that in the TRM?
Nov 08 08:08:46 <veremit> zmatt .. I always loved that .. :)
Nov 08 08:08:52 <GrumpeiYokoi> @ zmatt
Nov 08 08:08:54 <zmatt> that's how I select netbooting for my baremetal stuff
Nov 08 08:09:03 <zmatt> it is, but my spreadsheet is probably clearer
Nov 08 08:09:07 <Set_> Here goes nothing. See you all soon (again and again)...
Nov 08 08:09:30 <GrumpeiYokoi> zmatt: Do you baremetal netboot over wifi?
Nov 08 08:09:32 <GrumpeiYokoi> *shot*
Nov 08 08:09:37 <zmatt> ethernet :P
Nov 08 08:09:42 <zmatt> actually, yes over wifi
Nov 08 08:09:47 <zmatt> my laptop that is
Nov 08 08:09:51 <GrumpeiYokoi> We've had very spotty luck working with wifi on BBB
Nov 08 08:09:53 <veremit> eww wifi netboot :/
Nov 08 08:10:12 <GrumpeiYokoi> Maybe the newer kernels will be the bomb diggity
Nov 08 08:10:31 <veremit> brb
Nov 08 08:10:33 <zmatt> GrumpeiYokoi: no wifi on the BBB, note that I'm talking about having *rom* netboot a baremetal image
Nov 08 08:10:39 <zmatt> no linux kernel involved at any point
Nov 08 08:10:46 <Set_> first I got fatal: "git" does not exist.
Nov 08 08:10:49 <GrumpeiYokoi> But I guess it's kind of a linux problem than a BBB problem
Nov 08 08:10:54 <Set_> Dang it.
Nov 08 08:10:58 <Set_> This one is bunk.
Nov 08 08:11:01 <zmatt> GrumpeiYokoi: the BBB doesn't have wifi
Nov 08 08:11:02 <GrumpeiYokoi> *more than a BBB problem
Nov 08 08:11:02 <veremit> Set_ DON'T git on your BBB .
Nov 08 08:11:08 <Set_> Okay.
Nov 08 08:11:14 <zmatt> veremit: I git all the time on my BBB
Nov 08 08:11:15 <zmatt> :P
Nov 08 08:11:24 <GrumpeiYokoi> A lot of the same wifi dongles that failed on the BBB also failed on desktop Ubuntu
Nov 08 08:11:34 <zmatt> GrumpeiYokoi: you're talking about usb wifi dongles
Nov 08 08:11:38 <GrumpeiYokoi> I svn on my BBB <__<
Nov 08 08:11:40 <GrumpeiYokoi> Does that count
Nov 08 08:11:45 <tbr> if you want to build Ångström from scratch you have to do it on a rather beefy machine
Nov 08 08:11:45 <zmatt> go wash your mouth
Nov 08 08:11:46 <GrumpeiYokoi> zmatt: Of course, what did you think i meant?
Nov 08 08:11:48 <tbr> with lots of storage
Nov 08 08:11:54 <zmatt> GrumpeiYokoi: it wasn't a question
Nov 08 08:12:03 <zmatt> GrumpeiYokoi: it was more to put emphasis on the usb part
Nov 08 08:12:13 <Set_> Noooooo!
Nov 08 08:12:15 <zmatt> usb sucks donkey balls, both in general and moreso on the am335x
Nov 08 08:12:30 <Set_> Donkey!
Nov 08 08:12:50 <Set_> I need something with "beef."
Nov 08 08:12:51 <GrumpeiYokoi> zmatt: [03:09]	GrumpeiYokoi	*shot*
Nov 08 08:13:08 <GrumpeiYokoi> I was being silly
Nov 08 08:13:11 <Set_> Like...an old Dell?
Nov 08 08:13:12 <zmatt> ok :)
Nov 08 08:13:43 <zmatt> GrumpeiYokoi: anyhow, the Boot tab of my pins spreadsheet shows the meaning of the 16 sysboot pins
Nov 08 08:14:05 <zmatt> do avoid any "nand" boot device, and especially avoid any "xip" boot device
Nov 08 08:14:22 <zmatt> (I don't know anymore why, but I'm pretty sure that's why I marked them yellow and red respectively in my spreadsheet)
Nov 08 08:14:25 <tbr> Set_: dell made about a brezillion different machines. you need to be a bit more specific about its technical details.
Nov 08 08:14:50 <Set_> Okay...has anyone used, please forget the Dell for now, Wyliodrin?
Nov 08 08:15:28 <Set_> I was thinking since they are a part to the Yocto Project, I could use them to get a new system.
Nov 08 08:15:45 <Set_> Dell...Inspiron.
Nov 08 08:15:54 <Set_> Desktop.
Nov 08 08:16:00 <Set_> 5xx
Nov 08 08:16:20 <Set_> circa '04
Nov 08 08:16:40 <tbr> how much storage?
Nov 08 08:17:03 <tbr> building on that type of machine would probably take a day or two
Nov 08 08:17:04 <Set_> 512
Nov 08 08:17:14 <tbr> um, no
Nov 08 08:17:19 <Set_> 4
Nov 08 08:17:31 <tbr> you might want to try narcissus instead, if that has a BBB target
Nov 08 08:17:32 <zmatt> GrumpeiYokoi: anyhow, the complexity of the boot process does not really affect the complexity of a baremetal application of course... in fact since ROM already sets up the PLLs to sane defaults it saves you from having to do clock configuration if you're okay with running at sub-optimal performance (500 MHz)
Nov 08 08:17:56 <Set_> Okay.
Nov 08 08:18:05 <GrumpeiYokoi> zmatt: Is this 'ROM' you and the docs keep mentioning truly a ROM?
Nov 08 08:18:37 <GrumpeiYokoi> zmatt: As in, cannot be modified? Lives somewhere onboard?
Nov 08 08:19:25 <zmatt> GrumpeiYokoi: if I compile a "hello world", but with all init/support code (MMU, caches, irq dispatching, fault handling, basic console driver) the result is about 7 KB
Nov 08 08:19:32 <zmatt> yes
Nov 08 08:19:36 <zmatt> baked into the am335x
Nov 08 08:19:44 <GrumpeiYokoi> k, just wanted confirmation on that
Nov 08 08:19:51 <GrumpeiYokoi> Thanks
Nov 08 08:20:12 <GrumpeiYokoi> It was a bit confusing b/c I'd heard some people talk about the MLO and other boot images similarly
Nov 08 08:20:15 <zmatt> 7 KB of code means imho the support code isn't that complicated
Nov 08 08:20:34 <GrumpeiYokoi> 7 KB of support code sounds like a lot for hello world :)
Nov 08 08:21:14 <GrumpeiYokoi> But yeah I know there's a lot more to it than just the hello world code itself
Nov 08 08:21:27 <GrumpeiYokoi> What are you hello worlding to?
Nov 08 08:21:33 <zmatt> uart
Nov 08 08:21:35 <zmatt> console
Nov 08 08:21:37 <Set_> Okay...I am going to try some guy from Romania at wyliodrin.com.
Nov 08 08:21:39 <GrumpeiYokoi> kk
Nov 08 08:21:41 <tbr> GrumpeiYokoi: ROM-BL is mentioned vaguely in the TRM IIRC
Nov 08 08:21:46 <Set_> New image boy!
Nov 08 08:22:00 <zmatt> tbr: ROM bootloader is documented quite decently in the TRM
Nov 08 08:22:03 <GrumpeiYokoi> tbr: Vaguely? My favorite! -___-
Nov 08 08:22:21 <tbr> zmatt: the public one? I thought it was only in the sekrit one
Nov 08 08:22:38 <tbr> admittedly I haven't looked at the am335x trm in a while
Nov 08 08:22:39 <GrumpeiYokoi> zmatt: You mentioned you'd need the arm v7 reference manual so by that I take it you mean you're probably not getting away without writing some assembler
Nov 08 08:22:42 <veremit> Set_ .. I suggest that the image is not your problem . . more the process you're using to get it on-board
Nov 08 08:22:45 <GrumpeiYokoi> *assembly language
Nov 08 08:23:04 <veremit> GrumpeiYokoi .. it will all compile to byte-code
Nov 08 08:23:10 <zmatt> tbr: pubROM is documented (chapter 26)
Nov 08 08:23:15 <tbr> ok
Nov 08 08:23:22 * GrumpeiYokoi squints
Nov 08 08:23:27 <GrumpeiYokoi> byte code?
Nov 08 08:23:47 <veremit> one step up from Machine Code lol .. or same thing, depending on definition :)
Nov 08 08:23:54 <GrumpeiYokoi> I know what it is
Nov 08 08:23:56 <zmatt> tbr: secrom isn't, but it doesn't do much beyond pointlessly reserving some resources it doesn't need before irreversibly switching to public mode
Nov 08 08:24:01 <GrumpeiYokoi> I'm just...
Nov 08 08:24:14 <GrumpeiYokoi> tired?
Nov 08 08:24:14 <zmatt> tbr: on GP devices that is
Nov 08 08:24:24 <zmatt> GrumpeiYokoi: some asm, not not much
Nov 08 08:24:26 <zmatt> *but not
Nov 08 08:24:29 <GrumpeiYokoi> Too many dramatic twists in understanding for one night
Nov 08 08:24:29 <tbr> yeah, HS is a whole different story
Nov 08 08:25:11 <zmatt> tbr: I discovered that on HS DM814x devices you can make a secure monitor call that pushes a stack frame but fails to pop it before return XD
Nov 08 08:25:35 <tbr> "oops"
Nov 08 08:26:33 <zmatt> tbr: nothing fun you could do with that though, other than triggering a stack overflow in secmon which results in the ever-grumpy SSM resetting the system due to "MPU security violation"
Nov 08 08:27:17 <zmatt> (note that I don't have a HS devices to play with, but they failed to make secrom unreadable on the DM814x so I've been nosing around)
Nov 08 08:27:27 <tbr> well, in security you need to be paranoid and if anything goes wrong nuking from orbit is a valid solution
Nov 08 08:27:42 <zmatt> it's amazing how crap the rom code is
Nov 08 08:28:11 <zmatt> I don't understand what they were thinking putting so much supremely-privileged garbage in ROM where you can't apply bugfixes anymore
Nov 08 08:28:30 <tbr> feature creep ftw
Nov 08 08:28:40 <zmatt> yeah, especially in security -.-
Nov 08 08:28:55 <tbr> yeah, it doesn't make sense from a _sane_ perspective
Nov 08 08:29:08 <tbr> but who said anything about damagement having to be sane
Nov 08 08:29:38 <zmatt> secrom should have been a tiny amount of code, the absolute minimum to setup a dynamic root of trust, with the assembly code published and well-commented to the point its correctness is self-evident
Nov 08 08:29:42 <Set_> I have to go. Have fun. I will keep the updates and schtuff up to snuff.
Nov 08 08:31:27 <zmatt> GrumpeiYokoi: oh wait this isn't just hello world, it still included some LCDC test code
Nov 08 08:31:55 <zmatt> and pll configuration dump
Nov 08 08:32:21 <GrumpeiYokoi> zmatt: I could write hello world on my SNES and it would be about 256 bytes or less
Nov 08 08:32:45 <GrumpeiYokoi> zmatt: But actually I was doing some math in my head wrong, and 7K sounded like a lot more than it actually is
Nov 08 08:32:54 <GrumpeiYokoi> So nevermind anyway. Just being a stinker
Nov 08 08:32:59 <zmatt> ah, now it's down to 3356 bytes
Nov 08 08:33:06 <zmatt> that's better
Nov 08 08:33:13 <GrumpeiYokoi> Yee haw
Nov 08 08:33:52 <GrumpeiYokoi> The hello world in question would be writing to the controller port serial output, so it's kind of cheating
Nov 08 08:34:11 <GrumpeiYokoi> But graphical hello world wouldn't take much either
Nov 08 08:34:19 <zmatt> how is that cheating?
Nov 08 08:34:21 <zmatt> :P
Nov 08 08:34:30 <GrumpeiYokoi> B/c you'd need custom hardware to see it?
Nov 08 08:34:40 <GrumpeiYokoi> Or at least, to wire something up to see it
Nov 08 08:35:18 <zmatt> you need a cable to connect it to another device which decodes the signal thrown at it and visualizes it for you
Nov 08 08:35:26 <zmatt> this differs from HDMI.. how exactly?
Nov 08 08:35:46 <zmatt> also I don't actually use HDMI normally either
Nov 08 08:35:47 <GrumpeiYokoi> clock rate
Nov 08 08:36:53 <GrumpeiYokoi> Other than that, probably not much
Nov 08 08:36:56 <zmatt> the 7 KB code did include setup of the LCDC btw, so it could have done your "hello world" if an lcd cape is attached
Nov 08 08:37:04 <zmatt> clock rate doesn't matter much, that's handled by the peripheral
Nov 08 08:37:21 <zmatt> uart is actually kinda more involved than lcdc
Nov 08 08:37:50 <GrumpeiYokoi> Well, in the SNES case it would be tied to the master clock of the system, which is ~22 mhz. But yeah.
Nov 08 08:37:56 <zmatt> its setup procedure is more complicated, and you need to monitor its status when you want to output data
Nov 08 08:38:20 <zmatt> while lcdc is an initiator, you just hand it a pointer to your framebuffer
Nov 08 08:38:20 <GrumpeiYokoi> I need to get me one of them fancy LCD capes
Nov 08 08:38:46 <zmatt> getting hdmi going would be more work since you'd need to poke the hdmi framer
Nov 08 08:38:54 <GrumpeiYokoi> But I know the main thing I'd use it for is to display the device's IP address
Nov 08 08:39:04 <GrumpeiYokoi> Which is kind of silly
Nov 08 08:39:27 <zmatt> optimizing for size and enabling LTO reduces size to 2344 bytes btw ;)
Nov 08 08:39:53 <zmatt> that still includes MMU setup code and such
Nov 08 08:40:10 <GrumpeiYokoi> Still not good enough. I won't be impressed until it all fits into 4 bits
Nov 08 08:40:18 <GrumpeiYokoi> ;)
Nov 08 08:40:19 * zmatt slaps GrumpeiYokoi with a trout
Nov 08 08:40:26 * GrumpeiYokoi was hungry anyway
Nov 08 08:40:41 * GrumpeiYokoi grabs some old bay
Nov 08 08:43:56 <zmatt> GrumpeiYokoi: as far as asm goes... I have only one assembly source file, which is 143 lines (nearly half of them blank or comment)
Nov 08 08:44:19 <zmatt> mostly boilerplate for the fault handlers
Nov 08 08:44:40 <zmatt> 9 instructions of init code before I call main
Nov 08 08:44:55 <zmatt> or 10 I guess
Nov 08 08:46:12 <zmatt> the rest is C++ with some isolated lines of inline asm here and there
Nov 08 08:47:43 <zmatt> if main returns it goes into an infinite wfi-loop, so irq-driven apps can just do initialization in main and then return
Nov 08 08:51:42 <ag_melbourne> Hello :)
Nov 08 08:53:47 <ag_melbourne> Beaglebone Black, Jessie, wifi not working ( I have an SD card with Wheezy which runs fine on exactly the same hardware )
Nov 08 09:01:25 <ag_melbourne> Beaglebone Black, Jessie, wifi not working ( I have an SD card with Wheezy which runs fine on exactly the same hardware )
Nov 08 09:08:14 <Defiant> ag_melbourne: not working as in does not show up in iwconfig?
Nov 08 09:11:48 <veremit> kernel version .. lsusb ?
Nov 08 09:13:37 <ag_melbourne> hi defiant :) it seems as though I have to run wpa_supplicant manually ( systemctl status wpa_supplicant ->  Active: inactive (dead) after reboot ) and I still do not achieve connection when I run systemctl start wpa_supplicant
Nov 08 09:14:56 <ag_melbourne> iwconfig gives command not found
Nov 08 09:18:34 <ag_melbourne> latest drivers downloaded, lsusb shows device, kernel 4.1.10-ti-r24
Nov 08 09:18:50 <Defiant> I have no idea about systemd.. can you pastebin dmesg?
Nov 08 09:20:29 <ag_melbourne> Does anyone have a working wifi under jessie ?
Nov 08 09:21:42 <ag_melbourne> paste.debian.net/328107
Nov 08 09:22:32 <Defiant> looks like you have working wifi
Nov 08 09:24:12 <ag_melbourne> hi defiant, except for two things, the lamp on the dongle does not flicker, and ipscan.exe an windows IP scanner cannot see the device
Nov 08 09:25:49 <ag_melbourne> ...its nearly there, but not quite, hence I am asking for help :)
Nov 08 09:27:30 <Defiant> ag_melbourne: it has associated with your ap
Nov 08 09:27:52 <Defiant> ag_melbourne: ifconfig wlan0
Nov 08 09:30:23 <veremit> or ifconfig -a
Nov 08 09:30:32 <ag_melbourne> paste.debian.net/328118, yes it all looks good, I am talking to it now by USB, would you agree that I could Putty in on 192.168.1.64 when I disconnect the USB?
Nov 08 09:30:55 <Defiant> yes
Nov 08 09:31:00 <ag_melbourne> paste.debian.net/328118
Nov 08 09:32:26 <ag_melbourne> ok USB disconnected...192.168.1.64 on Putty time out
Nov 08 09:35:26 <veremit> you may need to restart ssh sometimes .. as it doesn't always bind to everything ..
Nov 08 09:35:40 <Defiant> veremit? Never had this problem
Nov 08 09:35:59 <Defiant> ag_melbourne: ssh to it over usb and try to ping 8.8.8.8
Nov 08 09:35:59 <veremit> I've seen it happen .. it shouldn't ..
Nov 08 09:36:10 <Defiant> with opensshd?
Nov 08 09:36:50 <veremit> opensshd 6.6 or thereabouts
Nov 08 09:37:18 <veremit> Defiant, ag_melbourne .. can also try to ping your pc over the wifi subnet ..
Nov 08 09:37:28 <veremit> over the usb ssh session :)
Nov 08 09:37:44 <Defiant> veremit: unless his pc is a windows
Nov 08 09:38:00 <veremit> do they block pings too?! f*** ***
Nov 08 09:38:17 <ag_melbourne> ...hmmm 192.168.7.2 ssh not connecting, shall I reboot?
Nov 08 09:38:26 <veremit> pretty sure most things replied to pings
Nov 08 09:38:38 <veremit> unless you actively block them
Nov 08 09:38:49 <Defiant> someone told ms that icmp is something only evil hacker use
Nov 08 09:39:20 <veremit> well of. . its useFUL therefore M$ have to Break it.
Nov 08 09:39:45 * veremit grumbles
Nov 08 09:40:24 <ag_melbourne> ooo...BBB has crashed
Nov 08 09:40:50 <ag_melbourne> reboot button pressed
Nov 08 09:42:49 <ag_melbourne> root@beaglebone:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 192.168.1.42 icmp_seq=1 Destination Host Unreachable
Nov 08 09:43:43 <Defiant> route -n or try to ping your ap
Nov 08 09:44:42 <ag_melbourne> paste.debian.net/328119
Nov 08 09:45:05 <Defiant> uuhm
Nov 08 09:45:13 <Defiant> unplug your ethernet
Nov 08 09:45:49 <veremit> lol
Nov 08 09:46:07 <veremit> ifconfig -a .. shows up everything :)
Nov 08 09:46:19 <ag_melbourne> more info, only USB cable to BBB, no ethernet
Nov 08 09:46:38 <veremit> stale config?!
Nov 08 09:47:36 <ag_melbourne> ifconfig -a -->  paste.debian.net/328121
Nov 08 09:48:08 <Defiant> do you have a static ip on eth0
Nov 08 09:48:31 <veremit> ./etc/network/interfaces ?
Nov 08 09:48:51 <ag_melbourne> yes 192.168.1.42, no ethernet cable connected
Nov 08 09:49:13 <veremit> same subnet as wifi?!
Nov 08 09:49:45 <veremit> yyyessssss...
Nov 08 09:50:28 <veremit> it won't know which interface to use :)
Nov 08 09:50:43 <veremit> ifdown eth0 for now
Nov 08 09:52:19 <ag_melbourne> Hello, I cannot see echo of my messages on screen
Nov 08 09:52:25 <veremit> this is where dhcp does have its advantages ...
Nov 08 09:52:54 <ag_melbourne>  /etc/network/interfaces  -> paste.debian.net/328123
Nov 08 09:53:24 <Defiant> right, ag_melbourne put # before "auto etho"
Nov 08 09:53:36 <veremit> try 'ifdown eth0' and try to reconnect over the wifi
Nov 08 09:54:02 <veremit> Defiant .. could also use 'allow hotplug eth0' too
Nov 08 09:54:31 <Defiant> right
Nov 08 09:54:41 <Defiant> hmm
Nov 08 09:55:05 <Defiant> veremit: wasn't that allow-hotplug if the hw is available?
Nov 08 09:55:14 <ag_melbourne> #auto eth0 done, reboot? ( USB only wired connection )
Nov 08 09:55:22 <veremit> Defiant .. yes, that's how I've used it
Nov 08 09:55:32 <veremit> no wait
Nov 08 09:55:44 <veremit> only if the cable is connected for wired
Nov 08 09:55:54 <veremit> ie. the interface is 'UP'
Nov 08 09:56:00 <veremit> or ..
Nov 08 09:56:02 <veremit> is it ..
Nov 08 09:56:04 <veremit> *lokos*
Nov 08 09:56:24 <veremit> ah yes "CARRIER" for ethernet usually
Nov 08 09:56:25 <ag_melbourne> andrew looks confused :)
Nov 08 09:56:35 <Defiant> ag_melbourne: yeah reboot
Nov 08 09:56:41 <Defiant> veremit: sounds driver dependent
Nov 08 09:57:04 <ag_melbourne> rebooting now
Nov 08 09:57:11 <veremit> Defiant .. yes, it probably is
Nov 08 09:58:38 <veremit> Defiant .. http://unix.stackexchange.com/questions/128439/good-detailed-explanation-of-etc-network-interfaces-syntax/128662#128662
Nov 08 09:59:20 <ag_melbourne> no lamp on wifi dongle, scanning IPs using windows program, no 192.168.1.64, only USB cable connected
Nov 08 10:00:28 <veremit> ag_melbourne .. does it have a light for 'link' and another for 'activity .. or one for both
Nov 08 10:00:42 <ag_melbourne> I have copied your suggestion to my detailed notes
Nov 08 10:00:51 <Defiant> ag_melbourne: ifconfig -a and route -n
Nov 08 10:06:27 <ag_melbourne> It is a NETGEAR WNA1000M, fine under Wheezy. lsusb, ifconfig -a, route -n  ->   paste.debian.net/328126
Nov 08 10:08:56 <Defiant> wifi is currently not up
Nov 08 10:09:05 <ag_melbourne> wifi dongle has one lamp, under wheezy it blinks for activity, under Jessie it remains on...but not as I write this
Nov 08 10:09:10 <Defiant> try ifup wlan0
Nov 08 10:09:12 <ag_melbourne> wifi not up
Nov 08 10:09:29 <veremit> wifi not loaded according to ifconfig .. but it could be associating
Nov 08 10:09:55 <ag_melbourne> Failed to bring up wlan0.
Nov 08 10:10:23 <veremit> crikey lol !
Nov 08 10:10:26 <tbr> what does dmesg say?
Nov 08 10:10:40 <tbr> anything about missing firmware or such?
Nov 08 10:10:56 <veremit> tbr.. I suspect its a dodgy rtl81xx driver :/
Nov 08 10:11:08 <veremit> there used to be all sorts of issues with that family ..
Nov 08 10:11:12 <tbr> yup
Nov 08 10:11:27 <ag_melbourne>  paste.debian.net/328127
Nov 08 10:11:56 <veremit> hm 8192 driver ..
Nov 08 10:11:59 <ag_melbourne> drivers have been updated to those currently available
Nov 08 10:12:12 <veremit> there used to be a few variants of that that I tried once
Nov 08 10:12:22 <veremit> ag_melbourne .. uname -a ?
Nov 08 10:12:45 <ag_melbourne> Linux beaglebone 4.1.10-ti-r24 #1 SMP PREEMPT Thu Oct 22 06:51:21 UTC 2015 armv7l GNU/Linux
Nov 08 10:13:14 <veremit> hmm thought they would have fixed it by 4.x
Nov 08 10:13:21 <ag_melbourne> variants? really?
Nov 08 10:13:34 <veremit> ag_melbourne .. yes I had a rtl8188 driver once
Nov 08 10:14:10 <ag_melbourne> so... what do I do?
Nov 08 10:14:33 <veremit> ok .. https://wiki.debian.org/rtl819x .. that says 8192cu should be fine for that chipset
Nov 08 10:16:55 <ag_melbourne> yes, its why I am here, I've searched extensively to help myself, I think there is a bug  with Jessie--drivers
Nov 08 10:19:04 <veremit> ag_melbourne .. have you done the firmware blobs from .. https://wiki.debian.org/rtl819x#Debian_8_.22Jessie.22
Nov 08 10:20:35 <veremit> unfortunately these mini cards can be a right royal pita .. I had to do a lot of googling after buying one model Completely unsupported by linux !
Nov 08 10:20:45 <ag_melbourne> in a prior irc session I was recommended 4.1.10-ti-r24, so not yet, it is such a painful process to change images
Nov 08 10:21:21 <ag_melbourne> the dongle I have listed is fine under wheezy
Nov 08 10:21:40 <veremit> yes, I suspect a more tolerant driver ..
Nov 08 10:21:56 <veremit> and/or fluke :)
Nov 08 10:22:38 <veremit> what do you get from 'dmesg|grep firmware' ?
Nov 08 10:23:31 <ag_melbourne> sall I follow you link above?
Nov 08 10:23:34 <veremit> oo just noticed I didn't fix my work desktop .. lol ..  enp1s0: unable to load firmware patch rtl_nic/rtl8168e-3.fw (-2)
Nov 08 10:23:47 <veremit> ag_melbourne .. yes, that doesn't depend on the kernel
Nov 08 10:24:19 <ag_melbourne> ok.. il''l be a couple of minutes...
Nov 08 10:24:27 <veremit> np :) tyt
Nov 08 10:32:44 <veremit> ooo proper broke it lol
Nov 08 10:42:59 <ag_melbourne> I'm back, did https://wiki.debian.org/rtl819x#Debian_8_.22Jessie.22, no USB, no ethernet, WIFI CONNECTS :)
Nov 08 10:43:55 <ag_melbourne> However dongle lamp does not flicker at all, steady on
Nov 08 10:45:03 <tbr> possibly different driver/firmware version and thus different behaviour?
Nov 08 10:46:26 <ag_melbourne> tbr, yes but not helpful...it is helpful to show alive ( lamp on ) and even more helpful to show activity; flickering
Nov 08 10:49:24 <ag_melbourne> andrew thinks he is a bit happier...it would be good to have a central repository
Nov 08 10:52:21 <ag_melbourne> Thank you for your assistance veremit, defiant :)
Nov 08 10:52:41 <veremit> np
Nov 08 10:53:43 <ag_melbourne> How does feedback ( in this case centraizing the driver and flickering ) get to where it's needed?
Nov 08 10:55:48 <veremit> probably a mailing-list somewhere ..
Nov 08 10:56:19 <ag_melbourne> ...everything is somewhere :/
Nov 08 10:58:03 <veremit> ag_melbourne .. starting point .. https://wireless.wiki.kernel.org/en/developers
Nov 08 10:59:18 <ag_melbourne> thanks, I will try
Nov 08 11:08:52 <zmatt> cool, I zapped a mosquito with an electric swatter and it got stuck in it but with wing-motors still enabled... by itself that's not remarkable, but then I noticed its wing frequency lined up
Nov 08 11:09:02 <zmatt> just right with the pwm of my lcd backlight
Nov 08 11:09:54 <zmatt> allowing the motion of wings to be viewed in slow-motion in the "strobe" light of my monitor
Nov 08 11:23:47 <veremit> zmatt.. its the little things ;) heh
Nov 08 11:24:06 <veremit> and .. err .. you have a Monitor that strobes, still?!
Nov 08 11:24:55 <zmatt> veremit: eh, most backlights do unless they're at 100%
Nov 08 11:25:11 <veremit> noticeably?!
Nov 08 11:25:54 <zmatt> normally? no.  if you use their light to view a fast-moving object? yes.
Nov 08 11:28:20 <zmatt> apparently the mosquito was flapping its wings at nearly an integer multiple of the pwm frequency
Nov 08 11:28:48 <veremit> but the 'beating' effect shows up the beating .. haha
Nov 08 11:28:56 <veremit> [of the wings]
Nov 08 11:31:13 <ag_melbourne> Good night from Melbourne :)
Nov 08 11:31:44 <veremit> nn
Nov 08 12:47:19 <_cpo__> hi
Nov 08 12:47:26 <_cpo__> i need help.:-)
Nov 08 12:48:30 <veremit> go see a doctor :D
Nov 08 12:49:05 <_cpo__> i'm using the freedombox image for the beaglebone (dd if=freedombox-unstable-free_2015-10-18_beaglebone-armhf.img | pv | dd of=/dev/mmcblk0), but the freedombox does not start. the sd-card is from sandisk. without the sd-card the box starts without problems, with the sd-card the box doesn't boot.
Nov 08 12:49:20 <_cpo__> veremit: :-) beaglebone doc?
Nov 08 12:50:27 <tbr> _cpo__: do you hold down the button S2 while powering up the board?
Nov 08 12:50:33 <veremit> hmm 1) whynot 'dd if=<img> of=/dev/mmcblk0' ... 2) you did unplug, hold Boot switch, Apply power.
Nov 08 12:50:55 <tbr> veremit: pv gives progress indication
Nov 08 12:51:06 <veremit> ah .. I use dcfldd :D
Nov 08 12:51:35 <veremit> but a useful note nontheless :)
Nov 08 12:52:13 <_cpo__> btr: no, i've pluged only the power supply into the bbone.
Nov 08 12:53:04 <_cpo__> ok, it try it.
Nov 08 12:53:14 <veremit> _cpo__ .. in order for the SD boot to work .. you have to power off, THEN hold button, THEN power up ..
Nov 08 12:53:35 <veremit> whether usb or DC barrel
Nov 08 12:53:49 <veremit> the s2 button is only 'read' when powering up
Nov 08 12:55:41 <_cpo__> is the boot button the button named with power?
Nov 08 12:56:20 <tbr> no, it says "S2" next to it
Nov 08 12:56:32 <tbr> it's close to the µSD and HDMI
Nov 08 12:57:05 <veremit> we call it the 'Boot' button, its opposite end of the board from 'power' and 'reset'
Nov 08 12:59:07 <_cpo__> sry, for this stupid questions, how long ? until it boots or short
Nov 08 12:59:08 <_cpo__> ?
Nov 08 13:01:34 <_cpo__> i'm pressed the button, but it doesn't boot. shoul i press the button until it boots?
Nov 08 13:02:29 <veremit> do you haev a serial debug cable?
Nov 08 13:03:09 <_cpo__> veremit: no.
Nov 08 13:03:41 <veremit> I highly recommend investing in one, especially to troubleshoot boot problems :)
Nov 08 13:07:00 <_cpo__> veremit: yes, i will do, but it's sunday, the markets here a closed. the only which give a light is the power led. but if a remove the sd-card the box make life signs:-)
Nov 08 13:08:01 <veremit> hmm .. well if the image is good .. and the sd card is good .. you should see at least a heartbeat pattern on the 4th led in addition to power.
Nov 08 13:08:30 <veremit> but without a serial cable .. you can;t tell whether the sd card is not being read .. or there's a filesystem problem or what :/
Nov 08 13:08:43 <veremit> have you tried with another uSD card and/or another image file?
Nov 08 13:08:52 <veremit> [process of elimination]
Nov 08 13:09:42 <_cpo__> veremit: hm, ok, yes i've tried several uSD cards, but only the freedombox image. a serial cable, is it a microhdmi?
Nov 08 13:10:49 <veremit> the uHDMI is for video/audio
Nov 08 13:10:51 <tbr> _cpo__: did you decompress the image before DDing it?
Nov 08 13:11:06 <_cpo__> tbr: yes.
Nov 08 13:11:07 <veremit> tbr .. looks like it to me ..
Nov 08 13:11:24 <veremit> only other thing to do is loop-mount it ..
Nov 08 13:11:29 <veremit> is there a checksum for it ?
Nov 08 13:11:33 <veremit> either zipped or not?
Nov 08 13:11:46 <veremit> I've downloaded corrupt images before
Nov 08 13:11:54 <tbr> or just plug it into a linux machine and see if partitions are in order
Nov 08 13:13:15 <veremit> that too ^^
Nov 08 13:13:57 <_cpo__> hmm, ok, it seems not to be a beagleboneboard- problem, more a freedombox- problem
Nov 08 13:15:18 <_cpo__> i thout the freedombox is the best security distro for beagleboneboard, there are alternatives?
Nov 08 13:18:05 <_cpo__> tbr: yes, the partitions are in the right order, i think.
Nov 08 13:18:10 <veremit> _cpo__ .. have you followed instructions at http://freedombone.uk.to/installation.html ?
Nov 08 13:20:03 <veremit> the ordinary beaglebone and black boards are very different :)
Nov 08 13:20:14 <_cpo__> veremit: no from https://wiki.debian.org/FreedomBox/Download
Nov 08 13:20:27 <_cpo__> veremit: oh, sry, it is a beaglebone black
Nov 08 13:21:40 <veremit> ah my bad ye s I see .. https://wiki.debian.org/FreedomBox/Download
Nov 08 13:24:24 <_cpo__> veremit: and i decompress and dded it on the sd-card
Nov 08 13:25:12 <veremit> the alternative is to do it within debian .. via https://wiki.debian.org/FreedomBox/Hardware/Debian
Nov 08 13:26:00 <veremit> if you have a stock debian there .. or can flash one from the main site
Nov 08 13:26:43 <veremit> recommended url for base images .. http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03
Nov 08 13:30:05 <_cpo__> veremit: flash means, to copy the image from freedombox to the beagle bone internal memory?
Nov 08 13:31:33 <veremit> yes
Nov 08 13:31:45 <veremit> ie. write the emmc
Nov 08 13:33:49 <_cpo__> veremit: hm, till now, i've tried to boot it from the sd-card, ... is it better? or is it senseless to use the sd-card. hm
Nov 08 13:35:06 <veremit> well you've got a chunk of onboard storage ..
Nov 08 13:35:14 <veremit> its a choice really
Nov 08 13:43:14 <_cpo__> veremit: ok, i understand. i'm downloading  the image from freedombox, maybe it's corrupt, and repeat it with dd.
Nov 08 13:43:26 <_cpo__> veremit: but dd is ok?
Nov 08 13:44:34 <veremit> dd should be fine, yes
Nov 08 13:44:46 <veremit> there are some gpg commands there to check it
Nov 08 13:48:25 <_cpo__> veremit: with root is fine, too?
Nov 08 13:49:52 <veremit> yeah
Nov 08 13:59:15 <_cpo_> re
Nov 08 14:01:52 <zmatt> lol, ARM mailing fail
Nov 08 14:02:03 <zmatt> "was viewed 145 email.digest.times and commented on by 0 email.digest.people"
Nov 08 14:17:18 <Set_> hello...
Nov 08 14:17:43 <Set_> Man...I am stuck again. My Angstrom BBB is too full of updates. I finally updated the packages.
Nov 08 14:17:59 <Set_> Besides that mess...I cannot set the time on my Debian BBB.
Nov 08 14:18:08 <Set_> How can I set the time and date on my Debian BBB?
Nov 08 14:19:06 <Koth> type after me: man date
Nov 08 14:19:13 <Set_> man date
Nov 08 14:19:23 <Koth> good
Nov 08 14:19:31 <Koth> now do that in a console window
Nov 08 14:19:35 <Set_> Okay.
Nov 08 14:19:37 <Set_> Please hold.
Nov 08 14:20:22 <Set_> Okay...
Nov 08 14:20:26 <Set_> Now what?
Nov 08 14:20:36 <Koth> read it
Nov 08 14:20:39 <Koth> understand it
Nov 08 14:20:41 <Koth> learn
Nov 08 14:20:45 <Set_> Okay...please hold.
Nov 08 14:22:08 <Set_> -R
Nov 08 14:22:09 <Set_> ?
Nov 08 14:22:32 <Set_> well...-R "Today's date"?
Nov 08 14:22:39 <Koth> http://26-26-54.hardwarebug.org/30
Nov 08 14:22:43 <Set_> Yikes...I know.
Nov 08 14:23:16 <Set_> I have been reading on dates and time at debian.org but I got nothing.
Nov 08 14:23:24 <Set_> I followed this book but the book if for Angstrom.
Nov 08 14:24:19 <Koth> you should try a linux basics book
Nov 08 14:24:33 <Set_> I have many.
Nov 08 14:24:43 <Set_> I still have problems starting out with Debian.
Nov 08 14:24:49 <Set_> Every time!
Nov 08 14:26:55 <Koth> but you understand that debian is just a linux distribution?
Nov 08 14:26:56 <Set_> I tried the -R method. I got nothing.
Nov 08 14:27:00 <Set_> Yep.
Nov 08 14:27:24 <Set_> I understand.
Nov 08 14:27:38 <Koth> have you read the manpage and understood what -R does?
Nov 08 14:27:45 <Set_> Yes.
Nov 08 14:27:51 <Koth> and what does it do?
Nov 08 14:28:14 <Set_> At least...I figured I could understand. It states the day, date, and month.
Nov 08 14:28:27 <veremit> Set_ .. is your bbb connected to the internet?
Nov 08 14:28:37 <Set_> Yes.
Nov 08 14:28:46 <Set_> Not with Ethernet, though.
Nov 08 14:28:54 <veremit> can you ping google/ etc
Nov 08 14:29:00 <Set_> I am online via this site and PuTTY.
Nov 08 14:29:01 <veremit> if so, you can use ntp
Nov 08 14:29:32 <Set_> I tried ntp and there were three options (0., 1., and 2.).
Nov 08 14:29:46 <Set_> I typed in ntp.pool.org
Nov 08 14:30:04 <Set_> in the quotation marks.
Nov 08 14:30:17 <veremit> you should be able to "ntpdate ntp.pool.org"
Nov 08 14:30:27 <Set_> I had to restart to reconfigure it.
Nov 08 14:30:33 <Set_> I can and I can change it in nano.
Nov 08 14:30:56 <Set_> But when I call the date, the system does not understand ntpdate-sync.
Nov 08 14:30:58 <veremit> if you have ntpd running .. you have to do something slightly different
Nov 08 14:31:08 <Set_> Oh.
Nov 08 14:31:11 <veremit> oh balls .. its system0shitty0d
Nov 08 14:31:18 <veremit> yeah I'm baling on that one
Nov 08 14:32:05 <veremit> normally, I'd say /etc/init.d/ntpd stop then ntpd -g -q then /etc/init.d/ntp start
Nov 08 14:32:10 <veremit> but 90% sure that won't work lol
Nov 08 14:32:35 <veremit> only 90 though .. so worth a try :D
Nov 08 14:32:39 <Set_> it is okay. I will keep trying. I am sorry to bother people again.
Nov 08 14:36:00 <veremit> systemd-timesyncd
Nov 08 16:49:39 <Set_> Hello...
Nov 08 16:49:50 <Set_> .gpg issues here.
Nov 08 16:50:25 <Set_> I followed what BBB let loose in 2014 for builds via Debian for BBB Wikipage.
Nov 08 16:51:02 <Set_> So...how do I get around the error codes ".gpg" files?
Nov 08 16:51:14 <Set_> I listened to what the Wiki said but that is bunk.
Nov 08 16:51:29 <Set_> The Wiki was updated in 2015, too.
Nov 08 16:53:18 <Set_> Okay...I know. Things are duplicating fast. I will just wait for updates.
Nov 08 16:53:22 <Set_> Until then!
Nov 08 16:57:19 <_cpo_> veremit: re, thanks a lot for your great support *hugs from me, and smile from my wife*.the problem with the beaglebone baord and freedombox was that dd writes a corruprt fs on the sd-card. i used gnome-disks and it works great.
Nov 08 16:58:35 <veremit> oh weird
Nov 08 16:59:10 <veremit> gratz on gettin it workin
Nov 08 16:59:36 <_cpo_> veremit: :-)
Nov 08 17:00:36 <veremit> wish this ebuild nonsense was more .. sense.
Nov 08 17:01:01 <veremit> time for a rest methinks .. python will strangle me else
Nov 08 17:01:25 <_cpo_> veremit: yeah, it was great, i try it in the next time. bye, we go to the pub. :-)
Nov 08 17:01:33 <veremit> cheers ^^
Nov 08 17:01:46 <_cpo_> veremit: cheers :-)
Nov 08 18:48:58 <GenTooMan> Hmm seems no gentoo BBB images.. here I was hoping too be lazy.
Nov 08 20:06:34 <wmat> GenTooMan: the gentoo wiki has build instructions though
Nov 08 20:14:53 <GenTooMan> hmmm Ok
Nov 08 20:58:06 <dgmurdockiii> can i use a begal board as a arduno alterno
Nov 08 20:58:41 <dgmurdockiii> alternative
Nov 08 21:02:13 <wmat> dgmurdockiii: i wouldn't
Nov 08 21:02:51 <dgmurdockiii> for driving LEDs
Nov 08 21:02:57 <dgmurdockiii> what the best options
Nov 08 21:03:59 <tbr> if it's just leds and nothing else, any microcontroller
Nov 08 21:07:17 <GenTooMan> perhaps a bit more detail you can do that with $10 eval boards from TI. If you give some more information that might help.
Nov 08 21:35:56 <dgmurdockiii> ok
Nov 08 22:05:46 <GenTooMan> :D
Nov 09 00:08:49 * mezydlop slaps contempt around a bit with a large fishbot
Nov 09 01:08:57 <rhodes> Hello, i wonder if i have killed my BBB after plugging it in a 9V instead of a 5V power supply, only the PWR led shines, is there anything that i can do?
Nov 09 01:28:39 <GenTooMan> I am uncertain I would have to hunt down the schematics and lurk at it.
Nov 09 01:32:44 <rhodes> I'm still trying to see if its still alive, i'll report back!
Nov 09 01:33:27 <GenTooMan> Use USB
Nov 09 01:35:50 <rhodes> I'm currently using it, 3.0 one to be exact.
Nov 09 01:39:29 <GenTooMan> I doubt the # will do a thing it just needs 200-400ma according to the specs.
Nov 09 01:40:16 <GenTooMan> You should be able to ping some IP address I can't remember 192.168.7.1 I think it creates when it boots for the default
Nov 09 01:42:54 <rhodes> Thanks GenTooMan, but i gotta go now, i'll get back here soon and report back!
Nov 09 01:42:57 <GrumpeiYokoi> From the host you can ping the BBB at 192.168.7.2
Nov 09 01:43:14 <GrumpeiYokoi> The host registers as 192.168.7.1
Nov 09 01:52:04 <zmatt> if only the power led shines it's not booting
Nov 09 01:52:17 <zmatt> but not broken either
Nov 09 01:52:23 <zmatt> the pmic has overvoltage protection
Nov 09 02:06:21 <Randy___> hello
Nov 09 02:11:17 <alairock> I have an LED array in P8_13 and my only options seems to be boolean (On/Off)
Nov 09 02:11:32 <alairock> However I want to fade this LED array.
Nov 09 02:12:11 <alairock> Is it a different pin I need to put it in?
Nov 09 02:12:15 * alairock nooob
Nov 09 02:57:08 <Set_> Hello...
Nov 09 02:57:14 <Set_> Dudes...guess what?
Nov 09 02:57:34 <Set_> I got the dang Debian image (new) booted finally.
Nov 09 02:57:37 <Set_> But...
Nov 09 02:58:00 <Set_> There is one small problem. I have another SD card in my slot. Oops.
Nov 09 02:58:13 <Set_> I keep making these mistakes.
Nov 09 02:58:36 <Set_> I booted via SD card a Wyliodrin.com BBB image. Dang it!
Nov 09 02:58:42 <Set_> I will just have to see what happens.
Nov 09 02:59:05 <Set_> Who knows node.js?
Nov 09 02:59:39 <zmatt> alairock: it's a pwm-capable pin, but may need to be explicitly configured as such
**** ENDING LOGGING AT Mon Nov 09 02:59:59 2015