Question 1

Does LoRa mode work on Cardputer ADV with the M5Stack LoRa Cap SX1262?

Accepted Answer

Yes. Connect the LoRa cap to the Cardputer ADV and use the default pin configuration; the required pins are already preconfigured.

Question 2

How to fix IRremoteESP8266 splitting long air-conditioner remote raw signals into multiple frames and missing marks/spaces?

Accepted Answer

The default raw capture buffer is too small. In IRremoteESP8266, `kRawBuf = 100` stores only 99 mark/space entries, so long AC remotes such as a repeated 72-bit frame can exceed it and be split or truncated. In `InfraredService.cpp`, allocate `IRrecv` with a larger buffer, for example 512:

```cpp
_receiver = new IRrecv(_rxPin, 512);
```

Before reallocating on each `configure()` call, release the previous receiver to avoid leaking the larger buffer:

```cpp
if (_receiver != nullptr) {
  _receiver->disableIRIn();
  delete _receiver;
  _receiver = nullptr;
}
_receiver = new IRrecv(_rxPin, 512);
```

Then rebuild and flash the ESP32 Bit Pirate firmware. A temporary alternative is to change `kRawBuf` in the library's `IRrecv.h`, but passing the size to the `IRrecv` constructor and fixing the object lifecycle is the preferred solution.

Question 3

How do I add support for ESP32-S3-Zero or ESP32-S3 SuperMini with ESP32-S3FH4R2, 4 MB flash, and 2 MB PSRAM?

Accepted Answer

Use a custom PlatformIO environment/profile based on the ESP32-S3 DevKit and set `board_build.flash_size = 4MB`. Create a 4 MB partition table, for example `partitions_s3_4m.csv`:

```csv
# Name,     Type, SubType,   Offset,    Size,
nvs,        data, nvs,       0x9000,    0x6000,
phy_init,   data, phy,       0xF000,    0x1000,
factory,    app, factory,   0x10000,   0x390000,
spiffs,     data, spiffs,    0x3A0000,  0x60000,
```

Reference it with `board_build.partitions = partitions_s3_4m.csv`, then configure the board-specific GPIOs in the new PlatformIO environment. This layout omits the coredump partition and uses a 384 KB SPIFFS partition to fit the 4 MB flash. If the dedicated environment triggers the memset-related crash from issue #180, calling `::memset()` explicitly is a known workaround.

Question 4

How do I fix IR signal reception or recording not working on M5StickS3 when using the default TX pins?

Accepted Answer

Use the M5StickS3’s internal IR receiver through the RMT peripheral instead of the default TX pins. Update to a library/firmware version that includes the M5StickS3 IR receive implementation, then configure IR receiving to use RMT reading and decoding as shown in M5Stack’s M5StickS3 IR NEC example. After rebuilding, test recording with an NEC-compatible remote.

ESP32-Bit-Pirate

Overview

README Preview

FAQ (4)

同类型项目

hermes-agent

firecrawl

go

markitdown