Strange TX_RUNNING not parsed/created

[julianneswinoga]

When comparing tracex_parser output with Azure TraceX Windows app output there is sometimes a minor (but consistent) dependency. It is visible in demo_netx_udp.trx/tests/demo_netx_udp.txt.
This line (permalink) is shown in the Windows app output:

Event Number     Relative Time                   Event                          Context                        Priority                Next Context                    Info1           Info2           Info3           Info4        Raw Time Stamp    Priority Inversion   Raw Event        Raw Priority
     536        00000000000000536000    TX EVENT FLAG GET          (   32)       NetX IP Instance (0000F7F0)           1 (   ?)           NetX IP Instance (0000F7F0)    I1: 0000F89C    I2: FFFFFFFF    I3: 00000000    I4: 00000001        0308B008            0-0             00000020          00000001
     537        00000000000000537000    TX INTERNAL RESUME         (    1)       Interrupt                      0000F7F0                  NetX IP Instance (0000F7F0)    I1: 0000FEA4    I2: 00000003    I3: 00029C8C    I4: 0000F7F0        0308B3F0            0-0             00000001          0000F7F0
 >>> 538        00000000000000537012    TX RUNNING                 (    6)       NetX IP Instance (0000F7F0)           1 (   ?)           NetX IP Instance (0000F7F0)    I1: 00000000    I2: 00000000    I3: 00000000    I4: 00000000        0308B3FC            0-0             --------          --------
     539        00000000000000538000    TX TIME SLICE              (    5)       Interrupt                      0000F7F0                  NetX IP Instance (0000F7F0)    I1: 0000FEA4    I2: 00000001    I3: 00000001    I4: 00029CA4        0308B7D8            0-0             00000005          0000F7F0
     540        00000000000000539000    TX INTERNAL SUSPEND        (    2)       NetX IP Instance (0000F7F0)           1 (   ?)           System Timer Thr (0000FEA4)    I1: 0000F7F0    I2: 00000007    I3: 0002C434    I4: 0000FEA4        0308BBC0            0-0             00000002          00000001

This is very strange because that line (or any of the resulting values) do not appear anywhere else in the raw trace dump! The time of the event is also pretty strange (offset by 12? Everything else is on 1000) but perhaps this could be explained because it is in an interrupt context?
The ThreadX source code doesn't really tell us anything special about TX_RUNNING either...

☹️ ☹️ ☹️