lm4flash hangs w/slow target SysClock

[Illusion65]

I've been using lm4flash to develop on my TM4C123GLX for six months or so. No problem until yesterday. I was progressively slowing down the CPU clock to test some PWM code that's not behaving. It doesn't make sense to me that this could be the cause, but it's the only thing I can think of that has changed.

The currently flashed code calls ROM_SysCtlClockSet(SYSCTL_SYSDIV_64 | SYSCTL_USE_OSC | SYSCTL_OSC_INT4); => System Clock at 62.5kHz
This seems about right, as my program is still running and outputting UART data that correlates with that clock speed.

I've recompiled lm4flash with the "#define DEBUG 1" line active, so I have a debug stream I could send (looks like a series of memory queries, a FlashErase, then hangs on the "FlashWrite" command (sending 537 bytes). I'm trying to load a small, known good .bin file (blinky.bin - 804bytes).

EDIT: I should also say that I left it overnight (not really thinking it would take that long) & also borrowed a friend's Win7 machine, loaded TI's LM Flash & ICDI drivers, but it could not find the target. I've not tried it before, so have no idea if it's a Win7 config issue or the device. But I'm sure something happened to my Linux setup (with no host computer changes).

[Illusion65]

My problem was related to the slow clock speed. I'm not sure what the Debug Port Unlock on TI's LM Flash tool does (something while board is powered up w/Reset button held), but that's what was needed to clear it. I'd be happy to help create a Linux tool to do this, using my board to test.

This issue can be closed.

Cheers,
Doug