https://github.com/TexasInstruments/mcupsdk-core-k3/blob/k3_next/source/drivers/device_manager/sciclient_direct/sciclient.c#L640-L640

This is problematic in the multi threaded environment as the `gSciclientHandle.currSeqId` may be modified between L640 and L641 by another task after preemption of the current one. This could lead to the sequence id matching failure after receiving response from the TIFS.

The L640 and L641 should be assigned with a local variable, after it is initialized with the global counter for sequence id, to ensure these always get the same value.