-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 Adeel,
>
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:
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 & AT86RF233
Hi Adeel,
please note that issue #5407 is about the F3 discovery so the pin
configuration might differ.
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
.aspx?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 d
; 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
/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 &
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 module
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
] On Behalf Of Peter
Kietzmann
Sent: Monday, July 25, 2016 8:40 AM
To: RIOT OS kernel developers
Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233
Hi Adeel,
generation of the CPUID shouldn't be a problem. I checked it on an
stm32f4discovery board. Can you try it with exampl
nn
> Sent: Monday, July 25, 2016 8:40 AM
> To: RIOT OS kernel developers
> Subject: Re: [riot-devel] Connecting STM32F4Discovery & AT86RF233
>
> Hi Adeel,
>
> generation of the CPUID shouldn't be a problem. I checked it on an
> stm32f4discovery board. Ca
kernel developers'
Subject: RE: [riot-devel] Connecting STM32F4Discovery & AT86RF233
Hi again,
I just used the following pin configuration for the AT86RF233 transceiver
now:-
#define AT86RF2XX_PARAMS_BOARD {
.spi = SPI_0, \
.spi_speed = SPI_SPEED_5MHZ, \
.cs_pin =
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 foll
anks
> 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
> >
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.
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
ehalf 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,
right?
/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
: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 Ju
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
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 eno
21 matches
Mail list logo