search

justcallmekoko / ESP32Marauder

A suite of WiFi/Bluetooth offensive and defensive tools for the ESP32
5.6k stars 614 forks source link

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

Closed coded-with-claws closed 8 months ago

coded-with-claws commented 1 year ago

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:

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:

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:

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

Thanks :)

justcallmekoko commented 1 year ago

Did you enable the SavePCAP setting?

coded-with-claws commented 1 year ago

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 commented 1 year ago

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

paolocamm commented 1 year ago

hi i have empty pcap files too esp32 wroom

D0mpie commented 1 year ago

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 commented 1 year ago

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:

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

Masimi commented 1 year ago

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 commented 1 year ago

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

codecolorado commented 1 year ago

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 commented 1 year ago

@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 commented 1 year ago

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

clipboard1 commented 1 year ago

@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 commented 1 year ago

@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 commented 1 year ago

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

codecolorado commented 1 year ago

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 commented 1 year ago

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

ritave commented 1 year ago

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 commented 1 year ago

I'd rather not. The entire point is to be able to properly use marauder.

Get Outlook for Androidhttps://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 GitHubhttps://github.com/justcallmekoko/ESP32Marauder/issues/249#issuecomment-1520524606, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH4DP3SHHH32LZJCRN4LMRLXC2WRNANCNFSM6AAAAAAWY5VEFI. You are receiving this because you commented.Message ID: @.***>

s3lfdstrukt commented 1 year ago

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 commented 1 year ago

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

s3lfdstrukt commented 1 year ago

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 commented 1 year ago

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

SAME HERE

D0mpie commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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

codecolorado commented 1 year ago

Listen. This thread was about the esp-wroom-32. You guys have corrupted the thread with your flipper dev boards and what not... I'm starting a new thread for the wroom.

ivanpfigueiredo commented 1 year ago

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.

ty

f1yaw4y commented 1 year ago

Amazing work finding this solution. I guess another solution would be to solder directly to gpio 9 and 10 on the chip as oppossed to the breakout board, but then the expansion board would look ridiculous.

Which file did you modify to change these lines? I am also using ESP-WROOM-32

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);

I soldered Tx0 and Rx0, it would be great to just change this to Serial0.begin, reflash and have it work. But I have no idea which firmware file you're referring to. Any help would be greatly appreciated.

Thank you much for the help and impressive job fixing the issue!

coded-with-claws commented 1 year ago

Hi, Thanks! I changed the files directly into the cloned github project (https://github.com/justcallmekoko/ESP32Marauder/tree/master/esp32_marauder) and I compiled and flashed with Arduino IDE. Tx0 and Rx0 should be reserved to the communication with the Flipper zero app (otherwise you will have to modify the app).

Shahar2k5 commented 1 year ago

Hi, Thanks! I changed the files directly into the cloned github project (https://github.com/justcallmekoko/ESP32Marauder/tree/master/esp32_marauder) and I compiled and flashed with Arduino IDE. Tx0 and Rx0 should be reserved to the communication with the Flipper zero app (otherwise you will have to modify the app).

@coded-with-claws can you share the final result? Which pins did you use? RX0/TX0 AND RX2/TX2? or just one pair? Where did you connect them on the flipper? Can you share the firmware bin file you compiled?

Thanks!

caliKev commented 1 year ago

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 :)

@coded-with-claws thank you very much for the helpful tips. I followed your source modification instructions and built v10.9 with the serial option and marauder v4 option and flashed it into a espwroom32. I connected rx0/tx0 to tx/rx on the flipper and rx2/tx2 pins 15/16 (low power UaRt) When I run marauder sniff pmkid from version 3.6 of the companion app I get pcaps between 4 bytes and a few kb but they can’t be opened in wireshark or other programs. I’ve tried connecting rx2/tx2 to 15/16 and 16/15.

Any suggestions anyone has are welcome

coded-with-claws commented 1 year ago

@Shahar2k5 @caliKev I rebuilt the firmware for marauder 0.10.8 (interesting sniffpmkid feature on targeted AP :grin: ) with the same code patch I described earlier, and uploaded it for you on: https://we.tl/t-Kp6TQw8zgp (expires in 1 week)

Like I said earlier, I had used the "sniff raw" feature to get pcap files, because I didn't manage to make "sniff pmkid" to work. But with the new developments on marauder, I hope to manage to do so!

Like I explained earlier, the serial wirings are:

@caliKev About you having corrupted pcap files, maybe you should check all you wirings with a multimeter. Make sure wanted connections, but also that unwanted connections are not present. But start checking the "sniff raw" first (wait for flipper displaying data so that you're sure you got packets).

Hope it helps you both make it work!

Balzermw commented 1 year ago

@Shahar2k5 @caliKev I rebuilt the firmware for marauder 0.10.8 (interesting sniffpmkid feature on targeted AP 😁 ) with the same code patch I described earlier, and uploaded it for you on: https://we.tl/t-Kp6TQw8zgp (expires in 1 week)

Like I said earlier, I had used the "sniff raw" feature to get pcap files, because I didn't manage to make "sniff pmkid" to work. But with the new developments on marauder, I hope to manage to do so!

Like I explained earlier, the serial wirings are:

  • FZ 13/TX <=> ESP32 3/RX0
  • FZ 14/RX <=> ESP32 1/TX0
  • FZ 15/TX <=> ESP32 RX2
  • FZ 16/RX <=> ESP32 TX2

@caliKev About you having corrupted pcap files, maybe you should check all you wirings with a multimeter. Make sure wanted connections, but also that unwanted connections are not present. But start checking the "sniff raw" first (wait for flipper displaying data so that you're sure you got packets).

Hope it helps you both make it work!

can you please re-upload or send to me? on a ESP-WROOM-32 with the same issue

Hravid commented 1 year ago

@Balzermw ur WeTransfer has already expired tho 😫😫😫

Shahar2k5 commented 1 year ago

@Shahar2k5 @caliKev I rebuilt the firmware for marauder 0.10.8 (interesting sniffpmkid feature on targeted AP 😁 ) with the same code patch I described earlier, and uploaded it for you on: https://we.tl/t-Kp6TQw8zgp (expires in 1 week)

Like I said earlier, I had used the "sniff raw" feature to get pcap files, because I didn't manage to make "sniff pmkid" to work. But with the new developments on marauder, I hope to manage to do so!

Like I explained earlier, the serial wirings are:

  • FZ 13/TX <=> ESP32 3/RX0
  • FZ 14/RX <=> ESP32 1/TX0
  • FZ 15/TX <=> ESP32 RX2
  • FZ 16/RX <=> ESP32 TX2

@caliKev About you having corrupted pcap files, maybe you should check all you wirings with a multimeter. Make sure wanted connections, but also that unwanted connections are not present. But start checking the "sniff raw" first (wait for flipper displaying data so that you're sure you got packets).

Hope it helps you both make it work!

Works like a charm! Great work!

asizon commented 1 year ago

Hello all! Thank you very much for the solution @coded-with-claws. I cant make it work on my xiao c3 esp32 board because it only have 1 uart available, do you think that can be a solution on uart comunication to use two uart0 wires only?

coded-with-claws commented 1 year ago

Here you go for a new upload (dunno the delay for this site) @Balzermw @Hravid https://www.udrop.com/KfDF/esp32_marauder.ino_(v0.10.8_ESP-WROOM-32_SD_serial).bin

@Shahar2k5 Great, happy to hear :)

@Asizon I don't know enough about ESPs to answer you, I guess you could search two other pins for the serial pcap communication and change the code into marauder's code (and handle the pins with your own code, as they are not uart?!), but it seems kinda complicated (to me at least!)

asizon commented 1 year ago

Looks like c3 also got an TX1/RX1 defined and available, where can i find serial1.write part code???

image

asizon commented 1 year ago

Here you go for a new upload (dunno the delay for this site) @Balzermw @Hravid https://www.udrop.com/KfDF/esp32_marauder.ino_(v0.10.8_ESP-WROOM-32_SD_serial).bin

@Shahar2k5 Great, happy to hear :)

@Asizon I don't know enough about ESPs to answer you, I guess you could search two other pins for the serial pcap communication and change the code into marauder's code (and handle the pins with your own code, as they are not uart?!), but it seems kinda complicated (to me at least!)

I have managed to get another uart working on c3, i will post the solution later! I tried to make raw attack but i get 1kb file... Im not sure if it is working as expected

asizon commented 1 year ago

@coded-with-claws you can decide wich pins to use for serial1 here, like that: Serial1.begin(115200, 8N1, 4, 5)

asizon commented 1 year ago

So here is the finnal easiest solution to configure uarts on wroom and xiao C·3

esp32 WROOM:
esp32_marauder/esp32_marauder.ino:    Serial1.begin(115200, 8N1, 16, 17);

Xiao C3:
esp32_marauder/esp32_marauder.ino:    Serial1.begin(115200, 8N1, 9, 10);

No need to modify buffer, just made this change.

coded-with-claws commented 1 year ago

Hi @Asizon, great, thanks for the info!

Lorenzo-95 commented 1 year ago

So here is the finnal easiest solution to configure uarts on wroom and xiao C·3

esp32 WROOM:
esp32_marauder/esp32_marauder.ino:    Serial1.begin(115200, 8N1, 16, 17);

Xiao C3:
esp32_marauder/esp32_marauder.ino:    Serial1.begin(115200, 8N1, 9, 10);

No need to modify buffer, just made this change.

Hi everyone, I have the same issue with WROOM board and I wanna recap the solution you found.

First of all, we have to edit esp32_marauder.ino line 195 like @Asizon commented, then compile with Arduino IDE. Then we can flash the compiled bin and solder the pins 16/17 with the Flipper pins C0/C1 (obviously inverting TX/RX). Is that right?

Could be this implemented in the next official release? @justcallmekoko

Lorenzo-95 commented 1 year ago

Hi, I've tried to compile the firmware following step by step the documentation Installing Firmware From Source but I have errors during the compiling process (all libraries installed correctly). Has anyone the compiled firmware or a fix? I need serial on pins 16/17. Thanks!

Lorenzo-95 commented 1 year ago

Hi, I'm still stuck :( Anyone can help me please?

roripocket commented 11 months ago

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.

HI, I just notice that for ESP32-S2-WROVER the only firmare that write pcaps correctly to the internal SD is the next version : https://github.com/justcallmekoko/ESP32Marauder/releases/download/v0.10.8/esp32_marauder_v0_10_8_20230621_flipper_sd_serial.bin Today is working fine.