**** BEGIN LOGGING AT Sat Jul 08 03:00:01 2017 Jul 08 05:00:06 Hello Jul 08 05:00:28 Hey Jul 08 05:00:29 I am facing usb ssh issues with BBG Jul 08 05:00:56 I am running Debian 8.7 IoT on BBG Jul 08 05:01:16 you're connecting to 192.168.7.3? Jul 08 05:01:18 and my host PC is running windows 7 (64 bit) Jul 08 05:01:38 whoops Jul 08 05:01:44 192.168.7.2 ** Jul 08 05:01:55 I am not getting 192.168.7.1 for BBG under windows Jul 08 05:02:09 Yes 192.168.7.2 Jul 08 05:02:45 do `ssh -v root@192.168.7.2` Jul 08 05:02:57 IP allocated to BBG under windows is 169.254.133.251 Jul 08 05:03:24 This means not allocated Jul 08 05:04:25 ssh -v root@192.168.7.2 in windows command line ? Jul 08 05:05:14 hmm, maybe try. if not look for "verbose" option in putty Jul 08 06:22:10 hey, anyone have any experience coupling a beaglebone to a RAID controller? Jul 08 06:23:49 I wanna get one for a media server, but I wanna do a RAID 5 or 6 so I can deal with a crash but still have plenty of room to expand into Jul 08 06:30:03 I know you guys are busy, but googling isn't turning up anything Jul 08 06:32:40 usb3.0 should have plenty of bandwidth to pull it off, and I was hoping that a separate RAID controller could talk to the beaglebone rather than having to host the RAID myself (like with freeNAS and the like) Jul 08 06:33:32 (host the RAID directly, not myself *typo*) Jul 08 06:53:47 hi, what is the correct way to read analog input from python? I have followed this guide but I get an error when trying to initialise the ADC: http://www.toptechboy.com/tutorial/beaglebone-black-lesson-9-reading-analog-inputs-from-python/ Jul 08 06:54:34 the error is: https://pastebin.com/raw/38S8bRhM Jul 08 07:00:29 never mind, this thread helped me: https://stackoverflow.com/q/33791856/12149 Jul 08 07:15:26 spuz: adafruit_BBIO is not exactly a well-written library Jul 08 07:17:49 I think you can read ADC values simpler and probably more efficient with just a few lines of python code Jul 08 07:19:12 it just opens and reads /sys/bus/iio/devices/iio:device0/in_voltage%d_raw (replace %d by the adc channel) Jul 08 07:19:32 very elegant how they hardcoded the iio:device0 :P Jul 08 07:20:58 so if one day you decide to connect some sensor to your bbb that's supported by an iio driver, Adafruit_BBIO's adc code might suddenly fail Jul 08 07:23:48 I think the adafruit drive is essential deprecated Jul 08 07:23:54 they're certainly not developing it actively Jul 08 07:24:05 pretty sure their focus is on other platforms Jul 08 07:24:08 mostly, their own ... Jul 08 07:24:30 although, I'm sure if you filed a PR, limor would get to it .. Jul 08 07:24:41 or whoever wrote it Jul 08 07:26:28 a PR would require me caring remotely Jul 08 07:27:15 also, it seems I just found a bizarre bug in IEP Jul 08 07:28:20 bit 23 of some 24-bit counter register always reads as zero, even though you can write a 24-bit value just fine. only readback is broken, and only of bit 23 Jul 08 07:32:00 https://pastebin.com/raw/32R668qR Jul 08 13:15:38 huh, ok... if pull input 0 of pru 0 or 1 high, you start to get periodic irqs belonging to the shift-in mode... even if shift-in mode isn't enabled Jul 08 13:15:44 *if you Jul 08 16:23:40 the pru interrupt controller is kinda interesting... it can trigger on high/low level and rising/falling edge of the irq lines it receives Jul 08 16:24:12 so you can actually detect when a peripheral *deasserts* its irq line :) Jul 08 17:30:10 hello Jul 08 17:30:30 I am using a BeagleBone Black Wireless and cannot connect to the device anymore. I was able to initially and was going through some tutorials but then it just stopped working. I am using Windows 7 and I have the drivers installed. When I type in http://192.168.7.2/ in Chrome it does not connect anymore. It also does not connect through Putty SSH anymore either. Could anybody please help me? Jul 08 18:49:23 Hello, I am trying to connect the robotics cape/beaglebone blue based edumip to labview. Does anyone know how to connect the board and labview? Jul 08 19:04:18 what's the best workflow to develop on BB from an iOS device? Jul 08 19:58:50 Hi All , I'm using gitHub/bb-kernel to build the BBB kernel, but i've noticed that it doesnt take the latest kernel , anyone have any idea why? Jul 08 20:13:37 can BBB linux can work with Sitara AM3352 (it doesn't have PRU) Jul 08 20:18:11 cyberguy: which branch of bb-kernel ? Jul 08 20:19:02 oh actually bbl Jul 08 21:07:15 back Jul 08 21:11:59 lol, workflow to develop from an iOS device... Jul 08 23:23:52 Can the RAM on the BBB be replaced with others to make up 1GB ? Jul 08 23:24:29 it's soldered on Jul 08 23:24:35 so no Jul 08 23:28:26 package-on-package Jul 08 23:28:47 I believe there are some addressing limitations Jul 08 23:29:02 I think some of the newer boards use some tricks .. Jul 08 23:29:09 but not 100% on that Jul 08 23:32:51 if you're a wiz with a hot air rework station you could swap it out Jul 08 23:33:27 Could the BBB output 4K on the hdmi? On a headless operating system CLI? Jul 08 23:33:28 1GB single-rank ddr3 chips are uncommon and expensive though Jul 08 23:33:33 no Jul 08 23:33:51 not without replacing the framer chip too. Jul 08 23:33:57 and probably the cpu Jul 08 23:34:02 simple no Jul 08 23:34:03 so .. I'm guessing the BBB isn't for you ... Jul 08 23:34:15 :) Jul 08 23:34:35 like, 4K is no on many levels Jul 08 23:35:00 I don't know much that deals with 4k .. its still relatively 'new' tech Jul 08 23:35:18 phinxy: it can't do 1080p really Jul 08 23:35:21 well, maybe you can output 4K on HDMI... if you can find a HDMI framer that can do the upscaling for you :P Jul 08 23:35:22 decode is only just starting to come to market .. Jul 08 23:35:33 zmatt: 'xactly... Jul 08 23:35:39 the clocks aren't fast enough Jul 08 23:36:06 at 1GHz I'm not entirely surprised .. Jul 08 23:36:21 the cortex-a8 clock isn't the problem Jul 08 23:36:24 it's not like that Jul 08 23:36:48 you run into the pixel clock rate ceiling of LCDC Jul 08 23:36:49 i could mass scaler values that would produce e.g. 200GHz clock signal Jul 08 23:36:52 you run out of memory bandwidth Jul 08 23:36:59 the signal that comes out ofc will not be anywhere near that Jul 08 23:37:25 the killer is that the display hardware has a minimum divisor of 2 for the input clock Jul 08 23:37:37 and of course if you'd manage to get LCDC going.... now you got a giant canvas you need to paint on :P Jul 08 23:37:41 if that didn't exist we could do 1080p @ 60fps Jul 08 23:37:54 i got it to work btw :) Jul 08 23:38:10 https://ce.gl/hooraydisplay.png Jul 08 23:38:10 that divider really isn't the problem Jul 08 23:38:34 that just means you need to configure the pll at twice the pixel clock rate. that's not a problem Jul 08 23:38:39 * veremit dispenses some popcorn .. Jul 08 23:38:56 yeah but that results in a too-fast output freq Jul 08 23:39:00 i forget the hard max Jul 08 23:39:08 but it was, i think, something around 1GHz Jul 08 23:39:15 i tried pushing it, to no luck Jul 08 23:39:30 i didn't try using the alternate CLKOUT sources tho... Jul 08 23:42:17 not sure what you're talking about right now Jul 08 23:42:25 the max pixel clock is 126 MHz Jul 08 23:43:32 so... the pll could run as low as... 4 times that I think? Jul 08 23:43:45 don't know all the constraints off the top of my head Jul 08 23:43:50 https://ce.gl/b47f4ba1.png Jul 08 23:43:51 these Jul 08 23:44:30 uhm, what about "those" ? Jul 08 23:45:54 err, i don't know Jul 08 23:46:04 for some reason i had it in my head that one of these could be faster than CLKOUT Jul 08 23:46:08 i guess i mis-remebered Jul 08 23:46:14 the pll is really not the limiting factor here Jul 08 23:47:19 what is ? Jul 08 23:47:24 LCDC Jul 08 23:47:47 and memory bandwidth/latency probably Jul 08 23:48:11 ah yeah Jul 08 23:57:05 the bbb just isn't the best choice if you want a graphics workstation :P Jul 08 23:58:04 kremlin: beautiful desktop btw ;P Jul 08 23:58:21 thanks :) Jul 09 00:01:14 uhh what? Jul 09 00:01:27 * zmatt stares at the CAVEATS section of the amdisplay manpage Jul 09 00:01:34 where did they get that nonsense from? Jul 09 00:01:42 of course lcdc doesn't conflict with eMMC Jul 09 00:03:18 lcdc uses P8.27-46, eMMC uses P8.03-06 and P8.20-25 Jul 09 00:09:26 zmatt: that's my nonsense Jul 09 00:09:30 yeah, i got that wrong Jul 09 00:10:23 and only 16 bit color depth is supported because only 16 data lines are connected to the hdmi framer :P if you're referring the red/blue issue, that doesn't mean only 16-bit is supported. it means that if you want 16-bit color on a board designed for 24-bit or vice versa that you get a slightly annoying pixel format Jul 09 00:10:48 though the issue wouldn't exist at all with this hdmi framer anyway since it can swap channels Jul 09 00:15:27 note btw that "amdisplay" might not be the best name for a driver for lcdc, most "AM..." SoCs from TI have a completely different display controller Jul 09 00:16:15 also, commit early, commit often ;) Jul 09 00:20:20 yeah they wanted me to redo all the names Jul 09 00:20:23 well Jul 09 00:20:25 the whole thing was a wash Jul 09 00:20:36 the stupid USB controller isn't ehci compatible Jul 09 00:20:46 its some mentor graphics USB OTG jawn Jul 09 00:20:46 welcome to musb Jul 09 00:20:50 yeah Jul 09 00:20:53 no driver for that yet Jul 09 00:20:56 im not about to write one Jul 09 00:21:08 no usb -> no mouse/keyboard -> why have a display driver Jul 09 00:21:08 musbhdrc in full Jul 09 00:21:54 touchscreen Jul 09 00:22:31 the adc is also a controller for resistive touchscreens Jul 09 00:30:11 a storm just knocked out mains here Jul 09 00:30:14 ill bbl **** ENDING LOGGING AT Sun Jul 09 03:00:01 2017