As written, Listing $4$ is considered a "blocking" function, i$.$e$.,$ it won't return until the delay as expired. However, Dr$.$ J would now like you to create a "non$-$blocking" hardware$-$assisted delay using the Core Timer and static variables as needed to implement the following behavior:

$($a$)$ The first time the routine is called, it sets an internal variable to to indicate that a delay is in progress, saves other information as well, and returns a $"1"$ to show a delay operation is in progress.

$($b$)$ Subsequent calls to the delay routine will check to determine if the delay has elapsed and if so$,$ return $"0".$ Otherwise, it returns a $"1".$

A sample application is below

main$()$

$\{$

non$\_$block$\_$delay$(100)$; $//$ Initial call

while$($non$\_$block$\_$delay$(100))$

$\{$

task$1$;

task$2$;

$\}//$ end while

$\}//$ end main

The above will cause task$1$ and task$2$ to be executed repeatedly for at least $100$ msec.