NewLC - Serial connection via DKU-2 - Comments

Re: Serial connection via DKU-2

sauooda — Wed, 18 Jun 2008 21:21:16 +0200

hi all,
i know it is along time that anyone didn't reply here

but i wish if somebody hears me

i have some question that i need to answer very much so please would any body help me?
1-i made aprogram that kills faxmodem process by the the solution posted here and put it in for loop that runs 1000 time to ensure that it is killed
when i run the program it deletes it three times and when close it and open it again it kills it again 3 times and so on...............btw i made an GUI program for that purpose and i use an 6630
THE question is why after running the process for the first time when running it again it still can to find the process and kill it again although i already had killed it?

THE second question i want to make aserial connection using DKU-2 cable

is there in problem in using the COMM::0 on the 6630 because when i tried to open it it returns KerrInUse although i had killed the faxmodem process by the previous program ( i putted the two prog in the same prog )

i think that the faxmodem process didn't killed successfully or there is another process that uses the serial?

if any body could help i would be grateful cause i'm trieng to solve this problem for aweek now

my code is here

        
        TBuf8<50> buf;
        TFullName repName;
          _LIT8(KFAXMODEM,  "FaxModem" );
        TFindProcess process;
           for(TInt i = 0; i < 1000; i++)
           {
              while(process.Next(repName) != KErrNotFound)
              {
                 buf.Copy(repName);
            
                    if ( (buf.Find(KFAXMODEM) != KErrNotFound) )
                  {
                    
                     EchoL(KMess2);
                     RProcess aProcess;
                     aProcess.Open(process);
                     aProcess.Kill(0);
                     aProcess.Close();
                 }
              }
           }

        _LIT(KLddName, "ECOMM");
        _LIT(KPddName, "EUART");
        _LIT(Kmodulename, "ECUART");
        _LIT(Kportname, "COMM::0");
        _LIT(Kerrorldd,"error ldd");
        _LIT(Kerrorpdd,"error pdd");
        _LIT(Kerrorcommserv,"error commserv");
        _LIT(Kerrorcommmodule,"error commmodule");
        _LIT(Kerrorloadmodule,"error loadmodule");
        TInt r1;
        r1=User::LoadLogicalDevice(KLddName);
        
        if (r1 != KErrNone)
                  EchoL(Kerrorldd);
        r1=User::LoadPhysicalDevice(KPddName);

        if (r1 != KErrNone)
                EchoL(Kerrorpdd);        
        StartC32 ();
        RCommServ icommserv;
        TInt s;
        TInt r;
        s=icommserv.Connect();
        if (s != KErrNone)
                EchoL(Kerrorcommserv);
        s=icommserv.LoadCommModule(Kmodulename);
        if (s != KErrNone)
                {
                EchoL(Kerrorcommmodule);
                }

        RComm icomm;
        r = icomm.Open(icommserv,Kportname ,ECommExclusive,ECommRoleDTE);
// here it returnes KerrInUse
        if (r != KErrNone)
                {
                EchoL(Kerrorloadmodule);
                 }

Re: Serial connection via DKU-2

Hex — Thu, 18 May 2006 10:29:00 +0200

Killing the PLPExe process helped me to open the EUART1. But after i close my application i can't connect the phone using the PC Suite. Though PLPExe is runing, it doesn't listen to EUART1 any more. Does anybody know how make PLPExe work again after killing it?

Re: Serial connection via DKU-2

shameus_burp — Fri, 07 Apr 2006 16:03:00 +0200

Thanks for the suggestion. I tried opening ACM::0 and I get either -14 or -21 which suggests something has the port. My target is the 6600 which doesn't have ECACM.csy driver. I'm merely trying to get something to work and go from there.

I attempt to delete the FaxModem.exe process just before opening the port. I print the number of faxmodem instances found which is 2 after the first kill. But when I check the processes after running glassterm there are still 3 instances running.

Here's some relevant code. I have also used ECUART and COMM::0 for opening the 6600 port.

r = User::LoadLogicalDevice (EUSBC);

r = server.LoadCommModule (ECACM);
User::LeaveIfError (r);

_LIT(KMessage21,"Before Killing\n");
_LIT(KMessage22,"After Killing\n");
_LIT(KMessage23,"Fax Found\n");

//////////////////////////////////////////////////////////////
// To kill the fax process on the phone

console->Printf (KMessage21);

TBuf8<50> buf;
TFullName repName;

TFindProcess process;
for(TInt i = 0; i < 1000; i++)
{
     while(process.Next(repName) != KErrNotFound)
     {
     buf.Copy(repName);

     if ( (buf.Find(KFAXMODEM) != KErrNotFound) )
     {

     RProcess aProcess;
     aProcess.Open(process);
     aProcess.Kill(0);
     aProcess.Close();
console->Printf (KMessage23);
     }
     }
}
console->Printf (KMessage22);

r = commPort.Open (server, _L ("ACM::0"), ECommExclusive);
User::LeaveIfError (r);

Re: Serial connection via DKU-2

c0deab1e — Fri, 07 Apr 2006 07:11:59 +0200

FaxModem respawns three times on Nokia 6260, no more. After killing last copy you get access to ACM::0.

Re: Serial connection via DKU-2

shameus_burp — Thu, 06 Apr 2006 18:05:17 +0200

I've been following this thread because I have been attempting to use the EUART comm port. I've tried killing the faxmodem.exe which just respawns in more numbers, I tried killing OBEX references in processes and I have tried finding plp.exe but it's not running on the phone as suspected.

I've had no luck at all with any of the suggestions using glassterm. I'm using 6600, 6620 and 7610 all with similar results. The port simply will not open.

I did read somewhere on forum nokia about having the right access level to use that port. Is this true?

Here's the quote....

"Access to serial ports is restricted to prevent unauthorized transmission
or reception of data. " now this pertained to java apps but is this also true with C++ apps as well? If so, how can this access be obtained?

Re: Serial connection via DKU-2

kt_y1022 — Thu, 06 Apr 2006 12:56:35 +0200

-> Hex, thank you for your advice.

I had a try, but I didn't find PlpExe on Motorola M1000.

kt_y1022

Re: Serial connection via DKU-2

kt_y1022 — Thu, 06 Apr 2006 05:16:57 +0200

FOMA M1000 supports m-Router and comunnicates with PC using m-Router and USB.

kt_y1022

Re: Serial connection via DKU-2

gavin — Wed, 05 Apr 2006 16:13:49 +0200

Quote from: Hex

Symbian replaced PLP with m-Router in the 7650, so the 9290 (the US version of the 9210) was one of the last devices to use it.

Nokia stopped using m-Router with the 7610, and now use an OBEX based protocol to communicate with PC-Suite. Most Nokia Series 60 phones and Series 80 v2 phones get ACM::0 locked by FaxModem.exe.

Gavin

Re: Serial connection via DKU-2

Hex — Wed, 05 Apr 2006 15:59:27 +0200

I've got nokia 9290 here, it also showed me errors:
KErrInUse and KErrAccessDenied. The glassterm didn't work also.

What is true, is that some process holds the port. But that process is NOT FaxModem!!!

Just think logically! You usually upload the applications using the PC Suite. The PC Suite is using PLP protocol. There's a plp server on device! So all you need to do is kill PlpExe process.

   _LIT(KProcess,"PlpExe");

   TFindProcess finder;
   TFullName fullName;
   RProcess process;

   while( finder.Next(fullName) == KErrNone )
   {
      // check if this is our process
      TInt err = fullName.FindF(KProcess);
      if(err != KErrNotFound)
      {
         TInt procErr = process.Open(finder);
         if( procErr == KErrNone)
         {
            process.Kill(KErrNone);
            process.Close();
         }
         break;
      }
   }

After killing it i successfully ran the Glassterm and was able to send data from HyperTerminal to glassterm.

Re: Serial connection via DKU-2

kt_y1022 — Wed, 05 Apr 2006 15:46:28 +0200

Thank you Gavin.

Addition:
Since Desktop Suite is connected, ACM::0 can be opened in shared mode(ECommShared) successfully.

Does anyone know how to communicate over USB on FOMA A1000 or M1000?
Please...!!

kt_y1022

Re: Serial connection via DKU-2

kt_y1022 — Wed, 05 Apr 2006 12:26:05 +0200

Does anyone know Desktop Suite?
Since Desktop Suite is connected , ACM::0 can be opened successfully.

Would anyone tell me what is happend on it?

Thanks very much!

Re: Serial connection via DKU-2

gavin — Wed, 05 Apr 2006 12:22:55 +0200

FaxModem.exe is the Nokia process that grabs ACM::0 at boot on series 60 devices. On a Foma (v7.0) device it is likely to be a different process that reserves ACM::0.

Unfortunately there is no guarantee that the Foma device uses ECACM.CSY to communicate over USB, it is possible that it uses a different mechanism.

Gavin

Re: Serial connection via DKU-2

kt_y1022 — Wed, 05 Apr 2006 11:41:43 +0200

-> c0deab1e , Uncle Sam Â

Thank you for your reply!

-> c0deab1e
I tried to do that, but i couldn't find FaxModem.
It seems not existing.

process.Next() returns (-1).
I 'll continue to try it.

Thanks a lot.

Re: Serial connection via DKU-2

c0deab1e — Wed, 05 Apr 2006 11:19:09 +0200

I refer to kt_y1022 , but his original today post I refered to was changed and so some misunderstanding occurs.

kt_y1022 , you should kill the FaxModem service first, otherwise you cannot get access to ACM::0.

Re: Serial connection via DKU-2

Uncle Sam — Wed, 05 Apr 2006 09:59:16 +0200

I'm not sure to how you refer, but if you ment me, my solution were the following settings:

Code:

TCommConfig usbPortSettings;
iUsbCommPort.Config(usbPortSettings);
usbPortSettings().iRate = EBps460800;
usbPortSettings().iParity = EParityNone;
usbPortSettings().iDataBits = EData8;
usbPortSettings().iStopBits = EStop1;
usbPortSettings().iFifo = EFifoEnable;
usbPortSettings().iHandshake =(KConfigObeyCTS | KConfigFreeRTS); // for cts/rts

I just don't check the capabilities; and it works - at least on 6630 and 6680.

Serial connection via DKU-2

c0deab1e — Wed, 23 Mar 2005 10:23:52 +0100