Aha - I think I know what this might be - NO - WRONG - SEE NEXT POST
Several different (mchip) modules use a static char array named printBuff and I have seen instances before where the linker goes bonkers if the same static name is used in different modules.
Last time I fell foul of this, the linker had used the same RAM for all those variables, on that occasion causing mysterious over-writing of DMA descriptors.
This time it is just at risk of corrupting debug output, which is far less disruptive but still bad.
And causing mis-allocation of RAM is doubly bad.
Assuming it is "legit" (if questionable) practice to use the same name for static variables in different source files in the same project, this is a definite linker bug and I will raise a ticket. (My knowledge of the "C" standard is practical rather than academic)
I will go through renaming these variables in tcpip_commands.c, sys_debug.c and sys_command.c and report back.
post edited by boatbodger - 2020/05/24 08:41:57