5/10/2012

How to debug the modem on 8960 using TRACE32

In DAP T32 shortcuts, all the processors are on DAP whereas in Dynamic T32 shortcuts, Q6 processors are in daisy chain & other processors are in DAP chain. Customers will have to use DAP shortcuts. DAP shortcuts are supported starting for june2011 version of T32. This version of trace is officially distributed by lauterbach.

 

Right now, std_debug.cmm cannot be used for debugging modem. Currently, new subsystem debug architecture is being implemented by blast kernel team. Once we have that, std_debug.cmm can be used for debugging modem.

 

For now, you need to follow the below steps to debug modem. You will need a debug image of modem to debug it.

 

1.       Run pil-debug.py(modem_proc\core\products\tools) on dsp1.mbn(i.e modem sw binary) to generate dsp1_isdb.mbn

2.       Run python pil-splitter(modem_proc\core\securemsm\tzbsp\build\scripts) on dsp1_isdb.mbn to obtain split images

3.       Push these split images on the device using adb

4.       Sync and power cycle.

5.       Let the Android UI come up

6.       Attach JTAG to RPM, Krait and Q6.

7.       Run do std_loadsyms_modem.cmm on Q6 window. This will load the symbols & set the breakpoints at all error cases.

 

pil-debug.py usage details

Usage:  python pil-debug.py <input mbn/elf file>  <output image file name>

Ex: python pil-debug.py dsp1.mbn  dsp1_isdb.mbn   


Note: this step is no longer needed from FC release (1020 build)

No comments:

Post a Comment