Sory. You were right this was jtag problem that occured after reseting C::B and not the jtag server. But this happened after C::B crashed once.
This is the correct debug log output:
>>>>>>cb_gdb:
> target jtag jtag://10.237.2.35:9999
load
set $pc=0x100
Remote ba debugging using jtag://10.237.2.35:9999
>>>>>>cb_gdb:
> directory /home/domenv/hello-uart/
Loading section .vectors, size 0x124 lma 0x0
Loading section .text, size 0x35c lma 0x2000
Loading section .data, size 0x4 lma 0x235c
Loading section .rodata, size 0x14 lma 0x2360
Start address 0x2000, load size 1176
Transfer rate: 7840 bits/sec, 294 bytes/write.
>>>>>>cb_gdb:>>>>>>cb_gdb:>>>>>>cb_gdb:
> delete breakpoints
>>>>>>cb_gdb:
> break "/home/domenv/hello-uart/hello.c:97"
Breakpoint 1 at 0x22c4: file hello.c, line 97.
>>>>>>cb_gdb:
> break "/home/domenv/hello-uart/hello.c:93"
Breakpoint 2 at 0x2290: file hello.c, line 93.
>>>>>>cb_gdb:
> break "/home/domenv/hello-uart/hello.c:90"
Breakpoint 3 at 0x226c: file hello.c, line 90.
>>>>>>cb_gdb:
> info locals
No symbol table info available.
>>>>>>cb_gdb:
> info args
No symbol table info available.
>>>>>>cb_gdb:
> info frame
Stack level 1, frame at 0xfffb9c:
PC = 0xf000149c; saved PC 0xf000149c
called by frame at 0xfffb9c, caller of frame at 0xfffb9c
Arglist at 0xfffb9c, args:
Locals at 0xfffb9c, Previous frame's sp is 0xfffb9c
>>>>>>cb_gdb:
> disassemble
No function contains program counter for selected frame.
>>>>>>cb_gdb:
And after this I push continue button again and get:
> start
Breakpoint 4 at 0x2264: file hello.c, line 89.
And after this the only option available on debugger is stop debugging and if I push that button C::B crashes.