fancy T-Deck / SenseCAP Indicator / unPhone / PICOmputer-S3 TFT screen #3259
Conversation
|
|
caveman99
force-pushed
the
tft-gui-work
branch
from
d14151e
to
dcc11ff
Compare
mverch67
force-pushed
the
tft-gui-work
branch
9 times, most recently
from
2084055
to
d69edc2
Compare
mverch67
force-pushed
the
tft-gui-work
branch
2 times, most recently
from
b8a74c6
to
7dfeedc
Compare
mverch67
changed the title
|
Is possible to test on PICOmputer S3 ? I can send sample hardware. |
To Germany? Good. I can support it when I have the actual hardware available. |
worldwide, Germany is almost a neighbor, I'm from Slovakia. Picomputer use direct gpio matrix keyboard implemented by @caveman99 cpu is bpi-PicoW-S3 + RFM95 send my your postage address to [email protected] |
|
I am on the road right now but iirc the picomputer does only have 4MB flash. May be a tight fit. The TFT tracksenger may be a better fit. 8 MB is the min for an integrated device I would think. @mverch I have a picomputer prototype I can send you. Assuming @bobricius doesn't have a newer revision :-) |
|
I ma not sure but on product page is:
|
That's also what I read on the ALI-Express page for the Banana-Pi. Should be fine. https://github.com/meshtastic/firmware/blob/tft-gui-work/boards/bpi_picow_esp32_s3.json#L28 |
caveman99
added
linux-native
…into tft-gui-work
|
@mverch67 Thanks for all your work on this. Was wondering if there could be an update on the most recent build artifacts? I have several t-decks and while I realize this is still very alpha and technically not supported I would very much like to experiment with this unfortunately trying to dig out newer build artifacts I have been unable to successfully flash this on any of my t-decks and get anything other than a black screen. The build artifacts I could find don't seem to have a matching release as I understand you need to flash a matching release first then this into the other slot; that being said I'm only going off what I have read elsewhere. Is it possible to get an update with some links to some recent artifacts that can be flashed onto the t-deck? Alternatively I do have a development environment setup for meshtastic so should I just attempt to compile this from there? Mainly looking for some direction on how to get the most recent version of this onto one of my t-decks to experiment with as mentioned. Again appreciate all your hard work here. |
|
There are no artifacts on purpose.
Just download the build environment and check out the latest commits to
test. That is The Way(tm) and it prevents people from overwhelming GitHub
with issues before there is a real Beta that’s ready.
…On Thu, Nov 7, 2024 at 10:42 AM Zachary Patten ***@***.***> wrote:
@mverch67 <https://github.com/mverch67> Thanks for all your work on this.
Was wondering if there could be an update on the most recent build
artifacts? I have several t-decks and while I realize this is still very
alpha and technically not supported I would very much like to experiment
with this unfortunately trying to dig out newer build artifacts I have been
unable to successfully flash this on any device and get anything other than
a black screen.
The build artifacts I could find don't seem to have a matching release as
I understand you need to flash a matching release first then this into the
other slot; that being said I'm only going off what I have read elsewhere.
Is it possible to get an update with some links to some recent artifacts
that can be flashed onto the t-deck? Alternatively I do have a development
environment setup for meshtastic so should I just attempt to compile this
from there?
Mainly looking for some direction on how to get the most recent version of
this onto one of my t-decks to experiment with as mentioned. Again
appreciate all your hard work here.
—
Reply to this email directly, view it on GitHub
<#3259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5KKIU46LSPPMFDDADWQ3Z7OYBHAVCNFSM6AAAAABDTUZSNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRSHE3DSMJRGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
@martinbogo Awesome thanks, I had a feeling; definitely don't want to be creating issues here around this since it's so early. I already have a meshtastic dev environment setup so shouldn't be an issue. Was my understanding correct that you need two copies of the firmware (a base image and the fancy ui) to flash based on the other instructions I've read or is that incorrect? |
|
It will flash directly using the build tools in VSCode … but the
ui/interface is far from ready for daily driving.
It also disables Bluetooth, as the mechanism the UI uses requires the same
resource to render the interface.
…On Thu, Nov 7, 2024 at 10:48 AM Zachary Patten ***@***.***> wrote:
@martinbogo <https://github.com/martinbogo> Awesome thanks, I had a
feeling; definitely don't want to be creating issues here around this since
it's so early. I already have a meshtastic dev environment setup so
shouldn't be an issue. Was my understanding correct that you need two
copies of the firmware (a base image and the fancy ui) to flash based on
the other instructions I've read or is that incorrect?
—
Reply to this email directly, view it on GitHub
<#3259 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5KKMGYB5GQAUEXHI6K6LZ7OYXTAVCNFSM6AAAAABDTUZSNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRSHE4DAMJVGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Awesome, thanks for the clarification! I'm aware of the Bluetooth and some of the other issues. Just wanting to experiment. I have other devices dedicated to daily driving. |
nothing to see here, yet. Work in progress
Download firmware-2.5.4.dbf46f8.zip. This artifact will be available for 90 days from creation