LPC MicrocontrollersのトピックRe: Red State SCT not compatible with LPC_Open examples. Error: EVENT member not found.

Red State SCT not compatible with LPC_Open examples. Error: EVENT member not found.

lpcware — Wed, 15 Jun 2016 20:04:42 GMT

Content originally posted in LPCWare by larsen on Sun Aug 23 13:21:13 MST 2015
I get the error:
LPC_SCT->EVENT[0].STATE = 0;
----> 'LPC_SCT_T' has no member named 'EVENT

LPC_SCT->DMA0REQUEST = 0x00000000;
-----> 'LPC_SCT_T' has no member named 'DMA0REQUEST

What I do is very simple to reproduce: With LPCXpresso 7.9.0, LPCOpen v 2.15 for LPC824 board i generate an SCT state machine with red state into the periph_gpio's src folder. I just use the default state machine, no edit, then generate code. Recompile.

The above error pops up in the sct_fsm.c file.

Am I using the tool inappropriately? How to correct this?

Re: Red State SCT not compatible with LPC_Open examples. Error: EVENT member not found.

lpcware — Wed, 15 Jun 2016 20:04:43 GMT

Content originally posted in LPCWare by lpcxpresso-support on Mon Aug 24 18:45:40 MST 2015
Hi Larsen,

Sorry that you running into difficulties with the Red State SCT tool.

It seems that the tool was not updated to reflect changes in the LPCOpen 2.15 header files.

As a short-term fix you could change the generated code to match the new headers by replacing:
1) "LPC_SCT->EVENT" with "LPC_SCT->EV"
2) "LPC_SCT->DMA0REQUEST" with "LPC_SCT->DMAREQ0"
3) "LPC_SCT->DMA1REQUEST" with "LPC_SCT->DMAREQ1"

Note that this would need to be done each time that the code is regenerated.

The next release of LPCXpresso should contain a fix for this issue - which will allow you to select the version of the LPC Open library you are building against.

Thanks for finding and reporting this bug. Apologies for any frustration it caused.

Ciao,
LPCXpresso-Support

Re: Red State SCT not compatible with LPC_Open examples. Error: EVENT member not found.

lpcware — Wed, 15 Jun 2016 20:04:44 GMT

Content originally posted in LPCWare by larsen on Tue Aug 25 00:32:38 MST 2015
thanks this fix works fine. looking forward to next release.