I2C Slave with a PIC

[Archangel]

Thanks for the update! This should be a hot topic now!

Btw, how many times I have seen this topic on the forum without any answers because: "my code that works is proprietary and I cannot share it"

Translation: My code does not work, but I won't admit it. At least 50% of the time <br> Anyway thanks Daniel and AL, Ralf , mister_e, Big Wumpus Something new to play with.

[aratti]

Translation: My code does not work, but I won't admit it. At least 50% of the time

Interesting assumption Joe.

Al.

[Archangel]

Interesting assumption Joe.

Al.

I mean it in context, sure there some very good professional coders in here, and when they say it I am sure it is true, now for a majority here, who likely are hobbyist, maybe some of which wish to make the jump with their own stellar idea, 50 / 50 is likely a generous assumption. And so what? EGO has value only to the person who owns it.<br>EDIT: Ego has value to anyone who wants to exert control over someone who has it too.

[ralfmayr]

Hi there,
i will test the code from Aretti soon on a PIC18F2431. I want to process four ad-converters and several digital io's. The slave address of the PIC is automatically detected when pluging it on a bus-system (16 addresses).
When it is finished and working (hope so), i will post it here.
FYI: I2C Apps from MCHIP seems not to work, a friend of me in an other company also tried this code to implement, no chance.
All others syaing "i can't post my working code here" must be sayed, that these people are wrong here, a forum lives from shared ideas, code snippets.... they should keep out here and keep their code for them selves.

Regards,
Ralf

[Charles Linquis]

I will be interested in your port to the 18F series, and it sounds like you will be willing to post your code. I have an upcoming project that will need it. I tried to get Soubie's code working about a year ago with no luck.

[ralfmayr]

Charles,
same problem, i also never got his code working.
I come back next week, hope with a working code.
Regards,
Ralf

[rswain]

Guys,

I've been working this problem for nearly a year now. I've tried Soubie's code with no luck, and the code from this thread isn't working either. I'm using the 18F4620 as the master talking to an 18F2620, the little brother of the 4620 as the slave. I've RTFM to the point I can recite it, and the Errata sheets, and I've tried countless logical, and even illogical options to trying to get it working.

The best I can get so far is the master sends the address byte and the slave accepts it when it matches its own address and ignores addresses not matching its own. When the address matches, the slave sets the Buffer Full and the Interrupt Flags, but for some reason won't send an ACK back to the master (at least that's what this thread's code [and my own polls of the master's ACK flag] are saying). I've made sure to clear all flags as the datasheet clearly directs, and still no luck. If the slave would ACK, the master would send the next byte and so on.

I'm operating both chips on their internal crystal (8 MHz) and using the 4x PLL (= 32MHz). Before you go there, I'm already successfully talking to an I2C real-time clock chip with no problems and I'm saving data to an external I2C EEPROM regularly with no problems. The I2C network is working with the PICs at 32 MHz. I'm on the right pins; I'm using the pull external pull-up resistors...

I've had this exact hardware working in the past when using MikroElektronika Basic, but I'm much happier in PBP. This one problem is holding up the entire project. Trying to get two 18F's to ping-pong data back and forth is a killer.

If someone has even a bit more success than what I've had, please post it and maybe together we can chip away at this challenge.