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.
Related Articles
7035 - Propel: Why Propel Timer/Counter IP register settings were reset when I start/stop the timer with driver API?
Description: This is due to a software bug in gp_timer.c where the gp_timer_config and gp_timer_stop API used reg_32b_write instead of read-modify-write reg_32b_modify. When write to control register, it overwrite the register value instead of ...7449 - Timer/Counter IP Core v1.3.0: Why Timer/Counter does not generate interrupt (IRQ)?
Description: Due to a known issue in Timer/Counter IP Core v1.3.0, user may observed that interrupt is not generated during counter timeout. Solution: To workaround this issue, please revert back to Timer/Counter IP Core v1.2.2. This is scheduled to ...7755 - RISC-V IP: Does the RISC-V Processor Support Vectored Mode Interrupts?
Description Only RISC-V RX balanced mode and advanced mode support vectored interrupt table. Other RISC-V variant does not support vector interrupt mode. Resolution For RX core, user may find the macro in riscv.h Change it to MTVEC_MODE_VECTORED and ...7501 - RISC-V CPU IP Core: How to achieve cache coherency with RISC-V CPU
RISC-V cacheable address is configurable in MC, and fixed in RX. The RISC-V core is implementing write through policy, both the cache and destination value will be updated when store operation happen. This imply that CPU store operation will write to ...7216 - What is the difference, in terms of circuitry and RTL, between the selected mode (Cycle/Time) for choosing the Timeout value of the Watchdog Timer IP?
The Cycle and Time mode uses the same circuit or RTL. The mode is just to give flexibility to the user to input the Timeout value (either through cycles or periods) through the IP GUI.