Use carbide C ++ 2.0 to set up a debugging environment for a real machine Debug on s60 Nokia 6120c

Recently, I officially started learning about the development of Nokia s60. The first basic problem I encountered was how to build a debug debugging environment on a real machine. My mobile phone is Nokia 6120c. The operating system of this mobile phone is Symbian OS v9.2, the development platform is s60 3rd edition, and the Feature Pack 1.

 

For more information, see the articles on debugging carbide C ++ and Nokia official website. For more information, see:
Http://hi.baidu.com/refyl/blog/item/294f5ad11b15d6309b502788.html (how to debug carbide2.0 online)
Http://blog.csdn.net/hhygcy/archive/2008/11/20/3339388.aspx (carbide online debugging experience)
Http://blog.csdn.net/lius1984/archive/2008/06/19/2564254.aspx (s60 real machine debugging notes)
Http://www.forum.nokia.com/info/sw.nokia.com/id/7ce0e6e5-737b-4ac4-8959-9367281cd8ca/On_device_debugging_with_Carbide_cpp.html (Video carbide C ++ 1.3)

As a result, the phone crashes frequently and restarts during the first setup. After a crazy Google search + ask someone for advice + Post help on csdn/devdiv, and overnight round-trip, countless tests finally solved the problem and could not guarantee a successful debugging of a real machine, however, I believe some of the experience gained from the above-mentioned Tear test will be helpful for debugging other models of real machines in the future. For this reason, I have compiled this blog post and kept a record.

 

1. Male is afraid of wrong behavior, and female is afraid of wrong marriage. First, you must select the TRK suitable for debugging the real machine. Otherwise, not only will your mobile phone automatically restart once it starts TRK, but even if you are lucky to successfully start TRK, once you start debug, 100% of your mobile phone will be restarted on a black screen, and debug will certainly fail 100%.

 

 

It is estimated that the correspondence between the mobile phone development platform and the carbide C ++ 2.0 device OS is as follows:
1. s60 3.0.0 corresponds to s60 3rd ed
2. s60 3.1.0 corresponds to s60 3rd ed FP1
3. s60 3.2.0 corresponds to s60 3rd ed fp2
4. s60 5.0.0 corresponds to s60 5th Ed

If you are not clear about the operating system for debugging the mobile phone, you can go to the Nokia official website to query:
Http://www.forum.nokia.com/devices/

 

If you want carbide C ++ 2.0 to download the latest TRK, you can use DEBUG configurations-> Symbian OS application TRK-> your app phone debug (gcce) -> main-> Use connection-> edit-> next-> install remote agents, select the latest TRK version, and click the "Install" button below, this installation method will automatically connect to the Internet, download the selected TRK, and then automatically install it on the debugging mobile phone that is connected to the computer (if no response is returned, multiple times ). If your computer is not connected to the Internet or you do not want to use the latest TRK, you can also install/carbide in the carbide installation directory. c ++ V2.0/plugins/COM. nokia. carbide. TRK. support_1.4.0.014/TRK/s60, find the corresponding TRK 3.0.8 installation package, I tested, as long as you select the device OS (see the above ing), whether it is TRK 3.0.8 or TRK 3.1.2, you can successfully build a debugging environment for a real machine.

 

Note: Compared with TRK 3.1.2, TRK 3.08 can modify one more setting, that is, the port used for the connection. TRK 3.1.2 is estimated to simplify the developer's configuration and set the port to 1, and cannot be modified. However, if the COM1 of your computer has been occupied by other peripherals, the Nokia PC kit can only use other COM ports to establish communications between the computer and the mobile phone, the tragedy is estimated to happen ......

 

2. Is everything ready for use, but what's worse? Make sure that the debugging mobile phone is connected to the computer. After installing and starting the appropriate TRK, select the COM port used by your mobile phone in the "Serial Port" of set connection settings of carbide C ++, the operating system for debugging the mobile phone is also selected in the device OS. Click the "initiate service testing" button in "ensure TRK is running on the device" and return the version similar to "installed TRK is latest available: version = 3. x. x. However, debugging on the real machine fails at the beginning. Tragedy, why?

 

Don't worry. Check the port (COM and LPT) in the "Device Manager" of the computer. What is the comport used for debugging the mobile phone? Then let's see how many TRK ports are on the debugging mobile phone? Are the two identical? Congratulations, you have met the second tragedy I have ever encountered. In a few minutes, I used the USB port on the computer to connect to the mobile phone. The system actually assigned com17 to establish a connection with the debugging mobile phone. The TRK installed on my mobile phone is 3.1.2, and the port is always 1, this is the tragedy. Same? If the same or debugging fails, I can't do the same. You can try Google again.

 

If the same tragedy has already been staged, there is still a way to turn it into a drama. Go back to the "Device Manager" on the computer, select the COM port used for debugging the mobile phone, and enter its properties configuration window. In "Port Settings", click "advanced" below. Haha, you can modify the port number and change it to the port number set in TRK. Try again...

 

 

Iii. repeated defeats? If it still fails, try the classic solution of windows blue screen, restart the computer and mobile phone once, and reconnect again. Make sure the two use the same comport for connection, after "initiate service testing" is successful, try again. Persistence is everything. In my desperate life, I have proved the correctness of this sentence countless times.