Accessing JTAG_UART from Matlab

As a first point, I want to add a comment about the jtag_atlantic problems addressed in the initial post. I'm not working with Matlab dll interfaces, but I guess the problem is caused by the nature of jtag_atantic being a C++ dll with decorated names. See below a listing of the exported names.

LIBRARY     JTAG_ATLANTIC.DLL
EXPORTS
    ?jtagatlantic_cable_warning@@YAHPAUJTAGATLANTIC@@@Z
    ?jtagatlantic_close@@YAXPAUJTAGATLANTIC@@@Z
    ?jtagatlantic_flush@@YAHPAUJTAGATLANTIC@@@Z
    ?jtagatlantic_get_error@@YA?AW4JATL_ERROR@@PAPBD@Z
    ?jtagatlantic_get_info@@YAXPAUJTAGATLANTIC@@PAPBDPAH2@Z
    ?jtagatlantic_open@@YAPAUJTAGATLANTIC@@PBDHH0@Z
    ?jtagatlantic_read@@YAHPAUJTAGATLANTIC@@PADI@Z
    ?jtagatlantic_wait_open@@YAHPAUJTAGATLANTIC@@@Z
    ?jtagatlantic_write@@YAHPAUJTAGATLANTIC@@PBDI@Z

This makes is difficult to import the dll with a compiler that doesn't use exactly the same (Microsoft VC) name mangling. At least you need to be familiar with the import library generation procedure.

--- Quote Start ---

My 2c on why they do not implement a Virtual COM Port; the JTAG port is too limited.

--- Quote End ---

The JTAG port is surely limited. I can't follow however the "polling" point as a serious argument against JTAG UART usability. Altera JTAG is polling the UART usually with 6 MBPS. So what? A FTDI chip is polled through USB with 12 MBPS. O.K., there's a kind of bottleneck in the JTAG protocol itself and VJTAG on top of it.

Choosing a suitable communication method is a matter of data throughput, possibly intended utilization of existing VJTAG IP (e.g. Source&Probe, In-System Memory Editor, JTAG UART) and applications enviroment. According to my experience, the VJTAG tools are well suited for various calibration and test purposes. My ultimate product improvement suggestion is still a fully documented sld_hapi interface.

Regards,

Frank