I2C Expansion Board

[martinayotte]

Hi,
This is the schematic  for the i2c POT board.

Thanks !
That clarify why other pins were also initialized with pullups, they are the interrupts.

[martinayotte]

I think I've succeed to place new DTS entries for S_TWI (PL8/PL9), it is now appearing as /dev/i2c-3 as I've prescribed in an DTS alias.
The only thing is that I didn't test with some hardware yet, I'm usually using TWI0 (/dev/i2c-0).
I will probably try tomorrow using dupont jumpers and will post back.

Unfortunately, false victory, at least until now.
The SoC does'nt seem to communicate on the pins, although no complain in dmesg, not even seeing their pullups, "i2cdetect -y 3" still choking.
I'm running out of ideas...

[xalius]

Do you have your changes to the dts on github?

[khgoh]

Hi,
This is the schematic  for the i2c POT board.

Thanks for sharing. Hoping this can be added to the wiki for easy reference (along with the other POT device schematics....).

Just put it up in the wiki at http://wiki.pine64.org/index.php/POT#POT...PMI2C01.29

[martinayotte]

Do you have your changes to the dts on github?

No, I'm usually doing commit only and things are working and are ready for PR.

So, here is a gist snippet instead :

https://gist.github.com/martinayotte/145...e53ecc2b84

[xalius]

Do you have your changes to the dts on github?

No, I'm usually doing commit only and things are working and are ready for PR.

So, here is a gist snippet instead :

https://gist.github.com/martinayotte/145...e53ecc2b84

Thanks, that is about as far as I got in my attempts too... but I could not figure out how to set the interrupts =.... attribute, can you help me out there? I wonder if those devices in the CPUS domain need any special configuration?

[martinayotte]

For interrupt, following the specs sheet, it was pretty easy to determine that the s_twi is 0x2c (76 in the specs, but offsetted by 32) since the s_uart is 0x26 (70 in specs) (except if the previous offsetting is wrong), maybe I should try to get rid of this offset which I don't know where it is coming from.
Problem can also be from clock and reset, which are not using apb0_gates/apb0_reset like other sunxi such H3 where the I2C on i2c@01f02400 is working.
I hate this PineA64 DTS since it is coming from a decompiled version from AllWinner and doesn't follow rules used in Mainline, where apb0_gates/apb0_reset doesn't even exist.

EDIT: I've checked the interrupt on H3, and it is really 0x2C (76 with offset of 32). Som it must be something else, the clock or the reset.

[Artyom]

Hi. About latest version IDE CodeBlocks. http://forum.pine64.org/showthread.php?tid=1896 This is the first test version of the manual writing in two languages. If you have any comments and suggestions please send them to me by e-mail blademoon@yandex.ru. I sincerely hope that it will help you.

[tllim]

Hi. About latest version IDE CodeBlocks. http://forum.pine64.org/showthread.php?tid=1896 This is the first test version of the manual writing in two languages. If you have any comments and suggestions please send them to me by e-mail blademoon@yandex.ru.  I sincerely hope that it will help you.

Thanks on the IDE CodeBlocks..

[AndrewC78]

Gentlemen,

Could you please guide me taking the below info into account?

# ./enable_i2c_pullup
I/O Port for Pine64 I2c POT pull up enabled.

# sudo i2cdetect -l
i2c-1 i2c      mv64xxx_i2c adapter            I2C adapter
i2c-0 i2c      DesignWare HDMI                I2C adapter


# i2cdetect -y 0
    0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --                       


# i2cdetect -y 1
    0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --                        


I've got an impression the second read isn't effective.