Elapsed time logging inserts extra zero

• Reporter: (Anonymous)
• Owner: (None)
• Type: Bugs
• Status: Closed
• Component: Tera Term
• MileStone: Tera Term 4.106 (closed)
• Priority: 5 - Medium
• Severity: 5 - Medium
• Resolution: Fixed
• File: None

Details Reply

When using the elapsed time logging, an extra 0 gets inserted in the log.

Below are two comparisons of a logged bootup from the same Linux embedded device.

The first log was done with local time, the second with the "elapsed time (logging)" option.

As you can see, the SF: 2097152 line took 515ms when using local time logging, but when using elapsed time logging, it reports that it took from 3.0875 to 4.0391s, or 0.9516s. I think it actually took from 3.875 to 4.391s, or 0.516s.

This is a fairly consistent step, bulk loading the Linux kernel from SPI flash, so the speed should be pretty consistent boot to boot.

[2021-05-26 12:03:31.446]  256 Bytes, erase size 64 KiB, total 32 MiB
[2021-05-26 12:03:31.453] SF: 24320 bytes @ 0x70000 Read: OK
[2021-05-26 12:03:31.968] SF: 2097152 bytes @ 0x180000 Read: OK
[2021-05-26 12:03:31.976] Kernel image @ 0x83000000 [ 0x000000 - 0x1ade40 ]

[0 00:00:03.0875]  256 Bytes, erase size 64 KiB, total 32 MiB
[0 00:00:03.0875] SF: 24320 bytes @ 0x70000 Read: OK
[0 00:00:04.0391] SF: 2097152 bytes @ 0x180000 Read: OK
[0 00:00:04.0406] Kernel image @ 0x83000000 [ 0x000000 - 0x1ade40 ]

Ticket History (2/2 Histories)

2021-05-27 02:16 Updated by: None

• New Ticket "Elapsed time logging inserts extra zero" created

2021-05-27 18:02 Updated by: nmaya

• Status Update from Open to Closed
• Resolution Update from None to Fixed
• Milestone Update from (None) to Tera Term 4.106 (closed)
• Component Update from (None) to Tera Term

Comment Reply

Hi,

This issue was solved at r8794, and this change will be included in the next release.

Thank you for your reporting.