Lauterbach Trace32 Setup Guide.ppt

lauterbach trace32 setup guide,zhao xiaoliang & yang fengkai for p1a&p1b,2/5/2019,confidential,2,contents,setup preparation trace32 startup tips,setup preparation,lauterbach software installation install lauterbach software from tddlte09-tools lauterbachsoftware follow the following steps to install the lauterbach software,2/5/2019,confidential,3,setup preparation,patch copy and replace three patches of the following folder to the c:t32 directory tddlte09-toolslauterbachpatch20090921 drivers if usb driver is not available when plugging usb, choose driver from the following folder tddlte09-toolslauterbachsoftwarebin windowsdrivers or manually copy t32usb.sys to c:windowssystem32drivers,2/5/2019,confidential,4,setup preparation,license and configuration copy the license file(license.t32) and the configuration file (config.t32) from the following path to “ c:t32“ tddlte09-toolslauterbach open the configuration file (config.t32), and change “tmp=c:docume1dp037locals1temp” to “tmp=c:docume1locals1temp”,2/5/2019,confidential,5,setup preparation,scripts copy the scripts from the following folder to “c:t32script“ tddlte09-toolslauterbachscript for p1a find t32_usb.ts2 from the following folder with an editor c:t32scriptp1a_scriptsu7xxpcsally make a shortcut of t32_usb.ts2 to you desktop, and change the name of shortcut to “pc-sally t32_usb.ts2” for p1b find t32_usb.ts2 from the following folder with an editor c:t32scriptp1a_scriptsu7xxsally make a shortcut of t32_usb.ts2 to you desktop, and change the name of shortcut to “sally t32_usb.ts2”,2/5/2019,confidential,6,setup preparation,source files collection source files for phy sw you can find the source files in “c:sdecccrh1090667_lte_phycrh1090667_main_lte_phy_lm_debugrvctsrc” or “c:sdecccrh1090667_lte_phycrh1090667_main_lte_phy_lmrvctsrc” source files for mcore for p1a b700 the source files for mcore can be found in tddlte04-physw05-versions04_p1a_versions02_p1a_r1a056crh1090667crh1090667_p1a014execrh1090672_mcore_pc_cardrvct-nandsrc for p1b b700 the source files for mcore can be found in tddlte04-physw05-versions08_p1b_versions02_p1b_r2c013crh1090667crh1090667_p1b004execrh1090672_mcore_pc_cardrvct-nandsrc for p1b p700 the source files for mcore can be found in tddlte04-physw05-versions08_p1b_versions02_p1b_r2c013crh1090667crh1090667_p1b004execrh1090672_mcore_pc_card_p700rvct-nandsrc,2/5/2019,confidential,7,setup preparation,load file unified mcore elf file is used for p1a b700 you can find the crh1090672_mcore_pc_card_debug.elf for p1a version in “tddlte04-physw05-versions04_p1a_versions02_p1a_r1a056crh1090667crh1090667_p1a014execrh1090672_mcore_pc_cardrvct-nandexecrh1090672_mcore_pc_card_debug.elf “and it will be released with p1a version release. for p1a b700 you can find the crh1090672_mcore_pc_card_debug.elf for p1b version in “tddlte04-physw05-versions08_p1b_versions02_p1b_r2c013crh1090667crh1090667_p1b004execrh1090672_mcore_pc_cardrvct-nandexecrh1090672_mcore_pc_card_debug.elf “ and it will be released with p1b version release. for p1a p700 you can find the crh1090672_mcore_pc_card_debug.elf for p1b version in “tddlte04-physw05-versions08_p1b_versions02_p1b_r2c013crh1090667crh1090667_p1b004execrh1090672_mcore_pc_card_p700rvct-nandexecrh1090672_mcore_pc_card_debug.elf “ and it will be released with p1b version release.,2/5/2019,confidential,8,setup preparation,user cmm file after start t32, you should here you can load a private cmm file which may contain other loadmodule elf files and their source path or add some breakpoints be sure that the loadmodule which will be loaded is a debug version for p1a you can find the example file(loadlte.cmm) in tddlte09-toolslauterbach put loadlte.cmm into c:t32 for p1b you can find the example file(loadlte_sally.cmm) in tddlte09-toolslauterbach put loadlte_sally.cmm into c:t32,2/5/2019,confidential,9,setup preparation,hardware set a jumper to on/off(b),2/5/2019,confidential,10,trace32 startup,powering order connect the lauterbach while the b700/p700 board powered off to the jtag/etm connector switch on the lauterbach switch on the b700/p700 board switch off is in the other order,2/5/2019,confidential,11,trace32 startup,step 1: press the debug halt button and hold until step 5 finished this step is necessary to stop boot-rom code running in a normal way,2/5/2019,confidential,12,trace32 startup,step 2: power on the b700/p700 board step 3: double click the sally t32_usb.ts2 or pc-sally t32_usb.ts2 shortcut on the desktop for p1b or p1a, the following dialog will popup, press start button on the right side.,2/5/2019,confidential,13,trace32 startup,three windows will appear for different cpus,2/5/2019,confidential,14,trace32 startup,for dat cpu dialog, there are five buttons with different colors: green button : used for setup yellow button : used for loading the software itself red button : used for resetting (currently this button does not work) purple button : used for synchronization of the 3 cores in case of a breakpoint teal button : used for etm setup - which side to be traced for the dialog of lte cpu and acc cpu, only first three button above exists.,2/5/2019,confidential,15,trace32 startup,step 4: set the “target setup dialog” this dialog can be called by pressing the green button pc sally flash setup flashed by pa in advance use the following setting data cpu: nand /nocode /vm /strippart 0 access cpu: nand - /nocode / vm /strippart 0 lte cpu: nand - /nocode / vm /strippart 0 kernel/ main load file load the crh1090672 debug elf files as follows: all three cpu: crh1090672_mcore_pc_card_debug.elf source path: choose the directory src for mcore as page 6 said use custom cmm file choose a cmm file only in dat cpu, and the path is “c:t32loadlte.cmm” for p1a or “c:t32loadlte_sally.cmm” for p1b. leave other options as their defaults,2/5/2019,confidential,16,trace32 startup,step 5: press the yellow load button in dat window to load the elf files. after all loaded, the state of dat window is “system ready” and the state of lte and acc window is “running”,2/5/2019,confidential,17,trace32 startup,step 6: set breakpoint for example, if we want to debug lte cpu precondition: crh1090667_main_lte_phy_lm_debug.elf is loaded by cmm file and source path is spicified method i: menu: break-set to set a breakpoint note: you could not see the code because the state is running, but the debug unit is available method ii: step 7 after usb cable connected (debug