PSoC: Configurable Mixed-Signal Array with On-chip Controller

PSoC: Configurable Mixed-Signal Array with On-chip Controller
January 11, 2002 Changing the Embedded WorldTM PSoC: Configurable Mixed-Signal Array with On-chip Controller 1

Objectives Cypress overview
Introduce Cypress MicroSystems & PSoCTM System on Chip PSoC Designer Development Kit Demo with Software and Dev. Tool Support Applications The agenda for this training module is shown here. First we want to make sure everyone is on the same page with regard to the general information about the capabilities of the PSoC Microcontrollers and how we can harness those capabilities through PSoC Designer IDE software. The final step will be to demonstrate our creation on working hardware. It is this final step alone that will require the use of the PSoC In-circuit emulator (ICE) and the PSoC Pup demo board which is included as part of the development kit. All other aspects of this training module can be accomplished using only a computer and PSoC Designer IDE software (which is available from our web site at Let’s get started < Click Mouse or Spacebar>

Divisions CYPRESS MPD DCD TTD PCD CMS Memory Product Division Data
Communication Division TTD Timing Technology Division PCD Personal Communication Division CMS Cypress Micro- Systems Async SRAM Sync SRAM NoBL / QDR MoBL NVM Specialty Memory DP-RAM, FIFO Communication CPLD Ultra 37000 CPLD Quan. 38K CPLD Delta 39K HOTLink / PSI IP Solutions Software Tools FTG RF PLLs HS Clock Control Clock Distribution Spread Spectrum Low Speed USB Full Speed USB High Speed USB USB Hubs USB Dev. Tools USB Ref. Designs WirelessUSB Neuron PSoC Support Tools App. Notes

Cypress MicroSystems Strategy
Provide a Single Chip Programmable Solution for small electronic products Leveraging Cypress Semiconductors World leader position in USB – 80% world Market share in the respective market. The M8C Core in PSoC is used in the USB product Proven Technology – 185+ million M8 microcontrollers sold Here we see our strategy provide small chip for most electronic applications. No one know of Cypress history in industry We use USB group’s success to push our product.

Microcontroller Market
Current Embedded Marketplace: Each part covers small functionality Embedded Marketplace Families tend to cluster; second sourcing leads to overlaps Cypress Cypress Customers believe they need custom micros Current Embedded Marketplace: Tens of thousands of Part Numbers Over 20 Vendors; Over 15 Architectures Each part covers a small functionality Customers think they are in need of customs, CPLDs, ASICs, CPLDs, PGAs They need a different peripheral set Most designs have additional analog components adjacent to the MCU Cypress Strategy: Entering the market requires covering a large share of space Provide part numbers that each cover MORE functionality Section Time: 10 minutes Learning Objectives: Describe the corporate directive for PSoC Keypoints: Black circle represents the $5 billion marketplace of microcontrollers In the microspace, there are dozens of vendors and tens of thousands of part numbers Those each cover a little bit of functional space In each of those functional spaces, you may cover multiple markets One part might be in 5 or 6 markets The customer is always looking for the part that fits his exact function (i.e., need). They need a different peripheral set Most designs have additional analog components adjacent to the MCU Because the customer has a unique need, he/she believes that a custom solution is provided by an ASIC or CPLD Cypress Strategy is to provide one microcontroller that will solve multiple products and multiple projects Cypress Cypress Strategy: Provide part numbers that each cover MORE functionality (i.e., cover hundreds of competitive devices)

PSoC™ System on Chip Benefits
What has changed for you? The search for the perfect part is over PSoC reduces your system’s parts count PSoC adapts to changing Customer Requirements PSoC simplifies purchasing and inventories Better than a custom part No NRE No Waiting No Minimum quantities How are we going to change your life? Only for the better, because: Integration of more peripherals, especially analog, reduces your board’s part count. Extending peripherals through re-configuration makes a $2 MCU act like a $4 MCU (or much, much more). You can store one part to fit many configurations. No more reliance on “fixed peripheral” microcontrollers. As you upgrade and improve your products, you can tune, upscale, or downscale the processor often without even changing the chip. Or you can choose a compatible chip with a more appropriate pin count, but that has the same capabilities and resources. But mostly, you get to end the search for the perfect fit. You make it perfect. Custom without the cost, time and hassles of custom.

Security Sensor Application
Traditional Approach Competitive Solutions Op amp LP filter Op amp A/D Microcontroller D/A Sensor Digital Outputs This is a typical MCU system. What you are looking at is a carbon monoxide detector. It has an analog input chain, filtering and amplifying the signal before it goes to the A/D in the Microcontroller. The outputs are a driver for a sound generator and drivers for a couple of LEDs for battery test and an “on” indicator. For the microcontroller, a critical issue the ability to go into very low-power sleep modes to conserve battery life. LEDs

What They can do We can Do So Much More! PSoC Microcontrollers Sensor
Op amp LP filter Op amp A/D Microcontroller D/A Digital Outputs LEDs

Traditional CO Solution
Decrease System Costs Traditional CO Solution Cypress CO Solution 8-bit Micro $2.00 Crystal + Caps $0.57 Filters $0.30 Amps $0.20 Speaker Driver $0.15 LED Drivers $0.05 Circuit Board $1.20 Assembly $1.60 PSoC Micro. $2.00 Circuit Board $0.90 Assembly $1.40 System BOM = $6.07 PSoC BOM = $4.30

Parts Reduction Do you use these external components?
Op Amps and Comparators PWMs Filter components Analog drivers Transistors / Buffers External ADC High speed crystal Pseudo Random Sequence Generator These are external components that could be integrated with a PSoC design

Why Choose PSoC? Parts Reduction

What Functions Appear When They Appear How They Interconnect
PSoC = Programmable System-on-Chip Create your customized chip User Defines : What Functions Appear When They Appear How They Interconnect <NO Clicks Required, Auto Timing on this slide> What is a Programmable System-on-Chip anyway? Since there are so many flavors of SOC in the marketplace, we simplify things by describing PSoC as follows: you get to define the functionality you want (digital and/or analog), when you want it and interconnected exactly how you want it . The PSoC concept is system design with a single chip, which has a microcontroller at its core and (almost) all of the other functions on-board needed to complete the system. <Wait for “HOW…” to appear, Click Mouse or Spacebar>

Example of “What Functions Appear”
One 8-Bit Counter One 16-Bit Timer One Full-Duplex UART w/Baud Rate Generator One SPI Slave (Full Duplex) Controller One 4-Input 8-Bit Delta-Sigma A/D One 6-Bit D/A One 8-Bit D/A Two Low-Pass Filters (Bi-Quad) We have two slides to come which will show two very different MCUs. This first MCU shown here consists of a low resolution 8-bit counter, a high resolution 16-bit timer, a full duplex UART with a dedicated baud rate generator, an SPI (serial peripheral interface) slave controller, 4 analog inputs to an 8-bit Delta-Sigma A/D converter, a 6-bit D/A output, an 8-bit D/A output, and two low-pass filters that can be cascaded if necessary. A fairly rich set of functions, not all generally available at all or in this combination on an off-the-shelf 8-bit MCU. < Click Mouse or Spacebar> On LEFT HAND SIDE – screen shot of PSoC designer software. Right side shows rich set of analog and rich set of digital peripherals.

Example of “What Functions Appear”
One 16-Bit Counter One 8-Bit PWM One Half-Duplex UART One SPI Master One 12-Bit Incremental A/D One Low-Pass Filter (Bi-Quad) One 8-Bit D/A Two Instrumentation Amplifiers This second MCU shown here consists of a different set of functions, a high resolution 16-bit counter, an 8-bit PWM, a half duplex UART with a dedicated baud rate generator, an SPI (serial peripheral interface) master controller, a 12-bit Incremental A/D converter, an 8-bit D/A output, one low-pass filter, and two instrumentation amps that can operate on the same or different analog inputs. Again, this is a fairly rich set of functions, not all generally available at all or in this combination on an off-the-shelf 8-bit MCU. < Click Mouse or Spacebar>

Both of these devices are made from the same chip
Example of “What Functions Appear” Both of these devices are made from the same chip - PSoC can be defined to meet customer requirements with Countless configuration possibilities One 8-Bit Counter One 16-Bit Timer One Full-Duplex UART w/Baud Rate Generator One SPI Slave (Full Duplex) One 4-Input 8-Bit Delta-Sigma A/D One 6-Bit D/A One 8-Bit D/A Two Low-Pass Filters One 16-Bit Counter One 8-Bit PWM One Half-Duplex UART One SPI Master One 12-Bit Incremental A/D One Low-Pass Filter One 8-Bit D/A Two Instrumentation Amplifiers Both devices shown are made form same chip. There can be countless configurations. Here is a side-by-side summary of the two MCUs. Two very different chips, but both come from just one device. The user gets to tell the chip whether to be the left chip or the right chip. And since the part is completely FLASH programmed, and can be programmed in circuit, you can tell this chip what it should be all the way up to final test by programming it in-circuit. But when does the chip really decide it should be the left chip or the right chip? When you define the chip, using the simple tools we provide, the description of the chip, including peripheral selection and pin-out is added to your program as a block of data. When you power up, that block of data is moved to a group of registers that control the configuration of the chip. So the chip really doesn’t get it’s personality until it actually powers up. So the personality of the chip is really the values in a set of registers! And that wasn’t even the good stuff. Now let’s hit the good stuff. < Click Mouse or Spacebar>

Example of “When They Appear”
Dynamic Re-Configurability means both devices can be the SAME CHIP at DIFFERENT TIMES in the SAME APPLICATION One 8-Bit Counter One 16-Bit Timer One Full-Duplex UART w/Baud Rate Generator One SPI Slave (Full Duplex) One 4-Input 8-Bit Delta-Sigma A/D One 6-Bit D/A One 8-Bit D/A Two Low-Pass Filters One 16-Bit Counter One 8-Bit PWM One Half-Duplex UART One SPI Master One 12-Bit Incremental A/D One Low-Pass Filter One 8-Bit D/A Two Instrumentation Amplifiers Can all change on the fly. And can make chances while the chip is running. Since the configuration settings are controlled by dynamic registers, the PSoC microcontroller can be dynamically changed to have a completely different set of features at any time. As your application changes state, the chip changes peripherals to meet the new state’s requirements. But it is even simpler than that… < Click Mouse or Spacebar>

Dynamic Reconfiguration
23 Hours 59 minutes per day Accepts Money Distributes Beverages A few seconds each night Dynamically reconfigures into a 300 baud Modem Transmits coin, beverage and maintenance status to central office Benefits Only cost delta is phone interface Increased machine profitability Dynamically configured while running. Here is an example. Takes money and dispenses beverages all day. However for short time each day it can report back to main hub and relay information.

Example of “How They Interconnect”
Same 8-Bit Counter Finally counts positive edges on pin 13 Sets pin 16 high after 77 edges An 8-Bit Counter Counts positive edges on pin 4 Sets pin 25 high after 10 edges Same 8-Bit Counter Later Counts positive edges on pin 8 Sets pin 21 high after 15 edges INPUT OUTPUT INPUT OUTPUT Here, we talk about how chip can interconnect. B/w internal peripherals and package pins. Helps make PCB routing a lot easier. With the PSoC MCU you control not only the functions but the pins connected to the functions. How many times have had only one counter but had to count more than one thing at different times. You had to put a multiplexer out on your board and use pins to drive it. Works, but that takes extra work and extra cost. Besides, you really need to know not just what to count, but when to change what you count. So you may also need to poll a couple pins to monitor what’s happening in the system. That’s possible, but way too difficult. Now lets see an example of what the PSoC MCU can do. Here you see the first pin selection for the one 8-bit counter you decided to include in your configuration. The input signal to count is connected to pin 4, and when 10 positive edges are counted, pin 25 will set high by the counter. < Click Mouse or Spacebar> Later your application needs to count the edges on another pin. To do this, you simply change the connection at the pin to move the counter input from pin 4 to pin 8. And all other aspects of the counter function can be changes as well, including the number of edges to count and the output pin. < Click Mouse or Spacebar> But, since the configurations are defined by volatile registers, so there is no limit to the pinouts or configuration of this or all of the functions for that matter. Here is a third arrangement, which has the counter input moved to pin 13, and the output of the counter is now connected to pin 16 with the number of edges to now set to 77. And since any pin can be set to interrupt, you even can let each individual signal determine when it needs to be connected to the counter, by only connecting the pin to the counter in an interrupt routine trigger by the input signal! It isn’t hard to see that a savvy design team could dramatically increase the value of a small set of functions used within A PSoC MCU as compared with what is possible with last year’s crop of 8-bit microcontrollers. This all turns the embedded design world on it’s head, putting the power into the hands of the designers to determine their own destiny, rather than live at the mercy of a vendor’s catalog and whims. < Click Mouse or Spacebar> INPUT OUTPUT

World-Class MCU Features
24 MHz/4 MIPs Operation at 5V 12 MHz Operation at 3.3V Single-cell (1.2V to start) Operation at up to 24MHz With Built-in Voltage Pump and Three Passive Components Eight-Level Low Voltage Detection/Alert Built-In Multiply-Accumulate Hardware (MAC) 8 X 8 Multiply, 32-Bit Accumulate Answer Available Immediately on Next Instruction Cycle 2.5% Accurate Oscillator with no ext. Components PLL for Precise Time-base With Inexpensive Watch Crystal Flexible Sleep Modes, as Low as 5μA in Standby 2.5% allows for no need to get an external crystal. It’s a very small size, low power, and low cost. All of these SOC capabilities would be worthless if the microcontroller features surrounding them didn’t meet your needs. The features listed here and on the following two slides,combined with the SOC capabilities we will explore further, all add up to a World-class microcontroller that you configure to meet your project needs exactly. Perfectly. < Click Mouse or Spacebar>

All Flash Program Memory (4 to 16 Kbytes) EEPROM Emulation in Flash Four Memory Protection Modes Allows Factory or Field Upgrade on Individual 64-byte Blocks From One Block up to the Entire Flash Memory Protectable Robust Read/write Protection Algorithm for Added Security In-System Programmable Supports Production Test/Calibration Re-Programming Supports Field Upgrade of firmware or configuration < Click Mouse or Spacebar>We recommend that all systems be designed for In-system programming. This helps in the prototype phase by allowing design engineers to download new firmware into the prototypes without removing the PSoC from the board. If the manufacturing group decides to use ISSP then the PCB will already support it. The flexibility of the PSoC allows the ISSP pins to be used for other functions and if a low impedance load is on an ISSP pin the ISSP programmer cannot overdrive the pin for programming.

Configurable I/O Pins Every Pin Can Source 10mA and Sink 25mA Integrated/Selectable Pull-up and Pull-down Resistors Selectable as Interrupt Source on Either Edge or Change in State 8 Muxable Analog Inputs (except 8-pin device) Up to 4 Analog Outputs w/ 40mA Integrated Drive 4 Direct Input Analog Lines (except 8-pin and 20-pin devices) < Click Mouse or Spacebar> Pins are configurable on a bit by bit basis.

PSoC Blocks Programmable System- on- Chip Blocks

PSoC Blocks- The Underlying Hardware
Digital Blocks (8) Two Types Basic Type (4) Communications Type (4) Programmed at the Function Level Not programmable at the Gate Level Analog Blocks (12) Three Types Continuous Time (4) Switch Capacitor A (4) Switch Capacitor B (4) Basic Communication Programmed at function level. So, its not a CPLD. The benefit is that its convenient and don’t need schematic or need to use VHDL. They can just choose the hardware w/o having to design the parts. This allows low cost Bad points though, some engs might want to integrate other digital circuits into parts on the board, but it won’t be possible. It’s a good trade off though.

Digital PSoC Blocks Eight 8-Bit Digital PSoC Blocks Available
Four Digital Basic Blocks Timer, Counter, PWM Dead Band Generator (2 Phase Underlapped Clock) Pseudo Random Source (PRS) Cyclic Redundancy Check Generator (CRC) Four Digital Comm Blocks All Basic functions, plus SPI Master SPI Slave I2C IrDA CRC16 Async Rx Async TX UART Difference b/w the two types of blocks basic and comm. W/ examples. Comm blocks include a shift register for doing comm functions.

Analog PSoC Blocks Amplifiers Comparators
Filters: 2, 4, 6 pole LP,BP,HP,Notch ADCs: Incremental, D-S, SAR DACs Continuous Time Upper right…show cont time w/ resistors Switch caps , replace resistors w/ capacitors and switches. This allows flexibility for functionality Switched Cap A Switched Cap B

User Modules User Module = Pre-configured Digital and Analog PSoC Blocks Analogous to an On-chip Peripherals Timer- Counters – PWM’s UART – SPI A/D –DAC’s - SAR Defines the Register Bits for Initial Configuration Selected via Double Click in IDE User Modules Include Application Programmer Interfaces (APIs) Interrupt Service Routines (ISRs) Specific UM Data Sheets For analog especially… a lot of engs do not know how to develop/design a filter. Here, all the information like that is written in data sheet. There is no need for HSPICE Here, you can also just call a function rather than write to a register. *PSoC designer generates a lot of firmware to help the user

Digital User Modules 8, 16, 24, 32-bit Timer 8, 16, 24, 32-bit Counter
8, 16-bit PWM 8, 16-bit Dead Band Generator (2 Phase Underlapped Clock) Pseudo Random Source (PRS) Cyclic Redundancy Check (CRC) Generator SPI Master SPI Slave Full Duplex UART IrDA receiver and transmitter Dig blocks are 8 bits wide. Cascaded together you can see how they work.

Analog User Modules A/D Converters D/A Converters Filters Amplifiers
8-bit Successive Approximation 8-bit Delta Sigma 11-bit Delta Sigma 12-bit Incremental 7-13 bit Variable Incremental Dual input 7-13 bit Variable Incremental Tri input 7-13 bit Variable Incremental D/A Converters 6, 8, and 9-bit 6 and 8 bit multiplying Filters 2-pole Low-pass filter 2-pole Band-pass filter Amplifiers Programmable Gain Amplifier Instrumentation Amplifier Inverting Amplifier Programmable Threshold Comparator DTMF Dialer More examples of analog side. There are many many many analog possibilities. We are continually making new UM. They will be included in new releases each time.

Software User Modules/ Reference Designs
I2C Master I2C Slave EEPROM LCD – Interface for Hitachi HD44780 controller Reference Design (hard- and software) : LIN-Bus controller 300 Baud modem Electronic Ballast For Fluorescent Lamps Q2 2003 Power Line Modem 2400 BAUD Q2 2003 Dig blocks are 8 bits wide. Cascaded together you can see how they work.

ADC Selection Trade off signal requirements with resource usage # Bits
# Analog Blocks # Digital Blocks Rate (SPS) ADCINC12 12 1 2 10-480 Minimum digital block usage, integrates noise ADCINCVR 7-13 3 k Reduced latency error TriADC 5 k Three simultaneous ADCs (also Dual) DELSIG8 8 30k Fast but multiplexing sacrifices speed DELSIG11 11 7.8k SAR6 6 40k Minimum total block usage

Flexible, Highly Integrated SOC, Cost-competitive Solution
Product Family Flexible, Highly Integrated SOC, Cost-competitive Solution Marketing Part No. Flash (Kbytes) RAM (Bytes) Single Battery Pump Package Pins CY8C PI 4 256 N PDIP 8 CY8C PI Y 20 CY8C SI SOIC CY8C PVI SSOP CY8C PI 16 28 CY8C SI CY8C PVI CY8C PI 48 CY8C PVI CY8C AI TQFP 44 Best of all, PSoC MCUs are priced ultra-competitively. Based upon your system needs, a system-to-system comparison will always tilt the value scale in the PSoC direction (we know, we have competitive cross-references of over 700 parts to prove it!) In mixed signal applications, we always come up competitive and often present a downright steal over a traditional microcontroller and off-chip functions. And that is before you consider the increased reliability and flexibility of the system in-chip rather than scattered around a circuit board!

PSoC Microcontroller Families
CY8C25xxx/26xxx 8 Digital PSoC blocks 12 Analog PSoC blocks 16k Flash bytes SRAM 6-44 IO CY8C27xxx Improvements: Analog Digital CY8C24xxx 4 Digital PSoC blocks 6 Analog PSoC blocks 4k bytes Flash 256 bytes SRAM 6-16 IO CY8C21xxx 4 Digital PSoC blocks 12bit ADC 4k bytes Flash 256 bytes SRAM 6-16 IO

PSoC Microcontroller CY8C27xxx
8 Digital PSoC blocks 12 Analog PSoC blocks 16k Flash bytes SRAM 6-44 IO Improvements compared to current part: Reduction of analog noise Improved OpAmp offset: automatic compensation ( ~1mV ) 48MHz clock can be turned of if not needed: less current consumption More flexible external clocking: kHz Crystal or 15MHz-30MHz external clock signal Dedicated I2C block More flexible digital blocks: AND, OR, NAND, NOR, ... functions

Sample Roadmap CY8C21xxx CY8C27643 CY8C26643 CY8C27443 CY8C26443
Q4 2003 Development Functionality CY8C27643 CY8C27443 CY8C27233 CY8C27122 Q2 2003 CY8C26643 CY8C26443 CY8C26233 CY8C25122 Current CY8C24xxx Q3 2003

PSoC Designer Integrated Development Environment Device Editor
Application Editor C Compiler Assembler Librarian Debugger As you have already seen a glimpse of, harnessing the power of Programmable System-on-Chip requires a well developed tool. The screen shots shown came from PSoC Designer, the Integrated Development Environment for the PSoC Microcontrollers. This tool brings the expected components to support embedded system design: the ability to develop the application code (Application Editor), the ability to develop applications in a high level programming language (optional C compiler), the ability to build the code into and executable program (Assembler and Librarian) and the ability to debug and emulate applications (Debugger). These components are shown in white because they are the necessary and expected parts of any development environment. The component listed in blue, the Device Editor, is the unique capability PSoC Designer delivers. It is with the Device Editor that a designer creates their custom configuration or System-on-Chip. < Click Mouse or Spacebar>

PSoC Designer Device Editor – Modes of Operation
Device Editor has Three Windows of Operation Selecting User Modules Placing User Modules Specifying Pin-out The Device Editor has three modes of operation corresponding to the three phases of creating your “Perfect Fit” MCU < Click Mouse or Spacebar> The first task is to select the functions you want in your MCU from the catalog of User Modules shown as categorized lists on the left side of the screen. What’s a User Module? This is our term for a specific piece of functionality in the MCU. As you look through the catalog you will notice there are User Modules which correspond to expected peripherals in a traditional MCU, including A/D converters, counters, UARTs, etc. You will allso notice unique functions, not found in conventional MCUs, such as, but not limited to CRC generator, amplifiers, as well as a wide range of types of expected functions (different types and/or sizes of A/Ds and D/As or instance). < Click Mouse or Spacebar> Once you have selected the functions you want, the next step is to map these onto the raw resources of the PSoC MCU. And set the parameters for the functions (such as the gain on the amplifier or the period of a counter). < Click Mouse or Spacebar> The final phase is to connect the internal SOC and individual functions to the output pins of your choice. And then of course you can always jump back and forth between these phases as your understanding of the project requirements changes or to interate your design towards the optimal solution. Unlike some tools, the process works just as smoothly the second, third or fourth time as you refine your system configuration. < Click Mouse or Spacebar>

Device Editor - The End Result
User Clicks “Generate Application” Icon The Software Takes All User Inputs; Generates files specifying the configured device Sets up the source files for the project application code Moves the user to Application Editor to start coding Creates a custom configuration sheet based on your inputs – Your custom “data sheet” The real beauty of the Device Editor is delivered so effortlessly that it is easy to miss the magnitude of the benefit. Once you have completed the three phases of the Device Editor and now have a definition for your MCU, the device editor, when you push the “Generate Configuration” button, creates all the coded necessary to program the 512 registers that control the PSoC MCU’s configuration. This is a set of files which will execute at power-up. And it is so complete that you will also get a full set of customized API functions (for instance a function to start or stop a timer or set its period) and the ISR files with placeholders for your own interrupt code. If you aren’t fully aware of it, this is a process that typically take anywhere from several days to several weeks with a conventional MCU and is often fraught with unintended obstacles. For a simple comparison, take any other MCU and see how long it takes you to go from opening the package to connecting and blinking an LED. Even a simple task like this can take days of configuration and headaches. But one button-press in PSoC Designer and you are on your way to developing your application, not preparing the MCU. < Click Mouse or Spacebar>

Software IDE Application Editor
For Users to Write Code For Users to Assemble/Compile Code View and edit individual source files Set and remove bookmarks (Editing tool) Set and remove breakpoints (Debugging tool) Assemble/compile individual files Build entire project including assemble/compile* all flies in project Source line error pointer Here is a look at the rest of the components that comprise the PSoC Designer Integrated Development Environment Blah *The C compiler needs to be enabled for use

PSoC Designer C Compiler
The CY3202-C compiler is fully integrated into the PSoC Designer IDE. PSoC Designer supports C source level debugging. In order to activate the compiler, you must enable an upgrade. Features Include: ANSI C Compiler Supports Inline Assembly and Can Interface with Assembly Modules Integrated code compressor Modern Stack-Based Architecture 7 Basic Data Types Including IEEE 32-Bit Floating Point Assembler and Linker Math and String Libraries C Interrupt Service Routines Librarian Code development is supported through the M8C assembly language as well as an optional C compiler ($145) Now is a great time to give away half of the C compilers. Do a raffle and select 25%-30% of the audience Give the other’s away at the end of the seminar. < Click Mouse or Spacebar>

Software IDE Debugger Interface to ICE Unit
View contents of Register and Memory spaces Change the contents of these spaces Connect to ICE Run/Halt /Single Step Set breakpoints and event points Capture trace The fully integrated Debugger and ICE are full-featured and fully reflect the unique capabilities of the PSoC MCU as well as the expected debugging functions. For instance, from within the debugger a user can write a value into one of the configruation registers and dynamically change or adjust the functionality of the PSoC MCU, allowing an interactive debug of the system as well as the code (i.e. change a receiver block into a transmitter block and see it changing functionality). < Click Mouse or Spacebar>

Development Kit CY3205-DK Basic Development Kit
Kit includes everything to support the 28-pin PDIP package Price: $248 The hardware for PSoC MCU development is available from us today, and includes a full-featured interactive emulator (not a peek and poke tool) < Click Mouse or Spacebar> Here you see: 28 Pin package set up ICE – White box in-circuit emulator You have CAT5 cable Pup – w/ LEDs this part is for validation, allowing customer to design small project and blink the LED Two 28pin package samples Y programmer board Uses a foot to adapt package type to a PCB New power supply volts. Works for all. Adaptor included. Its all in one kit now. Not two kits anymore.

PSoC ICE Pod Kits Smallest POD on the market fits customer PCB better.
Versions are available for all device/package types Sold separately to support various pin-outs Every part type/package type has a pod/foot Pod Pup Mask Shows close up view of Rev E pod. This is the latest. To get a new pod to upgrade an old kit. Click on active design support. At top of page, you can request a new pod upgrade along w/ Y programmer. IT IS FREE! And to personalize the emulator to your project we have the pods that match every PSoC MCU type and package, allowing direct emulation on your hardware of even our surface mount devices. Or you can create your custom kit by purchasing multiple pods to take your project from bread-boarded prototye all the way through surface-mounted production, with emulation capability at every step. We have also provided device programming either using the 5-pin header and connecting to any of the devices, in or out of circuit, or by using a programming board we are just starting to include in development kits. We also have third-party programming support and volume device programming from Cypress and through distributors. BP MicroSystems was the first to provide this and Hi-Lo as well as Data IO are in the process of providing it. < Click Mouse or Spacebar> Foot

What is a Y-programmer ??? Programmer board with socket available for each package type Connects to ICE

PSoC Microcontroller Design Flow
Determine system requirements Choose User Modules Place User Modules Set global and User Module parameters Define the pin-out for the device Generate the application Review generated code Demonstrate working configuration <Auto Timing through bullets> Now that you have seen the overview of the PSoC microcontroller and PSoC Designer, lets jump in the deep-end and get started. We will follow these steps in order and at the end see the working MCU project (if you have an ICE available) Start PSoC Designer IDE software at this time, and we will walk through step by step in the following slides. < Click Mouse or Spacebar>

Our Project Requirements:
Blink two LEDs at approx 2Hz, with duty cycle of 40% and 20% Implementation: Create An MCU with Two Pulse Width Modulators: Select Two PWM User Modules Set the PWM parameters Initialize the global clocks Connect the PWM outputs to the PSoC Pup LEDs We want to create a fairly generic MCU with the functions shown, The unique element here is the on-board temperature sensor, but otherwise this should look like a familiar and very useful device. < Click Mouse or Spacebar>

Our Project Implementation:
Use on chip clock resources (24V1, 24V2) to generate clocks for selected User Modules P2[2] 16-bit PWM ÷ 65535 (1.4Hz) (1.5MHz) (93kHz) 24MHz ÷16 ÷16 24V1 24V2 We want to create a fairly generic MCU with the functions shown, The unique element here is the on-board temperature sensor, but otherwise this should look like a familiar and very useful device. < Click Mouse or Spacebar> P2[3] 16-bit PWM ÷ 65535 PSoC devive (1.4Hz) Pup board

Let’s Create Our Project
Start PSoC Designer Click Start New Project Select Create a new Configuration Type in the name GettingStarted Set destination directory Desktop/default or select one The dialog shown here appears whenever you start PSoC Designer <Click on “Start new project” > We want to create a new project titled GettingStarted at the location c:\windows\desktop <Click on “Create a new Configuration” or Next> <Click on “Yes”>

Select the Base Part View the drop-down menu and the catalog We’ll use CY8C PI (28 PDIP, same as the pod) The next step is to choose a device type. This is achieved through the drop-down menu if you know which device you want, or by viewing the catalog, which we’ll do first. <Click on “View Catalog”> The table you see lays out the parametric differences between the devices to let you select the one that matches your needs. But what if you don’t know what you need? Will you have to start over from scratch if your original selection doesn’t have enough I/O or memory, and will you have to recreate everything? No, PSoC Designer makes it easy to maigrate a project both to a larger part as well as to a smaller one. And all you have to change is the pins that either disappear or appear as you migrate. All of the system-on-chip work goes along without change. This will also hold true to the extent possible as we release additional product families, allowing you to reuse projects many many times, just adding or adjusting your application or system to meet the new or different requirements. Lets choose the 28-Pin Dual Inline device, partly because our demo hardware is based around this and partly because it is the smallest device with the largest memory. <Click on “Select”> < Click Mouse or Spacebar>

Select Project’s Language Assembly and C languages available, (C, only if enabled) We’ll choose assembly The final choice to make is the application development language. This choice appears at this time because the IDE is going to start creating the code files to support your application, and these will need to be in the language you ultimately want to do your development in. As mentioned earlier, if you want to change your mind, the tool allows for this through the “Clone a configuration” selection, without having to start all your work over. <Click on “Finish”>

Select User Modules Explore the “Select” Mode of Device Editor
User Module Catalog ( tabs on left side of screen) Resource Manager (right side of screen) User Module Data Sheet Viewer (bottom middle of screen) Adding, Deleting, User Module Instances Select User Modules for this Project Go to the indicated tab section and double-click PWMs tab,PWM16 : An 16-bit Pulse Width Modulator Repeat the selection and Select a second PWM16 < Click Mouse or Spacebar> First step is to select the User modules or functions that meet our project requirements, but first lets take a look at what the Selection mode of the Device Editor contains The user modules catalog is at left and you can see the rich set of user modules available. And more user modules are being added all the time, a few that are on the list to be available by the end of the year are a BandPass filter, more ADC and DAC choices and a DTMF generator. At the far right is the Resource manager that provides a running total of resources used as you make selections In the middle is shown the data sheet for each UM, which can be scrolled or accessed via the tabs To select a function double click it from the catalog and it appears in the upper selection pane. From there you can rename it, activate the data sheet or even delete it. < Click Mouse or Spacebar> Lets now select the specific UMs for our project < Click Mouse or Spacebar> Now select each UM in the selection pane in turn and click the name field so we can specify their names. This is an important step to do though not required. By selecting application relevant names you will enable your application code to be better documented and make reuse of project code. Also, Using RTC rather than the default Counter16_1 means that later you could use a counter of a different size, larger or smaller and the interfaces would remain the same name, isolating the application code from these changes. < Click Mouse or Spacebar>

Place User Modules STOP! Explore the “Place” Mode of Device Editor
Next Position icon Selecting the “Active” UM block Place Here icon Unplace icon Place User Modules for this Project STOP! How do I know where to place the User Modules? How does PSoC Designer help me? < Click Mouse or Spacebar> Explore the enabled features of this mode by clicking on one of the UMs and then trying the enabled buttons to see the possible placements, place, and unplace the module. Also, if the UM consists of multiple blocks, you can click on one of the blocks and now it will be the block which is affected directly by the “Next Position” button. Now lets place our modules But How? Where do I place them and how do I know what to do?

How to Place User Modules
Try-out the modules individually first See how restrictive they are, then return to place PSoC Designer will only allow the modules to be placed where the chip can support them PSoC Designer will not prevent a placement that may create a conflict for resources Example: If you have an ADC and temperature sensor, they both use the comparator bus. There is only one comparator bus per column, therefore these two UMs must reside in separate columns in order to be used simultaneously. Read the UM Data Sheets for details Use the Cypress MicroSystems Online Resources < Click Mouse or Spacebar>

Place User Modules Place the two selected UM’s in the default positions. PWM16_1 – Digital Blocks DBA00/DBA01 PWM16_2 – Digital Blocks DBA02/DBA03 Recommend to put the PWM’s in the Basic Digital Blocks to Save the Digital Com Blocks Lets go through each UM in turn and place it. I have chosen the blocks to put them in and indicated if there was a specific reason. Positions of UMs will depend upon the system you are trying to accomplish, since the inter-connection possibilities are affected by position. More details on this are found in the device datasheet which you will find loaded into your “Documentation” directory of PSoC Designer. When we are all done you may want to just play around with the project (perhaps create a clone) and try different positions and see how they affect the system. The block labels shown for each UM correspond to the label you will see in the block diagram < Click Mouse or Spacebar>

Configure Global Resources
CPU_Clock: Set to 12MHz 32K_Select: Set to Internal Not using an external crystal PLL_MODE: Set to Disable PLL can only be enabled when 32K_Select is External (crystal) Sleep_Timer: Set to the default value of 512_Hz. 24V1= 24MHz/ N: Set to 16 This divides 24MHz by 16 = 1.5MHz 24V2=24V1/N: Set to 16 This divides the 24V1 by 16 (1.5MHz/16=94kHz) Analog Power: Set to SC On/Ref Low This is required to power up any of the analog blocks, depending on the number of analog functions. A Ref Med or Ref High may be required (and will increase power consumption) After each function is configured we also want to make sure all the common or global resoureces are set properly. In this case it is the device data sheet in conjunction with configuration decisions for user modules which will determine how you need to set global resources. < Click Mouse or Spacebar>

Configure Global Resources
Ref Mux: Set to (Vcc/2) ±Bandgap (the default) Op-Amp Bias: Set to Low (the default) This is not recommended as anything but low A_Buff_Power: Set to Low (default) This selects the power level of the analog output buffer There is a tradeoff between drive output power and power consumption. Low is adequate for most projects SwitchModePump: Set to Off VoltMonRange: Set to 5.0V VoltMonThreshold: Set to 80% < Click Mouse or Spacebar>

Configure User Modules
PWM_1: We want to generate a 1/5 duty cycle User module parameters can be configured in two ways: through the GUI or through the User Module Parameters window. In this class we will use the User Module Parameters window in the left bottom corner. Set Clock to 24V2 (94kHz) Set Enable High to keep the PWM always running Set Period to (1.4Hz) Set PulseWidth to 13107 Compare Type Less Then Or Equal Interrupt Type Terminal Count Set Output to Global_OUT_2 Now configure the Baud Rate Generator < Click Mouse or Spacebar>

PWM_1: We want to generate a 1/5 duty cycle Now configure the Baud Rate Generator < Click Mouse or Spacebar>

PWM_2: We want to generate a 2/5 duty cycle Set Clock to 24V2 (94kHz) Set Enable High to keep the PWM always running Set Period to (1.4Hz) Set PulseWidth to 26214 Compare Type Less Then Or Equal Interrupt Type Terminal Count Set Output to Global_OUT_3 Now configure the Baud Rate Generator < Click Mouse or Spacebar>

Interconnect Blocks to Resources
What interconnection possibilities are there? Device Inputs Device Outputs Clocks Block-to-block When you specify a PSoC block connection to a pin you are making a physical connection to the hardware of the PSoC device. All the resources are configured, but are all the system connections made? What are the connections that need to be made? < Click Mouse or Spacebar> Here are all the things that can/must be connected to complete the functionality. DAC8 connections Check that all clocks are connected

Define the Pin-out What pins need to be defined? UM Inputs UM Outputs
General Purpose IO Block-to-block What pin-out options are there? Permanent vs. test/debug What happens as pins are defined? Pin-out our project LEDs SignalOut Define the pinout for your system. < Click Mouse or Spacebar>

Connect PWM_1 output to the pins We have already enabled the output from block Global_Out_2 Go to Pin 21 (Port_2 Bit 2) Enable the Port 2_2 (top choice) pin and then Chose Global_OUT_2 (strong) This will result in turning the pin dark red for Global Out Port 2 is connected to the LEDs on the Pup board. All the resources are configured, but are all the system connections made? What are the connections that need to be made? < Click Mouse or Spacebar> Here are all the things that can/must be connected to complete the functionality. DAC8 connections Check that all clocks are connected

Connect PWM_2 output to the pins We have already enabled the output from block Global_Out_3 Go to Pin 7 (Port_2 Bit 3) Enable the Port 2_3 pin and then select Global_OUT_3 (strong) This will result in turning the pin dark red for Global Out Port 2 is connected to the LEDs on the Pup board. All the resources are configured, but are all the system connections made? What are the connections that need to be made? < Click Mouse or Spacebar> Here are all the things that can/must be connected to complete the functionality. DAC8 connections Check that all clocks are connected

Configuration Complete!
Save project- Go to File tab Now What? Where are we? Time to Generate Application All settings used by PSoC Designer to create the boot-up code to configure the registers at reset ISRs are created (but not updated) APIs are created or updated Device Data Sheet generated You must Generate Application whenever changes are made to the configuration Save your project if you haven’t already done so. So where are we? We have just complete (for now) the entire system configuration, set the parameters for the functions all the way down to the periodic interrupt for the frame and the baudrate on the UART. Now the fun part, let PSoC Designer take all these setting and generate our code Each time you make a change to your configuration you will want to regenerate the application, which will update all originally generated code files except for ISRs, which must be removed manually from a project (using the Project manager of PSoC Designer) if you want the tool to re-generate them. Be careful with ISRs, since they are likely to contain your code as well as generated code. < Click Mouse or Spacebar> Now switch to the Application Editor view

Time to Create Application Code
PSoC Designer creates application code for the user based on the inputs from the Device Editor configurations. View the files on the left side of the application window. All interrupt routines, header files, include files, configuration tables. Application code for using the selecting User Modules can be used as supplied or modified by the user. To complete your project you need to insert the code excerpts I have provided into main.asm and RTCINT.asm < Click Mouse or Spacebar>

Create Application Code
Open the PWM16_1.asm file Select the PWM16_1_Start line routine and copy and paste it into the main.asm file Open the PWM16_2.asm file Select the PWM16_2_Start line routine and copy and paste it into the main.asm file export _main _main: ; Insert your main assembly code here. call PWM16_1_Start call PWM16_2_Start ret To complete your project you need to insert the code excerpts I have provided into main.asm and RTCINT.asm < Click Mouse or Spacebar>

Create Application Code
To complete your project you need to insert the code excerpts I have provided into main.asm and RTCINT.asm < Click Mouse or Spacebar>

Build Project Assembles code, links, and locates
Can individually assemble files as well Explore Application Editor Features Project file management (view/add/delete files) Finding compilation errors Build project and explore the files as well as the application editor features < Click Mouse or Spacebar>

Execute Project Within Debugger
Switch to the Debugger – What’s Different? Looks like Application Editor, but files are read-only Connect to the ICE Download the project to ICE Now lets have fun. If you have an ICE, make sure it is connected with the Pup board plugged into the Pod. Press the Connect button, then download the project. Now press the green arrow to execute. The LEDs should show the value stepping down, corresponding to the level which is being generated by the DAC8 and put out as an analog value on the middle pin of the Pup Board. Congratulations! You have completed a not-so-simple MCU project and it was Fast! Any questions? Here is a preview of other upcoming Teletraining Modules Module II will go into the use of PSoC Designer Debugging capabilities in great detail, including complex event thread features that help you quickly pinpoint certain specific behavior, and improve or correct it. Module III will return to the design aspects and this time dig into how to take advantage of dynamic reconfiguration features to both stretch resources and implement complex signal flows which have characteristics that match each individual signal you want to sense (amplification, filtering and analog-to-digital conversion).

Select the green arrow – Go button The two LED’s should flash at rotating rates Let’s set a breakpoint on the first line of code in the main.asm routine Now lets have fun. If you have an ICE, make sure it is connected with the Pup board plugged into the Pod. Press the Connect button, then download the project. Now press the green arrow to execute. The LEDs should show the value stepping down, corresponding to the level which is being generated by the DAC8 and put out as an analog value on the middle pin of the Pup Board. Congratulations! You have completed a not-so-simple MCU project and it was Fast! Any questions? Here is a preview of other upcoming Teletraining Modules Module II will go into the use of PSoC Designer Debugging capabilities in great detail, including complex event thread features that help you quickly pinpoint certain specific behavior, and improve or correct it. Module III will return to the design aspects and this time dig into how to take advantage of dynamic reconfiguration features to both stretch resources and implement complex signal flows which have characteristics that match each individual signal you want to sense (amplification, filtering and analog-to-digital conversion).

NOTE: If you tell the student online to copy the code lines on this slide. Their PWM will have a different name from the one pictured. If not corrected, the code will not build correctly Now lets have fun. If you have an ICE, make sure it is connected with the Pup board plugged into the Pod. Press the Connect button, then download the project. Now press the green arrow to execute. The LEDs should show the value stepping down, corresponding to the level which is being generated by the DAC8 and put out as an analog value on the middle pin of the Pup Board. Congratulations! You have completed a not-so-simple MCU project and it was Fast! Any questions? Here is a preview of other upcoming Teletraining Modules Module II will go into the use of PSoC Designer Debugging capabilities in great detail, including complex event thread features that help you quickly pinpoint certain specific behavior, and improve or correct it. Module III will return to the design aspects and this time dig into how to take advantage of dynamic reconfiguration features to both stretch resources and implement complex signal flows which have characteristics that match each individual signal you want to sense (amplification, filtering and analog-to-digital conversion).

Select the green arrow – Go button The program will stop at the first call to Start the PWM Use the Step function (First blue arrow) to step through the assembly code. Observe the LED’s Now lets have fun. If you have an ICE, make sure it is connected with the Pup board plugged into the Pod. Press the Connect button, then download the project. Now press the green arrow to execute. The LEDs should show the value stepping down, corresponding to the level which is being generated by the DAC8 and put out as an analog value on the middle pin of the Pup Board. Congratulations! You have completed a not-so-simple MCU project and it was Fast! Any questions? Here is a preview of other upcoming Teletraining Modules Module II will go into the use of PSoC Designer Debugging capabilities in great detail, including complex event thread features that help you quickly pinpoint certain specific behavior, and improve or correct it. Module III will return to the design aspects and this time dig into how to take advantage of dynamic reconfiguration features to both stretch resources and implement complex signal flows which have characteristics that match each individual signal you want to sense (amplification, filtering and analog-to-digital conversion).

Now lets have fun. If you have an ICE, make sure it is connected with the Pup board plugged into the Pod. Press the Connect button, then download the project. Now press the green arrow to execute. The LEDs should show the value stepping down, corresponding to the level which is being generated by the DAC8 and put out as an analog value on the middle pin of the Pup Board. Congratulations! You have completed a not-so-simple MCU project and it was Fast! Any questions? Here is a preview of other upcoming Teletraining Modules Module II will go into the use of PSoC Designer Debugging capabilities in great detail, including complex event thread features that help you quickly pinpoint certain specific behavior, and improve or correct it. Module III will return to the design aspects and this time dig into how to take advantage of dynamic reconfiguration features to both stretch resources and implement complex signal flows which have characteristics that match each individual signal you want to sense (amplification, filtering and analog-to-digital conversion).

On-line Support Self help knowledge base
Submit online applications support with a 4 hour response guarantee Community PSoC forum

Additional Support Resources
Application Notes Reference Designs Cypress Field Application Engineers Cypress Design Center Engineers

Tele-Training Live Classes 4 Day’s a Week Actual design projects completed in the two hour classes with high quality presentation and full documentation Taught by Factory PSoC Experts Classes for all levels of Experience

External Design Resources
Over 140 Design Consultants are enrolled in the Cypress MicroSystems program. Contact information and a short bio can be found at either page listed here: Full Consultant Support Program Factory Training Monthly Newsletter Free Tools, Samples, Software

Application - Examples

Reference Design Lin Bus Reference Design Available Now!

LIN Bus Reference Design Overview
LIN bus reference design created jointly by Cypress Microsystems and Crealie Logiciel Enfoui Includes hardware board Includes all software Includes PSoC configurations for master and slave nodes Demonstrates the use of PSoC in LIN applications Has 1 master node, and 2 slave nodes Passes simple messages to light LEDs Packaged into reference design kit with all documentation ($195 US)

Lin Bus Demonstration Board

Reference Design Power Line Modem
2400 BAUD, EN Compliance and a spare microcontroller Remote monitoring / control applications Thermostat Lighting Replace DALI in ballast

PSoC Solution AC Line interface standard passive design
Filters are clock synchronous S+K filter uses 4 external parts 12.0 MHz oscillator External replaced by on-chip PLL

Reference Design (CY3220BALLAST-RD)
Electronic Ballast For Flourescent Lamps Using PSoC PSOC is ideal for electronic ballasts: control the lamp drive circuit can also add connectivity. Benefits: Reduced circuit complexity/ lower build cost. Digital dimming, networking. Better “manufacturability” as PSOC ballasts are the first TRUE digital ballasts.

STUFF all this into a single low cost PSoC
Competitive Solution Current Best Competitive Ballast Implementation MCU $1.20 Ballast Controller IC $2.50 Power Factor Chip $0.75 Other Components $8.55 Total ballast cost $13.00 STUFF all this into a single low cost PSoC

PSoC Value Solution MCU $2.20 Transistor Driver IC $.45
Current Best Competitive Ballast Comparison MCU $2.20 Transistor Driver IC $.45 Power Factor Chip $0.75 Other Components $7.80 Total ballast cost $11.20 PSoC costs more than the MCU it replaces, but the overall BOM cost goes down

Important Features for Ballast Reference Designs
Drives one or two lamps, T8 or T5 Low total harmonic distortion High power factor >= 98% Standby power less than 1W Inherent transistor protection Dimming range % Timed pre-heat of filaments Missing lamp detection Short/open detection on four filaments DALI communication (Digital Addressable Lighting Interface) serial communication standard for remote monitoring and control of lighting systems

PSoC Applications Tachometers
Traditional tachometer implementation Sensor Amplifier $0.35 MCU $1.00 Display driver $0.75 $0.05/button $0.10 Integrated Crystal $0.15 A/D Converter $0.75 EEPROM $0.35 Total traditional cost $3.45 Industry tachometer examples STUFF all this into a single low cost PSoC

PSoC Applications Tachometers
Traditional tachometer implementation PSoC $2.00 MCU $0.00 Display driver $0.00 $0.05/button $0.00 Integrated Crystal $0.00 A/D Converter $0.00 EEPROM $0.00 Total PSoC cost $2.00 Industry tachometer examples

Tachometer Block Diagram
PSoC Display Driver EEPROM Real Time Clock PWMs Charge Pump for Ultra Low Voltage Operation I2C Core Tachometer function MPU More Filters, Amplifiers, A/D converters if needed Timer Value 600 kHz 30 kHz 8 bit Counter 8 bit Count 30kHz 8 bit TACH timer HW Capture Comparator Clocks for external use MPU PGA Tach Random Number Generators 2-Pole low pass filter TACH_1 A=1

PSoC Application Motor Control
Fan Motor Thermistor Temperature PSoC ADC PWM LUT TIMERS UART PGA PSoC Using thermistor instead of internal temp to demonstrate additional user modules. Talk about the 3 blocks on the labVIEW screen. RS-232

PSoC user modules PWM_8 UART Baud rate clock
Drives motor UART Used to upload speed value to PC and download mode to the PSoC Baud rate clock 57.6 kb/s Communication interval timer 2 Hz interrupt. Loads speed value into UART, updates PWM. PGA Connects thermistor network to ADC. Delta-Sigma ADC Converts thermistor input. Switch over to the PSoC IDE to get a view of the user modules utilized and talk about the function that each one performs in the project. ADC sampling at 5KHz UART Baud rate is 57kB

PSoC firmware LUT A LUT B UART Interrupt Service Routine (ISR)
Contains gain so that small temperature change results in large change in fan speed. LUT B Manual mode, increase in PWM duty cycle proportional to movement of slide control in Lab View. UART Interrupt Service Routine (ISR) Eliminates polling that may waste throughput. Communication timer ISR 2 Hz, updates PWM compare register, sends PWM duty cycle to Lab View. Main Initialize user modules, handles commands from Lab View Design will run without PC communication link Depending on the number of questions we may or may not show Visio diagrams of the main and different ISR’s. We should be at about the 20 minute mark of the presentation. Emphasize that the customer could use this design as is, since we are starting up in automatic mode.

STUFF all this into a single low cost PSoC
PSoC Applications Magnetic Card Reader Traditional one or two channel magnetic card reader implementations Industry examples Sensor Amplifiers $0.50 MCU $1.00 Display driver $0.75 $0.05/button $0.10 Integrated Crystal $0.15 A/D Converter $0.35 EEPROM $0.35 Total traditional cost $3.20 to $15 depending on application STUFF all this into a single low cost PSoC

PSoC Value Traditional mag card implementation PSoC $n.nn MCU $0.00
Display driver $0.00 $0.05/button $0.00 Integrated Crystal $0.00 A/D Converter $0.00 EEPROM $0.00 Total PSoC value $3.20 to $15 Customers’ cost are also reduced by fewer components, ease of manufacturing, shorter development time, and leverage with the reuse of PSoC! Industry examples

Magnetic Card Reader Block Diagram
Display Driver EEPROM Real Time Clock PWMs – Motor Drive Charge Pump for Ultra Low Voltage Operation I2C Bit Timer 1 x16 x10 Ref Lo 100 Core Mag Reader 10K 33K Comparators PWM-1 Ref Hi 470pF 0.1uF UART Tx Out Baud Rate Generator Dual Magnetic Head Ref Lo x16 x10 100 10K 33K Comparators PWM-2 Ref Hi 470pF 0.1uF Bit Timer 2 PSoC

PSoC Application Pyroelectric Motion Detector
Traditional PIR detector implementation Sensor Amplifier $0.35 MCU $1.00 Relay Driver $0.35 $0.05/button $0.10 Integrated Crystal $0.15 Comparator $0.20 EEPROM $0.35 Total PSoC cost $2.50 Industry PIR Detection examples

PSoC Value Traditional PIR detector implementation Sensor Amplifier
$0.00 PSoC $n.nn Relay Driver $0.00 $0.05/button $0.00 Integrated Crystal $0.00 Comparator $0.00 EEPROM $0.00 Total PSoC value $2.50 STUFF all this into a single low cost PSoC 75% of the Analog blocks and 61% of the digital block still available for free product enhancement. Industry PIR Detection examples

PIR Detector Block Diagram
Display Driver EEPROM Real Time Clock PWMs Charge Pump for Ultra Low Voltage Operation I2C Core PIR function More Filters, Amplifiers, A/D converters if needed MUX PGA PGA ADCINC 240 sps Alarm PIR Element MCU Clocks for external use Random Number Generators PSoC

Customer Example - Precision Solar
Their Business Highway signs Benefits They Cared About “The perfect fit MCU” Low cost / high function tools Excellent application support Successful Sales Strategy Distributor identified/ Rep made it happen Had their schematic analyzed by CMS applications

Customer Example – Wildseed/Elektrobit
Their Business Cell phone with “skin” Adapt phone to market Benefits They Cared About Wide range of peripheral functions Ability to add features to their product Ability to offload main processor Successful Sales Strategy Distribution presentation to start the process Training to reduce time to productivity Support for the consultant doing the design

Customer Example - Dynalite
Their Business Commercial lighting components Benefits They Cared About Flexibility Analog integration Successful Sales Strategy Lots of persistence and hard work by distributor Range of capability of PSoC

Customer Example - Eaton
Their Business Inductive sensors Benefits They Cared About Integration/board size reduction Common platform requirement Successful Sales Strategy Aligning customer with consultant Support for entire application,not just PSoC

Customer Example - Teleflex
Their Business Marine and truck gauges Benefits They Cared About Inventory reduction 400 gauges replaced Board diversity reduction Successful Sales Strategy Distribution partner support Consultant instrumental in PSoC choice. Great support for the customer and consultant

Customer Example – Icon
Their Business Fitness equipment Benefits They Cared About High integration Cost reduction from part reduction Flexibility/customizability Successful Sales Strategy Hands-on full day training Great support Competitive pricing

Customer Example – CKesp
Their Business Facial Massagers Benefits They Cared About Single Hardware platform High integration Cost reduction from part reduction Successful Sales Strategy Support for the consultant doing the design. PSoC Sales Champion in the UK

PSoC: Configurable Mixed-Signal Array with On-chip Controller

Similar presentations

Presentation on theme: "PSoC: Configurable Mixed-Signal Array with On-chip Controller"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

PSoC: Configurable Mixed-Signal Array with On-chip Controller

Similar presentations

Presentation on theme: "PSoC: Configurable Mixed-Signal Array with On-chip Controller"— Presentation transcript:

Similar presentations

About project

Feedback