6784 - Propel / Timer/Counter IP version 1.2.0 or earlier: Why is CPU hanging in debug when the number of timers set on the Timer/Counter IP GUI is 1?

6784 - Propel / Timer/Counter IP version 1.2.0 or earlier: Why is CPU hanging in debug when the number of timers set on the Timer/Counter IP GUI is 1?

Description: This error will only be observed when performing Open OCD debugging. A hang will be observed while doing a step-through debugging.
This is caused a bug on the python script that generates the IP RTL. There is a NUM_OF_TIMERS parameter on the IP RTL that is based on the number of timers set on the IP GUI. The NUM_OF_TIMERS is an 8-bit parameter (as 8 is the maximum number of timers) with each bit assigned to a specific Timer instance.



However, when the no. of timers is set to 1, the NUM_OF_TIMERS parameter should be 1 but then it is set to 0 on the IP RTL.