Search found 32 matches

I finalized this routine, just need to clean up from my application and working very well on both processors. It is finally different and based on MC. Just please give me 1-2 days to deliver the proj ...

Hi,
I wrote new I2C handler that is working with all (bad and good) hardware
Will release to publicity tomorrow. It is universal for any 24 version

I made finally procedure that is working fine for a read/write on both processors types

sudo i2cget -y 1 0x69 0x04
return 0x05

and after
sudo i2cset -y 1 0x69 0x04 0xaa
return 0xaa

/*
...

No way with CCS, and the worst is that I d not know why.
So implementing the Microchip handler, where at least I can read values via I2C.
Now implementing the writing, also.

/////////////////// ...

same results (even worst - as also the first byte is wrong)
with

#use delay(internal=4MHz, AUX:crystal=32768Hz, clock=32768Hz)
or
#use delay(internal=8MHz, AUX:crystal=3276 ...

Hi,
I ran the same software on both PCBs (first on the good processor, and then on the bad processor) with different results
See below what I ran

Clock setup

#use delay(internal=32MHz, A ...

yesss

Yes, the ID is the same on both batches 0x750B
If we use the CCS library, always the first read is proper after reset. ALWAYS.
Each next reading is damaged. In example first read is 0x4e, next is 0x ...

Hi,
I already corrected it in the mean time, but still not working. More specifically working in the former micro controller without any problem (both versions) and NOT working on the new batch.
Act ...

Can you please explain what do you mean with

First thing, what you post is very flawed. You are holding the bus when
it should not be held, and releasing it when it should be held.

This is work ...

I modified your function to 8bit
however the results are the same

pi@rpi:~ $ sudo i2cget -y 1 0x69 0x38
0x4e
pi@rpi:~ $ sudo i2cget -y 1 0x69 0x38
0x02
pi@rpi:~ $ sudo i2cget -y ...

Hi,
My answer is in the text

First thing, what you post is very flawed. You are holding the bus when
it should not be held, and releasing it when it should be held.

What do you mean, I followe ...

Hi,
I made a PCB based on the PIC24FJ128GA705 using I2C that is working with Raspberry Pi. We manufactured some hundreds of them and working perfectly. New production we done, used the same PIC24FJ12 ...

In the i2c in theory we do not need to care about that. This is because we have open drain I/O ins SDA and SCL, and that is the reason we are using pull up resistors that must be pulled up to "ot ...

I release this simple code tomorrow, now in hurry to send system to manufacture PCB, and then assembly. The original library sent from CCS can not share as it is under CCS license, so I will write my ...