**** BEGIN LOGGING AT Fri Jul 13 03:00:01 2018 Jul 13 03:02:13 I received a symlink at first but after daemon-reload, I have not received another symlink for systemctl enable. Jul 13 03:02:16 ... Jul 13 03:02:30 you only need to enable once Jul 13 03:02:41 Even after daemon-reload? Jul 13 03:02:57 yes? Jul 13 03:03:12 unless you change the [Install] section, in which case you may want to do systemctl reenable Jul 13 03:03:28 Okay. Jul 13 03:05:41 Out for the night. Nothing is working again. Boo! Jul 13 03:05:44 My fault. Jul 13 03:58:41 zmatt: If you are up and reading, here: those files, the .html and .js files, only work at times for some reason on port :8085. Jul 13 03:58:45 I cannot explain it yet. Jul 13 03:59:07 But...this is why my .service file probably is failing. It was not my fault, sort of. Jul 13 03:59:12 my guess would be it's because you did something wrong Jul 13 03:59:25 Yea. Jul 13 03:59:27 Probably. Jul 13 03:59:45 as before, keep an eye on logs using journalctl -f (exit with ctrl-C) Jul 13 04:00:02 then you can see whether your service is exiting and being restarted, or logging errors Jul 13 04:00:14 It is odd. The files run and then they do not run. Jul 13 04:01:21 journalctl -f and then exit w/ ctrl-c. Got it. Jul 13 04:02:50 Should I run my file, the .js file that calls the server up, and then add another terminal w/ the journalctl -f cmd? Jul 13 04:09:36 ehh, if you're running your server manually then obviously there's nothing of relevance in journal Jul 13 04:09:42 only when you start it as a service Jul 13 04:11:02 (although you should probably first get your server working *properly* when run manually and only then take the step of making it a service) Jul 13 04:11:05 okay. Jul 13 04:24:56 Yea...the server is odd. It works and then it does not work. I have no reasoning for it right now. Jul 13 04:25:16 <<< is going to keep plugging at it. Jul 13 04:25:33 Bon Voiage? Jul 13 04:25:35 Later. Jul 13 11:51:51 hello Jul 13 13:53:08 Bummer... Mu pocket beagle crashes my Laptop (bluescreen) and gets really hot... but otherwise works as expected... Jul 13 13:55:01 but this ONLY started after I tried USB network sharing on WIndows 7. Jul 13 13:59:09 If I disable network sharing... it runs cooler, no crashes... I'm stumped. Jul 13 16:22:21 helo Jul 13 19:03:00 So yesterday I came up with a problem of having unexpected I2C address when I connect my BBG with the eval board of adt7516 Jul 13 19:05:13 I've moved one step ahead now. According to the datasheet of eval board, the unexpected address that was shown up i.e. 0x51 is the address of another i2c part on the bus, a serial rom chip 24lc64 Jul 13 19:05:59 It can be seen here on the page 11 of the datasheet http://www.analog.com/media/en/technical-documentation/evaluation-documentation/512585584eval_adt7516eb.pdf Jul 13 19:07:26 But, I want adt7516 to be connected hence would like to have some help here Jul 13 19:35:57 shreeya: the schematic shows the i2c connection of the adt7516 goes through a mux controlled by the microcontroller on this board Jul 13 19:37:18 so you may want to read the docs of this eval board carefully to figure out how to get it to set that mux in a way that connects the adt to the i2c bus you can access Jul 13 19:40:06 btw, be very careful when interconnecting different boards with independent power supplies... the beaglebone will not appreciate it if its pins are being pulled to an external 3.3v when it's not powered, and the same is probably true for the components on this eval board. this may mean that the only safe thing to do is make sure both boards are powered on and their grounds are connected together ... Jul 13 19:40:12 ...before making any data connections Jul 13 19:41:33 Hmm yes, but I don't have much experience with this so will need some more help with the mux part Jul 13 19:42:18 it very much looks like this board wasn't designed to let you interface with the adt directly, instead it's just to play with it via the usb microcontroller using their software Jul 13 19:43:57 anyway, bbl, shopping Jul 13 19:44:15 For the connection part, I've just connected SDA and SCL, and as both the devices are connected through usb so there will be a common ground and hence have not connected that. Jul 13 19:47:34 zmatt: ok, will wait :) Thanks Jul 13 20:13:44 connecting both devices via usb to the same computer and then connecting them via i2c should indeed be safe, but I'd nevertheless recommend an explicit ground connection between the boards just for peace of mind. (also for signal integrity on the i2c line it's desirable to have a ground connection that runs more or less alongside the i2c wires) Jul 13 20:16:04 how are you connecting to i2c anyway? via the test points? I don't see any connector for i2c on the schematic (which is another clear indication that this board wasn't designed for what you're trying to use it for) Jul 13 20:17:04 For having I2C connection, I just connected SDA and SCL Jul 13 20:17:52 I hope this is the correct procedure Jul 13 20:17:57 you mean you soldered onto the testpoints? Jul 13 20:18:03 No Jul 13 20:18:07 unless I'm blind and overlooking a connector Jul 13 20:18:30 Just chopped the wire a bit and wrapped it around the pins Jul 13 20:18:43 ??? Jul 13 20:19:27 wirewrapping style Jul 13 20:19:37 ah they've mounted hooks on the testpoints Jul 13 20:19:52 https://www.google.co.in/url?sa=i&source=images&cd=&ved=2ahUKEwja24CP85zcAhXBbCsKHXfaCNAQjRx6BAgBEAU&url=https%3A%2F%2Felectronics.stackexchange.com%2Fquestions%2F383901%2Fconnecting-temperature-sensor-eval-board-adt7516-to-the-beaglebone-green%2F383915&psig=AOvVaw0G58PmEOyJGy-VB6R_djHm&ust=1531599559376977 Jul 13 20:19:54 for making it easy to connect a probe Jul 13 20:20:01 opps Jul 13 20:21:08 you can see the photo of the eval board on the above link Jul 13 20:22:51 my suggestion would be to ask on analog's EngineerZone forum whether it's possible to convince the on-board microcontroller to connect the adt to the i2c bus (via the mux) to enable such a connection to work Jul 13 20:25:11 alternatively you may be able to hold the microprocessor in reset and manually control the mux by connecting the control pin to ground or vdd (haven't checked which of the two is correct). this assumes the microcontroller's pins will be high-z when it's in reset, which is also something you'd need to check Jul 13 20:25:42 I did this Jul 13 20:26:08 ? Jul 13 20:26:43 according to the adt7516 datasheet, it's given there to connect control pin to ground or vdd Jul 13 20:27:09 I have no idea what you're saying Jul 13 20:29:42 http://www.analog.com/media/en/technical-documentation/data-sheets/ADT7516_7517_7519.pdf Jul 13 20:29:54 page 37 ^ Jul 13 20:30:50 ? what about it? Jul 13 20:31:40 it is showing to connect CS to vdd and DOUT/ADD to ground Jul 13 20:32:15 So I tried that but it didn't work Jul 13 20:33:43 they both have pull-ups on board, so you can simply leave them alone to get address 0x4b Jul 13 20:33:58 but that has nothing to do with what I just said Jul 13 20:35:08 Ok so I need to work with the mux part. Jul 13 20:36:36 Do I need to solder the wires? I don't think so that this can be a problem Jul 13 20:37:14 Yet if this is suggested then I'll do it Jul 13 20:38:28 I've given two suggestions above, neither of them was related to your wire connections Jul 13 20:38:39 I suggest actually reading what I said Jul 13 20:39:22 Yes I've read that. I'll study on it. Honestly, I don't know much about it so I'll have to study it first Jul 13 20:41:07 And also my mentor has the same suggestion. Thanks zmatt Jul 13 20:41:26 unless Analog has a software solution for your problem, you're going to have to solder onto pin 1 of U4 (the mux) and connect it to ground (after first making sure the microcontroller is held in reset, e.g. by bridging capacitor C15 by a solder blob) Jul 13 20:48:12 Ok, so first I'll ask on analog's EngineerZone forum and if that doesn't work well then will go with your second suggestion. Jul 14 01:49:34 e **** ENDING LOGGING AT Sat Jul 14 03:00:00 2018