|
1 // Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies). |
|
2 // All rights reserved. |
|
3 // This component and the accompanying materials are made available |
|
4 // under the terms of the License "Symbian Foundation License v1.0" |
|
5 // which accompanies this distribution, and is available |
|
6 // at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html". |
|
7 // |
|
8 // Initial Contributors: |
|
9 // Nokia Corporation - initial contribution. |
|
10 // |
|
11 // Contributors: |
|
12 // |
|
13 // Description: |
|
14 // |
|
15 |
|
16 Purpose |
|
17 This corehci allows you to run tproxy whilst the associated serial port is still connected to a controller |
|
18 (for example a Casira). |
|
19 It obviates the need to replace the controller with a null modem connection to a second serial port |
|
20 on which you would have hcemeulator running. It therefore obviates the need to configure the hci to use the |
|
21 h4 (uart original) host controller transport layer (hctl). |
|
22 |
|
23 What does it do? |
|
24 This is the standard Symbian Core HCI branched (Nov 2008) and modified to intercept Vendor specific commands. |
|
25 Instead of passing vendor specific commands down to the HCTL, it sends back a corresponding command complete |
|
26 event with an event payload identical to the payload in the vendor specific command. Further more, prior to |
|
27 sending back the corresponding command complete event it sends several vendor specific debug events. |
|
28 This is an advantage over hcemeulator which requires user input to send vendor debug events. |
|
29 |
|
30 How do you set it up |
|
31 Just compile this core hci. The config files are automatically exported, though, to be |
|
32 sure, do an "abld test reallyclean" first .... or simply use the supplied bldcorehci.bat file |
|
33 |
|
34 Constraints |
|
35 It only works with HCI_V2. |
|
36 |
|
37 Warning |
|
38 If debugging in Carbide make sure you do not debug from a project containing the HCI source tree. |
|
39 If you do, Carbide may revert your config to using the standard CoreHCI implementation. |
|
40 |
|
41 What tproxy expects |
|
42 tproxy expects the (vendor specific) command complete event. TProxy will handle the vendor debug events. |
|
43 It does not, however, require them. |
|
44 |
|
45 Contact |
|
46 Nick Frankau |