Using its_sysinfo to identify firmware asserts

Symptom

Sometimes when troubleshooting an issue, it is necessary to identify whether a firmware assert has occurred.  The main symptoms that indicate a possible firmware assert are:

1. Multiple channels fail simultaneously

2. Problem can be resolved by re-downloading boards

Procedure

When the firmware of a Dialogic JCT-series Media Board asserts, it writes what info it can about the assert into shared memory.  The its_sysinfo.exe utility that comes with the Dialogic System Release automatically collects a dump of this memory space.  

To detect whether a firmware assert has occurred:

1. Ensure that the board is still in the failed state.  Re-downloading the boards will clean the memory and eliminate any stored information pertaining to asserts

1. Run its_sysinfo.exe

1. Check the its_sysinfo.htm file

For most boards, the assert area is at memory address 0x7e00, so search the entire .htm file for 0x7e00.  The first 3 hex bytes on that line will identify whether any problems occurred with the firmware.  Note: 4 port boards such as the D4PCIU series of boards have only 8K of shared memory, and the assert area is at 0x1e00 instead.

Possible patterns are:

00 00 00 -- No problems
01 00 01 -- Firmware assert occurred
02 00 01 -- Firmware warning occured.  This may be benign, or may be a problem.  Tech support may be needed to identify whether this is root cause.

Example of assert area showing firmware assert

Product List

Dialogic JCT-series Media Boards