PSoC™ 5, 3 & 1 Forum Discussions

Hallo,

I wish my micro (CY8C29x66) to stay in a sleeping state for a very short while (i.e. 2ms) is this possible?

What's the side effect of staying in this state i.e. running devices such as UARTs, I2C or ADC, DAC how do they behave ?

If I have an user interrupt routine defined for the UART RX event will this 'wake-up' my micro from the sleeping state?

Best regards,

  Michele Santucci

The demo application has been tested on the following evaluation kits:

    
• CY8CKIT-001 PSoC® Development Kit
    
• utilising the CY8CKIT- 010 PSoC® CY8C55 Family Processor Module Kit
   

The PSoC5 demo includes a schematic design with several peripherals to demonstrate their integration with the RTOS. The included peripherals are the UART, LCD Character Display and two different types of timer implementations.

The demo uses:

    
• The FreeRTOS GCC and Keil Cortex-M3 ports.
    
• The PSoC Creator 1.0 beta 5 with its included GNU ARM Toolchain.
    
• Or the PSoC Creator configured to use the Keil MDK or RVDS ARM Toolchains.
   

I'm using the USBUART component from app note EP60246 but the question might also be valid for other USB interfaces.

Everything works fine until the USB cable to the PC is unplugged. Now USBUART_bGetConfiguration() still reports a non-zero value. If I replug the PC and try to write to it USBUART_Write() fails to return.

How can I detect the unplug and reconnect and reinitialize my USBUART component when possible?

Thanks

Hello,

I purchased a DVK 001 when it was just recently released. At the time, it had the PSoC 1 module and an ES2 PSoC 3 module. On the DVK website, it says that we can get updated silicon.

How and when can we do this? Will I be able to get the PSoC 5 module in addition?

DiodeDan 

Hello

I have currently migrated my project from a PSoC 3 to 5 (CY8CKIT-014). My analog design uses an Analog Mux Sequencer in differential mode with 6 dual inputs from GPIO. The Mux is connected directly to a differential DelSig ADC, 16-bit @ 1000 sps in multi-sample mode. Conversion results are stored in an array, and in the ADC's interrupt there is a logic to stop conversion, change mux channel and start conversion again.

In the PSoC 3 this design was working perfeclty. But when I switched to the PSoC 5 I started to get weird results from the ADC. Some input channels are converted by ADC, but output values have significant offset, and seem to be attenuaded. Other channels (mainly evenly numbered) return always the same value, regardless of voltage applied to GPIO. Furthermore this output value seems to change with PSoC reset.

I tried to use both Analog Mux and Analog Sequencer Mux, with no luck. When I connect pins directly to the ADC, conversion works properly. Using the Analog Mux in Single mode also works. So, at the moment, I ended up with two seperate muxes to drive both inputs of the ADC. It works, but my analog routing now looks like a spaghetti.

I am using PSoC Creator 1.0 Production (7727). 

I can post more details if necessary.

Does anybody else had similar issues with those muxes? Or mabye there is somebody who has working project with muxes in differential mode? I would be grateful for any iformation.

Regards

Tom

Dear PSOC Developer,

I'm newer use for PSOC programming. I want to use PSOC send AT command by UART module and connect with 3 wire Tx,Rx,GND. In 3 wire is need use flow control by software must to use XON/XOFF right? And this is my need.

1. Send command "AT+COPS?"+Enter button to UART.

2. When UART send it successful to GSM Module. GSM Module will send data back such as "Operator name".

3. I will bring it to show on my LCD display. (Methode for show on LCD Display it's ok, but in communication with GSM module it's not ok.)

I try to find source code sample for it but i cannot found it. If somepeople know how to write code for it. Please help me.

Thank you for your help.

Birdy. 🙂

amarin@ThaiModernArt.co.th

 Hi, I've just purchased and received my CY8CKIT-001 devkit, and all seems to be OK... except for the Miniprog 3 programmer.

Specifically, the programmer shipped with the kit has an unusual mini-a type USB connector, but the only USB cable supplied is a standard A-to-MiniB cable that only fits the dev board's USB port!

There's no physical way I can 'plug the Miniprog 3 into your computer's USB port' unless I have a hammer. 🙂

This seems such a stupid oversight that I'm sure I must be overlooking something basic - but without a real BOM in the kit (the referred BOM entry in the User's Guide and release notes simply says 'Miniprog-3 programmer and cables', not what sort of cables), I can't be sure if this is normal or an oops.

If I'm not going quietly mad, is there a way to get the additional (correct) USB cable for the MP3 from Cypress? I don't want to get involved in an RMA if I can possibly avoid it (not with a brand-new otherwise working dev kit!!), so an alternative would be to identify anything special about the USB connector and any cable used so I can purchase one locally. I'll be going shopping today to do just that - but because this is Australia, finding special USB connectors is quite difficult, if not impossible, without importing directly.

I'd also like to raise this as a potential issue with other new developers getting the same kits. I'm unsure if this is a single shot issue or if it's systemic. FWIW, my kit's serial number starts with 1041DG.

Thanks for any enlightenment on what is truly a frustrating issue!

Cheers,

PCPete