mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-02 04:34:59 +00:00
dc7b307a47
The hexdump was earlier printed using 8 bytes in one line like this [00:00:00.131,143] <wrn> sample_instance.inst2: Example of hexdump: 01 02 03 04 05 06 07 08 |........ 09 0a 0b 0c 0d 0e 0f 10 |........ 11 12 13 14 15 16 17 18 |........ 19 1a 1b 1c 1d 1e 1f 20 |....... 21 22 |!" This is not utilizing the width of the output best way possible. Better utilization of the output is to print 16 bytes in one line like this: [00:00:00.131,136] <wrn> sample_instance.inst2: Example of hexdump: 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 |........ ........ 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 |........ ....... 21 22 |!" In order to make it easier to find / calculate the bytes in the output, print the output bytes in 8 byte groups. This has the benefit that it is easier to map the Zephyr hex output to Wireshark output which prints the bytes like this. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Kconfig.template.log_config | ||
| log_backend_native_posix.c | ||
| log_backend_net.c | ||
| log_backend_qemu_x86_64.c | ||
| log_backend_rtt.c | ||
| log_backend_std.h | ||
| log_backend_swo.c | ||
| log_backend_uart.c | ||
| log_backend_xtensa_sim.c | ||
| log_cmds.c | ||
| log_core.c | ||
| log_list.c | ||
| log_list.h | ||
| log_minimal.c | ||
| log_msg.c | ||
| log_output.c | ||