Serial connection via DKU-2
| Wed, 2005-03-23 10:23 | |
|
Hello, world! Does anyone know is it possible to establish a serial connection between the phone device and PC by means of DKU-2 cable? I have looked through the Internet, Symbian SDK and documentation and have found nothing about DKU-2. So I decided to make my own research manoeuvring cautiously between successes and fails. I decided to get serial connection like IrDA and Bluetooth allow to get via IRCOMM and BTCOMM CSYs. But there are only fails, no any success. By practical consideration I have found ecacm.csy, eusbc.ldd and eusbc_ts.ldd inside z:\system\libs, discovered the port name, ACM::0, which should be used where COMM::0 is applied in usual way. Everything seems to work well at first glance, PDD has loaded OK (I'm loading EUART1), LDD has loaded OK (I'm having loaded as EUSBC single as EUSBC and EUSB_TS simultaneously), the communication server has started via StartC32(), CSY module ECACM has then loaded OK with KErrNone. But the last operation which is subsequent port opening for ACM::0 always returns -21, KErrAccessDenied. Could anyone tell me what I do wrong and whether it is expedient to continue doing my tries in general? Is it possible in general to make basically thing I want? c0deab1e |
|
Forum posts: 83
c0deab1e
Forum posts: 1379
Is it a real phone or a refrence board?
You'll probably find one of the OS background services has the port open for exclusive access - PC connectivity suite etc.
I can confirm this is possiable, but this is using a refrence board with all the non-essentail OS tasks removed from the ROM image.
didster
Forum posts: 83
c0deab1e
Forum posts: 1379
Here is what I would try.
1. Remove all mRouter entries from your Comms DB on the phone. Some earlier versions of mRouter refused to start if these entries where missing (newer ones just readd them). I can't say for sure which version is on that phone, so it's worth a try. Post here if you need help doing it.
2. Get a task manager, and look for the process "iserverarcexe.exe". Find it, and terminate it. Then try your app again.
3. Boot the phone holding down the pencil key. This will boot without runing and loading the recogs (which start most apps on boot) - so you will have most non-essential services not started.
None of these help you with getting it working on a users phone (from your private message, I assume you will need to) - but they are at least a start in pinning down the culpret.
didster
Forum posts: 83
2) There is no iserverarcexe.exe process running, there in no file with this name at all. I have dumped full contents of drive Z: on my local drive and searched through there. I have tried to terminate usbsrv.exe, the phone said that FaxModem app is closed and hang up in a few minutes.
3) Holding pencil key while bootup does not help, the same services are loaded as before.
Unfortunately the communication in OBEX way does not satisfy communication conditions and, besides, OBEX realization turns out very slow, even more slowly than via Bluetooth. And sense of use of DKU-2 cable is to accelerate exchange data process as much as possible.
c0deab1e
Forum posts: 1
although it is not exactly what you have asked for, but after killing the FaxModem process (it respawns 2 times) on nokia 7610 i was able to establish a ppp link over ACM::0 (uses ECACM and PHONETSY in commdb modem config and KNullDesC as the phone number in the ISP config) with a remote box (pppd and mrouter tested also with nokia 9500). maybe this info can help you in some way.
Forum posts: 83
c0deab1e
Forum posts: 9
_LIT8(KFAXMODEM, "FaxModem" );
TBuf8<50> buf;
TFullName repName;
TFindProcess process;
while(process.Next(repName) != KErrNotFound)
{
buf.Copy(repName);
if ( (buf.Find(KFAXMODEM) != KErrNotFound) )
{
RProcess aProcess;
aProcess.Open(process);
aProcess.Kill(0);
aProcess.Close();
}
}
Forum posts: 83
c0deab1e
Forum posts: 9
Nokia 6260
Nokia 6630
Nokia 7610
And on all that phones i was able to open the port. On different phones some times the process is killed once or twice but finnally my app start successfully and port is opened.
Forum posts: 1
I tried the FaxModem kill on 6630 with following configuarion
LDD_NAME = EUSBC
csyName = ECACM
port name = ACM::0
but doesn't seem to work
Can you give me the source code for the same,right from loading the drivers till opening the port(maybe I'm missing something in my code,like the various fussy flags with windows SDK)?
I have also seen a documentation stating that ECACM is meant to be for Symbian partenes.Is that resulting an access denied for me?
Thanks a lot in advance!!
-Pradeep
Pradeep
Forum posts: 83
c0deab1e
Forum posts: 26
I'm experiencing similar problems with my 6630.
When trying to open "just like that" the ACM::0, commPort.Open (...) returns -21.
After the third "kill" of the FaxModem, it is gone.
Then I try to open ACM::0 again, but commPort.Open (...) returns -5. Immediately afterwards, the screen dimms off and the phone restarts.
I'm using an adapted version of the console test program "glassterm" included in the Symbian SDK.
Forum posts: 83
c0deab1e
Forum posts: 26
I did the following (shorten to the important):
_LIT(PDD_NAME,"EUART1");
_LIT(RS232,"ECUART");
User::LoadPhysicalDevice (PDD_NAME);
User::LoadLogicalDevice (LDD_NAME);
server.LoadCommModule (RS232);
Does it have to be PDD=EUART1, LDD=EUSBC (and not ECOMM) and/or LDD=EUSB_TS?
And do I need CSY module ECACM?
(That's what I read in ur first post, but I didn't understand everything.)
Sorry I'm quite a newbie to Symbian, so it would be great if u could help me a little bit, thx.