FCONSTANT not recognized

[proto pro]

I have an IsoPod V2 SR with IsoMax V0.5 wich suddenly stopped recogizing FCONSTANT. I had a program installed in flash which used several FCONSTANT commands and it worked perfectly.
I made a minor change to emit the program name to MAXTERM when the Isopod is first powered up. After I SCRUBed it and flashed the new version, it hanged at FCONSTANT ?
I then SCRUBed and flashed the old version and had the same problem. I then scrubbed and tried to define an FCONSTANT interactivly with the same results.
ex.
1 S>F FCONSTANT FTEST <RETURN>
would echo back
FCONSTANT ?

Previously, I have jumpered pins 2&4 of J5, reset, and SCRUBed many times to load other versions while I developed this code, so , I know I'm SCRUBing correctly.
I measured voltages on the SR supply as
Vin = 14.2VDC
+5 = 4.89VDC
+3.3 = 3.25VDC
Any Ideas?

[RMDumse]

This is very curious, and not obvious. If the board were here, I'd try to reflash the kernel and see if the problem went away. But if that's not possible right away, then another question comes to mind.

First are there any other words missing?

Do a WORDS list and see if something goes wrong with the list before the FCONSTANT word. Make sure the FCONSTANT word appears in the list. Let us know.

[nmitech]

Your program may be set in HEX mode, so do not forget to change it back to DECIMAL mode. Sometimes we may overlook on a simple thing like this.

[proto pro]

O.K. I'v checked out your suggestions, I do have a DECIMAL statement just before my FCONSTANT statements. I listed WORDS, all the commands listed to the end and all looked O.K. with one exception, FCONSTANT listed, but the ending T was replaced with a solid triangle pointing to the right. Looks like somehow something got corrupted.

[nmitech]

proto pro,

Do you have any luck with the FCONSTANT word after a long cool down? This is a bizzard case, and we would really like to know more how you did this because Flash-memory words don't allow a write within the kernel address range. Was there any power or reset glitch while you were writing to Flash (with EEWORD)? or any attempt to overwrite certain addresses in the flash memory, etc...

You can send the unit back to NMI to reflash or purchase the JTAG cable and sign up for the License Agreement we will send you the IsoMax Srecord and JTAG loader to reflash or upgrade each time the new IsoMax version released.

Download the License Agreement form here,
http://www.newmicros.com/cgi-bin/store/order.cgi?form=prod_detail&part=IsoMax-DSP&id=3LFu7LdhXBwHHpOB6q8IkmveH7P4imUM

Jtag-cable-10P,
http://www.newmicros.com/cgi-bin/store/order.cgi?form=prod_detail&part=JTAG-Cable-10P&id=3LFu7LdhXBwHHpOB6q8IkmveH7P4imUM

[proto pro]

I have since noticed the power cord seems to have a bad connection, so in all liklyhood I had a power glitch durring download.
The JTag cable and licence sounds like a good idea because now I'm down for a couple of weeks, where if I had these, I could just reflash the kernal and be back up right away.
Thanks for your help,
Dave