Buffering logs in flash when off line #100

revk commented 2021年07月23日 11:13:00 +02:00 (Migrated from github.com)

I think we should make devices with 16MB flash not 4MB. A device with 4MB flash probably wants to avoid being root on the mesh (unless it is alone). This means the root can log events to flash, and replay logs when connected to back end control. A 16MB flash allows a lot of space for off line logging, but it should, none the less, be cyclic. This can be a feature of the library for all "event" messages.

I think we should make devices with 16MB flash not 4MB. A device with 4MB flash probably wants to avoid being root on the mesh (unless it is alone). This means the root can log events to flash, and replay logs when connected to back end control. A 16MB flash allows a lot of space for off line logging, but it should, none the less, be cyclic. This can be a feature of the library for all "event" messages.

revk commented 2021年08月13日 15:17:44 +02:00 (Migrated from github.com)

We ideally need to allow for some 4MB devices. If we report details the root can pick a device to ask as a flash log.

We ideally need to allow for some 4MB devices. If we report details the root can pick a device to ask as a flash log.

revk commented 2022年07月29日 16:01:19 +02:00 (Migrated from github.com)

Work on PICO with bigger flash is a start to this - I suspect we want to only log where we have the flash capacity

Work on PICO with bigger flash is a start to this - I suspect we want to only log where we have the flash capacity