Trace Documentation Errors & Omissions


#1

Undocumented ADL traces: https://forum.sierrawireless.com/t/undocumented-adl-trc-trace-levels-used-internally-by-adl/1371/1

This is not true!

The ADL trace function in the embedded Application is not limited to 6 parameters and does not ignore additional parameters.

The limitation is only in Developer Studio’s ability to display the traces - see: https://forum.sierrawireless.com/t/ds-1-2-0-2-0-0-trace-limitation/5049/1

A note should also be added about the %f bug - at least, a cross reference to where that is described

(when will this bug be fixed??)

  1. There is no “Application Initialization service” - it is called the Application Entry Points Interface
  2. The Task Initialisation Table does not affect what flow is used - it’s always ‘ADL’

“CUS4” was changed to “ADL” years ago: https://forum.sierrawireless.com/t/undocumented-adl-trc-trace-levels-used-internally-by-adl/1371/1

I have never seen this appear anywhere in any Traces - what does this mean?