- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
using Creator 1.0 you can use USB with the built in IMO clock source without any problems (experiences with the cyc85588-LTI114 ES1, ...AXI-60 ES1 and PSoC 3 Production devices).
Why was this option cancelled in 2.0? I didn't noticed any problems. Could this be optional reactivated in future updates?
Bye
Franz
Solved! Go to Solution.
- Labels:
-
PSoC 5LP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Charlie,
The load capacitance recommendation is just that, a recommendation. Errors in load capacitance will have a small impact on oscillating frequency.
Thanks,
Max
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
PSOC5 IMO is not as good as it supposed to be, I think you need crystal for PSOC5 with USB. The PSOc3 should be OK without xtal I think.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it mandatory to have an external crystal as the clock source for PSoC5 device?
It depends on the application in which PSoC5 is used. The PSoC5 device family has a tolerance of 5% on the IMO. If your PSoC5 application has strict timing requirements it is necessary to have an accurate clock source. Especially, for projects that have communication components such as UART or USB, it is mandatory to use external MHz crystal with PSoC5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Listed below are the recommended crystal and the capacitors for PSoC5.
CY8CKIT-050:
Y3 | CRYSTAL 24.000MHZ 20PF SMD | ECS Inc | ECS-240-20-5PX-TR |
C30,C31 | CAP, CER, 22 pF, 50V, 5%, COG, 0603, SMD | Panasonic - ECG | ECJ-0EC1H220J |
CY8CKIT-010:
Y2 | CRYSTAL, 24 MHz, 30 ppm, HC49, SMD | ECS Inc | ECS-240-12-5PX-TR |
C26,C27 | CAP, CER, 12 pF, 50V, 5%, COG, 0603, SMD | Murata Electronics North America | GRM1885C1H120JA01D |
In case of CY8CKIT-010 ( PSoC CY8C55 Processor Module) the crystal and the corresponding capacitors(C26 and C27) should be mounted as shown in the picture below:
In case of CY8CKIT-050, the crystal and the corresponding capacitors(C30 and C31) should be mounted as shown in the picture below:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In order to use the external MHz crystal in your PSoC Creator project, the following setting needs to be done in the Design Wide resource file of the project:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it really a 12pF capacitor for the -010? The image shows 22pF capacitors, and the datasheet says the same (and AN54439 too)..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why not leave using IMO for USB as an option? Maybe showing warnings or notices? As said I did not had any failures with Creator 1.0.
I think wih external crystal you will lose flexibility for some applications.
Bye
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can I use a 12MHz crystal as well? (I just have one laying around, but not a 24MHz one). I would neet to change the configuration, but I don't know whether USB / UART uses the IMO directly or the master clock...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As long as the PLL is using a XTAL as the source, it should be OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any crystal in the range 4 – 25 MHz can be used. The crystal input can be locked to any frequency in the range 24 – 67 MHz using the PLL; same can be used as Master Clock for the system. The tolerance on the PLL is dependent on the tolerance of the input clock; that is the crystal. Chosse a crystal which is accurate enough for your frequency.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It was a cold shower after installing 2.0 and an external XTAL is required to compile my old project. I'm really sorry to read this. We are just starting production with a NO-XTAL-design that we have iterated several revisions during long time. We haven't found any problems or seen any warnings about the USB-communication. And nothing is mentioned about that in new features for Creator2.0 nor on the Cypress site either, only now in this thread. Really bad. I'll say Cypress is lucky to have saved my 1.0-files as backup before installaition of 2.0. We will have to stick to Creator 1.0 until next revision of our PCB. Not happy 😞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This link http://www.cypress.com/?rID=55948 has documentation on migrating designs between different silicon, software versions. It can be accessed from Creator from, Help -> Documentation -> Migration Guide.
Regards,
-Vivek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The need for using an external crystal was documented during Creator 2.0 release in this Knowledge base article on Cypress website.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'am still asking why not let the option to choose IMO as USB clock source as this is possible in Creator 1.0?
Franz
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anybody tried to down-grade to an older version of an USB-component? Is that possible?? Will it work (without x-tal)???
Bob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Even if you downgrade the version of the USBFS component, as long as you use PSoC Creator 2.0, you will have to use an external crystal for PSoC5.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For the CY8CKIT-010, and following AN54439 equation 2:
CL1 = CL2 = 2 * CL - (CP - CB)
Let CL = 20pF (from ECS crystal specification)
Let CP = 5pF (from PSoC® 5: CY8C55 Family Datasheet page 61)
Let CB ~= 1pF (from microstrip estimate)
...how can one arrive at the 22pF value for the pi-network capacitors?
Why was a different crystal chosen for the CY8CKIT-010?
Resolving the conflict between the table and the illustration posted in the forum post for the CY8CKIT-010 by assuming 12pF is the correct value for C26 and C27, and matches the ECS specification of a 12pF for CL, again, how can one arrive at the 12pF value for the pi-network capacitors using equation2?
How can this information be applied to the design of a Cypress customer's PCB for the PSoC5?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Charlie,
The load capacitance recommendation is just that, a recommendation. Errors in load capacitance will have a small impact on oscillating frequency.
Thanks,
Max
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think that a little sum-up would help here...
The root of the problem is that the IMO is not accurate on PSoC 5 as we would like. As a result USB, when clocked from the IMO, would fail certification. It might "work" but would not be compliant. We added a design check for that siutation in the 2.0 release.
The easy fix is to add a crystal to the design and set up XTAL as the USB clock. The design check directs you to do just that. But, we forgot another viable solution; using an external clock signal. It should be possible to put a good clock onto a GPIO and use that as the USB clock. The design is attached, showing how to name the signal and use it in the Clock editor. Sadly, the design check we put in erroneously prohibits using XTAL as the IMO source and using that for USB. We'll fix that in the next release.
But, there's more. In the last post pavloven has cunningly shown a way around the bogus error. Instead of using IMO as the USB clock source, he runs the IMO through the PLL and then to USB. This dodges the error condition and lets you run USB without a crystal (you still cannot run it off the internal IMO clock though). Nice job, pavloven, we'd not thought of that one! Of course, this does put a bit of a restriction on what you run the PLL at but that may not be a problem in your designs.
-- Mark.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pavleon Great job !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To answer my own question about the capacitors: it depends 🙂 One needs to look up the data sheet for the crystal to be used, and then calculate the capacitors from that. When using the formula Cload=((C1*C2)/(C1+C2))/Cstray, and assume that Cstray is 10pF (5pF for the PCB, and 5pF for the PSoC5 inputs, according to the data sheet), the 12pF and 22pF values are not that far off.
I soldered my crystals on the -050 yesterday. The one I used was specified with a load capacitance of 20pF, and I soldered 22pF capacitors (the formula above gives 20pF). Soldering the 0603 parts was a real pain, and I needed multiple tries to get it right 😞
My testcase was to divide the crystal frequency by 256, and using this clock to drive a 16bit PWM block. This gives a nice 1.4 second period, and worked right from the start.
After that, I tried the USBFS-HID example project, which naturally didn't work... The reason in the end was that the code specifies a 3.3 volt supply, but the project was somehow set to 5 volts (and the board too). After changing the code to set a 5 volt supply, everything worked fine.
Since I was using a 12MHz crystal instead of the recommended 24MHz one, I did use pavlovens trick from above: use the crystal as source for the PLL, and create the needed 48MHz frequency from that. Then one can use the PLL to drive the USB clock. Hte only disadvantage of this is that the PLL then cannot be used to create another frequency, which might be needed in some cases.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content