--- Quote Start ---
Have set up SignalTap.
However, the jtag side of it seems unreliable, at least for me.
--- Quote End ---
Yeah, I've noticed a few annoying things too.
For example, if working with system-console, I need to make sure I close any JTAG connections before starting signal tap (the GUI), and then open a JTAG connection in system-console before starting signaltap acquire.
Once I figured out the sequence that works, then its been ok.
--- Quote Start ---
I'm on 64 bit Fedora 14
--- Quote End ---
I have been doing my development under WinXP and Win7. I have got Quartus installed under VirtualBox + Ubuntu and Centos 6.2. Though I haven't played much with signaltap, so I don't know if the same sequence is required.
--- Quote Start ---
Having Quartus (including jtagd and SignalTap) work out of the box on more Linux flavours would be nice.
--- Quote End ---
From Altera's perspective, I'm sure they're thinking "Having less flavors of Linux to choose from would be nice ... " :)
--- Quote Start ---
I also get 10 lines of warnings when the USB blaster stuff is loaded at boot time like this:
udevd[470]: BUS= will be removed in a future udev version, please use SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match a parent device, in /etc/udev/rules.d/51-usbblaster.rules:8
All in all, a great tool - shame about the jtagd problems.
--- Quote End ---
I haven't noticed those errors ... I'll have to keep an eye out for them.
Cheers,
Dave
Honored Contributor
