- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I encounter this strange behaviour: I try to disable file generation of speciifc HAL driver file.
Yet, although I change it to "-" with "disable generation" and saves the settings
I verified that in xml there are addition lines:
<IgnoredFileInfo>
<componentName>altera_generic_quad_spi_controller</componentName>
<fileName>altera_generic_quad_spi_controller.c</fileName>
</IgnoredFileInfo>
Yet, on clicking generate bsp, it regenerate the file, and also remove the xml lines from setting, and in gui it also appears as enabled generation.
Any idea why it ignores the setting ?
I'm using quartus 15.1.
Thanks,
ran
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
May I know if this is related to Nios II software development or something else?
If yes, which version are you using?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, NIOS II /f
IP: altera_nios2_qsys Version: 15.1
Thanks for any suggestion,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there any idea ?
We really struggle with it for a long time now.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
This is a known bug that the option to disable BSP file generation in the Nios II BSP Editor not working properly in older version of Quartus.
The workaround is to manually edit, or script updates to the settings.bsp to re-disable the file generation (or to remove the file).
Have you try using a newer version of Quartus (17 and up)?
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This bug is still present in Quartus 20.1
Are there plans to actually fix this? It's been years at this point. The only thing that's happened in the mean time is that rshal2's fix no longer seems to work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We need to use version 15.1 by customer request.
Anyway, I did eventually solved the issue, by changing the driver tab from "default" to its number (I think 13.1 was the only other option except for default),
After doing this change, it all worked as should be.
Thanks,
Ranran
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page