**** BEGIN LOGGING AT Thu Jun 08 03:00:02 2017 Jun 08 06:55:07 hi all Jun 08 09:57:54 Hi all! does someone know the operating temperature range of the BeaggleBone Black Wireless? Jun 08 10:26:56 Hello People Jun 08 12:52:07 Hi, i need some help connecting a touchscreen on my BeagleBone Black Rev C latest debian jessie OS Jun 08 12:57:44 hedesis: it will help if you actually ask a question... people are not likely to volunteer to hold your hand Jun 08 12:58:31 I have tried many solutions, HDMI output is working properly and USB touchscreen, works fine on Windows but not on it. Jun 08 12:59:59 is the USB touchscreen supported on linux at all? Jun 08 13:02:16 I think it is, it saws the xinput of it, once i start the lightdm it recognise i have connected a touchscreen it starts xinput-calibrator but did not detect when i touch, meanwhile in Raspberry using raspbian it is working plug and play Jun 08 13:04:34 see, this kind of info is rather important :) you should have stated "it works fine on the rpi" rather than the meaningless "works fine on Windows" Jun 08 13:05:09 Well sorry, not sure about how to ask about the problem Jun 08 13:06:56 there's a somewhat useful guide "how to ask smart questions", also linked to in the channel topic Jun 08 13:07:42 anyway, next up a pastebin of the kernel log would be helpful (dmesg | pastebinit) Jun 08 13:09:50 (I'm not sure I'll be able to help you since I have zero experience with usb touchscreens, but perhaps I can at least help you formulate your problem in a way that makes it easier to others to help you) Jun 08 13:11:29 ok, dont worry i appreciate the help you are giving Jun 08 13:11:33 http://paste.debian.net/970621/ Jun 08 13:12:34 I think it can be close line 406 Jun 08 13:13:46 yeah but it's only triggering activity in the input subsystem, not in the video subsystem Jun 08 13:14:05 the last line also strikes me as odd Jun 08 13:14:31 logitech can be the keyboard Jun 08 13:14:36 ah Jun 08 13:14:48 KB + touchpad Jun 08 13:15:47 hedesis: line 413, 414 Jun 08 13:15:52 maybe compare with what happens when you attach it to the rpi Jun 08 13:16:15 hedesis: looks like the hit-multitouch driver is unable to initialize the panel properly Jun 08 13:16:26 hedesis: hid-multitouch Jun 08 13:16:38 also, yes, compare with what happens on rpi Jun 08 13:17:27 (ah nm what I said about not triggering activity in the video subsystem, I misunderstood what you meant by "USB touchscreen") Jun 08 13:17:55 hedesis: sorry, no /msg Jun 08 13:18:10 hedesis: keep discussion on the channel, please Jun 08 13:18:43 how can i compare with rpi? Jun 08 13:18:59 checking dmesg? Jun 08 13:19:04 yup Jun 08 13:19:05 for example Jun 08 13:19:44 thanks for your help Jun 08 13:19:47 i will try Jun 08 13:19:59 you can also track udev activity by running "udevadm monitor -u -p" while connecting the usb Jun 08 13:22:15 i'll be back in an hour i will try to come back with more info Jun 08 13:22:19 thanks for your help Jun 08 13:35:19 Hello. I use TSC_ADC in continuous mode. I set buffer at 6400 bytes with iio driver. In every loop, I take 3200 bytes from buffer then do some stuff ( calculate fft ). The absolute value at 50hz freq return from fft would be 7000-8000. But when in the "while loop", the value is just a few dozen after some loops. I do all in python environment. Jun 08 13:42:35 https://pastebin.com/KUHscmZ3 Jun 08 13:45:21 The value must be alway in range 7000-8000. But after some loop, it's just 20-40 Jun 08 13:54:33 Anyone happen to know what sort of ports or busses are presented at the Grove connectors on a BeagleBone Green? Jun 08 13:55:06 hieu: os.read(fd,3200) returns *at most* 3200 bytes Jun 08 13:55:26 hieu: it may very well return less than that, if less than 3200 bytes are available at the time of the call Jun 08 13:57:08 lopta: well they just connect to some expansion header pins I think, i.e. GPIO + whatever other function(s) happen to be available on those pins... I could check the schematic I guess Jun 08 13:58:14 hieu: why are you using os.open and os.read instead of open and read ? Jun 08 13:58:35 Thanks zmatt Jun 08 13:58:43 I shall return after I've done some reading. Jun 08 13:59:30 sure, don't bother sticking around after I offered to check to schematic Jun 08 13:59:38 *check the Jun 08 14:25:16 Hi, I'm back Jun 08 14:25:34 http://paste.debian.net/970637/ Jun 08 14:25:46 thats the rpi dmesg Jun 08 14:32:11 rpi unplug and plugin the usb touchscreen : http://paste.debian.net/970640 Jun 08 14:39:44 debian jessie dmesg: http://paste.debian.net/970621/ Jun 08 14:39:52 on bbb Jun 08 14:39:58 and its unplug and plug Jun 08 14:40:03 http://paste.debian.net/970645 Jun 08 15:06:46 some ideas? Jun 08 15:53:06 hello everybody. can anyone tell me how to get to the uboot on the beaglebone black? how do i access the original files, how to edit them. Jun 08 16:30:31 it would already help me to get a hint on how to upgrade it. Jun 08 18:01:43 \o/ got the HDMI cape working on my BBGW and even showing up nicely on the 800X400 HDMI panel. now the fun begins.. (well o.k. after the updates) Jun 08 18:57:53 Is it possible to clone an image of the SD card while it is in the card slot in the BBB over USB on extrenal computer? Jun 08 19:33:20 Hi, I am unable to write to GPIO pins. I think everything is setup right: executing as root, the file exists, the direction is set to "out". What am I missing? Jun 08 19:36:53 and by "unable to write", I mean "echo 1 > /sys/class/gpio/gpio49/value" succeeds and changes the contents of that file to 1, but the voltage on the pin doesn't change Jun 08 20:22:15 aaronm04: pinmux probably Jun 08 20:23:58 freemor: you have a BBGW and then put a HDMI cape on it? o.O Jun 08 20:24:58 aaronm04: you can use my show-pins utility to check the pin configuration, https://github.com/mvduin/bbb-pin-utils Jun 08 20:25:38 hmm, desperate_dude clearly wasn't desperate enough to actually bother staying for a bit Jun 08 22:30:15 zmatt: I'll check it out tonight. Thanks! Jun 08 22:41:52 Q: how are 'feature' requests tracked. For example: RPI @ boot, auto expands the SD Card image BBB does not Jun 08 22:42:20 I think adding this feature (auto-expand image) to BBB would be a very good thing. Jun 09 00:29:04 zmatt: I did not understand when I first envisioned my master plan quite how IoT focused the BBGW is.. I'll use my second BBGW more IoT-ish Jun 09 00:29:59 My first foray into BB* so still on the learning curve Jun 09 00:30:21 IoT focused? Jun 09 00:33:26 Consideing the default image on a BBGW is titled IoT.. yeah kinda.. lotsa connectivity.. meant to be headless Jun 09 00:34:25 the "iot" image basically just means "no gui" Jun 09 00:34:35 which makes sense since the BBGW has no HDMI output Jun 09 00:35:24 right.. I think the makers of the board were envisioning headless embedded type projects Jun 09 00:36:47 probably... the design of the BBGW is pretty sillybeans though, they pointlessly sacrificed quite a bit of I/O Jun 09 00:37:26 (by attaching the wireless chipset to expansion header pins instead of reusing the pins normally used for ethernet) Jun 09 00:38:19 hmmm... good to know going forward... I was actually worried at one point that there was a pin conflict with the HDMI cape (also seeed studio) and thus it would be a total no go Jun 09 00:39:10 the BBBW does reuse the ethernet pins for the wireless chipset, hence avoiding the sacrifice Jun 09 00:39:28 nice Jun 09 00:39:36 presumably the blue does the same, haven't checked Jun 09 00:40:41 am I right in believing that the max-ish through put on the wifi will be about 2Mbps Jun 09 00:40:52 (the remaining bbb-derivative with wireless I know of, the BBE, takes a very different strategy and embeds a usb hub and usb-wifi chipset) Jun 09 00:41:18 2? that sounds rather slow? Jun 09 00:43:20 I'll have to run some tests then... might have been the servers I was talking to, miss configuration, or device/router issue.. Jun 09 00:43:24 but no idea really, of all of the aforementioned I only have the BBE and haven't done much testing with it Jun 09 00:45:15 but definitely people in the seed studio forums saying it maxes out at about 2MBps and I wos only seeing a little over 200KB/s (max) while doing apt-get upgrade Jun 09 00:45:35 It'll be fun to poke at and see what I can do. Jun 09 00:48:09 It's a whole new world, dtb's and alll the flexability of the am335X hardware.. love the openness Jun 09 00:48:34 yeah, nice set of peripherals too Jun 09 00:48:47 and a fairly detailed processor TRM Jun 09 00:48:59 even with all the info that's still missing Jun 09 00:50:11 ....still missing?!? the TRM is huge.. I've only barely scratched it.. Jun 09 00:50:38 not doubting you.. but WOW.. still more. This is a deep rabbit hole Jun 09 00:51:09 the chapters on the interconnects and the debug subsystem are a joke in the am335x TRM Jun 09 00:51:48 Ah I'll bear that in mind when I get that far. Jun 09 00:51:58 (you can find much more info on those in the TRMs of the DM814x (for interconnects) and DM816x (for debug subsystem), both of which are closely related to the AM335x) Jun 09 00:52:14 the crypto accelerators are also not publicly documented Jun 09 00:52:31 well thats a shame Jun 09 00:53:53 there are drivers for them though, except for the public-key accelerator, and the driver for the AES accelerator only supports a subset of the functionality Jun 09 00:55:38 heres a question I've been pondering.. how am i gonna access the seial header with the cape on? Jun 09 00:56:08 https://www.tindie.com/products/spirilis/beaglebone-black-ftdi-friction-fit/ Jun 09 00:57:14 works like a charm :) Jun 09 00:57:44 well cool beans... thanks Jun 09 00:58:30 I've been hacking it with an arduino board with the amtel chip pulled out :) Jun 09 00:59:13 another creative solution would be to desolder the header and resolder it on the opposite side of the pcb Jun 09 01:00:35 i suppose so.. but as the one with the HDMI cape is bound for mounting on a board.. that wouldn't be the best fit.. That cable will be handy tho Jun 09 02:02:58 that is no more IoT focused then buying a headless SunSparc Station Jun 09 02:19:54 zmatt: I used show-pins, but I'm not sure how to read the output. Here is the line for the GPIO I want to write to: "P9.12 30 fast rx up 7 gpio 1.28 hi >> P9_12 (pinmux_P9_12_default_pin)" Jun 09 02:20:27 the rx looks like it's wrong. I suppose I want tx instead Jun 09 02:28:42 rx means rx-enabled Jun 09 02:29:06 that line actually says the pin is actually muxed to gpio and being driven high ("hi >>")... Jun 09 02:30:20 are you're saying the voltage on that line is low? **** ENDING LOGGING AT Fri Jun 09 03:00:03 2017