see [1]. If you want get fix it yourself, you can extend _get as such, that it returns the length in byte of cc110x->radio_address (which would be 1 in the cc110x case) as a uint16_t [2] on that opt value and provide a PR for it [3]. I think in the end that would be the faster alternative.
In general, I don’t know if anyone ever tested NDN over cc110x (we usually use IEEE 802.15.4 devices), so expect more errors the way done ;-). But I think it’s good that somebody finally does that work.
see [1]. If you want get fix it yourself, you can extend _get as such, that it returns the length in byte of cc110x->radio_address (which would be 1 in the cc110x case) as a uint16_t [2] on that opt value and provide a PR for it [3]. I think in the end that would be the faster alternative.
In general, I don’t know if anyone ever tested NDN over cc110x (we usually use IEEE 802.15.4 devices), so expect more errors the way done ;-). But I think it’s good that somebody finally does that work.
Ok, i will provide a PR for this bug.
And i read an paper[1] from Freie Universität Berlin, in this paper, people used MSB-A2 and cc110x to running CCN-lite on RIOT.
OK, i see, so in the process of test ccn over cc110x, maybe there are some issues which i can’t fix, i will ask on mailing list or github issue, i will feel appreciate if you guys can help me.
And thanks in advance.