Flash Utility trouble with TiniARMDK

[mckenney]

I've got my TiniARMDK, and have been through the (Forth) LED
test, but I'm having trouble using the Philips Flash Utility to
load the C demo program. The symptom is "Cannot communicate
with test board!" (I'm beginning to think this is the program's
only error message). I get this from "Upload to flash", "Compare
Flash", and "Read Device ID". The Utility seems to switch itself
to 115K, but the symptom persists even if I force the line speed
to 9600 or 19.2K.

Hyperterm has no trouble talking to the board. The Boot jumper
(J1) appears to be working -- at least removing/replacing it has
a visible effect on the communication as seen by HyperTerm. I've
been resetting alternately with the button and the power switch.

Is there something obvious I should be checking? Is there some
way to figure out exactly what the Flash utility is seeing/objecting
to, or to type at the ARM-side boot loader?

I'm running WinXPH. The Flash Utility is V2.1.0.

[mckenney]

A bit more on this: The boot loader's ABR seems to be wrong, but
consistently so. Flipping through a collection of "standard" line
rates (using BrayTerm), the string "Synchronized\r\n" comes out
within 1/16th (1 bit varies in 16) of "0x91ac8eb4,b5ab6fa1,51fc".
This isn't even the correct length (10 vs 14), so it looks more like
a clock skew than a bit-error or parity or something. But it's
(nearly) the same string whatever speed I choose, so the ABR is
evidently doing its work, but tripping over something.

I assume the crystal is OK, since otherwise Forth wouldn't have
been able to get its line rate correct. (The ABR is supposed to
be independent of clock speed, but the clock does have to be
>= 10 MHz.)

I'm hoping this sounds familiar to someone here. To judge from
Google, I'm the only person in the world who's ever had trouble
with this.

[PS: BOOT is of course J11, not J1, when I have my glasses on.]

[mckenney]

So I poked it at 38400 (which I thought I checked) and it got
"Synchronized". Then I tried at 19.2K and 9600 (which I was sure
had failed repeatedly before) and they similarly succeeded. So I
forced the Flash Utility to 38400 and it works great.

[Cue Emily Latella: "Never mind."]

[nmitech]

Flash Utility synchronized at 38400 :confused:
I can only got it to work at 9600 on my XP/Win9x/2000. I wish we have more info on Philips flash utility program. Good to know, and thanks for the info!!!

[nhbeachgoer]

As I understand the LPC210X manual, the maximum baud
rate for a 10MHZ clock is 38400. I have downloaded
forth and ran verify. No errors at 38400 under XP pro.

[nmitech]

nhbeachgoer is right. It does work great on my XP at 9600/19200/38400. Previously i just used the default configuration, 9600. Thanks for the info.