- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nice idea, having improved and flexible NIOS cores with additional
peripherals. But what happens to the design flow? (1) The use of legacy sdk is not acceptable while looking for new features and improvements. This seems to be a not well supported workaround that will die soon. (2) Now the system libary will be build wihtin the NIOS IDE, resulting in long compilation times and specially each new build checks the existing lib for update. To reduce the turn-around time I'm now using the NIOS 2 SDK shell for the make command and the download command to achieve adequate turn-around cycles. (3) The application must be downloaded via JTAG - fast enough and o.k for lab use and development. What about downloads in the field or the fab? A JTAG connection and the IDE installtion is required on each computer (with NIOS1 and Germs, a serial terminal was enough). (4) In general a JTAG interface is not available at component level (external interface). How to download/upgrade SW without opening the box? Seems serial application interfaces like UART and Ethernet are no longer supported and you have to write your own bootloader. Have I missed anything? Any feedback welcome!Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
've just uploaded an assembly version of GERMS to the "Post your own tested IP" section of the forum.
This version of GERMS uses Altera HAL and fits in a 1 KByte memory. It works best with the upcoming Nios II 6.0 release (coming out very soon) but can be made to work with older releases. We use this version of GERMS at Altera for internal testing of the CPU. Feel free to use it with the understanding that it is not supported by Altera.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page