**** BEGIN LOGGING AT Mon May 28 03:00:03 2018 May 28 03:31:44 hi May 28 03:31:58 has beaglebone black stopped production? May 28 03:32:04 sounds unlikely May 28 03:33:08 couldn't get it at element14 May 28 03:33:22 china site says the production has stopped for 1 month + May 28 03:34:36 element14 says 7000+ units are available for delivery on 23-jun-2018 May 28 03:35:18 looks like a production hiccup (maybe waiting for some components?), I'd hardly call it "stopped production" May 28 03:35:43 i see May 28 03:35:45 thanks May 28 03:35:49 jkridner[m]: you know anything about this? May 28 03:35:53 so i will have to wait for a month then May 28 03:37:05 or hunt for a distributor that still has stock May 28 03:39:01 google yielded https://www.kiwi-electronics.nl/beaglebone-black-rev-c and https://www.antratek.nl/beaglebone-black-revc both of which have stock. presumably you'll get results closer to you if you search yourself May 28 03:45:41 thanks guys May 28 03:45:47 or gals... May 28 04:04:47 Good evening! I'm a newbie with BBB. I installed the latest Debian image and used the following commands: May 28 04:04:49 sudo apt-get update May 28 04:05:02 sudo apt-get install gdbserver May 28 04:05:13 sudo apt-get upgrade May 28 04:05:47 But... whenever I try to debug my (very simple) C++ code, I get: May 28 04:05:51 ERROR while launching the debugger: "gdbserver" is not installed May 28 04:06:01 Anyone have any ideas? May 28 04:06:17 what is producing that error? May 28 04:06:25 e May 28 04:06:30 and I'm assuming the apt-get install gdbserver completed successfully? May 28 04:08:52 yes, the updates all looked good. Thx May 28 04:09:15 the error happens whenever I try to debug my code (using Cloud9) May 28 04:09:43 I did get the debugger working in python... May 28 04:09:45 oh, I've never used cloud9 May 28 04:10:39 I don't have to use cloud9... anything will do really as long as I can debug it. I've also been trying Eclipse but have had even more issues with that. May 28 04:10:53 (figured I would start on the easy problem) May 28 04:12:34 remote debugging using gdbserver should work of course, but I have no idea how to set that up in the IDE of your choice. I generally just use gdb directly on the beaglebone May 28 04:14:18 (tip: use ctrl-X + A to enable split view in gdb, ctrl-X + O to toggle focus between the source window and the command window) May 28 04:15:10 I'm not really finding any relevant google hits on your problem, so for some reason it seems to be an uncommon one May 28 04:16:18 yeah, I've been googling it for the last two days. May 28 04:28:32 OK, dumb question... where can I find gdb on the BBB? I can at least try debugging it that way. May 28 04:28:37 I tried gdb the other day. May 28 04:29:05 MattBradley: what do you mean "where can I find gdb" ? assuming it's installed you can simply invoke it as a command May 28 04:29:56 that's what I figured... I started a terminal window and typed "gdb" ... it said command not found. May 28 04:30:05 sudo apt-get install gdb May 28 04:30:32 hmmmm... that may be the root of the problem. May 28 04:31:29 I'll try it in a minute... but I will lose this internet connection when I do. So I may not be back right away. Thanks for all your help. May 28 04:36:54 That was it! Thank you so much! May 28 08:25:01 does anyone know why in kernel 4.14 vim is super slow? May 28 08:25:16 scrolling is super annoying cause it has such a lag May 28 08:32:46 hmm? haven't noticed such a thing myself May 28 08:35:10 ohh, can you check: grep CONFIG_PREEMPT /boot/config-$(uname -r) May 28 08:38:36 https://pastebin.com/mc8WGZLN May 28 08:39:19 hm okay, so that's not the problem (iirc it was set to CONFIG_PREEMPT_VOLUNTARY for a while for some reason) May 28 08:39:32 oh May 28 08:41:39 things you could try: 1. check with cpufreq-info whether the "performance" governor is used 2. see if using a -bone kernel instead of a -ti kernel makes a difference May 28 08:42:54 it's specifically the 4.14 kernel that's causing the problem? i.e. downgrading to the latest 4.9-ti kernel fixes the issue? May 28 08:44:50 (or conversely the issue only started after switching to a 4.14 kernel) May 28 08:54:07 yes specifically 4.14 May 28 08:54:16 and downgrading to 4.9 does fix the issue May 28 08:56:57 zmatt: this is the result of cpufreq-info https://pastebin.com/t9CKhmd3 May 28 09:09:58 then trying a 4.14-bone kernel might still be worth a try, and otherwise ¯\_(ツ)_/¯ May 28 09:10:09 like I said I haven't noticed it, but I'm using a customized 4.14-bone kernel May 28 09:10:37 this is a compiled 4.14 kernel, but I have it on the standard -ti one too May 28 09:14:40 I found the problem, it appears its one of my vim plugins thats slowing it down May 28 09:18:51 seems like vundle is the culprid May 28 09:18:53 culprit May 28 09:32:10 its the 'syntax on' that kills it May 28 09:32:17 with my plugins, vundle or not May 28 10:12:40 well I obviously use syntax highlighting, and like I said I haven't noticed any particular slowdown May 28 10:12:43 and I use vim a lot May 28 10:14:08 hi, I'm trying to use a JTAG debugger for the first time with the beagleboard-x15 and Code Composer Studio. When I try to connect I get an error: "Device is held in reset. Take the device out of reset, and retry the operation." May 28 10:14:51 how do I take my device out of reset? May 28 10:15:18 Or does anyone have any pointers as to what is going wrong? May 28 10:18:28 lttxo: I can't say for sure what is wrong or how to fix it, but take messages from CCS with a grain of salt. typically what it claims is the problem isn't, and its suggestions to fix the problem won't May 28 10:23:17 zmatt, ok. I will try to figure out what is going wrong. May 28 10:43:59 how can I prevent the beagleboard-x15 from booting from the internal memory? May 28 10:51:48 hold P3 May 28 10:51:50 on powerup May 28 10:51:52 (iirc) May 28 11:05:54 ahh, an issue of linux disabling the debugss clocks May 28 11:06:30 I thought icepick could override that, but maybe that doesn't work May 28 11:20:53 good day to all. May 28 11:23:05 no, it's too warm May 28 11:23:16 too warm indeed May 28 11:34:33 i'm having an issue with my beaglebone black. if I run "i2cdetect -r 2" command without any device connected to it shows the complete map of addresses but as soon as I can the I2c device to it it just freezees on the second line of that address map. Can anybody assist? May 28 11:36:42 in general, i2cdetect should not be used. to quote its manpage, "WARNING This program can confuse your I2C bus, cause data loss and worse!" May 28 11:37:00 however, my guess would be that your problem actually ca May 28 11:37:09 however, my guess would be that your problem actually may actually be caused by lack of pull-ups May 28 11:38:02 what errors are shown in the kernel log? May 28 11:38:27 pull-ips resistors on the SDA and SCL lines? May 28 11:38:40 yes May 28 11:39:46 if those are present and the problem nonetheless persists, then it's back to "i2cdetect should not be used" :) May 28 11:45:21 Zmatt this is what happening -> https://photos.app.goo.gl/DYA4Pa7ySyA4CGMk1 May 28 11:45:56 yes that's what you said already May 28 11:47:15 ok will try to add pull ups and see what i get May 28 12:16:59 Zmatt: Thanks, the pull p resistors have eliminate the freezing problems but the device is still not detected (shown) on the address map. Any Idea? I'm fairly new with this... May 28 12:19:42 I'm interfacing the beaglebone black with the kionix Kx022 magnetometer May 28 12:30:17 don't use i2cdetect May 28 12:30:32 send correct i2c transactions for the device, based on its datasheet May 28 12:30:37 i2c is not a discoverable bus May 28 12:36:06 zmatt: especially not when routed through inner layers! May 28 12:36:16 ? May 28 12:36:33 oh argh -.- May 28 12:36:43 * zmatt slaps LetoThe2nd with a fish May 28 12:37:59 big tasty fish? May 28 12:39:15 Aryan: try i2c -y 2 0x1f 0x0f b May 28 12:39:51 Aryan: or possibly 0x1e instead of 0x1f depending on whether the address pas is connected to vdd or vss May 28 12:40:17 i2cget May 28 12:40:18 sorry May 28 12:40:26 ok May 28 12:40:36 i connected to vss May 28 12:40:49 0x1e then May 28 12:41:08 i2cget -y 2 0x1e 0x0f b reads byte-register 0x0f of slave device 0x1e on bus 2 May 28 12:48:27 success? no success? May 28 13:08:58 Zmatt: Error: Read failed, that's the message i"m getting. Just to make sure: to use I2C_2; SCL is connecteed to P9_19 and SDA to P9_20 right? May 28 13:11:30 yes May 28 13:11:39 any messages in the kernel log? May 28 13:16:22 Zmattt: I'm log in the beaglebone black via my windows pc through Putty (ssh). So not to sure of how to check the Kernel log May 28 13:19:13 dmesg May 28 13:19:41 (or if it refuses access use sudo dmesg ) May 28 13:37:44 Zmatt: Everythin in red are the errors right? https://photos.app.goo.gl/owkR1CrGRTLrcD1K3 May 28 13:45:04 none of this is relevant. any i2c errors would obviously be all the way at the end May 28 13:59:56 Zmatt: https://photos.app.goo.gl/owkR1CrGRTLrcD1K3 May 28 14:01:18 Zmatt: the end shows the same message over and over : timeout waiting for bus ready May 28 14:07:46 that indicates the bus is being messed up somehow, e.g. due to something pulling sda or scl to ground May 28 14:09:53 btw, if you've been connecting stuff while the system is powered, don't. the resulting glitches can easily confuse the total heck out of i2c devices. power the system down, then connect, then power up May 28 14:17:47 Zmat: that what i did. May 28 14:17:57 ok, was just making sure May 28 14:23:37 ok May 28 14:24:08 Zmatt: thanks for the help. any other idea maybe? May 28 14:32:47 I can't remotely diagnose your hardware setup May 28 14:39:09 ok May 28 15:38:06 zmatt: would you please tell me where you are getting 0x0f included in this command "i2cget -y 2 0x1e 0x0f b"? May 28 16:12:17 it's one of the registers listed in the datasheet May 28 22:48:19 Are there any translations of digitalRead() and digitalWrite() into Python? May 28 22:55:10 hi can anyone tell me if it's alright to use the GUI image with the pocketbeagle? this step instructs use of the IOT image only: https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual#figure-6-download-latest-software-image May 29 02:29:15 pocketbeagler: why would you want to? it has no video output **** ENDING LOGGING AT Tue May 29 03:00:04 2018