It should be a an I2C Controller than can perform a single byte write. Compensation may be considered
Guest
#3104545
Tell us, what you already know and have. How far are you with your current code? What is the problem in detail?
Guest
#3104558
Do you have to write it on your own? Otherwise have a look at: http://opencores.org/project,i2c
Joe Daddy wrote: > It should be a an I2C Controller than can perform a single byte write. I have one written in Assembler, runing on a NEC uPD78017663A. Will that be ok?
1 | |
2 | |
3 | |
4 | |
5 | |
6 | |
7 | |
8 | |
9 | |
10 | |
11 | |
12 | |
13 | |
14 | |
15 | |
16 | |
17 | |
18 | |
19 | |
20 | |
21 | |
22 | |
23 | |
24 | |
25 | |
26 | |
27 | |
28 | |
29 | |
30 | |
31 | |
32 | |
33 | |
34 | |
35 | |
36 | |
37 | |
38 | |
39 | |
40 | |
41 | |
42 | |
43 | |
44 | |
45 | |
46 | |
47 | |
48 | |
49 | |
50 | |
51 | |
52 | |
53 | |
54 | |
55 | |
56 | |
57 | |
58 | |
59 | |
60 | |
61 | |
62 | |
63 | |
64 | |
65 | |
66 | |
67 | |
68 | |
69 | |
70 | |
71 | |
72 | |
The above code is what I have so far. I know it is incomplete, but I need the I2c to perform a single byte write and a single byte read. At this point I am confused on where to go from here.
Guest
#3112018
Do you have a testbench? Without testbench simulation is not possible. Test on hardware Without simulation is like Russian roulette... Duke
Guest
#3112851
>Russian roulette...
You mean, we all can die from a bad coding?
I have a question about this subject: Does anybody know about I2C
patents a license issues? I recently was told I2C was under protection
and has to b licensed for commercial use.
Guest
#3112867
Atmel showed how to bypass the License, just call it twi :-)
I am willing to compensate anyone who is willing to assist me
Guest
#3128602
Do you have a requirement SPEC? Hourly Rates for such projects are around €60,-
Guest
#3128628
Hi, I've got an i2c single master-only engine ready, but it kinda requires a soft CPU to be useful. Basically it is a module of a System on Chip design. Example access (from the soft CPU core firmware):
1 | |
2 | |
3 | |
4 | |
5 | |
6 | |
7 | |
8 | |
9 | |
10 | |
11 | |
12 | |
13 | |
14 | |
15 | |
16 | |
17 | |
18 | |
In order to draft some pecuniary house numbers of the support expenses, you might have to post more about the requirements (what HW it should support, what soft core you'd be using, etc. ) BTW: No need to worry about any licensing issues, the patent has expired a while ago. Greetings, Butze
To Fitzebutze, Can you send me an email to paparit432@yahoo.com? I wanna discuss the I2C controller further in depth and I also want to send you additional documents regarding this as well?
Tom wrote: > Do you have a requirement SPEC? > Hourly Rates for such projects are around €60,- Yes. Send me a personal message @ paparit432@yahoo.com and we can talk further.
Guest
#3152069
is this project still open? i could provide you with a working scalable iwc controller offering a dynamic number of inputs and outputs configurable by genererics, data is stored in brams it comes complete with testbench and implementation example for both xilinx and altera devices
fpgaengineer wrote: > is this project still open? i could provide you with a working scalable > iwc controller offering a dynamic number of inputs and outputs > configurable by genererics, data is stored in brams > > it comes complete with testbench and implementation example for both > xilinx and altera devices Please email me at paparit432@yahoo.com
Guest
#3186136
You want to pay for a simple i2C? For a fex lines of code? Why not using OS?
Guest
#3313833
Hello there, Can you tell me why the divider in the code is set to "(input_clk/bus_clk)/4".
Guest
#3332915
because it takes various operarion frequencies into account
Reply
Please log in before posting.