Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Clock generator in psoc by using verilog

Status
Not open for further replies.

jasi

Newbie level 5
Joined
Jan 23, 2018
Messages
8
Helped
0
Reputation
0
Reaction score
0
Trophy points
1
Activity points
74
hello everyone
Iam using PSOC . PSOC board support verilog. i wanted to implement clock generator in this board. anyone please help me .how to implement this .
 

"Clock generator" is a very general description. What do you want to achieve?
 

i wanted to implement i2c communication with psoc by using verilog . As a part of this i wanted to generate SCL clocks signal . i know SCL timing diagram and also what changes happened to reading and writing operation on SCL . how to implement SCL signals by using this data . If anyone knows logic please give me idea .
 

Hi,

Your PSOC has an input clock.

All you need is a counter to generate an "enable" signal to control a toggle FF .... it's output is the SCL.
There is more than plenty of code in the internet on how to do this.

Also - I'm sure - there are complete I2C codes available.
*****

You have to consider if you want to implement "SCL stretching by an I2C slave".
This is a bit more complicated, because you need to take care about the true SCL state of the bus
..and you need to consider how to timeout this situation.

Klaus
 

An I2C interface implemented in programmable logic will usually generate all required timings by dividing down the system clock, creating clock enables with specific rate.

Can you mention the used PSoC device to give us an idea of the available logic resources?
 

Iam using psoc 3 .
 

Iam using psoc 3 .

Afaik, the PSOC3 is a registered trademark belonging to Cypress, composed of a CPU and a SOC (analog+digital) on the same chip, and in this architecture - based on the core 51 - already has an I2C peripheral built into the CPU itself, no need to waste extra resources on that. Considering that this is a bus that can be shared among devices, are you sure you're really needing another I2C interface ?
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top