tree: ab14b4f4e3009dece17ae6c522d5b8980b2ddfc1 [path history] [tgz]
  1. lib/
  2. adsplog.py
  3. cavs-fw-v15.py
  4. cavs-fw-v25.py
  5. cavsload.sh
  6. dump_trace.py
  7. flash.sh
  8. fw_loader.py
  9. logtool.py
  10. mbterm.py
  11. README.md
boards/xtensa/intel_adsp_cavs15/tools/README.md

For various legacy reasons this directory has two similar log tools: logtool.py and adsplog.py

Both may be used in automation so merging them would require some coordination.

They both read from the same data from the exact same shared memory yet they have significant differences:

  • logtool.py reads /sys/kernel/debug/sof/etrace which requires the kernel driver to be loaded.

  • adsplog.py finds the memory address by scanning /sys/bus/pci/devices/; this does not require a driver.

  • logtool.py supports reading from a special QEMU location.

  • logtool.py performs a raw dump of the memory and exits immediately.

  • adsplog.py parses the data, understands the ring buffer and reads continuously. Its output is much more human-readable.

  • adsplog.py has technical details explained in a comment at the top.