[riot-devel] C.H.I.P

2016-07-20 Thread Arash Shafiei
Hi, I was wondering if there is any plan to support C.H.I.P ? https://getchip.com/pages/chip ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] C.H.I.P

2016-07-20 Thread Emmanuel Baccelli
Hi Arash, at first sight Linux can run on C.H.I.P. So why not use Linux? RIOT targets devices which cannot run Linux (or derivatives/equivalents). Hence: there are no plans to support CHIP best, Emmanuel On Wed, Jul 20, 2016 at 10:29 AM, Arash Shafiei wrote: > Hi, I was

Re: [riot-devel] Silicon Labs Microcontroller handed out at summit

2016-07-20 Thread Bas Stottelaar
Hi all, No official documentation yet, but I just found this link: https://www.mit.bme.hu/system/files/oktatas/targyak/9979/Silabs_Wireless_Gecko_MIT.pdf. Page 32 describes all the sensors. Seems like the part number/name is SLTB001A, and Thunderboard Sense is just the marketing name. Kind

Re: [riot-devel] C.H.I.P

2016-07-20 Thread Oleg Hahm
Hi! On Wed, Jul 20, 2016 at 10:36:09AM +0200, Emmanuel Baccelli wrote: > at first sight Linux can run on C.H.I.P. > So why not use Linux? > RIOT targets devices which cannot run Linux (or derivatives/equivalents). > Hence: there are no plans to support CHIP I added a point to the FAQ:

[riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Adeel Mohammad Malik
Hi all, I am struggling a bit to understand how to connect my STM32F4Discovery board with my AT86RF233 ZigBit Xplained Pro Extension board (http://www.atmel.com/tools/ATZB-X-233-XPRO.aspx). I have a few questions that I list as follows:- * When connecting the SPI interface, is it

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Adeel Mohammad Malik
Hi Thomas, I did as you said. I have 9 wires connected between my STM32F4Discovery board and the AT86RF233 ZigBit Xplained Pro Extension board. 4 SPI wires, 3 GPIO wires and 2 for power (+3.3V and GND). Now doing an "ifconfig" gives me the following result:- ifconfig Iface 3 HWaddr: 00:00

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Thomas Eichinger
Hi Adeel, please see my answers inline. I hope this helps, let us know if there is further open questions. Best, Thomas On 20 Jul 2016, at 13:46 CEST(+0200), Adeel Mohammad Malik wrote: Hi all, I am struggling a bit to understand how to connect my STM32F4Discovery board with my AT86RF233

[riot-devel] [xtimer] [cc2650] Use of xtimer on top of driver causes havoc

2016-07-20 Thread Florent-Valéry Coen
Hi everyone, I'm currently working on fixing the buggy timer of the CC2650. The driver I rewrote seems to be working fine when used on its own: I'm able to set a period for the

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Peter Kietzmann
Hi, just as a side note: @Nordzisko has a pretty similar setup wich worked (except the button issue) https://github.com/RIOT-OS/RIOT/issues/5407 Best Peter Am 20.07.2016 um 16:22 schrieb Thomas Eichinger: Hi Adeel, the transceiver uses the cpuid module to generate hwaddr. If your port is

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Adeel Mohammad Malik
Hi Peter and Thomas, I was quite skeptical about my pin connections/configurations. I did realize that the default pin mapping of the Atmel driver could be a problem so I had already defined my own pin mapping in the file "/boards/stm32f4discovery/include/board.h" before writing to the mailing

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Thomas Eichinger
Adeel, we're happy to help and please keep us posted about your progress. Best, Thomas On 20 Jul 2016, at 18:33 CEST(+0200), Adeel Mohammad Malik wrote: I will fix my pin configuration tomorrow and see if it works for me. Thanks for your replies. You guys are really helpful.