**** BEGIN LOGGING AT Wed Nov 18 02:59:59 2015 Nov 18 05:19:03 hrm Nov 18 05:19:12 maybe I have that issue Nov 18 05:19:27 why would direct memory access make it sower Nov 18 05:21:20 thanks for making that spreadsheet zmatt Nov 18 05:21:39 I just want pins I can plug sensors and leds into and stuff like on an arduino :o Nov 18 05:22:00 maybe the x15 is too powerful for such nonsense Nov 18 06:16:33 hehe Nov 18 06:16:44 you can do that on a BBB Nov 18 06:17:31 the x15 could use an "I/O for normal people" expansion board Nov 18 06:18:30 and the USB subsystem is pretty awful in general, its DMA engine is no exception Nov 18 06:18:59 it's also quite possible the kernel driver just does some really stupid things, but I can't be bothered to look at it Nov 18 06:19:23 any time I come too close to the USB subsystem I feel a need to shower Nov 18 06:21:47 (the usb subsystem of the am335x that is... no idea how the one on the x15 is, though it's still usb which is bad enough) Nov 18 07:44:52 Gicha-Gicha-Gicha! Nov 18 07:45:40 Does Electric Imp and BeagleBone Black connect to each other? Nov 18 07:45:59 Squirrel Code? Nov 18 08:16:24 you should be able to connect them, yes Nov 18 08:17:18 Cool! Nov 18 08:18:18 I will try soon...thank you. Nov 18 08:18:34 you will need a breakout board Nov 18 08:18:44 I have an April Board. Nov 18 08:18:48 but then you hae serveral possibilities to connect the two boards Nov 18 08:18:59 Augh...like? Nov 18 08:20:26 I get it...sort of. I could apt-get Squirrel Code to the BBB and get apt-get install some type of driver for SDHC cards. Nov 18 08:20:48 Then...I would have to get the board for the SDHC card. Nov 18 08:22:06 you will need the UART or I2C or even PWM connection between the boards. Nov 18 08:22:19 just apt-get something will not work Nov 18 08:23:04 The board does not have i2c or UART. Nov 18 08:23:16 the april board? Nov 18 08:23:20 Yes. Nov 18 08:23:35 sure Nov 18 08:23:50 https://electricimp.com/docs/hardware/imp/pinmux/ Nov 18 08:23:54 It has ground, 3.3, and some Pins... Nov 18 08:23:59 Augh...okay. Thank you. Nov 18 08:25:08 i have no clue how to configure the imp right to use it. but it should be possible to get uart and or i2c running Nov 18 08:26:20 Yea...there is. I noticed that board to board communication is possible. I will figure that out. Nov 18 08:26:28 Thank you for the link. Nov 18 08:27:27 I will figure it out but they are big on Arduino now instead of the BBB. Nov 18 08:27:30 Yikes! Nov 18 08:28:38 I am going to have to purchase an Adafruit breakout board. You were right Nov 18 08:32:19 why not use the april board? Nov 18 08:33:21 The April Board has a timing issue. The i2c info. on the i2c page states that a board is used to help with timing. Nov 18 08:35:29 I am on the UART page now. They say I need a Serial to USB adapter. Nov 18 08:35:37 i.e. for UART. Nov 18 08:35:47 Oh and software. Nov 18 08:36:34 if you want uart to usb, yes. but if you want uart to uart noone needs a adapter Nov 18 08:37:13 Oh? Nov 18 08:37:35 Okay...so? I could just get code? Nov 18 08:37:45 and program the two systems? Nov 18 08:40:06 right Nov 18 08:40:34 "get code" will be more like "write code" ;) Nov 18 08:42:24 Write...right! Nov 18 09:05:24 so... it's a tiny processor with wifi Nov 18 09:05:58 why not stick wifi into your BBB? then you have a much bigger processor with wifi :P Nov 18 09:07:23 I like the Squirrel Code and I want to learn more. Nov 18 09:11:19 it looks like a number of other high-level languages, but with some random things different for the sake of incompatibility Nov 18 09:11:58 Yep. Nov 18 09:12:12 That is why I want to use it. Just for the absurd notion. Nov 18 09:12:28 then use haskel... Nov 18 09:13:10 http://www.timber-lang.org/ Nov 18 09:13:35 there's some different for ya Nov 18 09:14:18 but oriented toward real-time embedded systems, unlike haskell Nov 18 09:16:16 "Plans for the next release (Q1 2009)" seems to be dead Nov 18 09:16:45 details, details, just reinvigorate development yourself if you like it Nov 18 09:19:07 OpenSCAD! Nov 18 09:19:50 I am learning this slowly too... Nov 18 09:20:08 epigram also seems dead Nov 18 09:20:15 shame, it had such pretty syntax... Nov 18 09:20:20 ( ! ( ! ( n : Nat ! Nov 18 09:20:20 data !---------! where !----------! ; !-----------! Nov 18 09:20:20 ! Nat : * ) !zero : Nat) !suc n : Nat) Nov 18 09:20:46 Making objects is cool. They have a linux version. I can use the FPGA Cape to make me a Bot. Nov 18 09:20:54 A bot that makes bots. Ha! Nov 18 09:21:13 don't come complaining to us if they take over your house Nov 18 09:21:27 Ha..."the toaster just bit me!" Nov 18 09:25:00 squirrel borrowed all the wrong things from javascript -.- Nov 18 09:25:19 Dang Nov 18 09:25:50 Pin 9 on my April board can give me i2c. Nov 18 09:26:02 and UART Nov 18 09:27:01 i think i saw a internet connected toaster yesterday at CHTF... Nov 18 09:27:23 Your toast is burnt! Nov 18 09:27:33 via e-mail Nov 18 09:28:25 I see that there are many UARTs. Nov 18 09:28:41 1289 and 57 and 12 Nov 18 09:28:59 Each set of numbers have different types too. Nov 18 09:29:56 e.g. uart1289 RX/TX and uart1289 RTS/CTS Nov 18 09:35:41 330 ohm resitor...dang! Nov 18 09:35:54 I got a 10k and a 100 ohm. Nov 18 09:36:08 330? Who has got that? Nov 18 09:36:10 Sheesh. Nov 18 09:40:45 use 3 of each Nov 18 09:40:56 or only 3 of 1M Nov 18 09:41:01 in parallel Nov 18 09:41:10 Okay. Nov 18 09:41:22 if there was only a way to combine resistors like Lego Nov 18 09:41:22 I can I guess. Nov 18 09:41:31 philenotfound: solder? Nov 18 09:41:50 also, why does it have to be 330k? Nov 18 09:42:00 I do not know. It says so. Nov 18 09:42:10 I guess becaue of that law. Nov 18 09:42:12 Hhahaha. Nov 18 09:42:35 Not 330k, it is only 330. Nov 18 09:42:47 av500: sarcasm Nov 18 09:43:17 i think lego with resistors in it will kickstart quite good Nov 18 09:44:01 uavcamm: there was one with LEDs, iirc Nov 18 09:44:11 LEDs! Nov 18 09:44:21 Blink.py? Nov 18 09:44:22 Ha... Nov 18 09:45:08 I 3D printed some stuff tonight. That CURA software needs no slic3r engine. Cool! Nov 18 09:45:14 I got me a knob or two printed. Nov 18 09:45:31 I had to drill but oh well. Nov 18 09:45:55 I want to figure out how to use the Cape to make a 3D Printer. It is on the bucket list. Nov 18 09:46:47 DJWillis: how is the openpandora? Nov 18 09:47:35 av500: not touched it other that ScummVM coding for some time ;). Had that nasty 'real job' think ruining all hacking options. Nov 18 09:49:21 Firmware is out of date and rotted, parts still on OE classic, the rolling modern Yocto/OE/Angstrom firmware never really got traction and of course it has OMAP3 'cruddy OGL driver support' syndrome ;) Nov 18 10:08:01 I am looking for a capacitive touch display for beagle bone black Nov 18 10:08:17 i found NHD-5.0-800480TF-ATXL#-CTP Nov 18 10:08:40 I am not sure whether it is compatable with BBB or not Nov 18 10:09:10 Try Element14.com. Nov 18 10:09:11 can any one tell me whether it is compatible with BBB or not Nov 18 10:09:32 They have compatible displays. Nov 18 10:09:50 but they have resistive touch displays Nov 18 10:10:05 i am looking for a 5 inch capacitive touch display Nov 18 10:10:09 Sure...they should. They have everything! Nov 18 10:10:15 Capacitive means what? Nov 18 10:10:36 Okey... Nov 18 10:10:51 capacitive touch Nov 18 10:10:59 Oh...okay. Nov 18 10:11:15 So, they have touch screens. Nov 18 10:11:20 DJWillis: sounds good ;) Nov 18 10:11:30 You can go directly to what goes with the BBB. Nov 18 10:12:13 i.e. Part# 13568 (Touch Screen) goes with Part# 5458 (BBB) and etc... Nov 18 10:12:35 i found 4.3" and 7" of which only 7" is capacitive Nov 18 10:13:04 i am looking for 5" capacitive touch display Nov 18 10:13:42 Dang...I hope that works out. Try the 7" because it is bigger Nov 18 10:14:01 Okay...5". Got it. Nov 18 10:14:25 Um...did you check online at the local retailers that sell the BBB? Nov 18 10:14:32 Yeah... but for my application max size i can use is 5" so Nov 18 10:15:07 ya they said 4.3" resistive touch display are avilable with them Nov 18 10:15:59 sushma: use a 5" android phone: http://elinux.org/BeagleBoard/GSoC/BARD Nov 18 10:17:21 http://elinux.org/BeagleBoard/GSoC/2015_Projects#Project:_Android-based_Remote_Display Nov 18 10:19:24 can we interface mobile display with beagle bone? Nov 18 10:20:50 I mean we can get a mobile display with touch panel, can we connect that to BBB? If yes how to connect and display data? Nov 18 10:25:36 Plug it in and write the code to connect. Nov 18 10:26:51 Time and effort. Yep. Nov 18 10:26:58 sushma: no, you cannot Nov 18 10:27:02 Oh. Nov 18 10:27:07 I did not say to use a mobile display Nov 18 10:27:14 use a mobile phone :) Nov 18 10:27:23 of course you can connect a display Nov 18 10:27:42 if you know how to implement that needed parallel to DSI bridge Nov 18 10:27:49 and write all the SW for it Nov 18 10:28:30 http://www.logicsupply.com/cs-bbb-exp50/ Nov 18 10:28:33 why not this one? Nov 18 10:29:34 http://www.ebay.com/itm/Beaglebone-Newhaven-LCD-5-inch-cape-with-capacitive-touch-multitouch-nh5cape-/151885521631? Nov 18 10:34:07 ya it is good thank you Nov 18 10:35:36 NHD-5.0-800480TF-ATXL#-CTP is this not compatable with beagle bone black? Because we are asked to use that by our TL Nov 18 10:38:20 seems OK to me Nov 18 10:38:49 if you wire it up properly Nov 18 10:39:54 looks like its the one used here: p://www.logicsupply.com/cs-bbb-exp50/ Nov 18 10:55:46 NHD-5.0-800480TF-ATXL#-CTP it has two different lines, one for display and other for touch Nov 18 10:56:08 do i need any controller or driver circuit to connect Nov 18 10:58:59 touch is I2C Nov 18 10:59:14 google will tell you how to use I2C on the BBB Nov 18 10:59:20 for the display part, read the data sheet Nov 18 10:59:46 if you have no idea about hardware, buy a ready made solution Nov 18 11:02:06 ok thank you Nov 18 11:06:11 Well...I got my Squirrel Code printed out. Now, it is onto superior coding skills (maybe). Nov 18 11:06:29 Probably a lot of reading only... Nov 18 11:07:47 I was getting NPM Warn codes when upgrading my BBB. Nov 18 11:07:55 Does anyone know of what happened? Nov 18 11:08:31 I looked on their site and everything was A-Okay. Nov 18 11:10:13 excluding symbolic link keeps popping up. Nov 18 11:13:30 npm WARN excluding symbolic link tests/filelist_fixtures/symlink-to-1.txt -> 1.txt Nov 18 11:13:30 npm WARN excluding symbolic link tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt Nov 18 11:13:30 npm WARN excluding symbolic link tests/search_fixtures/symlink-to-file1.txt -> file1.txt Nov 18 11:13:30 npm WARN excluding symbolic link tests/filelist_fixtures/symlink-to-1.txt -> 1.txt Nov 18 11:13:30 npm WARN excluding symbolic link tests/filelist_fixtures/symlink-to-nowhere.txt -> nowhere.txt Nov 18 11:13:30 npm WARN excluding symbolic link tests/search_fixtures/symlink-to-file1.txt -> f Nov 18 11:13:36 That is what happened. Nov 18 11:16:05 I am off to look it up but if you know, please say something. I am creating an issue with npm on Github... Nov 18 11:25:55 I came up with two links. Two! Both are useless and I am bugged. Dang! Nov 18 11:45:59 Bye for now...I could not find anything. I will see what the people at npm say later in the day. Good times... Nov 18 12:11:00 hi everyone Nov 18 12:11:29 do you have any idea about the 6lowpan solution Nov 18 12:11:52 who i can talk about with him/her Nov 18 12:11:53 ?, Nov 18 12:15:48 try talking to Google Nov 18 12:18:05 I also searched and I need a solution with beaglebone with including 3g connection. Nov 18 12:22:34 * tbr has that working with 802.15.4 Nov 18 12:23:25 works OotB on the 4.x kernels, just need to add the RF chip to the DT obviously Nov 18 12:24:51 aliag: which pffz Nov 18 12:24:58 meh! Nov 18 12:36:54 yaaaaaaaaaaay wooohooo!! \o/ Nov 18 12:37:06 avahi-daemon has finally been fixed to stop spamming the logs Nov 18 12:37:51 (yeah, two weeks ago already, but I finally noticed and quickly updated the BBBs) Nov 18 12:39:13 av500: you should have send him to signal11 Nov 18 12:57:38 or to #linux-wpan Nov 18 16:56:34 hello Nov 18 16:59:28 question to you: anyone has any experience with BBB set up as an I2C SLAVE device? Nov 18 17:55:24 hola Nov 18 17:56:05 alguien que pueda ayudar mi bgboard no conecta Nov 18 19:04:26 Zsolt-- wouldn't that be part of the board? Nov 18 19:04:40 I have no idea Nov 18 19:04:47 like part of the board's design Nov 18 19:05:10 I can use the board as an I2C master right now Nov 18 19:05:40 but my aim would be to have it set up for slave mode Nov 18 19:06:34 the 4.1 kernel should have the i2c_slave support, but until now I did not find any good documentation or example codes Nov 18 19:06:36 what's your project? Nov 18 19:07:03 my kernel is still the 3.8.x one I think Nov 18 19:07:25 as far as I know its available from 3.19 Nov 18 19:08:00 oh, I'm probably mistaken Nov 18 19:08:47 the aim would be that the BBB would sit on the I2C bus, it would catch messages and respond accordingly Nov 18 19:08:57 I upgraded it to the latest this weekend using the ./update_kernel.sh script Nov 18 19:09:08 then you should have the one I have Nov 18 19:09:13 :) Nov 18 19:10:01 I'm still in heavy learning phase right now, curious what other people are working. I'm just happy there's activity in the channel Nov 18 19:10:03 :D Nov 18 19:11:10 me too...learning... Nov 18 19:12:04 I'm also working on to drive two high voltage DC motors with encoder feedbacks. it works quite nicely, but still many things to do on how to sync the two motors... Nov 18 19:12:55 anyway, now the headache is with this I2C slave mode... Nov 18 19:19:41 I2C slave mode -.- Nov 18 19:19:45 fun Nov 18 19:20:03 well I suppose it's not quite as buggy as master mode Nov 18 19:20:40 well, until now in master mode I've done simple dev reads and writes Nov 18 19:21:11 apart from the bit where an malformed bus transaction (such as a negative pulse on SDA) can cause the I2C peripheral's state machine to lock up, invisibly (bus busy/free is still indicated correctly but it no longer responds to any address) until you reset it Nov 18 19:22:13 do you have any docs or references/examples how to implement it? Nov 18 19:23:59 not really, just notes... it's relatively straightforward since it'll automatically stall (clock stretch) if the rx fifo is full (or tx fifo empty, depending on direction) Nov 18 19:24:41 annoying limitations is that it always acks its configured address(es), general call, and every byte written -- you have no way to nak Nov 18 19:26:56 and if it performs a read it will happily read any data that might accidently still be in the tx fifo Nov 18 19:27:01 *if the master Nov 18 19:27:12 ok that sentence is a mess Nov 18 19:27:28 if the master performs a read, the peripheral will happily transmit any data that might accidently still be in the tx fifo Nov 18 19:28:00 e.g. from a previous read that was nacked and ended by the master before all data in the fifo had been read Nov 18 19:28:55 though you can prevent that one with careful use of the stall bits (and then clear the fifo before releasing the stall) but it's a bit messy Nov 18 19:31:01 here are some old notes I have: http://gerbil.xs4all.nl/ti-i2c-notes.txt Nov 18 19:33:26 the line activity is transcribed using <> to denote sda falling/rising while scl high, . is scl falling, 0/1/x is scl rising while sda is 0/1/something Nov 18 19:35:09 +FOO/-FOO means the irq is asserted/deasserted, ^FOO means it's pulsed (so it's set but you can clear it) Nov 18 19:36:48 sorry if turns out unreadable, they're just personal notes Nov 18 19:40:26 trying to figure it out Nov 18 19:40:51 there, added comments on the bus notation and irq notation (reload page) Nov 18 19:41:46 i2c's irq registers have really obnoxious behaviour Nov 18 19:49:49 I suggest just mapping it in userspace (if you use uio you can even get irq delivery, though you can also just poll the irq register) and playing with it while generating requests using another device or even just by bitbanging two gpios Nov 18 19:50:14 with i2c you can take all the time you need :) Nov 18 19:53:21 this will be a hell of a work Nov 18 19:53:39 it's not *that* bad Nov 18 19:54:54 aforementioned suggestion can be ignored if you think playing with the peripheral to get acquainted with it and its quirks has insufficient added value of course Nov 18 19:55:20 can I connect two I2C buses together on the BBB? Nov 18 19:55:40 in this case I have already set up a master Nov 18 19:56:11 and it works, coz I have a device which responds correctly. The aim would be to mimic the device by the BBB Nov 18 19:56:42 you could connect i2c 1 and 2, but that will make it harder to gently see what's going on since you can't easily make the master take one small step at a time Nov 18 19:57:22 in all cases, I recommend keeping the stall bits for your slave address(es) enabled Nov 18 19:57:56 this means i2c will stall the master as soon as it recognizes the address Nov 18 19:59:31 this gives you opportunity to get ready for the new request, e.g. clear the fifos if there's still crap in them Nov 18 20:00:38 then clear and immediately set the stall bit for the addressed slave, and the transaction will proceed (limited only by the master and by tx fifo empty / rx fifo full) Nov 18 20:01:09 I would lie if I would tell all clear what you are telling... :) Nov 18 20:01:33 are you familiar with how i2c clock stretching works? Nov 18 20:02:18 its when the slave keeps the clock line down until it needs it, no? Nov 18 20:02:40 yeah, to stall the master until the slave is ready to proceed Nov 18 20:03:17 well, you have limited control over that: it's done automatically if the master wants to read from you but your tx fifo is empty, or the master wants to write to you but your rx fifo is full Nov 18 20:03:25 yep, I have read the I2C docs, and also verified the communication with a logic sniffer Nov 18 20:03:49 you can also request stalling when the i2c peripheral recognizes a master is addressing you Nov 18 20:04:10 by setting the relevant bits in the SBLOCK register Nov 18 20:04:24 (last reg of the peripheral) Nov 18 20:04:26 is there a higher level driver for this? Nov 18 20:04:43 I have no idea, I only have experience with this thing on baremetal Nov 18 20:04:46 or do I have to do it in low level, kernel space Nov 18 20:04:52 I would do it in userspace Nov 18 20:05:11 basically you would do bitbanging? Nov 18 20:05:14 no Nov 18 20:05:31 well, it's tempting, given how eccentric the I2C peripheral is, but no :P Nov 18 20:06:09 I was looking something similar then the Wire library for the Arduino Nov 18 20:06:31 * zmatt never used an Arduino Nov 18 20:07:01 and I have tried to use the arduino for my project, but it does not work...dont know why...it just simply does recognizes, when the master calls for it Nov 18 20:07:08 hehe Nov 18 20:07:10 thing is, I wouldn't trust an existing driver to be reliable anyway, since the behaviour of the I2C peripheral is non-obvious and poorly documented Nov 18 20:08:41 to create the notes you see I made an interactive I2C debugger running on a microcontroller on the same I2C bus, that could be used to construct i2c requests bit by bit in master mode, and allowed single-stepping through transactions in slave mode (using clock stretching) Nov 18 20:09:10 so I could single step through the transaction to see how the I2C peripheral on the TI processor behaved Nov 18 20:09:29 that sounds cool Nov 18 20:11:00 it kinda was, though needing it to make sense of the docs was a bit sad Nov 18 20:11:43 though TI is in good company here, its I2C peripheral isn't really much buggier than that of, say, the STM32 or that broadcom thing that's on the rpi Nov 18 20:12:33 the silent state machine lockup that can occur is a bit nasty though Nov 18 20:12:45 :) Nov 18 20:12:55 means you may need to reset occasionally just in case Nov 18 20:13:09 it may just be less trouble to write a soft I2C slave implementation and call it a day Nov 18 20:13:12 in master-mode it's easier, the driver just resets the peripheral on any timeout or other error Nov 18 20:13:17 ds2: slave is tricker than master though Nov 18 20:13:30 zmatt: which aspect are you referring to? Nov 18 20:13:53 ds2: having to react within a narrow window of time Nov 18 20:14:14 if you don't have a hw mechanism to stretch the clock for you until you're ready to react Nov 18 20:14:29 let me be more explicit - by soft I mean using the PRUSS Nov 18 20:14:42 <-- would rarely recommend bitbang on the A8 if ever Nov 18 20:14:48 oh, and don't forget the open drain aspect :) Nov 18 20:15:02 right, the open drain Nov 18 20:15:02 stick a MOSFET or a 2N2222 on there Nov 18 20:15:05 next problem? Nov 18 20:15:11 hehe Nov 18 20:15:26 if that doesn't give you an opendrain/open collector, nothing will :D Nov 18 20:15:30 :D Nov 18 20:15:43 yeah if you use an external FET then PRU could do it with its eyes closed and one hand behind its back Nov 18 20:16:18 at rates that make other i2c chips go OMG WTF WAS THAT ALL THOSE BITS FLYING BY Nov 18 20:16:46 so basically with some 2N2222 the BBB can be turned to a bidirectional I2C sniffer? Nov 18 20:16:51 given the rates you are probally looking at, you might be able to do the input/output mode pinmux trick Nov 18 20:17:02 doubt if the L4 would block longer then typical I2C bus times Nov 18 20:17:18 ds2: that's icky though, since you can't do it atomically Nov 18 20:17:32 so you'd need to be careful not to do any direction changes from the a8 Nov 18 20:17:36 at the same time Nov 18 20:17:48 Zsolt--: it can sniff without a FET Nov 18 20:17:50 if you are doing it to those pins, you are screwed. Nov 18 20:18:17 ds2: ah wait, of course with PRU you can do it per pin Nov 18 20:18:24 since it's a pinmux option Nov 18 20:18:28 hw or sw i2c will fail if there are conflicting mux changes Nov 18 20:18:30 yes! Nov 18 20:18:53 I mean the bus would be cut in half, inbetween the BBB would be placed, and it would transmit to both directions. Nov 18 20:19:11 Zsolt--: you mean an i2c bridge, sure it could do that Nov 18 20:19:20 really? Nov 18 20:19:27 it's PRU Nov 18 20:19:44 you need FETs for that though, especially if you want to be compliant to the standard Nov 18 20:19:57 for the open drain, ye? Nov 18 20:20:14 unless you have logic level fets lying around, I'd use a bipolar Nov 18 20:20:16 yeah, officially an i2c device is not supposed to disturb the bus it's connected to if it's unpowered Nov 18 20:20:19 more chance of one just lying around Nov 18 20:20:35 open drain, open collector, open something Nov 18 20:22:08 well, so my aim is to mimic one I2C slave. What are you recommending to do so? PRU or I2C slave driver? Nov 18 20:22:08 PRU could probably also act as an "I2C PHY" ... handle the low-level dirty work while allowing the a8 to handle the actual requests without any particular time constraints Nov 18 20:22:53 Zsolt--: depends on what you're more comfortable with, and also on some specifics of the slave you're trying to emulate Nov 18 20:23:17 well, there are 4 type of question-answers Nov 18 20:23:32 if the master asks for this, the slave has to reply that Nov 18 20:23:53 its about couple of hundred bytes Nov 18 20:24:32 so something like write request read data Nov 18 20:25:10 yes Nov 18 20:25:14 no need to NAK anything, or deal with some crazy master spamming you with small writes or shit like that Nov 18 20:25:31 ye Nov 18 20:25:52 you could have the PRUSS emulate a I2C slave controller and have the PRUSS firmware talk to the A8 using rpmsg Nov 18 20:25:55 then I *personally* would still go for the I2C peripheral, simply because it's already there and working (most of the time) Nov 18 20:25:58 that way you can use stock kernel APIs Nov 18 20:26:00 simpler solution than PRU Nov 18 20:26:02 for me Nov 18 20:26:11 but then again, I'm familiar with the I2C peripheral Nov 18 20:26:30 there i2c controller is scarce enough as it is without having to compete with other demands like slave mode Nov 18 20:26:42 analyze the pinmux options for the BBB signals that are available Nov 18 20:26:48 ds2: if it's available, it's available Nov 18 20:27:10 zmatt: not if you consider the braindead "cape" system Nov 18 20:27:10 OK but where are the damned documentations? :D Nov 18 20:27:17 Zolft--: TRM and SRM Nov 18 20:27:22 lovely Nov 18 20:27:26 TRM for the I2C controller indeed Nov 18 20:27:33 and my notes Nov 18 20:27:37 that cape system plus the way Uboot is setup means it bruns 2 I2C controllers right there Nov 18 20:27:44 ds2: 1 Nov 18 20:27:47 you barely have 1 assuming there is no pin conflict that eat away with that Nov 18 20:28:04 or well, i2c 0 but that's not accessible anyway and reserved for pmic and shit Nov 18 20:28:06 zmatt: 2... one is not exposed on the header... it is used for the onboard EEPROM Nov 18 20:28:18 eeprom, pmic, hdmi framer Nov 18 20:28:33 the pmic is reason enough to *not* put too much other shit on it Nov 18 20:28:37 there are 2 controllers on the header, one of which is "used" Nov 18 20:28:43 Guys, thanks for the responses Nov 18 20:28:44 easily disabled though Nov 18 20:29:02 I gtg now, but tomorrow I will carry on, thanks again Nov 18 20:29:06 bbl Nov 18 20:29:14 yeah, I could also get goign Nov 18 20:29:15 *going Nov 18 20:30:58 Good afternoon/evening/or possibly morning. Nov 18 20:31:13 I'd appreciate some help with my sudo apt-get problems. Nov 18 20:32:17 sudo apt-get returns error or ignores. The errors typically result in 404s. Nov 18 20:32:51 Why would this be? Likely either bad repos or bad certificates on my side. Nov 18 20:33:10 Or incorrect date on my hardware. Nov 18 20:33:32 wget https://rcn-ee.com/repos/debian/pool/main/r/rcn-ee-archive-keyring/rcn-ee-archive-keyring_2015.10.22~bpo70+20151022+1_all.deb Nov 18 20:33:43 Returns Resolving rcn-ee.com (rcn-ee.com)... 130.184.6.25 Connecting to rcn-ee.com (rcn-ee.com)|130.184.6.25|:443... connected. ERROR: The certificate of `rcn-ee.com' is not trusted. ERROR: The certificate of `rcn-ee.com' hasn't got a known issuer. The certificate's owner does not match hostname `rcn-ee.com' Nov 18 20:34:25 the cert looks fine to me Nov 18 20:35:47 http://pastebin.com/6GittT0k for apt-get results. Nov 18 20:36:34 @zmatt Any ideas? Nov 18 20:36:47 can you check cat /etc/dogtag Nov 18 20:37:22 debian@beaglebone:~$ cat /etc/dogtag BeagleBoard.org Debian Image 2015-11-03 Nov 18 20:37:25 is your time set properly? Nov 18 20:37:31 ohh nice one Nov 18 20:37:39 date Wed Nov 18 20:37:00 UTC 2015 Nov 18 20:37:49 @zmatt Yeah, fresh from the oven. Nov 18 20:37:58 Joe___: well, stale from the oven Nov 18 20:38:00 it's wheezy Nov 18 20:38:02 which is ancient crap Nov 18 20:38:10 (yes, I know it's the latest "official" release Nov 18 20:38:11 ) Nov 18 20:38:23 @tbr I can't use ntp for automated date setting. Nov 18 20:38:35 @zmatt I know! This drives me crazy! Nov 18 20:38:51 Joe___: consider grabbing the latest jessie image Nov 18 20:39:17 the "owner does not match hostname" suggests the software doesn't understand Subject Alternative Names Nov 18 20:39:28 and "is not trusted" might mean the ca-certificates is outdated Nov 18 20:39:51 @zmatt Good, I think the upgrade is right. Nov 18 20:40:12 @zmatt I'm very confident all of my credentials are outdated. Nov 18 20:40:12 weird Nov 18 20:40:25 the errors from debian.org are probably because wheezy has been officially declared "obsolete" a while ago already Nov 18 20:40:39 @tbr I can't used apt-get at all, so I'll have to manually install anything. Nov 18 20:40:50 hmm, isn't there some kind of override? Nov 18 20:41:11 wheezy is old-stable by now Nov 18 20:41:17 which is still supported Nov 18 20:41:24 @zmatt: Well, I'm pretty sure my settings are pointing to non-existant repos, anyhow. Nov 18 20:41:39 you can probably work around the "owner does not match hostname" by changing it to 'www.rcn-ee.com' instead of 'rcn-ee.com' Nov 18 20:42:01 tbr: it looks like debian abandoned that notion... https://www.debian.org/releases/ Nov 18 20:42:25 @zmatt: Nov 18 20:42:26 debian@beaglebone:~$ wget https://www.rcn-ee.com/repos/debian/pool/main/r/rcn-ee-archive-keyring/rcn-ee-archive-keyring_2015.10.22~bpo70+20151022+1_all.deb --2015-11-18 20:41:34-- https://www.rcn-ee.com/repos/debian/pool/main/r/rcn-ee-archive-keyring/rcn-ee-archive-keyring_2015.10.22~bpo70+20151022+1_all.deb Resolving www.rcn-ee.com (www.rcn-ee.com)... 130.184.6.25 Connecting to www.rcn-ee.com (www.rcn-ee.com)|130.184.6.25|:443... Nov 18 20:42:49 Joe___: are you on some corporate or university network? Nov 18 20:42:54 actually Nov 18 20:43:03 the url looks wrong entirely Nov 18 20:43:07 @tbr Yes, the latter. Firewall issues? Nov 18 20:43:09 I have in my sources.list: Nov 18 20:43:11 deb http://repos.rcn-ee.com/debian/ stretch main Nov 18 20:43:17 your DNS is being hijacked Nov 18 20:43:25 *stretch should be wheezy in your case Nov 18 20:43:33 and indeed Nov 18 20:43:34 it is Nov 18 20:43:38 www.rcn-ee.com has address 45.33.2.10 Nov 18 20:43:40 www.rcn-ee.com has address 45.33.2.10 Nov 18 20:43:57 that also explains the invalid certificate Nov 18 20:44:04 @zmatt and tbr: I thought I set my DNS to 8.8.8.8 Nov 18 20:44:23 Joe___: that might still be intercepted transparently Nov 18 20:44:29 Joe___: that doesn't help since your traffic is being intercepted and redirected Nov 18 20:44:46 so https warning about it is actually 'Working As Intended' Nov 18 20:44:53 consult your local network/IT department Nov 18 20:44:53 or well, warning, failing Nov 18 20:46:00 @zmatt, tbr:...crap. Nov 18 20:46:03 Joe___: what is the procedure for connecting to that network? any authentication or special stuff? Nov 18 20:46:38 @tbr On a wired connection nothing. Nov 18 20:46:51 well apparently there's something Nov 18 20:47:38 @tbr There is a list of registered MACs on this network. Nov 18 20:47:51 @tbr If you're on the list, you're good to go. Nov 18 20:48:08 well, then you should register the Ethernet MAC of your BBB Nov 18 20:48:48 @tbr. (Illumination from the heavens) Yes. I see. Nov 18 20:49:27 @zmatt I'll still use the Jessie image. Nov 18 20:49:37 definitely recommend that Nov 18 20:49:45 jessie and 4.1 kernel Nov 18 20:50:06 or later (I use stretch myself) Nov 18 20:50:50 tbr and zmatt, I thank you both. Nov 18 22:05:56 has anyone have experience using the adafruit libraray? Nov 18 22:09:02 which adafruit library and doing what? Nov 18 22:12:59 in python Nov 18 22:13:23 Traceback (most recent call last): File "wajeeh.py", line 4, in ADC.setup() RuntimeError: Unable to setup ADC system. Possible causes are: - A cape with a conflicting pin mapping is loaded - A device tree object is loaded that uses the same name for a fragment: helper Nov 18 22:13:44 im trying to import the gpio and adc but it keeps giving this error Nov 18 23:48:18 Hello... Nov 18 23:56:39 I found the answer to the WARN excluding symbolic link "issue." Nov 18 23:57:19 I found the answer on StackOverflow! Nov 18 23:59:56 The "WARN" issue from npm is when "sympbolic links" are not neeeded and npm does not update that specific file /directory. Nov 19 00:10:36 It's whats his set_ Nov 19 00:10:52 Me too? Nov 19 00:11:06 Guess who? Nov 19 00:11:52 that would be better than guess what probably. :D Nov 19 00:12:00 It is cool! Nov 19 00:12:06 I enjoy everything... Nov 19 00:12:17 Esp. the BBB/BBG. Nov 19 00:12:39 Pin here, connect there, and go, go, go. Oh and stop. Nov 19 00:16:04 Gen in "da hizzy!" Nov 19 00:16:37 That was a bit odd. Nov 19 00:16:42 I have this old VoIP machine/board. I wanted to find the code. I have looked. Nov 19 00:17:18 the code for what exactly? Nov 19 00:17:55 you want to have VOIP control with a BBB? Nov 19 00:18:08 Where do you think I can find some old code for a Grandstream H Nov 19 00:18:19 I wanted to change it to use it. Nov 19 00:18:27 Sure. Nov 19 00:19:33 H702 grandstream...this is the board/machine (VoIP). I thought I could attach it to my BBB but I am not sure yet. Nov 19 00:20:20 There are some connections but very few and no support. I looked on YouTube.com and found one manual worth lookin' at. Nov 19 00:21:03 Probably copywritten... Nov 19 00:23:54 I could only find a user manual. Boo! Nov 19 00:24:13 www.grandstream.com/sites/default/files/Resources/Release_HT702_1.0.8.2.zip Nov 19 00:24:36 Heh? Nov 19 00:24:41 Hold on...let me check it out. Nov 19 00:27:26 Well I was confused because the only thing I could find was the ht702... Nov 19 00:30:11 Uavcamm...what should I do with that .zip file? Nov 19 00:31:05 seems to be a firmware for ht702 device Nov 19 00:31:30 http://www.grandstream.com/support/firmware a h702 is not listed here Nov 19 00:31:40 not even a H series Nov 19 00:32:34 I should have listed it correctly. HT702. Sorry. Nov 19 00:33:53 then its a firmware for the device you have. Nov 19 00:36:03 Oh...did you get that .zip file from grandstream.com? Nov 19 00:36:20 I mean...I see you have. I could not find it. Nov 19 00:36:47 i googled "grandstream h702" - second hit Nov 19 00:38:21 Oh. I found a .bin file. Nov 19 00:39:25 Grandstream 'uses" gpl software but doesn't say what software it is... how odd. Nov 19 00:39:34 Errr! Nov 19 00:39:38 yes. pload it. more you will not get i think. couldnt find opensource code Nov 19 00:40:26 Those people created an empire and not avail. to the public. Nov 19 00:40:37 I will keep looking. Nov 19 00:40:40 if they use gpl2 code, i expecded busybox, hey must have some kind of open source repo somewhere Nov 19 00:43:43 so you have one of these? HT701/HT702/HT704 Analog Telephone Adaptor Nov 19 00:44:53 Yea...I bought one a while back. Nov 19 00:44:59 I forget from which company. Nov 19 00:45:17 But...that is the mfg. Nov 19 00:45:21 Grandstream. Nov 19 00:45:36 I found a bunch of text files. Nov 19 00:46:54 Oh...I just downloaded their GNU Public "whatever-it-is-called." Nov 19 00:47:14 it is a .gz file. Nov 19 00:48:44 7-Zip! Nov 19 01:28:42 Well funny thing about the Z 7z lzh etc. the actually are peoples names. Nov 19 01:30:19 eh? Nov 19 01:32:04 LZW etc are short for peoples names for example Z is oft short for a guy named Ziv L lempel W welch h hoffman. etc. Kind of funny how it ended that way. now some of the names are a bit odd like S - and F or Shano and Fano. (real names) Nov 19 01:32:25 interesting Nov 19 01:33:25 All of them are related to encoding schemes and compressions schemes. Mathematicians :D gotta love them. Nov 19 01:33:44 aye Nov 19 01:33:48 and the the google guys came and call thing weird... Nov 19 01:34:20 like "brotli" Nov 19 01:35:01 google guys are nothing but "S&M" people "sales and marketing" some call it I term it "gently" "slobbish masterbation" Nov 19 01:35:11 Okay...my HT702 has 12 holes for headers. Nov 19 01:35:22 I have the software. Nov 19 01:36:05 Now...how-to? How would I go about connecting the pins without the info. regarding the schematics? Nov 19 01:36:23 The holes for the headers are not listed. Nov 19 01:36:30 listed = labeled. Nov 19 01:36:34 How about the user manual? use google or yahoo "ht702 user manual" Nov 19 01:36:41 Oh. Nov 19 01:36:48 Sorry...I have one. I will check it again. Nov 19 01:37:54 looked under SOFTWARE UPGRADE Nov 19 01:38:00 :D Nov 19 01:38:56 anyhow ... Google has apparently had difficulty recruiting good people the last 10 years. They also are loosing top talent "doing other things". STill their engineering section stuff is pretty good. Nov 19 01:38:58 heh. Think its time to zz here .. nn all .. happy hacking! Nov 19 01:39:34 heh happen thanksgiving if your celebrate it. :D if not enjoy your family for a change? :D Nov 19 01:45:55 Nope...the manual has no info. on these holes. Nov 19 01:52:05 It is like two TTL to USB holes for programming. Nov 19 01:52:15 I guess...yikes. Nov 19 02:14:36 hello hello Nov 19 02:14:41 there is some one? Nov 19 02:15:44 does some one have some experience with debian and wifi module? Nov 19 02:18:03 Hello... Nov 19 02:18:16 apt-get install wifi? Nov 19 02:20:14 there is a Debian-Handbook.pdf out there. Nov 19 02:20:17 Check it out. Nov 19 02:21:31 https://debian-handbook.info/get/ Nov 19 02:22:00 That link goes directly to the page online where you can get the handbook...they have older versions and Jessie. Nov 19 02:25:08 apt-get install mt7601-sta-dkms Nov 19 02:25:23 when i try to run this apt-get install mt7601-sta-dkms Nov 19 02:25:35 it's say to me that is already installed Nov 19 02:25:49 if i make lsusb i see the module Nov 19 02:26:10 what do you want to do to the module? Nov 19 02:26:34 i'm running the kernel 4.3 Nov 19 02:26:42 use it :D Nov 19 02:26:53 use the wifi Nov 19 02:27:09 so just connect to my local wifi lan Nov 19 02:27:12 what os? Nov 19 02:27:16 mt7601-sta-dkms ls will show you the files and you can change them. Nov 19 02:27:30 wich file? Nov 19 02:27:56 answer uavcamm first. She knows a lot more than me. Nov 19 02:28:24 ok :) Nov 19 02:28:34 i'm using debian Nov 19 02:28:49 i have updated the kernel to 4.3 Nov 19 02:29:00 ,on a beagle bone black, Nov 19 02:29:07 BBB! Nov 19 02:29:45 it incuded in 4.2 Nov 19 02:30:01 I got the dang Wheezy handbook. No wonder I am fronting on this assignment. Nov 19 02:30:08 Hold please... Nov 19 02:30:17 https://github.com/torvalds/linux/tree/master/drivers/net/wireless/mediatek/mt7601u Nov 19 02:30:24 perhaps build it again? Nov 19 02:30:43 the dongle is not working at all? Nov 19 02:30:57 the dongle? Nov 19 02:31:12 isnt it a usb wifi thing? Nov 19 02:31:20 yes Nov 19 02:31:33 if make lsusb i see it Nov 19 02:32:22 do you see it with "ip link show" ? Nov 19 02:32:59 or "ls /sys/class/net" ? Nov 19 02:33:25 Bus 001 Device 003: ID 148f:7601 Ralink Technology, Corp. Nov 19 02:33:30 this is what i see Nov 19 02:34:13 should work. driver for that was included in 4.2 Nov 19 02:34:37 how can i check if there are the driver? Nov 19 02:38:09 lsmod Nov 19 02:38:37 see if the driver is laoded Nov 19 02:39:16 should i see something like this mt7601 right? Nov 19 02:40:47 uavcamm...what page are you reading online or what text do you have? Nov 19 02:41:27 I read out of the book, previously Wheezy, in .pdf format. Nov 19 02:41:47 I am trying to find better sources for specific info. Nov 19 02:42:16 right elaray Nov 19 02:42:24 i use my memories set... Nov 19 02:42:35 there is nothig about it Nov 19 02:42:44 Oh. Nov 19 02:42:52 I use the book and the wiki still. Nov 19 02:47:03 https://wiki.debian.org/Manual-Howto Nov 19 02:47:28 601 Nov 19 02:49:43 https://wiki.debian.org/DebianEeePC/HowTo/Wifi Nov 19 02:49:46 Does that help? Nov 19 02:52:44 https://packages.debian.org/jessie/wireless-tools Nov 19 02:52:48 That may help too! Nov 19 02:53:34 https://wiki.debian.org/it/rt2800usb Nov 19 02:53:48 i have also follwed this guide **** ENDING LOGGING AT Thu Nov 19 02:59:58 2015