Changes between Version 1 and Version 2 of Getting-Started/Symbian

May 6, 2009 8:55:12 AM (15 years ago)



  • Getting-Started/Symbian

    v1 v2  
     1= Getting Started: Building and Debugging PJSIP on Symbian S60 3rd Edition Device using Carbide C++ = 
     6This document covers the following topics: 
     13== Requirements == 
     15For this tutorial, we will need: 
     16 - [ Symbian S60 3rd Edition Maintenance Release (MR)]. We also have tried this on FP1. Other SDK versions may work, but I did not test it. 
     17 - Carbide C++ version 2.0. You will need choose Developer Edition during install to do on-device debugging. 
     18 - [ Nokia PC Suite] for the connectivity between the device and your PC (I use version 6.85) 
     19 - Latest PJSIP from SVN trunk 
     20 - Nokia S60 3rd Edition device (I use Nokia E70, but any S60 3rd Edition device should do, I think) 
     21 - Nokia data cable for on-device debugging (you can also use Bluetooth connection, but this tutorial will not cover it) 
     25== Installations == 
     27=== SDK === 
     29Follow the installation instructions in the SDK documentation (make sure that the SDK requisites, such as Perl version, are satisfied). Please install Symbian SDK on the same drive as PJSIP. 
     31=== Carbide === 
     33Follow the installation instructions in the Carbide C++ documentation. The installation should be straightforward, but don't forget to '''select the Developer's Edition''' to get the On-Device debugging/TRK Debugging feature. 
     35=== Nokia PC Suite === 
     37Install PC Suite, connect your device with the USB cable, and make sure your PC can access your device.  
     39==== Connect Data Cable ==== 
     41Connect the USB cable to the phone, and on the phone, select '''PC Suite''': 
     45If this is the first time you connect your phone to the PC, then it may take some time for Windows to install the USB drivers for the phone. Wait for it to complete and the Nokia PC Suite and PC Sync icons on the task bar tray become green: 
     49Leave PC Suite running with the device connected using the USB cable throughout this tutorial session. 
     51=== PJSIP === 
     53Retrieve and configure PJSIP: 
     54 1. For this tutorial, I assume pjsip will be checked out to '''{{{C:\project\pjproject}}}''' directory. 
     55 1. Checkout PJSIP from the usual location (see [ PJSIP Download page] for details).  
     56 1. Fill in your '''{{{config_site.h}}}''' with: 
     58#include <pj/config_site_sample.h> 
     63== Importing PJSIP Projects == 
     66Run Carbide C++. When it asks the workspace location, enter a directory where you would want to put Carbide specific settings for PJSIP (or just accept the default value): 
     70You will now be presented with Carbide Welcome page. 
     73Now we need to import PJSIP's project files (the MMP files) into Carbide's workspace.  
     75Select '''File''' --> '''Import''' from the menu: 
     79This dialog below will pop up. Select '''Symbian OS''' --> '''Symbian OS Bld.inf file''' from the list, then press '''Next''' button: 
     83On the next dialog, click '''Browse..''' button to select '''bld.inf''' file from PJSIP's {{{build.symbian}}} directory, then press '''Next''' button: 
     87Then on the SDK selection dialog, select the build configurations that you want to support. For this tutorial, select WINSCW and GCCE from S60 3rd Edition MR SDK, and press '''Next''' button ('''do not select ARMV5 unless you have the commercial ARMV5 compiler'''): 
     91You will then presented with MMP selection dialog. Leave the default selection (normally it should select all MMPs) and press '''Next''': 
     95The project now is ready to be imported, press the '''Finish''' button: 
     99Carbide is now exporting the MMP files into the workspace and this progress window will be displayed: 
     103Wait for the process to complete. 
     105Once it completes, you will see the PJSIP project tree on the bottom left part of the Carbide main window: 
     109On the '''Problems''' pane (bottom center of the main window) you can see there is one ''Warning'' about duplicate path, but we can ignore this for now. 
     111The projects should now be ready to be build. 
     115== Building the Projects == 
     117Lets try to build the project first to make sure that the source is okay. 
     119=== Select the Build Configuration === 
     121First select the build target by selecting '''Project''' --> '''Active Build Configuration''' from main menu (or right clicking the ''Bld.inf'' or ''pjproject'' item from ''Symbian Project Navigator'' pane from the bottom left part of the main window).  
     123Select '''Phone Debug (GCCE) [S60_3rd_MR]''' from the menu: 
     127=== Build the Project === 
     129Then right click ''Bld.inf'' or ''pjproject'' item from ''Symbian Project Navigator'' pane from the bottom left part of the main window, and select '''Build Target Only''': 
     133Wait for the build process to complete. You may take a peek on what Carbide is doing by clicking on ''Console'' pane/tab in the bottom part of main window. 
     135Once it completes, watch out for any errors in the ''Problems'' pane (at the bottom center). There shouldn't be any errors, although there may be few warnings which I think can be ignored, for now: 
     139We are now ready to build the .sis/.sisx file to be deployed to the phone. 
     145== Preparing the .sis/.sisx File == 
     147The .sis file is the packaging for the executable to be deployed in the device. The .sisx file is a signed .sis. Both the .sis and .sisx file can be created very easily with Carbide C++. 
     150=== Set the .pkg File to be Used === 
     152First we'll need to configure the .pkg file to be used to generate the .sisx file. PJSIP provides some sample .pkg files which can be used, however there may be few editing needed before you can use them (this is because the .pkg file contains absolute directory path for your Symbian SDK, which may be different on your installation). 
     154Assign the .pkg file to be used by the project by selecting Project Properties: 
     158Then Project Properties dialog will appear. On this dialog: 
     160 1. Select ''Carbide Build Configuration'' from the tree (left part of the dialog). 
     161 1. Make sure that the Active Configuration is set to '''Phone Debug (GCCE) [S60_3rd_MR]''' (the SDK name will be different, if you use different SDK version) 
     162 1. Set the ''PKG File'' by clicking ''Browse...'' button, and choose {{{symbian_ua_udeb.pkg}}} from PJSIP's {{{build.symbian}}} directory. 
     164We can leave the "SIS creation and Signing" settings empty to use the default settings. 
     166The dialog window now should look like this: 
     170Press ''OK'' button to save the project configuration. 
     172Now right click '''bld.inf''' (or '''pjproject''') and click '''Refresh''': 
     176Wait for few seconds (30 seconds on my computer) for Carbide to do its job, once it's done, you will see the .pkg file in the ''Project Navigator'' pane: 
     181 The picture above displays ''symbian_ua.pkg'' in the tree, while actually it should display ''symbian_ua_udeb.pkg'' instead. 
     183=== Edit the PKG File === 
     185As said earlier, the PKG file contains absolute directory path for the SDK, so you may need to edit it if your SDK location is different than the one specified in the PKG. 
     187Edit the PKG by ''double clicking'' it in the ''Symbian Project Navigator'' pane. Check out these lines in the PKG file: 
     190; Target 
     194Check that the SDK path is correct. 
     196Once you are done with the modification, save the file. We can close the PKG file editor window now. 
     199=== Build the SISX File === 
     201Once PKG has been setup on the project, a SISX file will be created everytime we build the project. So lets build the project now. 
     203Right click '''bld.inf''' or '''pjproject''' from the ''Symbian Project Navigator'' pane, and select '''Build Target Only''': 
     207The build process will start. You can take a peek on the '''Console''' tab to see what's being done. Once the build process completes, you should see something like this on the '''Console''' tab: 
     212***SIS Creation Complete 
     214Total Time: 12 sec 
     218Check the '''Problems''' tab again to see if we have any errors (there shouldn't be any). 
     224== Configuring On-Device Debugging == 
     226Make sure the phone is connected to the PC using the data cable. 
     228=== Configuring Device Security === 
     230By default, your phone does not allow self-signed certificate to be installed on the phone, I think. To change this setting: 
     231 1. Go to '''Menu''' --> '''Tools''' --> '''App. Mgr''' 
     232 1. On ''App. manager'', select menu '''Options''' --> '''Settings''' 
     233 1. Set '''Software installation''' to '''All''' 
     235=== Installing TRK Application on the Phone === 
     237Install TRK support on the phone. The TRK application can be found in '''{{{C:\Program Files\Nokia\Carbide.c++ v1.2\plugins\\trk\s60}}}''' directory. For my phone, the one that works is '''{{{s60_3_0_app_trk_2_7.sisx}}}'''. Right click this .sisx file and select '''Install with Nokia Application Installer''': 
     241When asked if we want to install, click '''Yes''': 
     245On the PC, this window should be displayed.  
     249Leave it this way, the installation will start on the phone now. Your phone should display something like this: 
     253Click Yes. 
     255Now the phone will display '''Details''' information: 
     259Click Continue. 
     261Your phone may now display the target memory location: 
     265Select the memory and press '''Select''' menu. 
     267Now the phone will display license agreement: 
     271Click '''OK''' (if you agree, of course). The phone should display installation progress window for couple of seconds now: 
     275Once it's done, '''Installation Complete''' window will appear briefly: 
     279TRK is now installed on the phone. Next step is to run it. 
     282=== Running TRK Application on the Phone === 
     284 1. Run it from '''Menu''' --> '''Installations''' --> TRK (it may be different on your phone). 
     285 1. When it asks to switch on Blueetooth, click '''No'''. We use USB cable for this session. 
     286 1. The TRK window will appear. We can ignore the error message for now: 
     290 1. Select '''Options''' --> '''Settings''' menu. 
     291 1. Change the '''Connection''' to USB, and leave all settings unchanged: 
     295 1. Click '''Back''' to get back to TRK main window. 
     296 1. Now select '''Options''' --> '''Connect''' from the menu. 
     297 1. TRK main window should display '''Status: Connected''' now: 
     301Leave TRK running on the phone for the duration of this tutorial. 
     304=== Finding the COM Port Mapping for the Phone Connection === 
     306Find out which COM port is the phone connection mapped to, in Device Manager: 
     310In this case, the COM port is COM3. Note this COM port number, as we will need to specify it in Carbide. 
     313=== Configure the Debug Settings in Carbide === 
     315Back to Carbide. 
     317Next we will need to create a new on-device debugging configuration. 
     319Select '''Run''' --> '''Debug...''' from the main menu: 
     323'''Debug''' dialog will appear like below: 
     327==== Create a new Debug configuration for on-device debugging ==== 
     329Right-click '''Symbian OS App TRK''', and click '''New'''. 
     331New configuration will appear on the dialog. We need to edit few things: 
     332 1. Rename the configuration name from '''pjproject Phone Debug...''' to '''symbian_ua Phone Debug...''', as seen in the picture below. (Hints: when we have different executable to debug, we will create different configuration). 
     333 1. Set the ''Executable'' 
     334 1. Set the ''Remote process to launch'' 
     336You should see something similar to the image below. 
     340Now click on '''Apply''' button. The configuration name on the left tree now will get updated. 
     342==== Configure TRK Connection ==== 
     344Now select '''Connection''' tab. Choose the '''Serial Port''' to the COM port where your phone connection is mapped to, which you have found out from the step above (look at the Device Manager). In my case, it was COM3: 
     348The ''Baud Rate'' setting should match the setting on the TRK application running on the phone. Since we have not changed this setting, just accept the default value (115200). 
     350Now click on '''Apply''' button.  
     352==== Configure SIS File ==== 
     354Now select the '''Installation''' tab. Browse the .sisx file from PJSIP's {{{build.symbian}}} directory: 
     358Now click '''Apply''' button 
     360We are now ready to perform on-device debugging! Get yourself some tea, you deserve some break. 
     363=== Debugging Application === 
     365Still in the '''Debug''' dialog, press the '''Debug''' button. Hold your breath! 
     367Carbide now may rebuild the project (you may take a peek on what it's doing by looking at '''Console''' tab). Once it's done, Carbide will switch to ''Debug Perspective'' and the SIS file will be downloaded to the phone and this window will appear briefly: 
     371When this window dissappear, you should see the application runs on the phone: 
     375You may make calls, receive calls, do presence stuffs, etc. Full debugging should also be possible; you may set breakpoints, step into functions, etc. 
     380== Common Problems == 
     382=== Problem with Build/Clean === 
     384Sometimes Carbide does not build the project properly after we make some changes to the source. This will cause the old code to be built instead of the new changes. 
     386My standard work flow is to always clean the library/application project containing the modified source before building the whole project, to make sure that the modified libraries/application gets rebuilt properly. 
     389=== I/O Error: File in Use (I/O Fault) === 
     391Sometimes .SIS creation fails with I/O error message in the ''Problems'' pane similar to this message: 
     394file I/O fault 
     395makesis.exe returned with exit value == 1 
     396The process cannot access the file because it is being used by another process. 
     399This sounds like a generic error from the build system, and it may be caused by several problems. You can try these and see which one solves it: 
     400 1. First check that the build process has completed without errors (a build error will cause the executable not to get built, and this will cause .sis creation to fail).  
     401 1. Rather than selecting "Build Target Only", try with "Build Project" from the menu. Sometimes build directories are not created when "Build Target Only" is used. 
     402 1. Try cleaning and re-building the project. 
     403 1. Sometimes restarting Carbide C++ also fixes it. 
     406=== TRKProtocolPlugin: Failed to download the specified file to target === 
     408I had experienced this few times. The file seems to be downloaded to the phone fine (the download progress bar shows progress), but once debugging starts Carbide displays "Carbide Alert": "Load Failed", "TRKProtocolPlugin: Failed to download the specified file to target" (as shown in the picture below). 
     412I'm not sure what's causing this, but closing TRK on the phone, then reconnecting the USB cable and restarting TRK seems to have fixed this. 
     414=== TRKProtocolPlugin: Failed to continue thread === 
     418The solution is similar to above. 
     420=== TRK Not Running Error === 
     422Sometimes I get Carbide complaining about TRK not running: 
     427Target request failed: TRKProtocolPlugin: Can't connect to TRK 
     428(TRK may not be running on the phone or mismatch between selected and 
     429connected com port.). 
     432Like this dialog: 
     436If you see TRK is running on the phone, it means that your phone is hung now. Restart the phone by disconnecting the USB cable, taking of the battery, put it back on, start the phone, connect the USB cable, and re-run TRK again. 
     439=== High Audio Latency === 
     441We're working on this issue. 
     443=== Random Crash/Stack Size Problem === 
     445When you have random crash (sometimes in ICE/pjnath or in DNS SRV resolver) or KERN-EXEC 3 when running without debugger, check if increasing stack size in the MMP fixes the problem. The default stack size (8KB) '''is not sufficient''', hence in {{{symbian_ua.mmp}}} the EPOCSTACKSIZE setting is set to 12KB. 
     449== Other Resources == 
     452 - [ Carbide.c++: Setting up On Target Debugging | NewLC] - this article describes how to set up on-device debugging using Bluetooth connection.