defragster
Senior Member+
Looked like Kurt's would work to catch the beginning wrapping backwards for Delete. Delete not used often, but it is done 'inline' so smaller is better.
Also @Mike - re: Interesting note in p#45 - note the pointer address values in the example? They are not given pointers inline with source code lines.
> important to see where the items are stored to know it is showing what it seems to be showing.
> the 32B boundary shifts under those allocs - so the overlap/underlap will not affect those ptr sets the same
> also somewhere under 32KB alloc the HAB forces data on restart
>> Might be best to manually pick the pointers from fixed 32KB offset, rather than letting the build pick them
--> that's how I came to the 'ugly' but effective use case for LittleFS DMAMEM survival
And for ref - this 2nd line should have buffer2 not buffer:
Also @Mike - re: Interesting note in p#45 - note the pointer address values in the example? They are not given pointers inline with source code lines.
> important to see where the items are stored to know it is showing what it seems to be showing.
> the 32B boundary shifts under those allocs - so the overlap/underlap will not affect those ptr sets the same
> also somewhere under 32KB alloc the HAB forces data on restart
>> Might be best to manually pick the pointers from fixed 32KB offset, rather than letting the build pick them
--> that's how I came to the 'ugly' but effective use case for LittleFS DMAMEM survival
And for ref - this 2nd line should have buffer2 not buffer:
Code:
Serial.printf("\n------------- Kurt's first complete function in post 46 -----------------\n");
Serial.printf("%x %x %x\n", (uint32_t)&ptr5, (uint32_t)[B][U]buffer[/U][/B], (uint32_t)&ptr6);