Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)

2016-06-15 Thread Kees Bakker
On 15-06-16 09:32, Peter Kietzmann wrote: Hi Kees, if you volunteer you could start with moving code to samd21_common and open PR(s) for that :-). Well, OK. I'll give it a try. Seems like a step in the right direction. I personally won't find time for that unfortunately. On our side we coul

Re: [riot-devel] How does the Border router excute the command that ethos sends?

2016-06-15 Thread Jianwen Ouyang
HI, Thanks for your answer. it's the function "readline()", which will read the ringbuffer, right? with "getchar()" operation. my problem is that, I send hundreds of commands to the Border router. sometimes, UART did receive the command, but the command was not executed. it's really strange. Owe

Re: [riot-devel] How does the Border router excute the command that ethos sends?

2016-06-15 Thread Kaspar Schleiser
Hi, On 06/15/2016 05:30 PM, Jianwen Ouyang wrote: > And my question is how this ringbuffer related to the function which I > defined in "shell_commands[]" array? The ringbuffer is is used to buffer incoming UART bytes for consumption. In main(), the function shell_run() is called which starts th

[riot-devel] How does the Border router excute the command that ethos sends?

2016-06-15 Thread Jianwen Ouyang
Hi RIOTers, I am using the example Border router, and I add a command in the "shell_commands[]" array, like the example gnrc_networking. When I ran the start_network.sh, I input the command, like "ifconfig", in the terminal. Then this text will be sent to Border router by serial port. And in the B

Re: [riot-devel] [BLE] Random 48-bit address generation

2016-06-15 Thread Florent-Valéry Coen
Thanks to all of you for your help! Generating a hash based on the CPU ID seems like a great solution. @Brett My understanding of the BLE specs was that a device was allowed to use a random address rather than a public one, thus effectively bypassing the need of an OUI (volume 6, part B, section 1

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Peter Kietzmann
Hi, probably todays problems were caused by my computer... Best Peter Am 15.06.2016 um 14:35 schrieb Martine Lenders: Hi, Should we rathe change to skype & co? Cheers, Martine 2016-06-15 14:25 GMT+02:00 Peter Kietzmann : Sorry, PC hung up. Session available under link as before: http://plac

Re: [riot-devel] [BLE] Random 48-bit address generation

2016-06-15 Thread Brett Swann
Hi Florent, A random BD_ADDR is "okay" for testing, but just be aware of the requirement for an OUI as discussed in BLE Core specification, volume 2, section 1.2 [1]. Also, steer clear of the reserved range mentioned in section 1.2.1. Kind regards, Brett [1] https://www.bluetooth.org/docman/hand

Re: [riot-devel] [BLE] Random 48-bit address generation

2016-06-15 Thread Martine Lenders
Hi, alternatively, instead of truncating you can just "fold" the remaining bytes over using XOR this way you keep some of the variance introduced by the longer hash. Best regards, Martine 2016-06-15 15:12 GMT+02:00 Jose Alamos : > Hello, > > I don't know exactly how the BD_ADDR works, but you mig

Re: [riot-devel] [BLE] Random 48-bit address generation

2016-06-15 Thread Jose Alamos
Hello, I don't know exactly how the BD_ADDR works, but you might try generate a hash (maybe SHA256? [1]) from CPU ID (function cpuid_get [2]). Then you can truncate to 48 bits and manually set/fix required bytes. Of course the truncation makes the hash weaker in terms of the chances of having 2 s

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Martine Lenders
I think not everyone has Mumble configured right now so using it as im-promptu replacement not suitable. 2016-06-15 14:34 GMT+02:00 Kaspar Schleiser : > Hey, > > On 06/15/2016 02:35 PM, Martine Lenders wrote: >> Should we rathe change to skype & co? > > please! :) IMHO voice only is fine, so shoul

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Johann Fischer
Am 15.06.2016 um 14:35 schrieb Martine Lenders: Hi, Should we rathe change to skype & co? Cheers, Martine +1 -- Johann Fischer ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Kaspar Schleiser
Hey, On 06/15/2016 02:35 PM, Martine Lenders wrote: > Should we rathe change to skype & co? please! :) IMHO voice only is fine, so should we go with mumble? Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/deve

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Martine Lenders
Hi, Should we rathe change to skype & co? Cheers, Martine 2016-06-15 14:25 GMT+02:00 Peter Kietzmann : > Sorry, PC hung up. Session available under link as before: > > http://placecam.de/call.php?c=kWtmE~M0jTbKGFQSGnUBLtC.xAbWgTythbQbBMVXUvs- > > > Am 15.06.2016 um 14:06 schrieb Peter Kietzmann:

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Peter Kietzmann
Sorry, PC hung up. Session available under link as before: http://placecam.de/call.php?c=kWtmE~M0jTbKGFQSGnUBLtC.xAbWgTythbQbBMVXUvs- Am 15.06.2016 um 14:06 schrieb Peter Kietzmann: Forgot to attach the Padlink for the agenda: http://www.yourpart.eu/p/riot-2016-05-17-virtual-meeting Am 15.06.

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Peter Kietzmann
Forgot to attach the Padlink for the agenda: http://www.yourpart.eu/p/riot-2016-05-17-virtual-meeting Am 15.06.2016 um 14:04 schrieb Peter Kietzmann: Hi, session should be available under: http://placecam.de/call.php?c=kWtmE~M0jTbKGFQSGnUBLtC.xAbWgTythbQbBMVXUvs- Please note that it might be

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Peter Kietzmann
Hi, session should be available under: http://placecam.de/call.php?c=kWtmE~M0jTbKGFQSGnUBLtC.xAbWgTythbQbBMVXUvs- Please note that it might be a different link as usul. Cheers Peter Am 15.06.2016 um 13:21 schrieb Peter Kietzmann: Hi all, there is a point on the agenda for todays virtual mee

Re: [riot-devel] Notification: Biweekly virtual meeting @ Wed Jun 15, 2016 2pm - 3pm (RIOT Events)

2016-06-15 Thread Peter Kietzmann
Hi all, there is a point on the agenda for todays virtual meeting, so it will take place. The proposed topic concerns the network stack architecture. In that regards it would be great if someone of the main authors could participate :-). Hear your later! Peter Am 14.06.2016 um 14:00 schrie

[riot-devel] [BLE] Random 48-bit address generation

2016-06-15 Thread Florent-Valéry Coen
Hello everyone, I'm currently working on implementing Bluetooth Low Energy communications on the TI CC2650STK (aka sensortag). As you may know, each Bluetooth device is uniquely identified among its peers using a Bluetooth Device Address (BD_ADDR). This 48-bit number plays a role similar to the M

Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)

2016-06-15 Thread Kaspar Schleiser
Hey, On 06/15/2016 09:15 AM, temmi...@gmail.com wrote: > Soc and mcu family relations and naming schemes should be respected as well. Well, there's always the tradeoff between consistency within RIOT and consistency with whatever a vendor does to sort it's MCU variants. I must say that I prefer

Re: [riot-devel] Assign address ipv6 to RIOT mote (openmote)

2016-06-15 Thread Aaron Sowry
Hi Alessandro, RIOT does not have a radio driver for the cc2538 yet, but work is in progress - see https://github.com/RIOT-OS/RIOT/pull/5291. Feel free to test. Cheers, Aaron 2016-06-15 20:09 GMT+12:00 ALESSANDRO NICOLI : > Hi Rioters, > I'm trying to assign a static ipv6 global address to a mot

[riot-devel] Assign address ipv6 to RIOT mote (openmote)

2016-06-15 Thread ALESSANDRO NICOLI
Hi Rioters, I'm trying to assign a static ipv6 global address to a mote (OpenMote-cc2538) from the shell command line, with the *ifconfig *command. Since i've not the Border Router yet, how can i enable the network autoconfiguration for this mote? Otherwise how can i set the global ipv6 address for

Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)

2016-06-15 Thread Oleg Hahm
Hey! On Wed, Jun 15, 2016 at 09:45:19AM +0200, Kaspar Schleiser wrote: > On 06/15/2016 09:32 AM, Peter Kietzmann wrote: > > AFAIK Kaspar has a > > saml21-xpro board. > > Unfortunately not anymore. I think Hauke has one, or at there should be > one at FU Berlin. Yes, we have at least two of them

Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)

2016-06-15 Thread Kaspar Schleiser
Hey, On 06/15/2016 09:32 AM, Peter Kietzmann wrote: > AFAIK Kaspar has a > saml21-xpro board. Unfortunately not anymore. I think Hauke has one, or at there should be one at FU Berlin. Kaspar ___ devel mailing list devel@riot-os.org https://lists.riot-

Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)

2016-06-15 Thread Kaspar Schleiser
Hey, On 06/14/2016 08:59 PM, Kees Bakker wrote: > Notice the TXPO and RXPO. These indicate which "pads" the pin can use on > a certain SERCOM. > So, what we can learn from this is that we need to expand uart_conf_t. > We need PAD configuration > too. yep, that makes sense. +1! Kaspar _

Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)

2016-06-15 Thread Peter Kietzmann
Hi Kees, if you volunteer you could start with moving code to samd21_common and open PR(s) for that :-). Seems like a step in the right direction. I personally won't find time for that unfortunately. On our side we could test your PR(s) with the samr21-xpro board and AFAIK Kaspar has a saml21

Re: [riot-devel] Working on port to SODAQ Autonomo (SAMD21)

2016-06-15 Thread temmi...@gmail.com
> On 14.6.2016, at 21:30, Kees Bakker wrote: > > On 13-06-16 22:39, Peter Kietzmann wrote: >> >> # define the cpu used by SAMR21 Xplained Pro board >> export CPU = samd21 >> export CPU_MODEL = samr21x18a > If you ask me, I'd say that already a lot of files from cpu/samd21/periph can > be move