Porting to Renesas RISC-V MCU - portasmHANDLE_INTERRUPT

[Pole (Riccardo Polelli)]

Hi everyone, I am working a porting on Renesas RISC-V MCU (R9A02G021). The problems I am encoutering are many, I’ll start by exposing one of them.

The problem is about portasmHANDLE_INTERRUPT. On the website (Using FreeRTOS on RISC-V Microcontrollers - FreeRTOS™) it is stated that it must be declared as an assembler macro. It is not clear to me what this routine should do and where shuold I look for it. If I am unable to find it, how should I implement it?
Also this is stated to be responsible for managing external interrupts. Are the MTIME interrupts considered external? I have a problem regarding the non increasing of the value of xTickCount, but probably that’s for another thread.

[aggarg (Gaurav Aggarwal)]

@Pole

The problem is about portasmHANDLE_INTERRUPT. On the website (Using FreeRTOS on RISC-V Microcontrollers - FreeRTOS™) it is stated that it must be declared as an assembler macro. It is not clear to me what this routine should do and where shuold I look for it. If I am unable to find it, how should I implement it?

Apologies for the inconvenience - we need to update our documentation but this macro is no longer needed.

@Pole

Are the MTIME interrupts considered external?

We handle MTIME in the port itself - FreeRTOS-Kernel/portable/GCC/RISC-V/portASM.S at main · FreeRTOS/FreeRTOS-Kernel · GitHub.

You can try to refer one of these demos -

• FreeRTOS/FreeRTOS/Demo/RISC-V_RV32_QEMU_VIRT_GCC at main · FreeRTOS/FreeRTOS · GitHub
• FreeRTOS/FreeRTOS/Demo/RISC-V_RV32_SiFive_HiFive1-RevB_IAR at main · FreeRTOS/FreeRTOS · GitHub