PSoC™ 5, 3 & 1 Forum Discussions
text.format{('custom.tabs.no.results')}
The schematic shows that the USB Micro-B receptacle shield should be connected to the board's GND by way of a 100K resistor and 0.01uF capacitor in parallel. All my copies have no solder in the receptacle mounting holes that would make this connection. Once I add solder myself the components test present.
It doesn't make much difference because 3 of the 4 USB cables I tested don't have a shield.
I'm trying to determine if the RC connection is best, or direct connection of the shield to GND is better. Both are recommended by skilled designers. I haven't seen anyone recommend open-circuit.
Show LessHi there!
I've got 2 old cy8ckit-001 boards and don't know their revision (A,B,C?).
Board is pdcr-9461 rev5 (text on label is 121R-46100)
I'm interesting is it compatible with last PSOC5 kits as CY8CKIT-010?
And maybe there are still exist a way to "update" a revision of my PSOC3 cy8ckit-009 ( to "release"-revision mcu) for free.
Show LessHello,
I was trying to teach myself how to use CapSense using the CY8CKIT-001 and can't even get the tuner helper to connect, I keep getting the error message shown in the subject line. I set up my pins as shown in http://www.cypress.com/file/46756/download, page 5 for the PSoC3 module, which I'm using at the moment. I note that this uses the MiniProg3 but looking at the PSoC3 module's schematic, the MiniProg3 connects to J5 TDO, TDI and TCK but the CapSense Tuner is set to use the MiniProg3 I2C link (my pins are set to P12[5:4] as indicated by the module's schematic).
The CapSense data sheet covering the Tuner GUI User Guide shows a very simple procedure for accessing CapSense data that I can't get to work. I've checked my parameters a number of times and they align between the settings shown in the CapSense Tuner configuration window and that shown for the PSoC components.
Any suggestions?
Show LessHi ,
I have just started with PsoC 5 and following Cypress document http://www.cypress.com/blog/psoc-insiders-blog/manchester-code however I do not know how to create dummy connectors as in referenced article. I ended up having pins which I need to connect otherwise I would get error about not connecting all visible ports.
Any hints welcome 🙂
Thanks
Rafal
Show LessHello,
I have the following piece of code which is working fine on the main thread
uint8 MOTOR_bufsize=3
uint8 xSpeedLSB = value & 0xff;
uint8 xSpeedMSB = value >> 8;
uint8 MOTOR_waarde[3] = {0x0, xSpeedLSB, xSpeedMSB};
//set MOTOR
I2C_MOTOR_MasterClearStatus(); /* Clear any previous status */
I2C_MOTOR_MasterWriteBuf(MOTOR_I2C_SLAVEADRES, MOTOR_waarde, MOTOR_bufsize, I2C_MOTOR_MODE_COMPLETE_XFER);
But as soon I put the same lines into a function, nothing happens when the function is called. The function is shown below;
void set_speed(axis, speed) {
if (axis == Xaxis) {
uint8 channel = 0x0;
}
uint8 bufsize=3;
uint8 SpeedLSB = speed & 0xff;
uint8 SpeedMSB = speed >> 8;
uint8 MOTOR_waarde[3] = {channel, SpeedLSB, SpeedMSB};
I2C_MOTOR_MasterClearStatus(); /* Clear any previous status */
I2C_MOTOR_MasterWriteBuf(MOTOR_I2C_SLAVEADRES, MOTOR_waarde, bufsize, I2C_MOTOR_MODE_COMPLETE_XFER);
}
the function is called by:
set_speed(Xaxis, value);
in which Xaxis is an integer (0) and value is an integer between 0 and 1023.
The function is initialized by:
void set_speed(int axis, int speed);
Can anybody help me on my way why my function does not work?
Show LessHello,
I am a fairly new user of the PSOC and have been working with the 049-42xx kit. The project I want to build consists of an external ADC sending data to the PSOC SPI master component and relaying that through the UART to the USB-serial bridge card edge connector into a PC. I put myself into a jam by already creating a PCB for the project with the dev board on top of the PCB.
I later realized I couldn't get the PSOC 4 UART to transmit data fast enough or store enough data in a buffer in SRAM (4kB) - and has no DMA channels to do these fast transfers. My current solution is to switch to a PSOC 5 which has 64kB of SRAM and DMA channels. However, since the pinout is different with a larger spacing between target board and KitProg, I am investigating suitable workarounds. A .png is attached showing a somewhat to scale comparison of the two kits with the spacing difference indicated by blue lines.
I am using MATLAB to collect the data on a PCB and am more comfortable interfacing with usb-serial communications compared to using a USBFS component.
I have had many ideas so far so bear with me (all involve some pins on the target board not being connected to the PCB):
1) Snap the KitProg off and place it above the target board horizontally overlapping to achieve proper pinout spacing. Though the pinout of the usb-serial bridge vs KitProg has the GND and VDD in different locations ( and I foolishly connected them to PCB)
2) Snap the KitProg off and replace with a USB-serial bridge from the 049-42xx kit connecting that to target board. Might not be feasible given the different interconnect traces e.g. SWDIO and SWDCLK vs RX and TX
3)Snap off KitProg and use it once in a while to program but use the USB micro connector for data output. However, I am unsure if I can use the USB UART component with the micro connector or only the USBFS component.
I was wondering if I could get some advice and thoughts on these options or any others that might be more feasible.
Sorry for the length of the post and thank you in advance for any help,
Scott
Show LessI am using 4 opamp for the design of filter and ADC
I want an reference voltage in PSoC to drive the external circuit and as well as ADC.
What are the possible ways to do it?
Can do it using MUX or PGA or any other way?
Regards,
Umama Shireen
Show LessHello Every Body,
I am using two dithering VDAC having same clocks. Now the problem is, one dithering VDAC is generating correct voltage but the other is not.
Please see pic attached.
Looking forward for your reply.
Regards
Awais
Show LessHello,
I am trying to do a filtering process on psoc5. I did lots of thing but with small issue I turn back the basic form of the project. I tried to solve problem myself but I couldn't understand the reason of the problem.
Here I am doing with ping pong dma and send datas to sd card with emfile. When I writing the datas to sdcard I am writing an array after that I am doing a shift operation (just for try to solve problem. I will use the results after.) Like this code.
if(TD_Num==DMA_FilterToAvgFilter_TD[1]){
FS_Write(pFile, (uint8*)filteredDataP0, (NO_OF_SAMPLES*2));
for(c=0;c<NO_OF_SAMPLES;c++){
filteredDataP0
}
But in graph (you can see in attachments) , I wouldn't think to see shift operation results. But there are.
Firstly, I thought about the clear the isr flag, but it seems clearly that clear isr isn't needed.
Do you have any idea about the this problem.
Regards
Burak
Show LessThere is a KB article that mentions that a bug is there in the USB component in Psoc Designer. The same bug was found in USBFS in creator as well. KB article: http://www.cypress.com/?id=4&rID=38107 I have added some more analysis on the problem from the PC side.
The problem is that when a few packets of size 64 bytes is sent; the data is received, but not shown by the Hyperterminal/ any Serial Port Application. But when we constantly send a lot of data over the Hyperterminal in 64 bytes size packets, we are able to see that data on the Hyperterminal. This happens because the application has a buffer where it keeps the data and waits for a smaller size packet/ zero length packet to indicate the finish of transfer. If the data transferred is more than the buffer size, the data is displayed. This is what happens when you send a lot of data continuously on the USBUART.
This buffer size was found to be 4K for Tera Term and Cool Term Applications.
If you send suppose 3K bytes of data (in 64 bytes packets), you will not see the data displayed. Now, if you send another 3K bytes of data (in 64 bytes packets) you will see the first 4K data on the display of the application and the rest 2K would be in the buffer. To confirm this, now send 2K bytes of data (in 64 bytes packets). You will see 4K bytes of data getting displayed, with the last 2K as what you last sent.
Cheers.!!!