Internal error on command:"G2"

[LifeOfBrian]

Either in addition or related to the above error your have the following as well:

MCU 'toolboard' shutdown: Timer too close

See here:

Timer too close

Timer too close Background A “Timer too close” error occurs when the MCU is asked to schedule an action at a time that is already in the past. This typically results from delayed communication between the host and the MCU - for instance, if the host was busy or the message was blocked en route. Important: Klipper can identify what command was too late, but cannot determine why the delay occurred. The root cause is often external - such as USB congestion from a webcam or high system …

A side note from @Sineos to the original topic:

General note: Log lines like stepcompress o=4 i=0 c=17 a=0: Invalid sequence often are a consequence of errors / events that happened before. This means they are rather a symptom but not the root cause.

What is connected to your Pi Zero 2?