**** BEGIN LOGGING AT Mon Oct 15 03:00:01 2018 Oct 15 07:31:59 hi..? Oct 15 07:32:42 what do the sgx modules offer? Do I have to have them installed? Oct 15 07:34:45 zmatt: is that matlab Oct 15 07:42:56 umbaman: they are binary blobs, graphics drivers. Oct 15 08:06:44 yes I know, but should I install them or not and why? Oct 15 08:07:34 some packages will require them Oct 15 08:07:39 some will make them optional Oct 15 08:07:54 if you have some kind of graphics, you should install them Oct 15 08:12:05 is there an api reference for those somewhere? Is it just opengl es? Oct 15 08:28:39 and drm, I guess. Oct 15 09:28:20 I am developing with qt, I guess sgx will be more descent that linuxfb Oct 15 10:05:36 gles1, gles2, egl Oct 15 10:06:24 no package *requires* the sgx drivers. you're perfectly free to use mesa's software renderer instead :) Oct 15 10:06:37 in fact, unless you put in effort, that's exactly what you'll get Oct 15 10:38:55 any tutorials on using it? Oct 15 10:39:01 actually forget it Oct 15 10:39:10 linux graphics, mesa, wayland, x, all this crap ugh Oct 15 10:39:17 thats why i went straight to framebuffer Oct 15 10:39:27 DRM for eff's sake Oct 15 12:43:23 well right now you're not using drm but legacy fbdev :P Oct 15 12:44:03 I did some work on an object-oriented drm wrapper, but haven't had time yet to get it into a githubbable state Oct 15 12:45:17 yeah exactly Oct 15 12:45:28 i mean i think drm is rather complex Oct 15 12:45:35 not that its an excuse but Oct 15 12:46:07 it actually isn't, but it does look a bit intimidating. especially if you look at the header file and have to wade through all the irrelevant legacy shit Oct 15 12:47:17 so what exactly is the architecture tree looking like? drm replaces fbdev? wayland replaces x? is any of this related Oct 15 12:47:37 yep and yep Oct 15 12:47:55 drm has pretty much already replaced fbdev Oct 15 12:48:12 and there's a kis wayland drm based and x fbdev based or is it unrelated- both x and wayland now use drm Oct 15 12:48:17 fbdev just sticks around for the console and legacy clients Oct 15 12:48:24 i see Oct 15 12:48:48 so DRM is an interface to GPUs and Mesa is too, but a userspace/higher layer component of the system Oct 15 12:49:40 ugh i have another tab to read i guess Oct 15 12:49:42 fml Oct 15 12:50:02 mesa is an mainly implementation of opengl Oct 15 12:50:54 i.e. to go from userspace apis like the many flavors of opengl to either a software rendere or whatever low-level command stream the GPU you use requires Oct 15 12:51:13 at least that's my superficial understanding, I don't know much about mesa Oct 15 12:52:19 yeah Oct 15 12:52:28 i mean, it seems like DRM is also abstracting GPU hardware Oct 15 12:52:40 so mesa must interface with DRM somehow Oct 15 12:52:48 if it intends to use hardware rendering for opengl Oct 15 12:52:53 i wasn't sure what type of interface DRM presents Oct 15 12:53:03 but now there is KMS too and now i am looking at a graph chart with 100 nodes Oct 15 14:00:47 modesetting (kms) is part of the functionality of drm Oct 15 14:03:05 I'd say it's the main part of it, but that may be due to my perspective of having only used drm with simple modern non-gpu display drivers like tilcdc and omapdrm Oct 15 14:03:52 there the only functionality drm has is 1. buffer allocation 2. modesetting (atomic modesetting and nuclear pageflips) Oct 15 14:17:11 when dealing with actual GPUs the story is quite different I suspect, and afaik that's what drm was originally created for: giving userspace as much direct access to the gpu as safely possible (hence the name Direct Rendering Manager) Oct 15 15:11:58 i guess this is one of those cases tho where its like, Application --> GPU --> Application --> LCD Peripheral Oct 15 15:12:10 Most of the time its Application --> GPU --> Monitor right? Oct 15 15:20:55 search Oct 15 15:24:36 how you doin rd_ Oct 15 15:24:47 weren't you on here the other day wanting to use beaglebone blue in your factory automation? Oct 15 16:22:08 @ayjay_t Good Morning Oct 15 16:24:34 good morning rd_ Oct 15 16:31:25 Morning XD not in Connecticut. Finally going through this uxmux source :-P Oct 15 16:40:59 RD: I replaced the beginner's guide link. Oct 15 16:41:54 wish I knew how to make one of those cool web animations that highlighted the features of webchat.freenode.net Oct 15 16:46:19 removed the part to set the nick on https://beagleboard.org/chat and now made it random. Folks that know can always use /nick. Oct 15 16:46:55 just trying to lower the bar a bit.... Oct 15 16:47:11 I need to figure out how to add a link to the Slack #support channel. Oct 15 16:47:20 though it could be largely unpopulated. Oct 15 16:56:35 @ayjay_t good morning Oct 15 16:57:38 hey rd! Oct 15 16:57:51 hows it going man, getting used to the IRC community yet Oct 15 16:57:52 ? Oct 15 17:00:16 * ayjay_t is hanging Oct 15 17:00:46 @ayjay_t I am going to have to go with baby steps.....starting to feel a bit more welcoming but I am not wanting to interject driver questions in the middle of developer conversations. Oct 15 17:01:24 its not really like that Oct 15 17:01:28 you can dsay whatever you want Oct 15 17:01:45 its totally asynchronous in here, you're not injecting anything... Oct 15 17:02:21 have courage, rd! Oct 15 17:03:25 The instructions on the top of this page go to a link " read and watch this IRC survival guide." The link is dead by the way..... but it sounds like it was written for developers at a higher level. Oct 15 17:07:34 My biggest issue was that I am not familiar with this format of chat room. It is a bit more old school and I did not know how to .....still don't know how to see what people have been talking about just before I got on. Since I would join this chat room at hours early or late, no one was saying anything and I thought the community was pretty dead or had abandoned this chat room. Now that it is apparent that people use this chat room. Oct 15 17:10:28 yeah well i guess there is some getting used to Oct 15 17:10:34 people run their chat rooms however they want Oct 15 17:10:43 #gentoo for example is explicitly support and you'll get prodded to move elsewhere Oct 15 17:11:02 so there are usually several conversations going at once and liberal use of @'ing people to track conversation threads Oct 15 17:11:10 #avr is where engineering goes to die Oct 15 17:12:02 #beagle is pretty relaxed, but i think for something like #beagle you have a very wide range of beginner to super expert and the super experts usually still need support Oct 15 17:12:45 of course if we had 1000 users like in #electronics or ##linux there would need to be more rules Oct 15 17:13:26 for a long time it was just me not knowing how chips worked, and then for a while it's been set_ and his dotted monologues and play-by-plays trying to get an inductor to spin Oct 15 17:14:45 people CAN be rude on IRC tho and i think there is a bit of burnout/impatience Oct 15 17:15:03 but might does not make right Oct 15 17:15:11 Yeah Oct 15 17:17:20 I am reading "BeagleBone Robotics Projects" because it specifically supports BeagleBone Blue. The Beagboard.org support wiki for BeagleBone Blue has been blank for about 18 months and I have no idea what info from BeagleBone Black applies or dosen't apply. Oct 15 17:20:12 are you trying to accomplish something specific? are you familiar with linux in general? Oct 15 17:20:15 @ayjay_t I am a manufacturing engineer. I took Paskal about 20+ years ago but no other knowledge about programming. Oct 15 17:20:15 soo i'll take the answer to the second question as "no" Oct 15 17:20:15 I write instructions for a living. Oct 15 17:20:15 oh in paskal? Oct 15 17:20:16 I do not know Linux. Oct 15 17:20:16 thats cool Oct 15 17:20:16 you have a long way to go then, it's a great system but it is a lot Oct 15 17:20:30 is ther something specific you're trying to do? and did you say that you write instruction in paskal? how does that work? Oct 15 17:20:49 I do not write instructions for Paskal. I have built things like Mass Spectrometers and Semiconductor equipment and rock concert lighting. Oct 15 17:21:21 oh i guess i don't know what you mean by "write instructions" then Oct 15 17:21:44 work instructions for people assembling products on a production line. Oct 15 17:21:52 interesting Oct 15 17:22:02 i have a quality control startup Oct 15 17:22:07 Sorry......we are speaking different languages. Oct 15 17:22:16 hahaha no its fine no problem Oct 15 17:22:52 so whats your first goal? Oct 15 17:23:36 That has been part of the problem. People get upset and make assumptions and a Newb has no idea they asked a different question than what they intended. Oct 15 17:23:50 yeah rd i have bad news, it just happens on IRC Oct 15 17:23:56 there are some famously poor mannered people here Oct 15 17:25:26 Yeah. I understand. I can hold my own but it looked dead in the past so it was not worth the effort. Slack makes it a bit smoother to share photos.....(almost said images) Oct 15 17:25:49 yeah well, the problem with slack is it's resource usage Oct 15 17:26:11 but you can create external links from slack and then post them here too Oct 15 17:26:17 @ayjay_t I am wanting to build a robotic bird house building machine. Oct 15 17:26:25 oh boy Oct 15 17:26:28 thats the long goal Oct 15 17:26:49 that sounds like a job for a robotic arm. Oct 15 17:27:12 Long goal is lowering the barriers to entry for the bottom billions to manufacturing. Oct 15 17:28:37 no dude, that birdhouse is definitely a long goal Oct 15 17:28:37 @ayjay_t It is a job for several actuators, vision system, AI, Machine vision...... AR....... Oct 15 17:29:03 i was thinking more like "spin a motor. activate a pump" Oct 15 17:29:11 thats a lot of buzzzzz Oct 15 17:29:18 lots of buzzz rd Oct 15 17:29:30 I am going to do each piece of the puzzle manually and add automation as I go. Oct 15 17:29:40 Lot of buzzz? Oct 15 17:30:16 yeah those are buzzwords Oct 15 17:30:53 My short term goal is to find out if my Microsoft driver is working correctly or giving me a false error message. Oct 15 17:31:11 hahaha ethernet over usb for W10? Oct 15 17:31:39 its been a pain point for a long time, for some reason Oct 15 17:32:07 @ ayjay_t My wife just got home for lunch so I am going to be offline for a bit. Yeah. Windows 10 and USB. Oct 15 17:32:35 good luck Oct 15 18:09:25 uxmux makefile has a target that runs cmake and then runs make i'm gonna die Oct 15 18:56:50 @ayjay_t are you still online and listening? Oct 15 18:57:25 hmm? Oct 15 18:57:48 sometimes i'm here sometimes i adhd Oct 15 18:57:55 sometimes i go to a different channel and forget XD Oct 15 18:58:00 @ahjay_t LOL Oct 15 18:59:15 @ahjay_t does adding the "@" symbol in front of someones name create a noise or pop up? Oct 15 18:59:24 well everyone uses different clients Oct 15 18:59:43 in my client, and maybe in all IRC, all you have to do is type my name and at least in my case, it highlights the line Oct 15 18:59:54 just type "ayjay_t" Oct 15 19:01:05 rofl uxmux is huge Oct 15 19:01:07 and its a mess Oct 15 19:01:09 and its c++ Oct 15 19:02:18 with weechat, an overlay appears on screensaver when you mention somebody in IRC Oct 15 19:02:22 @ayjay_t Sorry. I had to refresh the page so I can not see what you typed previously. Oct 15 19:02:51 you use /nick NAME to set your name now rd Oct 15 19:02:59 if you're on windows, i really like Hexchat Oct 15 19:03:04 for a good IRC client Oct 15 19:03:13 and if you type my name w/o @, it'll highlight the line for me Oct 15 19:03:19 but i don't get a notification persay Oct 15 19:03:23 so its very relaxed Oct 15 19:03:54 sorry, my last sentense was a nonsense... Oct 15 19:04:08 i really dont know what to do about uxmux Oct 15 19:04:18 like i feel like i'm going to rewrite the entire thing Oct 15 19:05:21 @ayjay_t Sorry. The log in screen just shows the check box Capcha to show I am not a robot. Normally it shows a box to add my name. Oct 15 19:07:07 but i just said, use `/nick NAME` Oct 15 19:07:23 ping Oct 15 19:07:30 hey CoffeeBreakfast_ whatsup Oct 15 19:07:41 and qwebirc60199, you don't need @ Oct 15 19:07:57 qwebirc60199: you don't need @, you type `/nick NAME` to change your name to NAME Oct 15 19:08:02 good on ya ayjay_t Oct 15 19:09:17 RD: LOOK AT THAT Oct 15 19:09:19 FANCY Oct 15 19:09:37 you got caps and everything Oct 15 19:09:41 I am not sure if it allowed me. Oct 15 19:09:51 Well it did. Oct 15 19:10:29 other commands you might like: /me MESSAGE HERE, /whois NICK, /join CHANNEL, /names Oct 15 19:12:12 I just clicked on my name in the bar to the right and the "who is" and other options came up. Then it switched my name even though it initially said "RD" was registered and to pick another name. Oct 15 19:12:36 well the thing about that, RD Oct 15 19:12:45 is that the person who registered RD will have to kick you off if they want it back Oct 15 19:12:57 this is me IRL https://www.linkedin.com/in/rdchilders/ Oct 15 19:12:58 because otherwise IRC assumes that you're just the RD who registered it but not logged in Oct 15 19:13:08 OR that RD is never coming back and so you're RD now Oct 15 19:13:26 I am the one who logged in as RD yesterday and today. Oct 15 19:13:34 well i figured Oct 15 19:13:39 but IRC is a big network of chatrooms Oct 15 19:13:55 it's not just #beagle, it's also #kicad, ##electronics, ##C, #gentoo, #arch-linux, it goes on and on Oct 15 19:14:08 there are literally thousands of technical people on here, mostly helping each other with open source Oct 15 19:14:26 you can type /j ##electronics probably Oct 15 19:14:33 maybe /join ##electronics Oct 15 19:14:41 Yeah. I thought IRC would only restrict the name for this room. Oct 15 19:15:05 no its the whole network, there's a formal login mechnanism too to "claim" your name /msg NickServ username password Oct 15 19:15:21 i connected with you on linkedin Oct 15 19:15:28 i'm more active on twitter: twitter.com/misterpikul Oct 15 19:16:56 oh you worked for FLEX? big company. Oct 15 19:17:21 I did until they had a layoff back in the spring Oct 15 19:18:27 /shrug Oct 15 19:21:40 did you get into your beaglebone blue yet? Oct 15 19:22:53 Storrs Mansfield, Connecticut Birr Oct 15 19:23:10 No, I am stuck on page 14 of the book. Oct 15 19:23:27 yeah not a huge fan of central connecticut Oct 15 19:23:43 RD i honestly have no idea if the drivers for the beaglebone are fixed Oct 15 19:23:49 when they first set it up, it was fine, you installed it normally Oct 15 19:24:02 and then eventually ou had to jumpt through hoops to turn off driver signing, which was a pain in the butt Oct 15 19:24:19 now apparently they're getting fixed again, or there is some other work around? Oct 15 19:24:19 I was in shorts and sweating yesterday. This morning I am sweating. Thanks for the invite on LinkedIn by the way. Oct 15 19:25:25 So for a Newb......how are people supposed to know what is going on and distinguish it from their own mistakes? Oct 15 19:27:08 yeah no i mean, this particular pain point is pretty bad Oct 15 19:27:13 because this is the first thing the user gets to Oct 15 19:27:39 but most of the time, for advanced stuff, you just need to have the knack... have good support... etc Oct 15 19:28:04 understand how things wrok and move forward Oct 15 19:31:43 I have tried to "Get started" off and on for a few years. The last time I was at it, me and a friend spent a number of hours trying to set the clock on a BeagleBone Black. Then we stopped. Oct 15 19:32:17 yeah the rabbithole never really ends, sorry Oct 15 19:32:36 allt he people that use linux and work with me have spent at least one or two weeks locked in their rooms pulling their hair out Oct 15 19:33:24 weekends* Oct 15 19:33:29 And don't forget Murphy's law Oct 15 19:36:11 meh i'm gonna rewrite uxmux Oct 15 19:36:12 probably on twitch Oct 15 19:40:58 live streaming?? Oct 15 19:41:29 of course Oct 15 19:41:39 silly me Oct 15 19:41:45 yeh i guess Oct 15 19:41:48 how awful Oct 15 19:41:59 i'm going to subject everyone to my pain on twitch haha Oct 15 19:42:08 ayjay_t Thanks.....I gotta run. Oct 15 19:42:32 good luck RD Oct 15 19:42:50 /shrug Oct 15 19:43:52 what is your user on twitch? Oct 15 19:50:20 ceo_aj i thnk Oct 15 20:05:19 ayjay_t: well it used to Just Work(tm) for a while, then apparently microsoft did an update that broke things again, and now they should be fixed again (i.e. the beaglebone should work plug&play) Oct 15 20:08:10 This is what microsoft recommend Jason to do, after they re-wrote their driver: https://github.com/RobertCNelson/boot-scripts/commit/7eab749333e859001784569984b1f13992cb7d70 Oct 15 20:08:43 they=microsoft... if it wasn't clear.. Oct 15 20:10:14 oh it didn't have an os descriptor yet? I thought it already did Oct 15 20:11:25 the thread you link to in that comment is not a new issue though Oct 15 20:34:55 rcn-ee[m]: i don't really undersatnd how this sort of thing would ever work in production Oct 15 20:35:09 rcn-ee[m]: does msft expect every supplier to have remote update of devices? Oct 15 20:35:40 or is beagleboard supposed to maintain some sort of automatic driver update server Oct 15 20:36:00 since i'm guess bbb is unique in supplying its own driver from memory of msd Oct 15 20:36:15 i think we are suppost to spend $ and pay microsoft for that.. Oct 15 20:40:00 the crazy thing, we are using Microsoft's RNDIS driver, which they changed.. If only they just supported the usb-cdc class like Mac and Linux.. Oct 15 20:44:00 the crazy thing is that it's such a never-ending headache to convince Windows to use Microsoft's own driver for their own proprietary protocol Oct 15 20:51:50 makes you wonder, is there any "official Microsoft" device that utilizes RNDIS, that we could mirror... Oct 15 20:52:16 well we're also a composite device, which afaik is part of the problem Oct 15 20:52:59 true, and no good way to detect.. .hey windows is on this other end, reset usb bus and start over. ;) Oct 15 20:54:12 but I thought the issue was now fixed? Oct 15 21:16:43 should be, the october 2018 release worked for me, but i bet they'll break it again in 6 months.. Oct 15 21:27:15 I have a BBBW with a MikroBUS cape and clicks from uBlox Oct 15 21:27:46 I am desperately stuck trying to get the proper config in place to get the BBBW to "see" the clicks so that I can interact with them Oct 15 21:28:24 I would happily pay for someone who knows how to interact with these things to get on a screenshare with me and show me how to get this configured properly Oct 15 21:51:28 Anybody here? :) Oct 15 21:56:05 qwebirc10344: please wait.. eventually someone (who knows that topic) will answer Oct 15 21:58:36 Thank you. I don't mean to be impatient. I just really need some expertise. Oct 15 21:59:19 what are those things? Oct 15 22:00:04 zmatt: is that question directed to me? Oct 15 22:00:16 yep Oct 15 22:01:27 we have a MikroBUS cape on our Beaglebone. we have it so that we can plug in two "clicks" from MikroElectronica Oct 15 22:01:34 the 2 "clicks" are... Oct 15 22:01:59 the GNSS5 click for GPS Oct 15 22:02:00 and Oct 15 22:02:15 the 4G LTE click for LTE Oct 15 22:02:21 both are made by uBlox Oct 15 22:02:48 okay I see, so this cape is an adapter for those little "click" boards Oct 15 22:02:55 and, the BBBW has a built in chip for BLE and we need to interact with it as well. Oct 15 22:03:06 yes, the cape is an adapter. Oct 15 22:03:19 in other words the EEPROM of that cape is totally useless since it can't be used to actually identify the hardware connected Oct 15 22:03:28 hence no cape autodetection Oct 15 22:03:33 hence no plug&play Oct 15 22:03:53 https://www.mikroe.com/beaglebone-mikrobus-cape Oct 15 22:04:00 okay, let's see what we have in the overlays repo... I do remember seeing some "click" stuff Oct 15 22:04:50 useless is what we are feeling, but we are blaming ourselves for just not knowing the magic config combo to get it all talking to each other Oct 15 22:05:22 no, blame the guys who made this "cape" which isn't really a cape Oct 15 22:05:48 normally a cape can be automatically recognized by linux and the correct overlay will be loaded for it Oct 15 22:06:24 in this case you'll have to manually specify the overlays to be loaded for the specific click boards you connected Oct 15 22:06:43 that is assuming of course that the clicks you want to use already have an overlay Oct 15 22:07:33 if you check BB-mBC* in the overlays repo: https://github.com/RobertCNelson/bb.org-overlays/tree/master/src/arm Oct 15 22:07:50 you'll see a rather small number of overlays are provided Oct 15 22:08:22 is there hardware documentation for the clicks you want to use? Oct 15 22:08:33 well Oct 15 22:08:36 let me look Oct 15 22:08:45 There are spec sheets for sure Oct 15 22:09:18 lol, this is listed as the "mikroBUS Cape User Manual" on their site: https://download.mikroe.com/documents/add-on-boards/click-shields/mikrobus-cape/beagleboane-mikrobus-cape-manual-v100.pdf Oct 15 22:09:37 excellent manual, very clear instructions Oct 15 22:09:50 https://www.mikroe.com/gnss-5-click Oct 15 22:10:24 man, I hope that was sarcasm Oct 15 22:10:29 :P Oct 15 22:12:06 Would you be willing (for a nice fee, or Lakers tickets, or something else hard to get) to get on a screen share and help us out? Oct 15 22:13:04 I don't even like the Lakers. Not sure why I threw that in there. ;) Oct 15 22:13:09 not really, I prefer irc Oct 15 22:13:16 what was the other click? Oct 15 22:13:19 oh yeah, LTE Oct 15 22:13:22 oh sorry Oct 15 22:13:25 so probably the gnss one is simpler Oct 15 22:14:10 https://www.mikroe.com/4g-lte-na-click Oct 15 22:15:12 actually, the modem might be simpler to get some response from Oct 15 22:15:22 ok Oct 15 22:15:37 let me check some things Oct 15 22:21:25 I'm assuming you've already tried getting support from mikro ? Oct 15 22:23:19 "Quickly add functionalities like GSM, GPS" Oct 15 22:23:41 surely they can give a quick outline then on how to "quickly" add those functionalities :P Oct 15 22:23:44 We've been trying for about 4 days to get someone to help Oct 15 22:23:57 and striking out Oct 15 22:24:38 you have installed m-center and it sees the modem? Oct 15 22:25:13 lol Oct 15 22:26:30 I do not think we have installed m-center Oct 15 22:27:42 I know I haven't. One of my guys has been trying things for the past couple of hours. He says he doesn't know what m-center is and I don't either. So I guess the short answer is no. Oct 15 22:27:57 it doesn't look relevant Oct 15 22:27:58 and what part of the tutorial are you stuck on? A link to the tutorial might help. Oct 15 22:28:07 windows software for... seomthing Oct 15 22:28:17 lol, what tutorial Oct 15 22:28:22 nothing is windows in this project Oct 15 22:28:43 if there is a tutorial, I'm happy to use it. Oct 15 22:29:03 ok...so with zero knowledge...zero place to start...instead of flailing about on IRC I'd install the windows ware and find out if the board is even good. Oct 15 22:29:15 good lord. Oct 15 22:29:17 Snert_: what are you talking about? Oct 15 22:29:34 how would he use windows to communicate with the click board? Oct 15 22:29:58 looked like m-center was used to talk to the board. Oct 15 22:30:05 What I really want is an expert to just get me over this particular hurdle. I don't want to become a syslevel BeagleBone developer. :) I just ultimately want my node.js application to run on this thing. That part, I can handle, but the difficulty I'm having is being able to recognize the three IO components I need to recognize. Oct 15 22:30:12 Snert_: how did you arrive at that conclusion? Oct 15 22:30:51 14:14 (qwebirc10344) https://www.mikroe.com/4g-lte-na-click <----- from this. Oct 15 22:30:57 qwebirc10344: yeah don't worry, I'm still gathering some info so I can help you without having to look stuff up along the way Oct 15 22:31:44 Snert_: and how is windows software going to talk to a board that's plugged into the beaglebone? Oct 15 22:31:56 ohhh Oct 15 22:31:58 it has micro-usb Oct 15 22:32:05 or not Oct 15 22:32:08 no never mind Oct 15 22:32:31 no it does say it... jeez I need to read first and type later -.- Oct 15 22:32:37 gotta start somewhere. And the manufacturer's software might be a good place to start Oct 15 22:32:49 then adapt to bb Oct 15 22:32:50 Snert_: but still, the only thing you test that way is that the board isn't DOA Oct 15 22:33:00 yep. Oct 15 22:33:10 Proving the board is not DOA is a good start. Oct 15 22:33:19 I'd say with a new board I'd assume it isn't unless there are indications it might be Oct 15 22:33:21 a solid place to move forward from Oct 15 22:33:26 no it isn't Oct 15 22:33:35 since after learning that info he will be no step closer Oct 15 22:33:51 board is def not dead. We can interact with it quite a bit. In fact, my colleague is now able to talk to the onboard BLE system Oct 15 22:34:03 it's onboard, so not a cape/click situation, but it's progress Oct 15 22:34:07 he means the LTE click Oct 15 22:35:09 getting the LTE click to work by connecting it via micro-usb to a windows machine does not provide any useful info on how to get it to work when connected to the bbb via the mikroBUS cape Oct 15 22:36:45 I don't think the parts are defective Oct 15 22:37:17 Our trouble is getting the dev/tree set right so that our application can talk to the LTE and GPS respectively Oct 15 22:37:26 At least, we think that's the issue Oct 15 22:37:31 my suggestion would be to first use config-pin instead of making an overlay Oct 15 22:37:50 that's a simpler way to test communication with the boards Oct 15 22:37:55 DTS and DTC compilers and such. That's the part that's swahili to us. Oct 15 22:38:29 I found some command line stuff for config pin. But when I try, the display tells me no rights. Oct 15 22:38:54 it does look like a bit of care is needed since you can't plug the two clicks into any two slots Oct 15 22:38:56 And, based on what you are saying about the cape, I'm not sure I'm even trying the correct pins Oct 15 22:38:58 some slots share some resources Oct 15 22:39:08 wait, what? Oct 15 22:39:35 we have GNSS 5 (GPS) in slot 1 Oct 15 22:39:41 and LTE in slot 2 Oct 15 22:40:34 If that's the whole problem, I'm gonna be so happy (and so dang ticked off)!!! ;) Oct 15 22:41:20 it looks like those choices should be fine Oct 15 22:42:37 ok Oct 15 22:44:40 just hold on a bit longer, I've nearly gathered the info I need from the schematics Oct 15 22:45:47 I'm holding, and very grateful Oct 15 22:56:12 of course they labeled all the peripherals wrong in the schematics, how helpful Oct 15 22:56:23 yikes Oct 15 22:56:49 (i.e. "spi2" means spi0, "rx2" is the rxd of uart4, etc) Oct 15 22:56:49 this is the cape schematics or the "click" schematics? Oct 15 22:56:51 cape Oct 15 22:57:00 holy cow Oct 15 22:57:36 I can try some command line commands if you think that's a good next step Oct 15 22:58:29 I've gathered all I need from the schematics, I'm cross-referencing it with my pins list to check what it actually connects to and if there are any conflicts/caveats Oct 15 23:02:57 hmmmmmm Oct 15 23:03:59 so Oct 15 23:05:13 the LTE click uses the "CS" and "INT" pins as uart RTS and CTS signals Oct 15 23:06:01 but for none of the slots on the mikroBUS cape do the CS/INT pins connect to pins configurable as any uart RTS/CTS (let alone the right one) Oct 15 23:06:37 so, I'm hosed? Oct 15 23:07:07 I don't know if hw flow control is required Oct 15 23:07:17 I mean, it's literally the same manufacturer for the cape and the clicks, if I understand it correctly Oct 15 23:07:43 yep Oct 15 23:08:20 yep, I'm hosed? Oct 15 23:08:29 or yep, it's same mfgr Oct 15 23:08:44 or same "mf" in this case Oct 15 23:09:19 same mfgr Oct 15 23:09:26 I don't know if you're hosed Oct 15 23:09:56 at the very least they didn't keep this LTE click in mind when they selected the pinmux Oct 15 23:10:39 (or they couldn't figure out any way to allocate the pins to allow hw flow control to work for it) Oct 15 23:12:08 do you want me to try something? Oct 15 23:12:12 so, here's my notes: https://pastebin.com/raw/2sr8YgVZ Oct 15 23:12:18 yeah I think we can try something Oct 15 23:12:33 ok Oct 15 23:12:36 I'm ready Oct 15 23:13:11 so, the gnss click uses both uart and spi Oct 15 23:13:32 hence your clicks cannot be in slots 2 + 3 Oct 15 23:13:49 so, I should use 1 and 4 then Oct 15 23:14:00 right? Oct 15 23:14:02 nor is the combination (slot 1 lte, slot 3 gnss) allowed Oct 15 23:14:20 and if you put gnss in any slot other than slot 3, you need to disable hdmi audio in /boot/uEnv.txt Oct 15 23:14:23 1 lte, 4 gnss?? Oct 15 23:14:36 I have absolutely no care at all about which slot Oct 15 23:14:50 as long as I don't need to put both in the same one, I'm happy Oct 15 23:15:41 i have boot/uEnv.txt open Oct 15 23:15:52 there should be a line about disable audio Oct 15 23:17:21 https://pastebin.com/3ck4L728 Oct 15 23:17:39 #disable_uboot_overlay_audio=1 Oct 15 23:17:47 just remove the #, yes? Oct 15 23:18:15 yep, uncomment that one if you want the gnss click in slot 1, 2, or 4 Oct 15 23:18:36 You are the boss. Which slots do you recommend? Oct 15 23:20:18 also, if you don't need video output from the beaglebone, it looks like it would be fairly easy (minor patch) to get hw flow control working for the lte module if it's in slot 1 or 4 Oct 15 23:21:17 so, disable video in the uEnv.txt also? Oct 15 23:21:43 that's not urgent, it's more just to influence slot decision right now Oct 15 23:21:55 ok. I disabled video as well Oct 15 23:21:56 gnss in 3 + lte in 4 might be an option? Oct 15 23:21:59 we def do not need Oct 15 23:22:27 you said earlier that we cannot be in 2+3 Oct 15 23:22:45 as in, use those two slots for the two cards Oct 15 23:22:49 but I guess that meant in both. It didn't mean that both 2 and 3 are off limits to me Oct 15 23:23:00 (lte in 2 + gnss in 3 or lte in 3 + gnss in 2) Oct 15 23:23:23 slots 2 and 3 share the same uart Oct 15 23:23:26 both cards need an uart Oct 15 23:23:28 we are trying gnss in 3 and lte in 4 Oct 15 23:24:19 rebooting now Oct 15 23:25:15 ok, we are back up Oct 15 23:26:41 what next? ;) Oct 15 23:26:52 there are some jumpers that need to be set right Oct 15 23:27:07 wait WHAT Oct 15 23:27:27 those aren't jumpers, they're soldered 0ohm resistors Oct 15 23:27:34 ok Oct 15 23:29:00 can you check the bottom side of the cape, does it look like https://cdn1-shop.mikroe.com/img/product/beaglebone-mikrobus-cape/beaglebone-mikrobus-cape-thickbox_default-2.jpg ? Oct 15 23:29:13 i.e. those jumper resistors soldered in the same position? Oct 15 23:29:25 (all toward the left) Oct 15 23:29:57 hold. this sucker is hard to pull apart Oct 15 23:31:10 yes, looks exactly like that Oct 15 23:31:34 okay, so without grabbing a soldering iron, slot 3 has no spi Oct 15 23:31:59 I'm guessing that's bad Oct 15 23:32:02 it's really great how well they documented these slot constraints Oct 15 23:32:05 gnss uses spi Oct 15 23:32:26 should we do Oct 15 23:32:27 lte in 3 + gnss in 2 Oct 15 23:32:28 ? Oct 15 23:32:29 I don't know why exactly gnss has both spi and uart, haven't read the docs yet Oct 15 23:32:32 (maybe it's either-or) Oct 15 23:33:39 wait Oct 15 23:33:43 I'm blind Oct 15 23:33:49 it uses i2c and uart, not spi Oct 15 23:33:57 ok excellent Oct 15 23:34:00 okay that makes things a lot simpler Oct 15 23:34:26 cool Oct 15 23:34:41 then lte in 1 or 4, gnss in any other slot Oct 15 23:35:45 so Oct 15 23:35:57 GNSS in 3 and LTE in 4 is what we had a minute ago Oct 15 23:36:03 is that ok, you think? Oct 15 23:37:20 should be fine Oct 15 23:37:44 cool Oct 15 23:38:14 any command line stuff I should run now? Oct 15 23:42:15 ah good, the docs are lying Oct 15 23:42:39 ok Oct 15 23:42:42 "The PWRKEY pin is routed to the mikroBUS RST pin, and it is used during the power-up sequence. A low pulse on this pin will power up the device" Oct 15 23:43:06 which device? Oct 15 23:43:34 hmm, or are they actually right Oct 15 23:43:53 the LTE modem Oct 15 23:45:48 well let's not worry about that signal for now Oct 15 23:45:53 ok Oct 15 23:50:57 really appreciate your help. I feel like we are close to clearing this hurdle that's been haunting me Oct 15 23:52:12 oh jeez I was like 'wait WHAT?", but it turns out that in the click schematics the "TX" and "RX" pins are labeled opposite to the cape schematic Oct 15 23:53:27 that's makes me feel a little better Oct 15 23:53:40 I saw that yesterday and thought I just didn't understand something Oct 15 23:53:50 what a mess -.- Oct 15 23:54:33 to say the least Oct 15 23:54:37 so, let's start with config-pin P9.11 uart && config-pin P9.13 uart Oct 15 23:54:50 sudo? or no? Oct 15 23:55:05 I don't think it should require it Oct 15 23:55:18 but if you get permission denied then try with sudo :P Oct 15 23:55:47 ok. let me try it Oct 15 23:56:16 is this gps or lte? Oct 15 23:56:19 lte Oct 15 23:56:31 ok Oct 15 23:56:55 gotta ssh back in. Had to move the device to different power source. Had it on a battery on my desk and the battery died Oct 15 23:57:21 config pins seemed to work Oct 15 23:57:24 no errors this time Oct 15 23:57:48 okay Oct 15 23:58:04 is there a test I can run to check? Oct 15 23:59:12 so, this is the pin usage: https://pastebin.com/raw/fM0EksPq Oct 15 23:59:36 ok Oct 15 23:59:41 I did 11 and 13 Oct 15 23:59:44 so we'll want to set powerkey and rts both as output-high with: Oct 16 00:00:15 echo high >/sys/class/gpio$((1*32+14))/direction Oct 16 00:00:25 echo high >/sys/class/gpio$((2*32+4))/direction Oct 16 00:00:42 -bash: /sys/class/gpio46/direction: No such file or directory Oct 16 00:00:50 oh hum Oct 16 00:00:56 oh sorry Oct 16 00:01:03 class/gpio/gpio$(( Oct 16 00:01:08 the /gpio/ was missing Oct 16 00:01:45 yep Oct 16 00:01:55 figured that one out all by myself ;) Oct 16 00:01:57 you might be interested in my show-pins script to examine the status of pins and gpios: https://github.com/mvduin/bbb-pin-utils/#show-pins Oct 16 00:02:00 what should have happened Oct 16 00:03:17 after installation check sudo show-pins | grep -P 'P8\.1[6703]|P9\.1[13]' Oct 16 00:03:26 to get an overview of the relevant pins Oct 16 00:03:45 oh, ok Oct 16 00:04:39 but you can also manually check what e.g. CTS is doing with: cat /sys/class/gpio/gpio27/value Oct 16 00:04:54 (and gpio23 for RI) Oct 16 00:05:33 https://pastebin.com/FzAV3UW5 Oct 16 00:05:54 hmm, cts is low Oct 16 00:06:16 27 is 0 Oct 16 00:06:18 23 is 1 Oct 16 00:06:41 wait, you didn't set rts (gpio2.04) to output yet Oct 16 00:07:22 probably not Oct 16 00:07:32 echo high >/sys/class/gpio/gpio$((2*32+4))/direction Oct 16 00:07:35 I've only run the commands you told me to. I may have missed one Oct 16 00:07:45 yeah I gave two of such echo commands Oct 16 00:07:53 one for 1.14 and one for 2.04 Oct 16 00:08:00 yes, upon further review Oct 16 00:08:03 I see that now Oct 16 00:09:29 did it Oct 16 00:09:33 but still looks same Oct 16 00:09:34 oh btw, apparently the LTE click has a logic voltage select jumper. I do hope it's set to the "3.3v" position. (but I assume it is, since your beaglebone hasn't died yet) Oct 16 00:09:39 hold Oct 16 00:09:44 lol Oct 16 00:09:45 brb Oct 16 00:11:11 I'm back Oct 16 00:11:42 so, before we go any further though... suppose you have communication with the modem working at some point. then what? Oct 16 00:12:54 with respect to the modem? Oct 16 00:13:21 it gets used in our node.js app. It is how we send json data into AWS Kinesis Oct 16 00:13:52 you already know how to talk to the modem, or have a library for it? or is there a kernel driver? Oct 16 00:14:07 The BLE and the GNSS are used to do some math based on Lat/Lng values and RSSI strength from the BLE devices we are listening to. Oct 16 00:14:59 mikro apparently has a library for it, but it's some weird binary package for their own compilers Oct 16 00:15:03 We had all of that working on a Raspberry PI before using some libraries Oct 16 00:15:23 with this same module? have a link to the library? Oct 16 00:15:45 for the LTE modem specifically Oct 16 00:16:01 wasn't this same module. We probably erroneously assumed this stuff would have readily available libs Oct 16 00:16:36 I see no evidence of it Oct 16 00:18:12 does the output in pastebin at least look correct? Oct 16 00:19:28 I kinda expect CTS to be high... Oct 16 00:19:52 unless that doesn't work initially and needs to be configured via AT commands or something Oct 16 00:20:16 but I haven't seen any docs, so I have no idea what the proper startup procedure is, or what the signals should look like, or even what baudrate to use Oct 16 00:20:30 you can try pulsing powerkey low Oct 16 00:20:53 i.e. set gpio46/value to 0 and back to 1 Oct 16 00:20:58 see if that has any effect Oct 16 00:21:22 I'm sorry, do you have a command for that? Oct 16 00:22:00 echo 0 >/sys/class/gpio/gpio46/value # 46 == 1*32+14 Oct 16 00:22:06 and then echo 1 to it Oct 16 00:23:01 echo: write error: Operation not permitted Oct 16 00:23:04 huh Oct 16 00:23:17 sudo echo 0 >/sys/class/gpio/gpio46/value Oct 16 00:23:50 sudo doesn't work like, you're redirecting the output of "sudo echo 0" to that path Oct 16 00:23:55 but... you shouldn't need sudo for this Oct 16 00:24:22 cat /sys/class/gpio/gpio46/direction Oct 16 00:24:27 I tried it without sudo first Oct 16 00:24:56 or, can you show the show-pins output again? Oct 16 00:25:05 that cat command returns Oct 16 00:25:06 in Oct 16 00:25:26 wait what? did you reboot? it was output earlier Oct 16 00:26:40 honestly this is starting to feel a bit hopeless Oct 16 00:28:22 https://pastebin.com/MaD6bGh1 Oct 16 00:28:40 so you did reboot Oct 16 00:28:47 everything is back to default Oct 16 00:29:59 anyway, doesn't matter... unless you can find docs or code to get this modem working, what we're doing is kinda pointless Oct 16 00:30:52 Oh Oct 16 00:31:04 the stuff we were doing goes away if we reboot? Oct 16 00:31:17 mikroe did not do the beaglebone a favor by selling this cape and pretending you can actually get random click boards working on it Oct 16 00:31:25 yes Oct 16 00:33:08 I see that Oct 16 00:33:19 not sure how to proceed Oct 16 00:35:02 bitch at mikroe Oct 16 00:36:10 "Quickly add functionalities like GSM, GPS" -- product description of cape Oct 16 00:36:23 well, let's hear from them which GSM and GPS modules they have *tested* on the beaglebone Oct 16 00:40:52 I am super thankful for your help Oct 16 00:41:10 unfortunately, I have an urgent issue that I have to step away for at the moment Oct 16 00:41:25 but I definitely plan to bitch at mikroe Oct 16 00:42:06 it also just occurred to me this cape is basically nothing more than a set of jumper wires, except using jumpers to connect a click to the beaglebone would probably have taken less time :P Oct 16 00:49:02 qwebirc10344: in retrospect we should have tried to get the gnss working first... it actually seems to have docs :P Oct 16 00:49:26 but I'm kinda done with these clicks for now Oct 16 00:52:35 but the very short version for any click that uses uart: Oct 16 00:53:13 config-pin P9.21 uart && config-pin P9.22 uart # slot 1 (ttyS2) Oct 16 00:53:31 config-pin P9.24 uart && config-pin P9.26 uart # slot 2 or 3 (ttyS1) Oct 16 00:53:50 config-pin P9.13 uart && config-pin P9.11 uart # slot 4 (ttyS4) Oct 16 00:55:40 the gnss module seems to have plenty of docs: https://www.u-blox.com/en/product/neo-m8-series Oct 16 00:59:47 (plus it also supports i2c, which should work without having to do any pin setup) Oct 16 01:15:29 I have that Cape! Oct 16 01:15:54 I should use a click or two to try 'em out. Oct 16 01:16:09 Hmm...I will use what you all described earlier. Thank you. Oct 16 01:41:48 thank you Oct 16 01:41:55 set_: thank you Oct 16 01:42:12 zmatt: can't thank you enough. You are a champ Oct 16 02:58:42 set_: ehm, in case you missed it: the cape sucks **** ENDING LOGGING AT Tue Oct 16 02:59:59 2018