New Contributor
Regular Contributorhi zjyoof
For the error you are facing it points to the NiosV is not being brough up.
Could you check with the command "jtagconfg -n". You would see the NiosV under the list of device.
If you do not see the NiosV there are some steps to check:
-The System connection in the Platform Designer? Are the Instruction and data of the Nios connected properly?
-Check if the reset of the NiosV is connected properly. Check if it is constantly being held in reset.
New ContributorHi,
Thank you for the detailed guidance. I ran the command as suggested and have attached a screenshot of the output for your reference. Could you please take a look and advise on the next steps based on what you see? I appreciate your help.
Regular ContributorHi
From the screenshot you shared we could see the NiosV is being brought up.
You could not start downloading you application file (.elf) to the device using the command "niosv-download <path to elf>"
Once completed you could see the Nios V logs that are output to the jtag uart using the the command "juart-terminal"
You could refer to the ED on running the HelloWorld in the link :
For BSP setting I would suggest you to take a look at the boot method guide in the link:
https://docs.altera.com/r/docs/726952/25.3/nios-v-embedded-processor-design-handbook/introduction-to-nios-v-processor-booting-methods
New ContributorHi,
niosv-download download prompts the same error
After the Riscfree download error occurred, we also tried other methods to start the niosv platform, that is, the 5.5.2. Niosv Processor application execute-In-Place from UFM described in the manual. This can solve the situation where the elf is larger than the available RAM, and when the elf changes, you only need to regenerate the pof.
However, after strictly following the hardware and software design procedures in 5.5.2.1 and 5.5.2.2, the Niosv serial output still has problems. Using Signal Tap to capture the niosv data_manager bus, we found that wvalid and rvalid were never pulled high.
