Actions
Forum Thread Details
  • Replies 9 replies
  • Subscribers 598 subscribers
  • Views 663 views
  • Users 0 members are here
Related

PSoC 5 PCB Design Using Eagle

Former Member

I'm new to PCB design and would like to use Eagle CAD to create my own PCB using the PSoC microcontroller. To help myself learn, I'd like to first model the PSoC 5 in Eagle along with a USB interface to program it, and respective power connections. I've already made an Eagle library part for the PSoC 5 but have no idea where to go from there. How do I properly read the datasheets to know and learn how to make connections? I'm new to all of this so please let me know if there is any information I'm missing. My first goal would be to program the PSoC 5 with the USB interface to control a simple servo with a PWM signal. Any help would be greatly appreciated

 

Thanks

Parents

  • I'd suggest getting a PSoC 4 Pioneer Kit.  It's only US$25 and has both a PSoC 4 and a PSoC 5.  The PSoC 5 is normally used to program and debug the PSoC 4, but you can reprogram it for other purposes.  There are lots of information and projects at the link to get your started.

  • in reply to johnbeetem

    Thanks for the advice John Beetem. But my idea isn't to buy a kit or something already made. I'd like to design my own PCB using the PSoC 5 microcontroller to take advantage of all the programming software developed for the PSoC already. If I had just the PSoC 5 microcontroller, how would I design a PCB containing just the power connections, a USB interface, and a way to send a PWM signal to a servo? I'd like to do something similar to the FreeSoC (http://freesoc.net/) or EzPSoC3 (http://dangerousprototypes.com/docs/EzPSoC3). I'd like some suggestions or guidance as to how to read a datasheet to learn how to design everything on Eagle CAD.

     

    Thanks

  • in reply to Former Member

    I thought of the PSoC 4 Pioneer Kit because it sounded like you needed to do some software, and it's generally easier to get that working on a tried-and-true development board first, and then port the working code over to your own design.  As far as making your PC board, I would suggest starting with FreeSoC since it's open hardware with published schematics and layout.  You can then omit what you don't need and add other things that you do.

     

    I don't know what to suggest about how to read a data sheet.  I learned how to read data sheets as part of an undergrad ECE degree.  Data sheets are designed to provide data quickly to experienced engineers who know what they're looking for, so there's a steep learning curve for newbies.  In this case I'm talking about electrical data sheets which specify voltages, currents, and timing.  There are also technical reference manuals which describe the functionality of chips.  They're sometimes also called "data sheets", even if they're 1000 pages long.

     

    There are probably EE books out there that talk about reading data sheets, but it's been so long since I taught EE that I wouldn't be able to make a decent recommendation.

  • in reply to johnbeetem

    Good idea. I have the PSoC 5 development kit and have working software I'd like to port to my own PSoC 5 board. I not too familiar with PCB design which is why I'm asking for all this guidance. I'll take a look at how the FreeSoC was done and go from there. Also, one other question. Are the PSoC 3 and PSoC 5 microcontrollers the same? For example, can I follow the same traces for USB connections on the PSoC 3 and just replace the PSoC 3 microcontroller with a PSoC 5 microcontroller?

  • in reply to Former Member

    Hi Justin,

     

    By traces, do you mean schematic? After you've worked with the dev kit as John Beetem has explained (it is the most valuable resource to proving the code and hardware design), prepare a schematic, and use the development kit documentation (circuit diagram) and the datasheets for a reference. There is no getting away from the datasheets, regardless of the dev kit documentation. I too can't recommend any book specifically for this, some of it is just through practise that you'll begin to know what topics to expect in datasheets and to follow any advice in the datasheet strongly.

    Usually after that it is very advisable to inspect the gerber files of the reference design/dev kit (if available)to study them as a reference to identify any areas of your eventual PCB layout that you need to pay close attention to.

    Also, if you're new to PCB design, don't forget mechanical considerations like screw-holes :-)

Reply
  • in reply to Former Member

    Hi Justin,

     

    By traces, do you mean schematic? After you've worked with the dev kit as John Beetem has explained (it is the most valuable resource to proving the code and hardware design), prepare a schematic, and use the development kit documentation (circuit diagram) and the datasheets for a reference. There is no getting away from the datasheets, regardless of the dev kit documentation. I too can't recommend any book specifically for this, some of it is just through practise that you'll begin to know what topics to expect in datasheets and to follow any advice in the datasheet strongly.

    Usually after that it is very advisable to inspect the gerber files of the reference design/dev kit (if available)to study them as a reference to identify any areas of your eventual PCB layout that you need to pay close attention to.

    Also, if you're new to PCB design, don't forget mechanical considerations like screw-holes :-)

Children
No Data