Closed dirkbeer closed 2 weeks ago
@dirkbeer Thanks for the PR! With this changes the AXP192 won't be supported any more. That's not what we want to achieve, we want backward compatibility. We need a device agnostic approach, e.g. detect chip at first, then select appropriate chip driver.
Understood. If I find some time, I'll work on a better implementation.
@cyberman54 I do have boards with the AXP2101 and the previous AXP192.
Not sure yet if we can detect it properly at boot, but would it also be OK if we added a new board definition for the 1.2 revision? Then the defines can be set to either add code for the AXP192 or the AXP2101.
Sure! You're welcome to create a PR on this. I assume chiptype should be identifyable by the used Xpowers library.
I will look into this, but I will create my own PR for it, so you can keep this one closed I guess :)
Also I am struggling with the AXP192 on the T-beam 1.0, but will open another issue about it.
I'm not a programmer, but this does get the T-Beam with the new AXP2101 working. It senses devices and successfully uplinks packets to Helium. There are probably some functions that are not yet working correctly.