PSoC™ 5, 3 & 1 Forum Discussions

Hi,

My usecase requires PSoC controller as both I2C Master and I2C Slave and switch between those two seamlessly without reprogramming. 

I2C Write from PSoC to EP - PSoC should be master here. Immediately after, EP should be able to control clock & become master and doI2C Write from EP to PSoC. What should be my design like in this case ? Do I need two separate I2C components - one for Master (I2C_1) and one for Slave(I2C_2) ? In that case, which I2C line will my EP have access to so will that work  ? Or a single I2C component can be configured to be both I2C Master and Slave and switch between those two modes based on who sends START condition & controls the clock ? I'm new to embedded programming so any help and explanation would be really helpful. Thanks in Advance.

I have a project based on the USB_FS example that has a HID descriptor that describes an input and a feature report.  This is a HID compliant custom device.

There is support to send the input reports using EP1+, using USBFS_LoadInEP, but not to send the feature report, which should be sent on EP0.  I did some searches on this that yielded results from 5 years or more back saying there is no way to do this, but it is being worked on.

So, what is the current state?  Is there a way to do this?  This seems like a fairly common usage of HID, so I'm surprised if it is not implemented.

I'm implementing a device that works with a pre-existing application that performs a set HID feature report to initiate an operation (allocate a resource id) and then a get HID feature report to retrieve the status and handle.  I need some guidance on the best way to implement get/set feature reports on the PSoC5LP.  I've read through the various application notes on implementing a USB HID device (AN57473, AN58726, AN82072 etc) but I haven't found much guidance on set/get HID feature reports.  From web searches I found references to the USBFS_FindReport_Callback function and have tried experimenting with it but haven't found a good guide on the best practices.

I've implemented HID feature get reports in the FindReport callback function without difficulty.  But for set reports - I see the reportType and reportId values are available in the FindReport callback, but the data for the report descriptor itself isn't populated in the USBFS_DEVICEx_CONFIGURATIONx_INTERFACEx_ALTERNATEx_HID_FEATURE_BUF_IDx buffers yet.  I found that the USBFS code doesn't fill out those buffers until after the FindReport callback returns.  The USBFS3.2 document says that the "main" application should monitor the completion status block to determine if the value in the buffers is valid or not before using it.

I added a flag in the FindReport callback to tell the main loop that a set feature report was seen.  The main loop polls that flag and checks the status completion block to see if the report is valid before acting upon it.  The issue is that the main loop does a lot of other work and that the get feature request for the status from the host can often come before the main loop gets to the point when it can check the flag and status control block to even process the initial set feature report.

I've experimented and found that I can implement a USBFS_EP_0_ISR_ExitCallback function and the USBFS_DEVICEx_CONFIGURATIONx_INTERFACEx_ALTERNATEx_HID_FEATURE_BUF_IDx buffers and status control blocks are set by that point and I can process the set feature request before the following get status request is encountered.

Is this a good solution to my problem, or are there better ways of implementing this?  Are there any good resources or guidance on implementing get/set HID feature reports for the PSoC series?

Hi,

I'm using a CY8CKIT-059 in combination with TeraTerm. One thing I can observe when downloading a new binary is that the KitProg UART gets a bunch of garbage and confuses TeraTerm, which needs to disconnect and connect again.

Interestingly, other tools behave different:

YAT: gets just a few characters including escape sequences
HTerm: same as YAT
PuTTY: can't see any garbage

Currently it looks like the effect pops up mostly if the application sends UART messages after reset by itself (e.g. without receiving a message first and then send an answer), but I've to verify that. I assume that when KitProg is resetting the device within a character transmission, the application might interpret it as some escape sequences or something like that. I also can see the effect at a much lower rate and much less garbage if the application doesn't send anything at startup, so even transmitting nothing is not the (full) solution.

Disconnecting and reconnecting is not a big issue, it's simply annoying if you've to do it everytime a binary is downloaded. Since also YAT and HTerm show at least 'some effect', I want to suggest that the KitProg firmware disables the UART while downloading a binary.

Regards