Hi,
I observed the following behaviour using Quartus 17.0.
When i start to add my own custom IP into the qsys, then the time_limited sof file is generated and the behaviour of my eclipse program is not the same anymore.
1. Where can I find the evaluation timeout?
2. Why is there a different sof(time limited) file generated once I add my own IP?
3. There seems to be a functional difference between a time_limited_sof and the .sof.
I do the following. I receive over the UART IP core some data values and loop them back in the NIOS-II using a small c-program.
This is working fine when I do not use my own IP core in the design, as soon as I include my own IP core the time_limited_sof is generated, but from this point of time the loopback on the UART is not working anymore.
In both cases I use the same c-program, sure I have different system.h files due to the fact that one my IP core is in the design, once it not included in the design. My c-program does not access my IP core instance, so the software
is independent from the usage of my IP core.
Any idea where I could look for understanding this behaviour ?
Thanks in advance!
I observed the following behaviour using Quartus 17.0.
When i start to add my own custom IP into the qsys, then the time_limited sof file is generated and the behaviour of my eclipse program is not the same anymore.
1. Where can I find the evaluation timeout?
2. Why is there a different sof(time limited) file generated once I add my own IP?
3. There seems to be a functional difference between a time_limited_sof and the .sof.
I do the following. I receive over the UART IP core some data values and loop them back in the NIOS-II using a small c-program.
This is working fine when I do not use my own IP core in the design, as soon as I include my own IP core the time_limited_sof is generated, but from this point of time the loopback on the UART is not working anymore.
In both cases I use the same c-program, sure I have different system.h files due to the fact that one my IP core is in the design, once it not included in the design. My c-program does not access my IP core instance, so the software
is independent from the usage of my IP core.
Any idea where I could look for understanding this behaviour ?
Thanks in advance!