DigRF Protocol Analyzer TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents... PowerIntegrator... PowerIntegrator Application Notes... DigRF Protocol Analyzer... 1 General Function... 2 Probes 4 Target Connector 5 How to use the PROTOanalyzer... 6 Features 6 <trace>.list LIST display 7 <trace>.chart CHART display 9 <trace>.statistic Statistic visualization 9 <trace>.draw Draw I/T Q/T graphs 10 Menu... 11 FAQ... 12 DigRF Protocol Analyzer 1
DigRF Protocol Analyzer Version 22-Mar-2018 General Function 3G/DigRF trace support requires the following hardware components: PowerIntegrator (logic analyzer) three 3G/DigRF specific probes A 3G/DigRF specific menu setup can be found on the installation CD. This setup file does the basic PowerIntegrator settings and adds a DigRF pull down menu to the TRACE32 GUI. see: ~~/demo/powerintegrator/probedigrf copy all files to your TRACE32 working directory and run the setupdigrf.cmm file. The PowerIntegrator is configured in a 2 GSample/s mode and has to be connected to any type of TRACE32 debug box. In 2 GSample/second mode the number of PowerIntegrator trace-channels is limited to 4 signals. The PROTOanalyzer decodes the whole transmission, considering the 3G/DigRF specifications. DigRF Protocol Analyzer 2
The results of the Protocol Analysis are time correlated to other TRACE32 tools. This way there is a close linkage between the display of 3G/DigRF activity and program-execution and vice versa. For 3G/DigRF the PowerIntegrator provides: two channels with a sampling rate of 2 GSample/s for RX, TX sampling. For 3G/DigRF mode 312 MHz this means 6 samples per bit. two channels with a sampling rate of 125 MSample/s for status signal sampling like SysClkEn and SysClk. For 312 MHz mode a maximum of around 8MBits (3G/DigRF bits; for RX, TX each) can be traced. For low/mid speed mode a maximum of around 512 KBit (3G/DigRF bits) can be traced. Transient detection prevents recording as long as there is no signal activity which expands the recording time. The minimum recording time is 25 ms. DigRF Protocol Analyzer 3
Probes The probes only can be used with a PowerIntegrator, they are not supported by the PowerTrace II! Two probes to capture the differential inputs of one RX and one TX channel One probe to capture the single ended inputs of SysClkEn and SysClk Active probe design to capture signals close to the target. This minimizes target signal disturbance Voltage range 0 3.3 V, less then 1 pf capacitive load, 700 k input resistance Probe connection to PowerIntegrator: Connector-A: Single-ende probe for SysClk and SysClkEn tracing. Connector-C: Differential probe for RX tracing. Connector-E: Differential probe for TX tracing. NOTE: Tracing of SysClk and SysClkEn is optional. The PROTOanalyzer can handle the missing signals. DigRF Protocol Analyzer 4
Target Connector Top view of target connector Signal assignment of the three 6-pin connectors Probes Pin-1 Pin-5 Probe-A (single ended) SysClkEn (any) SysClk (any) Probe-C (differential) RXp RXn Probe-E (differential) TXp TXn DigRF Protocol Analyzer 5
How to use the PROTOanalyzer First of all a recording of the 3G/DigRF activity has to be done. Based on this recording various types of protocol displays can be done. For offline analysis the recordings can be saved to disk. When loaded back to the TRACE32 system or to the TRACE32 simulator this data set can be used as base for the PROTOanalyzer. The PROTOanalyzer requires a 3G/DigRF specific file (ProtoDigRF.dll) which contains the algorithm to analyze and display the recorded transmission. The source code and the ProtoDigRF.dll file is part of the installation CD. The code matches the TRACE32 Protocol Analysis interface. It is open for user modifications to add application specific analysis and display levels. RX and TX transmissions are decoded independently and they are displayed in separate windows. The linkage between the windows is done by the TRACE32 tracking system (use option /TRACK) Literature on installation CD: protocol_app.pdf protocol_user.pdf The PROTOanalyzer also can be used for saved recordings. Features LIST display: Shows the appearance of 3G/DigRF transmissions as a listing. CHART display: Shows the period of time in which a transmission was active. STATISTIC display: Shows how often specific transmissions were active. Additionally it calculates the min/max and average transmission times. DRAW display: Shows the I and Q data of the payload as time correlated graph DigRF Protocol Analyzer 6
<trace>.list LIST display Format <trace>.protocol.list <file> <chantype> <Chan-> <.> Base Command <trace>.protocol.list File: protodigrf.dll ChanType type of differential signal to be analyzed RX for RX+/- RXn for RX-/+ (in case of inverse signal polarity) TX for TX+/- TXn for TX-/+ (in case of inverse signal polarity) Chan channel name of differential input signal, e.g. i.rx or i.tx SysClkEn Type type of SysClkEnable signal ENA for SysClkEn+ ENAn for SysClkEn- (in case of inverse signal polarity) NONE if no SysClkEn signal is traced SysClkEn Chan channel name of SysClkEn signal, e.g. i.sysclken NOTE: not requested if SysClkEnType==NONE SysClk Frequency frequency of 3G/DigRf SystemClock 19MHZ for 19.2 MHz 26MHZ for 26.0 MHz 38MHz for 38.4 MHz ClockMode Def default ClockMode at start of PROTOanalysis LOW for SysClk/4 MID for Sys Clk HIGH for 312 MHz DigRF Protocol Analyzer 7
DigRF Protocol Analyzer 8
<trace>.chart CHART display The command format has the same structure as that one above. Only the BaseCommand is different. Format <trace>.protocol.chart <file> <chantype> <Chan-> <.> BaseComman d <trace>.protocol.chart This visualization shows the duration of every transmission frame and when the bus is in sleep or idle mode. It s very useful for checking the traced transmissions for any errors or rare message frames. <trace>.statistic Statistic visualization The command format has the same structure as that one above. Only the BaseCommand is different. Format <trace>.protocol.statistic <file> <chantype> <Chan-> <.> BaseComman d <trace>.protocol.statistic This visualization shows the share of every transmission type. It s very useful for checking the transmission timing. This way critical timings can be found easily. DigRF Protocol Analyzer 9
<trace>.draw Draw I/T Q/T graphs The command format has the same structure as that one above. The BaseCommand is different and as additional parameter the 3G/DigRF channel of the I/Q data has to be selected. Format <trace>.protocol.draw <file> <chantype> <Chan-> <.> BaseComman d <trace>.protocol.draw I/Q Channel channel select: ChanA, ChanB, ChanC, ChanD DigRF Protocol Analyzer 10
Menu A 3G/DigRF specific menu setup can be found on the installation CD. This setup file does the basic PowerIntegrator settings and adds a DigRF pull down menu to the TRACE32 GUI. see: ~~/demo/powerintegrator/probedigrf copy all files to your TRACE32 working directory and run the setupdigrf.cmm file. The menu topic Config DigRF Params opens a file which contains the default parameters for the PROTOanalyzer. These parameters are used when activating one of the menu topics. Please modify the parameters to your requirements. DigRF Protocol Analyzer 11
FAQ Q: The timing display does not show any channel A: Check if the single ended probe is connected to PowerIntegrator connector A. Q.: The traced raw material is full of spikes. A.: Try to adjust the threshold of the Single Ended Probe. Q.: The PROTOanalyzer shows a lot of protocol errors. A.: Check if the probes are connected correctly. Check the parameter settings of the PROTOanalyzer.Check for spikes and adjust the threshold. Q.: The PROTOanalyzer shows nothing, but the timing display shows activity. A.: Check the setting of the Default-Clock-Mode. The PROTOanalyzer has to know the current ClockMode to detect the 3G/DigRF bits. The PROTOanalysis starts calculation with the Default-Clock-Mode setting. A: Check the SysClkEnable signal. Try PROTOanalysis with SysClkEnType=NONE. DigRF Protocol Analyzer 12