On Sat, 4 Oct 2008, ?yvind Harboe wrote:

> I'm not too familiar with that code or the problem w/PLL/clocks that
> you are seing,
> but I modified it to wait 1000ms rather than try 100 times...
>
> Seems a tad more robust to me.
>

I try clarify my problem again. I have two almost identical programs 
runing from flash. First work with the internal clock:

SysCtlClockSet(SYSCTL_SYSDIV_1 | SYSCTL_USE_OSC | SYSCTL_OSC_MAIN |
                SYSCTL_XTAL_6MHZ);

second work with the full speed PLL:

SysCtlClockSet(SYSCTL_SYSDIV_4 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN |
               SYSCTL_XTAL_6MHZ);

SysCtlClockSet function come from Luminary Micro driver library.

In the first case I have no problem with openocd. In second, openocd 
report "Timeout waiting for ACK..." error. The only way to tackle a 
problem is pushing a board reset button, then connect to the openocd 
server via telnet, and give the following commands: init and halt. After 
that I am able to erase the flash and put a new program.

So, if I have the program in the uC flash that change the PLL frequency to
50MHz, I am not able to use the openocd because of the mentioned error.
I haven't checked the case if PLL clock is different form 50MHz.

What is more, if I debug a program in RAM and that program change the PLL
frequency in the similar way, the openocd work fine.

I think that, JTAG work faster at 50MHz clock than at 6MHz clock so time 
that you modified should be shorter not longer.


-- 
Best regards,
Mariusz
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to