2 <html> |
2 <html> |
3 <head> |
3 <head> |
4 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> |
4 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> |
5 <meta http-equiv="Content-Style-Type" content="text/css" /> |
5 <meta http-equiv="Content-Style-Type" content="text/css" /> |
6 <meta name="LASTUPDATED" content="06/17/05 11:09:43" /> |
6 <meta name="LASTUPDATED" content="06/17/05 11:09:43" /> |
7 <title>Setup a Virtual Drive for Techview and Cust Kits</title> |
7 <title>Setup a Virtual Drive</title> |
8 <link rel="StyleSheet" href="../../../book.css" type="text/css"/> |
8 <link rel="StyleSheet" href="../../../book.css" type="text/css"/> |
9 </head> |
9 </head> |
10 <body bgcolor="#FFFFFF"> |
10 <body bgcolor="#FFFFFF"> |
11 <h2>Setup a Virtual Drive for Techview and Cust Kits (optional)</h2> |
11 <h2>Setup a Virtual Drive (optional)</h2> |
12 <p>Techview Kits and cust kits have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.</p> |
12 <p>SDKs have kernel components, kernel extensions and device drivers that are typically built on a virtual drive. So if you want to debug them the debugger will need to load files from the virtual drive that the binaries were built on. If you do not know the virtual drive the kit was built on you should first pick a drive letter randomly.</p> |
13 <div class="step"> |
13 <div class="step"> |
14 <h4><a name="runVirDrive" id="runVirDrive"> </a>Setup a Virtual Drive for Techview and Cust Kits</h4> |
14 <h4><a name="runVirDrive" id="runVirDrive"> </a>Setup a Virtual Drive for SDKs</h4> |
15 <ol> |
15 <ol> |
16 <li>To subst a drive, type on a command line:<br /> |
16 <li>To subst a drive, type on a command line:<br /> |
17 > subst <span class="question">drive_letter:</span> <span class="question">path_to_kit<br /> |
17 > subst <span class="question">drive_letter:</span> <span class="question">path_to_kit<br /> |
18 </span>For example:<br /> |
18 </span>For example:<br /> |
19 ><span class="code"> subst M: C:\Symbian\S60_3_0_200626</span></li> |
19 ><span class="code"> subst M: C:\Symbian\S60_5_0_201012</span></li> |
20 <li>On the command line type:<br /> |
20 <li>On the command line type:<br /> |
21 ><span class="code">subst</span><br /> |
21 ><span class="code">subst</span><br /> |
22 <p>You should see the new virtual drive pointing to your kit. If the debugger tries to load a file it can’t find, it will look for it on the virtual drive. You can see this in the stack crawl. The stack crawl should give the full path of the file on the virtual drive the file was built on. The debugger will not be able to load the file until the correct virtual drive is specified.</p> |
22 <p>You should see the new virtual drive pointing to your kit. If the debugger tries to load a file it can’t find, it will look for it on the virtual drive. You can see this in the stack crawl. The stack crawl should give the full path of the file on the virtual drive the file was built on. The debugger will not be able to load the file until the correct virtual drive is specified.</p> |
23 <p>If this happens you can redo the virtual drive to use the drive specified in the stack crawl or navigate to the file using the existing virtual drive. From that point the IDE will add that path and recursively check folders for files it needs.</p> |
23 <p>If this happens you can redo the virtual drive to use the drive specified in the stack crawl or navigate to the file using the existing virtual drive. From that point the IDE will add that path and recursively check folders for files it needs.</p> |
24 </li> |
24 </li> |
25 <li>Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.</li> |
25 <li>Make sure when you set up your default SDK in the Carbide IDE that you use the virtual drive.</li> |
26 </ol> |
26 </ol> |
27 </div> |
27 </div> |
28 <h5>Other references</h5> |
28 <h5>Other references</h5> |
29 <ul> |
29 <ul> |
30 <li><a href="run_mode_debug.htm">Run Mode On-Device Debugging</a> </li> |
30 <li><a href="../../projects/tutorials/run_mode_debug_example_01.htm">Verify System Setup (Run-mode) Tutorial</a><a href="run_mode_debug.htm"></a> </li> |
31 </ul> |
31 </ul> |
32 <div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
32 <div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div> |
33 |
33 |
34 </body> |
34 </body> |
35 </html> |
35 </html> |