Re: [riot-devel] one wire communication

Hi, The DHT devices use a protocol similar to 1-wire. See pull request #2990 for reference. Cheers, Ludwig Am 18. August 2015 09:51:21 MESZ, schrieb shishir tiwari sumit.tiwari1...@gmail.com: Hello RIOTers, we are trying to communicating with DS2430A IC which support is one wire protocol.

Re: [riot-devel] MQTT + RIOT

Hi, I can't report any progress either. Cheers, Ludwig Am 4. August 2015 14:43:58 MESZ, schrieb Cenk Gündogan cenk.guendo...@fu-berlin.de: Hey, As far as I'm concerned the mqtt-sn implementation that Ludwig and me started a while back can be labled as Work In No-Progress. We never went

Re: [riot-devel] Fwd: tapsetup problem

Hi, Apparently your project is not configured to use a transceiver. Cheers, Ludwig Am 20. September 2015 21:22:49 MESZ, schrieb samira afzal : >Hi all, >Ii had sent a question about my problem but i didn't get any answer, if >i >have to email to another address or sth

Re: [riot-devel] The border router wi^H^H is ready!

Hi, I bow my head to everyone who contributed :) Cheers, Ludwig Am 17. September 2015 18:31:21 MESZ, schrieb Oleg Hahm : >Ladies and gentlemen! > >I'm more than proud to announce that just a couple of minutes ago I >sent the >first successful ping from an iotlab-m3 node

Re: [riot-devel] RIOT, Windows, and Code Composer Studio

Hi Clark, I am not aware of anyone using CCS. In my perception most of us are Linux based and don't even use Eclipse. Cheers, Ludwig Am 20. Juni 2016 15:59:29 MESZ, schrieb Clark Leach : >Nothing? Really? > >On Tue, Jun 14, 2016 at 2:43 PM, Clark Leach

Re: [riot-devel] Issue in mailing list

Hi, There are two mails from you and two answers. Maybe the problem confused you so much you overlooked and/or forgot the answers ;) https://lists.riot-os.org/pipermail/devel/2016-February/003488.html There is a link labeled "next message" you can use to click through the thread to find the

Re: [riot-devel] Implementing rng

Hi, The Makefile.features defines the features of a board, that's why it lives in the boards directory. So yes, it is intended to declare the RNG in there even if it is not part of the CPU/SoC. It would be architecturally nicer to have such files in various places (eg CPU, radio, board) and

Re: [riot-devel] Make error: SPI Driver test program

Hi, It seems you are not building for your target board but for native. Native has no SPI support (as indicated by the error message). If you export BOARD for your target hardware (which has to support SPI), things should go better. Cheers, Ludwig Am 21. Februar 2016 22:55:13 MEZ, schrieb

Re: [riot-devel] Happy 10k!

Hoorah! BTW: what's the current SLoC count? Cheers, Ludwig Am 22. Februar 2016 00:56:13 MEZ, schrieb Kaspar Schleiser : >Hey fellow RIOTers, > >we've passed 1 commits... > >Congratulations to everyone! > >Kaspar >___ >devel

Re: [riot-devel] Interim Hack'n'ACK

Hi, On Tue, Mar 01, 2016 at 07:49:42PM +0100, Oleg Hahm wrote: > Hi! > > On Tue, Mar 01, 2016 at 07:23:26PM +0100, Ludwig Ortmann wrote: > > apparently there was a copy/paste error, the correct URL is: > > http://placecam.de/call.php?c=VBYEpXi43MZ2MOrV~pegsMm6Z7woUbw.VRY0Qxal2pE- > > Actually,

Re: [riot-devel] Sample applications

Hi, Based on a quick scan this looks very good indeed and think we should incorporate it into the RIOT project space. Not sure where exactly though. Cheers, Ludwig Am 1. März 2016 11:48:19 MEZ, schrieb Alexandre Abadie : >Dear Rioters, > >I started to use riot-os a

Re: [riot-devel] Bridge border router and 6LowPan interfaces

Hi, Am 4. März 2016 18:05:14 MEZ, schrieb "Bernhard Nägele" : >Hello everyone, >just one thought about border-routers from a newbie: Why not using >embedded boards like Raspberry Pi for this purpose. Everything from the > >software stack side is available (bridging

Re: [riot-devel] Booting my App from USB.

Hi, I am uncertain what you mean by "boot to a VM" and "from a USB". Currently RIOT is meant neither for running virtual machines nor for running on virtual machines. Booting from USB is generally not supported by any of the target platforms of RIOT. What are you trying to achieve? What

Re: [riot-devel] Απ: Make bootable .elf file!

Hi, On Thu, Jul 28, 2016 at 10:25:14PM +0200, astralien3000 wrote: > Ah, ok I understood MiTsArAs was trying to run the native > implementation on qemu-i385, which is not possible, right ? It is not possible to run a 'native' binary directly on 'qemu-i386', correct. > But I did not know this

[riot-devel] Booting RIOT

Hi, first of all: Both of you turned up at about the same time with about the same question .. Are you the same person/working together? Can I ask where and how you learned about RIOT? Regarding booting RIOT: - RIOT is generally targeting microcontroller IoT hardware, not PC hardware - when

Re: [riot-devel] FW: Missing Libraries

Hi, ncurses is not supported in RIOT, neither is MS DOS (conio.h and dos.h). It is possible to link native against libraries on your host OS, but that is because it ends up running as a process. You need to understand that you can not just pull libraries from your desktop OS and use them on an

[riot-devel] Compatibility matrix

Hi, One idea for improving understanding of the meaning of "supported platform": We could provide a matrix showing which test application runs on which platform. Opinions? Cheers, Ludwig ___ devel mailing list devel@riot-os.org

Re: [riot-devel] Byte array should be uint8_t, not char

sues/4758, but it has not yet been >> merged because of various other things getting in the way. >> >> Best regards, >> Joakimr >> >> On Mon, Jul 4, 2016 at 7:23 AM, Ludwig Knüpfer >> <ludwig.knuep...@fu-berlin.de <mailto:ludwig.knuep...@fu-berlin.de&

Re: [riot-devel] Byte array should be uint8_t, not char

There are 16 CPU's that use spi_transfer_byte(s) and 6 drivers. > >I won't mind creating a PR, but of course I can only test it by >building >examples for all boards that support SPI. And look at compile errors. >Or are >there other procedures? > >On 04-07-16 07:23, Ludw

Re: [riot-devel] Απ: Απ: Problem with "make" -lm missing.

Hi, Yes, you said that you want do that before but you never explained: *WHY* do you want to do that? Also: RIOT is an OS! Cheers, Ludwig Am 9. August 2016 11:15:26 MESZ, schrieb MiTsArAs Jimaras : >I made trouble once, speaking about this project, but I am going at it

Re: [riot-devel] Απ: Απ: Απ: Problem with "make" -lm missing.

Hi, If you have been told to write an application that runs on a VM without using an OS, RIOT is not the answer because it is an OS, so your application is using an OS. Apart from that there is no difference between running on native and running on QEMU from the application point of view. As

Re: [riot-devel] Απ: Problem with "make" -lm missing.

Hi, It's difficult to say anything about this without seeing the actual source code. Cheers, Ludwig Am 9. August 2016 10:27:04 MESZ, schrieb MiTsArAs Jimaras : >Problem solved. > >Now I have another problem! > >I compile on native board, and everything is alright. >

Re: [riot-devel] qemu-i386 port

All of them? Am 9. August 2016 14:11:12 MESZ, schrieb Martine Lenders <m...@martine-lenders.eu>: >Hi Ludwig, >well at least the FU boards are now "obtainable" through the IoT-Lab >testbed. ;-) > >Cheers, >Martine > >2016-08-09 14:06 GMT+02:00 Ludwig Knüpfe

Re: [riot-devel] qemu-i386 port

Hi, I'm all for cleaning up stale boards, especially I'd they are as hard to obtain as for example the FU boards. If I'm not mistaken this would also enable the removal of at least one legacy driver interface (I have some GPIO API in mind). Cheers, Ludwig Am 9. August 2016 13:52:56 MESZ,

Re: [riot-devel] [eeprom] [stm32l151] Driver for internal EEPROM

Dear Anon, On Thu, Jul 21, 2016 at 05:32:19PM +0300, Anon Anonymous wrote: > I have a task to read/write the internal EEPROM block on the > STM32L151 MCU and as I can see there's no driver or interface > implemeted yet for this kind of task. > > My question is how can I add the EEPROM features

Re: [riot-devel] Byte array should be uint8_t, not char

Hi Kees, Unless there is a good reason to deviate from this guideline all violations should be corrected. This particular rule was added relatively recently, so it would not surprise me if not all occurrences in RIOT have been adapted yet. Cheers, Ludwig Am 3. Juli 2016 22:50:10 MESZ, schrieb

Re: [riot-devel] Progress of port to SODAQ Autonomo

On Mon, Jul 04, 2016 at 07:44:21AM +0200, Ludwig Knüpfer wrote: > Am 2. Juli 2016 13:21:19 MESZ, schrieb Kees Bakker <k...@sodaq.com>: > >While going through the code I notice that there are too many "magic" > >constants. Hard coded numbers that are obvio

Re: [riot-devel] Low-Power-Management - LPM_arch

Hi neo, Please compare: https://github.com/RIOT-OS/RIOT/releases/tag/2017.01 and: http://api.riot-os.org/group__drivers__periph__pm.html Apropos: Our documentation does have a search function in the upper right corner of the site ;-) Cheers, Ludwig Am 14. Februar 2017 23:44:27 MEZ schrieb Neo

Re: [riot-devel] Github Issue

Hi, Of your base bench (6541) contains content your work branch depends, on there is no way open a PR against master without including that content. What you could do is open a PR of your work branch against your base branch and rebase on master once the base branch is merged. Cheers, Ludwig

Re: [riot-devel] BIN FILES

Hi, I guess you need glasses ;) If you have your target exported, then 'make' creates a binary image. 'make flash' flashes this image onto your board. Cheers, Ludwig Am 7. Oktober 2016 15:29:38 MESZ, schrieb Ilias Seitanidis : >Dear all, >Is it possible to create a

Re: [riot-devel] Sensors with STM32F4Discovery

Hi, I would take a look at the existing drivers in RIOT. The drivers say what connection type the support (most often SPI/I2C). Then you go on eBay and look for "Arduino" + the sensor you are interested in. Usually that leads you to a cheap board with the sensor and all the infrastructure

Re: [riot-devel] Coding conventions amendment

Hi, Am 14. Oktober 2016 10:04:07 MESZ, schrieb Oleg Hahm <oliver.h...@inria.fr>: >Hi Ludwig! > >On Fri, Oct 14, 2016 at 09:13:50AM +0200, Ludwig Knüpfer wrote: >> In general it is safer to explicate the integer width. As RIOT is >targeted >> at 32 bit architec

Re: [riot-devel] Coding conventions amendment

Hi, Am 14. Oktober 2016 08:05:51 MESZ, schrieb Kees Bakker : >But I believe the question was more, in case of an unsigned type, >should we use "unsigned int" or size_t. In that case I would go for >size_t. BTW: there is also the signed type `ssize_t`. Cheers, Ludwig

Re: [riot-devel] Coding conventions amendment

Hi, Am 13. Oktober 2016 22:42:11 MESZ, schrieb Kaspar Schleiser : >Hi, > >On 10/13/2016 09:43 PM, Kees Bakker wrote: Does anybody object to adding this to the coding >> conventions explicitly? >>> > What about `size_t`? >> +1 for size_t > >Well, any convention

Re: [riot-devel] Απ: BSc Thesis

Hi, Please keep messages to the mailing list in English. Cheers, Ludwig Am 15. November 2016 14:42:28 MEZ, schrieb Dimitris Kazantzas : >Ναι, σκέφτηκα να ρωτήσω και την κοινότητα, αν και τελικά πήρα >ανακατευθυνση για εσάς ξανα. > > >Καμιά ιδέα; >

Re: [riot-devel] RIOT OS Student Research

Hi, On Sat, Nov 12, 2016 at 01:23:03AM -0500, Dominic Massoni wrote: > To whom it may concern: This is a fairly good place to ask. > We are hoping to ask for some helpful information in regards to the > security policies and practices ... Thanks for giving us a heads up ;) I would suggest

Re: [riot-devel] MIPS Support of RIOT RTOS

Hi, Please have a look at the open pull requests: https://github.com/RIOT-OS/RIOT/pulls?utf8=✓=is%3Apr%20is%3Aopen%20mips For further information, please also have a look at the mailing list archives: https://www.mail-archive.com/search?q=Mips=devel%40riot-os.org If that does not answer your

Re: [riot-devel] To global seed or not to global seed

Hi, Am 8. März 2017 10:21:15 MEZ schrieb Oleg Hahm : >Is testing and simulation the only use case you can imagine? I'm >somewhat >reluctant to add code just for non-production purposes. Since we outspokenly target researchers with RIOT this is a production feature. However

Re: [riot-devel] To global seed or not to global seed

Hi, Am 8. März 2017 10:06:17 MEZ schrieb "Cenk Gündoğan" : >On 17-03-08 09:09:34, Kaspar Schleiser wrote: >> That way we'd have: >> >> - user controlled state >> - the ability to overload (e.g., combine hwrng, collected entropy, >prng >> but with the same interface) >

Re: [riot-devel] flash command without compiling

Hi, In general this should not be the case. I'd imagine one of the packages messes up the build system's dependencies. Hard to say without seeing the project. Cheers, Ludwig Am 17. April 2017 16:47:12 MESZ schrieb Jose Alamos : >Dear RIOTers, > >I noticed the 'make flash'

Re: [riot-devel] RIOT integration options for Whitefield

Hi Rahul, Regarding implementation proposal 2: As I don't know anything about Whitefield: what would that implementation look like in detail? In particular: how would RIOT communicate with Whitefield? (Unix) socket/thread messages/other IPC? Cheers, Ludwig Am 30. Juli 2017 17:13:51 MESZ

Re: [riot-devel] Host Name

Hello Jana, If you're looking for a way to distinguish nodes based on their hardware, this might be what you want: http://riot-os.org/api/group__drivers__periph__cpuid.html Cheers, Ludwig Am 19. April 2018 21:18:30 MESZ schrieb Janna Om : >Hello! >Is it possible with RIOT

Re: [riot-devel] FreeRTOS comparison in the website

Hi, I've been using FreeRTOS for a while now. I've not been using their network stack. It's a bit hard to compare, as freertos doesn't have the "cover all bases centrally" approach RIOT has. NXP for example will let you choose from several software components (TCP/IP among others) to include

Re: [riot-devel] FreeRTOS comparison in the website

actually care about seeing in a comparison today. The timeline/history also skips to "future" 6 years ago. Cheers, Ludwig Am 12. März 2019 18:16:52 MEZ schrieb "Ludwig Knüpfer" : >Hi, > >I've been using FreeRTOS for a while now. >I've not been using their n

Re: [riot-devel] Fwd: Using IEEE802.15.4 on RIOT-OS native

Hehe, thank you for the praise :) If there's interest I think the sources of the thesis are available somewhere and could be used to make an updated version.. as far as I recall it was a CC licensed document anyways? Cheers, Ludwig Am 15. Juli 2020 14:28:02 MESZ schrieb Linda Fliss : >Thanks