-->
Page 7 of 13

Re: Possible replacement MQTT library

PostPosted: Sun Aug 30, 2020 9:24 am
by eriksl
I guess not many people tend to program "real" microprocessors these days, like attiny with 256 bytes RAM ;)

Re: Possible replacement MQTT library

PostPosted: Sun Aug 30, 2020 9:34 am
by Pablo2048
Agree wit that, but I'm doing little different approach - I have 2 phase initialization - in 1. phase I collect memory consumption for every active system runtime component, then I ask heap for the memory in single block and in phase 2 I initialize all modules via given pointer to assigned memory pool so there is just 1 malloc in my application. This allows me to dynamically (at system startup) choose and activate just required drivers without doing holes to the heap.

Re: Possible replacement MQTT library

PostPosted: Sun Aug 30, 2020 10:51 am
by rudy
eriksl wrote:I guess not many people tend to program "real" microprocessors these days, like attiny with 256 bytes RAM ;)

256 bytes of ram :o the luxury. I recently have been using the ATTINY102 with only 32 bytes of ram.

Re: Possible replacement MQTT library

PostPosted: Sun Aug 30, 2020 10:51 am
by eriksl
so there is just 1 malloc in my application


I you do a single malloc, you could just as well replace it by a single static char[] declaration ;)