using the debugger with BYTE CONST ROM LUTs

[jventerprises]

i am using the following chunk of code..


byte const ARRAY[2] = {10, 20};
....
my_var = ARRAY[my_index];


i notice two things...

1. when you place the debuggers cursor over the ARRAY[my_index] when debugging, the array has the right length and structure, but the values are garbage. i can probably understand this since the array is just a compiler LUT.

2. if you try to step through the above assignment, the debugger hangs even thought the ROM looks correct. if you step over the section of code that contains the above assignment, all works fine.

has anybody had similar experiences? the ROM LUT seems to work fine, the values are returned correctly. I just wish i could step over the line..
_________________
Jon

[valemike]

Are you talking about the PCW environment? Or are you using the CCS compiler with Microchip's MPLAB IDE?

I've had experiences with the MPLAB IDE by Microchip where the debugger does not interpret CCS's floating point correctly, so what I do is just do a printf() to Hyperterminal.

Basically, I usually don't trust the MPLAB IDE debugger with floating point numbers. As for bytes, i haven't had a problem.

[jventerprises]

this is with the PCW environment... i find that the ccs environment is more reliable...
_________________
Jon