I'm not sure if this should be posted elsewhere but...

 Does anyone know of any quaternion libraries or functions geared towards microcontrollers like PSOC5?
It would be nice if Creator came with some extended math libraries for robotics or other 3D applications.

Can someone let me know how to change the font type and size for the code edit windows.

Cheers

Hi,

you can now find the production release on the Cypress website. No more Creator Beta releases.

http://www.cypress.com/?rID=39551

To check important information such as minimum system requirements, changes to previous releases and more, please read the Release Notes first:

http://www.cypress.com/?docID=23759

This is exciting!

Robert

 In military and medical applications, it is vital to know if the code you are running is what was written.  That is why the ECC idea is great.  I love that the processor takes care of this issue instead of me having to run a CRC on the Flash at run-time.  

I have written a simple piece of code that re-writes an instruction in flash after programming to force a fault.  For example, I set up a simple sum in normal code and then switch it to a subtraction afterwards.  When I turn on ECC mode, the ECC prevents the switch from occurring (great...ECC works!).  I haven't checked, but I imagine the subtract opcode is only 1-bit different from the add opcode.  The trouble is I can't figure out how to register the ISR code when a supposed ECC event occurs.  I have found allusions to this ability in the PSoC 5 datasheet and in several appnotes, but there are no examples or further information.  Does anyone have this working or have any suggestions?  My code is shown below.  It is a variation on what I found in an application note.  I have commented out my attempts at registering the ISR.  I tried a system-level interrupt (only available on the ARM) and a regular one.  

#include    
volatile uint8 a = 5; // don't let the compiler optimize this away
volatile uint8 b = 3; // don't let the compiler optimize this away
volatile uint8 sum; // don't let the compiler optimize this away

/* To find Row number by dividing the address by 256 */
#define ADDRESS_TO_ROW(A) (A / SIZEOF_FLASH_ROW)

/* To find address of next row */
#define ROW_INCREMENT SIZEOF_FLASH_ROW

/* Define PSoC 5 Flash Base */
#define FLASH_BASE CYDEV_FLASH_BASE

/* define the ECC interrupt code */
/*
CY_ISR(ECC_Fault_ISR)
{
LCD_ClearDisplay();
LCD_Position(0,0);
LCD_PrintString("PROG MEM FAULT");
}
*/
void main()
{
/* Array which contains value to be written to the Flash Row */
uint8 rowFinalData[SIZEOF_FLASH_ROW];

/* Temp Buffer for Flash line of code*/
uint8 rowBuffer[SIZEOF_FLASH_ROW SIZEOF_ECC_ROW];

/* Start and end locaton of the concerned data */
uint8 rowDataOffset;
uint16 rowDataEnd;

/* Row address for instruction in flash */
uint16 rowAddress1;

uint16 index1;

uint8 runTwice = 0;


// Various attempts at assigning the ECC ISR to the vector table
//CyIntSetSysVector(1, ECC_Fault_ISR);
//CyIntSetVector(1, ECC_Fault_ISR);
//CyIntSetPriority(1, 3);
//CyIntEnable(1);

/* Start LCD */
LCD_Start();

/* To display demo started */
LCD_Position(0,0);
LCD_PrintString("Flash Mem CRC TST");

LCD_Position(1,0);
LCD_PrintNumber(a);
LCD_PrintString(" ");
LCD_PrintNumber(b);
LCD_PrintString("=");

//CYGlobalIntEnable; /* enable global interrupts */

/* create a label for the difference operation. In GCC, this will also be
the address of the operation. This code is never called after the initial
declaration. The instruction will be copied into the SUM flash location after
to simulate a program memory fault. */
DIFOPERATION:
sum = a - b;

while( runTwice != 2 )
{

/* create a label for the difference operation. In GCC, this will also be
the address of the operation. This instruction will get clobbered in flash
as this code executes. I do not recommend re-writing flash too much as this
will weaken the holding-power of the flash. If you really want to test the
program memory fault code every time, then you will need a seperate label
to copy the code back to it's original state. */
SUMOPERATION:
sum = a b;

LCD_Position(1,0);
LCD_PrintNumber(a);
LCD_PrintString(" ");
LCD_PrintNumber(b);
LCD_PrintString("=");

LCD_PrintNumber(sum);
LCD_PrintString(" a:"); // show address for verification
LCD_PrintHexUint16( &&SUMOPERATION );
LCD_PrintString(" ");
LCD_PrintNumber(runTwice);

CyDelay(2000); // wait 2 seconds

if( runTwice == 0 )
{
/* Get the address where the sine lookup table is stored */
rowAddress1 = (uint16) &&SUMOPERATION;

/* Calculate the row number from the address, which is the remainder of address/256 (max row size) */
rowDataOffset = rowAddress1%SIZEOF_FLASH_ROW;

/* Calculate the starting address of row */
rowAddress1 = rowAddress1 - rowDataOffset;

for(index1 = 0; index1 < SIZEOF_FLASH_ROW; index1 )
{
if ( index1 == rowDataOffset )
{
rowFinalData[index1] = (uint16) (void*)(&&DIFOPERATION); // replace sum operation with difference operation
}
else
{
/* Save the other elements of the flash row in the same position as they were */
rowFinalData[index1] = CY_GET_XTND_REG8((const void *)(FLASH_BASE rowAddress1 index1));
}
}

/* Must get temperature and set a temp buffer first. My understanding is different power is used
to write to the flash depending upon its temperature. */
if(!CySetTemp() && !CySetFlashEEBuffer(rowBuffer))
{
/* Erase and Program the row. */
CyWriteRowData(0, ADDRESS_TO_ROW(rowAddress1), rowFinalData);
}
runTwice = 1;
}
else
{
runTwice = 2;
}
}
while( 1 )
{
/* Never exit */
}
} // end of main()

Hi,

I am working with PSOC5 CY8CKIT-014. At the moment my exmerimental codes are very small <5% of code space. Nevertheless Creator software downloads 1024 blocks. I do not think this is really needed? I there a possibility to download only the needed blocks for faster download?

Thanks!

Christof

 Hi, basically i'm designing a capsense button and slider by using CY8C20424. i need to generate a PWM to drive a buzzer, does the psoc designer 5.1 have the PWM generator module? or any other way i can do?

thanks in advance.

Hi all,

I tried to open my old project in PSoC Creator 1.0 Beta 2.0 (1.0.0.4248).

But it shows

Error: prj.M0052: Unable to open the project "Project": (There is an error in XML document (1659, 3).). Address the error and try again.

how to rectify that? I think it may be due to PSoC Creator version on which project created is different from the Beta 2.0 , but how to check in which version project is created??

or some other reason is there for this error?

Kindly help.

rgds,

yaj
 

 I updated to new software release and now the project I've been working on for over a month does not work!

I tried building after updating components and when that didn't work re-copied all files from archive and tried building it without updating components.

When I updated the components even the UART didn't work reliably.

Any help would be greatly appreciated.

Dan

 I am getting the following error when trying to build a PSOC3 project.

I am looking for the best way to create private data accessor methods in the generated APIs.

Here is an example of what I'm trying to do.

I have an ISR which is connected to digital input pin. The interrupt is called, for example, "pin_isr"
The ISR gets called on the falling edge of the digital input. So far so good.

Now, the ISR fills in an array of uint16's which are declared in the 'pin_isr.c' file. The declaration is in the section of the .c file bewteen #START pin_isr_intc and `#END`

In that same section i have the accessor method so that I can access the data, via the accessor, from inside main.c

Now here is the problem:

In order to let main.c know about the accessor method I have declared it ('prototyped' it) inside pin_isr.h - but, that file does not have any persistent areas in it, so the prototype gets lost whenever the apis get re-generated (for example it I make any changes to the schematic).

Is there anyway to create a 'persistent' area in the .h file, in a similar way to the #START and #END in the .c files?

Or, is there a better way to create accessor methods for data in the generated api files?

Thanks in advance,

Kenny.