I probably need to file this bug with rppal, but I'll post it here in case anyone else runs into it...
I've got a system that runs the Debian kernel as opposed to raspbian kernel, and after probing i2c-dev and i2c-bcm2835, the pisugar 2 pro is on i2c-3 and not i2c-0 or i2c-1 like is expected.
What I had to do was fork the rppal repo, and modify the line that sets the bus from 1 to 3, and then modified the pisugar-core cargo toml to point to my local checkout that has the info in there. Once I did this, I was able to use the manager correctly.
I probably need to file this bug with rppal, but I'll post it here in case anyone else runs into it...
I've got a system that runs the Debian kernel as opposed to raspbian kernel, and after probing i2c-dev and i2c-bcm2835, the pisugar 2 pro is on i2c-3 and not i2c-0 or i2c-1 like is expected.
What I had to do was fork the rppal repo, and modify the line that sets the bus from 1 to 3, and then modified the pisugar-core cargo toml to point to my local checkout that has the info in there. Once I did this, I was able to use the manager correctly.