Unsupported Struct

[bkidney]

I am trying to debug a piece of code in MPLAB (using an ICE 2000) but in my watch list I am getting the message "Unsupported Struct" for sec[] array.


typedef struct
{
int16 end;
int16 cost;
} Sectioned;

typedef struct
{
Sectioned sec[5];
} SecCosts;


typedef struct
{
int16 cost;
} Unsectioned;



typedef union
{
Unsectioned usec;
SecCosts seced;
} Rate;

typedef struct
{
int16 base;
int16 tax;
BYTE type;
Rate rate;
INT32 check;
} CostTable;

Is this a limitation of the compiler, or have I done something wrong? (My compiler version is Version 3.181).

Thanks,
Brian

[ckielstra]

Which version of MPLAB are you using?
In the release notes for v6.50 I noted the following under the new features:
"Watch windows support pointers, structure members, enum symbol values."

[Max]

also I have problems with watch and to see structure with mplab 6.61:

typedef struct
{
bit enablea:1;
bit enableb:1;
bit enablec:1;
bit stop:1;
bit flagdelay:1;
bit run:1;
unsigned int16 delay;
unsigned int16 delay_t;
} my_struct;

my_struct in_out[MAX];
-----------------------------------------------------------
watch MPLAB 6.61:

address symbol name value

00B4 - in_out
[0] orted Struct
[1] orted Struct
[2] orted Struct
[3] orted Struct
------------------------------------------------------------

Help thanks

[ChrisW]

I'm also getting "Unsupported Struct" messages in the MPLAB Watch window (MPLAB 8.00, CCS 4.057).

Does anyone know a fix for this?

Many thanks,
Chris

[iigruntii]

Can someone on the CCS staff please confirm this as an issue? I have the same problem. Watch window says "Unsupported Struct" when I try to create a struct array. Is this a limitation or is it a bug?

Example code:
typedef struct {
UCHAR write;
UCHAR readBuff[4];
UCHAR readCounter;
UCHAR *readDest;
UCHAR device;
}SPIMSG;

static SPIMSG SpiQueue[8];

[ckielstra]

Three things:
1) You are reporting a problem in MPLAB, a Microchip product and not from CCS.
2) Always post the version numbers of your tools (CCS and MPLAB)! It might be a known problem.
3) Read the forum rules and the message on the right top of each page: