| 01:04.33 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 01:41.50 | *** join/#qi-hardware fengling (~fengling@111.198.29.53) |
| 02:36.46 | *** join/#qi-hardware archang (~archang@122.133.52.113.static.ximdns.com) |
| 02:41.59 | *** join/#qi-hardware wpwrak (~werner@59-132-231-201.fibertel.com.ar) |
| 02:42.14 | wpwrak | welcome back, world ! :) |
| 03:06.21 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 03:06.23 | *** join/#qi-hardware fengling (~fengling@111.198.29.53) |
| 03:40.14 | *** join/#qi-hardware atommann (~atommann@58.251.2.94) |
| 03:46.06 | *** join/#qi-hardware rjeffries (~rjeffries@pool-74-111-228-106.snloca.dsl-w.verizon.net) |
| 04:04.52 | *** join/#qi-hardware archang (~archang@122.133.52.113.static.ximdns.com) |
| 04:22.32 | wpwrak | (pronunciation of "wpwrak") i'd just pronounce it as if it was a regular german word. sounds bumpy and ugly, but given that it's mainly optimized for uniqueness, that ought to be fine :) |
| 04:56.09 | DocScrutinizer05 | err I fail to speak "wpwrak" |
| 04:56.39 | DocScrutinizer05 | 4 consonants :-o |
| 04:57.21 | DocScrutinizer05 | "wepewrak" would work |
| 04:57.30 | wpwrak | yeah, it's an effort to make it to he bonus vowel ;-) |
| 04:58.05 | DocScrutinizer05 | even wepwrak |
| 04:58.16 | wpwrak | maybe think of "wpwrak" as a stifled burp ;) |
| 04:58.21 | DocScrutinizer05 | "wp" is unspeakable |
| 04:58.56 | wpwrak | think "whip" and delete the "i" :) |
| 05:00.38 | DocScrutinizer05 | maybe provide a audio for the pronunciation |
| 05:02.53 | DocScrutinizer05 | on an unrelated topic I think I cought a slight cold in the night of tuesday to wednesday. which comes in handy for finishing the whole camp infra etc |
| 05:17.22 | wpwrak | indeed :) i'm kinda surprised i didn't get one of my own |
| 05:28.26 | *** join/#qi-hardware xiangfu (~xiangfu@111.198.29.54) |
| 06:00.46 | nicksydney | something cool to build http://imgur.com/a/DyQZL |
| 06:29.56 | DocScrutinizer05 | xiangfu: HI! |
| 06:30.09 | DocScrutinizer05 | hi! (sorry capslock) |
| 07:08.27 | *** join/#qi-hardware fengling (~fengling@111.198.29.53) |
| 08:08.38 | xiangfu | DocScrutinizer05: Hi |
| 08:12.06 | *** join/#qi-hardware pcercuei (~paul@p4FDE7823.dip0.t-ipconnect.de) |
| 09:02.22 | *** join/#qi-hardware jwhitmore (~jwhitmore@86-44-0-88-dynamic.agg2.cty.lmk-pgs.eircom.net) |
| 09:35.49 | *** join/#qi-hardware fengling (~fengling@111.198.29.53) |
| 10:02.21 | *** join/#qi-hardware wolfspraul (~wolfsprau@xd9ba0ef4.dyn.telefonica.de) |
| 10:46.58 | *** join/#qi-hardware ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 11:13.27 | *** join/#qi-hardware jwhitmore (~jwhitmore@213.233.149.7) |
| 11:52.01 | *** join/#qi-hardware FDCX (357@ceata/consiliu/FDCX) |
| 12:29.18 | *** join/#qi-hardware kanzure (~kanzure@unaffiliated/kanzure) |
| 13:30.41 | *** join/#qi-hardware FDCX (357@ceata/consiliu/FDCX) |
| 14:26.27 | *** join/#qi-hardware ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 16:03.08 | larsc | eintopf: so, you want a adf7242? |
| 17:26.44 | *** join/#qi-hardware xiangfu (~xiangfu@60.10.71.45) |
| 17:54.32 | *** join/#qi-hardware pcercuei (~pcercuei@ip5f5ac6c3.dynamic.kabel-deutschland.de) |
| 18:09.25 | eintopf | larsc: I got a offer that somebody will give me a adf7242, but I am also happy to maintain at86rf2xx and to work with mrf24jFOOBAR |
| 18:09.34 | eintopf | and of course work with atusb |
| 18:10.50 | eintopf | not important, I will keep to work with at86rf2xx, mrf24jFOOBAR and atusb. It's still hard to keep everything up-to-date to the recent mainline state |
| 18:11.01 | eintopf | so they have the latest greatest features |
| 18:12.03 | eintopf | http://www.spinics.net/lists/linux-wpan/msg02876.html |
| 18:12.11 | eintopf | here my work for the mrfj24FOOBAR |
| 18:12.22 | eintopf | I say foobar because I can't remember the last numbers |
| 18:13.16 | eintopf | mrf24j40 ist the transceiver |
| 18:13.31 | eintopf | but there exists mrf24j40ma and mrf24j40mc, etc some different boards |
| 18:13.37 | eintopf | with amplifier or not |
| 18:15.28 | larsc | eintopf: that somebody is boss, your adf7242 is on my desk, I'll ship it on monday |
| 18:15.34 | larsc | is my boss |
| 18:15.56 | eintopf | and why do you know my name >:-| |
| 18:16.35 | larsc | I expected it to be you |
| 18:17.27 | eintopf | does your company like to have the driver mainline? |
| 18:17.45 | larsc | sure |
| 18:17.57 | larsc | that was always the paln |
| 18:19.24 | eintopf | yea but mainline is also not quite now, it's better than when the project was linux-zigbee |
| 18:19.44 | eintopf | depends many people (inclusive myslef) have more effort to implement 6lowpan |
| 18:19.58 | eintopf | the address family 802.15.4 is still somewhat broken at some places |
| 18:20.09 | eintopf | but we working on this |
| 18:20.21 | eintopf | the project grabs now some frameworks from wireless |
| 18:23.17 | eintopf | larsc: how easily is it to connect some wires on the transceiver? |
| 18:23.28 | eintopf | does it has some female connecters |
| 18:23.32 | eintopf | connectors |
| 18:23.46 | eintopf | I don't want to solder here much |
| 18:23.54 | eintopf | and I am very bad in soldering |
| 18:24.39 | larsc | it's a male header |
| 18:25.38 | larsc | what baseboard do you want to use? |
| 18:28.05 | eintopf | I have some beaglebones here and raspberry pi's |
| 18:28.10 | eintopf | and I have wires |
| 18:28.20 | larsc | we tested it ith the pi |
| 18:28.22 | eintopf | in diffent colors male<->male, female<->male |
| 18:28.52 | larsc | you'll need 7 wires. 4 for SPI, a interrupt and VCC and GND |
| 18:29.23 | eintopf | VCC is 3.3? |
| 18:29.51 | larsc | yes |
| 18:30.27 | eintopf | and when I have other questions to things what the datasheet doesn't say anything. I can ask you? |
| 18:30.34 | larsc | sure |
| 18:30.38 | larsc | http://media.digikey.com/Photos/Analog%20Devices%20Photos/EVAL-ADF7242-PMDZ.JPG |
| 18:32.03 | eintopf | this looks beautiful |
| 18:32.37 | eintopf | the most people @linux-wpan use these transceivers http://openlabs.co/store/Raspberry-Pi-802.15.4-radio |
| 18:32.55 | eintopf | I think the price is 1 cent cheaper each day |
| 18:33.29 | eintopf | and currently I think this man need to produce many of them because - https://lists.riot-os.org/pipermail/devel/2015-August/002858.html |
| 18:33.56 | eintopf | but the price is okay |
| 18:34.25 | eintopf | I heard the eval board of adf7242 cost much |
| 18:34.41 | eintopf | never looked what it costs |
| 18:35.25 | eintopf | larsc: does the adf7242 have one frame buffer only? |
| 18:35.33 | eintopf | or seperate rx/tx buffer? |
| 18:35.46 | eintopf | need to look |
| 18:36.13 | larsc | no idea to be honest |
| 18:36.46 | eintopf | a separate |
| 18:36.49 | eintopf | that's good |
| 18:37.17 | eintopf | the at86rf2xx have one only, I expierence improvements at mrf24j40 |
| 18:37.34 | eintopf | mrf24j40 has also separate rx/tx buffer |
| 18:39.28 | eintopf | ah cca mode 1 only |
| 18:39.30 | eintopf | okay |
| 18:41.07 | eintopf | yea, datasheets looks okay |
| 18:41.21 | eintopf | I am sure I have question when I look again into it |
| 18:42.40 | eintopf | larsc: and can I have the source for the firmware? :-) |
| 18:42.55 | eintopf | no, little joke :( |
| 18:43.47 | larsc | probably not |
| 18:43.50 | larsc | I don't have it either |
| 18:44.18 | larsc | we are unworthy software developers ;) |
| 18:46.42 | eintopf | mhh, where are the register settings for the address filter |
| 18:46.49 | eintopf | maybe I should lookup it in the current driver |
| 18:48.15 | eintopf | doesn't described inside the datasheet but driver use 0x116 |
| 18:48.31 | eintopf | base address 0x116 for the extended address |
| 18:51.09 | eintopf | I think I have not the _real_ for internal use datasheet ;-) |
| 18:51.26 | larsc | this is the latest version of the driver https://github.com/analogdevicesinc/linux/blob/xcomm_zynq/drivers/net/ieee802154/adf7242.c |
| 18:51.54 | eintopf | yes |
| 18:52.17 | eintopf | #define REG_IEEE_ADDR_0 0x116 |
| 18:52.27 | eintopf | this isn't described in my version of datasheet |
| 18:52.48 | eintopf | Rev. 0 |
| 18:53.07 | eintopf | http://www.analog.com/en/products/rf-microwave/integrated-transceivers-transmitters-receivers/low-power-rf-transceivers/adf7242.html |
| 18:54.01 | larsc | All I have is what is on the public website |
| 18:54.32 | pcercuei | it's a fake register IIRC |
| 18:54.36 | pcercuei | handled by the firmware |
| 18:55.27 | eintopf | hmpf |
| 18:57.59 | eintopf | so the datasheet doesn't represent the current available firmware? |
| 18:59.06 | pcercuei | 0x116 is for the 64-bit address |
| 18:59.16 | eintopf | http://www.analog.com/media/en/technical-documentation/application-notes/AN-1082.pdf |
| 18:59.22 | eintopf | ahh here is the right document |
| 18:59.24 | pcercuei | yeah. I don't know where that info actually comes from. |
| 18:59.32 | eintopf | register map extensions |
| 19:00.13 | eintopf | okay |
| 19:00.24 | eintopf | I will put that to my materials |
| 19:00.25 | pcercuei | ah, great |
| 19:01.45 | pcercuei | also, I'm pretty sure that the chip can work without any firmware |
| 19:02.39 | pcercuei | (and then the advanced features are not available) |
| 19:05.16 | eintopf | address filtering is also only a optional feature |
| 19:05.20 | eintopf | to reduce workload |
| 19:05.32 | eintopf | I think I will have more question when I work on it :/ |
| 19:06.21 | eintopf | also question is for me if the transceiver automatically detects if acknowledge request bit is set and waiting after transmit for an ack |
| 19:06.40 | eintopf | or I need to go into some special state or do I need set some register bit for that |
| 19:18.23 | eintopf | a great |
| 19:18.30 | eintopf | the transceiver will do that automatically |
| 19:19.13 | eintopf | <PROTECTED> |
| 19:19.14 | eintopf | frame is expected following the transmission. |
