Re: [riot-devel] Status of the MRF24J40 radio module support
Hello Peter,
sorry for the mistake - Frederic? I thought about Tobias Fredersdorf.
Here is my hint about the hardware access to the MRF24J40.
The SPI-Interface of the MRF24J40 is a little bit tricky.
If you take a look onto the diagram of the chip datasheet (chapter
2.14.2) you see that the bit which makes the decision between read and
right access is not on a 8bit border but rather in the middle if you
have a SPI-controller which is 8bit oriented.
Therefore you have to introduce a MRF24J40_ACCESS_WRITE_LONG bit to set
the write bit correct.
/**
* @brief SPI access specifiers
*@{
*/
#define MRF24J40_SHORT_ADDR_TRANS (0x00)
#define MRF24J40_LONG_ADDR_TRANS (0x80)
#define MRF24J40_ACCESS_READ (0x00)
#define MRF24J40_ACCESS_WRITE(0x01)
#define MRF24J40_ACCESS_WRITE_LONG (0x10)
#define MRF24J40_ADDR_OFFSET (0x01)
/** @} */
void mrf24j40_reg_write_long(const mrf24j40_t *dev, const uint16_t addr,
const uint8_t value)
{
uint8_t reg1,reg2;
reg1 = MRF24J40_LONG_ADDR_TRANS | (addr>>3);
reg2 = (addr<<5) | MRF24J40_ACCESS_WRITE_LONG;
spi_acquire(dev->params.spi);
GPIOB->BRR = (1 << 12);
spi_transfer_byte(dev->params.spi, reg1, 0);
spi_transfer_byte(dev->params.spi, reg2, 0);
spi_transfer_byte(dev->params.spi, value, 0);
GPIOB->BSRR = (1 << 12);
spi_release(dev->params.spi);
}
Without this bit you will never achieve a working write access.
Best regards,
Neo
Am 22.07.2016 um 19:25 schrieb Peter Kietzmann:
Hi Neo,
the PR was closed because it was outdated but Tobias Fredersdorf
promised to open a new one with more up to date code -> so there is
more code but not available until now. I will meet him f2f in the next
week and report the status, in case there is no PR to await soon.
At the RIOT summit several people stated their interest and we agreed
on blocking that work about two more weeks for Tobias. In case there
is no progress, someone else will take this over (probably me).
Which hints do you have about hardware access?
And who is Frederic? At least I'm not aware to be his follower.
Best regards
Peter
Am 22.07.2016 um 12:54 schrieb Neo:
Hello developers,
in the comments of the Pull-Request 5099 it seems that Tobias
Fredersdorf stops now his efford in implementing the MRF24J40 driver.
What is the status of the MRF24J40 driver development? Is there more
code available as stored in GitHub?
If not - I have some additional important hints about that driver
(depending especially the hardware access of this radio chip).
Who will be the follower of Frederic? Is it Peter Kietzmann?
Best regards
Neo
___
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] Hack'n'ACK July 2016
Hi, Unfortunately, I won't be available tomorrow. It will be for next time. Cheers, Alex - Mail original - > Hi, > tomorrow we have our monthly Hack'n'ACK again. Oleg and I will most > likely sit together at FU Berlin and are happy about any other dev > from Berlin that likes to join. Hamburg & Saclay are you holding a > Hack'n'ACK at your location, too? > > Cheers, > Martine > ___ > 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] Hack'n'ACK July 2016
Hi, yes we will. So let's set up a PlaceCam session as usual. I propose you initiate the call, as it as proven this way. Best Peter Am 25.07.2016 um 15:39 schrieb Martine Lenders: Hi, tomorrow we have our monthly Hack'n'ACK again. Oleg and I will most likely sit together at FU Berlin and are happy about any other dev from Berlin that likes to join. Hamburg & Saclay are you holding a Hack'n'ACK at your location, too? Cheers, Martine ___ 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
[riot-devel] Hack'n'ACK July 2016
Hi, tomorrow we have our monthly Hack'n'ACK again. Oleg and I will most likely sit together at FU Berlin and are happy about any other dev from Berlin that likes to join. Hamburg & Saclay are you holding a Hack'n'ACK at your location, too? Cheers, Martine ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
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 examples/gnrc_networking?
"ifconfig" works there as well.
The f4 board usually has no network interface and now you're about to
initialize two. I could imagine it's just a configuration problem but to
be sure, please check gnrc_networking first.
Best
Peter
Am 21.07.2016 um 12:11 schrieb Adeel Mohammad Malik:
Hi again,
I think I got the SPI connection right now. I just configured an address using
ifconfig and was able to change the address. I am still not getting an address
automatically which as Thomas mentioned I should be getting using the cupid
module. Seems like I am missing a module in my 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 configuration for the AT86RF233 transceiver
now:-
#define AT86RF2XX_PARAMS_BOARD {
.spi = SPI_0, \
.spi_speed = SPI_SPEED_5MHZ, \
.cs_pin = GPIO_PIN(PORT_E, 0), \
.int_pin = GPIO_PIN(PORT_E, 1), \
.sleep_pin = GPIO_PIN(PORT_E, 2), \
.reset_pin = GPIO_PIN(PORT_E, 3)}
I still have the same problem. I have the following relevant modules included
in my Makefile:-
...
USEMODULE += gnrc_netdev_default
USEMODULE += auto_init_gnrc_netif
GNRC_NETIF_NUMOF := 2
USEMODULE += ethos gnrc_netdev2
CFLAGS += '-DETHOS_UART=UART_DEV(0)' -DETHOS_BAUDRATE=115200 -
DUSE_ETHOS_FOR_STDIO USEMODULE += at86rf233 ...
Any hints/clues would be appreciated.
/Adeel
-Original Message-
From: Adeel Mohammad Malik
Sent: Wednesday, July 20, 2016 6:33 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 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
Re: [riot-devel] ADC on SAMR21-xpro (Alessandro Nicoli)
Hi Alessandro, you're pretty much welcome! Even though I didn't do that much. Do you think you could open a PR with this ADC driver implementation? Best Peter Am 23.07.2016 um 11:50 schrieb ALESSANDRO NICOLI: Hi all, I've successfully put in work the ADC module on SAMR21-xpro. I'm still trying to set up the offset and gain corrections, i tried to edit the "periph_conf.h" file, but when i compile and run it, it seems that nothing has changed... Anyway i want to say "thanks" to Peter that gave me a huge help! /best regards, / /Alessandro/ ___ 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
