**** BEGIN LOGGING AT Sun Mar 04 03:00:02 2018 Mar 04 03:00:18 either 'Device' is not defined or I get an IO error. Either way...no go. I will keep testing software. Mar 04 03:04:55 Maybe something is mounted incorrectly? Mar 04 03:18:11 Okay... Mar 04 03:18:25 So, line 274 in PureIO...right? Mar 04 03:18:54 How can I get this fellow to address line 274 (self._device.write Mar 04 03:19:07 (data) Mar 04 03:19:39 How can I get this fellow to address line 274, which is, self._device.write(data) Mar 04 03:20:06 I think this is the issue. I would like to goof around but I do not know this fellow yet. Oops! Mar 04 03:25:16 ... Mar 04 03:27:21 I am off to look up line 281 & 223 in the MotorBridgeCape library and line 129 in Adafruit_GPIO/I2C.py. Mar 04 03:27:22 ... Mar 04 03:27:34 and line 274 in Adafruit_PureIO/smbus.py. Mar 04 03:27:38 ... Mar 04 03:27:43 That is all my errors so far. Mar 04 03:28:18 ... Mar 04 03:28:19 Aw! Mar 04 03:37:34 Okay... Mar 04 03:42:46 is there too much info. for us to put a sys/ioctl.h file on our BBB/BBG? Mar 04 03:53:29 I checked Torvalds/Linux page and found that he or someone is working on i2c stuff now. Maybe this is what is happening? Mar 04 03:53:30 ... Mar 04 04:01:33 Too much to read...too little brain. BBB! Mar 04 04:12:25 When I look up i2c.h, I find https://www.google.com/search?q=i2c.h&sitesearch=man7.org%2Flinux%2Fman-pages&sa=Search+online+pages. Mar 04 04:12:26 ... Mar 04 04:19:08 https://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/529240 shows a solution for i2c stuff. Work w/ a brother! Mar 04 04:36:49 ... Mar 04 04:37:13 Why is i2c-1 and i2c-2 in /dev not a normal file? Mar 04 04:37:39 Why is i2c-1 and i2c-2 in /dev not normal files? Mar 04 08:10:42 because an i2c bus isn't a file? Mar 04 08:11:17 in fact, in /dev you'll mostly find... *surprise* devices! Mar 04 08:26:04 Aw! Mar 04 08:41:37 I just remembered something. I think the MotorBridgeCapeFirmware that needs to flash w/ make flash has a file called: /MotorBridgeCapeFirmware/script/flasher. Mar 04 08:41:38 ... Mar 04 08:42:08 This file must be changed to suit the needs of the current configuration of the BBB/BBG. Mar 04 08:42:12 I am pretty sure. Mar 04 08:45:41 that sounds highly implausible Mar 04 08:46:35 You are probably right. I am trying to remember how I got the darn thing working last time. Mar 04 08:46:37 ... Mar 04 08:46:48 I changed a bunch of stuff w/ the system to make it once work. Mar 04 20:57:17 hi guys Mar 04 20:58:21 i have a question that could not answer myself by searching the web Mar 04 20:58:34 i need to enable PRU on a BBB Mar 04 20:58:44 and here is what i have Mar 04 20:58:45 sudo config-pin P8_45 pruout P8_45 pinmux file not found! bash: /sys/devices/platform/ocp/ocp*P8_45_pinmux/state: No such file or directory Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P8_45_pinmux/state Mar 04 20:59:12 device-tree-override:[dtb=am335x-boneblack-overlay.dtb ] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[disable_uboot_overlay_audio=1] uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo] uboot_overlay_options:[enable_uboot_cape_universal=1] Mar 04 21:00:30 as of my conclusion this PRU is like an Achile's heel Mar 04 21:01:11 such a nice feature with such lack of info. on how to set it up Mar 04 21:38:25 hi i need help to reset my beagleboard password temporary password doesnot work Mar 04 21:38:54 write a blog post or wiki page Mar 04 21:39:03 on pru Mar 04 21:39:05 i tried but Mar 04 21:39:14 i have debian linux Mar 04 21:39:17 cosscat ^ Mar 04 21:39:34 can u tell me commands to reset beagleboard passrord Mar 04 21:39:38 passwd Mar 04 21:40:04 i go as a super user using sudo -s command Mar 04 21:40:37 after i connect my board to computer a command passwrd debian Mar 04 21:40:46 but its not working Mar 04 21:40:48 what password are you trying to set? for what user? Mar 04 21:41:25 when i connect my board to laptop using ssh command then tmppwd is not working Mar 04 21:41:39 i waanna enter into my board Mar 04 21:42:16 ssh 192.168.7.2 Mar 04 21:42:40 then ask me for password but temppwd isn't working Mar 04 21:42:52 did you try just using the button return/enter? Mar 04 21:43:12 yes Mar 04 21:43:17 Damn...okay. Mar 04 21:43:25 g Mar 04 21:43:42 passwd usually works. Try a new image. Mar 04 21:43:58 bbb.io/latest-images? Mar 04 21:57:57 Here is a pastebin paste. See here: https://pastebin.com/zV4Pf8NZ. This is a paste from info. about my BBGW and the Motor Bridge Cape while in working order. Mar 04 21:57:58 ... Mar 04 21:58:08 ... Mar 04 21:58:40 Now...I am going to cross reference this BBGW w/ the BBG w/ separate info. Please hold. Mar 04 22:00:32 zmatt: If you get this message, I am finishing the deal we made. I said I would see the different configurations on my separate boards to see what is different. Mar 04 22:00:33 ... Mar 04 22:00:38 So, here goes nothing. Mar 04 22:09:31 https://pastebin.com/95ntRftF is the BBG paste w/ current info. but the cape does not work. I am off to cross reference now. Mar 04 22:09:34 ... Mar 04 22:12:20 I see something. Yes...I see it now. It is the i2c addresses not being at 4819c000, i.e. i2c@4819c000. This may be it. Mar 04 22:12:31 I will look up now on how to change this factoid. Mar 04 22:25:21 I see in my uEnv.txt file that there is enable_uboot_cape_universal=1. Should this be enabled? Or should I disabled it? Mar 04 22:29:43 bien_salad: That is a bit of DT overlay that allows using "config-pin" to configure pins. Not sure what you need, though. Mar 04 22:30:20 bien_salad: It is automatically disabled if any overlays for capes are loaded (because they are autodetected, or you specify an explicit overlay in uEnv.txt) Mar 04 22:31:44 Oh. Mar 04 22:33:32 blathijs: did you look at my pastebin.com pastes? Mar 04 22:35:32 blathijs: I need to set my i2c address at 4819c000, e.g. i2c@4819c000 instead of ocp/P9_19_pinmux. Mar 04 22:35:54 bien_salad: Just now, but I'm not sure what they should show. Mar 04 22:36:07 The BBGW is the one that works. Mar 04 22:36:17 i2c@4819c000 indicates the address of the I2c controller, IIRC this is i2c2 Mar 04 22:36:44 The BBG setup does not work. Mar 04 22:36:44 Oh. Mar 04 22:37:10 And i2c2 is enabled by default, no overlays needed Mar 04 22:37:17 I need to make my BBG setup show i2c2 like you stated instead of ocp/... Mar 04 22:37:18 Oh. Mar 04 22:38:27 I guess I can make that file renamed to what i need. Off to test that... Mar 04 22:38:32 bien_salad: I think there was a change in the base devicetree recently, that lets the I2C2 pins be claimed by ocp/P9_20_pinmux / ocp/P9_19_pinmux instead of i2c2, but they are still configured for i2c2 by default. Mar 04 22:38:46 Oh. Mar 04 22:39:16 bien_salad: So perhaps you're just running different kernel / image versions on both boards and the difference you're seeing now is not the cause of your issue. Mar 04 22:39:35 That could very well be but I am still clueless. Mar 04 22:39:50 That is the only difference so far from what I can tell. Mar 04 22:40:55 I can't really tell what you're doing and what you're actually issue is from what you've said. You seem to say a lot, without really making clear what is going on... Mar 04 22:41:06 ... Mar 04 22:41:08 Oh... Mar 04 22:41:09 In any case, I'm off for the night, so I wish you good luck1 Mar 04 22:41:15 I am using the Motor...damn. Okay. Mar 04 22:41:21 Thank you. Mar 04 22:41:36 Chat w/ you later. Mar 04 22:42:22 <<<< smoking Mar 05 01:18:05 hello Mar 05 01:19:25 for some reason my updates fail for my beaglebone black when doing the initial setup. Also, the beaglebone doesnt recognize my internal hard drive i have plugged in through a usb-sata adapter (the raspberry pi does). Could someone please help me? Mar 05 01:19:55 not sure what you mean by "updates fail" or "initial setup", can you pastebin an error log? Mar 05 01:20:09 For the hard drive, try adding a powered hub. **** ENDING LOGGING AT Mon Mar 05 03:00:03 2018