Re: [riot-devel] Support for Microchip MRF24J40 Radio Module
Hi Bernhard, I'm a bit confused. Just some days ago @TobiasFredersdorf stated to work on this. Did you synchronize each others? Regarding the module initialization: Honestly I don't quite understand your doubts. Yes it is a signed 16 bit integer in dBm. The quantization to valid values is done inside the function. It makes things easier for the netdev(2) abstraction. You won't get an OpenLabs transceiver within days. By experience not even within two weeks. If you want to cross-test drivers you could a) get an Atmel samr21-xpro (same transceiver as OpenLaps on board) and run RIOT b) get a Phytec evaluation kit. There you can cross-test with kinetis kw2x transceivers on either RIOT or Linux c) use the MRF24J40 with the Linux driver on a RasPi d) work together with @TobiasFredersdorf. He hast the hardware available. Cheers Peter Am 29.02.2016 um 00:58 schrieb Bernhard Nägele: Hello everybody, today I started to port the AT86RF2XX driver for the MRF24J40 radio module. Hier I have 2 question: 1. At the module initialization I found the following comment: /** * @brief Set the transmission power of the given device [in dBm] * * If the device does not support the exact dBm value given, it will set a value * as close as possible to the given value. If the given value is larger or * lower then the maximal or minimal possible value, the min or max value is * set, respectively. * * @param[in] dev device to write to * @param[in] txpower transmission power in dBm */ void at86rf2xx_set_txpower(at86rf2xx_t *dev, int16_t txpower); How should the txpower be coded? A int16 value in dBm ??? I don't understand this. The Atmel AT86RF231 has a tx-power range from -17dBm to +3dBm and the MRF24J40 has a range from -30 to 0dBm. How fits this together with that comment above? 2. From where could I get as fast as possible some OpenLabs 802.15.4 modules (delivery should be in 2-3 days, prefered in Germany)? At the store of OpenLabs there is mentioned a delivery time from about 2 weeksthis is to long for my purpose. Best regards Bernhard ___ 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] Support for Microchip MRF24J40 Radio Module
Hello Bernhard, as for first question: check for the AT86RF2XX_REG__PHY_TX_PWR macro and dbm_to_tx_pow function + rf231 datasheet for the second question have a look at atzb-a-233-xpro module from atmel (can get it from mouser) if you are or ok with 233 and not strictly 231. wbr malo On 29 February 2016 at 00:58, Bernhard Nägele wrote: > Hello everybody, > today I started to port the AT86RF2XX driver for the MRF24J40 radio module. > Hier I have 2 question: > > 1. At the module initialization I found the following comment: > > /** > * @brief Set the transmission power of the given device [in dBm] > * > * If the device does not support the exact dBm value given, it will set a > value > * as close as possible to the given value. If the given value is larger or > * lower then the maximal or minimal possible value, the min or max value > is > * set, respectively. > * > * @param[in] dev device to write to > * @param[in] txpower transmission power in dBm > */ > void at86rf2xx_set_txpower(at86rf2xx_t *dev, int16_t txpower); > > How should the txpower be coded? A int16 value in dBm ??? I don't > understand this. > The Atmel AT86RF231 has a tx-power range from -17dBm to +3dBm and the > MRF24J40 > has a range from -30 to 0dBm. How fits this together with that comment > above? > > 2. From where could I get as fast as possible some OpenLabs 802.15.4 > modules (delivery should be in 2-3 days, prefered in Germany)? At the store > of OpenLabs there is mentioned a > delivery time from about 2 weeksthis is to long for my purpose. > > Best regards > Bernhard > ___ > 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] Support for Microchip MRF24J40 Radio Module
Hello everybody, today I started to port the AT86RF2XX driver for the MRF24J40 radio module. Hier I have 2 question: 1. At the module initialization I found the following comment: /** * @brief Set the transmission power of the given device [in dBm] * * If the device does not support the exact dBm value given, it will set a value * as close as possible to the given value. If the given value is larger or * lower then the maximal or minimal possible value, the min or max value is * set, respectively. * * @param[in] dev device to write to * @param[in] txpower transmission power in dBm */ void at86rf2xx_set_txpower(at86rf2xx_t *dev, int16_t txpower); How should the txpower be coded? A int16 value in dBm ??? I don't understand this. The Atmel AT86RF231 has a tx-power range from -17dBm to +3dBm and the MRF24J40 has a range from -30 to 0dBm. How fits this together with that comment above? 2. From where could I get as fast as possible some OpenLabs 802.15.4 modules (delivery should be in 2-3 days, prefered in Germany)? At the store of OpenLabs there is mentioned a delivery time from about 2 weeksthis is to long for my purpose. Best regards Bernhard ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Issue in mailing list
Hi , https://github.com/RIOT-OS/RIOT/issues/4855 from the above link there is no answer for my question.But i already subscribed.Where i can see my answers.There no notification ...I am waiting for 3 or 4 days for your replies.Its really very difficult to get support from your side. Pls try to solve this. On Sun, Feb 28, 2016 at 4:43 PM, Oleg Hahm wrote: > Hi Giri, hi Ludwig! > > On Sun, Feb 28, 2016 at 06:38:43AM +0100, Ludwig Knüpfer wrote: > > There are two mails from you and two answers. > > And subscribing the mailing list might also help to receive answers, please > visit https://lists.riot-os.org/mailman/listinfo/devel > > > Gmail also has a search function that might be of help in case you > struggle > > with the invalid certificate of the archives page. > > That's the second time in a short period someone called the certificate > "invalid". This is incorrect. The certificate is valid and correctly > signed by > a well-known CA. The problem is, however, that (due to mostly bureaucratic > reasons) cacert.org is unfortunately not installed per default on most > operating systems/browsers, but you can do so quite easily visiting > http://www.cacert.org/index.php?id=3 > > However, I agree that getting certificates from the letsencrypt project, is > probably a better idea. If someone is willing to go forward with this, > please > let me know and I will happily grant access to the mailing list server. > > Cheers, > Oleg > -- > /* > * We used to try various strange things. Let's not. > */ > linux-2.2.16/fs/buffer.c > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] netdev2 - some hints about the relationships between the 6lowpan protocol
Hi!
On Fri, Feb 26, 2016 at 10:11:45PM +0100, Martine Lenders wrote:
> that's not what I said: cc11xx is the only *radio* in master.
To be clear on that: the only radio in master that is ported to netdev2! There
are other operational network drivers in master that allow IPv6 connectivity.
Cheers,
Oleg
--
printk("WE HAVE A BUG HERE!!! stk=0x%p\n", stk);
linux-2.6.6/drivers/block/cciss_scsi.c
signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Issue in mailing list
Hi Giri, hi Ludwig! On Sun, Feb 28, 2016 at 06:38:43AM +0100, Ludwig Knüpfer wrote: > There are two mails from you and two answers. And subscribing the mailing list might also help to receive answers, please visit https://lists.riot-os.org/mailman/listinfo/devel > Gmail also has a search function that might be of help in case you struggle > with the invalid certificate of the archives page. That's the second time in a short period someone called the certificate "invalid". This is incorrect. The certificate is valid and correctly signed by a well-known CA. The problem is, however, that (due to mostly bureaucratic reasons) cacert.org is unfortunately not installed per default on most operating systems/browsers, but you can do so quite easily visiting http://www.cacert.org/index.php?id=3 However, I agree that getting certificates from the letsencrypt project, is probably a better idea. If someone is willing to go forward with this, please let me know and I will happily grant access to the mailing list server. Cheers, Oleg -- /* * We used to try various strange things. Let's not. */ linux-2.2.16/fs/buffer.c signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
