date:20160720

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.

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

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 list. 
I defined it as follows:-

#define AT86RF2XX_PARAMS_BOARD {
.spi = SPI_0, \ 
.spi_speed = SPI_SPEED_5MHZ, \ 
.cs_pin = GPIO_PIN(PORT_A, 0), \ 
.int_pin = GPIO_PIN(PORT_E, 0), \ 
.sleep_pin = GPIO_PIN(PORT_E, 1), \ 
.reset_pin = GPIO_PIN(PORT_E, 2)}

After reading the thread that Peter referred to, I checked the file 
"/boards/stm32f4discovery/include/board.h" and saw that there is an overlap on 
PA0:-

#define BTN_B1_PIN  GPIO_PIN(PORT_A, 0)

The reason I defined AT86RF2XX_PARAMS_BOARD as above is the link 
https://github.com/RIOT-OS/RIOT/wiki/Board%3A-STM32F4discovery where a picture 
of the STM32F4DISCOVERY board shows the different pins. I just assumed that 
GPIO_0 (PA0), GPIO_1 (PE0), GPIO_2 (PE1), GPIO_3 (PE2), as shown in the 
picture, are not connected to anything and hence free to use. My assumption was 
obviously wrong.

I will fix my pin configuration tomorrow and see if it works for me. Thanks for 
your replies. You guys are really helpful.

Regards,
Adeel

> -Original Message-
> From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Peter
> Kietzmann
> Sent: Wednesday, July 20, 2016 4:48 PM
> To: RIOT OS kernel developers
> Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233
> 
> 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 based on the stm32f4discovery board it should be configured already
> > which makes me think there might still be some nit in your SPI connection.
> >
> > You could try to issue `ifconfig set addr `. If you then do
> > `ifconfig` again and nothing changed I guess it would be the SPI
> > connection. Else you might miss some configuration still.
> >
> > Best, Thomas
> >
> > On 20 Jul 2016, at 15:16 CEST(+0200), Adeel Mohammad Malik wrote:
> >
> >> 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  Channel: 0  Page: 0  NID: 0x0
> >>Long HWaddr: 00:00:00:00:00:00:00:00
> >>TX-Power: -17dBm  State: IDLE  max. Retrans.: 15
> >>
> >>Source address length: 2
> >>
> >> Iface  4   HWaddr: 00:15:01:00:40:e4
> >>
> >>Source address length: 6
> >>
> >> I was expecting to see a valid HWaddr but this doesn't look right.
> >> Should I be able to see a HWaddr if the connection is alright?
> >>
> >> /Adeel
> >>
> >>> -Original Message-
> >>> From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Thomas
> >>> Eichinger
> >>> Sent: Wednesday, July 20, 2016 2:17 PM
> >>> To: RIOT OS kernel developers
> >>> Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233
> >>>
> >>> 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 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 enough to connect
>  SCK, MISO and MOSI? Or should I also connect SS?
> >>> What you refer to as SS (Slave Select) is called CS (Chip Select) in
> >>> RIOT. So yes, you have to connect this pin too to actually activate
> >>> the slave's SPI interface.
> >>>
> 
>  * I see that the file
>  https://github.com/RIOT-
> >>> OS/RIOT/blob/master/drivers/at86rf2xx/include/at86rf2xx_params.h
>  has some PIN configuration parameters. What is
> AT86RF2XX_PARAM_CS?
>  Looking at the manual for my AT86RF233 board
>  (http://www.atmel.com/Images/Atmel-Wireless-ATZB-X-233-
> >>> XPRO_design_documentation.PDF),
>  on page 3 I see the RESET (AT86RF2XX_PARAM_RESET), SLP_TR
>  (AT86RF2XX_PARAM_SLEEP) and the IRQ (AT86RF2XX_PARAM_INT)
> pins. I
> >>> do
>  not seem to find the corresponding pin for AT86RF2XX_PARAM_CS.
> Any
>  clues?
> >>> See above.
> >>>
> 
>  * Should I include anything

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 based on the stm32f4discovery board it should be configured already
which makes me think there might still be some nit in your SPI connection.

You could try to issue `ifconfig set addr `. If you then do
`ifconfig` again and nothing changed I guess it would be the SPI
connection. Else you might miss some configuration still.

Best, Thomas

On 20 Jul 2016, at 15:16 CEST(+0200), Adeel Mohammad Malik wrote:


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  Channel: 0  Page: 0  NID: 0x0
   Long HWaddr: 00:00:00:00:00:00:00:00
   TX-Power: -17dBm  State: IDLE  max. Retrans.: 15

   Source address length: 2

Iface  4   HWaddr: 00:15:01:00:40:e4

   Source address length: 6

I was expecting to see a valid HWaddr but this doesn't look right.
Should I be able to see a HWaddr if the connection is alright?

/Adeel


-Original Message-
From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Thomas
Eichinger
Sent: Wednesday, July 20, 2016 2:17 PM
To: RIOT OS kernel developers
Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

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 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 enough to connect
SCK, MISO and MOSI? Or should I also connect SS?

What you refer to as SS (Slave Select) is called CS (Chip Select) in
RIOT. So
yes, you have to connect this pin too to actually activate the
slave's SPI
interface.



* I see that the file
https://github.com/RIOT-

OS/RIOT/blob/master/drivers/at86rf2xx/include/at86rf2xx_params.h

has some PIN configuration parameters. What is AT86RF2XX_PARAM_CS?
Looking at the manual for my AT86RF233 board
(http://www.atmel.com/Images/Atmel-Wireless-ATZB-X-233-

XPRO_design_documentation.PDF),

on page 3 I see the RESET (AT86RF2XX_PARAM_RESET), SLP_TR
(AT86RF2XX_PARAM_SLEEP) and the IRQ (AT86RF2XX_PARAM_INT) pins. I

do

not seem to find the corresponding pin for AT86RF2XX_PARAM_CS. Any
clues?

See above.



* Should I include anything besides USEMODULE += at86rf2xx to
be able to use the transceiver?

In your particular case you will want to include `USEMODULE +=
at86rf233`.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


--
Peter Kietzmann

Hamburg University of Applied Sciences
Dept. Informatik, Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49-40-42875-8426
Web: http://www.haw-hamburg.de/inet
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Thomas Eichinger


Hi Adeel,

the transceiver uses the cpuid module to generate hwaddr. If your port 
is based on the stm32f4discovery board it should be configured already 
which makes me think there might still be some nit in your SPI 
connection.


You could try to issue `ifconfig set addr `. If you then do 
`ifconfig` again and nothing changed I guess it would be the SPI 
connection. Else you might miss some configuration still.


Best, Thomas

On 20 Jul 2016, at 15:16 CEST(+0200), Adeel Mohammad Malik wrote:


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  Channel: 0  Page: 0  NID: 0x0
   Long HWaddr: 00:00:00:00:00:00:00:00
   TX-Power: -17dBm  State: IDLE  max. Retrans.: 15

   Source address length: 2

Iface  4   HWaddr: 00:15:01:00:40:e4

   Source address length: 6

I was expecting to see a valid HWaddr but this doesn't look right. 
Should I be able to see a HWaddr if the connection is alright?


/Adeel


-Original Message-
From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Thomas
Eichinger
Sent: Wednesday, July 20, 2016 2:17 PM
To: RIOT OS kernel developers
Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

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 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 enough to connect
SCK, MISO and MOSI? Or should I also connect SS?
What you refer to as SS (Slave Select) is called CS (Chip Select) in 
RIOT. So
yes, you have to connect this pin too to actually activate the 
slave's SPI

interface.



* I see that the file
https://github.com/RIOT-

OS/RIOT/blob/master/drivers/at86rf2xx/include/at86rf2xx_params.h

has some PIN configuration parameters. What is AT86RF2XX_PARAM_CS?
Looking at the manual for my AT86RF233 board
(http://www.atmel.com/Images/Atmel-Wireless-ATZB-X-233-

XPRO_design_documentation.PDF),

on page 3 I see the RESET (AT86RF2XX_PARAM_RESET), SLP_TR
(AT86RF2XX_PARAM_SLEEP) and the IRQ (AT86RF2XX_PARAM_INT) pins. I

do

not seem to find the corresponding pin for AT86RF2XX_PARAM_CS. Any
clues?

See above.



* Should I include anything besides USEMODULE += at86rf2xx 
to

be able to use the transceiver?

In your particular case you will want to include `USEMODULE +=
at86rf233`.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

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  Channel: 0  Page: 0  NID: 0x0
   Long HWaddr: 00:00:00:00:00:00:00:00 
   TX-Power: -17dBm  State: IDLE  max. Retrans.: 15 
   
   Source address length: 2
   
Iface  4   HWaddr: 00:15:01:00:40:e4 
   
   Source address length: 6

I was expecting to see a valid HWaddr but this doesn't look right. Should I be 
able to see a HWaddr if the connection is alright?

/Adeel

> -Original Message-
> From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Thomas
> Eichinger
> Sent: Wednesday, July 20, 2016 2:17 PM
> To: RIOT OS kernel developers
> Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233
> 
> 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 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 enough to connect
> > SCK, MISO and MOSI? Or should I also connect SS?
> What you refer to as SS (Slave Select) is called CS (Chip Select) in RIOT. So
> yes, you have to connect this pin too to actually activate the slave's SPI
> interface.
> 
> >
> > * I see that the file
> > https://github.com/RIOT-
> OS/RIOT/blob/master/drivers/at86rf2xx/include/at86rf2xx_params.h
> > has some PIN configuration parameters. What is AT86RF2XX_PARAM_CS?
> > Looking at the manual for my AT86RF233 board
> > (http://www.atmel.com/Images/Atmel-Wireless-ATZB-X-233-
> XPRO_design_documentation.PDF),
> > on page 3 I see the RESET (AT86RF2XX_PARAM_RESET), SLP_TR
> > (AT86RF2XX_PARAM_SLEEP) and the IRQ (AT86RF2XX_PARAM_INT) pins. I
> do
> > not seem to find the corresponding pin for AT86RF2XX_PARAM_CS. Any
> > clues?
> See above.
> 
> >
> > * Should I include anything besides USEMODULE += at86rf2xx to
> > be able to use the transceiver?
> In your particular case you will want to include `USEMODULE +=
> at86rf233`.
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[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
timer and to generate interrupts without the CPU freezing at all.

Although I've setup the timer to be 16-bit@1MhZ (using a 48MhZ clock with a
prescaler of 48), everything goes to hell whenever I try to use x-timer on
top of my driver. One of the major issue seems to come from the prescaler
value.

For example in xtimer_drift, the CPU freezes immediately with 16-bit@(48MhZ
/ 48)

2016-07-20 15:08:24,522 - INFO #  ===
2016-07-20 15:08:24,524 - INFO #  = Test begins =
2016-07-20 15:08:24,526 - INFO #  ===
2016-07-20 15:08:24,528 - INFO # Starting thread 3
2016-07-20 15:08:24,530 - INFO # sending 1st msg
2016-07-20 15:08:24,612 - INFO # sending 2nd msg
2016-07-20 15:08:24,614 - INFO # Starting thread 4
2016-07-20 15:08:24,615 - INFO # sending 3rd msg
2016-07-20 15:08:24,698 - INFO # sending 4th msg
**FREEZE**

However with any prescaler value above 63 the test doesn't get stuck and
the time is running, albeit much faster that it should.

Does anyone have an idea regarding the origin of this behavior? Is there
something more that I need to setup in xtimer?

Best,

Florent
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

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 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 enough to connect 
SCK, MISO and MOSI? Or should I also connect SS?
What you refer to as SS (Slave Select) is called CS (Chip Select) in 
RIOT. So yes, you have to connect this pin too to actually activate the 
slave's SPI interface.




* I see that the file 
https://github.com/RIOT-OS/RIOT/blob/master/drivers/at86rf2xx/include/at86rf2xx_params.h 
has some PIN configuration parameters. What is AT86RF2XX_PARAM_CS? 
Looking at the manual for my AT86RF233 board 
(http://www.atmel.com/Images/Atmel-Wireless-ATZB-X-233-XPRO_design_documentation.PDF), 
on page 3 I see the RESET (AT86RF2XX_PARAM_RESET), SLP_TR 
(AT86RF2XX_PARAM_SLEEP) and the IRQ (AT86RF2XX_PARAM_INT) pins. I do 
not seem to find the corresponding pin for AT86RF2XX_PARAM_CS. Any 
clues?

See above.



* Should I include anything besides USEMODULE += at86rf2xx to 
be able to use the transceiver?
In your particular case you will want to include `USEMODULE += 
at86rf233`.

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[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 enough to connect SCK, MISO 
and MOSI? Or should I also connect SS?

* I see that the file 
https://github.com/RIOT-OS/RIOT/blob/master/drivers/at86rf2xx/include/at86rf2xx_params.h
 has some PIN configuration parameters. What is AT86RF2XX_PARAM_CS? Looking at 
the manual for my AT86RF233 board 
(http://www.atmel.com/Images/Atmel-Wireless-ATZB-X-233-XPRO_design_documentation.PDF),
 on page 3 I see the RESET (AT86RF2XX_PARAM_RESET), SLP_TR 
(AT86RF2XX_PARAM_SLEEP) and the IRQ (AT86RF2XX_PARAM_INT) pins. I do not seem 
to find the corresponding pin for AT86RF2XX_PARAM_CS. Any clues?

* Should I include anything besides USEMODULE += at86rf2xx to be able 
to use the transceiver?

Regards,
Adeel
___
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 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:
https://github.com/RIOT-OS/RIOT/wiki/FAQ#does-riot-supports-raspberry-pi

You could replace Raspberry PI with C.H.I.P. here.

@all: feel free to improve this answer or other parts of the FAQ.

Cheers,
Oleg
-- 
panic("Halt failed!");
linux-2.6.6/arch/sparc/kernel/process.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

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 regards,

Bas Stottelaar


2016-07-18 11:21 GMT+02:00 Bas Stottelaar :

> Hi Mathias,
>
> There are two chips: one is the board controller (for mbed-related stuff,
> virtual com, mass storage).
>
> The other is the actual chip, an EFR32MG1P132F256GM48 (as seen here:
> https://github.com/basilfx/EFM2Riot/blob/master/dist/doc/images/thunderboard_sense.png).
> That is, definitely a M4 with FPU.
>
> Kind regards,
>
> Bas Stottelaar
>
>
> 2016-07-18 10:45 GMT+02:00 Mathias Tausig <
> mathias.tau...@fh-campuswien.ac.at>:
>
>> Hy!
>>
>> Great that you already started working on it.
>> But I don't think that datasheet is quite accurate. The chip on the
>> backside of
>> the board states, that it is a Cortex-M3 processor, not an M4.
>>
>> On Mon, 2016-07-18 at 10:23 +0200, Bas Stottelaar wrote:
>> > Hi Mathias,
>> >
>> > I managed to get it working, based on the SLSTK3401a. I was lucky that
>> it
>> > shared the same pinout regarding the RX/TX. The reference manual and
>> > datasheet are available. I put the links in here:
>> >
>> https://github.com/basilfx/EFM2Riot/blob/master/dist/doc/Thunderboard%20Sense
>> .
>> > md
>> >
>> >
>> > You can find my PR here: https://github.com/RIOT-OS/RIOT/pull/5652.
>> Since I
>> > also work on other EFM32 targets, I have more to see here:
>> > https://github.com/basilfx/EFM2Riot.
>> >
>> > I don't have a driver for the radio. I leave that (the actual
>> challenge) up
>> > to who wants to win the hoodie :-)
>> >
>> > Kind regards,
>> >
>> > Bas Stottelaar
>> >
>> >
>> > 2016-07-18 10:15 GMT+02:00 Mathias Tausig <
>> > mathias.tau...@fh-campuswien.ac.at>:
>> >
>> > >
>> > > Hy!
>> > >
>> > > Does anyone have a link to the specification (or even some sort of
>> > > dccumentation) for the Silicon Labs microcontroller that was handed
>> out on
>> > > Friday at the summit? Unfortunately, the silabs website knows no
>> product
>> > > of that
>> > > name or part number.
>> > >
>> > > cheers
>> > > Mathias
>> > >
>> > > --
>> > > DI Mathias Tausig,
>> > > Kompetenzzentrum für IT-Security,
>> > >
>> > > FH Campus Wien,
>> > > Informationstechnologien und Telekommunikation.
>> > >
>> > > Favoritenstrasse 226, Raum B.2.18,
>> > > 1100 Wien, Austria.
>> > > T: +43 1 606 68 77-2142, F: +43 1 606 68 77-2139.
>> > > mathias.tau...@fh-campuswien.ac.at
>> > > PGP Key-ID: 75656BBF
>> > >
>> > > ___
>> > > devel mailing list
>> > > devel@riot-os.org
>> > > https://lists.riot-os.org/mailman/listinfo/devel
>> > >
>> > >
>> > ___
>> > devel mailing list
>> > devel@riot-os.org
>> > https://lists.riot-os.org/mailman/listinfo/devel
>> --
>> DI Mathias Tausig,
>> Kompetenzzentrum für IT-Security,
>>
>> FH Campus Wien,
>> Informationstechnologien und Telekommunikation.
>>
>> Favoritenstrasse 226, Raum B.2.18,
>> 1100 Wien, Austria.
>> T: +43 1 606 68 77-2142, F: +43 1 606 68 77-2139.
>> mathias.tau...@fh-campuswien.ac.at
>> PGP Key-ID: 75656BBF
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
___
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 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
>
>
___
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 Oleg Hahm

Hi Arash!

On Wed, Jul 20, 2016 at 10:29:07AM +0200, Arash Shafiei wrote:
> Hi, I was wondering if there is any plan to support C.H.I.P ?
> 
> https://getchip.com/pages/chip

That looks more like a Linux-class device than one for RIOT.

Cheers,
Oleg
-- 
printk("What? oldfid != cii->c_fid. Call 911.\n");
linux-2.4.3/fs/coda/cnode.c


signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[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] Connecting STM32F4Discovery & AT86RF233

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

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

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

[riot-devel] Connecting STM32F4Discovery & AT86RF233

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

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

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

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

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

13 matches

Site Navigation

Mail list logo

Footer information