Hi,

Quadrature Decoder function SetCounter() does not accept negative values (positive values are fine).

Example:

            QuadDec_SetCounter(-1); //can't set counter to a negative  value
            sprintf(strMsg1,"counter_val=%d \r\n", QuadDec_GetCounter() );
            SW_Tx_UART_PutString(strMsg1);
           

reading counter value in the above example returns -32767.

What I want is to limit counter values to some bounds, e.g. -100...+100. 

Regards,

odissey1

QuadDec_v2_30 (16bit)

A suggested addition to component, an output that is the clock used

to generate the waveform, and an equivalent for wc1/wc2 for the

start of the waveform.

Regards, Dana.

In the API description the following appears -

cystatus Em_EEPROM_Write (const uint8 srcBuf[], const uint8 eepromPtr[], uint16/uint32 byteCount)

This indicates the source buffer must be in code memory, which would not be generally useful.

In fact if the srcBuf[] is declared as a RAM location, not as const, the module works fine. So

this appears to be a datasheet error.

I have not checked the other datasheets, probably typed with same error.

Note this is also compounded by GCC after 2.5 (I gather) requiring the _attribute modifier be used

for placing stuff in code memory/FLASH. Which would make the const uint8 eepromPtr[] also typed wrong ?

Even though typed that way it does work. The open source compiler curse in action ?

Regards, Dana.

a number of times there was a problem:
I'm creating a project for CY8C5868AXI-LP035 - project works without errors.
Then I do: Project-> Device Selector ... CY8C3866AXI-040
after compilation:
Build error: unprintable character 0xEF skipped    main.c    line1
Build error: unprintable character 0xBB skipped    main.c    line1
Build error: unprintable character 0xBF skipped    main.c    line1

I had to create main.txt, copy the text from main.c and rename .txt to main.c
Why???

Hi,

I have upgraded to PSoC Creator 3.0 SP1 and have set about clearing up warnings.

I'm using an ISR to do millisecond timing. The prototype is CY_ISR_PROTO(MyInterrupt) ;

The function is CY_ISR(MyInterrupt) { ... }. There is red circle in the margin that displays the message "expected function body after function declarator". I've tried several things and have gotten the error to go away but it breaks my USBUART. It must have something to do with the CyGlobal interrupt because the ISR itself stops working.

The program works with the error message but I would, as a matter of course, like to resolve the error.

Nick

When installing PSOC creator 3.0_SP1 It goes OK until I'm asked to agree to the terms of service.  A few minutes later I get a window that says "PSOC Creator Installer has stopped working" and it terminates.  I got the registry cleaner from support, that did nothing.  I'm running Windows 7 Home premium on an Intel Core I-5-2320 with 8 GB of ram.  I have seen some development systems that can't handle multiple processors, but there's usually an option to lock them to one CPU.

PSoCCreatorSetup_3.0_SP1.exe is the file name as downloaded?  Could that extra dot in the 3.0 be making it barf?

If I have a pin connected to a schematic symbol (say a SPI Master block, for example), can I force the pin to a given state (high, low, tri-state) through software alone, or do I have to add a control register and mux to the schematic to do this?

My use case is a SPI Master talking to an external component, and the component has some very specific setup requirements that are not SPI. I'd like to wiggle the SPI MOSI pin and then "give the pin back" to the SPI module for normal SPI communications once my external component has been initialized.

I took a look through the pin datasheet and the resultant code generated, but I didn't see a way to do this. Adding a MUX and control register seems to be an awfully "heavy" way to do this.