Device request

[my-project-droid]

Describe the Bug & Scope

Currently, Rogue Radar is compiled strictly for the original, non-CC1101 LilyGo T-Embed layout. Because community M5Launcher repositories frequently list this firmware under multiple hardware categories, users flashing this binary on alternative ESP32-S3 / ESP32 form factors experience immediate black screens, bootloops, or system panics due to conflicting GPIO assignments and mismatched display SPI pin configurations.

To expand Rogue Radar's community reach and stop accidental "bricking" experiences on M5Launcher, we request adding native pinout/build compilation targets for three major alternative platforms:

1. LilyGo T-Embed CC1101 Variant
2. LilyGo T-Watch 2020 v3
3. M5Stack Cardputer ADV

---

Hardware Pin Mapping Requirements

1. LilyGo T-Embed CC1101 Variant

The sub-GHz variant shifts vital display and backlight controls away from the original T-Embed pins to accommodate the radio lines:

• TFT_MOSI: GPIO 3 (was 11)
• TFT_SCLK: GPIO 5 (was 12)
• TFT_CS: GPIO 46 (was 10)
• TFT_DC: GPIO 47 (was 9)
• TFT_RST: GPIO 6 (was 13)
• TFT_BL: GPIO 7 (was 15)
  (Note: Center encoder controls on pins 0, 1, and 2 remain unchanged).

2. LilyGo T-Watch 2020 v3

This wearable relies on an older ESP32 architecture (ESP32-D0WDQ6-V3) with an integrated AXP202 Power Management Unit (PMU) and an ST7789 display running at 240x240 pixels. Flashing the S3 T-Embed build here causes catastrophic architecture mismatches. A dedicated build definition targeting this standard ESP32 core is required.

3. M5Stack Cardputer ADV

Powered by the M5Stamp-S3A, this variant introduces a vastly reworked architecture compared to the original Cardputer. It swaps the old 74HC138 keyboard multiplexer for a dedicated TCA8418RTWR I2C Keyboard Expander chip. Running stock code causes keyboard mapping crashes. It features an ST7789V2 240x135 display and completely different SPI/Backlight pin paths.

---

Feature Roadmap: Maximizing Specialized On-Board Hardware

Adding compile targets for these devices unlocks unique, offensive security capabilities by leveraging their on-board modules:

📡 LilyGo T-Embed CC1101 Capabilities

• CC1101 Sub-GHz Transceiver: Expands Rogue Radar past Wi-Fi tracking into capturing, sniffing, and replaying sub-GHz frequencies. Useful for targeting garage doors, gate remotes, and wireless IoT sensors.
• PN532 NFC Module: Grants native RFID and contactless badge access. Useful for reading, writing, and emulating 13.56MHz NFC badges, hospitality key cards, and key fobs.
• IR Transceiver: Adds a stealthy universal remote control layer to brute-force TV power states or interact with line-of-sight electronic appliances.

⌚ LilyGo T-Watch 2020 v3 Capabilities

• BMA423 3-Axis Accelerometer: Enables motion-activated tracking toggles or tilt-to-scroll navigation gestures for covert operations.
• AXP202 PMU & RTC Chip: Provides highly optimized sleep cycles and precise, real-time logging of captured Wi-Fi handshake events without network syncing.
• Infrared Signal Transmitter: Turns the watch into a wrist-wearable universal TV/appliance disruptor.

📟 M5Stack Cardputer ADV Capabilities

• EXT 2.54-14P Expansion Bus & HY2.0-4P Grove Port: Makes attaching external custom hacking modules (like NRF24 or GPS modules) plug-and-play without messing with the micro SD slot.
• 56-Key Keyboard (Matrix/I2C via TCA8418): Provides a robust physical shell for entering custom text inputs, typing custom Wi-Fi deauth payloads, or configuring target filters on-the-fly.
• BMI270 6-Axis Motion Sensor: Can act as an anti-tamper trigger, shutting down or wiping temporary radar logs if the hardware pocket computer is aggressively moved or dropped.

Conclusion

Implementing a conditional hardware build matrix (via #ifdef build flags or PlatformIO environment profiles) will immediately turn Rogue Radar into a highly flexible, multi-platform pentesting framework while completely resolving the M5Launcher flashing dilemma.