Something's fishy about the clock

[smcameron]

On the simulator, the moonpatrol badge app relies on rtc_get_ms_since_boot() for timing the player, seems to work.

On the badge hardware, in moonpatrol, the time stays at zero.

On the badge hardware, rtc_get_ms_since_boot() relies on get_absolute_time(), on the simulator it relies on timespec_get().

get_absolute_time() seems to be from the pico sdk.

That's all I know about the problem so far.

[smcameron]

• 3c46f393686a8a835daf88992d742bbc61dc4180 Add clock to qc app

Added a clock to the qc app, and the clock appears to work on the hardware badge. Must be a bug in the moonpatrol app.

[smcameron]

Hmm, putting printf's in moonpatrol, I see via USB serial that the time being computed correctly in the game, just not displayed correctly.

the_time = 65829 player.start_time = 32403 elapsed_time_ms = 54125 ms = 125 sec = 54 secs = 54 minute = 0 the_time = 65863 player.start_time = 32403 elapsed_time_ms = 54159 ms = 159 sec = 54 secs = 54 minute = 0

[smcameron]

Fixed by:

• 3d464a0f61f8c118c1be50a072d700146fb2ac2a moonpatrol: fix issue that time was not displayed correctly

Always use inttypes.h PRIu64 instead of %lu or %llu directly.