This is a very important issue. pyocd directly faces hardware debugging and often needs to know the task, hardware execution time, time interval, and time sequence. It is hoped that a (computer) timestamp function can be added to add a real-time timestamp to each line of debugging output information, and not be affected by the time lag of pyocd buffers and windows pipeline technology.It is hoped that it is a correct and accurate timestamp precise to the millisecond level.
I try the following command:
pyocd rtt -t STM32H750VBTx -a 0x2407fcf0 | powershell -Command "$input | ForEach-Object { "[$(Get-Date -Format 'yyMMdd HH:mm:ss.fff')] $_" }"
In my test, the timestamp given by the above command was incorrect. I'm not sure if it's due to the caching mechanism of pyocd itself or the non-caching mechanism of windows Pipeline technology?
The time interval of the heartbeat packets(+keep_alive) output by this command line is less than 500 milliseconds, while my actual heartbeat interval is one minute.
Test data：
[260509 17:28:49.927] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:28:49.927] +keep_alive
[260509 17:29:50.375] Rcv_en=6
[260509 17:29:50.376] rcvT[7|A5]=8
[260509 17:29:50.376] A5,FA,00,81,0D,00,4A,FB,
[260509 17:29:50.377]
[260509 17:29:50.377] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:29:50.378] +keep_alive
[260509 17:30:50.840] Rcv_en=6
[260509 17:30:50.841] rcvT[7|A5]=8
[260509 17:30:50.842] A5,FA,00,81,0D,00,4A,FB,
[260509 17:30:50.842]
[260509 17:30:50.843] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:30:50.843] +keep_alive
[260509 17:31:51.294] Rcv_en=6
[260509 17:31:51.296] rcvT[7|A5]=8
[260509 17:31:51.297] A5,FA,00,81,0D,00,4A,FB,
[260509 17:31:51.298]
[260509 17:31:51.300] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:31:51.302] +keep_alive
[260509 17:32:51.750] Rcv_en=6
[260509 17:32:51.751] rcvT[7|A5]=8
[260509 17:32:51.752] A5,FA,00,81,0D,00,4A,FB,
[260509 17:32:51.753]
[260509 17:32:51.754] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:32:51.755] +keep_alive
Thanks!
This is a very important issue. pyocd directly faces hardware debugging and often needs to know the task, hardware execution time, time interval, and time sequence. It is hoped that a (computer) timestamp function can be added to add a real-time timestamp to each line of debugging output information, and not be affected by the time lag of pyocd buffers and windows pipeline technology.It is hoped that it is a correct and accurate timestamp precise to the millisecond level.
I try the following command:
pyocd rtt -t STM32H750VBTx -a 0x2407fcf0 | powershell -Command "$input | ForEach-Object { "[$(Get-Date -Format 'yyMMdd HH:mm:ss.fff')] $_" }"
In my test, the timestamp given by the above command was incorrect. I'm not sure if it's due to the caching mechanism of pyocd itself or the non-caching mechanism of windows Pipeline technology?
The time interval of the heartbeat packets(+keep_alive) output by this command line is less than 500 milliseconds, while my actual heartbeat interval is one minute.
Test data：
[260509 17:28:49.927] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:28:49.927] +keep_alive
[260509 17:29:50.375] Rcv_en=6
[260509 17:29:50.376] rcvT[7|A5]=8
[260509 17:29:50.376] A5,FA,00,81,0D,00,4A,FB,
[260509 17:29:50.377]
[260509 17:29:50.377] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:29:50.378] +keep_alive
[260509 17:30:50.840] Rcv_en=6
[260509 17:30:50.841] rcvT[7|A5]=8
[260509 17:30:50.842] A5,FA,00,81,0D,00,4A,FB,
[260509 17:30:50.842]
[260509 17:30:50.843] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:30:50.843] +keep_alive
[260509 17:31:51.294] Rcv_en=6
[260509 17:31:51.296] rcvT[7|A5]=8
[260509 17:31:51.297] A5,FA,00,81,0D,00,4A,FB,
[260509 17:31:51.298]
[260509 17:31:51.300] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:31:51.302] +keep_alive
[260509 17:32:51.750] Rcv_en=6
[260509 17:32:51.751] rcvT[7|A5]=8
[260509 17:32:51.752] A5,FA,00,81,0D,00,4A,FB,
[260509 17:32:51.753]
[260509 17:32:51.754] ---Rcv[7]=a5 fa 00 81 0d 00 4a fb
[260509 17:32:51.755] +keep_alive
Thanks!