Channel non-blocking write semantics.

There is no way to force channel depth in 16.1 for emulation. You can only change channel depth emulation behavior in v17.0. The only cases I have encountered where a receiving channel received more data than it should in emulator were when I had made a mistake in my code, resulting in two writing points to the same channel; unfortunately, at least in v16.1, the emulator does NOT fail when you have more than one writing point to a channel and it does in fact write data to that channel from both points. Chances are this has not been fixed in v17.0 either. Just to make sure, I recommend trying a trial standard compilation on your kernel to make sure you do not have more than one writing point to your channel (in which case the standard compilation will fail, telling you about the problem).