**** BEGIN LOGGING AT Thu Aug 31 03:00:01 2017
Aug 31 10:49:49 <OscarJGV24> hello
Aug 31 10:49:52 <OscarJGV24> is anyone here?
Aug 31 10:50:24 <tbr> nope, 200 people, all an illusion
Aug 31 10:50:31 <OscarJGV24> first time here... sorry
Aug 31 10:50:46 <OscarJGV24> i just wanted to know if someone knows how to fix a problem i have on my beaglebone blue....
Aug 31 10:51:11 <OscarJGV24> i can't apt-get upate because it says port 443 refused connection...
Aug 31 10:51:24 <OscarJGV24> i also can't git clone anything...
Aug 31 10:51:29 <OscarJGV24> but i can ping google...
Aug 31 10:51:38 <tbr> how do you connect the board to the internet?
Aug 31 10:52:11 <OscarJGV24> through usb.. and then share thee internet connection of my computer using /sbin/route add defautl gw 192.168.7.1
Aug 31 10:52:52 <tbr> are you using a proxy to browse the internet on your computer?
Aug 31 10:53:02 <OscarJGV24> I am not sure. how can i check that?
Aug 31 10:53:18 <OscarJGV24> I am connected to eduroam heree in uk...
Aug 31 10:53:25 <tbr> usually that's in the browser settings
Aug 31 10:54:07 <OscarJGV24> ok hold on let me check
Aug 31 10:56:06 <OscarJGV24> well... the "use proxy server for your lan" box is not ticked
Aug 31 10:57:29 <OscarJGV24> i checked it in internet explorer... does it matter whether it is IE, chrome etc?
Aug 31 11:00:20 <OscarJGV24> this is what i get when i run apt-get update on my beaglebone blue...
Aug 31 11:00:21 <OscarJGV24>  root@beaglebone:/etc# apt-get update Ign https://deb.nodesource.com jessie InRelease Ign https://deb.nodesource.com jessie Release.gpg Ign https://deb.nodesource.com jessie Release Err https://deb.nodesource.com jessie/main armhf Packages  Err https://deb.nodesource.com jessie/main armhf Packages  Err https://deb.nodesource.com jessie/main armhf Packages  Err https://deb.nodesource.com jessie/main armhf Packages  Err https://deb
Aug 31 11:00:42 <OscarJGV24>  Err https://deb.nodesource.com jessie/main armhf Packages   Failed to connect to deb.nodesource.com port 443: Connection refused 22% [Connecting to deb.debian.org (172.1.8.1)] [Connecting to repos.rcn-ee.com (172.1.8.1)]^
Aug 31 11:02:13 <OscarJGV24> anyone?
Aug 31 11:05:44 <OscarJGV24> tbr? you there?
Aug 31 11:06:04 <tbr> sorry, had to step out
Aug 31 11:06:57 <tbr> I vaguely remember about https repositories being problematic sometimes
Aug 31 11:07:05 <tbr> make sure the date is set properly on the BBB
Aug 31 11:07:47 <OscarJGV24> could you tell me how to do that?
Aug 31 11:07:49 <tbr> also you could try this to get a better idea what's going wrong: curl -v https://deb.nodesource.com >/dev/null
Aug 31 11:08:16 <OscarJGV24> okok
Aug 31 11:09:57 <OscarJGV24> i typed this command for updating the date ntpdate -b -s -u pool.ntp.org
Aug 31 11:10:20 <OscarJGV24> but it tells me  bash: ntpdate: command not found
Aug 31 11:10:32 <tbr> if you just type in "date" what does it report?
Aug 31 11:10:48 <OscarJGV24>  Sun Apr  9 18:57:05 UTC 2017
Aug 31 11:10:56 <OscarJGV24> so... it is outdated...
Aug 31 11:11:00 <tbr> right, so that's a possible reason
Aug 31 11:11:18 <OscarJGV24> okok.. so you know any other command to update?
Aug 31 11:11:33 <tbr> try this:
Aug 31 11:11:40 <tbr> systemctl restart ntp.service
Aug 31 11:11:56 <OscarJGV24>  Failed to restart ntp.service: Unit ntp.service not found.
Aug 31 11:12:12 <OscarJGV24> i feeel something is very wrong with my board :(
Aug 31 11:12:22 <tbr> no idea what current images use for time sync
Aug 31 11:12:31 <tbr> nah, that's just software
Aug 31 11:12:50 <OscarJGV24> ok so you think the date might be the reason...
Aug 31 11:12:55 <OscarJGV24> let me see if i can find other commands
Aug 31 11:13:10 <tbr> you can just set the date manually
Aug 31 11:13:23 <OscarJGV24> oh... how?
Aug 31 11:14:40 <tbr> date -s 1504178058
Aug 31 11:14:41 <OscarJGV24> i found it
Aug 31 11:15:20 <tbr> you can obtain the unix timestamp by using "date +%s" on another machine
Aug 31 11:16:58 <OscarJGV24> does the other machin have to be runing linux?
Aug 31 11:17:24 <tbr> for just a ballpark, use the above number
Aug 31 11:17:37 <tbr> you don't need second accuracy, all you need is the correct date
Aug 31 11:17:54 <OscarJGV24>  root@beaglebone:~# date -s 1504178058 date: invalid date ‘1504178058’
Aug 31 11:19:03 <tbr> meh, date syntax is so inconsistent across implementations
Aug 31 11:19:06 <OscarJGV24>  apt-get install ntp Reading package lists... Done Building dependency tree        Reading state information... Done E: Unable to locate package ntp
Aug 31 11:19:16 <tbr> probably "ntpd"
Aug 31 11:19:43 <OscarJGV24> no.. still doeesnt find it
Aug 31 11:19:49 <ogra_> ntpdate is easier to use
Aug 31 11:20:05 <ogra_> "apt install ntpdate"
Aug 31 11:20:08 <tbr> but deprecated for a long while now
Aug 31 11:20:09 <OscarJGV24>  root@beaglebone:/# ntpdate bash: ntpdate: command not found
Aug 31 11:20:17 <ogra_> then just call ntpdate
Aug 31 11:20:25 <OscarJGV24>  root@beaglebone:/# apt install ntpdate Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package ntpdate
Aug 31 11:20:40 <OscarJGV24> not found
Aug 31 11:20:57 <OscarJGV24> im gonna set it manually
Aug 31 11:21:45 <ogra_> weird, it is definitely available in all deian releases
Aug 31 11:21:49 <ogra_> *debian
Aug 31 11:22:06 <OscarJGV24> yeah like i said.. i think something is wrong with my board :(
Aug 31 11:22:15 <OscarJGV24> so ok i have correct date now..
Aug 31 11:22:17 <ogra_> did you call apt update (ntpd should have been found too, smells like your package database is out of date)
Aug 31 11:23:00 <OscarJGV24> the problem is that i cant update it
Aug 31 11:23:13 <OscarJGV24> because there is a problem with port 443
Aug 31 11:23:18 <OscarJGV24> do you know anythign about it?
Aug 31 11:23:34 <OscarJGV24> look...
Aug 31 11:23:34 <tbr> still? despite setting date?
Aug 31 11:23:55 <tbr> disable the nodejs repositories, as those are using https
Aug 31 11:24:52 <OscarJGV24> interesting... now it hangs on 22% of the update... exactly where it used to give me the eerror
Aug 31 11:25:22 <OscarJGV24> nvm
Aug 31 11:25:24 <OscarJGV24> is back again
Aug 31 11:25:39 <OscarJGV24> here is the error ogra...
Aug 31 11:25:40 <OscarJGV24>  root@beaglebone:~# apt-get update Ign https://deb.nodesource.com jessie InRelease Ign https://deb.nodesource.com jessie Release.gpg                                          Ign https://deb.nodesource.com jessie Release                                               Err https://deb.nodesource.com jessie/main armhf Packages                                      Err https://deb.nodesource.com jessie/main armhf Packages               
Aug 31 11:25:50 <OscarJGV24>  Err https://deb.nodesource.com jessie/main armhf Packages                                     Failed to connect to deb.nodesource.com port 443: Connection refused
Aug 31 11:25:55 <tbr> 11:23:55< tbr> disable the nodejs repositories, as those are using https
Aug 31 11:26:05 <OscarJGV24> mmm how to do that?
Aug 31 11:26:09 <OscarJGV24> sorry... im very new to linux
Aug 31 11:26:55 <OscarJGV24> ok found it
Aug 31 11:26:58 <ogra_> they should be in /etc/apt/sources.list ... edit the file
Aug 31 11:28:35 <OscarJGV24> i just run sudo apt-get remove nodejs
Aug 31 11:28:42 <OscarJGV24> cloud9 stopped...
Aug 31 11:28:50 <OscarJGV24> hopefully i can get it back online later.
Aug 31 11:28:58 <ogra_> that wont help at all
Aug 31 11:29:43 <OscarJGV24> ok mb... i guess i messed that one
Aug 31 11:29:44 <OscarJGV24> :P
Aug 31 11:31:01 <OscarJGV24> what am i looking for ogra?
Aug 31 11:31:14 <OscarJGV24> i am reading the sources.list
Aug 31 11:31:28 <ogra_> well, the hosts that produce the error ...
Aug 31 11:31:55 <ogra_> add a "#" sign at the from of the line for all of them
Aug 31 11:32:02 <ogra_> *front
Aug 31 11:32:14 <ogra_> save the file... run apt update again
Aug 31 11:33:30 <OscarJGV24> okok...
Aug 31 11:38:02 <OscarJGV24> sorry im having trouble modifying the file
Aug 31 11:38:10 <OscarJGV24> should i do it with vi?
Aug 31 11:38:18 <OscarJGV24> like i said.. im very very new
Aug 31 11:43:17 <OscarJGV24> ok done
Aug 31 11:43:18 <OscarJGV24> i used nano
Aug 31 11:43:36 <OscarJGV24> i comment all the sources...
Aug 31 11:44:43 <ogra_> well, all nodesource lines ... you still want the debian ones
Aug 31 11:47:47 <OscarJGV24> ah ok... then there weree no nodesoruce lines
Aug 31 11:47:50 <OscarJGV24> online debian ones
Aug 31 11:49:58 <OscarJGV24> it is still giving me eerrors while updating...
Aug 31 11:50:23 <OscarJGV24>  Err https://deb.nodesource.com jessie/main armhf Packages
Aug 31 11:53:16 <OscarJGV24> again.. same error...    Failed to connect to deb.nodesource.com port 443: Connection refused
Aug 31 11:53:54 <OscarJGV24> hold on
Aug 31 11:55:30 <OscarJGV24> im confused.
Aug 31 12:00:00 <OscarJGV24> if iremove nodesource, it freeezes.
Aug 31 12:00:11 <OscarJGV24> doesnt doanythign
Aug 31 12:00:52 <tbr> node is most likely in /etc/apt/sources.list.d/
Aug 31 12:02:12 <OscarJGV24> empty
Aug 31 12:04:14 <OscarJGV24> im thinking about flashing this thing again...
Aug 31 12:04:28 <OscarJGV24> this is nonsense
Aug 31 12:04:56 <OscarJGV24> all night trying to find how to solve this port nonsense and nothing
Aug 31 12:05:04 <OscarJGV24> cant update
Aug 31 12:05:08 <OscarJGV24> can git..
Aug 31 12:05:09 <OscarJGV24> i mean
Aug 31 13:43:20 <zarzar> should i be using the termios api to change config of uart1? i.e. tcgetattr, cfsetospeed, cfsetispeed
Aug 31 13:43:38 <alfatau> Hi all. I've 2 newly purchased BBBs, where the only apparent difference the package size. Now I've an auto-flasher micro-sd with my customized OS and for the first one the auto-flash process ends like a charm; for the second one (with smaller package) it seem impossible to mount the internal eMMC: this is the error: "g_multi: `' invalid for paramet
Aug 31 13:43:38 <alfatau> er `/dev/mmcblk0p1'" . Can you help me?
Aug 31 15:14:18 <zarzar> is spidev the best way to get SPI working on BBB? is there a more generic linux SPI method?
Aug 31 15:33:31 <zarzar> looks like SPI0 is set up by default in newer BBB images, pins setup, is that correct?
Aug 31 15:52:54 <zarzar> anyone available for help with SPI0 on BBB? no output on pins, pin config looks correct, I don't see spidev0.0 in dev like i expected, only 1.0,1.1,2.0,2.1
Aug 31 15:53:20 <zarzar> not necessarily SPI0, but any SPI
Aug 31 15:57:21 <zarzar> pin config was wrong even though it showed up as spi: P9.18 / spi boot out              86 fast rx  up  7 gpio 0.04 << hi  P9_18 (pinmux_P9_18_default_pin) P9.21 / spi boot in               85 fast rx  up  7 gpio 0.03 << hi  P9_21 (pinmux_P9_21_default_pin)
Aug 31 15:57:37 <zarzar> i guess that does not mean spi, even though it mentions spi
Aug 31 16:00:03 <zarzar> is it possible to save the pin config and apply as part of mcu init? part of init?
Aug 31 17:14:00 <zmatt> zarzar: whoa, lot of questions... let's see...
Aug 31 17:16:11 <zmatt> more generic than spidev ? you can do everything with spidev
Aug 31 17:17:24 <zmatt> spi devs set up by default?  that sounds odd to me, but it's possible
Aug 31 17:18:15 <zmatt> please don't paste multi-line text here, it becomes an awful mess.  use a website like pastebin.com
Aug 31 17:19:55 <zmatt> the first column in the show-pins output is just a label intended to highlight that the pins may have a special purpose under certain conditions, see https://github.com/mvduin/bbb-pin-utils#description
Aug 31 17:20:26 <zmatt> it doesn't mean the pin is configured for spi... in fact the paste shows that they are configured to gpio
Aug 31 17:23:00 <zmatt> and one way to get pins configured automatically during very early boot is by making a custom device tree file
Aug 31 17:23:33 <zmatt> anyway, afk again
Aug 31 17:33:33 <zarzar> zmatt i solved the others except for saving pin config for uart and spi, don;t want to have to reapply after reboot, maybe i will just add to application init code
Aug 31 20:09:35 <zarzar> what's a generic linux way to control with digital gpio? /sys/class/gpio export?
Aug 31 20:41:34 <mturquette> jkridner:
Aug 31 20:42:27 <mturquette> For BBB layout gurus, is the BBB reference design using an HDI PCB?
Aug 31 20:44:07 <mturquette> I've just been quoted that a BBB-based board using an eMMC part with 0.5mm pitch will force a high density board, which I found surprising. Any advice?
Aug 31 20:48:38 <zarzar> anyone know how to get around the permission denied issue when controlling gpio through sys/class/gpio export? i am connected by ssh, not sure how to run a terminal via sudo viqa ssh
Aug 31 20:54:41 <majuk> zarzar: 'sudo su' will drop you into root's bash prompt
Aug 31 20:54:51 <majuk> Not sure if that's what you're looking for exactly.
Aug 31 21:11:49 <zarzar> zmatt via ssh?
Aug 31 21:12:14 <zarzar> cool, thanks again zmatt
Aug 31 21:14:42 <zarzar> i mean majuk
Aug 31 21:15:08 <majuk> np
Aug 31 21:17:30 <zarzar> i still get permission errors when trying to echo > sys gpio "files"
Aug 31 21:17:45 <zarzar> ^shorthand
Aug 31 21:18:13 <zarzar> c program is working though, so that is good enough\
**** ENDING LOGGING AT Fri Sep 01 03:00:00 2017