Panic of client raised by the Serial Comms Server (or "Comms Server").
|
0 |
Write request made when request already in progress. |
|
1 |
Read request made when request already in progress. |
|
2 |
Break request made when request already in progress. |
|
3 |
Invalid port handle passed by client. |
|
4 |
Bad descriptor passed by client. |
|
5 |
RComm::SetConfig() call made when another request already in progress. |
|
6 |
RComm::SetSignals() call made when another request already in progress. |
|
7 |
RComm::ResetBuffers() call made when another request already in progress. |
|
8 |
RComm::ReceiveBufferLength() call made when another request already in progress. |
|
9 |
Cannot have two outstanding RComm::NotifySignalChange() requests from the same client. |
|
10 |
Cannot have two outstanding RComm::NotifyFlowControlChange() requests from the same client. |
|
11 |
Cannot have two outstanding RComm::NotifyConfigChange() requests from the same client. |
|
12 |
Cannot have two outstanding RComm::NotifyBreak() requests from the same client. |
|
13 |
Cannot have two outstanding RComm::NotifyDataAvailable() requests from the same client. |
|
14 |
Cannot have two outstanding RComm::NotifyOutputEmpty() requests from the same client. |
|
15 |
Thread size is negative. |
|
16 |
Minimum heap size is too small. |
|
17 |
Maximum heap size is less than minimum heap size. |
|
18 |
Wrong client session for set access request. |
|
19 |
Client must close object before setting comm access. |
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights
reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License
v1.0.