Re: [riot-devel] IPSEC/IKEv2
Hey Tobias Heider implemented G-IKEv2 [1], which should be fairly easy to port to IKEv2 as the messages are more the less the same. It has some a dependency on gnrc_pktbuf_merge [2], which has not yet included in RIOT (hopefully he will finish this soon). If you're interested I'm pretty sure that we can share the code with you. I had several students starting a RIOT port of ESP, but none finished it. I probably have to do it myself when time allows... I heard that Olaf Bergmann had a student who wanted to implement Diet-ESP [3], but I don't know a state of that. (obviously that would require an ESP port) Cheers Tobias [1] https://tools.ietf.org/html/draft-yeung-g-ikev2-13 [2] https://github.com/RIOT-OS/RIOT/pull/6487 [3] https://datatracker.ietf.org/doc/draft-mglt-ipsecme-diet-esp/ > -Ursprüngliche Nachricht- > Von: devel Im Auftrag von Thomas C. Schmidt > Gesendet: Dienstag, 3. Juli 2018 12:53 > An: devel@riot-os.org > Betreff: Re: [riot-devel] IPSEC/IKEv2 > > Hi Baptiste, > > as far as I remember, Tobias Guggemos http://www.mnm- > team.org/~guggemos/ > from LMU Munich was working on this. > > Plese back check with him. > > Cheers, > Thomas > > On 03/07/2018 08:50, Baptiste Clenet wrote: > > Hi, > > Is there any implementation of IPSEC/IKEv2 in RIOT network stack? Has > > anyone planned to implement it? > > > > Cheers, > > > > -- > > Prof. Dr. Thomas C. Schmidt > ° Hamburg University of Applied Sciences Berliner Tor 7 ° > ° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany ° > ° http://inet.haw-hamburg.de/members/schmidt Fon: +49-40-42875-8452 > ° > > ___ > 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] SPI on Arduino Zero for AT86RF233
Hey, thanks, GPIO_MUX_C was the missing puzzle. There is still a bug when receiving frames, but at least I can now initialize it correctly. Thanks Tobias Von: devel [mailto:devel-boun...@riot-os.org] Im Auftrag von Alexandre Abadie Gesendet: Montag, 5. März 2018 18:23 An: RIOT OS kernel developers <devel@riot-os.org> Betreff: Re: [riot-devel] SPI on Arduino Zero for AT86RF233 Hi, Not sure it will help but I recently tried to use a Semtech LoRa radio with an Arduino Zero and using a second SPI (for the radio) was working with the following configuration: { .dev = >SPI, .miso_pin = GPIO_PIN(PA, 19), .mosi_pin = GPIO_PIN(PA, 16), .clk_pin = GPIO_PIN(PA, 17), .miso_mux = GPIO_MUX_C, .mosi_mux = GPIO_MUX_C, .clk_mux = GPIO_MUX_C, .miso_pad = SPI_PAD_MISO_3, .mosi_pad = SPI_PAD_MOSI_0_SCK_1 } in the driver params, I had this line for the SPI: #define SX127X_PARAM_SPI(SPI_DEV(1)) Let us know if it works for you. Alex _ Hey, I’m trying to use the AT86RF233 with the Arduino M0 Pro (using the Arduino Zero configuration). Using the default SPI configuration (and pins) didn’t work, why I tried to change the SPI to the Arduino_Pins 11,12,13 in order to have CS (PIN 10) using the same SERCOM as the other SPI pins. However, I didn’t get it to work and it seems that using SPI with SERCOM1 does not initialize. Is there anything I did completely wrong or is it just a stupid idea to connect the AT86RF233 with an Arduino M0? SPI Config in arduino/periph_conf.h: static const spi_conf_t spi_config[] = { { .dev = >SPI, .miso_pin = ARDUINO_PIN_ICSP_MISO, .mosi_pin = ARUDINO_PIN_ICSP_MOSI, .clk_pin = ARUDINO_PIN_ICSP_CLK, .miso_mux = GPIO_MUX_D, .mosi_mux = GPIO_MUX_D, .clk_mux = GPIO_MUX_D, .miso_pad = SPI_PAD_MISO_0, .mosi_pad = SPI_PAD_MOSI_2_SCK_3 } , { .dev = >SPI, .miso_pin = ARDUINO_PIN_12, .mosi_pin = ARDUINO_PIN_11, .clk_pin = ARDUINO_PIN_13, .miso_mux = GPIO_MUX_D, .mosi_mux = GPIO_MUX_D, .clk_mux = GPIO_MUX_D, .miso_pad = SPI_PAD_MISO_3, .mosi_pad = SPI_PAD_MOSI_0_SCK_1 } }; at86rf2xx_params.h: #ifndef AT86RF2XX_PARAM_SPI #define AT86RF2XX_PARAM_SPI (SPI_DEV(1)) #endif #ifndef AT86RF2XX_PARAM_SPI_CLK #define AT86RF2XX_PARAM_SPI_CLK (SPI_CLK_5MHZ) #endif #ifndef AT86RF2XX_PARAM_CS #define AT86RF2XX_PARAM_CS ARDUINO_PIN_10 #endif #ifndef AT86RF2XX_PARAM_INT #define AT86RF2XX_PARAM_INT ARDUINO_PIN_7 #endif #ifndef AT86RF2XX_PARAM_SLEEP #define AT86RF2XX_PARAM_SLEEP ARDUINO_PIN_8 #endif #ifndef AT86RF2XX_PARAM_RESET #define AT86RF2XX_PARAM_RESET ARDUINO_PIN_9 #endif #define AT86RF2XX_PARAMS_BOARD{.spi = AT86RF2XX_PARAM_SPI, \ .spi_clk = AT86RF2XX_PARAM_SPI_CLK, \ .cs_pin = AT86RF2XX_PARAM_CS, \ .int_pin = AT86RF2XX_PARAM_INT, \ .sleep_pin = AT86RF2XX_PARAM_SLEEP, \ .reset_pin = AT86RF2XX_PARAM_RESET} Thanks Tobias -- Tobias Guggemos, M.Sc Ludwig-Maximilians-Universität München (LMU) Institue of Computer Science Oettingenstr. 67, Room E003 D-80538 München, Germany Munich Network Management Team (MNM) Tel: +49 89 2180-9209 <http://www.mnm-team.org/~guggemos> http://www.mnm-team.org/~guggemos ___ devel mailing list <mailto:devel@riot-os.org> devel@riot-os.org <https://lists.riot-os.org/mailman/listinfo/devel> 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] SPI on Arduino Zero for AT86RF233
Hey, Im trying to use the AT86RF233 with the Arduino M0 Pro (using the Arduino Zero configuration). Using the default SPI configuration (and pins) didnt work, why I tried to change the SPI to the Arduino_Pins 11,12,13 in order to have CS (PIN 10) using the same SERCOM as the other SPI pins. However, I didnt get it to work and it seems that using SPI with SERCOM1 does not initialize. Is there anything I did completely wrong or is it just a stupid idea to connect the AT86RF233 with an Arduino M0? SPI Config in arduino/periph_conf.h: static const spi_conf_t spi_config[] = { { .dev = >SPI, .miso_pin = ARDUINO_PIN_ICSP_MISO, .mosi_pin = ARUDINO_PIN_ICSP_MOSI, .clk_pin = ARUDINO_PIN_ICSP_CLK, .miso_mux = GPIO_MUX_D, .mosi_mux = GPIO_MUX_D, .clk_mux = GPIO_MUX_D, .miso_pad = SPI_PAD_MISO_0, .mosi_pad = SPI_PAD_MOSI_2_SCK_3 } , { .dev = >SPI, .miso_pin = ARDUINO_PIN_12, .mosi_pin = ARDUINO_PIN_11, .clk_pin = ARDUINO_PIN_13, .miso_mux = GPIO_MUX_D, .mosi_mux = GPIO_MUX_D, .clk_mux = GPIO_MUX_D, .miso_pad = SPI_PAD_MISO_3, .mosi_pad = SPI_PAD_MOSI_0_SCK_1 } }; at86rf2xx_params.h: #ifndef AT86RF2XX_PARAM_SPI #define AT86RF2XX_PARAM_SPI (SPI_DEV(1)) #endif #ifndef AT86RF2XX_PARAM_SPI_CLK #define AT86RF2XX_PARAM_SPI_CLK (SPI_CLK_5MHZ) #endif #ifndef AT86RF2XX_PARAM_CS #define AT86RF2XX_PARAM_CS ARDUINO_PIN_10 #endif #ifndef AT86RF2XX_PARAM_INT #define AT86RF2XX_PARAM_INT ARDUINO_PIN_7 #endif #ifndef AT86RF2XX_PARAM_SLEEP #define AT86RF2XX_PARAM_SLEEP ARDUINO_PIN_8 #endif #ifndef AT86RF2XX_PARAM_RESET #define AT86RF2XX_PARAM_RESET ARDUINO_PIN_9 #endif #define AT86RF2XX_PARAMS_BOARD{.spi = AT86RF2XX_PARAM_SPI, \ .spi_clk = AT86RF2XX_PARAM_SPI_CLK, \ .cs_pin = AT86RF2XX_PARAM_CS, \ .int_pin = AT86RF2XX_PARAM_INT, \ .sleep_pin = AT86RF2XX_PARAM_SLEEP, \ .reset_pin = AT86RF2XX_PARAM_RESET} Thanks Tobias -- Tobias Guggemos, M.Sc Ludwig-Maximilians-Universität München (LMU) Institue of Computer Science Oettingenstr. 67, Room E003 D-80538 München, Germany Munich Network Management Team (MNM) Tel: +49 89 2180-9209 <http://www.mnm-team.org/~guggemos> http://www.mnm-team.org/~guggemos ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT on the Arduino M0 Pro
In case anyone else has this issue: It was basically what Antonio said, the USER_WORD_0 was set wrong by Arduino. The factory setting is 0xD8E0C7F9, but it needs to be set to 0xD8E0C7FF. In Atmel Studio one can do that by changing the fuse-setting USER_WORD_0.NVMCTRL_BOOTPROT from 0x01 to 0x07. If we find a way to do that automatically with openocd we'll post it. Tobias -Ursprüngliche Nachricht- Von: devel [mailto:devel-boun...@riot-os.org] Im Auftrag von Antonio Galea Gesendet: Freitag, 23. Dezember 2016 08:01 An: RIOT OS kernel developersBetreff: Re: [riot-devel] RIOT on the Arduino M0 Pro On Thu, Dec 22, 2016 at 5:47 PM, Florian Eich wrote: > > Verification... > at address 0x0 expected 0x00, read 0xff > Error: verification failed Mh, then my best bet is that your CPU has the fises bits set to protect the first pages - see for instance: http://www.avrfreaks.net/forum/fuses-samd21-xplained If you have a copy of Atmel Studio, you can change the fuses in a snap. It might be possibile to do that with OpenOCD, but frankly I don't know how. Antonio ___ 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