feat: add GAT562 Mesh Trial Tracker device

[hayschan]

Add support for the GAT562 Mesh Trial Tracker device with nrf52840 architecture and support level 2.

This matches the support of the firmware addition meshtastic/firmware#6984 and the protobuf addition meshtastic/protobufs#699 .

[vercel]

@hayschan is attempting to deploy a commit to the Meshtastic Team on Vercel.

A member of the Team first needs to authorize it.

[hayschan]

Ben, is there anything that I should modify?

@thebentern

[foo-mr]

GAT562 still not deployed on web flasher?

[hayschan]

GAT562 still not deployed on web flasher?

Not yet. This PR has not been merged by the Meshtastic team yet.

[fifieldt]

I am seeing many instances of firmware files being passed around on Facebook because this device isn't in the flasher

[hayschan]

Ben, is there anything that I should modify?

@thebentern

Hi Ben and Tom,

This PR for adding GAT562 support to the web flasher has been open for nearly a month without any updates. I just wanted to check in—are there any modifications or changes needed from my side to help move it forward?

In the MeshCN community group chat, sharing .uf2 files for GAT562 has become a daily routine. This is something that could be streamlined greatly by simply integrating GAT562 into the official web flasher. I truly enjoy contributing to open source, and I’d much rather improve the official Meshtastic tools than create a fork—though that’s something more and more members are now suggesting just to meet the demand.

If there’s anything I can help with or change to get this merged, just let me know. I’m happy to assist however I can.

@fifieldt Tom, the Shenzhen event last month, hosted by Seeed Studio, was incredible. The room was packed with hobbyists, HAMs, and LoRa industry folks, software and hardware guys. Everyone loved the speeches from Didier, Manuel, and myself—so many great ideas were exchanged and three hours barely scratched the surface! Wish you could’ve been there, Tom ❤️

[thebentern]

Hi @hayschan, I believe @Kongduino is meeting soon to discuss the prospect of full support of this device in the meshtastic ecosystem. We added some new policies recently to the assignment of new HW_MODELs (which the GAT562 already has) and web-flasher distribution.

New Hardware Model Acceptance Policy

Due to limited availability and ongoing support, new Hardware Models will only be accepted from Meshtastic Backers and Partners. The Meshtastic team reserves the right to make exceptions to this policy.

Alternative for Community Contributors

You are welcome to use one of the existing DIY hardware models in your PlatformIO environment and create a pull request in the firmware project. Please note the following conditions:

• The device will not be officially supported by the core Meshtastic team.
• The device will not appear in the Web Flasher or Github release assets.
• You will be responsible for ongoing maintenance and support.
• Community-contributed / DIY hardware models are considered experimental and will likely have limited or no testing.

Getting Official Support

To have your hardware model officially supported and included in the Meshtastic ecosystem, consider becoming a Meshtastic Backer or Partner. Visit meshtastic.com for more information about partnership opportunities.

In terms of this proposed change, the resources.ts is generated from our API, so this pull request will only populate the board if the API is not acessible.