Priority: do not know? Lower as official firmware probably will NOT lower MAX_CONTACTS too often and "support team" will tell to users "just do full erase".
But just keep this in mind root cause.
Reproduce:
- compile with MAX_CONTACTS 100
- wait until its full
- recompille with some lower number MAX_CONTACTS (90 for example)
- crash loop
I found from backtrace it is because of _serial object is null during boot process.
Here: https://github.com/meshcore-dev/MeshCore/blob/main/examples/companion_radio/MyMesh.cpp#L327
It is because order of called initialization is reversed.. First is called the_mesh.begin()
and later is called
the_mesh.startInterface(serial_interface);
which will actually set that interface.
Priority: do not know? Lower as official firmware probably will NOT lower MAX_CONTACTS too often and "support team" will tell to users "just do full erase".
But just keep this in mind root cause.
Reproduce:
I found from backtrace it is because of
_serialobject is null during boot process.Here: https://github.com/meshcore-dev/MeshCore/blob/main/examples/companion_radio/MyMesh.cpp#L327
It is because order of called initialization is reversed.. First is called the_mesh.begin()
and later is called
the_mesh.startInterface(serial_interface);
which will actually set that interface.