**** BEGIN LOGGING AT Wed Jan 15 02:59:57 2020 Jan 15 04:39:35 hey,guys Jan 15 09:20:14 Can someone suggest a camera module for PocketBeagle board to make webcam or IPcam project? Jan 15 09:34:12 Siegurd: usb would be your only option, hence you'd need to equip your pocketbeagle with a usb host port (there are instructions for this I think) Jan 15 09:36:10 also... how were you planning on making a "webcam" or "IPcam" when the pocketbeagle has no networking? Jan 15 09:38:23 the linux driver for the usb controller on the am335x is known to currently have fairly poor performance. using usb-networking at the same time as an usb camera will no doubt further deteriorate that performance Jan 15 09:38:43 (in principle these performance issues should be fixable, but that requires someone to dig into fixing the driver) Jan 15 09:45:51 appreciative Jan 15 09:49:02 for an ip camera, there are no doubt better suited devices... like actual ip cameras, which I tink nowadays can be obtained for less than a pocketbeagle :P Jan 15 09:53:10 :] Jan 15 10:00:59 you sure can... 720p ip security cam with wifi, sd card recording, 120 degree FOV, infrared light for low-light conditions (can be turned on/off via app), motion detection, and li-ion battery to keep recording for 3.5 hours after power loss... normally $17.48, currently on sale for $12.41, free shipping Jan 15 10:01:14 that's china for ya Jan 15 10:01:44 oh, sold out Jan 15 10:02:33 but it's not the only one Jan 15 10:09:04 which exactly model do you recommend? Jan 15 10:10:30 I don't recommend anything, I just searched dx.com for a few seconds Jan 15 10:11:20 if you want to know in advance that whatever you're buying is not complete crap you'll have to put in more effort (or gamble) Jan 15 10:44:57 ok, thanks! Jan 15 13:14:50 https://makezine.com/2020/01/08/how-two-california-kids-overcame-doubters-to-automate-the-freshest-burger-ever-served/ Jan 15 13:15:13 “We’re using mostly BeagleBone Blacks, and it’s all Linux, off-the-shelf Ubuntu..." Jan 15 13:53:53 tlwoerner: cool! :D Jan 15 16:18:20 interesting read, the BBB is handy for a lot of things, simply because it's a platform in and of itself that is a quasi standard and has a known development cycle and platform. New platforms generally have none of that. Jan 15 16:53:09 I wonder what made them choose the BBB over the more popular rpi Jan 15 17:41:55 have you worked with an RPI? Jan 15 18:27:12 e Jan 15 18:40:17 m Jan 15 19:15:05 GenTooMan: nope Jan 15 19:15:17 I don't own any rpi Jan 15 19:44:30 zmatt It's fairly IO limited is the primary issue, even in the embedded form factor. It's not a good fit for industrial use since it is commercial grade (0-70C). Just a few frustrations with the RPI. It's primary bonus is it's cheap, easy to get, and drivers exist for a lot of simple things added on. Jan 15 19:45:19 I mean, I know the rpi has plenty of limitations, I'm just curious what exactly *their* motivation was Jan 15 19:47:31 hmmm that might have been something good to put in the article, my guess is they were familiar with it and it has a lot of the peripherals you want for robotics built in. Jan 15 19:57:10 well and the fact you can hook something up quick and test it out. :D Jan 16 01:26:30 Hey, is there going to be another official bone-linux image in the future for older boards, i.e. BBB, BBBW, and etc? Jan 16 01:27:10 I am asking b/c i was going to learn more and i have no clue as to what is going to be put on the newer images, e.g. nginx, apache2, blah, and which versions of these tech? Jan 16 01:28:30 I mean, I was thinking of getting a book on nginx but the current version of nginx is what I have been learning. So, if the update/upgrade to a new release of "nginx" is being put on the boards in the new images, I would like a notification or "heads up." Jan 16 01:28:58 Is that possible? Jan 16 01:30:47 Like this for instance: "Our new image will have 'nginx -v 13.4.x' and 'python -v 3.8.x' and so on... Jan 16 01:51:44 "is there going to be another official bone-linux image in the future for older boards, i.e. BBB, BBBW" ... why would you think there wouldn't be? the latest images on the site are available for all beaglebones Jan 16 01:52:20 B/c...people may only want users to make their own images in the future. I am guessing but that may very well be a new policy. Jan 16 01:53:38 ??? Jan 16 01:53:52 sometimes I have absolutely no idea how your mind works Jan 16 01:54:24 I am asking b/c i know sometimes things change. I just wanted to make sure that this changed or was not going to change. You know...get a brother the "down-low?" Jan 16 01:54:58 And yes. I am quoting rap songs. Sheesh. You never let me be me! Jan 16 01:56:23 Okay. Enough silliness. If I was going to use pasm, would I need it to be in my PATH or just put everything in one dir? Jan 16 01:56:49 I found some old source and I want to test it on my PRU(s). Jan 16 01:57:19 Or both or neither? Jan 16 01:57:41 I would suggest copying pasm to /usr/local/bin/ Jan 16 01:57:45 that's where I put it anyway Jan 16 02:00:31 Okay. I have understood that the kernel looks for things in that dir. Should I put all items I want for the system to recognize in /usr/local/bin/? Jan 16 02:00:46 the kernel does not look for anything in that dir Jan 16 02:01:21 To tell you the truth, I usually just put dir. in PATH for use since i rarely use envs. Jan 16 02:01:27 Oh. Jan 16 02:01:37 I don't know what you mean by "all items for the system to recognize" ... that directory is for exactly one thing, and that's for executables you want to be in PATH without actually bothering to change PATH Jan 16 02:01:50 Oh. Jan 16 02:01:55 Okay. I got it now. Jan 16 02:02:07 I misunderstood what I understood. Thank you. Jan 16 02:03:55 So, the executables go in /usr/local/bin/. Hmm. So, this basically helps me run them w/ the command ./ or sudo ./? Jan 16 02:04:21 Going to look now! Jan 16 02:05:00 There is nothing in my system in that dir. Is that odd? Jan 16 02:05:51 if you put pasm into /usr/local/bin then you can execute it as simply "pasm" Jan 16 02:05:51 Now, /usr/include/ is full of items. Jan 16 02:05:58 nice. Jan 16 02:06:05 it's for programs you installed yourself Jan 16 02:06:11 Oh. Jan 16 02:06:18 hence if you haven't put anything there, it'll be empty Jan 16 02:06:44 Okay. So, the system or system devs. develop and I add on stuff and make it work. Neat! Jan 16 02:06:54 Yep. It is empty b/c i have not put anything there. Jan 16 02:07:25 Now. Jan 16 02:07:47 Should I put the entire dir. of pasm in /usr/local/bin/ or should I just put the executable of pasm in it? Jan 16 02:07:52 just the executable Jan 16 02:07:56 Nice! Jan 16 02:08:09 putting a directory in /usr/local/bin would be completely pointless Jan 16 02:08:19 I never knew this idea to be true. There is one way now to test it. Jan 16 02:08:20 Oh. Jan 16 02:08:21 Okay. Jan 16 02:08:33 I had to build pasm from source. Jan 16 02:08:46 I found it on beagleboard.org's github.com page. Jan 16 02:08:59 yep, dunno why there's no debian package for it Jan 16 02:09:07 nor why it's not installed by default Jan 16 02:09:07 Me neither. I tested it. Jan 16 02:09:30 I tried pasm and then I tried in debian, "sudo apt install pasm." Jan 16 02:09:34 Neither nor. Jan 16 02:09:44 So, off to test. Jan 16 02:42:38 https://pastebin.com/HFUK4Xm8 is b/c of this idea, https://pastebin.com/ZWp22a4J (a makefile) for running pru(s) on the BBB. I have not got around to using the config-pin util on the board currently b/c I cannot make it past the makefile. Have you come across this issue before? Jan 16 02:43:15 oh you just need to install libprussdrv Jan 16 02:43:25 Oh. Nice! Jan 16 02:43:37 lemme check what the exact instructions are Jan 16 02:43:50 Okay! Jan 16 02:45:25 It seems this fellow did all the work and got the correct files but then just typed out in a readme to "add the the prussdrv libraries in /usr/lib/. Jan 16 02:45:54 so, you already have a checkout of the beagleboard/am335x_pru_package repo Jan 16 02:46:02 I had it and still have it. yes. Jan 16 02:46:15 in there go to the directory pru_sw/app_loader/interface Jan 16 02:46:18 Okay. Jan 16 02:46:41 then execute: make CROSS_COMPILE= install Jan 16 02:47:32 Permission errors. Jan 16 02:47:40 I will use sudo, just kidding. Jan 16 02:48:24 https://pastebin.com/hCNEgXKe Jan 16 02:48:29 curious, I thought the debian user should have permission Jan 16 02:48:41 Oh. Jan 16 02:48:43 oh Jan 16 02:48:54 yeah that makes sense Jan 16 02:49:01 bad makefile Jan 16 02:49:03 Oh. Jan 16 02:50:24 So, I should change the file to read /usr/local/bin/ instead or just /usr/local/? Jan 16 02:50:32 no Jan 16 02:50:57 The /usr/local/lib/ are my python directories. Jan 16 02:51:23 try removing these two lines: https://pastebin.com/raw/EgW0Ge4C Jan 16 02:51:47 and then retry the make CROSS_COMPILE= install Jan 16 02:52:15 Okay. Jan 16 02:53:29 https://pastebin.com/N0pUk8ve Jan 16 02:53:45 can you share the output of ls -l /usr/local Jan 16 02:53:51 sure. Jan 16 02:53:55 Please hold. Jan 16 02:54:38 https://pastebin.com/1UBSxcgM Jan 16 02:55:35 huh... can you share the output of the command: id Jan 16 02:55:43 sure. Jan 16 02:56:20 https://pastebin.com/Kx0fBZ2K Jan 16 02:56:55 oh lol, user debian isn't in group staff... so the fact that group staff can write in /usr/local/ is pointless Jan 16 02:56:59 in that case just sudo it Jan 16 02:57:07 Okay. Jan 16 02:58:23 @zmatt: should I put back those files I was supposed to take out in the Makefile? Jan 16 02:58:43 commands = files, sorry. Jan 16 02:59:13 I am asking b/c all I did was hash mark them out. Jan 16 02:59:23 Instead of erasing the entire line. Jan 16 02:59:40 no... but on second thought, just copy the relevant files manually: Jan 16 02:59:45 Okay. Jan 16 02:59:46 sudo cp ../lib/libprussdrv.a /usr/local/lib/ Jan 16 02:59:51 Right. **** ENDING LOGGING AT Thu Jan 16 02:59:59 2020