Empty pcap with SD Serial support (Flipper Zero app) on ESP-WROOM-32

[coded-with-claws]

Hi,
I compiled Marauder 0.10.2 branch develop (checked out yesterday) with WRITE_PACKETS_SERIAL and MARAUDER_V4, and uploaded it to my ESP-WROOM-32 (with Arduino IDE following the instructions from the Wiki), connected with double serial on my Flipper zero (Unleashed firmware with companion app supporting the SD serial pcap saving).
I say "double serial" because I got:

• a first TX/RX couple for the Marauder communication (sending commands and reading results like AP list)
• and a second TX/RX couple for the pcap SD card saving.

When I run a "sniff pmkid" or a "sniff raw", I get lines displayed (Received EAPOL: or RSSI ... Ch... BSSID) but I get empty pcap files (0 bytes for pmkid_0.pcap and raw_0.pcap) on the SD card of Flipper zero.

I soldered the connections for the pcap SD serial saving like it is expected:
- ESP32: RX2 -> FZ: 15 (TX pin)
- ESP32: TX2 -> FZ: 16 (RX pin)
And I checked the electrical continuity with a multimeter.

Is the SD serial support supposed to work on ESP32 (not ESP32-S2)?

To Reproduce
Steps to reproduce the behavior:

1. On Flipper Zero, open the application "[ESP32] WiFi Marauder" (v0.3.3)
2. Run Sniff PMKID on channel
3. Lines are displayed: Received EAPOL:
4. Check the pmkid_0.pcap on the Flipper zero's SD card: 0 bytes

Expected behavior
The pcap files should not be empty because packets were captured, according to the Marauder log.

Marauder:

• Firmware version: 0.10.2 branch develop (checked out yesterday)
• Hardware version: OG V4

Additional context
Except this problem for writing pcaps, the Flipper zero app works nice with Marauder on my ESP32.

Thanks :)

[justcallmekoko]

Did you enable the SavePCAP setting?

[coded-with-claws]

Yes, I have enabled this setting in the Flipper zero app.
I also enabled the "log saving on SD card" and this one works perfectly.
Sorry I forgot to give this precision.

Also, I have read the same kind of issue on #141 but I'm up to date. But maybe it's somehow related?

[JuriG66]

Hi, i have same problem with empty pcap files like you. ESP32 WROOM

[paolocamm]

hi i have empty pcap files too esp32 wroom

[D0mpie]

Hello, I have the same problem on my brand new Flipper Zero Wi-Fi Module v1 with an ESP32-S2-WROVER module.

The new files are written onto the internal SD of the flipper but are 0 bytes. I use the latest ESP32 Marauder v0.10.2 installed with FZEasyMarauderFlash and the Flipper-Xtreme)
firmware for the Flipper.

[coded-with-claws]

Ok I found something.

On ESP-WROOM-32, we have "serial0 aka TX0/RX0" and "serial2 aka TX2/RX2", but I don't see any TX1/RX1 printed on the chip. That's why I had soldered TX2 and RX2.
The Marauder code uses "Serial1" for the pcap data saving, and uses the library esp32 which maps the "Serial0/1/2" with the GPIO pin numbers, into HardwareSerial.cpp:

#ifndef RX1
#if CONFIG_IDF_TARGET_ESP32
#define RX1 9
[...]
#ifndef TX1
#if CONFIG_IDF_TARGET_ESP32
#define TX1 10

I also found this kind of information on this link:

Serial0: RX0 on GPIO3, TX0 on GPIO1
Serial1: RX1 on GPIO9, TX1 on GPIO10 (+CTS1 and RTS1)
Serial2: RX2 on GPIO16, TX2 on GPIO17 (+CTS2 and RTS2) 

Problem: On ESP-WROOM-32, I don't see GPIO 9 and 10 :(

So, I did a modification into the marauder code so that I now get the pcap files filled.

I replaced "Serial1" with "Serial2" into the following lines:

esp32_marauder/Buffer.cpp:      Serial1.write(bufB, bufSizeB);
esp32_marauder/Buffer.cpp:      Serial1.write(bufA, bufSizeA);
esp32_marauder/Buffer.cpp:      Serial1.write(bufA, bufSizeA);
esp32_marauder/Buffer.cpp:      Serial1.write(bufB, bufSizeB);
esp32_marauder/esp32_marauder.ino:    Serial1.begin(115200);

Now it works on my ESP-WROOM-32!

I'm not sure about the correct way to solve the problem:

• either modify Marauder code so that in OG V4 we use Serial2 for pcap data
• either re-solder on the good pins (but do they exist??)
• either modify HardwareSerial.cpp (I guess we should not do that!)

@justcallmekoko I guess you'll have a more enlightened opinion than me :)

[Masimi]

I had the same problem with the Flipper Zero Wifi Dev Board, I search in the logs and I find a error menssage:
#sniffpmkid -c 33 Set channel: 33 Starting PMKID sniff on channel 33. Stop with stopscan AP config set error, Maurauder SSID might visible : err=0x102 Received EAPOL:
I think the problem only happens to save pcaps, because other files like logs errors and list_ap files are save normally in sd card

[paolocamm]

Hi, i have same problem with empty pcap files like you. ESP32 WROOM i put the last update thanks koko

[codecolorado]

Same esp-wroom-32 on f0. Empty pcap files. I have 100% faith we will see a fix soon. Let me ask though. If I solder on an external card will it work?

[clipboard1]

@coded-with-claws hi! i tried edit code like u said, but it does'nt works, can u said where did u connect rx2 tx2 ?

[coded-with-claws]

Hi @clipboard1 I connected like I explained into the description:

• ESP32: RX2 -> FZ: 15 (TX pin)
• ESP32: TX2 -> FZ: 16 (RX pin)

[clipboard1]

@coded-with-claws I did everything as you described, but I still get 1kb pmkid pcaps. What I did:

1. uncomment WRITE_PACKETS_SERIAL and MARAUDER_V4
2. Replace Serial1 to Serial2 as you said
3. Turned on SavePCAP in marauder app on flipper
   Maybe i missed something...
   What esp32 are u using ?

[coded-with-claws]

@clipboard1
It seems you did everything like me...
I have an ESP-WROOM-32.
Can you test a "sniff raw" on a channel having wifi activity? (that's what I did to test the SD writing)
(you can set the channel with "Channel", use the arrow to select "Set" then click on button and choose the channel you want. The channels associated with access points are listed in the log when you do a "scan ap" (but they no longer are seen when you do a "list ap").
So, test the raw sniffing, because people saw errors in logs about pmkid sniffing, and I still never managed to capture those, so I guess there is something to fix about pmkid.

[paolocamm]

hi to all i just fix it i deleded marauder and i installed esp32 penetretion tool it works well

[codecolorado]

hi to all i just fix it i deleded marauder and i installed esp32 penetretion tool it works well

Wait what? I'm trying to get pcaps to save on flipper that surely wouldn't work

[s3lfdstrukt]

I have this issue on esp32-s2. Empty PCAP, logs work fine.

[ritave]

you have to use esp32_marauder_v0_10_3_20230414_flipper_sd_serial.bin rather than esp32_marauder_v0_10_3_20230414_flipper.bin

[codecolorado]

I'd rather not. The entire point is to be able to properly use marauder. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: paolocamm ***@***.***> Sent: Monday, April 24, 2023 12:00:06 PM To: justcallmekoko/ESP32Marauder ***@***.***> Cc: DubTechnic ***@***.***>; Comment ***@***.***> Subject: Re: [justcallmekoko/ESP32Marauder] Empty pcap with SD Serial support (Flipper Zero app) on ESP-WROOM-32 (Issue #249) hi to all i just fix it i deleded marauder and i installed esp32 penetretion tool it works well — Reply to this email directly, view it on GitHub<#249 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH4DP3SHHH32LZJCRN4LMRLXC2WRNANCNFSM6AAAAAAWY5VEFI>. You are receiving this because you commented.Message ID: ***@***.***>

[s3lfdstrukt]

you have to use esp32_marauder_v0_10_3_20230414_flipper_sd_serial.bin rather than esp32_marauder_v0_10_3_20230414_flipper.bin

I've tried both with the latest version. Now no logs or pcap.

[codecolorado]

I believe they only work on the official dev board. I don't believe they work on the esp-wroom-32.

[s3lfdstrukt]

I believe they only work on the official dev board. I don't believe they work on the esp-wroom-32.

I have the official dev board

[Codeined]

Hi, i have same problem with empty pcap files like you. ESP32 WROOM

SAME HERE

[D0mpie]

Hello, I have the same problem on my brand new Flipper Zero Wi-Fi Module v1 with an ESP32-S2-WROVER module.

The new files are written onto the internal SD of the flipper but are 0 bytes. I use the latest ESP32 Marauder v0.10.2 installed with FZEasyMarauderFlash and the Flipper-Xtreme) firmware for the Flipper.

I just updated my Flipper to Xtreme firmware XFW-0046 06-05-2023. Cloned a new version of FZEasyMaurauderFlash. After installing the requirements it downloaded esp32_marauder_v0_10_4_20230505_flipper_sd_serial.bin. Then I flashed the official Wifi dev board with option 2 (Flash SD Serial Marauder on Devboard or ESP32-S2). Now my pcap files aren't empty anymore. Not sure what fixed it. Nevertheless I wanted to share this. Hope some will find it helpful.

[sysfu]

Hello, I have the same problem on my brand new Flipper Zero Wi-Fi Module v1 with an ESP32-S2-WROVER module.
The new files are written onto the internal SD of the flipper but are 0 bytes. I use the latest ESP32 Marauder v0.10.2 installed with FZEasyMarauderFlash and the Flipper-Xtreme) firmware for the Flipper.

I just updated my Flipper to Xtreme firmware XFW-0046 06-05-2023. Cloned a new version of FZEasyMaurauderFlash. After installing the requirements it downloaded esp32_marauder_v0_10_4_20230505_flipper_sd_serial.bin. Then I flashed the official Wifi dev board with option 2 (Flash SD Serial Marauder on Devboard or ESP32-S2). Now my pcap files aren't empty anymore. Not sure what fixed it. Nevertheless I wanted to share this. Hope some will find it helpful.

Have you tested with the latest version of flipper unleashed firmware to confirm the issue is resolved there as well? Wonder if the fix is contained in the Xtreme firmware code or the latest esp32_marauder_v0_10_4_20230505_flipper_sd_serial.bin.

[sbenne]

Ok I found something.

On ESP-WROOM-32, we have "serial0 aka TX0/RX0" and "serial2 aka TX2/RX2", but I don't see any TX1/RX1 printed on the chip. That's why I had soldered TX2 and RX2. The Marauder code uses "Serial1" for the pcap data saving, and uses the library esp32 which maps the "Serial0/1/2" with the GPIO pin numbers, into HardwareSerial.cpp:

#ifndef RX1
#if CONFIG_IDF_TARGET_ESP32
#define RX1 9
[...]
#ifndef TX1
#if CONFIG_IDF_TARGET_ESP32
#define TX1 10

I also found this kind of information on this link:

Serial0: RX0 on GPIO3, TX0 on GPIO1
Serial1: RX1 on GPIO9, TX1 on GPIO10 (+CTS1 and RTS1)
Serial2: RX2 on GPIO16, TX2 on GPIO17 (+CTS2 and RTS2) 

Problem: On ESP-WROOM-32, I don't see GPIO 9 and 10 :(

So, I did a modification into the marauder code so that I now get the pcap files filled.

I replaced "Serial1" with "Serial2" into the following lines:

esp32_marauder/Buffer.cpp:      Serial1.write(bufB, bufSizeB);
esp32_marauder/Buffer.cpp:      Serial1.write(bufA, bufSizeA);
esp32_marauder/Buffer.cpp:      Serial1.write(bufA, bufSizeA);
esp32_marauder/Buffer.cpp:      Serial1.write(bufB, bufSizeB);
esp32_marauder/esp32_marauder.ino:    Serial1.begin(115200);

Now it works on my ESP-WROOM-32!

I'm not sure about the correct way to solve the problem:

• either modify Marauder code so that in OG V4 we use Serial2 for pcap data
• either re-solder on the good pins (but do they exist??)
• either modify HardwareSerial.cpp (I guess we should not do that!)

@justcallmekoko I guess you'll have a more enlightened opinion than me :)

I didn't try, but after a lot of different flash, I think it's good start, I have take some time to understand which of the - "serial0 aka TX0/RX0" and "serial2 aka TX2/RX2" -, I have to use, just a correction it is not TX0/RX0 but TXD/RXD, like Dev/Debug ? if I am not wrong this could have sens, thanks

[s3lfdstrukt]

Hello, I have the same problem on my brand new Flipper Zero Wi-Fi Module v1 with an ESP32-S2-WROVER module.
The new files are written onto the internal SD of the flipper but are 0 bytes. I use the latest ESP32 Marauder v0.10.2 installed with FZEasyMarauderFlash and the Flipper-Xtreme) firmware for the Flipper.

I just updated my Flipper to Xtreme firmware XFW-0046 06-05-2023. Cloned a new version of FZEasyMaurauderFlash. After installing the requirements it downloaded esp32_marauder_v0_10_4_20230505_flipper_sd_serial.bin. Then I flashed the official Wifi dev board with option 2 (Flash SD Serial Marauder on Devboard or ESP32-S2). Now my pcap files aren't empty anymore. Not sure what fixed it. Nevertheless I wanted to share this. Hope some will find it helpful.

I tried this exact process and with the same hardware and I have no logs or pcaps at all. not empty ones, nothing.

[sysfu]

I just updated the Wifi Dev Board firmware to 0.10.4 using Easy Flipper Zero Marauder Flash. https://github.com/SkeletonMan03/FZEasyMarauderFlash

Chose option "(2) Flash SD Serial Marauder on Devboard or ESP32-S2" as suggested by @chrisbward and now the pcaps are saving to the SDCard!

[1337speed1337]

The following worked for me and the flipper wifi dev board v1 and extreme firmware (XFW-0046_06052023) but should work with unleashed as well:

Go here https://esp.huhn.me/

Connect to device and put the following bins in the appropriate place:

0x1000 = FZEasyMarauderFlash-main\Extra_ESP32_Bins\Marauder\bootloader.bin
0x8000 = FZEasyMarauderFlash-main\Extra_ESP32_Bins\Marauder\partitions.bin
0xE000 = empty
0x10000 = FZEasyMarauderFlash-main\ESP32Marauder\releases\esp32_marauder_v0_10_4_20230505_flipper_sd_serial.bin

Obviously powercycle and plugin and do your thing. Pcaps now saved to disk.

[seanism]

Initially I selected 1 and had the zero bytes issue. Reflashed with option 2 and now my pcap files are saving correctly.

Wifi dev board v1

[coded-with-claws]

Hi,
I installed latest version (0.13.4), the SD write still works (ESP-WROOM-32).
But I still had to change the code. This time, I did like proposed by @asizon :
Serial1.begin(115200, SERIAL_8N1, 16, 17); in esp32_marauder.ino
@justcallmekoko : would it be possible to add new "#defines" for WROOM like there is for XIAO_ESP32_S3 with XIAO_RX1 and XIAO_TX1?
Meaning:

• into configs.h new lines for ifdef ESP32_WROOM32 => #define WROOM32_RX1 16 and #define WROOM32_TX1 17
• into esp32_marauder.ino, inside the #ifdef WRITE_PACKETS_SERIAL, new lines to test if we have ESP32_WROOM32, then run Serial1.begin(115200, SERIAL_8N1, WROOM32_RX1, WROOM32_TX1);

@justcallmekoko : could you add me the permission to propose a pull request? I have prepared the code but I'm denied when trying to push my branch :) Thanks!

[coded-with-claws]

When you say "uploaded it to my ESP-WROOM-32" with the instructions, which Board Type did you select under Tools? For step 9 in the instructions: "Select the appropriate ESP32 module under Tools>Boards

Select LOLIN D32 for the following:
	Marauder v4 (OG)
	Marauder v6
	Marauder Mini
Select Adafruit ESP32 Feather for the following:
	Marauder Kit
Select ESP32-S2 dev board for the following:
	Marauder Flipper (Flipper Zero WiFi Dev Board)"

I'm unsure which to pick for a default/normal ESP-WROOM-32 board. LOLIN D32 since we're using Marauder v4 in the config.h? Or maybe just ESP32 DevKit?

Hi, I chose LOLIN D32 like advised in the wiki.

[tmaiaroto]

@coded-with-claws do you have a fork of this repo somewhere with builds? I was trying to use act to run the git actions locally but builds failed. I think your adjustments are correct to support a larger number of boards.

I tried forking and building with the changes, but didn't seem to work (getting the 1kb pcap files like others indicated...better than empty files I guess) unless I'm missing something.

[coded-with-claws]

@tmaiaroto I pushed the changes on a fork and proposed a pull request: #401
As for the 1 kb pcap files, I think it's not due to this present issue, but rather to the testing method (personally I haven't digged this one yet). If you manage to get valid pcap files, your pin configuration is good.

[tmaiaroto]

@coded-with-claws It did say they weren't valid pcap files. it wasn't like it stopped at 1kb. or maybe it did and something wasn't finished properly. but they wouldn't open in wireshark. i'm using pins 16, 17 on the esp-wroom-32 board marked D16 and D17 and put those into 15 and 16 on the FZ (right after the TX/RX). I'll try the bin files from your PR maybe I messed something up though all I did was change Serial1.begin(115200); to -> Serial1.begin(115200, SERIAL_8N1, 16, 17); in esp32_marauder.ino

Update: I get same results with the bins the Git actions built from your PR. Maybe I have the wrong pins connected or something. I flipped them in case I got the RX/TX mixed up and it did produce a different file but both were not readable/valid. Error says (commview: NCFX data length 0 < 20) and leaving it scan for a while my file is like 66kb so stuff is writing.

[coded-with-claws]

@tmaiaroto Do you test with "sniffraw"? (in order to be sure to get valid pcap files)
Maybe check the electric continuity of your wiring?

[tmaiaroto]

@coded-with-claws I did use sniffraw. I'll see if I can somehow test the connections. I'm just using some dupont cables there, they're brand new. 🤷‍♂️ Something definitely populates the files I can leave it scan for some time and get larger files.

[coded-with-claws]

@tmaiaroto I guess with brand new dupont cables it should be fine. You said you wired D16 and D17, maybe it's not the good pins?
On mine, they are named RX2 / TX2.
I have another board where there are no RX2 TX2 D16 D17 anywhere, so I guess there is no standard...
Do you have a picture of your board?

[Asdii]

@tmaiaroto I guess with brand new dupont cables it should be fine. You said you wired D16 and D17, maybe it's not the good pins? On mine, they are named RX2 / TX2. I have another board where there are no RX2 TX2 D16 D17 anywhere, so I guess there is no standard... Do you have a picture of your board?

@coded-with-claws I'm experiencing the same result. I used the .bin file you provided on a ESP-WROOM-32 (ESP32-D0WDQ6) from aliexpress, connected both RX/TX pins, and after sniffing raw data i get a file with some data in them, but i get the same error on Wireshark (commview: NCFX data length 0 < 20).

Edit: I switched RX/TX pins, but the files weren't readable, the error described before only happens when they are in the right position. I also tried all sniffing methods, all of them are able to write data, but the same error happens.

[coded-with-claws]

@Asdii Your pins 16 & 17 are located exactly as my pins RX2 & TX2, and in between I have the same pins... So your wiring seems good to me.
You're saying that you're using the .bin I provided, are you talking about when I uploaded it on wetransfer, or my github repository? Because it seems the .bin are not pushed, they still are dated of last year hence the date of the original justcallmekoko repository. On my disks they have the date of my build... But they are not listed on .gitignore so I don't understand why they weren't pushed.
So, here are the .bin I have built. As I don't know which one Arduino IDE uploads on the board, I provided the "d32.bin" and the "old_hardware.bin". The link will be up for one week.
https://we.tl/t-LNeDCfktNf
@Asdii @tmaiaroto Please tell me if it's better?

[tmaiaroto]

I'll give those a try, thanks! Before, I took the bin files from the GitHub actions that should have built the files pushed.

Same results, files have content written but Wireshark shows an error when trying to open them.

[Asdii]

@coded-with-claws i used this link
https://www.udrop.com/KfDF/esp32_marauder.ino_(v0.10.8_ESP-WROOM-32_SD_serial).bin

I don't understand why it wouldn't work, i inspected some of the code inside buffer.cpp (I believe that's the one responsible of the serial writing) but couldn't find anything relevant, everything seems right. Maybe it's the flipper app that's expecting something different?, is there a way to see the Serial1 output before it's written to a file?

[tmaiaroto]

I got a devboard from justcallmekoko. It doesn't seem to write to the flipper's sd card either, but it has an sd card slot of its own. I guess that's what most folks do. I'm more interested in solving this problem and making something custom than having a working unit. I don't exactly have any real use case here, it's more about learning and building something custom. So I guess I'll keep tinkering.

@coded-with-claws do you have a link to the board you bought? I'm curious if maybe I just got some flawed or incorrectly put togther ESP32-WROOM board. I only have one RX0/TX0 I don't see an RX2/TX2. Your fixes make complete sense to me based on what I've read. Switching to use different pins seems exactly right. Yet it doesn't seem to work on the board I have. I got some board off Amazon (a 3 pack they were so cheap) that has USB-C. The chip does not say expressif on it. It does say ESP-WROOM-32 though. So maybe I got a knock off or something that isn't implemented quite right.

[Asdii]

I made this little test to see the output from the second serial communication by switching Serial1 with Serial 2 on the Flipper Zero and oppening Serial1 on PuTTy.

1.- Switch serial communications:
FZ RX -> ESP32 pin 17
FZ TX -> ESP32 pin 16

2.- Connect the ESP32 to your PC
3.- Open arduino IDE or PuTTy, open serial communication, scan ap's, select one and then sniffraw
4.- On the flipper zero select sniffraw (i know it doesn't work, but it shows communication anyway)

This is what i got:

@coded-with-claws could you do the same on your end to see if the data is simmilar? i'm trying to discard possible issues, and i know it's binary data, but at least it should be simmilar ascii.

[Lorenzo-95]

@Asdii Your pins 16 & 17 are located exactly as my pins RX2 & TX2, and in between I have the same pins... So your wiring seems good to me. You're saying that you're using the .bin I provided, are you talking about when I uploaded it on wetransfer, or my github repository? Because it seems the .bin are not pushed, they still are dated of last year hence the date of the original justcallmekoko repository. On my disks they have the date of my build... But they are not listed on .gitignore so I don't understand why they weren't pushed. So, here are the .bin I have built. As I don't know which one Arduino IDE uploads on the board, I provided the "d32.bin" and the "old_hardware.bin". The link will be up for one week. https://we.tl/t-LNeDCfktNf @Asdii @tmaiaroto Please tell me if it's better?

Hi, I tried flashing the compiled bin provided by @coded-with-claws on WeTransfer. Like @Asdii my pcaps are blank and the Wireshark error is the same, although pcaps dimension is not 0 anymore.

[coded-with-claws]

@coded-with-claws do you have a link to the board you bought? I'm curious if maybe I just got some flawed or incorrectly put togther ESP32-WROOM board. I only have one RX0/TX0 I don't see an RX2/TX2. Your fixes make complete sense to me based on what I've read. Switching to use different pins seems exactly right. Yet it doesn't seem to work on the board I have. I got some board off Amazon (a 3 pack they were so cheap) that has USB-C. The chip does not say expressif on it. It does say ESP-WROOM-32 though. So maybe I got a knock off or something that isn't implemented quite right.

It's this one I have: https://fr.aliexpress.com/item/1005001929935550.html?spm=a2g0o.order_detail.order_detail_item.5.11617d56iQx5cP&gatewayAdapt=glo2fra
=> click on the photo of "Color: 1pcs ESP-32".

At all: I don't have much time to help investigate, sorry.

[Lorenzo-95]

Guys, maybe I found something!

First of all, I have this board: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-devkitc.html#get-started-esp32-devkitc-board-front

Reading the documentation, I discovered that Serial1 is declared on GPIO9 (D2) and GPIO10 (D3), but these pins are used for internal communication and the documentation suggests avoiding the use of them.
So, maybe changing Serial1 to Serial2 in Buffer.cpp and esp32_marauder.ino can make the things work. I searched for other codes written for this board and everyone uses Serial2 with pins 16 and 17.

Can someone give it a try and compile the bin? I don't have the environment anymore :(

[casimirextreme]

Guys, maybe I found something!

First of all, I have this board: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-devkitc.html#get-started-esp32-devkitc-board-front

Reading the documentation, I discovered that Serial1 is declared on GPIO9 (D2) and GPIO10 (D3), but these pins are used for internal communication and the documentation suggests avoiding the use of them. So, maybe changing Serial1 to Serial2 in Buffer.cpp and esp32_marauder.ino can make the things work. I searched for other codes written for this board and everyone uses Serial2 with pins 16 and 17.

Can someone give it a try and compile the bin? I don't have the environment anymore :(

Yes it's correct, changing to Serial2 does the trick.
I still have a bin of ESP32Marauder v0.10.4 working fine with current WifiMarauder v0.6.5 shipped on latest Roguemaster (RM1130-1445-0.93.9-d9db571)
This one gives non empty pcap on my ESP32-WROOM:
esp32marauder_esp32-wroom-0.10.4.bin.zip
Flash with:
esptool write_flash 0x0 esp32marauder_esp32-wroom-0.10.4.bin (once unzipped)
Hope it helps.

[Asdii]

Guys, maybe I found something!
First of all, I have this board: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-devkitc.html#get-started-esp32-devkitc-board-front
Reading the documentation, I discovered that Serial1 is declared on GPIO9 (D2) and GPIO10 (D3), but these pins are used for internal communication and the documentation suggests avoiding the use of them. So, maybe changing Serial1 to Serial2 in Buffer.cpp and esp32_marauder.ino can make the things work. I searched for other codes written for this board and everyone uses Serial2 with pins 16 and 17.
Can someone give it a try and compile the bin? I don't have the environment anymore :(

Yes it's correct, changing to Serial2 does the trick. I still have a bin of ESP32Marauder v0.10.4 working fine with current WifiMarauder v0.6.5 shipped on latest Roguemaster (RM1130-1445-0.93.9-d9db571) This one gives non empty pcap on my ESP32-WROOM: esp32marauder_esp32-wroom-0.10.4.bin.zip Flash with: esptool write_flash 0x0 esp32marauder_esp32-wroom-0.10.4.bin (once unzipped) Hope it helps.

Does that bin has the serial communication switched? (Serial1 to Serial2)

[tmaiaroto]

Awesome, @casimirextreme that worked, thanks! I have a board with pins labeled D16 and D17 that I have plugged into the Flipper 15,16 respectively and it captured the data just fine now after using esptool to flash this file.

[casimirextreme]

Does that bin has the serial communication switched? (Serial1 to Serial2)

Yes.
Here is the diff:
ESP32Marauder-0.10.4-wroom.diff.zip

[harinath141]

Currently Mac users Couldn't Compile i believe ? Can anyone please provide Compiled bin files. Also Wiring from Esp32-WROOM to FZ

[laurent-luyckx-keemotion]

Currently Mac users Couldn't Compile i believe ? Can anyone please provide Compiled bin files. Also Wiring from Esp32-WROOM to FZ

The bin is for the ESP32. You'll only have to unzip @casimirextreme zip file and install it with esptool.
To use esptool on mac, you can probably follow what's written on this link: https://github.com/RavenSystem/esp-homekit-devices/wiki/Install-ESPTool-on-macOS
For wiring:

ESP32: 3v3 -> FZ: 9 (3v3)
ESP32: GND -> FZ: 11 (GND)
ESP32: RX -> FZ: 13 (TX)
ESP32: TX -> FZ: 14 (RX)
ESP32: 16 -> FZ: 15 (C1)
ESP32: 17 -> FZ: 16 (C0)

[Asdii]

Currently Mac users Couldn't Compile i believe ? Can anyone please provide Compiled bin files. Also Wiring from Esp32-WROOM to FZ

The bin is for the ESP32. You'll only have to unzip @casimirextreme zip file and install it with esptool. To use esptool on mac, you can probably follow what's written on this link: https://github.com/RavenSystem/esp-homekit-devices/wiki/Install-ESPTool-on-macOS For wiring:

ESP32: 3v3 -> FZ: 9 (3v3) ESP32: GND -> FZ: 11 (GND) ESP32: RX -> FZ: 13 (TX) ESP32: TX -> FZ: 14 (RX) ESP32: 16 -> FZ: 15 (C1) ESP32: 17 -> FZ: 16 (C0)

Doing this solved the problem. Thank you so much @casimirextreme and @coded-with-claws. Now i have pcap files that are readable on wireshark.

[gohv]

My pcap was empty when using RogueMaster.
Switched to Unleashed and it saved pcap correctly.

[BucciMobile]

My pcap was empty when using RogueMaster.

Switched to Unleashed and it saved pcap correctly.

Nearly the same here. Was using xtreme and tried multiple suggestions. After countless flashing of the wifi module the solution was simple: I switched the unleashed. And now it's working fine.

[coded-with-claws]

Since v0.13.7, with Unified serial PCAPs, we no longer need to do those changes.