I2CRead problem

[Ioannis]

Thank you Richard. Will do that this evening.

I tried byte read, word read, page read, Nothing works and all var's are just a zero.

The chip is a 16F1939 but I am sure this does not matter. Logic analyzer shows I2C activity either way.

Edit:

OK, now that is weird. On a 45K22 works just fine. On 1939 not...

Ioannis

[Ioannis]

I am very embarrassed...

I forgot completely ANSELD and ANSELE when testing it...

Ioannis

[richard]

I forgot completely ANSELD

Another good reason to migrate to xc8 , mcc gives all pin settings/names and function in one easy to use screen

[Ioannis]

It is not easy to me. I detest C lanquage. Despite my efforts so far, I did not managed to flip over.

It looks very cryptic...

Ioannis

[sayzer]

Using ready-to-use tools to adjust the registers as we need, kills our ability of playing with them, and lowers the understanding of the hardware registers.

Manual setting as much as possible is a good way of self developing, I think.

[richard]

Using ready-to-use tools to adjust the registers as we need, kills our ability of playing with them, and lowers the understanding of the hardware registers.

setting pin function is pic 101 stuff , but essential to get correct .not much programming skill in there once a basic understanding is reached

Manual setting as much as possible is a good way of self developing, I think.

would you not use dt_ints or PicMultiCalc
if there's a good tool use it ,I think

[Ioannis]

Fuses and the like are a pain. So many new options on the recent chips. I hate it as I loose too much time from the programming itself, on figuring out how to set up a new (or older) chip.

All these settings are getting more and more complex. A tool such as MCC is great but needs C understanding I suppose. Or maybe to that extend to get the fuses and then return to PBP?

Ioannis