Re: [riot-devel] TCP on RIOT OS
Hi Theresa, I would recommend waiting for tuesday. Cheers Simon Am 2018-05-22 16:29 schrieb Theresa Müller: Hi Simon, thanks for your reply! I would like to use TCP on RIOT for a project at my university which is related to my bachelor thesis, so would you rather recommend waiting until Tuesday since it would be better if I use a stable version for it? Best regards Theresa GESENDET: Dienstag, 22. Mai 2018 um 14:35 Uhr VON: "Simon Brummer" AN: "RIOT OS kernel developers" BETREFF: Re: [riot-devel] TCP on RIOT OS Hi Theresa, Martine is right, link local adresses don't currently work with gnrc tcp (even with the mandatory interface specifier). This is a known issue, I am currently working on it. I intend to merge it on the next Hack'n'Ack (next Tuesday). If you need it faster, there is a development branch for the fix on github. It should compile and work however, it could have some undesired side effects. Kind regards Simon Am 2018-05-22 14:03 schrieb Martine Lenders: > Hi Theresa, > > were you using link local addresses (i.e. are they prefixed > `fe80::/64`) for your trials? If yes, newer versions require to also > provide an interface with that (as it is the case e.g. also on Linux) > so this might be your problem. The client and server needs to be fixed > then of course to have the interface provided or warn the user that it > is missing.. > > Best regards, > Martine > > 2018-05-22 9:37 GMT+02:00 "Theresa Müller" : > >> Hi everyone, >> >> I am currently trying to use TCP on RIOT, but I'm having problems >> with it, since the "gnrc_tcp_server" and "gnrc_tcp_client" tests are >> not working on the latest version of RIOT. I tried to run these >> tests on the 2017.01 release where they were added the first time >> and everything works fine here, but when I run them on the 2018.01 >> or 2018.04 release, wireshark doesn't show any TCP pakets and the >> client always receives a timeout after a while, so somehow the >> client and the server aren't able to establish a connection. Maybe >> one of you knows what caused this change in behaviour and how this >> could be fixed. >> >> Thanks a lot for your help! >> >> Best regards, >> Theresa >> ___ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel [1] [1] > > > > Links: > -- > [1] https://lists.riot-os.org/mailman/listinfo/devel [1] > > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel [1] ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel [1] Links: -- [1] https://lists.riot-os.org/mailman/listinfo/devel ___ 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] TCP on RIOT OS
Hi Simon, thanks for your reply! I would like to use TCP on RIOT for a project at my university which is related to my bachelor thesis, so would you rather recommend waiting until Tuesday since it would be better if I use a stable version for it? Best regards Theresa Gesendet: Dienstag, 22. Mai 2018 um 14:35 Uhr Von: "Simon Brummer" An: "RIOT OS kernel developers" Betreff: Re: [riot-devel] TCP on RIOT OS Hi Theresa, Martine is right, link local adresses don't currently work with gnrc tcp (even with the mandatory interface specifier). This is a known issue, I am currently working on it. I intend to merge it on the next Hack'n'Ack (next Tuesday). If you need it faster, there is a development branch for the fix on github. It should compile and work however, it could have some undesired side effects. Kind regards Simon Am 2018-05-22 14:03 schrieb Martine Lenders: > Hi Theresa, > > were you using link local addresses (i.e. are they prefixed > `fe80::/64`) for your trials? If yes, newer versions require to also > provide an interface with that (as it is the case e.g. also on Linux) > so this might be your problem. The client and server needs to be fixed > then of course to have the interface provided or warn the user that it > is missing.. > > Best regards, > Martine > > 2018-05-22 9:37 GMT+02:00 "Theresa Müller" : > >> Hi everyone, >> >> I am currently trying to use TCP on RIOT, but I'm having problems >> with it, since the "gnrc_tcp_server" and "gnrc_tcp_client" tests are >> not working on the latest version of RIOT. I tried to run these >> tests on the 2017.01 release where they were added the first time >> and everything works fine here, but when I run them on the 2018.01 >> or 2018.04 release, wireshark doesn't show any TCP pakets and the >> client always receives a timeout after a while, so somehow the >> client and the server aren't able to establish a connection. Maybe >> one of you knows what caused this change in behaviour and how this >> could be fixed. >> >> Thanks a lot for your help! >> >> Best regards, >> Theresa >> ___ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel [1] > > > > Links: > -- > [1] https://lists.riot-os.org/mailman/listinfo/devel > > ___ > 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 ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] TCP on RIOT OS
Hi Theresa, Martine is right, link local adresses don't currently work with gnrc tcp (even with the mandatory interface specifier). This is a known issue, I am currently working on it. I intend to merge it on the next Hack'n'Ack (next Tuesday). If you need it faster, there is a development branch for the fix on github. It should compile and work however, it could have some undesired side effects. Kind regards Simon Am 2018-05-22 14:03 schrieb Martine Lenders: Hi Theresa, were you using link local addresses (i.e. are they prefixed `fe80::/64`) for your trials? If yes, newer versions require to also provide an interface with that (as it is the case e.g. also on Linux) so this might be your problem. The client and server needs to be fixed then of course to have the interface provided or warn the user that it is missing.. Best regards, Martine 2018-05-22 9:37 GMT+02:00 "Theresa Müller" : Hi everyone, I am currently trying to use TCP on RIOT, but I'm having problems with it, since the "gnrc_tcp_server" and "gnrc_tcp_client" tests are not working on the latest version of RIOT. I tried to run these tests on the 2017.01 release where they were added the first time and everything works fine here, but when I run them on the 2018.01 or 2018.04 release, wireshark doesn't show any TCP pakets and the client always receives a timeout after a while, so somehow the client and the server aren't able to establish a connection. Maybe one of you knows what caused this change in behaviour and how this could be fixed. Thanks a lot for your help! Best regards, Theresa ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel [1] Links: -- [1] https://lists.riot-os.org/mailman/listinfo/devel ___ 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] TCP on RIOT OS
Hi Theresa, were you using link local addresses (i.e. are they prefixed `fe80::/64`) for your trials? If yes, newer versions require to also provide an interface with that (as it is the case e.g. also on Linux) so this might be your problem. The client and server needs to be fixed then of course to have the interface provided or warn the user that it is missing.. Best regards, Martine 2018-05-22 9:37 GMT+02:00 "Theresa Müller" : > Hi everyone, > > I am currently trying to use TCP on RIOT, but I'm having problems with it, > since the "gnrc_tcp_server" and "gnrc_tcp_client" tests are not working on > the latest version of RIOT. I tried to run these tests on the 2017.01 > release where they were added the first time and everything works fine > here, but when I run them on the 2018.01 or 2018.04 release, wireshark > doesn't show any TCP pakets and the client always receives a timeout after > a while, so somehow the client and the server aren't able to establish a > connection. Maybe one of you knows what caused this change in behaviour and > how this could be fixed. > > Thanks a lot for your help! > > Best regards, > Theresa > > ___ > 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] PIC programmer with Linux support?
Hi, if its still needed and if it helps: I have a PICkit3 (my property) at my office that I don't really need and am willing to donate to the cause. I needed it years ago for a private project that I gave away (and was able to confirm that it is still running after all those years during my vacation ^^) and I'm not really involved into MIPS development, so I really don't need it. Cheers, Martine 2018-05-18 15:28 GMT+02:00 Francisco Acosta : > Hi Joakim! > > On 18 May 2018 at 10:44:29, Joakim Nohlgård (joakim.nohlg...@eistec.se) > wrote: > > Is this for pic32 HIL tests? > > Do the pic32 boards support jtag like the cortex boards? In that case you > > could maybe use one of the ftdi ft2232 based jtag programmers out there. > > > > Unfortunately that’s not the case. They have a kind of serial programming > interface > which is not super standard. However there are several tools out there > which might > be useful here. > > I’m thinking about pickit2 clones and compatible firmware which might be > the > solution in this case. > > I’ll let you know whenever I have a more concrete solution. > > Cheers, > > Paco. > > > > /Joakim > > > > On Fri, May 18, 2018, 10:30 Kaspar Schleiser wrote: > > > > > Hey fellow RIOTers, > > > > > > I'm looking for a readily available PIC programmer with Linux support. > > > > > > Main requirements are: > > > > > > > > > - can flash the boards that RIOT supports > > > - has a CLI application that runs on Linux (both x86 and ARM/RasPi) > > > (- not too expensive) > > > > > > Any suggestions? > > > > > > Kaspar > > > ___ > > > 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 > > > > ___ > 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
[riot-devel] makefile: info boards supported
Hello all, I've been using the `make info-boards-supported` command for a RIOT related project. I need to show all supported boards for an application (examples, etc). The problem I've found is the fact that `info-boards-supported` shows boards tagged by BOARD_INSUFFICIENT_MEMORY (so, in theory they can be compiled but strictly speaking they won't be supported by the board). I know Murdock is currently using this command to compile all examples (and prevent linking them if they don't fit in the board). Would make sense to add another command that shows all boards that are (compile+flash) supported? I somehow feels "info-boards-supported" is misleading, but changing the name might be extra work since it's used by Murdock. Comments? ;) Cheers, José ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Embargo on I2C API and drivers
Dear RIOTers, As of today start the embargo regarding I2C. All PR's related to I2C device or CPU drivers, new I2C board support etc. will be postponed for up to 2 weeks. A dedicated branch has been created (new_i2c_if) based on the lastest master. If you're willing to participate, don't hesitate :) There is a synchronization effort on this issue #6577 (the complete list is now up-to-date). Cheers ! -- Dylan Laduranty ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] TCP on RIOT OS
Hi everyone, I am currently trying to use TCP on RIOT, but I'm having problems with it, since the "gnrc_tcp_server" and "gnrc_tcp_client" tests are not working on the latest version of RIOT. I tried to run these tests on the 2017.01 release where they were added the first time and everything works fine here, but when I run them on the 2018.01 or 2018.04 release, wireshark doesn't show any TCP pakets and the client always receives a timeout after a while, so somehow the client and the server aren't able to establish a connection. Maybe one of you knows what caused this change in behaviour and how this could be fixed. Thanks a lot for your help! Best regards, Theresa ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel