-
-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardware support for T-Beam V1.2 with AXP2101 #990
Comments
Can you provide link to specs of v1.2 |
In all your links, i can't find a schematic or specs for v1.2, it all renders as v1.1? |
@XAct-6510 i checked the Xpowerslib example, and found that there is some refactoring of power.cpp needed. Could you do this, and make a PR? |
Unfortunately I'm not a programmer, I'm a networking guy... But I can provide you one of my 5 T-Beam V1.2 if that helps. |
@XAct-6510 not necessary, because if i would code it, you could test it on your board. But currently i have no time to code this. |
As mentioned I'm not a programmer, but maybe this can be used? |
i saw that, but would stick to the example code of XPowersLib, because Meshtastic has more complexity. But again, you or someone else would be welcome to show up with a completely refactored power.cpp |
Just for completeness, the schematics of the 1.2 version of the T-beam: Also they split off the older boards, so here are all the LilyGo LoRa series schematics: |
Anybody had a change to look at this guys? |
I am looking into this. I have both versions here on my desk, but since those T-beam boards are quite expensive these days, I wanted to make sure I knew how it all should work. |
@TD-er I could do some testing. Received a T-Beam "Supreme" with AXP2101 this week. I finalized a hal file with matching pinout already, build paxcounter code for S3 and flashed it successfully on the T-Supreme. The board seems to be alive, because i can see the USB port triggers on reset. But nothing else happenes. Probably becaue AXP2101 is missing proper initialization, thus the board components are probably not powered. |
I have been reading into the existing libraries. Still I'm puzzling a bit on how to make this as fool proof as possible as wrong settings for power chips like these can for sure ruin your device or stuff connected to it. The last 2 weeks have been extremely unproductive for me, as apparently Covid is still lurking around and even though I've had it 3 times already, it still hits you every time. |
Support for T-Beam v1.2 is now implemented in branch feature-asp2101 Does anyone who reads this own this board, and could test, please? Thanks. |
For those willing to test, please double or triple check these lines first: |
Can't get it to work yet - after flashing the new build the device hangs on boot: rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT) |
Looks like the i2c bus did not initialize for some reason. Thus, there is no communication with the AXP2101 chip, so it does not power up all board circuits. |
I can reproduce this with a T-Beam with AXP192 chip and single i2c bus. |
i committed a hot fix, it should work (please re-test), but yet to be discussed if this is a straight forward approach for boards with two i2c buses. /cc @XAct-6510 |
I have applied the hotfix and it is now working. I'm still running some tests, but it seems to be running fine. |
Please add support for the new version of the Lilygo T-Beam V1.2 with the new power management chip AXP2101.
The text was updated successfully, but these errors were encountered: