**** BEGIN LOGGING AT Thu Feb 21 02:59:57 2019 Feb 21 03:14:44 Is PRU uio being phased out by RPROC? Feb 21 03:26:34 I think it is there in the updated 4.19 kernel. Feb 21 14:08:42 Hi Feb 21 14:09:30 I want to test my beagleboard-x15 with bkinking an external led and i did not find any sample code in internet. Feb 21 14:09:53 *blinking external led Feb 21 14:10:13 in any language,python, c++... Feb 21 14:13:39 external led connected how? Feb 21 14:14:51 connected to one of the output port. Feb 21 14:15:13 in general things work the same on the beagleboard-x15 as on other embedded linux systems like the beaglebone, except for pin config. pin config is annoying on the bbx15 Feb 21 14:16:15 by default the expansion headers are configured by u-boot for use with the am572x-EVM LCD board Feb 21 14:16:34 if you find some pin configured as gpio among those, you should be able to use that Feb 21 14:17:12 ok how can i configure gpio port for my led for exemple? Feb 21 14:18:54 how can i configure pins as gpio in my bbx15? Feb 21 14:19:27 in general TI expects you to do the pin config in u-boot, because that's the only time when this can be done without risking glitches on the IOs. In some cases it wouldn't matter though, such as for a gpio controlling a led, which means you could also configure it using Device Tree like other ARM-based linux systems Feb 21 14:20:47 so your options are: Feb 21 14:21:21 1. reuse the pin config already done by u-boot for the lcd board, i.e. in this case find some pin that's currently configured as gpio (and then export it via sysfs and toggle it as usual) Feb 21 14:22:30 2. modify the device tree to configure a pin as gpio. (if you prefer I also have a patched u-boot that does not perform any configuration of the expansion header pins (leaves them in "safe mode"), to have a "clean slate" to start with.) Feb 21 14:23:44 3. modify u-boot to use your custom configuration of the expansion header pins, in addition to having to declare your devices in DT. This is the most annoying and difficult option but the only one that is safe for every type of pin usage. Feb 21 14:24:12 for your simple test of a gpio-connected led, any of these will do Feb 21 14:24:40 ok thank you Feb 21 14:26:20 where can i have the patched u-boot? Feb 21 14:31:21 the patch itself is https://github.com/dutchanddutch/u-boot/commits/patch/ti2017.01/x15-pinmux which you'd merge into rcn's u-boot for the bbx15. the merged result is https://github.com/dutchanddutch/u-boot/commits/ad608d1d1bc5 Feb 21 14:31:42 wait, no Feb 21 14:31:53 huh Feb 21 14:32:47 that merged result seems to include my uart patch, hmmz Feb 21 14:32:55 oh well, that's not a problem either I guess Feb 21 14:33:10 ok Feb 21 14:33:41 the uart patch adds support for baudrates 230400 and 460800, but the default is still 115200 Feb 21 14:38:15 so i can use this patch to configure all my gpios if i want to test led, relay, potentiometers....right? Feb 21 14:39:10 potentiometers? how do you use gpios to test a potentiometer? Feb 21 14:39:25 i meant pwm Feb 21 14:40:41 also, read the three options I gave carefully. my u-boot patch itself does not configure any pins, rather it disables the pin configuration done by u-boot (for the expansion header pins). it is also useful to have a reference of where this pin configuration is located in the u-boot source code. Feb 21 14:40:46 pwm is not gpio Feb 21 14:41:21 although all three options also exist for pwm (assuming the connected device is insensitive to a brief glitch on the pwm pin during boot) Feb 21 14:42:02 except pwm will require picking a pin with pwm support, and configuring the pwm controller in device tree (regardless of which of the three options you pick for pin configuration) Feb 21 14:42:21 ok Feb 21 18:31:25 Trying to serve the website today w/ Gunicorn instead. Wish me luck. Feb 21 18:33:59 ? why? Feb 21 18:34:18 For fun and to learn. I wanted to set up this site to run for the Maker Faire. Feb 21 18:34:33 I want people to visit this site to control my Robot! Feb 21 18:34:47 ok, what does this have to do with some obscure web server? Feb 21 18:35:09 Oh. I found this idea: https://www.digitalocean.com/community/tutorials/how-to-serve-flask-applications-with-gunicorn-and-nginx-on-ubuntu-18-04. Feb 21 18:35:13 ... Feb 21 18:35:26 It is b/c I am using a Flask App and Python w/ wsgi and nginx. Feb 21 18:35:58 They also had one w/ uwsgi but that one did not work w/ nginx for some reason. Feb 21 18:36:02 I am still testing. Feb 21 18:36:44 wait, gunicorn is just the application server? doesn't nginx support wsgi natively? Feb 21 18:37:16 ah, that's uwsgi Feb 21 18:37:16 Yes. Feb 21 18:37:33 Yes, to both ideas. Feb 21 18:37:43 no zmatt Feb 21 18:37:47 The uwsgi is for Python. Feb 21 18:37:50 it doesn't support it natively, sadly Feb 21 18:38:49 why don't you use uwsgi by the way set_ ? Feb 21 18:38:53 it seems lighter Feb 21 18:38:56 but gunicorn works too Feb 21 18:39:48 I tried and could not get it to work from this idea: https://www.digitalocean.com/community/tutorials/how-to-serve-flask-applications-with-uswgi-and-nginx-on-ubuntu-18-04. Feb 21 18:40:20 Nothing would work. I tried everything. My .service file is not good for some reason. It will not start. Feb 21 18:40:25 ok yeah, that's what I was thinking of Feb 21 18:40:36 I don't think you have to write any service file when using that? Feb 21 18:40:45 the distro would provide it Feb 21 18:40:50 exactly Feb 21 18:40:58 not all tutorials on the internet are good set_ , you can even say that most of them are bad Feb 21 18:41:06 I just read official documentation when I can Feb 21 18:41:06 I will test that but I am sure the .service file is for starting my .ini file. Feb 21 18:41:16 which ini file ? Feb 21 18:41:20 I will show you. Feb 21 18:41:22 Please hold. Feb 21 18:41:46 there is a .service involved indeed but you shouldn't be the one writing it Feb 21 18:41:54 distribution maintainers do it Feb 21 18:41:57 I mean, this tutorial you're pointing at emphatically uses python2 instead of python3, so it's automatically bad Feb 21 18:42:25 lol Feb 21 18:42:29 yeah Feb 21 18:42:34 https://pastebin.com/yTTDDM57 Feb 21 18:42:36 I know. Feb 21 18:42:43 Right... Feb 21 18:42:51 I had to adjust everything already. Feb 21 18:42:59 that looks like a uwsgi config file Feb 21 18:43:10 drop it in whatever is the uwsgi config directory and reload it Feb 21 18:43:11 It also uses Python3.6 which does not come w/ the distro. We have python3.5. Feb 21 18:43:16 it should be good Feb 21 18:43:23 yeah 3.5 3.6 almost the same Feb 21 18:43:24 Okay. Feb 21 18:43:53 you have the cool new f'{var}' format string in 3.6 tho Feb 21 18:43:53 They also said to keep using pip instead of pip3 which does not work well anymore. Feb 21 18:44:00 no you shouldn't do that Feb 21 18:44:00 Aw. Feb 21 18:44:04 pip is for python2 it won't work Feb 21 18:44:08 I know. Feb 21 18:44:13 I already figured that out. Feb 21 18:44:14 use pip3 or python3 -m pip if you're not sure Feb 21 18:44:17 good Feb 21 18:44:18 I have known that idea is true. Feb 21 18:44:23 Okay. Feb 21 18:44:52 I had to stop using the venv b/c it was jacked up for some reason. Feb 21 18:44:57 when you install uwsgi on debian, it will automatically enable a service to start uwsgi applications Feb 21 18:45:03 you don't need to write any service file Feb 21 18:45:13 The venv installed pip on purpose. Feb 21 18:45:14 Okay. Feb 21 18:45:19 No service file. Got it. Feb 21 18:45:30 you set chmod 660 on the socket, and I guess it's owned by user uwsgi Feb 21 18:45:31 you place your .ini file in /etc/uwsgi/apps-available Feb 21 18:45:42 Oh. Feb 21 18:46:13 Okay to both of those ideas. I will test that idea for apps-available now and the user ideas, too. Feb 21 18:46:34 and then create a symlink to it in /etc/uwsgi/apps-enabled Feb 21 18:46:37 ah but it's not the same tutorial Feb 21 18:46:45 if this is a pip installed with venv you can use just "pip" I guess Feb 21 18:47:00 pip = python2, pip3 = python3 Feb 21 18:47:14 in the venv pip would be for python 3 Feb 21 18:47:19 oh weird Feb 21 18:47:22 it sets up a new PATH and stuff Feb 21 18:47:25 ahh Feb 21 18:47:29 That is what they said. Feb 21 18:47:34 but it's not very intuitive, people are used to "python" and "pip" to be python 2 Feb 21 18:47:47 But...they also say start a service. Feb 21 18:47:59 yeah it ought to be set up to accept both Feb 21 18:49:53 Heh.../etc/uwsgi does not exist on my machine. Feb 21 18:49:56 I mean, you could create a custom service if you want to, but debian already ships with a service to launch uwsgi applications Feb 21 18:50:02 that's odd Feb 21 18:50:02 This could be the issue. Feb 21 18:50:16 how did you install uwsgi ? Feb 21 18:50:30 sudo pip3 install uwsgi Feb 21 18:50:35 since those directories are part of the uwsgi package Feb 21 18:50:36 oh Feb 21 18:50:50 so you didn't actually install uwsgi... okay, that makes sense Feb 21 18:51:09 I guess not. I did stop using the venv though. Feb 21 18:51:26 I gave up on their ideas on .service files. Feb 21 18:51:50 the venv part is not mandatory, some just find that cleaner to not pollute the global/user libraries with specific versions and stuff Feb 21 18:52:06 yeah it makes some sense Feb 21 18:52:18 but then you will indeed need a custom systemd service file Feb 21 18:52:22 what problems did you have with it? Feb 21 18:52:25 Okay. Feb 21 18:52:34 Let me see again. Feb 21 18:52:37 Please hold. Feb 21 18:52:52 it seems they explain the process in quite a bit of detail Feb 21 18:53:01 although I do wonder why they don't use a user service file instead Feb 21 18:53:14 that would make the whole process unprivileged Feb 21 18:53:43 hm, although you'd need to be in group www-data for that I guess Feb 21 18:58:49 Hey. Feb 21 18:58:54 What did you want again? Feb 21 18:59:11 oh! Feb 21 18:59:20 I asked what problems you had with setting up the systemd service Feb 21 18:59:31 just to confirm, you had things working up to that point in the tutorial? Feb 21 18:59:45 I can run my flask app w/ my set up, I can run my uwsgi flask app w/ uwsgi, and I cannot set up a .service file. Feb 21 18:59:52 Oh. Feb 21 18:59:54 Okay. Feb 21 19:00:22 What cmd should I show you, i.e. journalctl -xe? Feb 21 19:00:25 ok, so you tested running uwsgi manually and that worked? Feb 21 19:00:29 Yes. Feb 21 19:00:32 first pastebin the service file you created Feb 21 19:00:36 Okay. Feb 21 19:01:30 mawk: chmod 0660 is fine here btw, the service is started with group www-data Feb 21 19:01:48 https://pastebin.com/m3PMa2jt Feb 21 19:01:54 I changed everything already. Feb 21 19:02:15 that is complete nonsense, and also not remotely what the tutorial told you Feb 21 19:02:15 I am using /home/debian/bin for file and directories. Feb 21 19:02:31 I already tried their way. Feb 21 19:02:52 I followed every way they said in order. Many times. Nothing worked ever. Feb 21 19:03:10 their instructions look correct, all you have to do is replace "sammy" by "debian" and use the correct directory for the project and venv Feb 21 19:03:22 I tried that, too. Feb 21 19:03:37 what error did you get? Feb 21 19:03:41 If I use venv, I cannot get many items they say are easy to install. Feb 21 19:04:02 like: sudo pip install uwsgi flask Feb 21 19:04:04 oh you're not using the tutorial at all, but are doing random shit and then are surprised thigns don't work Feb 21 19:04:07 don't use sudo Feb 21 19:04:22 I tried w/out sudo and I get permission errors. Feb 21 19:04:28 don't use "pip" outside the venv, since that's python2 Feb 21 19:04:37 w/in the venv Feb 21 19:04:50 Right. I get that idea. Feb 21 19:04:51 that makes no sense Feb 21 19:04:59 so you probably missed a step Feb 21 19:05:02 No. Feb 21 19:05:04 or did something weird Feb 21 19:05:28 Look. I understand what they were saying and what i was doing. Neither worked so far. Feb 21 19:05:49 They want a Ubuntu 18.0.4 distro instead of Debian 9. Feb 21 19:05:54 Things might be just a bit different. Feb 21 19:05:55 also you lied when you said things worked except for having problems setting up the systemd service, you clearly had problems way earlier Feb 21 19:06:04 Oh. Feb 21 19:06:06 Right. Feb 21 19:06:15 I had all kinds of issues w/ their way. Feb 21 19:06:46 I could not do any of their commands w/in the ~/myproject directory. Feb 21 19:06:56 Once in the venv, that dir. is bogus. Feb 21 19:07:16 Server. Feb 21 19:07:28 I think they want me to have a set up server of Ubuntu. Feb 21 19:08:05 I'm trying the steps right now Feb 21 19:08:08 Cool! Feb 21 19:08:13 How is it going? Feb 21 19:08:30 brb Feb 21 19:08:35 I will let you do your thing. Feb 21 19:08:41 Right back. Feb 21 19:09:10 (looks like both pip and pip3 actually work inside the venv here, but I'm using python 3.7 so maybe this is something that didn't used to work) Feb 21 19:11:29 ok, "pip install uwsgi flash" inside the venv was successful Feb 21 19:12:19 the ufw step can be ignored Feb 21 19:12:29 (there's no firewall enabled by default on the beaglebone) Feb 21 19:13:21 Okay. Feb 21 19:13:24 flask app works when executed directly (development server) Feb 21 19:13:56 pip install uwsgi flask did not work on my end. uwsgi had to be installed differently. Feb 21 19:14:19 I will run it again and show you the issue. Feb 21 19:14:57 uwsgi works when invoked directly too Feb 21 19:16:17 Okay. Feb 21 19:17:36 and I can start the .service successfully Feb 21 19:17:47 not going to test the rest since I can't be bothered to install nginx :P Feb 21 19:17:59 Okay. Feb 21 19:18:01 Fine. Feb 21 19:18:08 I will keep trying on my end. Feb 21 19:20:05 nginx is light zmatt I promise Feb 21 19:21:03 https://pastebin.com/cdWLF9Yt is my "issue" when in my venv and installed wheel. Feb 21 19:21:14 w/ pip install wheel Feb 21 19:21:38 strange Feb 21 19:21:41 Yep. Feb 21 19:21:44 you installed something as root when you weren't supposed to Feb 21 19:21:48 Oh? Feb 21 19:21:48 so you can write files here and there Feb 21 19:21:53 Okay. Feb 21 19:22:02 maybe chown home/debian/40/40/lib/python3.5 to your debian user Feb 21 19:22:16 I have to install everything as root or my system gives me errors/permission stuff. Feb 21 19:22:18 Okay. Feb 21 19:23:16 Invalid user. Feb 21 19:23:21 Hmm. Feb 21 19:23:39 I will reboot a new image on this system. Feb 21 19:23:39 chown debian:debian -R $path Feb 21 19:23:50 Okay. I will try that idea. Feb 21 19:23:50 you have to install absolutely nothing as root apart from the .service file itself Feb 21 19:23:55 you don't have to chown anything Feb 21 19:23:59 you don't have to chmod anything Feb 21 19:24:03 Okay. Feb 21 19:24:16 yeah if in the beggining he doesn't install as root zmatt Feb 21 19:24:18 but it's too late here Feb 21 19:24:29 yes but there the tutorial explicitly uses sudo Feb 21 19:24:33 ah Feb 21 19:24:37 so it's a bad tutorial in the end Feb 21 19:24:42 no? Feb 21 19:24:47 I mean, sudo apt-get Feb 21 19:24:52 you're talking about those parts? Feb 21 19:25:13 ah, no Feb 21 19:25:16 I don't know where he used root Feb 21 19:25:16 okay, so those parts are done as root, you're right, but the tutorial explicitly uses sudo for that Feb 21 19:25:24 but I guess he did it as root with sudo pip3 install ... Feb 21 19:25:32 the tutorial does not use sudo pip3 Feb 21 19:25:38 yeah Feb 21 19:25:41 but he did it anyway Feb 21 19:26:02 after the install of the wheel did not work, I might have done anything to try. Feb 21 19:26:26 Actually, I know I tried other ways since I could not use pip install wheel. Feb 21 19:26:42 you should have stopped right there and asked what the problem is Feb 21 19:26:48 not try random shit Feb 21 19:27:04 Okay. Feb 21 19:27:05 definitely not try using sudo inside a venv Feb 21 19:27:13 Well, now I know. Feb 21 19:27:17 Too late for the past. Feb 21 19:27:34 "sudo pip" or "sudo pip3" is always a mistake Feb 21 19:27:41 Okay. Feb 21 19:27:44 Now, I know. Feb 21 19:27:57 I never thought twice about it. Feb 21 19:28:18 always think twice about using sudo, always know why sudo is needed when you need it Feb 21 19:28:18 outside a venv you do pip3 install --user Feb 21 19:28:25 you don't need that flag Feb 21 19:28:30 it is the default Feb 21 19:28:32 ah Feb 21 19:28:35 Odd days. Feb 21 19:28:36 is it a recent change ? Feb 21 19:28:45 no idea, I didn't know the flag existed Feb 21 19:28:58 Well, forget about my issue. Feb 21 19:29:08 I will restart and boot from a new image and try that way. Feb 21 19:29:20 Peace out! Feb 21 19:29:25 Thank you for the lessons. Feb 21 19:30:24 set_: oh, before you go Feb 21 19:30:49 next time you try, try "pip install setuptools" inside the venv before doing "pip install wheel: Feb 21 19:30:51 " Feb 21 19:31:01 I am in lack of things to do Feb 21 19:31:07 there might be some issue with the old version of setuptools shipped in debian stretch Feb 21 19:31:25 I vaguely recall having had a fight with that but don't remember the details Feb 21 19:31:46 yes Feb 21 19:31:54 mawk: that sounds bizarre, I can't remember the last time I had a lack of things to do Feb 21 19:31:57 I don't know if install upgrades by default, better add -U Feb 21 19:32:12 well I have a ton of things I have to do, but none sound interesting Feb 21 19:32:20 okay that's a very different thing Feb 21 19:32:34 I was asked to do a discord bot, I was asked to reverse engineer a usb smartcard for expensive industrial drawing software, I have to do a chrome extension Feb 21 19:32:46 o.O Feb 21 19:33:05 yeah pretty disparate stuff Feb 21 19:33:26 at my last internship I did everything from service desk to electrical work through firewall and programming Feb 21 19:36:28 I also have to write an article and finish the 6LoWPAN stack Feb 21 19:36:47 I took a look at the "proprietary" solutions out there: thread, ant, dotdot, zigbee Feb 21 19:37:03 all this environement is pretty closed to hobbyists Feb 21 19:37:26 boo Feb 21 19:37:27 in every case you have to pay either royalties or entrance fees to sell a product using these Feb 21 19:37:39 thread seemed the less bad Feb 21 19:37:53 but I still have to give every detail about me so they can me send an encrypted pdf by mail, with watermark and digital signature Feb 21 19:38:00 containing the specification Feb 21 19:38:28 and I like the fact it's over 6LoWPAN and under CoAP, both open stuff Feb 21 19:38:50 so IPv6, which is the future Feb 21 19:39:14 maybe part of it is wanting to keep tight control on the spec and its licensing to be able to enforce compliance testing before a product is allowed to use the trademark, thus ensuring "Thread" devices actually interoperate? Feb 21 19:39:28 yeah Feb 21 19:39:29 similar to what HDMI does Feb 21 19:39:33 that's the primary reason I think Feb 21 19:39:35 but it's not enough Feb 21 19:39:38 zigbee has bad interop Feb 21 19:39:51 and they still charge entrance fees to their foundation and brand Feb 21 19:40:01 USB theoretically also requires testing before you use their trademark, but nobody seems to care Feb 21 19:40:03 so it overall sounds like a bad solution to the problem Feb 21 19:40:08 lol Feb 21 19:40:09 I see Feb 21 19:40:37 USB is a nice example of what happens if you fail to enforce your trademark... with USB-A-male to USB-A-male cables being in shops all over the place Feb 21 19:40:53 I have one in my cables drawer Feb 21 19:41:11 I don't know why I bought it for, I think it's when I thought the rpi was a OTG device Feb 21 19:41:18 which it isn't, except the zero model Feb 21 19:41:25 and my phone's micro-USB OTG port being a "micro-B receptacle" instead of "micro-AB", which means that standards-compliant OTG adapters can't even fit in it Feb 21 19:43:04 well even for OTG it makes no sense to have an A-male to A-male cable :P Feb 21 19:43:26 yeah Feb 21 19:43:30 I figured out that later Feb 21 19:43:43 also I was shocked by the fact usb uses no interrupt, when I was reading the spec Feb 21 19:44:16 it needs micro-A-male to something-B-male or something-A-female Feb 21 19:44:55 (except if you want it to fit in my samsung smartphone, in which case it needs a micro-B-male that lies about being a micro-A-male) Feb 21 19:45:15 yup, usb is polling, polling all the way Feb 21 19:45:27 :D Feb 21 20:08:30 hi there i just got the new beaglebone blue Feb 21 20:09:14 it's not that new anymore I think Feb 21 20:09:48 when i try to connect to the local:3000 i just get an error, I recently just finshed an update Feb 21 20:10:50 ? Feb 21 20:11:06 that's cloud9 Feb 21 20:11:10 is the service up and running ? Feb 21 20:11:15 also it's localhost:3000 not local:3000 Feb 21 20:11:16 ah Feb 21 20:11:33 well it's not localhost either, because that suggests you're running a web browser on the device itself Feb 21 20:12:14 http://beaglebone.local:3000/ so this is what i typed and i got nothing? Feb 21 20:12:26 just a sadface Feb 21 20:12:47 when you say "finished an update", do you mean you reflashed it, or? Feb 21 20:13:04 i used apt-get update and it worked fine Feb 21 20:13:26 then i used apt-get upgrade and it froze and disconnected now it only runs the first blinky program Feb 21 20:13:46 that sounds problematic Feb 21 20:13:52 it sucks! lol Feb 21 20:14:01 did you resume the upgrade Feb 21 20:14:02 ? Feb 21 20:14:13 so i can no longer access the board via cloud9 to resume the upgrade :( Feb 21 20:14:26 oh you used a cloud9 terminal instead of ssh Feb 21 20:14:49 you could use the usb ethernet device no ? Feb 21 20:14:57 then use 192.168.7.2 or something Feb 21 20:15:08 oh god, that means it stopped cloud9 as part of the upgrade, and doing so killed apt-get Feb 21 20:15:18 yeah Feb 21 20:15:25 I run apt in a tmux or screen for that kind of reasons Feb 21 20:15:26 I mean, he probably is using the usb ethernet device Feb 21 20:15:31 how else would he be accessing cloud9 Feb 21 20:15:35 yeah I realized that Feb 21 20:16:08 jibbsmcgee: use an ssh client to connect to the beaglebone instead of using cloud9 Feb 21 20:16:50 then try "sudo apt-get upgrade" again and hope it can resume without problem Feb 21 20:16:51 ok i will try that i can access the file system but what ssh? Feb 21 20:16:59 or maybe first try "sudo apt-get install -f" Feb 21 20:17:04 sorry havent got that far yet Feb 21 20:17:26 run « ssh debian@beaglebone.local » Feb 21 20:18:11 ok so open a terminal and navigate to the BEAGLEBONE correct? Feb 21 20:18:16 every os nowadays has an ssh client, even windows Feb 21 20:18:17 no Feb 21 20:18:32 you can ignore the filesystem, it's irrelevant Feb 21 20:18:32 im on linux zorin Feb 21 20:18:39 ok, then you'll definitely have an ssh client Feb 21 20:18:40 ok thanks zmatt Feb 21 20:18:53 alright what is that lol sorry im so new Feb 21 20:18:59 run the command mawk said Feb 21 20:19:03 ssh debian@beaglebone.local Feb 21 20:19:31 password temppwd Feb 21 20:20:04 ok i have a > displayed in terminal now Feb 21 20:20:20 uhh what? Feb 21 20:20:48 ssh: Could not resolve hostname beaglebone.localtemppwd: Name or service not known Feb 21 20:21:21 type enter before typing the password Feb 21 20:21:22 ehm, I don't know what you did, but it clearly made a mess Feb 21 20:21:34 type ssh debian@beaglebone.local then hit enter and wait for the Password: prompt Feb 21 20:21:36 yeah i can see that :( Feb 21 20:21:38 they type the password and hit enter again Feb 21 20:21:42 yes, run the command "ssh debian@beaglebone.local" (without quotes) Feb 21 20:21:48 enter the password when it asks for it Feb 21 20:22:03 you won't see the password as you type, it's on purpose Feb 21 20:22:32 ok im in!!!!! Feb 21 20:22:35 now what??? Feb 21 20:22:42 just apt-get update? Feb 21 20:22:44 now we use less punctuation at the end of a sentence Feb 21 20:22:47 lol Feb 21 20:22:58 not update, update is just to updates your system's idea of the remote packages Feb 21 20:23:00 and we read what was said earlier Feb 21 20:23:09 21:16 < zmatt> then try "sudo apt-get upgrade" again and hope it can resume without problem Feb 21 20:23:12 upgrade is for effectively upgrading, and you have other commands to recover a failed state like zmatt said Feb 21 20:23:13 21:16 < zmatt> or maybe first try "sudo apt-get install -f" Feb 21 20:24:06 why were you doing apt-get upgrade anyway if you don't actually know what you're doing? Feb 21 20:25:31 cause the "for dummies guide" said so Feb 21 20:25:58 don't believe everything the internet said Feb 21 20:26:04 lol Feb 21 20:26:04 also apparently now im getting a message that tmppwd "Sorry, try again" Feb 21 20:26:09 unless it on the official website of the product you're using Feb 21 20:26:10 temppwd Feb 21 20:26:12 not tmppwd Feb 21 20:26:24 oh my gosh what an idiot wow Feb 21 20:26:26 sorry Feb 21 20:26:48 typos aren't a sin don't worry Feb 21 20:27:00 : dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Feb 21 20:27:04 yeah Feb 21 20:27:06 should i do this? Feb 21 20:27:19 yeah it's a bit like the second command zmatt was suggerating Feb 21 20:27:21 you can try Feb 21 20:27:24 first try sudo apt-get install -f Feb 21 20:27:24 suggering ? Feb 21 20:27:30 if that doesn't work, do what it said Feb 21 20:27:36 ok i will try that first zmatt Feb 21 20:28:03 yeah it said the same thing guess im typeing that in lol Feb 21 20:28:27 cut and paste are powerful tools Feb 21 20:28:38 use wisely :) Feb 21 20:28:40 perhaps not in the hands of noob Feb 21 20:28:42 lol Feb 21 20:29:08 ok its doing something!! ( less punctation less excitement sorry i cant) Feb 21 20:30:07 you can have a read on a popular "system administration" guide if you want to know how to use the command line Feb 21 20:30:48 ok i will thank you mawk, i just learned all the commands like touch, file, mv, rm, ipconfig and the coolest is connmanctl Feb 21 20:31:10 its so interesting but so hard as noob Feb 21 20:32:12 im in boys!! im back on cloud9 literally lol Feb 21 20:32:21 perfect Feb 21 20:32:34 mawk and zmatt thanks ever so much Feb 21 20:32:36 "ipconfig" ? you probably either mean "ip" or the old "ifconfig". "ipconfig" is a windows command Feb 21 20:32:57 yes sorry ifconfig, i pinged google ;) Feb 21 20:34:25 ok so i now have cloud9 back i am going to install the new robotics cape programs from github Feb 21 20:35:48 uhh, I'm pretty sure librobotcontrol is already installed by default Feb 21 20:37:28 it actually wasn't zmatt, for real. so i need to but it in through bash on cloud9 Feb 21 20:37:46 it is installed by default actually Feb 21 20:38:01 both librobotcontrol itself and examples (though not source code of the examples it seems) Feb 21 20:38:48 ok so where is it under the folders in cloud9, would it be in an examples one? Feb 21 20:39:05 cause ive used the "find" command and there isnt a folder with that name Feb 21 20:39:07 I don't know anything about cloud9, I've never used it Feb 21 20:39:27 i see ill open an ssh perhaps you can tell me from there where the files are? Feb 21 20:41:20 what files are you looking for exactly? the library itself is installed in the proper place so projects can use it (you don't need to access the files themselves normally), likewise for the programs (rc_*) which you should be able to execute Feb 21 20:41:34 there's also a project template in /usr/share/robotcontrol/rc_project_template Feb 21 20:42:27 note that official documentation is at http://strawsondesign.com/docs/librobotcontrol/manual.html Feb 21 20:44:14 since whatever tutorial you're following got you into a mess, I'm feeling a bit suspicious about it :P Feb 21 20:44:21 your right sorry i think i have old info from a "beaglebone black book for dummies" 2014 and youtube video 2017 Feb 21 20:44:28 oof Feb 21 20:44:35 that sounds like a recipe for disaster Feb 21 20:44:35 ha ha ha yes zmatt Feb 21 20:44:48 it was a youtube video by arrow Feb 21 20:45:04 any documentation from 2014 should be considered obsolete Feb 21 20:45:32 is there any beaglebone blue books you'd reccomend? Feb 21 20:49:10 no idea, sorry. I've never read any book about any embedded system Feb 21 20:49:17 (nor do I have a beaglebone blue) Feb 21 20:49:31 so how were you able to help?? Feb 21 20:50:06 because I'm familiar with debian systems in general and beaglebones in particular? Feb 21 20:50:31 but I mainly work with the beaglebone black (although I also have a beaglebone black wireless) Feb 21 20:51:06 gotcha i kinda wish i'd got the black now rather than the blue i wanted to build a robot but i think its gonna be way to hard Feb 21 20:51:36 well the blue will make things easier if you want to do robotics Feb 21 20:54:16 thats what i thought but i haven't even been able to really get anything working yet. thank you so much for your help i really appreciate it Feb 22 01:11:48 Heh? Feb 22 01:12:32 ? Feb 22 01:12:42 I am working w/ 4.19.24-bone-rt-r24 for arducopter/ardupilot stuff and now I cannot use echo. Feb 22 01:12:50 I tried to update my kernel and I did. Feb 22 01:13:03 "cannot use echo" ? Feb 22 01:13:32 zmatt: How should I go about using echo again for adding uart4 or the DSM2 port? Feb 22 01:13:48 echo 1 >/sys/class/gpio/gpio80/value? Feb 22 01:13:52 uhh, none of those involve echo Feb 22 01:13:54 Hey Feb 22 01:14:00 Oh. Feb 22 01:14:20 Sorry. For the header of the servos. Feb 22 01:14:30 if I remember correctly, that gpio was for the 6V power supply? and it needed to be exported first I think? Feb 22 01:14:39 not sure about that last part Feb 22 01:14:52 Right. How did you figure out that last part. Feb 22 01:15:06 I exported w/ echo and it did not stay. Feb 22 01:15:09 also I don't know if the -bone kernels are well supported on the blue, I remember that they had DT issues but I don't know if those have been fixed Feb 22 01:15:13 It went magically away. Feb 22 01:15:20 suffice to say, it does not get any real testing Feb 22 01:15:21 Okay. Feb 22 01:15:24 so I would advise against that combo Feb 22 01:15:28 Okay. Feb 22 01:15:30 So, ti? Feb 22 01:15:43 4.14-ti is the currently recommended series Feb 22 01:15:49 Okay. Feb 22 01:17:43 zmatt: Should my files get erased if I downgrade from 4.19 to 4.14-rt-ti? Feb 22 01:18:16 uh, no? Feb 22 01:18:24 switching kernel version just switches the kernel version Feb 22 01:18:47 That is what I thought but my .service files stopped working w/ the updated console image kernel update. Feb 22 01:18:54 the only process that can cause loss of data is reflashing Feb 22 01:19:01 Okay. Feb 22 01:19:03 Got it. Feb 22 01:19:07 "stopped working" and "get erased" are wholly different things Feb 22 01:19:43 Right but I was in a file and nothing was listed in it. Then, I got a dir. made w/ mkdir and the file contents appeared. Feb 22 01:19:46 It was really odd. Feb 22 01:19:54 ehmmm Feb 22 01:19:57 Yep. Feb 22 01:20:09 I'm just going to assume you made some sort of observational error there :P Feb 22 01:20:15 Okay. Feb 22 01:20:21 Maybe it was always just me. Feb 22 01:20:30 <<>> Feb 22 01:58:47 Okay. So, I went to ti.com and looked over their linux sdk. Feb 22 01:59:01 I found an SD Card image file. I will test it. Feb 22 01:59:08 what? why? Feb 22 01:59:22 I have no clue! I thought this is what you were talking about? Feb 22 01:59:23 fwiw, TI's sdk is not supported here Feb 22 01:59:27 no Feb 22 01:59:31 Oh. Feb 22 01:59:32 Okay. Feb 22 01:59:53 I could not downgrade to 4.14 from 4.19 for some reason. Feb 22 02:00:07 4.14-ti is the default kernel series on the debian images from beagleboard.org, i.e. the kernel you have unless you deliberately install a different one Feb 22 02:00:17 Oh. Feb 22 02:00:28 Okay. I will get that one again. Feb 22 02:01:54 /opt/scripts/tools/update_kernel.sh --ti-kernel --lts-4_14 Feb 22 02:02:13 I think that should fetch the latest kernel in the 4.14-ti series Feb 22 02:02:31 or you can use --ti-rt-kernel if you specifically need an RT kernel Feb 22 02:02:52 (but only use that if you really need it and are using software that specifically takes advantage of it) Feb 22 02:06:11 Okay. **** ENDING LOGGING AT Fri Feb 22 02:59:56 2019