ZillaStick S3 Firmware for M5Stack StickS3: Features, Setup & RF Pack S3 Guide
Partager
Quick answer: ZillaStick S3 is a community-developed firmware project by Hackazillarex for the M5Stack StickS3 (ESP32-S3). The project's source code and documentation explicitly reference the PINGEQUA RF Pack S3 v1, an expansion board that adds a CC1101-based 433 MHz radio and an nRF24L01+-based 2.4 GHz radio. This guide explains what the firmware does, what hardware you need, how to flash it, and what to check if a radio is not detected.
Last reviewed: November 6, 2026. ZillaStick S3 is an independent third-party project; it is not developed or maintained by PINGEQUA. References to support are based on its published documentation and source code, not an independent certification of every function.
What is ZillaStick S3?
ZillaStick S3 brings a collection of wireless observation, diagnostic and development tools to the compact M5Stack StickS3. The StickS3 contains an ESP32-S3 processor, an LCD, physical buttons, USB-C, built-in 2.4 GHz Wi-Fi and BLE. ZillaStick uses those onboard resources for its core interface and software features. External transceivers expand the available radio bands.
The firmware's author, Hackazillarex, publishes the ZillaStick S3 source repository and an official browser-based flasher. At the time of this review, the web-flasher manifest identifies the build as 1.0.0-beta; check the repository for changes before installing.
Watch ZillaStick S3 in action
See the community creator's short ZillaStick S3 demonstration. Video credit: Hackazillarex. The video is an external demonstration, not a test conducted or produced by PINGEQUA.
Can't play the embedded video? Watch the original YouTube Shorts demonstration.
ZillaStick S3 features: what uses the built-in radio, and what needs an RF Pack?
The distinction matters when selecting hardware: you do not need an RF expansion board for every ZillaStick feature. However, CC1101 and nRF24 features require their respective external transceivers.
| Feature area | Radio or interface | RF Pack S3 needed? |
|---|---|---|
| Wi-Fi network discovery and diagnostics | StickS3 onboard ESP32-S3 Wi-Fi | No |
| BLE device discovery | StickS3 onboard BLE | No |
| Browser-based remote interface | StickS3 Wi-Fi | No |
| USB HID experiments | StickS3 USB interface | No |
| 433 MHz signal monitoring and RF capture workflows | External CC1101 | Yes |
| 2.4 GHz nRF channel activity scanning | External nRF24L01+ | Yes |
| nRF24 packet-reception experiments | External nRF24L01+ | Yes |
The original project also contains active security-testing tools. Only use any transmission or security-testing function in an environment you own or are expressly authorized to test, and comply with local spectrum regulations.
What hardware do you need for ZillaStick S3?
For the full dual-radio hardware configuration documented in the project, use:
- M5Stack StickS3 — the ESP32-S3 host with display and controls.
- PINGEQUA RF Pack S3 v1 — the dedicated expansion board combining CC1101 433 MHz and nRF24L01+ 2.4 GHz radios.
- Appropriate antennas — a 433 MHz antenna for the CC1101 connector and a 2.4 GHz antenna for the nRF24 connector. The PINGEQUA product listing specifies both antennas in the package.
- USB-C data cable and a supported desktop browser — for the firmware flasher.

The PINGEQUA RF Pack S3 for M5Stack StickS3 is a purpose-built module rather than a pair of breakout boards connected with jumper wires. Its published hardware design includes a four-layer PCB, SN74 logic buffering, supply filtering, dedicated StickS3 form factor and two SMA antenna connections. See the PINGEQUA RF Pack S3 hardware guide for installation and troubleshooting details.
Important frequency limitation: the current RF Pack S3 v1 configuration uses a 433 MHz RF front end for the CC1101. The fact that a CC1101 chip can be configured to other frequencies does not mean this particular assembled module has equivalent 315, 868 or 915 MHz RF performance. Check the band-specific hardware before planning experiments outside 433 MHz.
View the PINGEQUA RF Pack S3 hardware and specifications →
ZillaStick S3 pinout for PINGEQUA RF Pack S3 v1
One unusually useful detail is that ZillaStick's actual source code contains the PINGEQUA RF Pack S3 v1 GPIO mapping. In src/globals.h, the project defines the following connections:
| Signal | StickS3 GPIO |
|---|---|
| SPI SCK | 5 |
| SPI MISO | 4 |
| SPI MOSI | 6 |
| CC1101 chip select | 2 |
| CC1101 GDO0 | 3 |
| nRF24 CE | 1 |
| nRF24 chip select | 8 |
These values are firmware-defined pin assignments, not an invitation to wire arbitrary boards without confirming voltage, power and physical pin order. They demonstrate why board-specific firmware configuration matters.
Why shared SPI handling matters
The CC1101 and nRF24L01+ share SPI clock and data lines but use different control signals. ZillaStick's code explicitly manages radio initialization and de-initialization, including the CC1101 chip-select state, when switching modules. The radios are not intended to run as two independent simultaneous SPI activities in this firmware. This is a practical compatibility detail worth checking when troubleshooting either module.
How to install ZillaStick S3 firmware on M5Stack StickS3
The creator supplies a browser-based flasher, so typical users do not need to compile PlatformIO source code. Follow the author's up-to-date instructions rather than flashing a binary from an unverified mirror.
- Confirm your host device: use an M5Stack StickS3. The published project targets this device; do not assume it works on M5StickC Plus2, Cardputer or Cardputer ADV.
- Connect USB-C to the StickS3: use a cable that supports data, not a charge-only cable. The author's flashing instructions specify the USB-C port on the StickS3 itself.
- Open the official ZillaStick S3 Web Flasher: the project lists Chrome or Edge as supported browsers.
- Follow the on-screen flashing instructions: select the correct device/port, review the firmware information and proceed. Back up any data you need before replacing existing firmware.
- Connect the RF Pack S3: with power off, seat the expansion board correctly and attach the correct antenna to each port. Do not transmit with an RF output left unterminated.
- Verify both modules: after startup, check the firmware's CC1101 and nRF24 hardware detection and open their respective passive scan functions.
The author also documents a headless web-control interface accessed through Wi-Fi. If you enable it, review its default access settings and avoid exposing the management interface beyond a controlled lab environment.
CC1101 or nRF24 not detected? Troubleshooting checklist
1. Confirm the correct device and firmware
ZillaStick S3 is a separate firmware project, not Bruce. If you are using Bruce instead, follow the PINGEQUA Bruce-specific firmware guidance; do not mix Bruce menu paths and version requirements with ZillaStick instructions.
2. Check mechanical connection and power
Power down the StickS3, verify the expansion connector is fully seated, and make sure the board is not displaced or shorting against another component. If the device restarts during RF use, consider cable power, battery state and peripheral load.
3. Check the expected GPIO and SPI mode
For the PINGEQUA RF Pack S3 v1, compare the GPIO table above to the currently installed firmware source. The firmware explicitly guards against SPI contention during CC1101/nRF24 switching; modifying both radio drivers without coordinating their bus state can introduce detection failures.
4. Confirm the antenna band
The 433 MHz CC1101 and 2.4 GHz nRF24 radio each require an appropriate antenna. Using an antenna designed for the wrong band can degrade RF performance even if the digital module initializes correctly.
5. Check project changes before reporting a bug
Because this is an independently maintained, recently published project, behavior may change between builds. For firmware-specific problems consult the ZillaStick S3 issue tracker. For RF Pack S3 physical hardware questions, see PINGEQUA support documentation.
ZillaStick S3 FAQ
Does ZillaStick S3 require the PINGEQUA RF Pack S3?
Not for onboard Wi-Fi, BLE or USB features. Its CC1101 Sub-GHz and nRF24L01+ 2.4 GHz radio functions require external hardware. The project's current source and documentation specifically reference PINGEQUA RF Pack S3 v1.
Which RF board is referenced in ZillaStick S3's source code?
PINGEQUA RF Pack S3 v1 is explicitly named in the repository's README, PlatformIO configuration and GPIO mapping. That is a documented project reference, not a claim of exclusive compatibility with all possible third-party boards.
Can I use ZillaStick S3 on M5StickC Plus2 or Cardputer?
The published build targets the M5Stack StickS3. Compatibility with those other devices has not been established in the reviewed project documentation.
Can the CC1101 and nRF24 radios work simultaneously?
They share an SPI bus. The reviewed firmware switches between radio modules and de-initializes the inactive radio; it does not promise independent simultaneous operation.
Does RF Pack S3 v1 provide optimized 868/915 MHz operation?
No such claim should be assumed. The product's assembled CC1101 radio path is specified for 433 MHz. Confirm the RF matching network and antenna before using any alternative band.
Who develops the ZillaStick S3 firmware?
The independent project is by Hackazillarex. PINGEQUA makes the RF Pack S3 expansion board referenced by the author. PINGEQUA does not represent the project as its own firmware or imply an official partnership with the author.
Get the compatible hardware and original firmware
If you already own an M5Stack StickS3 and want to explore ZillaStick's CC1101 and nRF24 modules, the PINGEQUA RF Pack S3 is the specific expansion hardware named in the project. Check the product page for the current package contents, stock and pricing.
Explore PINGEQUA RF Pack S3 for StickS3 →
Official project resources: ZillaStick S3 GitHub repository · author's Web Flasher · PINGEQUA RF Pack S3 hardware wiki.
Editorial note: This independent hardware-compatibility guide was prepared by PINGEQUA using publicly available project documentation and code reviewed on November 6, 2026. Feature descriptions reflect the author's implementation and may vary by build. Use radio hardware and wireless security tools only where authorized and permitted.