New Contributor
New ContributorHello, so:
there is nothing in my entire ashling riscfree window that refers to NiosV, not in new project wizard, not in import wizard, nowhere else. I will anyway double check on my server if the description explained in the manual you have just linked is realistic for our usecase.
Occasional ContributorHi Cloudscraper ,
there is nothing in my entire ashling riscfree window that refers to NiosV
I see, you are correct.
I reviewed the RiscFree IDE v23.1, and the following are my observations.
not in new project wizard
Most Nios V projects are imported BSP & APP projects. Currently, there is no equivalent "File > New > Nios II Application and BSP from Template" in RiscFree IDE.
not in import wizard
In RiscFree IDE v23.1, the import wizard is based on "File > New > Project > C/C++ > C++ Project". So, there is no "Nios V" text throughout the whole flow. But there will be a dedicated import feature called Import Nios V CMake Project starting from RiscFree IDE v24.1.
nowhere else
Debugging side of things --- Nios V is using the RISC-V Hardware Debugging run/debug configuration option. So, another no "Nios V" text workflow.
I will anyway double check on my server if the description explained in the manual you have just linked is realistic for our usecase.
Thanks for your help. I hope that my hypothesis is valid, and you will be unblocked soon.
If possible, please share your expected first impression. We and our partner, Ashling are interested to hear more to make the tool more intuitive.
Regards,
Liang Yu
New ContributorHello and thank you again for your detailed answer,
I have now realized that Ashling 23.1 is a bit more rudimental than more recent versions, but thanks to your answer and some research among the documents, we were able to import our application and our BSP and reference them together, thus we were able to complete a project build inside the Ashling RiscFree v23.1 environment.
The standing issue now lies in the Debugging component of Ashling RiscFree.
We have, in fact, tried two different approaches:
we get the error "selected debug probe is not available for debug session"
Both approaches have been failing us, that's why I am attaching a couple screenshots above of error messages we have been receiving.
This is what the jtagconfig launched from our NiosV-Shell is reporting us:
I have started wondering about user access/ user permissions in regards to these new errors popping up: have there been any previous reports of access limitations caused by lackluster user privileges or user permissions?
