[SOLVED] PCD Sanity Check w/BYTE sized CONST strings/values

[bkamen]

Hey there,

I'm using a verified LCD driver to talk with my Explorer 16.

the LCD.c was a carry over from all the CCS usual stuff.

And it's worked in the past.

When I compile the module into my stuff now, I have LCD init problems which I've whittled down to the LCD Init String which is normally posed as:

BYTE const LCD_INIT_STRING [] = {0x38, 0x0C, 0x01, 0x06};

I get the right number of bytes (4) written to the display (byte wide port on PORTE) but the bytes are wrong.

They come out 0x38, 0x00, 0x01, 0x00

I know there's compiler changes all the time. I even tried

#DEVICE CONST=

with the ROM and ROMI to see how MPLAB sees the output different.

When MPLAB's WATCH can see LCD_INIT_STRING, it has the wrong content (it's a printf to a UART!!) vs the right content on my scope but MPLAB lists the const as "out of bounds"

I'm using PCD 4.103 w/PIC24FJ128GA010.

The LCD works fine, I loaded up old working code that verifies its operation.

Thanks,

-Ben

EDIT: I looked at prog ROM and the spot that CCS sticks the string reads:

$0157E8 0C0038
$0157EA 060001

Which if I'm reading this right, is getting packed wrong.

_________________
Dazed and confused? I don't think so. Just "plain lost" will do. :D

[PCM programmer]

I don't have that compiler, but if you want a work-around, try removing
the 'const'. Let it be a RAM array.
It sounds like a possible bug and it should be investigated, but if
you were in a hurry to test the program...

[bkamen]

[bkamen]

This has been resolved with the latest version (4.104).

FAST!
_________________
Dazed and confused? I don't think so. Just "plain lost" will do. :D