PSoC™ 5, 3 & 1 Forum Discussions

The interrupt on capture box is disabled for the fixed function timer.

I assume this function is not available on fixed function timers but the documentation says differently. Timer_v2_70.pdf page 2 shows:

Am I doing something wrong or is this just wishful thinking in the documentation?

 Hi,

I trying to get a SPISlave to tranfer data to  an array via DMA.

It should be 2 byte per burst, with transfer count =2.Every burst need new request

Unfortunately only the first data is transfer , the second data is left in SPIS Rxbuffer.

The SPIMaster seem to be working .Tested with an ocsi, and the the RxBuffer not empty interupt seem to be working

Anyone have any idea what going on?

Attached is the Workspace bundle

Hadi

Hi,

I am considering the design of an interface device (board) that essentially will make multiple USB devices appear as one USB device. 

Just a bit of back ground.  I am an amateur radio operator and use a radio called the Peaberry V2.  I own multiple of these radios.  Currently each radio attaches to a PC via USB.  Each radio appears as a separate device on the PC.  Each radio has a operates on a unique band of frequencies.  Currently the PC host application needs to be stopped, reconfigured and restarted to switch between radios.  The idea is to use a PSoC 3 and configure multiple USBFS components (one for each radio) and then select a given USBFS component and route the data to a common USBFS component that is attached to the PC.  

The interface device will do more than USB interfacing but I would like to know what folks think about this aspect first. 

I need to stay with the PSoC 3 as this is the only chip that is available in a 48 pin configuration.  The board will be offered as kit and the 48 pin version is the only chip that can be reasonably be soldered into place by a kit builder

Thanks for taking a look,

Ron

I'm new to PSoC microcontrollers, and just started using the PSoC 5LP. 

I'm wondering how to interpret the timer interval values captured from a timer block, for instance with Timer_ReadCapture().

Is the value based on the clock signal given to Timer Block, or is it scaled to seconds, microseconds, etc?

- thank you

Hi,

I probably missed this somewhere, but is there a way to be notified by email when new topics are posted?  I can't see to find an option for this.

Thanks,

Ron Patton

I saw that these wonderful certified drivers take care of the few issues that were found with the Windows standard USBerial drivers.
The drivers though have two inf files, and there is no direct information on how to use them. I am thus posting these steps:

1. There are two inf files associated with the device: CypressUsbAndBus.inf and CypressSerial.inf. The device when comes up the first time, attach it to CypressUsbAndBus.inf file. This file has the PID_VID details of the device. These drivers are signed for VID_PID: 04b4_0003/0005/0008. During development to use these drivers with a Windows OS, you need to use these PID_VID only, as you cannot use an unsigned driver (When you change the inf file the signature is lost). So in your device, please program the PSoC with PID_VID 0003/0004/0005_04b4. The example project has a VID_PID of 04b4_F232. Do take care that you cannot use these PID_VID combination for your end product without Cypress's approval.

2. After the device is bound to CypressUsbAndBus.inf file, the device is recognized as Cypress USB to SERIAL adapter in the device manager. A New Hardware Found pop-up window appears again. Use the second inf file CypressSerial.inf file. The device will enumerate as a Cypress Serial device, with an associated COM port number alloted by the drivers and OS.

Remember to use the right inf file. Windows 7 , amd64 - 64 bit system, x86 is 32 bit system. Rest is trivial. 🙂

Cheers.!!!

 Hey guys i am interfacing arduino board with capsense MBR3.My task invovles as follows can anybody just  give me an idea as to how to go about:

if proximity detect--->disable proximity sensor and associated led on kit---->do some operation--->again enable proximity sensor

 I need to make a I2C slave without subadressing using the CY8C21534. The data to read and write is always 2 byte so with every read and write, these both bytes are transferred.

In fact the slave should act as a PCA8575 I2C port expander.

What I2C module can I best use for this? EZI2C always seems to expect a subadress.

Is there already an example for this?

Thanks.