**** BEGIN LOGGING AT Mon Jul 13 02:59:59 2015
Jul 13 05:22:31 <Sager_> Hello All, I am trying to flash my BBB and I am not having any success. I think the SD Card (64GB) may be too big, has anyone had success flashing theirs with this size of SD card?
Jul 13 05:36:14 <tbr> Sager_: that shouldn't matter, but you never know with TI...
Jul 13 05:37:25 <Sager_> Going to try a third image... what seems to end up happening is that the first led will blink twice and the third one seems to have a constant low powered twinkle.. and every now and then the second will blink. I have tried leaving it for up to 2 hours
Jul 13 05:37:41 <av500> it should not take 2hours
Jul 13 05:37:48 <av500> have another card to try?
Jul 13 05:38:00 <Sager_> yeah but they are all 64GB
Jul 13 05:39:09 <tbr> Sager_: are you sure it boots from SD and not whatever is on the emmc?
Jul 13 05:39:49 <Sager_> I am holding down the boot button when I plug it in. Just followed the instructions
Jul 13 05:54:36 <tbr> Sager_: mhm, how do you prepare the card? do you have a UART cable?
Jul 13 06:06:48 <keesj_> Sager_: often the problem is related to the flashing of the card itself (for example because of automount on your pc)
Jul 13 07:08:40 <Sager_> no luck with that image either
Jul 13 07:37:40 <Costin> hello
Jul 13 07:37:44 <Costin> anyone here ?
Jul 13 07:38:18 <Costin> need some info/help about configuring USB slave port
Jul 13 07:38:40 <Costin> someone ? anyone ?
Jul 13 07:40:04 <tbr> be more specific, maybe someone will answer...
Jul 13 07:40:39 <Costin> well, i need to configure USB slave port to emulate a dot matrix printer
Jul 13 07:40:49 <Costin> and save all it catches in a file
Jul 13 07:41:23 <Costin> I found someting that would work:https://android.googlesource.com/kernel/common/+/a7827a2a60218b25f222b54f77ed38f57aebe08b/Documentation/usb/gadget_printer.txt
Jul 13 07:41:43 <Costin> but i don;t know hot to implement/make that device block g_printer
Jul 13 07:43:46 <Costin> anyone ?
Jul 13 07:43:56 <Costin> help ?
Jul 13 07:46:46 <tbr> looks like you need to build a kernel module
Jul 13 07:47:17 <Costin> "Gadget drivers" ? it's enabled by default in beagleboard
Jul 13 07:48:32 <tbr> at least the 4.0 kernel package I use on my bone has g_printer already built
Jul 13 07:48:59 <tbr> then all you need to do is disable the script that enables g_multi and enable g_printer instead
Jul 13 07:49:33 <Costin> root@beaglebone:~# modinfo g_printer filename:       /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget/g_printer.ko license:        GPL author:         Craig Nadler description:    Printer Gadget srcversion:     DDF852A83CCE4691D9F9B96 depends:        libcomposite intree:         Y vermagic:       3.8.13-bone70 SMP mod_unload modversions ARMv7 thumb2 p2v8 parm:           idVendor:USB Vendor ID (ushort) parm:           idProduct:U
Jul 13 07:49:41 <Costin> how do i do that ?
Jul 13 07:49:57 <tbr> you're running a recent debian image?
Jul 13 07:50:02 <Costin> lastest
Jul 13 07:50:10 <Costin> installed on the sd card
Jul 13 07:50:25 <Costin> *latest
Jul 13 07:50:34 <tbr> check  /opt/scripts/boot/
Jul 13 07:50:43 <Costin> ok, what to check there ?
Jul 13 07:51:07 <Costin> am335x_evm.sh       beagle_x15.sh       capemgr.sh          generic-startup.sh  generic.sh          omap3_beagle.sh     omap5_uevm.sh
Jul 13 07:51:11 <tbr> I guess you'll need to disable the am335x_evm.sh script from being run
Jul 13 07:51:27 <Costin> just by moving it to another location ?
Jul 13 07:51:51 <tbr> there are more elegant ways
Jul 13 07:52:05 <tbr> you could also just modify it to your needs
Jul 13 07:52:20 <tbr> as you want to load g_printer instead
Jul 13 07:52:32 <Costin> like ? i;m not familliar to debian distros. i'm using a lot of centos/red hat
Jul 13 07:52:37 <tbr> please note that you will NOT be able to access the board anymore over usb
Jul 13 07:52:58 <tbr> do you know what a shell script is?
Jul 13 07:53:06 <Costin> no problem, i'm not using it at all. only ssh via ethernet
Jul 13 07:53:43 <Costin> sorry, i just read that post where you said i can modify it to my needs.
Jul 13 07:53:50 <Costin> ok, i-ll look into it
Jul 13 07:53:54 <tbr> :)
Jul 13 07:54:50 <Costin> shit !! there are a lot of lines in that script...
Jul 13 07:55:07 <tbr> meh, essentially just put a modprobe at the top and exit 0
Jul 13 07:55:41 <tbr> as you don't need all the fluff that they do to set up gmulti
Jul 13 07:56:49 <Costin> i tried to run modprobe in shell, but it simply didn't work. was it because g_multi was already loaded ?
Jul 13 07:56:55 <tbr> yes
Jul 13 07:57:04 <tbr> you'd need to unload g_multi first
Jul 13 07:57:35 <Costin> so, if i move this file, reboot, and do some testing from shell before implement it in a script, it should work ?
Jul 13 07:58:00 <tbr> sure, or you could just rmmod or modprobe -r
Jul 13 07:58:31 <Costin> thank you a lot !!!
Jul 13 07:58:38 <tbr> np
Jul 13 08:09:05 <Costin> one more question
Jul 13 08:11:26 <Costin> how do i disable X ? i modified inittab to have default runlevel to 3, but X still starts
Jul 13 08:12:12 <woglinde> systemd
Jul 13 08:12:15 <tbr> disable the relevant systemd services, I guess
Jul 13 08:14:02 <Costin> i'm not familliar at all with debian distros. In centos i would use chkconfig
Jul 13 08:14:13 <Costin> how do i use this systemd ?
Jul 13 08:15:26 <woglinde> lol
Jul 13 08:15:37 <woglinde> systemd comes from redhat
Jul 13 08:15:54 <woglinde> where did you live the last 3 years?
Jul 13 08:16:06 <Humpelstilzchen> .o0(you better do not use it)
Jul 13 08:16:36 <woglinde> Humpelstilzchen are you going to break your laptop too, when some metions systemd?
Jul 13 08:16:47 <tbr> and RHEL7 has systemd IIRC :)
Jul 13 08:17:04 <Humpelstilzchen> woglinde: hmm?
Jul 13 08:18:02 <woglinde> Humpelstilzchen I heard a story that some smashed his laptop to the floor, in a discussion about systemd
Jul 13 08:19:07 <philenotfound> woglinde: well, it did disable systemd on that machine
Jul 13 08:19:08 <Costin> i didn't say i'm an expert...
Jul 13 08:19:44 <Humpelstilzchen> woglinde: aah sure, I probably can smash one. If you like, we can do a systemd challange on youtube ;)
Jul 13 08:20:00 <Costin> i use yum, rpm, chkconfig, move/delete scripts rom /etc/init.d or /etc/rc.d ....
Jul 13 08:20:31 <Costin> ok, i got the point. i'll just google it for systemd
Jul 13 08:20:46 <woglinde> Costin systemctl is the command
Jul 13 08:21:05 <woglinde> and you need systemctl stop service
Jul 13 08:21:10 <woglinde> and systemctl mask service
Jul 13 08:30:15 <Costin> i just uninstalled lightdm. I'll speed up the system by removing unnecessary services
Jul 13 09:22:44 <Costin> does anyone know how to speedup BBB startup ? it takes ~1-2 min to boot and have the network ready. also, looking at the monitor attached, it shows a lot of errors "libphy: PHY 4a101000.mdio:01 not found" and "net eth0: phy 4a101000.mdio:01 not found on slave 1"
Jul 13 09:26:27 <jacxon> hello all
Jul 13 09:26:36 <Costin> fuck... it seems like there are some kernel issues....
Jul 13 09:26:40 <Costin> hi
Jul 13 09:27:05 <jacxon> i have a trouble with my beaglebone black
Jul 13 09:28:02 <jacxon> it doesnt support usb keyboard and mouse together
Jul 13 09:28:26 <jacxon> together*
Jul 13 09:28:55 <tbr> jacxon: how do you connect those?
Jul 13 09:29:08 <jacxon> using a hub
Jul 13 09:29:09 <tbr> Costin: sounds like you might have a hw issue
Jul 13 09:29:21 <tbr> jacxon: and it works if you only connect one of them to the hub?
Jul 13 09:29:39 <jacxon> yes
Jul 13 09:29:48 <jacxon> exactly
Jul 13 09:30:15 <tbr> how are you powering the BBB?
Jul 13 09:30:37 <jacxon> using 5v 2a dc adapter
Jul 13 09:30:59 <tbr> try a different usb hub
Jul 13 09:31:12 <jacxon> am already tried it
Jul 13 09:32:08 <woglinde> musb again
Jul 13 09:32:20 <av500> always musb
Jul 13 09:32:20 <woglinde> jacxon which kernel do you have?
Jul 13 09:32:23 <woglinde> uname -a
Jul 13 09:32:35 <jacxon> kernal v3.8
Jul 13 09:32:38 <woglinde> I wonder how the sunxi guys came along
Jul 13 09:32:57 <woglinde> might be fixed in latest upstream
Jul 13 09:33:07 <woglinde> 4.1
Jul 13 09:33:16 <tbr> Kernal? Comodore revival?
Jul 13 09:33:57 <jacxon> am using latest debian version
Jul 13 09:34:26 <woglinde> carnival
Jul 13 09:34:32 <woglinde> kernival
Jul 13 09:35:22 <jacxon> the kernal is the one which comes with beaglebones version of debian
Jul 13 09:35:56 <tbr> hint: It's kernEl not kernAl
Jul 13 09:36:24 <woglinde> you could try newer kernels from here
Jul 13 09:36:24 <jacxon> oh sorry
Jul 13 09:36:25 <woglinde> http://repos.rcn-ee.com/debian/pool/main/l/linux-upstream/
Jul 13 09:37:24 <jacxon> ohk
Jul 13 09:38:06 <jacxon> which of them should i use?
Jul 13 09:39:15 <jacxon> hello anyone plese help m
Jul 13 09:39:24 <jacxon> e
Jul 13 09:40:31 <woglinde> hm looks like you cant
Jul 13 09:40:56 <woglinde> because gst-inspect reads the .so files only
Jul 13 09:41:05 <woglinde> and there is no hint if it comes from bad or moon
Jul 13 09:45:15 <jacxon> i think my kernel version is 3.8.13
Jul 13 09:45:44 <jacxon> and i have the latest version
Jul 13 09:47:31 <akhil> hello
Jul 13 09:48:17 <jacxon> please anyone help me
Jul 13 10:09:42 <akhil> hello all
Jul 13 10:20:39 <akhil> i need a help
Jul 13 10:21:25 <akhil> i cant use usb mouse and keyboard at the same time using the port
Jul 13 10:24:28 <akhil> am using usb 2.0 hub and kernel is v3.8.13
Jul 13 10:26:04 <akhil> anyone please help me
Jul 13 11:59:24 <akhil> hello usb hub is not working with my beaglebone black why?
Jul 13 12:01:43 <agmlego> akhil: USB on the bone is rough at best. Did you even try any of the suggestions others here have given you?
Jul 13 12:01:46 <av500> akhil: powered hub?
Jul 13 12:02:08 <akhil> yes using external power supply
Jul 13 12:04:00 <akhil> yes am powered the hub using beaglebone and tried with 5.0 v 2a external power supply
Jul 13 12:04:29 <agmlego> How are you powering the *hub*?
Jul 13 12:04:57 <agmlego> Because if the answer is "off the USB port on the bone", that is the wrong answer.
Jul 13 12:05:14 <akhil> red wire disconnected from the hub and feed a 5.0v there and gnd makes common
Jul 13 12:05:15 <agmlego> Also, what keyboard and mouse are you trying to use, and have you tried different ones?
Jul 13 12:05:33 <agmlego> Becuase not all keyboards and mice draw the same amount of power.
Jul 13 12:05:46 <akhil> yes while using seperatly its works!!\
Jul 13 12:06:00 <agmlego> ...that does not disprove my point.
Jul 13 12:06:16 <agmlego> In fact, that is the *reason* I ask the questionm.
Jul 13 12:07:51 <agmlego> Where are you sourcing the 5V that you are putting into the hub on the red wire?
Jul 13 12:08:36 <akhil> another variable power supply capable for deliver 2a current\
Jul 13 12:08:51 <agmlego> OK, so that probably is not the problem.
Jul 13 12:09:07 <agmlego> What errors do you get in the system logs?
Jul 13 12:09:17 <akhil> am disconnect red wire to BBB and powered device externally(mouse and keyboard)
Jul 13 12:09:23 <agmlego> And...have you tried other keyboards and nice?
Jul 13 12:09:30 <agmlego> *mice
Jul 13 12:09:53 <akhil> when am using keybord only in that hub its ok
Jul 13 12:10:07 <agmlego> Yes, you have said that.
Jul 13 12:10:11 <akhil> and mouse only it also worrks
Jul 13 12:10:18 <agmlego> And you have said that too.
Jul 13 12:10:33 <agmlego> But when you use both together...what happens?
Jul 13 12:10:35 <akhil> oh sorry
Jul 13 12:11:01 <akhil> both mouse and keyboard not works
Jul 13 12:11:05 <agmlego> Do you get an error message?
Jul 13 12:11:14 <akhil> no!
Jul 13 12:11:29 <agmlego> Are you sure?
Jul 13 12:11:33 <tbr> dmesg → pastebin
Jul 13 12:11:33 <akhil> yes
Jul 13 12:11:35 <agmlego> Did you check the system logs?
Jul 13 12:12:03 <akhil> no am new to BBB how can i check that?
Jul 13 12:12:18 <agmlego> The same way you check them on any other Linux.
Jul 13 12:12:38 <agmlego> And if you need help with that, Google works well for instruction. ;-P
Jul 13 12:13:14 <akhil> ok i'll check it and get back to you
Jul 13 12:14:00 <akhil> could you please provide me your mail id?
Jul 13 12:14:03 <agmlego> No.
Jul 13 12:14:13 <akhil> oh sorry
Jul 13 12:14:15 <agmlego> Put a link to a pastebin here.
Jul 13 12:14:38 <agmlego> (and if you are unsure what that is...Google will help)
Jul 13 12:14:49 <akhil> ok
Jul 13 12:16:20 <agmlego> akhil: Basically, we recognize that you probably have a legitimate issue, but you are making it difficult to help you by being annoyingly persistent, and lacking in details. So, some time spent trying to learn how to do some basic stuff would be time well spent on your end.
Jul 13 12:16:51 <agmlego> akhil: Also, reading the first link in the channel topic, and all the links therein, would be a good use of time as well.
Jul 13 12:16:59 <agmlego> Maybe read it on the bus to work.
Jul 13 12:17:56 <akhil> ok thank you agmlego ..i'll learn it thanks for your help
Jul 13 12:18:05 <agmlego> Not a problem.
Jul 13 12:53:26 <akhil> hello
Jul 13 12:56:27 <spm_draget> Where woudl I find the revision number on the board?
Jul 13 12:56:37 <spm_draget> * Beaglebone Black
Jul 13 12:56:49 <agmlego> Usually on a sticker label, often near the Ethernet port.
Jul 13 12:56:59 <agmlego> Sometimes on the opposite side.
Jul 13 12:57:06 <agmlego> WHite label, black text.
Jul 13 12:57:19 <spm_draget> Ah, on the side! I looked everywhere at the bottom and top, not the side xD Thanks
Jul 13 12:58:43 <agmlego> No problem.
Jul 13 13:00:56 <spm_draget> Does anyone know if the freebsd port has longer/better security support than the debian port?
Jul 13 13:01:57 <av500> no idea
Jul 13 13:02:08 <agmlego> *BSD tends to be more secure than Linux in general.
Jul 13 13:02:35 <agmlego> Usually at the cost of even more delays in availablke software packages.
Jul 13 13:03:36 <spm_draget> Yeah, I know. I guess I will stick to debian. My BBB will not have external users and I will make sure to limit the daemons properly. So all that is left to worry about would be the kernel, which would leave little attack surface
Jul 13 13:04:28 <agmlego> spm_draget: What are you trying to protect it from?
Jul 13 13:04:48 <agmlego> Because there are an awful lot of servers out there in the wild running Debian with no issues. ;-P
Jul 13 13:04:51 <LetoThe2nd> agmlego: bad karma
Jul 13 13:05:19 <agmlego> No hope there. ;-P
Jul 13 13:06:27 <spm_draget> Attack vectors always depend on the ammount of services you are running on a server, how they are configured and reachable and how quick you install updates. If you plan to leave a system unattended for a long time (which I plan with my BBB), the updateability is really an issue.
Jul 13 13:07:20 <spm_draget> CentOS is something you could ride in auto-update mode for many years… as long as your services are configured securely, you can keep it like this for a long time witout worrying.
Jul 13 13:07:21 <agmlego> so use debian.
Jul 13 13:07:30 <spm_draget> Yeah, as I said, I will stick with debian =)
Jul 13 13:43:22 <akhil_> hello
Jul 13 13:43:44 <agmlego> akhil_: You said that once already.
Jul 13 13:44:36 <akhil_> Jul 13 13:35:55 beaglebone kernel: [ 1108.368068] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 Jul 13 13:35:55 beaglebone kernel: [ 1108.368200] hub 1-0:1.0: port 1, status 0100, change 0001, 12 Mb/s Jul 13 13:35:55 beaglebone kernel: [ 1108.368245] usb 1-1: USB disconnect, device number 3 Jul 13 13:35:55 beaglebone kernel: [ 1108.368279] usb 1-1: unregistering device Jul 13 13:35:55 beaglebone kernel: [ 1108.368311] usb 1-1: unre
Jul 13 13:44:44 <agmlego> PASTEBIN
Jul 13 13:44:50 <akhil_> system log while connecting
Jul 13 13:44:58 <akhil_> ok
Jul 13 13:51:02 <akhil_> http://pastebin.com/5gZb41jS
Jul 13 13:52:16 <akhil_> agmlego : here is the pastebin
Jul 13 13:52:31 <agmlego> Well, that looks a lot like the kernel sees and registers both devices just fine.
Jul 13 13:52:55 <akhil_> ok
Jul 13 13:53:47 <akhil_> but as i told you .doesn't work together ....
Jul 13 13:54:16 <agmlego> OK. Well, I *could* go get my crystal ball...
Jul 13 13:54:40 <agmlego> Or you could save us all a lot of time and give more information than just "doesn't work".
Jul 13 13:54:41 <akhil_> ok thanks in advance ...
Jul 13 14:03:39 <akhil_> ie, am connected a usb hub to beaglebone ...and trying to connect usb mice and keyboard into hub....but when connecting keyboard only to the hub its works normally   ...and mice only it is also working but while connecting mouse and keyboard to the hub .both of them doesnt works .. ...am really sorry for my english ...
Jul 13 14:04:29 <agmlego> RIght, and we have all of that information.
Jul 13 14:04:38 <agmlego> What desktop environment are you using?
Jul 13 14:05:31 <agmlego> When you say "doesn't work", what do you mean? YOu cannot type, the NumLock LED does not respond, the mouse fails to move, the board summons the Nameless One from the deep to bring about the apocalypse?
Jul 13 14:05:53 <agmlego> Data data data. We cannot help without data.
Jul 13 14:10:07 <akhil_> yes num lock led blinks but cant type .. mouse led also blinks but fails to move .......like both are stucks
Jul 13 14:12:21 <agmlego> Mouse LED blinks? THat seems not ideal. Does it blink when it is plugged into the bone by itself?
Jul 13 14:14:17 <akhil_> yes my optical mouse blinks...
Jul 13 14:14:58 <agmlego> This is expected behavior?
Jul 13 14:15:12 <agmlego> I cannot say I have ever had an optical mouse that blinks.
Jul 13 14:15:21 <agmlego> In any case, moving on...
Jul 13 14:15:37 <agmlego> What desktop environment are you using?
Jul 13 14:17:19 <akhil_> linux debian
Jul 13 14:20:27 <agmlego> THat is a Linux distribution, not your desktop environment.
Jul 13 14:20:45 <agmlego> The desktop environment will be something like LXDE, or XFCE, or GNOME, or KDE.
Jul 13 14:31:28 <akhil_> MY DESKTOP ENVIRONMENT IS LXDE
Jul 13 14:31:47 <agmlego> THanks for shouting.
Jul 13 14:33:05 <akhil_> ok please help me
Jul 13 14:34:35 <agmlego> No, now I am busy at work.
Jul 13 14:34:53 <agmlego> Be patient; someone else in the channel may help you.
Jul 13 14:35:16 <akhil_> ok
Jul 13 14:42:48 <Technicus> Hello . . . where is the code that monitors the soft power button?
Jul 13 14:45:43 <woglinde> Technicus in the kernel?
Jul 13 14:52:49 <Technicus> I am trying to write a code that will send a pin high when the BeagleBone is on and low when it is off.
Jul 13 14:53:04 <Technicus> Where can I put the code to do that?
Jul 13 15:00:14 <myself> when you say "on", you mean has power? or the OS is booted and running or something? Because it sounds like you just described the Vcc pin..
Jul 13 15:10:40 <Technicus> How do I make a pin go high at boot, and then low at shutdown?
Jul 13 15:13:18 <av500> Technicus: 1) manage to make a pin go high or low
Jul 13 15:13:37 <av500> 2) write a systemd unit that will call you pin high/low script at boot/shutdown
Jul 13 15:22:30 <Technicus> How do I write a systemd unit?
Jul 13 15:23:17 <agmlego> I am positive there are absolutely no resources on thasst at all on the Internet. No point in even trying to look it up on Google.
Jul 13 15:23:42 <Technicus> How do I make gpio go high or low with sysfs?
Jul 13 15:23:46 <ogra_> no, you need to buy "systemd for dummies" from lennart ...
Jul 13 15:23:57 <agmlego> Not O'Reilly? -P
Jul 13 15:23:59 <Technicus> Ok great!
Jul 13 15:24:00 <ogra_> th eonbly valid source :)
Jul 13 15:24:43 <Technicus> What are different methods for making a pin go high or low?
Jul 13 15:25:09 <agmlego> I am positive there are absolutely no resources on that at all on the Internet. No point in even trying to look it up on Google.
Jul 13 15:26:29 <Technicus> I am trying to follow this tutorial . . . I am trying to make gpio_39 go high, pin 4 on p8.  I was thinking of doing it with sysfs, but have no experience with it.  I am having trouble getting started.
Jul 13 15:26:49 <Technicus> The device is a Beagle Bone Black.
Jul 13 15:27:37 <agmlego> We assumed so, this being the channel for that.
Jul 13 15:27:51 <agmlego> Which tutorial are following? What trouble are you having with it?
Jul 13 15:28:03 <agmlego> Is it summoning the Nameless One?
Jul 13 15:28:12 <agmlego> THat *is* a common issue these days.
Jul 13 15:28:46 <Technicus> Here is the tutorial: < http://www.armhf.com/using-beaglebone-black-gpios/ >.
Jul 13 15:45:42 <Technicus> So I issue the following instructions:
Jul 13 15:45:46 <Technicus> `echo 39 > /sys/class/gpio/export`
Jul 13 15:46:01 <Technicus> `echo high > /sys/class/gpio/gpio39/direction`
Jul 13 15:46:13 <Technicus> `echo 1 > /sys/class/gpio/gpio39/value~
Jul 13 15:46:28 <Technicus> but I do not see any changes at the pin.
Jul 13 15:46:38 <Technicus> I have a led connected
Jul 13 15:46:47 <Technicus> I also have a volt meter connected.
Jul 13 15:46:57 <Technicus> There is no change.
Jul 13 15:57:25 <nyo> maybe pill puldown/up ?
Jul 13 15:57:35 <nyo> *pin
Jul 13 15:58:49 <Technicus> Is pin 4 on the beagle bone black GPIO_39?
Jul 13 15:59:16 <Technicus> *P8 pin 4
Jul 13 16:01:04 <myself> according to the pinout I'm looking at, P8 pin 4 is mmc1_dat7
Jul 13 16:04:10 <Technicus> myself:Will you share with me what you are looking at?
Jul 13 16:04:33 <myself> https://www.google.com/search?q=beaglebone+black+pinout&tbm=isch
Jul 13 16:04:55 <myself> very first one, which is http://beagleboard.org/static/images/cape-headers.png
Jul 13 16:08:21 <myself> So I'm gonna go out on a limb, being a guy who's never done this, and say that unless you've taken steps to wrest control of that pin back from its MMC function, you probably don't want to use it. Start with something that's tagged as the mint-green GPIO instead, those are probably not otherwise-spoken-for.
Jul 13 16:10:41 <Technicus> Ok thanks.
Jul 13 16:26:32 <Technicus> How can I monitor if the system is doing a shutdown?
Jul 13 16:28:54 <Technicus> I am writing a systemd service that will manipulate a pin if the system begins a shutdown procedure.
Jul 13 16:29:59 <myself> I think you're out of scope for #beagle and should probably head to #your-distro-of-choice
Jul 13 16:30:00 * ogra_ thinks you might want to ask in #systemd (if that exists)
Jul 13 16:30:30 <myself> #systemd has 583 nicks in it
Jul 13 16:31:07 <ogra_> well, then there is hope that one of them can answer :)
Jul 13 16:43:21 <Technicus> With sysfs, how do I put a pin into tristate?
Jul 13 16:45:59 <Spirilis> set it to input mode I think
Jul 13 17:00:07 <yates> is there a recommended howto to interface with a serial device on the bbb?
Jul 13 17:00:15 <yates> using C
Jul 13 17:00:57 <agmlego> Probably the same way you interface with a serial device on any other platform.
Jul 13 17:01:07 <yates> e.g., open(0, tcsetattr(), read(), write()?
Jul 13 17:02:16 <yates> you don't have to mess with the device manager or other stuff?
Jul 13 17:03:38 <agmlego> If the port exists, it should act like any other serial device.
Jul 13 17:03:47 <agmlego> If not, then you have a DT thing, not a C thing.
Jul 13 17:05:53 <yates> ok, i'm still looking for the answer to my question. whether it's general or specific to the bbb.
Jul 13 17:06:16 <yates> is there a recommended howto to interface with a serial device?
Jul 13 17:06:59 <KaaK> yates, its a very open questions. There are many many kinds of serial devices, all with different ways to talk to them.
Jul 13 17:07:28 <KaaK> Your best starting place will be with any user manual/docs that came with the serial device.
Jul 13 17:07:51 <yates> i mean a standard rs-232 uart device, without hardware flow control, just tx/rx
Jul 13 17:08:27 <yates> KaaK: no cts/rts, no xon/xoff, etc. stadnard rate 9600 1N1
Jul 13 17:09:42 <yates> i have googled. there is a whole bunch of stuff, some of it outdated, some of it contradictory. i just thought the DIY gurus here would have a better clue than i for what is a probably a common task on this platform.
Jul 13 17:10:02 <KaaK> yates, You can use the command stty to set/get the serial parameters for a give device
Jul 13 17:10:57 <KaaK> yates, Your problem, is that the question you are asking, and the info you are providing are out-of-sync and very vague
Jul 13 17:11:41 <yates> bullshit
Jul 13 17:11:44 <KaaK> yates, can you be more specific? Device you are attempting to talk to; how you have tried; where you have failed; etc
Jul 13 17:12:13 <yates> sure, i can do that.
Jul 13 17:12:22 <KaaK> yates, Don't interpret me/us wrong. It just no one here is telepathic. No need for anger.
Jul 13 17:13:09 <yates> here's my code: http://ur1.ca/n43kj -> http://paste.fedoraproject.org/243898/68075811
Jul 13 17:13:31 <yates> this is under fedora 20, using a Keyspan USA-19HS usb/serial adapter
Jul 13 17:14:28 <yates> what's happening is that the data going FROM the PC TO the device gets into the low (mark?) state and hangs there when no data is being sent, and that is invalid for the rs-232
Jul 13 17:14:59 <yates> i'm under nda for the device, so i can't really tell you what it is.
Jul 13 17:15:55 <yates> my statement about the low/mark state is based on my observations using a scope
Jul 13 17:16:50 <yates> actually, the communication is successful, but only sporadically, say, once ever 10 times or so
Jul 13 17:17:14 <yates> it seems like something in the linux device driver or the keyspan device is getting hosed.
Jul 13 17:17:23 <yates> at least that's my guess.
Jul 13 17:17:58 <yates> ok, it's a tpms device. i guess my naming gave that away...
Jul 13 17:18:10 <agmlego> Well, I can honestly say at this point that a) you are not a clueless neophyte asking a simple question that can be Googled for and that b) I have no idea what the issue is.
Jul 13 17:18:23 <yates> lol!
Jul 13 17:18:29 <yates> np with that!
Jul 13 17:18:50 <KaaK> yates, It certainly could be driver/device related -- its good to keep an open mind though, 9/10 its usually the program (by my own person experience)
Jul 13 17:18:57 <agmlego> THose two things could not have been verified with your initial question; this is why we literally have a link on asking questions the smart way in the channel topic.
Jul 13 17:20:04 <myself> yates: Just to double-confirm a silly assumption, that you're plugging the USB side of the Keyspan into the Beaglebone, and the RS232 side goes into the mystery-device, right? (I'm trying to make sure you're not trying to work RS232 voltages with the 'bone IO pins)
Jul 13 17:20:04 <yates> KaaK: which is why asked for a howto (hopefully with example code). actually this IS from an example, one that seemed pretty competent.
Jul 13 17:21:05 <yates> myself: no.
Jul 13 17:21:27 <yates> the keyspan device is a dongle: usb on one end, and rs-232 on the other.
Jul 13 17:22:00 <yates> so the keyspace rs-232 goes to my mystery device. there is no beaglebone involved, though eventually that is where this code must run.
Jul 13 17:22:12 <yates> i'm just doing it under a standard linux box to get it going (hopefully).
Jul 13 17:22:24 <KaaK> yates, you might concider a loopback on your rs-232 to help test in isolation
Jul 13 17:22:25 <yates> s/keyspace/keyspan/
Jul 13 17:22:36 <yates> that's a pretty goo didea.
Jul 13 17:22:56 <myself> It's entirely possible that the Keyspan dongle is just bad, there are some amazingly horrible counterfeits and some pretty reprehensible actual products out there. Try a few different USB-serial dongles, with as many different chipsets as you can lay hands on. We had months of trouble with a PCB mill, simple thing, should just eat HPGL, until we tried a different dongle and suddenly everything Just Worked
Jul 13 17:23:02 <myself> (tm).
Jul 13 17:23:52 <yates> myself: when you plug in the keyspan, you get a /dev/ttyUSB0 device, which looks just like tty (or so i think)
Jul 13 17:24:02 <myself> My present "old trusty" is a Gearmo: http://smile.amazon.com/dp/B00AHYJWWG/
Jul 13 17:24:06 <yates> myself: definitely a possibility
Jul 13 17:24:31 <yates> good
Jul 13 17:24:40 <yates> i was looking around to buy another this morning - thanks
Jul 13 17:26:03 <agmlego> Yeah, anything (legitimate) FTDI or Cypress ought to work jsut fine.
Jul 13 17:27:33 <KaaK> that is what I've also found -- on the shit side of things is probably anything with a 'prolific' chipset
Jul 13 17:28:09 <agmlego> They had a major issue with counterfeits.
Jul 13 17:28:12 <agmlego> *have
Jul 13 17:28:21 <agmlego> Actual Prolific chipsets are pretty solid.
Jul 13 17:28:24 <myself> Prolific is terrible and ubiquitous, cause of innumerable bluescreens (but hey, the hours were billable; I recommended better hardware), and the counterfeit FTDIs are everywhere.
Jul 13 17:28:35 <myself> Perhaps the one they supplied was counterfeit. Heh.
Jul 13 17:28:38 <agmlego> Unfortunately, from experience, legit chipsets are like 2% of the market.
Jul 13 17:28:55 <myself> The Gearmo I linked above is genuine, 's why I linked it.
Jul 13 17:30:13 <yates> myself: is the gearmo known to work under a modern linux kernel?
Jul 13 17:30:31 <myself> Yes, though not by me personally. It's an FTDI chipset, so yes.
Jul 13 17:32:05 <yates> sold!
Jul 13 17:36:08 <yates> thanks everyone.
Jul 13 17:37:38 <evanmeagher> i recently open-sourced some ansible goodies that my company has been using to provision beaglebone black devices
Jul 13 17:37:46 <evanmeagher> apologies for the shameless plug, but i figure it could be relevant to some folks here: https://evanmeagher.net/2015/07/introducing-armsible/
Jul 13 18:22:30 <Technicus> journalctl: command not found
Jul 13 18:22:35 <Technicus> Why is it not there?
Jul 13 20:28:33 <Technicus> How do I emulate a tristate gpio?
Jul 13 20:35:58 <_av500_> emulate?
Jul 13 20:36:56 <ds2> stick a tristate buffer in front
Jul 13 20:49:20 <Technicus> Tri state with sysfs, how do I set it up?
Jul 13 20:50:38 <ds2> stop screwing with sysfs
Jul 13 20:50:41 <ds2> write proper drivers.
Jul 13 20:52:12 <_av500_> Technicus: set the GPIO to input
Jul 13 20:52:16 <_av500_> thats the same as high Z
Jul 13 20:52:37 <ds2> strictly speaking, it is not the same
Jul 13 20:53:06 <_av500_> highest Z
Jul 13 21:25:37 <Technicus> Ok, thanks :)
**** ENDING LOGGING AT Tue Jul 14 02:59:58 2015