Doesn't compile about freertos-riscv HOT 5 CLOSED

As far as I can tell, it appears to be a mechanism introduced on top of the original port here for detecting where certain peripherals are mapped. Unfortunately, its use is not documented. See my related issue over at #5.

Keep in mind that this FreeRTOS port was written to conform for RISC-V privileged specification 1.9. You'll want to build using older tools to use this port without modification. A few things have changed with the latest version of the architecture and tools. See 1.10 Privilege Specification. I have a working port to 1.10 and plan to issue a merge request soon, though I suspect this page is dead.

from freertos-riscv.

Yes, @sherrbc1 is right. The configstring was a way to get the address of timers, IO and other devices in priv spec 1.9. This has changed with version 1.10.
This repo has been inactive since I got busy with academic work. I intend to continue maintaining and updating this port starting from the second week of January. If you already have a working 1.10 port, please send a merge request.

from freertos-riscv.

@sherrbc1 I am working on freeRTOS port to RISCV. I am facing issue because of change in specifications. Can I have access to your patch to test it?

Thanks
Shankar

from freertos-riscv.

See it here. The changes were minor.

#7

from freertos-riscv.

Thanks, it works. Appreciate your help.

from freertos-riscv.