**** BEGIN LOGGING AT Mon Apr 06 02:59:58 2020
Apr 06 03:00:11 <KenUnix> Yes relay 2  gpio 7
Apr 06 03:00:25 <zmatt> anyway, zZ
Apr 06 03:01:42 <KenUnix> thanks. good night
**** ENDING LOGGING AT Mon Apr 06 05:10:20 2020

**** BEGIN LOGGING AT Mon Apr 06 05:12:21 2020
Apr 06 21:01:00 <Mike123> what is the proper python module to use with the beaglebone black for gpio?
Apr 06 21:02:13 <Mike2448> Does anyone happen to know what is the proper python module to use with the beaglebone black for gpio?
Apr 06 21:18:02 <GenTooMan> adafruit might be a good hint
Apr 06 21:19:34 <Mike2448> adafruit_BBIO doesn't seem to work with ubuntu
Apr 06 21:21:32 <Mike2448> I tried using it and I kept getting "...returned with NULL..." errors
Apr 06 21:23:57 <GenTooMan> is it installed?
Apr 06 21:32:01 <Mike2448> yes
Apr 06 21:32:06 <Mike2448> and updated
Apr 06 21:32:12 <Mike2448> using python 3
Apr 06 21:32:24 <Mike2448> python 3.6 (i know thats not 3.8)
Apr 06 21:34:59 <GenTooMan> ummm don't go for 3.8 just yet. 3.7 is very stable
Apr 06 21:35:47 <GenTooMan> IE it's what 3.6 was (stable) version of python 3. OK did you use python3 as the interpretor and is the environment correct?
Apr 06 21:36:33 <zmatt> Mike2448: ubuntu is not officially supported on the bbb anyway
Apr 06 21:37:06 <zmatt> and it's entirely possible stuff doesn't work right there
Apr 06 21:37:58 <GenTooMan> hmm I guess assuming things "are OK" might have been a bit too far huh?
Apr 06 21:45:27 <GenTooMan> zmatt so you suggest he install a debian image suitable for his use?
Apr 06 21:45:51 <zmatt> generally speaking using the latest official iot image is recommended
Apr 06 21:48:44 <GenTooMan> that does make sense, because of the limited space available on the other images, I've had to delete unused stuff each time I've updated the image.
Apr 06 22:09:18 <zmatt> Mike2448: not terribly efficient (and only marginally tested) but super simple gpio "library":  https://pastebin.com/EU77NQtN
Apr 06 22:10:15 <zmatt> (I shouldn't use assertion for validating arguments, but I was lazy)
Apr 06 22:27:51 <set_> It is the 6th! New image time or has things been pushed back?
Apr 06 22:28:58 <set_> I understand, things get so quirky w/ releases, that people are rarely on time these days w/ projections. I will stay patient.
Apr 06 22:30:21 <set_> I want to try to join the learning ideas from Jason too. I think he has a new year resolution to teach some people some stuff.
Apr 06 22:30:23 <set_> Neat!
Apr 06 22:30:29 <zmatt> set_: https://groups.google.com/d/msg/beagleboard/8mIOwz9zDfc/QmEtc_fIBQAJ
Apr 06 22:30:38 <set_> Okay. brb. off to read.
Apr 06 22:32:36 <set_> So, Aug. this year now? That is okay. I see where I should report bugs back to github.com. Oops. I should have been trying older source to test things. Sheesh.
Apr 06 22:33:01 <set_> @zmatt: Thank you.
Apr 06 22:33:17 <set_> I saw the elinux page reference too.
Apr 06 22:33:28 <set_> I will go and check out a fresh image to test.
Apr 06 22:41:26 <set_> https://elinux.org/Beagleboard:Latest-images-testing is for testing thus far and bbb.io/latest-images will be for the "official released" images?
Apr 06 22:42:47 <set_> @zmatt: I was premature. The email just arrived w/ the link you supplied.
Apr 06 22:51:47 <set_> Console image on its way!
Apr 06 22:52:24 <GenTooMan> Well they provided the most commonly used image (or needed).
Apr 06 22:52:37 <set_> Right. I think that is smart.
Apr 06 22:52:47 <set_> People can set up their own GUI later.
Apr 06 22:53:23 <set_> Instead of wasting time on what we can do, console and IoT w/ the GUI was a smart path.
Apr 06 22:53:38 <set_> w/ = w/out.
Apr 06 22:53:40 <set_> Sorry.
Apr 06 22:55:22 <set_> GenTooMan: My old bot broke! I tried to make it work. It is either the Chrome OS or lack of permissions on that Chrome OS.
Apr 06 22:55:37 <set_> Well, now I have a reason to start from scratch.
Apr 06 23:10:43 <set_> It workeths!
Apr 06 23:10:50 <set_> Fast too!@
Apr 06 23:19:37 <GenTooMan> well that's the chromiest thing to happen.
Apr 06 23:20:54 <set_> Yep. I am going to install debian on it most likely. 16GB only, though.
Apr 06 23:21:50 <GenTooMan> you are using an BBAI?
Apr 06 23:25:45 <set_> Not right now. I am testing on the BBB.
Apr 06 23:25:51 <set_> w/ the BBB image.
Apr 06 23:25:53 <set_> Console.
Apr 06 23:26:12 <set_> Oh, no.
Apr 06 23:26:31 <set_> GenTooMan: I have this chromebook I was going to turn into a linux machine.
Apr 06 23:31:20 <set_> I think b/c of the issue w/ Chrome OS, I cannot help my bot turn and move. I read over tons of articles last night on it.
Apr 06 23:31:48 <set_> It seems there is an issue w/ Chrome OS and providing one's own allowed sites to visit, i.e. server or whatever.
Apr 06 23:31:56 <set_> Here nor there.
Apr 06 23:32:43 <set_> Anyway, it intefered w/ my BBGW usage w/ a server.
Apr 06 23:40:40 <GenTooMan> interfered even
Apr 06 23:40:47 <GenTooMan> that would sucatash.
Apr 06 23:43:17 <set_> My server came up and then could not be reached. The Chrome OS kept telling me that I have not Internet.
Apr 06 23:43:45 <set_> not = no
Apr 06 23:43:48 <set_> Odd days.
Apr 06 23:46:37 * GenTooMan holds a RJ45 cable end and asks "Does it need to be connected to the router?"
Apr 06 23:49:01 <set_> Hmm. The WiFi is up and running, no RJ45 ability.
Apr 06 23:49:11 <set_> It has no RJ45 on it.
Apr 06 23:58:14 <GenTooMan> the chrom OS toy or the BBAI?
Apr 06 23:58:32 <set_> Chrome OS thingy. The BBAI has one on it!
Apr 07 00:03:52 <set_> The BBGW has an older image on it but I am blaming the OS onboard the Chromebook. Anyway, I am setting up a linux distro on it soon. So, we shall see!
Apr 07 00:22:21 <GenTooMan> I don't use WiFi because it's very easy to sniff data from even with WEP protocol.
Apr 07 00:23:33 <set_> Oh. Okay. Nice but boo! I am on my own. Stay healthy, Cin-Cin.
Apr 07 00:32:49 <GenTooMan> You do seem to be on your own. Then again I have a pile of neighbors and an idiot ISP that offers WiFi access to there connection (really... hows that work well). LTE here isn't too bad my phone seems to get reasonable reception and not garbled up but it's a newer model than my old phone so no surprise.
Apr 07 00:38:54 <set_> Oh.
Apr 07 00:39:35 <set_> ISP, schmISP. I have it done on my end too.
Apr 07 00:39:52 <set_> I can see all my neighbor's WiFi signal names.
Apr 07 00:47:12 <bs1phc> Hi everyone
Apr 07 00:51:24 <bs1phc> How can i put the beaglebone back to default
Apr 07 00:52:27 <set_> Hello...Get the normal image on bbb.io/latest-images might be of some help if you are having current issues.
Apr 07 00:52:57 <zmatt> bs1phc: reflash it
Apr 07 00:53:26 <bs1phc> with balenaethcer right
Apr 07 00:54:26 <zmatt> etcher is a tool to flash an image to sd card (the 2019-08-03 IoT image is recommended, although a new image has been released today but it's not yet at https://beagleboard.org/latest-images it seems)
Apr 07 00:55:09 <zmatt> if you boot from that and uncomment the last line of /boot/uEnv.txt (cmdline=init=...something with eMMC flasher..) and reboot then it'll reflash your eMMC
Apr 07 00:55:11 <bs1phc> so should i just press the reset buton
Apr 07 00:55:43 <bs1phc> basically want i want to do is to run kali i have a 16gb sd card should be enough
Apr 07 00:55:59 <zmatt> the reset button?  that just force-reboots the system (like power cycling)
Apr 07 00:56:20 <zmatt> you just said you wanted it back at default, but now you instead want to run some obscure distro?
Apr 07 00:56:20 <GenTooMan> You want to run kali from the SD card?
Apr 07 00:57:36 <bs1phc> well i want to try some tools on the beaglebone like decrypters and other stuff while im doing other stuff on the computer and see how it reacts
Apr 07 00:57:39 <zmatt> if you want to boot from an sd card that has a wildly different bootloader from the one on eMMC you probably need to power on with the S2 button held down (the one closest to the card slot), you can (and should) let go of it once the power led turns on
Apr 07 00:58:01 <zmatt> "decrypters" ?
Apr 07 00:58:23 <bs1phc> y
Apr 07 00:58:33 <bs1phc> bruteforce and other stuff
Apr 07 00:58:37 <bs1phc> just play with it a bit
Apr 07 00:58:49 <zmatt> on a beaglebone with its cortex-a8 cpu?  lol
Apr 07 00:59:08 <bs1phc> are smalling things
Apr 07 00:59:19 <zmatt> anyway, what does this have to do with the distro? why not just run debian?
Apr 07 00:59:33 <bs1phc> okey nothing at all i guess
Apr 07 00:59:44 <bs1phc> was just an example
Apr 07 00:59:49 <bs1phc> debian is fine aswell
Apr 07 00:59:57 <bs1phc> just give me some help cause right now
Apr 07 01:00:21 <bs1phc> when i tried to boot it the explorer opens and is looking for a disk so im kind confused
Apr 07 01:00:21 <GenTooMan> what are you stuck on?
Apr 07 01:00:34 <zmatt> bs1phc: you can ignore the drive that appears
Apr 07 01:00:53 <zmatt> but if the beaglebone is running firmware of unknown age you may want to reflash it anyway
Apr 07 01:01:30 <bs1phc> well right now when i connect it the explorer opens and nothing happens
Apr 07 01:01:51 <bs1phc> like i cant open the beaglebone folders anything
Apr 07 01:02:01 <zmatt> if you're just going to use it as a generic debian system rather than use beaglebone-specific functionality I'd recommend the debian 10 (buster) console image from https://elinux.org/Beagleboard:Latest-images-testing since the IoT image would just be superfluous bloat
Apr 07 01:02:06 <zmatt> what do you mean?
Apr 07 01:02:44 <zmatt> the drive that shows up when connected via usb is just a tiny disk image containing some stuff to get started... I don't really get its point either
Apr 07 01:02:49 <bs1phc> do you guys have discord so i can send u a pic
Apr 07 01:03:00 <zmatt> no
Apr 07 01:03:29 <zmatt> but like I just said, you can ignore the disk image that shows up when you connect it via usb
Apr 07 01:03:58 <zmatt> also like I said, if the beaglebone contains firmware of unknown age, I strongly suggest reflashing it as step 1
Apr 07 01:03:59 <bs1phc> i tried to write to it using the debian one and the win32disk imager and after that i cant do nothing with it
Apr 07 01:04:09 <zmatt> write to what?
Apr 07 01:04:52 <zmatt> "the debian one" ??
Apr 07 01:04:56 <bs1phc> y
Apr 07 01:04:56 <zmatt> you're being really vague
Apr 07 01:06:01 <GenTooMan> are any of the user LED's flashing while it's on?
Apr 07 01:06:14 <bs1phc> yyup
Apr 07 01:06:17 <bs1phc> d2
Apr 07 01:06:18 <zmatt> GenTooMan: if it shows up as a usb device it is obviously running
Apr 07 01:07:10 <bs1phc> when i connect it the a new file explorer windows opens and it starts looking for a disk
Apr 07 01:07:29 <zmatt> what do you mean by "starts looking for a disk"
Apr 07 01:07:31 <bs1phc> it says insert a disc into usb drive E
Apr 07 01:07:36 <zmatt> uhhhhh
Apr 07 01:08:15 <zmatt> sorry I have no idea, that sounds really bizarre
Apr 07 01:08:44 <bs1phc> well i installed the drivers from the website
Apr 07 01:08:53 <zmatt> no drivers should be installed
Apr 07 01:08:55 <zmatt> none are needed
Apr 07 01:09:00 <bs1phc> well
Apr 07 01:09:01 <zmatt> at least on windows 10
Apr 07 01:09:06 <bs1phc> nope
Apr 07 01:09:08 <zmatt> (and mac, and linux)
Apr 07 01:09:22 <zmatt> I think drivers might be needed for ancient windows versions but I'm not sure
Apr 07 01:09:24 <bs1phc> well everyone in my class installed them
Apr 07 01:09:39 <GenTooMan> zmatt can he ping 192.168.7.2 with just the USB plugged in?
Apr 07 01:09:41 <zmatt> bad idea, whatever you installed isn't needed
Apr 07 01:10:05 <zmatt> but also, unless you have a very good reason not to (i.e. need to preserve its current contents), please just reflash it first
Apr 07 01:10:09 <bs1phc> okey so then i used the win32disk and write the debian iso to it
Apr 07 01:10:14 <zmatt> to what?
Apr 07 01:10:41 <bs1phc> beagleboneblack the device it appeared
Apr 07 01:10:51 <zmatt> 03:03 <@zmatt> but like I just said, you can ignore the disk image that shows up when you connect it via usb
Apr 07 01:11:02 <zmatt> 03:02 <@zmatt> the drive that shows up when connected via usb is just a tiny disk image containing some stuff to get started
Apr 07 01:11:25 <bs1phc> y i donwloaded the iso from the website
Apr 07 01:11:39 <zmatt> which?
Apr 07 01:12:24 <bs1phc> the first debian that appears
Apr 07 01:12:48 <zmatt> like I said earlier (and I'm starting to get _really_ tired of having to repeat myself), if you're just going to use it as a generic linux system (as it sounded like you were) rather than use beaglebone-specific functionality I'd recommend the debian 10 (buster) console image from https://elinux.org/Beagleboard:Latest-images-testing
Apr 07 01:13:11 <zmatt> but regardless of what image you intend to use, grab an "eMMC flasher" for "AM335x based BeagleBone's and PocketBeagle"
Apr 07 01:13:26 <zmatt> flash that to sd card and boot the beaglebone from it
Apr 07 01:13:38 <zmatt> (using Etcher to flash the sd card)
Apr 07 01:13:47 <zmatt> it should then proceed to reflash the eMMC
Apr 07 01:14:01 <bs1phc> okey ill try it
Apr 07 01:15:11 <KenUnix> bs1phc - Listen to zmatt. He knows...8) 8)
Apr 07 01:15:21 <set_> Go-go gadget-BBB!
Apr 07 01:15:33 <set_> KenUnix: I set up a "start" to a journey!
Apr 07 01:15:37 <set_> Look on google groups.
Apr 07 01:15:45 <set_> I am working on it now.
Apr 07 01:16:10 <KenUnix> yea! what's that?X-P X-P
Apr 07 01:16:53 <set_> Oh. A book from someone has a GPIO script in it. This script sets up usage in .c files for GPIO use. It can be applied to the RelayCape.
Apr 07 01:17:35 <KenUnix> Oooh where is it ?=D =D
Apr 07 01:17:50 <set_> What? The book or the GPIO driver?
Apr 07 01:18:54 <KenUnix> set_ my header spacers came in so I have the relay cape mounted and can still access Jtag serial port. All I need now is some 'c'.
Apr 07 01:19:05 <set_> Okay.
Apr 07 01:19:25 <set_> Please hold. Let me get the header file. It may take a while b/c I have to look around in the book again.
Apr 07 01:19:44 <set_> Then, from that header file, we can promote a .c file to compile for use w/ the Cape.
Apr 07 01:20:18 <set_> http://exploringbeaglebone.com/
Apr 07 01:20:52 <set_> Get the source by cloning it w/ git. The source is further down the page on the right side.
Apr 07 01:21:01 <zmatt> controlling gpios in C is trivial: https://pastebin.com/JwK4rDpj
Apr 07 01:21:42 <set_> Okay.
Apr 07 01:21:46 <set_> I thought this would be fun.
Apr 07 01:21:49 <GenTooMan> actually I should use C instead of python for testing the SPI port now that I think about it.
Apr 07 01:21:50 <set_> Dang.
Apr 07 01:21:57 <set_> Ha!
Apr 07 01:22:00 <KenUnix> zmatt, now at boot after mounting relay cape some weird messages are displayed.   https://paste.debian.net/1138811/
Apr 07 01:22:52 <zmatt> KenUnix: looks like your relay cape contains garbage in its eeprom
Apr 07 01:23:33 <zmatt> thus cape autodetection fails
Apr 07 01:23:49 <zmatt> this would be considered a manufacturing defect
Apr 07 01:25:55 <zmatt> I'd suggest dumping its eeprom to verify that it's indeed garbage (as opposed to something weird going wrong in u-boot) and once confirmed, contact the manufacturer
Apr 07 01:26:23 <KenUnix> zmatt, lots of errors  https://paste.debian.net/1138813/
Apr 07 01:26:44 <zmatt> why are you compiling c code with a C++ compiler?
Apr 07 01:26:46 <bs1phc> god finally some stupid reason i deleted the partition of the beagle bone
Apr 07 01:26:49 <zmatt> and yeah I forgot #include <stdio.h>
Apr 07 01:26:58 <zmatt> bs1phc: ?
Apr 07 01:27:14 <zmatt> KenUnix: oh and I'm missing #include <stdlib.h>
Apr 07 01:27:32 <zmatt> (for exit())
Apr 07 01:29:25 <set_> I am going to test it and I will see what happens.
Apr 07 01:29:33 <set_> Be prepared.
Apr 07 01:29:43 * GenTooMan waits for someones head to go boom?
Apr 07 01:29:55 <set_> Who's head? Mine!
Apr 07 01:29:59 <zmatt> KenUnix: for dumping the eeprom you can use something like   hexdump -C /sys/bus/nvmem/devices/2-00540/nvmem | head
Apr 07 01:30:25 <zmatt> (I hope I guessed the path right, otherwise try /sys/bus/nvmem/devices/*54*/nvmem )
Apr 07 01:32:38 <KenUnix> Am getting  open: No such file or directory
Apr 07 01:34:01 <zmatt> the second one doesn't hit anything either?
Apr 07 01:34:04 <set_> https://pastebin.com/HTfGH1KM is my first issue w/ the source, @zmatt. What would be another step? While you are helping KenUnix, I will be patient.
Apr 07 01:34:22 <zmatt> set_: I literally just answered the same question from KenUnix
Apr 07 01:34:30 <KenUnix> zmatt - heres the dump https://paste.debian.net/1138816/
Apr 07 01:35:31 <zmatt> KenUnix: that seems fine, then apologies for assuming it was a problem with the cape, it actually appear a problem with u-boot overlays
Apr 07 01:35:54 <zmatt> I guess report it to rcn
Apr 07 01:36:08 <KenUnix> If i'm not mistaken they are disabled
Apr 07 01:36:21 <zmatt> ?
Apr 07 01:36:40 <KenUnix> Where do i check if it is enable?
Apr 07 01:37:05 <zmatt> what is?  your log clearly shows u-boot overlays is enabled, why wouldn't it be?
Apr 07 01:38:03 <KenUnix> I dunno. This is new to me  . Oh I had to add #include <stdlib.h> to get it to compile
Apr 07 01:38:12 <zmatt> 03:27 <@zmatt> KenUnix: oh and I'm missing #include <stdlib.h>
Apr 07 01:38:21 <zmatt> KenUnix: reading helps
Apr 07 01:41:00 <KenUnix> OK. ./a.out results in  open: No such file or directory
Apr 07 01:41:11 <set_> It works.
Apr 07 01:41:12 <set_> !
Apr 07 01:41:19 <set_> How do I turn this relay off now?
Apr 07 01:41:24 <set_> Ha.
Apr 07 01:41:31 <zmatt> set_: change '1' to '0'
Apr 07 01:41:37 <set_> oh.
Apr 07 01:41:38 <set_> Ha.
Apr 07 01:42:25 <zmatt> KenUnix: without the relay cape's overlay I would have expected it to not work, but "no such file or directory" suggests you don't even have cape-universal enabled?
Apr 07 01:42:46 <set_> That is so nice.
Apr 07 01:42:50 <set_> On/Off.
Apr 07 01:42:59 <zmatt> hmm, your log claims it should be enabled though
Apr 07 01:43:20 <set_> Well, I should read more on Python, C/C++, and nodejs. Time to have some fun.
Apr 07 01:44:43 <KenUnix> uEnv.txt  enable_uboot_cape_universal=1
Apr 07 01:45:53 <zmatt> *shrug* something is borked on your system I guess, dunno what.  apparently it works for set_
Apr 07 01:46:12 <zmatt> but I'm kinda done with support for today
Apr 07 01:46:22 <set_> No!
Apr 07 01:46:31 <set_> https://pastebin.com/sFkfeavE
Apr 07 01:46:34 <set_> Look once and enjoy!
Apr 07 01:47:01 <set_> KenUnix: You need std.io.h.
Apr 07 01:47:03 <set_> sorry.
Apr 07 01:47:05 <set_> stdio.h.
Apr 07 01:47:35 <set_> That paste is from a simple nodejs file run w/ node.
Apr 07 01:48:46 <KenUnix> set_ on your BBB whats enabled in /boot/uEnv.txt ?
Apr 07 01:49:36 <set_> Oh. let me see.
Apr 07 01:49:38 <set_> Please hold.
Apr 07 01:50:17 <set_> Oh and KenUnix: I just grabbed the latest IoT image from this site: https://elinux.org/Beagleboard:Latest-images-testing.
Apr 07 01:50:38 <set_> So, things are updated and faster w/ "newness." Ha. Please hold. I will get the info.
Apr 07 01:52:24 <GenTooMan> set_ C/C++ is not as easy to start with as Python but in the end is more versatile to use in terms of resources.
Apr 07 01:52:28 <set_> https://pastebin.com/iFRYi99t <<< KenUnix: There.
Apr 07 01:52:38 <set_> That is my uEnv.txt file from the boot dir.
Apr 07 01:54:27 <set_> GenTooMan: Got it. I study all at times but only really get into it if I want to have projects for me.
Apr 07 01:54:40 <set_> I know it sounds silly but I need stuff to do too!
Apr 07 01:55:12 <set_> Luckily, that maker faire thing showed up. I would be bored out of my mind.
Apr 07 01:57:59 <KenUnix> Mine has  cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
Apr 07 01:59:42 <set_> That is the eMMC booting.
Apr 07 02:00:17 <set_> @zmatt taught me something a while back.
Apr 07 02:00:26 <set_> It was to put the emmc back to sd card mode.
Apr 07 02:00:39 <set_> Do you have a sd card?
Apr 07 02:00:48 <set_> Oh and I have an updated image.
Apr 07 02:01:10 <set_> That and it is a fresh install and not the older image, i.e. in case you missed me typing that up.
Apr 07 02:01:35 <set_> Oh.
Apr 07 02:02:25 <GenTooMan> set_ you can do a lot with the robot starting with simple C although you may wish to make it multi threaded for handling PID control type things.
Apr 07 02:03:02 <set_> Yep. I learned about "case" a while back but have not implemented it.
Apr 07 02:03:09 <set_> KenUnix: Sorry. I was mistaken.
Apr 07 02:03:18 <set_> Mine is there too. I have that line too.
Apr 07 02:03:54 <KenUnix> Upload the 'c' code you used. thx
Apr 07 02:04:00 <set_> Okay. Please hold.
Apr 07 02:05:00 <KenUnix> Oh ya   case  don't forget to catch if notging matches
Apr 07 02:05:36 <set_> https://pastebin.com/ivwyBDwL w/ the #include <stdio.h> header like described earlier.
Apr 07 02:06:29 <set_> Your "char c = '1'" line is different than mine. I turned mine off.
Apr 07 02:07:33 <set_> So, your line will read: char c = '1' and mine reads char c = '0' b/c I turned the RelayCape relay1 off.
Apr 07 02:07:43 <KenUnix> open: No such file or directory
Apr 07 02:07:55 <set_> Hmm. Did you try the new headers?
Apr 07 02:08:04 <set_> Did you see all four headers?
Apr 07 02:11:07 <set_> So, gcc myfile.c -o myfile would be a good way to compile that .c file.
Apr 07 02:11:10 <set_> For starters.
Apr 07 02:12:12 <KenUnix> Do you have those pins exported?
Apr 07 02:12:47 <set_> I did nothing w/ exporting files or pins outside of add the RelayCape and w/ what code @zmatt gave to the room.
Apr 07 02:12:57 <set_> But...
Apr 07 02:13:16 <KenUnix> Stupid question. Relay cape U shape end faces barrel jack?
Apr 07 02:13:25 <set_> Yes.
Apr 07 02:14:05 <set_> When I got the RelayCape, get this, I put it on incorrectly. The two pins stuck out on it and i could not get it to work.
Apr 07 02:14:23 <set_> I then thought, dang BBB.io! But, I knew something was wrong on my end.
Apr 07 02:14:57 <set_> I looked over the source, 100 times. Then, under the cape was those pins bare w/out being joined to the board. Oops!
Apr 07 02:15:05 <KenUnix> Do a  ls -l /sys/class/gpio/gpio20
Apr 07 02:15:10 <set_> Okay. Please hold.
Apr 07 02:15:46 <set_> lrwxrwxrwx 1 root gpio
Apr 07 02:15:51 <set_> Is that the part you need?
Apr 07 02:17:02 <KenUnix> You don't see something like   lrwxrwxrwx 1 root gpio 0 Apr  6 19:44 /sys/class/gpio/gpio112 -> ../../devices/platform/ocp/481ae000.gpio/gpiochip3/gpio/gpio112
Apr 07 02:17:21 <set_> Yes.
Apr 07 02:17:30 <set_> I have that but for gpio/gpio20.
Apr 07 02:17:43 <KenUnix> On my box  gpio20 does not exist
Apr 07 02:18:01 <set_> Hmm. sudo dpkg-reconfigure tzdata and tell the truth.
Apr 07 02:18:21 <KenUnix> huh?
Apr 07 02:18:33 <set_> Type that command and be truthful.
Apr 07 02:18:42 <set_> To you and everyone that might snoop on you.
Apr 07 02:19:08 <set_> a prompt pops up for timing while plugged in.
Apr 07 02:19:18 <set_> timezone, time, etc.
Apr 07 02:21:24 <KenUnix> Time is already set to update
Apr 07 02:21:32 <set_> Okay.
Apr 07 02:21:40 <set_> I just updated my time, date, etc.
Apr 07 02:22:04 <set_> do you have config-pin capabilities?
Apr 07 02:22:13 <KenUnix> sudo timedatectl set-timezone America/New_York
Apr 07 02:22:30 <set_> sudo dpkg-reconfigure tzdata is better to me but have at it.
Apr 07 02:23:05 <KenUnix> I am getting weary of this nonsense.. =L =L
Apr 07 02:23:31 <set_> Well, I was going to get you to update and upgrade once you updated your timezone and date.
Apr 07 02:23:44 <set_> Sometimes things get odd b/c of those things.
Apr 07 02:23:44 <KenUnix> With wifi working that's the recommended plan
Apr 07 02:24:13 <set_> Oh.
Apr 07 02:24:32 <set_> Try Relay2.
Apr 07 02:24:37 <set_> Forget about RElay1.
Apr 07 02:25:05 <set_> My relay1 on node does not work for some reason.
Apr 07 02:25:11 <KenUnix> With wifi working and search to 8.8.8.8 it is automatic assuming wifi is your default gw
Apr 07 02:25:21 <set_> Okay.
Apr 07 02:25:38 <set_> Try all relays before you give up.
Apr 07 02:25:50 <set_> It might be a small bug in the dts file.
Apr 07 02:26:02 <set_> I read over some bugs so far in the new kernel/images.
Apr 07 02:29:12 <KenUnix> I have relay 1,2,3 and 4 all no go
Apr 07 02:29:26 <set_> Let me try something.
Apr 07 02:29:29 <set_> Please hold.
Apr 07 02:30:09 <set_> Line 14 reads what on your end?
Apr 07 02:30:24 <set_> char c = '1';
Apr 07 02:30:37 <KenUnix> '1'
Apr 07 02:30:42 <set_> Okay.
Apr 07 02:30:43 <set_> Hmm.
Apr 07 02:30:50 <set_> Did you update your image yet?
Apr 07 02:30:54 <KenUnix> 1 = operate 0 = release
Apr 07 02:30:57 <set_> Okay.
Apr 07 02:31:45 <KenUnix> my image is  BeagleBoard.org Debian IoT Image 2020-03-26
Apr 07 02:32:17 <MattB0ne> Hello everybody
Apr 07 02:32:23 <set_> The bbb.io peoples came out w/ a new image today.
Apr 07 02:32:28 <set_> Get that one.
Apr 07 02:32:37 <MattB0ne> Ken how did you like that image
Apr 07 02:32:47 <KenUnix> Off to the trash X) X)
Apr 07 02:32:53 <MattB0ne> that is the release candidate
Apr 07 02:33:04 <MattB0ne> ?
Apr 07 02:33:09 <set_> Look here: https://elinux.org/Beagleboard:Latest-images-testing
Apr 07 02:33:15 <KenUnix> I think it works well. vnc works better firefox works
Apr 07 02:33:49 <KenUnix> However  bone101 is gone EOL
Apr 07 02:34:02 <MattB0ne> hmm
Apr 07 02:34:07 <KenUnix> Cloud-9 and node-red OK
Apr 07 02:34:10 <MattB0ne> i think I am going to stay put
Apr 07 02:34:12 <MattB0ne> with what I got
Apr 07 02:34:17 <MattB0ne> for a bit
Apr 07 02:34:39 <KenUnix> EOL End Of Life per RCN
Apr 07 02:35:42 <KenUnix> image now includes firefox and chromium
Apr 07 02:36:38 <KenUnix> install lxterminal and mate-terminal both accessable from vnc session
Apr 07 02:37:55 <KenUnix> tuning vnc makes it much faster on both server and client
Apr 07 02:39:07 <KenUnix> vncserver -depth 24 -geometry 1280x600 -name "Kens-BBB" :1
Apr 07 02:41:39 <KenUnix> Got screen size to work correctly in xshell6 by adding   stty rows 19 columns 85 in login script
Apr 07 02:44:14 <KenUnix> My release is one less then bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz
Apr 07 02:44:48 <KenUnix> Any body here?
Apr 07 02:44:53 <set_> Hey.
Apr 07 02:45:18 <KenUnix> Did you see all my nots above?
Apr 07 02:45:32 <set_> Yep.
Apr 07 02:45:42 <set_> Did you get the new image yet?
Apr 07 02:45:55 <set_> The pinmux is messed up on specific languages.
Apr 07 02:46:02 <set_> I cannot figure it out just yet.
Apr 07 02:46:12 <KenUnix> Not now. Mine is only a couple of weeeks old
Apr 07 02:46:13 <set_> nodejs and node each result w/ something different.
Apr 07 02:46:34 <set_> Okay. Good luck for now. I need to break for a bit.
Apr 07 02:47:29 <KenUnix> In the future I think 'c' is the better solution
Apr 07 02:48:46 <KenUnix> 'c' started unix. python, perl, bison all came later
Apr 07 02:50:58 <MattB0ne> has anyone communicated with BBB through regular usb
Apr 07 02:51:08 <MattB0ne> as opposed to the micro
Apr 07 02:52:58 <KenUnix> Where does %m come from  fprintf( stderr, "open: %m\n" );
Apr 07 02:53:21 <KenUnix> in what way?
Apr 07 02:54:03 <KenUnix> mattbone - in what way?
Apr 07 02:54:56 <KenUnix> Hello?
Apr 07 02:55:01 <MattB0ne> like ssh
Apr 07 02:55:08 <KenUnix> yes
Apr 07 02:55:11 <MattB0ne> i need to use the micro port for power
Apr 07 02:55:16 <MattB0ne> do you have to do anything different
Apr 07 02:55:31 <MattB0ne> or those the board automatically handle everything
Apr 07 02:56:22 <KenUnix> I have micro usb to pc. When BBB powered up new COM# ports should show up in devices
Apr 07 02:57:04 <MattB0ne> right but i will have micro to wall outlet and usb to usb on my computer
Apr 07 02:57:07 <MattB0ne> will itstill work
Apr 07 02:57:14 <KenUnix> And you should hear a tone
Apr 07 02:58:13 <KenUnix> usb type A port is for devices. micro port is for BBB to pc
Apr 07 02:59:33 <KenUnix> type A large port is for things like usb hub sd-card readers and the like
**** ENDING LOGGING AT Tue Apr 07 02:59:57 2020