You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NRF52, ESP32, RP2040, Linux Native, Cross-Platform
Description
As a first step towards building customized firmware it would be good if we could start by disabling modules in the firmware and apps that are unsupportable on specific hardware.
The heltec wireless paper for example does not have pins that would make most GPIO related functionality work.
The text was updated successfully, but these errors were encountered:
You might as well forget the Heltec V3 altogether.
It's unusable.
There are an utterly ludicrously large number of bugs in the Heltec firmware and in client.mestastic.org on Chrome.
it's as good as impossible to get recent versions of the firmware to work at all.
@garthvh A lot defines are already available for excluding modules at compile time - assume what is needed is code changes to signify to the phone apps what modules are/are not compiled in when connecting to the node and gathering module configs.
Platform
NRF52, ESP32, RP2040, Linux Native, Cross-Platform
Description
As a first step towards building customized firmware it would be good if we could start by disabling modules in the firmware and apps that are unsupportable on specific hardware.
The heltec wireless paper for example does not have pins that would make most GPIO related functionality work.
The text was updated successfully, but these errors were encountered: