Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tinydtls-dev] Question about current status/support with Contiki

Hi Raul,

Raul Fuentes <ra.fuentess.sam+tinyDTLS@xxxxxxxxx> writes:

> After be able to run smoothness TinyDTLS with RIOT, I'm retaking my
> work with Contiki and TinyDTLS. Right now, I'm focused to make run
> your code correctly with Contiki 3.0. 

Thank you very much. I appreciate both, your work on making this run on
RIOT-OS as well as Contiki.

> But seems that the general issue is memory. I'm unable to fit the
> client inside of sky or wismote motes. Only in Z1 motes, I generated a
> special file for the platform-specific with the following parameters: 

Yes. With Contiki 2.7, it was possible to run it with wismote using the
large memory model. Fortunately, I have a couple of OpenMotes and
STM32W, both of which have plenty of storage...

> #define HAVE_ASSERT_H 1
> typedef unsigned int ssize_t;
> The ssize_t is because I'm using the same code I used for RIOT.

Which is okay per se but using unsigned int is really weird. The first
's' in ssize_t is for 'signed'. You should reconsider that.

> Everything is fine except the dynamic memory in Contiki as is
> impossible to generated enough space for the sessions and thus all the
> calls to memb_alloc fails.



Back to the top