Closed mamin27 closed 1 year ago
Is the device address of the mv64xxxx chip 0x30?
Not sure if there is a driver for mv64xxxx on your system,It looks like it is not enabled.
In your kernel I detected in case of H616 GPIO settings big differences towards current kernel version: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi
I2C port description is changed now.
Is there any way how to update/replace kernel version in your project?
Here is also some advice to fix i2c and gpio issues: https://github.com/orangepi-xunlong/orangepi-build/tree/main/external/packages/pack-uboot/sun50iw9/bin/dts
I do not quite understand what you mean, my kernel is modified on the basis of the kernel of Orange Pie: https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.16-sunxi64
You can refer to the original kernel section on i2c.
If you want to replace the kernel version, you can just replace the whole kernel folder, but I don't guarantee that it will compile.
https://forum.mangopi.org/t/enable-i2c-and-spi/2079/4
I2C is working now.
I work at MangoPI with H616 processor. I installed there debian (11.6 version).
something is active there and listening at I2C network
I add modprobe file that is running with mv64xxxx chip, swith clock frequency to
fast mode
400khzsome gpio test
I would like to activate I2C pins at GPIO port and test it. I have tested I2C IC's at RPI Zero and now I would like to run it also at MangoPi.
Could you give me some advice?