ContributionsMost RecentMost LikesSolutionsUse 3rd Party Terminal for JTAG-UART IP Hello! I have a MAX10 with a NIOS2 core. I tested both JTAG-UART (USB Blaster from Terasic) and UART IP (a common RS232 to USB adapter) an they work great. I can communicate between NIOS and PC with both of them. I wrote my own code (3rd Party) and it works with UART-IP and RS232-USB adapter. There is a COM Port in Windows Device Manager: from there is easy. But I used the JTAG-UART + USB Blaster only in Eclipse. How can I access the JTAG-UART + USB Blaster in a 3rd Party Terminal/Console? I want to access the UART over JTAG-UART IP in my own software. Any ideas? Regards, Paul Re: Nios2 - Cannot write the OnChip-Flash - Timeout error Hello, I solved the problem. It was the configuration of the BSP. I was booting from FLASH but using the FLASH as program memory (I hope that terms I'm using are correct - I'm not a uController specialist). After I changed the settings to copy the code from FLASH to RAM and boot it from RAM, I was able to delete and to write the FLASH again. Regards, Paul Nios2 - Cannot write the OnChip-Flash - Timeout error Hi there, I have the following configuration: - MAX 10 FPGA (Compact) - NIOS2/e with OnChip Flash Intel Firstly, I set the reset vector memory an "on chip memory RAM" for the NIOS2/e and program it over Eclipse: - I tried to write the flash alt_onchip_flash_write_block (&onchip_flash_0, 0, parameters[0], parameters[1], 1); and after several seconds got the error: 0x8c from the function. This looks like the "#define ETIMEDOUT 116 /* Connection timed out */" in the alt_onchip_flash_poll_for_status_to_go_idle. The functions returs -ETIMEDOUT (minus) that is why 0x8c - After this error I tried to read the flash: alt_onchip_flash_read(&onchip_flash_0, parameters[0], out, parameters[1]); Successful - Try again to write it: alt_onchip_flash_write_block (&onchip_flash_0, 0, parameters[0], parameters[1], 1); Successful. I needed always a Read command before a Write. Not ideal but no a big deal. Ok, now I want to program the NIOS2 in the non-volatile memory. Because I have a MAX10 DC (Compact version) I have to load the NIOS2 firmware in flash. I changed the reset vector memory to "on chip flash" and I set the correct values in the BSP. Booting is successful. All the functions (NIOS2 and FPGA) are working except write flash. alt_onchip_flash_write_block (&onchip_flash_0, 0, parameters[0], parameters+1, 1); --> gives me all the time a 0x8C error "#define ETIMEDOUT 116 /* Connection timed out */" the trick with read first and than write is not working anymore. I cannot write to flash anymore.... Any idea what am I doing wrong? Suggestions? Thank you, Paul Re: IP-NIOS, Licensing, Distributors in Europe 30 mins after my post from above I got the email with the license from Intel. Maybe it was a coincidence. If it was not a coincidence: thank you guys. IP-NIOS, Licensing, Distributors in Europe Hi! I ordered an IP-NIOS license. Here is my experience with it: - there is absolutely no Intel office in Europe where I can call or write and to discuss with a "human person" and ask her/him questions about the product - there is nothing like the old "Altera Europe" office in Europe anymore - I sent a Intel Premium Support request and it was denied. We are a small company but still a company.... great! - I searched for Distributors in Europe for INTEL-FPGA products and related products and I got only: 1. digikey - FPGA, CPLD but no Licenses 2. arrow - FPGA, CPLD, they offer licenses but IP-NIOS is not in stock and cannot be ordered 3. mouser - FPGA, CPLD and licenses. I order it 2 weeks ago. Order status after 2 weeks for a downloadable license: "pending"!! I'm spamming mouser with emails and by phone requesting at least a delivery date and all I get is: "we get no information back from Intel" And I need as soon as possible the IP-NIOS license for a demo unit which is going to be sent to a potential customer. Further in this design we will need a new package/license from Intel which is way more expensive than IP-NIOS and less documented. We are completely in the dark about it: technical and purchasing. What is your experience with Intel support and purchasing from them? Do you have some advice for me? Regards, Paul