Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-08-04 Thread Adeel Mohammad Malik
-Original Message- > From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Thomas > Eichinger > Sent: Thursday, August 04, 2016 3:17 PM > To: RIOT OS kernel developers > Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233 > > Hi Ade

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-08-04 Thread Thomas Eichinger
Hi Adeel, you could try to add a printf() in the `spi_transfer_byte` function in stm32f4/periph/spi.c for the `in` pointer and see if there are reasonable values shown - to make sure SPI communication is working. Best, Thomas On 3 Aug 2016, at 19:24 CEST(+0200), Adeel Mohammad Malik wrote:

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-08-04 Thread Peter Kietzmann
...@riot-os.org] On Behalf Of Peter Kietzmann Sent: Thursday, August 04, 2016 11:44 AM To: RIOT OS kernel developers Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233 Hi Adeel, please note that issue #5407 is about the F3 discovery so the pin configuration might differ. I conne

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-08-04 Thread Adeel Mohammad Malik
hard to troubleshoot. /Adeel > -Original Message- > From: devel [mailto:devel-boun...@riot-os.org] On Behalf Of Peter > Kietzmann > Sent: Thursday, August 04, 2016 11:44 AM > To: RIOT OS kernel developers > Subject: Re: [riot-devel] Connecting STM32F4Discovery & A

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-08-04 Thread Peter Kietzmann
?tab=overview). This could possibly be the problem. /Adeel -Original Message- From: Adeel Mohammad Malik Sent: Wednesday, August 03, 2016 7:24 PM To: RIOT OS kernel developers Subject: RE: [riot-devel] Connecting STM32F4Discovery & AT86RF233 Hi Peter, What PIN configuration do you

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-08-04 Thread Adeel Mohammad Malik
; From: Adeel Mohammad Malik > Sent: Wednesday, August 03, 2016 7:24 PM > To: RIOT OS kernel developers > Subject: RE: [riot-devel] Connecting STM32F4Discovery & AT86RF233 > > Hi Peter, > > What PIN configuration do you use with AT86RF233? I went through the > thread http

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-08-03 Thread Adeel Mohammad Malik
/include/at86rf2xx_registers.h#L38. /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 &

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-27 Thread Peter Kietzmann
AM To: RIOT OS kernel developers Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233 Hi Adeel, not sure I fully understand you previous mail. The driver will generate a default hardware address which is based on the CPUID. USEMODULE += at86rf233 AFAIK one of these mod

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-27 Thread Adeel Mohammad Malik
Kietzmann > Sent: Wednesday, July 27, 2016 10:25 AM > To: RIOT OS kernel developers > Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233 > > Hi Adeel, > > not sure I fully understand you previous mail. The driver will generate a > default hardwar

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-25 Thread Peter Kietzmann
PM To: RIOT OS kernel developers Subject: RE: [riot-devel] Connecting STM32F4Discovery & AT86RF233 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

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-21 Thread Adeel Mohammad Malik
Makefile. /Adeel > -Original Message- > From: Adeel Mohammad Malik > Sent: Thursday, July 21, 2016 11:29 AM > To: 'RIOT OS kernel developers' > Subject: RE: [riot-devel] Connecting STM32F4Discovery & AT86RF233 > > Hi again, > > I just used the following pin

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.

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Adeel Mohammad Malik
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/R

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Peter Kietzmann
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

Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233

2016-07-20 Thread Adeel Mohammad Malik
M > 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 201

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