Re: Run Time Error

It's been awhile since I've seen that error, but as I recall it can come up as part of your software crashing.  The processor ends up executing random data until it hits an RST 38 opcode.

If you compile to target, but don't run your program (leave the debugger at the first statement in main()), does it happen?

If you compile a simple sample down to the target, do you get that error?

I think that after downloading, the module executes the BIOS, including all #GLOBAL_INIT blocks, and then enters main().

Is this an RCM3000 that you've done lots of development with (like a large number of compile/debug sessions)?  I think I had an RCM2200 stop working after years of development with it, and I assumed I had exceeded some flash read/write rating.  Or maybe I just gave it a static shock one day...

-Tom


On Oct 26, 2016, at 3:03 PM, seecwriter-/[email protected] [rabbit-semi] wrote:

> I tried running the DC v9.62 debugger on an RCM3000 module with a program that has been running for years. DC loads the firmware and when it's done I get the following error message before it closes:
> 
> 
> 
> Run Time Error: An RST 38 occurred, but the RST 38 vector is uninitialized. Address 00:e5cf
> 
> 
> 
> I've never seen that error before. Anyone know what it means or at least how to solve it?
>