03-18-2017 11:39 AM
Hello,Does exist a straightforward approach on the synchronization of the two parts of a NIOS II project - hw & sw. Here is my case:
- For my de1 soc terasic (cyclon v) board I've developed in qsys a project that features nios ii, some peripherals and sdram memory
- After adding top-level wrapper for qsys system in quartus, I downloaded hw part in my board.
- Then I've created sw part (generated sbp based on .sopcinfo + application)
- After compiling sw application I've tried to run it in the board (right-click application --> "Run As" --> "NIOS II hardware")
- Unfortunately this attempt was unsuccessful (please, see my previous post - "problem with downloading of a nios ii program")
- Having no clear idea how to workaround such issue, I've decided to approach this project to an another, working project
- The major difference between 2 projects is the memory type - in "working" project - on-chip memory, in "nonworking"- sdram.
- So, I replaced in "nonworking" project sdram with onchip memory.
- After compiling and downloading the hw part, I returned to sw development ... and didn't find any option (!!!), allowing to "refresh" bsp in order to take into account the new .sopcinfo.
- Attempts to compile the application resulted in error messages, containing allusions on sdram, that is already removed from project !
- After some exploration I've discovered that in bsp editor window one can remove the link to non-existing sdram and replace it with onchip-memory.
- Then I've tried to build application with modified bsp (as I believed)
- The result of this building you can see from the screenshot below
- Moreover, I checked the content of the system.h file - there are still the definitions, related to sdram ...
03-19-2017 10:23 AM
I was a bit imprecise with the previous post - in point 12 I meant "Generate BSP".So, according to my explorations, after modifying the qsys (i.e. updating .socpinfo file), it's impossible to take into account these modifications in bsp (at least until now I didn't find how to do this). Well ... probably, creating of a new package (from modified .socpinfo) will settle a case ... Not at all !!! After creating of a new bsp, the new problem raised - how to attach this new bsp to the existing application ? What a curious tool this nios ii sbt for eclipse !
03-25-2017 01:21 PM
--- Quote Start --- After creating of a new BSP, the new problem raised - how to attach this new BSP to the existing application ? --- Quote End --- Well ... the another BSP can be attached to application this way:
- right-click on the application
- then select properties, then under "nios ii application properties"
- then go to the "bsp project location"
- then specify a new location for bsp