Richard,
I'm not seeing timeouts, but what I've found is that starting the
debugger is flawed here in KDS.
Do you have it plugged into a direct USB port or through a hub? I've
seen hub issues before with other tools.
For some reason it doesn't remember which debug configuration you used
last, so if you just hit F11 or the Debug button, this will fail 2nd
time in. You have to specifically choose the configuration, or just
relaunch your last one.
I've also had the gdb backend server die on Linux for no reason, yet the
debugger does not seem to sense this, so a complete bailout is needed to
actually kill the process and restart it.
There is alot of other strange behaviour. If I go to the memory browser,
enter 0x400, I see the flash fine. If I put in 0x3c0 to see the
bootloader config area, I get nothing but ???? I have no reason why it
won't inspect this....
I installed KDS as a user with almost root permission, however it won't
do anything unless I start it as root. No amount of fiddling with
permissions will fix this. Again, I'm sure it's some eclipse or java
crap buried somewhere that wants to write a file it can't.. Why does no
one seem to know what's wrong here..who is maintaining this product?
I suspect most all of these issues are eclipse related. I think the PE
backend is mostly good and have found no real issues with the compiler
or linker.
All in all I've wasted far too much time on the tools not working right
and not being able to trust them. A real productivity drain...
The Kboot v2.0 has more bugs and mistakes than I can list so far....
Sorry for the rant, but this is really eating into my time...
Ken