Hi,
When I tried to debug some C-code(compiled using or32-elf-gcc) on OR1200 through advanced Jtag bridge, it is not printing the printf strings. But the code execution is going forward and it reaches the end of the program. When I used scanf, it just halts and not taking any inputs.But it takes all other GDB commands and executes. Basically the debug setup is running very slowly(executable loading,response for GDB commands).The same code works fine on simulator with printf and scanf. Did any body try this when working on advanced jtag bridge.

Thanks,
A.Vamsi

You still have to use a serial cable+console to communicate with the system. Leon3 has the ability to pipe the serial console through the debug port, but, as far as I know, orpsocv2 does not.

The Advanced Debug System is also able to tunnel data through the JTAG cable. Its interface is equal to the uart16550. Only the address of the debug interface on the interconnect has to be used instead.

However, I doubt that the uClib/newlib implementations are mapped to that. The configuration would have to be remapped to it. I also don't know if you're using adv_jtag_bridge. Adv_jtag_bridge opens a telnet port for the IO data. If openocd also does that, I don't know.

Regards,
Raul

Hi Firefalcon.
That is correct. It's routing the prints to UART only, not to debug tap. When I made the working uart available in the tool chain board.S file, now it is printing the printf strings on UART console.

Thank you,
A.Vamsi