| 5.17. DEBUG commands | ||
|---|---|---|
 | Chapter 5. Command language |  |
| 5.17. DEBUG commands | ||
|---|---|---|
| | Chapter 5. Command language | |
Debug commands show advanced diagnostic about Abilis CPX system and resources. These type of commands need administrator or super user rights.
![[Note]](../images/note.png) | Note |
|---|---|
Shown information is strictly technical and meaningless for the user; Abilis CPX technicians could need it for detecting and solving eventual problems. |
By typing the following command, it is possible to display the syntax.
[12:43:19] ABILIS_CPX:debug ?BM Display Boot Manager configuration file CPXRUN Display CPX Run configuration file FILE File system information and statistics IRQ Interrupts information and statistics MEM Memory information and statistics PCIDEV Display PCI service debug information PO: CPX port number [0..999] RES: Resource identifier 'type-n', where 'n' can be [1..999] SIMULATE Simulate an event for debugging purposes TASK Tasks information and statistics USBDEV Display USB service debug information WDGMEM Watchdog memory
This command shows debugging information about the specified resource. By typing the following command, it is possible to display the command syntax.
[12:43:19] ABILIS_CPX:debug res: ?DEBUG RES:val [par:val] Display debug information of a resource Additional parameters: LAYER: Select resource lower layer [L2, LINK, LAN, IP, IPT, PPP, PPPOE] <Optional, only if PROT: not specified> PROT: Select protocol layer [LAPB, MLM, ML, IPLAN, PLINKE, PPP, POECLI] <Optional, only if LAYER: not specified> SIZE: Select debug buffer size [7..63 Kbytes] <Optional> LSN: Lsn value [0..65534(dec) or 0000..0FFFE(hex), A] <Optional> CMD: Command string. Strings holding spaces must be written between quotation marks (e.g. CMD:"str1 str2 ...") <Optional>
Data are stored in a 6 KB size buffer. Depending on the resource
type, where the command is executed on, this buffer could not be enough
and at the end of the visualization the following message will be
displayed “INCOMPLETE INFORMATION: BUFFER SIZE TOO SHORT”.
By using the option SIZE, the user can eventually
increase the maximum buffer size used by the command. The indicated
value (in KB) must be in the interval [7 - 63].
By using the options LSN and
CMD it is possible to select the type of debugging
information to be displayed.
For example, to show debugging information of an ADSL line, type
the command debug res:ip-xx prot:ppp, where
xx is the number of the ip resource associated to the
ADSL line. With the options LSN, it is possible to
select the type of debugging information to be displayed; if it is set
to 0, it will be displayed the command help.
[12:43:19] ABILIS_CPX:debug res:ip-5 prot:pppRES:Ip-5 - IP over PPP (PPP) ------------------------------------------------- ADSL-xx.xxx.xxx.xxx/32 BufferLength:384 Date/Time:30/11/2010 16:23:27 TraceTime:67955961 Usage: LSN:0 == This help LSN:1 == Complete debug LSN:2 == Upper/Lower NCB status LSN:3 == Layer states LSN:4 == Link status LSN:5 == Negotiated options LSN:6 == Echo information LSN:7 == RADIUS information LSN:10 == Show CALL log LSN:11 == Show PPP Negotiation log LSN:20 == Clear CALL log LSN:21 == Clear PPP Negotiation log [16:23:27] ABILIS_CPX:debug res:ip-5 prot:ppp lsn:10RES:Ip-5 - IP over PPP (PPP) ------------------------------------------------- ADSL-xx.xxx.xxx.xxx/32 BufferLength:377 Date/Time:30/11/2010 16:23:44 TraceTime:67973497 29.11.10 21:30:51 ********************* 29.11.10 21:30:51 * * * * START * * * * 29.11.10 21:30:51 Calling PLink 29.11.10 21:30:51 Calling PLink - succeeded 30.11.10 13:06:10 Hanging-up PLink - succeeded 30.11.10 13:06:10 ********************* 30.11.10 13:06:10 * * * * START * * * * 30.11.10 13:06:10 Calling PLink 30.11.10 13:06:10 Calling PLink - succeeded
The command DEBUG SIMULATE EVENT:val simulates an event for debugging purposes. Use the following command to show all possible events:
[14:45:58] ABILIS_CPX:debug simulate event: ?
DEBUG SIMULATE EVENT:val Simulate an event for debugging purposes
Possible events:
XCP Structured exception
WDL WDLIVE1 event. It executes a never ending loop without task
switching.
WDGRESET WDG Reset. It resets WDG but doesn't make SW reset of the PC.
BLOCKAGE Complete lock. It disables ALL the interrupts and executes a never
ending loop without task switching.
TSAVE Automatic TRACE saving request (trace stop-save-start)
HOVR Heap overflow (bad allocation exception)This command simulates the structured exception:
[10:47:52] ABILIS_CPX:debug simulate event:xcp
YOU ASKED TO SIMULATE THE 'STRUCTURED EXCEPTION' EVENT.
THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y
PROCEEDING WITH STRUCTURED EXCEPTION EVENT SIMULATION...The log shows the following information:
...
12/05/2011 10:48:15 [00221] I: DEBUG SIMULATE EXCEPTION
12/05/2011 10:48:16 [00029] E: PO1
12/05/2011 10:48:16 [00032] AUTO WARM START
12/05/2011 10:48:52 [00103] -------------------- NEW RUN --------------------
...This command simulates the WDLIVE1 event:
[10:50:16] ABILIS_CPX:debug simulate event:wdl
YOU ASKED TO SIMULATE THE 'WDLIVE1' EVENT.
THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y
PROCEEDING WITH WDLIVE1 EVENT SIMULATION...The log shows the following information:
...
12/05/2011 10:52:26 [00222] I: DEBUG SIMULATE WDLIVE-1
12/05/2011 10:53:19 [00103] -------------------- NEW RUN --------------------
...This command resets WDG but doesn't make Abilis SW reset. It is useful to verify if the watchdog (MFIDE/MFPCI/MFLPC) is really able to make HW reset of the Abilis CPX, and thus if the reset cable is properly connected.
[14:52:17] ABILIS_CPX:debug simulate event:wdgreset
YOU ASKED TO SIMULATE THE 'WDG RESET' EVENT.
THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y
PROCEEDING WITH WDG RESET EVENT SIMULATION...The log shows the following information after using this command:
[14:53:25] ABILIS_CPX:d l
Current Local Time: Wednesday 11/05/2011 14:53:26 (UTC+2.00)
...
11/05/2011 14:39:10 [00092] I: Pv-6 PLink:d2 SLink:ln
11/05/2011 14:39:28 [00092] I: Pv-5 PLink:RD SLink:ln
11/05/2011 14:39:28 [00092] I: Pv-6 PLink:RD SLink:ln
11/05/2011 14:52:23 [00394] I: DEBUG SIMULATE WDG RESET
11/05/2011 14:53:00 [00103] -------------------- NEW RUN --------------------
11/05/2011 14:53:02 [00362] I: WATCHDOG MFIDE3 FW Rev. 11
11/05/2011 14:53:02 [00163] I: SYSTEM RESET
...If the reset does not take place, the only way to restart abilis is using the warm start command:
[06:04:07] ABILIS_CPX:debug simulate event:wdgreset
YOU ASKED TO SIMULATE THE 'WDG RESET' EVENT.
THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y
PROCEEDING WITH WDG RESET EVENT SIMULATION...
WARNING: WDG RESET HAD NOT EFFECT.
******************************************************************************
ATTENTION!
THE SYSTEM MUST BE RESTARTED WITH 'WARM START' COMMAND.
ALLOWED COMMANDs: 'CLOSE', 'EXIT', 'WARM START'.
******************************************************************************This command simulates the system blockage event:
[10:53:45] ABILIS_CPX:debug simulate event:blockage
YOU ASKED TO SIMULATE THE 'SYSTEM BLOCKAGE' EVENT.
THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y
PROCEEDING WITH SYSTEM BLOCKAGE EVENT SIMULATION...The log shows the following information:
...
12/05/2011 10:54:50 [00365] I: DEBUG SIMULATE BLOCKAGE
12/05/2011 10:55:53 [00103] -------------------- NEW RUN --------------------
...This command simulates the trace autosave event (trace stop-save-start):
[11:02:31] ABILIS_CPX:debug simulate event:tsave
YOU ASKED TO SIMULATE THE 'TRACE AUTO SAVE' EVENT.
THIS WILL ACTIVATE CURRENT TRACE AUTOMATIC SAVING (WITHIN 2 min.),
PROCEED (N/Y)?y
PROCEEDING WITH TRACE AUTO SAVE EVENT SIMULATION...
COMMAND EXECUTEDThe log shows the following information:
... 12/05/2011 11:02:39 [00284] I: DEBUG SIMULATE TRACE AUTO SAVE 12/05/2011 11:04:39 [00275] I: TRACE AUTO SAVE: STARTED (TOUT) 12/05/2011 11:04:39 [00279] I: TRACE AUTO SAVE: TRACE STOPPED 12/05/2011 11:04:39 [00280] I: TRACE AUTO SAVE: TRACE SAVED ...
This command simulates the heap overflow event:
[11:03:49] ABILIS_CPX:debug simulate event:hovr
YOU ASKED TO SIMULATE THE 'HEAP OVERFLOW' EVENT.
THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y
PROCEEDING WITH HEAP OVERFLOW EVENT SIMULATION...The log shows the following information:
...
12/05/2011 11:06:44 [00079] I: DEBUG SIMULATE HEAP OVERFLOW
12/05/2011 11:06:44 [00030] E: P02
12/05/2011 11:06:44 [00135] MEMORY SUMMARY:
12/05/2011 11:06:44 [00136] TOT: 134,217,728
12/05/2011 11:06:44 [00137] FREE:59,870,240
12/05/2011 11:06:44 [00138] HU: 59,808,960
12/05/2011 11:06:44 [00139] HLFB:59,870,080
12/05/2011 11:06:44 [00140] HLUB: 8,388,608
12/05/2011 11:06:44 [00032] AUTO WARM START
12/05/2011 11:07:20 [00103] -------------------- NEW RUN --------------------
...| |  | |
| 5.16. Trace functionalities |  | Chapter 6. Licencing |