ElectronicCats / CatSniffer

CatSniffer is an original multiprotocol and multiband board for sniffing, communicating, and attacking IoT (Internet of Things) devices using the latest radio IoT protocols. It is a highly portable USB stick that integrates TI CC1352, Semtech SX1262, and an RP2040 for V3 or a Microchip SAMD21E17 for V2
https://github.com/ElectronicCats/CatSniffer
Other
500 stars 67 forks source link

ElectronicCats #49

Closed fe8769a closed 8 months ago

fe8769a commented 9 months ago

Hello I just received my catsniffer today . I have 40 years of computers stall knowledge and the same in radio reception.

I don't know how to begun

Under windows 10 , my catsniffer is recognize as com 3 but no led are lighting I tried to push all buttons as described in documentation -- no chance

I have plenty of windows, linux , raspi computers all kind of versions

I installed the arduino IDE on a raspi 4 using dragon OS v31 (ubuntu) trying to communicate with catsniffer

I have error in running Arduino 1.8.19 like :+1:

Arduino: 1.8.19 (Linux), Board: "Arduino Uno"

/tmp/arduino_modified_sketch_710303/sketch_sep25a.ino: In function 'void setup()': sketch_sep25a:68:3: error: 'Serial1' was not declared in this scope Serial1.begin(baud); ^~~ /tmp/arduino_modified_sketch_710303/sketch_sep25a.ino:68:3: note: suggested alternative: 'Serial' Serial1.begin(baud); ^~~ Serial /tmp/arduino_modified_sketch_710303/sketch_sep25a.ino: In function 'void loop()': sketch_sep25a:91:5: error: 'Serial1' was not declared in this scope Serial1.write(Serial.read()); // read it and send it out Serial1 (pins 0 & 1) ^~~ /tmp/arduino_modified_sketch_710303/sketch_sep25a.ino:91:5: note: suggested alternative: 'Serial' Serial1.write(Serial.read()); // read it and send it out Serial1 (pins 0 & 1) ^~~ Serial sketch_sep25a:94:7: error: 'Serial1' was not declared in this scope if (Serial1.available()) { // If anything comes in Serial1 (pins 0 & 1) ^~~ /tmp/arduino_modified_sketch_710303/sketch_sep25a.ino:94:7: note: suggested alternative: 'Serial' if (Serial1.available()) { // If anything comes in Serial1 (pins 0 & 1) ^~~ Serial exit status 1 'Serial1' was not declared in this scope

This report would have more information with "Show verbose output during compilation" option enabled in File -> Preferences.


Can you explain the way to use catsniffer in windows 10 with TI packets sniffer

is there any different firmware for different applications ?

What is the exact way to start catsniffer

1- serial passthrough ? how ? 2- serial passthrough with bootloader ?

-- using sniffe ? how ? different firmware ?

Thanks for help

cldrn commented 9 months ago

Hey,

We recently gave a 2-hour workshop at Blackhat USA; the booklet contains a step by a step guide to get started. You might want to take a look at it first: https://drive.google.com/drive/folders/1G3v-2CfkqfrdCpSST1b0W_9A_G2I_XbE?usp=drive_link

There is also a lot of information in the wiki, which we are in the process of re-arranging: https://github.com/ElectronicCats/CatSniffer/wiki

You need to load different firmware, depending on what you are trying to achieve. On Windows, I would recommend using TI’s packet sniffer firmware as it contains a GUI and support for all protocols supported to start sniffing traffic.

Please do reach out if you have additional questions!

fe8769a commented 9 months ago

I retreived documentation early this morning and followed you on twitter .

1 - trying to put catsniffer in upload mode - no led . I tried many times many computers 2- I installed Arduino IDE on my raspberry 4 - 4go using dragon OS (ubuntu) and I have errors using both serialpassthroughwithboot or serialpassthrough 3- As I read on documentation, in order to use TI packet sniffer, I have to put catsniffer in upload mode then send with arduino IDE the serialpassthrough script , I can't because of errors 4- in catsniffer lora script I have the error radiolib.h not found

thanks for help

Le lun. 25 sept. 2023 à 20:34, Paulino Calderon @.***> a écrit :

Hey,

We recently gave a 2-hour workshop at Blackhat USA; the booklet contains a step by a step guide to get started. You might want to take a look at it first: https://drive.google.com/drive/folders/1G3v-2CfkqfrdCpSST1b0W_9A_G2I_XbE?usp=drive_link

There is also a lot of information in the wiki, which we are in the process of re-arranging: https://github.com/ElectronicCats/CatSniffer/wiki

You need to load different firmware, depending on what you are trying to achieve. On Windows, I would recommend using TI’s packet sniffer firmware as it contains a GUI and support for all protocols supported to start sniffing traffic.

Please do reach out if you have additional questions!

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1734267645, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDVZEX2V3GCDLHHXTVYDX4HFBPANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 9 months ago

Hi,

To better understand your situation let me know which version of the CatSniffer are you using? v1,2 or v3?

fe8769a commented 9 months ago

hello It is V3.1

yesterday I was able to have some leds , last down led blinking blue . When using catsniffer buttons , I have all leds blinking one after the others . before I have no led and now I can't switch off leds

In Arduino IDE, I don't know the way to update

SerialPassthroughwithboot.ino or SerialPassthroughwithboot.ino.elf.uf2

Thanks

Le mar. 26 sept. 2023 à 23:53, Marcelo Arredondo @.***> a écrit :

Hi,

To better understand your situation let me know which version of the CatSniffer are you using? v1,2 or v3?

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1736353241, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV6XELAC7IQV2L5ICLLX4NFGXANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

--

fe8769a commented 9 months ago

hello

In order to use catsniffer with TI packet analyser and following the documentation , we have to install embedded card in arduino IDE.

using this command :

git clone @.***:arduino/ArduinoCore-mbed mbed

we got the following error :

sudo git clone @.:arduino/ArduinoCore-mbed mbed Cloning into 'mbed'... @.: Permission denied (publickey). fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

I tried to solve but I can't

the same with the following line :

git clone @.***:arduino/ArduinoCore-API

the other line is unclear :

Create a symlink to ArduinoCore-API/api in $sketchbook/hardware/arduino-git/mbed/cores/arduino.

what is the exact syntax

As soon as I will install catsniffer, as fast I will make a documentation

Le mar. 26 sept. 2023 à 23:53, Marcelo Arredondo @.***> a écrit :

Hi,

To better understand your situation let me know which version of the CatSniffer are you using? v1,2 or v3?

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1736353241, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV6XELAC7IQV2L5ICLLX4NFGXANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 9 months ago

Hi,

If you are using V3.1 and trying to use TI's Packet Sniffer you will nedd to load SerialPassthroughwithboot.ino.elf.uf2 to the RP2040 and the sniffer_fw_Catsniffer_v3.x.hex

GitHub\CatSniffer\firmware\V3.x\CC1352P7\sniffer_fw_cc1252P_7\sniffer_fw_Catsniffer_v3.x.hex GitHub\CatSniffer\firmware\V3.x\RP2040\SerialPassthroughwithboot\SerialPassthroughwithboot.ino.elf.uf2

To load the .UF2 firmware to your board we recommend putting the RP2040 in bootloader mode by double tapping (fast as a double click) the Reset1 button. A file explorer window will open and you can drag the .UF2 file and drop it in there, it should close automatically. Using the Arduino IDE for this board model is possible but you will need to make some modifications to the core and that could impact the usability of other RP2040 boards. We recommend loading all the firmware with the .UF2 method.

For the .hex file you will need to use the python tool in out repository. You can find the procedure here. To put the cc1352 in bootloader mode, hold reset1, hold boot1, release reset1 and wait until LED4 stops blinking and you see a swiping pattern on the other LEDs to release boot1.

If you have both of those firmwares on your board, just open TI's Smart RF Packet Sniffer 2 (v1.8) and your board will be detected and you can follow the tutorial on how to use it on our wiki in the Supported Software section. Also remember to use the suggested version of WireShark (3.0.14) and make the direct access as described here.

Regarding the lora firmware that error implies that that library (radiolib.h) is missing from your directory.

fe8769a commented 9 months ago

Hello

the first part with copy UF2 to media is OK the second part copy from arduino ide with SerialPassthroughwithboot.ino is working fine

then when I plug the catsniffer there is 2 leds top and bottom blinking alternatively

Doing the sequence key reset I have of leds swiping pattern .

when I pass the following command :

python cc2538-bsl.py -e -w -v -p COM8 sniffer_fw_Catsniffer_v3.x.hex

I have always a timeout

I tried with TI programmer same trouble , what did I do wrong?

Initiate access to target: COM8 using 2-pin cJTAG.

Communication initialization failed. Failed to send data.

Connecting over serial bootloader failed: Communication initialization failed. Failed to send data.

Failed to create device object.

thanks for answer

Le mer. 27 sept. 2023 à 20:27, Marcelo Arredondo @.***> a écrit :

Hi,

If you are using V3.1 and trying to use TI's Packet Sniffer you will nedd to load SerialPassthroughwithboot.ino.elf.uf2 to the RP2040 and the sniffer_fw_Catsniffer_v3.x.hex

GitHub\CatSniffer\firmware\V3.x\CC1352P7\sniffer_fw_cc1252P_7\sniffer_fw_Catsniffer_v3.x.hex

GitHub\CatSniffer\firmware\V3.x\RP2040\SerialPassthroughwithboot\SerialPassthroughwithboot.ino.elf.uf2

To load the .UF2 firmware to your board we recommend putting the RP2040 in bootloader mode by double tapping (fast as a double click) the Reset1 button. A file explorer window will open and you can drag the .UF2 file and drop it in there, it should close automatically. Using the Arduino IDE for this board model is possible but you will need to make some modifications to the core and that could impact the usability of other RP2040 boards. We recommend loading all the firmware with the .UF2 method.

For the .hex file you will need to use the python tool in out repository. You can find the procedure here. https://github.com/ElectronicCats/CatSniffer/wiki/02.-CatSniffer-v1.x-and-2.x#flashing-with-python To put the cc1352 in bootloader mode, hold reset1, hold boot1, release reset1 and wait until LED4 stops blinking and you see a swiping pattern on the other LEDs to release boot1.

If you have both of those firmwares on your board, just open TI's Smart RF Packet Sniffer 2 (v1.8) and your board will be detected and you can follow the tutorial on how to use it on our wiki in the Supported Software section. Also remember to use the suggested version of WireShark (3.0.14) and make the direct access as described here https://github.com/ElectronicCats/CatSniffer/wiki/04.-Supported-software#wireshark .

Regarding the lora firmware that error implies that that library (radiolib.h) is missing from your directory.

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1737882447, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3IMFTCJO6S3GTRBS3X4RVZ3ANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 9 months ago

Hi,

Just to clarify a bit more, the .UF2 process is just another way to load the SerialPassthroughwithboot.ino firmware (or any other available firmware) to the RP2040, you do not need to also do it on the Arduino IDE.

The swiping pattern indicates the cc1352 is in bootloader mode (as long as the LED 4 is turned OFF).

Are you putting the cc1352 in bootloader mode when running the python commands?

Does it give the same error running the first command to open the port? <python cc2538-bsl.py -p COM08>

Can you share the complete error code?

lukeswitz commented 9 months ago

It says there’s Linux support but is that limited to Sniffle only? Nothing else is compatible and all Windows. The pain points trying to use this are innumerable. Please create software that is simple to compile and can support your devices; or at the least some clear instructions for both Linux and Windows. I have both the 3.1 and 2.1 and both are useless without a windows desktop environment. Useless in the field. Help.

fe8769a commented 9 months ago

So I did only the way sending UF2 to media using pressing twice on reset . Media windows is closing

the I made the boot loader sequence , the led 4 is blinking

I send python command

python cc2538-bsl.py -e -w -v -p COM8 sniffer_fw_Catsniffer_v3.x.hex

Opening port COM8, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file Connecting to target... ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'

once I have this error I have led 4 blinking and led 1 fixed

I saw on the net , we could install zadig driver like rtl-sdr SDR Is there a special configuration of serial port because port setting is 128000 and python is sending 500000 baud rate

here is more details :

Opening port COM8, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file For more solid firmware type auto-detection, install python-magic. Please see the readme for more details. Connecting to target... *** sending synch sequence Traceback (most recent call last): File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 1195, in if not cmd.sendSynch(): ^^^^^^^^^^^^^^^ File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 372, in sendSynch return self._wait_for_ack("Synch (0x55 0x55)", 2) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 265, in _wait_for_ack raise CmdException("Timeout waiting for ACK/NACK after '%s'" CmdException: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'

best regards

Le ven. 29 sept. 2023 à 20:10, Marcelo Arredondo @.***> a écrit :

Hi,

Just to clarify a bit more, the .UF2 process is just another way to load the SerialPassthroughwithboot.ino firmware (or any other available firmware) to the RP2040, you do not need to also do it on the Arduino IDE.

The swiping pattern indicates the cc1352 is in bootloader mode (as long as the LED 4 is turned OFF).

Are you putting the cc1352 in bootloader mode when running the python commands?

Does it give the same error running the first command to open the port? <python cc2538-bsl.py -p COM08>

Can you share the complete error code?

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1741301547, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3GDFDQXQK462QORKLX44FIRANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 9 months ago

It says there’s Linux support but is that limited to Sniffle only? Nothing else is compatible and all Windows. The pain points trying to use this are innumerable. Please create software that is simple to compile and can support your devices; or at the least some clear instructions for both Linux and Windows. I have both the 3.1 and 2.1 and both are useless without a windows desktop environment. Useless in the field. Help.

Hello,

We apologize for any inconvenience you've faced while trying to use our devices on Linux. We truly value your feedback and understand the importance of having a seamless experience across different operating systems, especially in field applications.

Your input is invaluable, and we're committed to addressing these pain points. While we cannot provide an immediate solution, please rest assured that we're taking your feedback into account as we continue to enhance our products and offer clearer instructions for both Linux and Windows users.

We appreciate your patience and dedication to our products.

Marcelol52 commented 9 months ago

So I did only the way sending UF2 to media using pressing twice on reset . Media windows is closing the I made the boot loader sequence , the led 4 is blinking I send python command python cc2538-bsl.py -e -w -v -p COM8 sniffer_fw_Catsniffer_v3.x.hex Opening port COM8, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file Connecting to target... ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' once I have this error I have led 4 blinking and led 1 fixed I saw on the net , we could install zadig driver like rtl-sdr SDR Is there a special configuration of serial port because port setting is 128000 and python is sending 500000 baud rate here is more details : Opening port COM8, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file For more solid firmware type auto-detection, install python-magic. Please see the readme for more details. Connecting to target... sending synch sequence Traceback (most recent call last): File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 1195, in if not cmd.sendSynch(): ^^^^^^^^^^^^^^^ File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 372, in sendSynch return self._wait_for_ack("Synch (0x55 0x55)", 2) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 265, in _wait_for_ack raise CmdException("Timeout waiting for ACK/NACK after '%s'" CmdException: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' best regards Le ven. 29 sept. 2023 à 20:10, Marcelo Arredondo @.> a écrit : Hi, Just to clarify a bit more, the .UF2 process is just another way to load the SerialPassthroughwithboot.ino firmware (or any other available firmware) to the RP2040, you do not need to also do it on the Arduino IDE. The swiping pattern indicates the cc1352 is in bootloader mode (as long as the LED 4 is turned OFF). Are you putting the cc1352 in bootloader mode when running the python commands? Does it give the same error running the first command to open the port? <python cc2538-bsl.py -p COM08> Can you share the complete error code? — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3GDFDQXQK462QORKLX44FIRANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

Thank you for providing detailed information about the issue you're facing with updating the firmware on your CatSniffer.

We will test a CatSniffer board on our end to replicate the issue you're experiencing. This will help us identify any potential device-specific issues and find a solution for you.

We appreciate your patience as we work to resolve this matter.

Marcelol52 commented 9 months ago

So I did only the way sending UF2 to media using pressing twice on reset . Media windows is closing the I made the boot loader sequence , the led 4 is blinking I send python command python cc2538-bsl.py -e -w -v -p COM8 sniffer_fw_Catsniffer_v3.x.hex Opening port COM8, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file Connecting to target... ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' once I have this error I have led 4 blinking and led 1 fixed I saw on the net , we could install zadig driver like rtl-sdr SDR Is there a special configuration of serial port because port setting is 128000 and python is sending 500000 baud rate here is more details : Opening port COM8, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file For more solid firmware type auto-detection, install python-magic. Please see the readme for more details. Connecting to target... sending synch sequence Traceback (most recent call last): File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 1195, in if not cmd.sendSynch(): ^^^^^^^^^^^^^^^ File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 372, in sendSynch return self._wait_for_ack("Synch (0x55 0x55)", 2) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\PB\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 265, in _wait_for_ack raise CmdException("Timeout waiting for ACK/NACK after '%s'" CmdException: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' best regards Le ven. 29 sept. 2023 à 20:10, Marcelo Arredondo @.> a écrit : Hi, Just to clarify a bit more, the .UF2 process is just another way to load the SerialPassthroughwithboot.ino firmware (or any other available firmware) to the RP2040, you do not need to also do it on the Arduino IDE. The swiping pattern indicates the cc1352 is in bootloader mode (as long as the LED 4 is turned OFF). Are you putting the cc1352 in bootloader mode when running the python commands? Does it give the same error running the first command to open the port? <python cc2538-bsl.py -p COM08> Can you share the complete error code? — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3GDFDQXQK462QORKLX44FIRANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

Hi,

Try to follow this tutorial on our wiki to restore the cc1352 chip on your board. Sometimes after loading a firmware the bootloader might get stuck and erasing the memory fixes the issue. After that try to use the python tool to flash the firmware again. If you ecounter any issues with the tutorial do not hesitate to comment here again.

Good luck!

fe8769a commented 9 months ago

Before try on with cc1352 reset . Let make sure on catsniffer status led . When I put catsniffer on USB . I have top up led fixed and bottom down blinking , PC recognize as raspi pico on usb . peripherical serial USB on COM9 . What is this state ? good or faulty ? Using sequence reset1 boot release reset and boot , the bottom down led is blinking After sending .hex file with cc2538-bsl and having the error Timeout waiting for ACK/NACK after 'Synch (0x55 0x55) 3 bottom down leds are on and le 4th is blinking

If catsniffer is in error please explain the way to reset (this tutorial)

Thanks

Marcelol52 commented 9 months ago

Hi,

The LED pattern you discribe is not a 'faulty' one, but it does mean that the cc1352 is not going into bootloader mode. If you have SerialPassthroughwithboot.ino.elf.uf2 on the RP2040, after putting the cc1352 in bootloader mode, LED 4 should stop blinking and the other 3 LED's should be doing a swiping pattern. To put the cc1352 in bootloader mode, press and hold the BOOT1 button, tap the RESET1 button and then finally release the BOOT1 button. If it doesn't work the first time, try doing it a bit slower. You have to see the swipping patter and LED 4 should be OFF. If the cc1352 is not on bootloader mode, you will keep getting the error Timeout waiting for ACK/NACK after 'Synch (0x55 0x55). If that does not work try with ereasing the chip as I mentioned before.

Good luck!

fe8769a commented 9 months ago

tutorial of catsniffer is faulty

./configure --disable-werror --enable-picoprobe

need to install gcc .

need also find the way to install libusb 1.0.26 then configure is ok

make is no ok with the following errors 👍

/bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Wpointer-arith -g -O2 -o src/openocd.exe src/main.o src/libopenocd.la -lws2_32 ./jimtcl/libjim.a libtool: link: gcc -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Wpointer-arith -g -O2 -o src/openocd.exe src/main.o src/.libs/libopenocd.a -lusb-1.0 -lws2_32 ./jimtcl/libjim.a /usr/lib/gcc/x86_64-pc-msys/13.2.0/../../../../x86_64-pc-msys/bin/ld: cannot find -lusb-1.0: No such file or directory collect2: error: ld returned 1 exit status make[2]: [Makefile:3223: src/openocd.exe] Error 1 make[2]: Leaving directory '/home/fe8769/openocd' make[1]: [Makefile:5319: all-recursive] Error 1 make[1]: Leaving directory '/home/fe8769/openocd' make: *** [Makefile:2176: all] Error 2

So I can't reset my catsniffer , I can't put some firmwares .

Marcelol52 commented 9 months ago

Hi,

We are sorry you are experiencing this issues, we constantly try to update our Wiki. We are currently in the porcess of a big restructure of the Wiki to add valuable details and update many things. We apreciate your patience so far.

Try following the steps in the tutorial using MSYS2 MINGW64 insted of MSYS2 MSYS. If you get the gcc error again you will just need to install it, if you need help with that let me know.

alphafox02 commented 9 months ago

Before try on with cc1352 reset . Let make sure on catsniffer status led . When I put catsniffer on USB . I have top up led fixed and bottom down blinking , PC recognize as raspi pico on usb . peripherical serial USB on COM9 . What is this state ? good or faulty ? Using sequence reset1 boot release reset and boot , the bottom down led is blinking After sending .hex file with cc2538-bsl and having the error Timeout waiting for ACK/NACK after 'Synch (0x55 0x55) 3 bottom down leds are on and le 4th is blinking

If catsniffer is in error please explain the way to reset (this tutorial)

Thanks

I have tried every way possible to get a firmware flashed on the v3 and it always ends with Timeout waiting for ACK/NACK after 'Synch (0x55 0x55). However, it just occurred to me I was not hitting reset1. So I corrected that, but I still end up with a sweeping pattern of lights towards led 4, but led 4 is still blinking as well.

Marcelol52 commented 9 months ago

Hi,

I will try to replicate this behavior with the LED's and get back to you.

lukeswitz commented 9 months ago

but I still up up with a sweeping patter of lights towards led 4, but led 4 is still blinking as well.

Had same with same error. Sent it back to reflash. Still waiting for them to fix it. Losing hope lol.

alphafox02 commented 9 months ago

I got mine back, don't lose hope yet. I will say, I've attempted to flash it more times then I'd like to admit...

alphafox02 commented 9 months ago

Hi,

I will try to replicate this behavior with the LED's and get back to you.

Good morning. After loading your v3.1 rp2040 with the serial pass through with boot, unplugging and plugging back in do you get two blinking blue lights? When you follow your recommend procedure to then enter boot mode are you getting all three leds 1-3 making a sweeping motion? Do you also get the 4th led blinking on and off? Or just 4th led off? I get the sweeping motion 1-3, but also 4th led blinking. I’ve tried numerous times at different speeds, different length usbc cables, different computers (all Linux) and each time I get the same result which seems like I’m not getting into boot loader mode. Is there perhaps any other method? If I can get perhaps the sniffle firmware loaded I can maybe do something in Linux.

Marcelol52 commented 9 months ago

"Good morning. After loading your v3.1 rp2040 with the serial pass through with boot, unplugging and plugging back in do you get two blinking blue lights? When you follow your recommend procedure to then enter boot mode are you getting all three leds 1-3 making a sweeping motion? Do you also get the 4th led blinking on and off? Or just 4th led off? I get the sweeping motion 1-3, but also 4th led blinking. I’ve tried numerous times at different speeds, different length usbc cables, different computers (all Linux) and each time I get the same result which seems like I’m not getting into boot loader mode. Is there perhaps any other method? If I can get perhaps the sniffle firmware loaded I can maybe do something in Linux."

Hi,

After loading the SerialPassthroughwithboot.ino (v3.x from the repository) to the RP2040. yuo should have D3 (LED3) static and LED4 blinking. That is the normal status and indicates the board is working fine. When putting the board in bootloader mode you should have a swiping patter going from D3 to D1 and D4 should be OFF. For getting the cc1352 on bootloader mode: press 'boot1', without releasing it tap 'reset1' you should hear the disconnect and connect sound on your OS, after that release 'boot1'. When D4 is off it means the cc1352 chip has gone into bootloader mode. At this point is where you can use the python tool (cc2538-bsl) to load the firmware to the cc1352.

The only other available method is using a JLINK or similar cJTAG programmer to load the firmware to the cc1352 using the JFlash lite software. There is also a guide for this on our Wiki.

If you want, we can schedule a videocall to get your board working with other firmwares. Let me know if this would be an option for you.

alphafox02 commented 9 months ago

A video call will be great. Once I have it working I will in turn make videos and share with others. I’m on EST time. Let me know some days/times that work and I will arrange for everything to be setup on my end.

Marcelol52 commented 9 months ago

Hi,

Our working hours go from 9 am to 5 pm CST, Monday through Friday. Let me know which would be the best time for you.

alphafox02 commented 9 months ago

"Good morning. After loading your v3.1 rp2040 with the serial pass through with boot, unplugging and plugging back in do you get two blinking blue lights? When you follow your recommend procedure to then enter boot mode are you getting all three leds 1-3 making a sweeping motion? Do you also get the 4th led blinking on and off? Or just 4th led off? I get the sweeping motion 1-3, but also 4th led blinking. I’ve tried numerous times at different speeds, different length usbc cables, different computers (all Linux) and each time I get the same result which seems like I’m not getting into boot loader mode. Is there perhaps any other method? If I can get perhaps the sniffle firmware loaded I can maybe do something in Linux."

Hi,

After loading the SerialPassthroughwithboot.ino (v3.x from the repository) to the RP2040. yuo should have D3 (LED3) static and LED4 blinking. That is the normal status and indicates the board is working fine. When putting the board in bootloader mode you should have a swiping patter going from D3 to D1 and D4 should be OFF. For getting the cc1352 on bootloader mode: press 'boot1', without releasing it tap 'reset1' you should hear the disconnect and connect sound on your OS, after that release 'boot1'. When D4 is off it means the cc1352 chip has gone into bootloader mode. At this point is where you can use the python tool (cc2538-bsl) to load the firmware to the cc1352.

The only other available method is using a JLINK or similar cJTAG programmer to load the firmware to the cc1352 using the JFlash lite software. There is also a guide for this on our Wiki.

If you want, we can schedule a videocall to get your board working with other firmwares. Let me know if this would be an option for you.

Okay I went back and checked. After loading the rp2040 with the SerialPassthroughwithboot.ino.elf.uf2 (not the uno) after double tapping the button and getting the file explorer my v3.1 has both led 3 and 4 blinking in sync. Led 3 is not static as you mentioned. Then after i do the button combo to get into boot loader mode I end up with the sweeping pattern of all leds towards led 4 and led 4 is blinking, not off. In both cases it seems different then what you are suggesting I see.

I'll set aside some time and show you as soon as possible.

Marcelol52 commented 8 months ago

Hi,

Don't worry, we can arrange the videocall when you get a chance. Let me know.

fe8769a commented 8 months ago

We are all waiting .. Do you have a discord channel ? we could send video of our actions

Le mer. 11 oct. 2023 à 18:28, Marcelo Arredondo @.***> a écrit :

Hi,

Don't worry, we can arrange the videocall when you get a chance. Let me know.

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1758067184, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV65ZTFVJIWDNZ55L4TX63CKJANCNFSM6AAAAAA5GP7MB4 . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 8 months ago

Hi,

We do not have discord channel as of now, but you can share a video of your actions through here or we can share an email address if you would like to send it there.

fe8769a commented 8 months ago

here is 2 vidéos sequences by swisstransfert provider

https://www.swisstransfer.com/d/39da5fa5-9234-4b88-afff-cdfa20849e97

Le jeu. 12 oct. 2023 à 17:47, Marcelo Arredondo @.***> a écrit :

Hi,

We do not have discord channel as of now, but you can share a video of your actions through here or we can share an email address if you would like to send it there.

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1759886183, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV5HICDVELNWSL56RFTX7AGJ3AVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJZHA4DMMJYGM . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 8 months ago

here is 2 vidéos sequences by swisstransfert provider https://www.swisstransfer.com/d/39da5fa5-9234-4b88-afff-cdfa20849e97 Le jeu. 12 oct. 2023 à 17:47, Marcelo Arredondo @.> a écrit : Hi, We do not have discord channel as of now, but you can share a video of your actions through here or we can share an email address if you would like to send it there. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV5HICDVELNWSL56RFTX7AGJ3AVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJZHA4DMMJYGM . You are receiving this because you authored the thread.Message ID: @.>

Hi,

We could not download your videos, could you share them with me through another service?

fe8769a commented 8 months ago

@.*** sent you catsniffer

2 items, 75.4 MB in total ・ Expires on 21 October, 2023

Download link: https://wetransfer.com/downloads/152a2fdcd17b2fe901a962cbba34dbce20231014132822/83ca0f5a7b3780a3256f23c541f99d8620231014132842/7fd311?trk=TRN_TDL_01&utm_campaign=TRN_TDL_01&utm_medium=email&utm_source=sendgrid

2 items

Entering_bootloader.mp4 - 33.2 MB first_usb_plug.mp4 - 42.2 MB

Get more out of WeTransfer, get Pro

About WeTransfer: https://wetransfer.com/about Help: https://wetransfer.zendesk.com/hc/en-us Legal: https://wetransfer.com/legal/terms

To make sure our emails arrive, please add @.*** to your contacts.

Marcelol52 commented 8 months ago

@. sent you catsniffer 2 items, 75.4 MB in total ・ Expires on 21 October, 2023 Download link: https://wetransfer.com/downloads/152a2fdcd17b2fe901a962cbba34dbce20231014132822/83ca0f5a7b3780a3256f23c541f99d8620231014132842/7fd311?trk=TRN_TDL_01&utm_campaign=TRN_TDL_01&utm_medium=email&utm_source=sendgrid 2 items Entering_bootloader.mp4 - 33.2 MB first_usb_plug.mp4 - 42.2 MB Get more out of WeTransfer, get Pro About WeTransfer: https://wetransfer.com/about Help: https://wetransfer.zendesk.com/hc/en-us Legal: https://wetransfer.com/legal/terms To make sure our emails arrive, please add @. to your contacts.

Hi,

Thank you for sharing your videos with us.

The LED pattern shown on the video 'first_usb_plug.mp4' indicates the board is working fine with the preloaded firmware.

In the second video 'Entering_bootloader.mp4' I can see you are pressing the 'reset1' button first, you have to press the 'boot1' button first. I will share with you a video of the button combination to get the board in bootloader mode. You will know that the board is in bootloader mode when the swiping pattern starts, this pattern will stay on until you reset the board or connect and disconnect it. If the pattern only appears once, the board did not get into bootloader mode and you will need to try again. Remember that you have to have the SerialPassthroughwithboot.ino.elf.uf2 firmware on the RP2040 for this to work.

Let me know if you are able to get the board into bootloader mode.

Video link: https://drive.google.com/file/d/1YKInd8i-U1Li84s3yXCrmlXoIWE0hj3l/view?usp=sharing

fe8769a commented 8 months ago

Hello

I follow your video . I have LED 04 blinking after the same sequence as I saw on your video but here is the result

C:\Users\fe8769\Documents\GitHub\CatSniffer\tools\cc2538-bsl>C:\Users\fe8769\AppData\Local\Programs\Python\Python311\python.exe cc2538-bsl.py -e -w -v -V -p COM9 sniffer_fw_Catsniffer_v3.x.hex Opening port COM9, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file For more solid firmware type auto-detection, install python-magic. Please see the readme for more details. Connecting to target... *** sending synch sequence Traceback (most recent call last): File "C:\Users\fe8769\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 1195, in if not cmd.sendSynch(): ^^^^^^^^^^^^^^^ File "C:\Users\fe8769\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 372, in sendSynch return self._wait_for_ack("Synch (0x55 0x55)", 2) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\fe8769\Documents\GitHub\CatSniffer\tools\cc2538-bsl\cc2538-bsl.py", line 265, in _wait_for_ack raise CmdException("Timeout waiting for ACK/NACK after '%s'" CmdException: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)' ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'

Le lun. 16 oct. 2023 à 17:59, alphafox02 @.***> a écrit :

So I did later realize my mistake, however, doing the correct combo always resulted in the inability to update the firmware.Now the bigger problem is that I followed the request for me to reflash stock firmware. I followed the guide here step by step 08. Restore the CC1352 firmwaregithub.comBut once I got here flash erase_sector 0 0 lastIt did not complete properly and now when I power on the CatSniffer I get no lights. I cannot get the rp2040 to open up anymore and it only seems I have access via telnet using the guide above but can’t really do anyrhing..So now I’m stuck again. I must be unlucky. Possibly maybe I send it back to you? Maybe third time is the charm? Aaron Sent from my iPhoneOn Oct 16, 2023, at 11:45 AM, Marcelo Arredondo @.***> wrote:

@. sent you catsniffer 2 items, 75.4 MB in total ・ Expires on 21 October, 2023 Download link: https://wetransfer.com/downloads/152a2fdcd17b2fe901a962cbba34dbce20231014132822/83ca0f5a7b3780a3256f23c541f99d8620231014132842/7fd311?trk=TRN_TDL_01&utm_campaign=TRN_TDL_01&utm_medium=email&utm_source=sendgrid 2 items Entering_bootloader.mp4 - 33.2 MB first_usb_plug.mp4 - 42.2 MB Get more out of WeTransfer, get Pro About WeTransfer: https://wetransfer.com/about Help: https://wetransfer.zendesk.com/hc/en-us Legal: https://wetransfer.com/legal/terms To make sure our emails arrive, please add @. to your contacts.

Hi, Thank you for sharing your videos with us. The LED pattern shown on the video 'first_usb_plug.mp4' indicates the board is working fine with the preloaded firmware. In the second video 'Entering_bootloader.mp4' I can see you are pressing the 'reset1' button first, you have to press the 'boot1' button first. I will share with you a video of the button combination to get the board in bootloader mode. You will know that the board is in bootloader mode when the swiping pattern starts, this pattern will stay on until you reset the board or connect and disconnect it. If the pattern only appears once, the board did not get into bootloader mode and you will need to try again. Remember that you have to have the SerialPassthroughwithboot.ino.elf.uf2 firmware on the RP2040 for this to work. Let me know if you are able to get the board into bootloader mode. Video link: https://drive.google.com/file/d/1YKInd8i-U1Li84s3yXCrmlXoIWE0hj3l/view?usp=sharing

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1764800002, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV7FKCQSFTIZKQGQIXLX7VKXHAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUHAYDAMBQGI . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 8 months ago

Hi fe8769,

I can see in the output that you shared that you do not have the python-magic library, you can install it by running the command: 'pip install python-magic' It seems like the board is not getting into the bootloader mode, since you confirm the LED 4 is not turning off. This means that the wrong firmware was loaded to the board, one that does not have the option for bootloader mode in the CC1352 chip. To restore the board you will need to follow the tutorial again. For what I can see from before you got stuck installing gcc and with the make file. Follow the suggestions I shared before:

"Try following the steps in the tutorial using MSYS2 MINGW64 insted of MSYS2 MSYS. If you get the gcc error again you will just need to install it, if you need help with that let me know."

You can install gcc in MSYS2 MINGW64 using the command 'pacman -S base-devel gcc vim cmake'

If you encounter any issues please share screenshots of the errors.

fe8769a commented 8 months ago

Hello

I have an error in make command

Following this command

1.

Open MSYS2 MINGW64 and start by updating the package database and host packages with:

$ pacman -Syu

  1. After:

$ pacman -Su

  1. To complete the updating. Installing the necessary dependencies

$ pacman -S mingw-w64-x86_64-toolchain git make libtool pkg-config autoconf automake texinfo mingw-w64-x86_64-libusb

1.

To select all press enter. 2.

Close MSYS2 MINGW64 and open it again, and follow the following commands.

$ git clone https://github.com/raspberrypi/openocd.git --branch rp2040 --depth=1

$ cd openocd

$ ./bootstrap

$ ./configure --disable-werror --enable-picoprobe

  1. Execute a make

$ make

$ make make all-recursive make[1]: Entering directory '/home/fe8769/openocd' Making all in jimtcl make[2]: Entering directory '/home/fe8769/openocd/jimtcl' MKLDEXT _load-static-exts.c CC _load-static-exts.o CC jim-subcmd.o CC jim-interactive.o CC jim-format.o CC jim.o In function 'Jim_Alloc', inlined from 'Jim_ConcatObj' at jim.c:7025:21: jim.c:654:19: warning: argument 1 range [18446744071562067969, 18446744073709551615] exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=] 654 return size ? malloc(size) : NULL; ^~~~ In file included from jim.c:49: C:/msys64/mingw64/include/stdlib.h: In function 'Jim_ConcatObj': C:/msys64/mingw64/include/stdlib.h:538:17: note: in a call to allocation function 'malloc' declared here 538 void *__cdecl malloc(size_t _Size); ^~ jim.c: In function 'JimCreateProcedureCmd': jim.c:4062:5: warning: 'memset' offset [0, 71] is out of the bounds [0, 0] [-Warray-bounds=] 4062 memset(cmdPtr, 0, sizeof(*cmdPtr)); ^~~~~~~~~~ In function 'Jim_WhileCoreCommand', inlined from 'Jim_WhileCoreCommand' at jim.c:11548:12: jim.c:11561:12: warning: 'boolean' may be used uninitialized [-Wmaybe-uninitialized] 11561 if (!boolean) ^ jim.c: In function 'Jim_WhileCoreCommand': jim.c:11557:13: note: 'boolean' was declared here 11557 int boolean, retval; ^~~ CC utf8.o CC jimregexp.o CC jimiocompat.o jimiocompat.c: In function 'Jim_MakeTempFile': jimiocompat.c:124:28: warning: cast from pointer to integer of different size [-Wpointer-to-int-cas ] 124 return _open_osfhandle((int)handle, _O_RDWR _O_TEXT); ^ CC linenoise.o CC jim-win32compat.o CC jim-nosignal.o CC jim-aio.o CC jim-array.o CC jim-clock.o CC jim-eventloop.o CC jim-exec.o jim-exec.c: In function 'JimMakeErrorCode': jim-exec.c:241:72: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 241 Jim_ListAppendElement(interp, errorCode, Jim_NewIntObj(interp, (long)pid));
^ jim-exec.c:246:72: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 246 Jim_ListAppendElement(interp, errorCode, Jim_NewIntObj(interp, (long)pid));
^ jim-exec.c:274:72: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 274 Jim_ListAppendElement(interp, errorCode, Jim_NewIntObj(interp, (long)pid));
^ jim-exec.c: In function 'Jim_ExecCmd': jim-exec.c:403:74: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] 403 Jim_ListAppendElement(interp, listObj, Jim_NewIntObj(interp, (long)pidPtr[i]));
 ^

jim-exec.c: In function 'Jim_WaitCommand': jim-exec.c:615:19: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 615 | pid = waitpid((pidtype)pidarg, &status, nohang ? WNOHANG : 0); | ^ CC jim-file.o CC jim-history.o CC jim-interp.o CC jim-load.o CC jim-namespace.o CC jim-pack.o CC jim-package.o CC jim-readdir.o CC jim-regexp.o TCLEXT _glob.c CC glob.o TCLEXT _nshelper.c CC nshelper.o TCLEXT _oo.c CC oo.o TCLEXT _stdlib.c CC stdlib.o TCLEXT _tclcompat.c CC tclcompat.o TCLEXT _tree.c CC tree.o AR libjim.a CC jimsh.o TCLEXT _initjimsh.c CC initjimsh.o LINK jimsh.exe C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function JimSignalCmdDelete': /home/fe8769/openocd/jimtcl/jim-signal.c:420:(.text+0x7a): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function find_signal_by_name': /home/fe8769/openocd/jimtcl/jim-signal.c:149:(.text+0x113): undefined reference to__locale_ctype_p tr' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function do_signal_cmd': /home/fe8769/openocd/jimtcl/jim-signal.c:225:(.text+0x4d0): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : /home/fe8769/openocd/jimtcl/jim-signal.c:235:(.text+0x53b): undefined reference to sigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : /home/fe8769/openocd/jimtcl/jim-signal.c:228:(.text+0x5db): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function Jim_KillCmd': /home/fe8769/openocd/jimtcl/jim-signal.c:523:(.text+0x727): undefined reference tokill' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function Jim_AlarmCmd': /home/fe8769/openocd/jimtcl/jim-signal.c:445:(.text+0x8ee): undefined reference toualarm' collect2.exe: error: ld returned 1 exit status make[2]: [Makefile:62: jimsh.exe] Error 1 make[2]: Leaving directory '/home/fe8769/openocd/jimtcl' make[1]: [Makefile:5319: all-recursive] Error 1 make[1]: Leaving directory '/home/fe8769/openocd' make: *** [Makefile:2176: all] Error 2

Le mer. 18 oct. 2023 à 00:40, Marcelo Arredondo @.***> a écrit :

Hi fe8769,

I can see in the output that you shared that you do not have the python-magic library, you can install it by running the command: 'pip install python-magic' It seems like the board is not getting into the bootloader mode, since you confirm the LED 4 is not turning off. This means that the wrong firmware was loaded to the board, one that does not have the option for bootloader mode in the CC1352 chip. To restore the board you will need to follow the tutorial https://github.com/ElectronicCats/CatSniffer/wiki/08.-Restore-the-CC1352-firmware#restore-catsniffer-v3-with-rp2040-or-rasberrypico again. For what I can see from before you got stuck installing gcc and with the make file. Follow the suggestions I shared before:

"Try following the steps in the tutorial using MSYS2 MINGW64 insted of MSYS2 MSYS. If you get the gcc error again you will just need to install it, if you need help with that let me know."

You can install gcc in MSYS2 MINGW64 using the command 'pacman -S base-devel gcc vim cmake'

If you encounter any issues please share screenshots of the errors.

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1767304903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV2NLF7VRSYCZGFECXDX74CMXAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGMYDIOJQGM . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 8 months ago

Hi,

it seems like you are missing some of the dependencies requiered for the make command. Please run 'pacman -S mingw-w64-x86_64-toolchain git make libtool pkg-config autoconf automake texinfo mingw-w64-x86_64-libusb' again and let me know if you get any errors.

fe8769a commented 8 months ago

same error . I have already did this before posting previous message

$ make make all-recursive make[1]: Entering directory '/home/fe8769/openocd' Making all in jimtcl make[2]: Entering directory '/home/fe8769/openocd/jimtcl' LINK jimsh.exe C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function JimSignalCmdDelete': /home/fe8769/openocd/jimtcl/jim-signal.c:420:(.text+0x7a): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function find_signal_by_name': /home/fe8769/openocd/jimtcl/jim-signal.c:149:(.text+0x113): undefined reference to__locale_ctype_p tr' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function do_signal_cmd': /home/fe8769/openocd/jimtcl/jim-signal.c:225:(.text+0x4d0): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : /home/fe8769/openocd/jimtcl/jim-signal.c:235:(.text+0x53b): undefined reference to sigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : /home/fe8769/openocd/jimtcl/jim-signal.c:228:(.text+0x5db): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function Jim_KillCmd': /home/fe8769/openocd/jimtcl/jim-signal.c:523:(.text+0x727): undefined reference tokill' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function Jim_AlarmCmd': /home/fe8769/openocd/jimtcl/jim-signal.c:445:(.text+0x8ee): undefined reference toualarm' collect2.exe: error: ld returned 1 exit status make[2]: [Makefile:62: jimsh.exe] Error 1 make[2]: Leaving directory '/home/fe8769/openocd/jimtcl' make[1]: [Makefile:5319: all-recursive] Error 1 make[1]: Leaving directory '/home/fe8769/openocd' make: *** [Makefile:2176: all] Error 2

I did also a previous compil of " jimsh.exe"

Same result

Did you test using ubuntu linux ?

Le ven. 20 oct. 2023 à 21:23, Marcelo Arredondo @.***> a écrit :

Hi,

it seems like you are missing some of the dependencies requiered for the make command. Please run 'pacman -S mingw-w64-x86_64-toolchain git make libtool pkg-config autoconf automake texinfo mingw-w64-x86_64-libusb' again and let me know if you get any errors.

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1773282264, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV4XC6YAYCA42722QX3YALFSNAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTGI4DEMRWGQ . You are receiving this because you authored the thread.Message ID: @.***>

--

alphafox02 commented 8 months ago

I would be very careful even after you build this, I followed the steps and was able to build. Got all the way to telnet and issuing the command after loading the rp2040 with the necessary file. Once I ran the commands in telnet it did not produce the result the repo shows and ultimately I now have a CatSniffer that I plug in and it shows no lights at all. I can no longer double tap and have the file explorer pop up on the rp2040 and I can only use the openocd to telnet the device.

Marcelol52 commented 8 months ago

same error . I have already did this before posting previous message $ make make all-recursive make[1]: Entering directory '/home/fe8769/openocd' Making all in jimtcl make[2]: Entering directory '/home/fe8769/openocd/jimtcl' LINK jimsh.exe C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function JimSignalCmdDelete': /home/fe8769/openocd/jimtcl/jim-signal.c:420:(.text+0x7a): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function find_signal_by_name': /home/fe8769/openocd/jimtcl/jim-signal.c:149:(.text+0x113): undefined reference to__locale_ctype_p tr' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function do_signal_cmd': /home/fe8769/openocd/jimtcl/jim-signal.c:225:(.text+0x4d0): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : /home/fe8769/openocd/jimtcl/jim-signal.c:235:(.text+0x53b): undefined reference to sigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : /home/fe8769/openocd/jimtcl/jim-signal.c:228:(.text+0x5db): undefined reference tosigaction' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function Jim_KillCmd': /home/fe8769/openocd/jimtcl/jim-signal.c:523:(.text+0x727): undefined reference tokill' C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/13.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe : libjim.a(jim-signal.o): in function Jim_AlarmCmd': /home/fe8769/openocd/jimtcl/jim-signal.c:445:(.text+0x8ee): undefined reference toualarm' collect2.exe: error: ld returned 1 exit status make[2]: [Makefile:62: jimsh.exe] Error 1 make[2]: Leaving directory '/home/fe8769/openocd/jimtcl' make[1]: [Makefile:5319: all-recursive] Error 1 make[1]: Leaving directory '/home/fe8769/openocd' make: [Makefile:2176: all] Error 2 I did also a previous compil of " jimsh.exe" Same result Did you test using ubuntu linux ? Le ven. 20 oct. 2023 à 21:23, Marcelo Arredondo @.> a écrit : Hi, it seems like you are missing some of the dependencies requiered for the make command. Please run 'pacman -S mingw-w64-x86_64-toolchain git make libtool pkg-config autoconf automake texinfo mingw-w64-x86_64-libusb' again and let me know if you get any errors. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV4XC6YAYCA42722QX3YALFSNAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTGI4DEMRWGQ . You are receiving this because you authored the thread.Message ID: @.***>

Hi fe8769a,

I am really sorry for my confusion. If you are using ubuntu you do not need to download MSYS2, you can follow the steps using the linux terminal. MSYS2 is used for Windows systems, I had understood since you mentioned having Windows systems that you were following the steps on a Windows system.

The process is basically the same in the linux terminal, you just need to do some syntx changes.

sudo apt-get install openocd cd openocd sudo apt-get install make sudo apt-get install libtool sudo apt-get install git sudo apt-get install pkg-config sudo apt-get install autoconf sudo apt-get install automake sudo apt-get install libusb-1.0-0-dev git clone https://github.com/raspberrypi/openocd.git --branch rp2040 --depth=1 cd openocd ./bootstrap ./configure --disable-werror --enable-picoprobe make openocd -f interface/cmsis-dap.cfg -c "transport select jtag" -f target/ti_cc13x2.cfg -s tcl On another terminal window: telnet localhost 4444 halt flash erase_sector 0 0 last exit

Be carfull with the notes on the wiki about modifying the .cfg file, you will need to add the adapter speed and change the id as mentioned there.

i just tried it in my ubuntu machine and it worked. Let me know if you have any issues. Sorry this thread is getitng so long.

Marcelol52 commented 8 months ago

I would be very careful even after you build this, I followed the steps and was able to build. Got all the way to telnet and issuing the command after loading the rp2040 with the necessary file. Once I ran the commands in telnet it did not produce the result the repo shows and ultimately I now have a CatSniffer that I plug in and it shows no lights at all. I can no longer double tap and have the file explorer pop up on the rp2040 and I can only use the openocd to telnet the device.

Hi Alphafox,

If you loaded the free_dap_Catsniffer.uf2 the method to put the board into bootloader mode will change from a double tap to: press 'reset1', press 'sw1', release 'reset1' , release 'sw1'.

After that you will be able to load the serial pass through with boot again and work with your catsniffer as normal.

This is one of the things we are adding to the wiki soon, sorry.

Let me know if you are able to load the firmware again

alphafox02 commented 8 months ago

Okay this is helpful info. I even just went back after changing your directions slightly above. You mention sudo apt install openocd - I think you meant to leave that off? But anyways, on Linux I got this

telnet localhost 4444
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> halt
target halted due to debug-request, current mode: Thread                                                  
xPSR: 0x41000000 pc: 0x100009ac msp: 0x20000fdc      
> flash erase_sector 0 0 last
DAP transaction stalled (WAIT) - slowing down
erased sectors 0 through 87 on flash bank 0 in 2.087785s

> exit
Connection closed by foreign host.

So now I guess I will load the serial pass though with boot again, but I don't understand what the above erasing of flash was for?

alphafox02 commented 8 months ago

Holy cow, I think after all this maybe I'm back in business...

dragon@dragon:~/Downloads/CatSniffer/firmware/V3.x/CC1352P7/sniffer_fw_cc1252P_7$ python3 ../../../../tools/cc2538-bsl/cc2538-bsl.py -e -w -v sniffer_fw_Catsniffer_v3.x.hex
Opening port /dev/ttyACM0, baud 500000
Reading data from sniffer_fw_Catsniffer_v3.x.hex
Firmware file: Intel Hex
Connecting to target...
CC1350 PG2.0 (7x7mm): 704KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x000AFFD8
Primary IEEE Address: 00:12:4B:00:29:B6:82:63
    Performing mass erase
Erasing all main bank flash sectors
    Erase done
Writing 720896 bytes starting at address 0x00000000
Write 208 bytes at 0x000AFF308
    Write done                                
Verifying by comparing CRC32 calculations.
    Verified (match: 0x52c24bf8)

I should've flashed maybe sniffle though...

alphafox02 commented 8 months ago

And now I've flashed sniffle and have results!!! Perfect start to my weekend.

fe8769a commented 8 months ago

alphafox02 is lucky but I will succeed !!

First I run under ubuntu . I have better results - compilation is OK

I copy the firmware on card following this

Located at the following link: free_dap_Catsniffer.uf2 https://github.com/ElectronicCats/CatSniffer/releases/download/v3.1/free_dap_catsniffer.uf2 based in the project free-dap https://github.com/ataradov/free-dap

That is working fine

I modify the cfg file /home/fe8769/Desktop/Catsniffer/erase/openocd/tcl/target/ti_cc13x2.cfg

With the content :

#

Texas Instruments CC13x2 - ARM Cortex-M4

#

http://www.ti.com

#

set CHIPNAME cc13x2 set JRC_TAPID 0x0BB4102F set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg]

I start the command

openocd -f interface/cmsis-dap.cfg -c "transport select jtag" -f target/ti_cc13x2.cfg -s tcl Open On-Chip Debugger 0.11.0 Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html jtag cortex_m reset_config vectreset

Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : Using CMSIS-DAPv2 interface with VID:PID=0x6666:0x9930, serial=7F17C5F9 Info : CMSIS-DAP: SWD Supported Info : CMSIS-DAP: JTAG Supported Info : CMSIS-DAP: FW Version = 2.0.0 Info : CMSIS-DAP: Serial# = 7F17C5F9 Info : CMSIS-DAP: Interface Initialised (JTAG) Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 0 nTRST = 0 nRESET = 1 Info : CMSIS-DAP: Interface ready Info : clock speed 4000 kHz Info : cmsis-dap JTAG TLR_RESET Info : cmsis-dap JTAG TLR_RESET Info : JTAG tap: cc13x2.jrc tap/device found: 0x1bb7702f (mfg: 0x017 (Texas Instruments), part: 0xbb77, ver: 0x1) Warn : JTAG tap: cc13x2.jrc UNEXPECTED: 0x1bb7702f (mfg: 0x017 (Texas Instruments), part: 0xbb77, ver: 0x1) Error: JTAG tap: cc13x2.jrc expected 1 of 1: 0x0bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x0) Error: Trying to use configured scan chain anyway... Warn : Bypassing JTAG setup events due to errors Info : starting gdb server for cc13x2.cpu on 3333 Info : Listening on port 3333 for gdb connections

I open the telnet and I have error

telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger

halt Target not examined yet

flash erase_sector 0 0 last Target not examined yet auto_probe failed

when trying send the firmware again :

python3 cc2538-bsl.py -e -w -v sniffer_fw_Catsniffer_v3.x.hex Opening port /dev/ttyACM0, baud 500000 Reading data from sniffer_fw_Catsniffer_v3.x.hex Your firmware looks like an Intel Hex file Connecting to target... ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'

let me know

Le sam. 21 oct. 2023 à 12:49, alphafox02 @.***> a écrit :

And now I've flashed sniffle and have results!!! Perfect start to my weekend.

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1773750636, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3J7DZTIQDJVNIGPXLYAOSC7AVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTG42TANRTGY . You are receiving this because you authored the thread.Message ID: @.***>

--

alphafox02 commented 8 months ago

Change this

set CHIPNAME cc13x2 set JRC_TAPID 0x0BB4102F set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg

to this

set CHIPNAME cc13x2 set JRC_TAPID 0x1bb7702f set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg

However you may end up with a failure to erase. Give me about 2 hours and I’ll have a YouTube video up.

fe8769a commented 8 months ago

here the result :

telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger

halt target halted due to debug-request, current mode: Thread xPSR: 0x61000000 pc: 0x1002e2ec psp: 0x20003b70 flash erase_sector 0 0 last DAP transaction stalled (WAIT) - slowing down cc26xx: Flash operation failed failed erasing sectors 0 to 87

Is it good ?

Le lun. 23 oct. 2023 à 16:21, alphafox02 @.***> a écrit :

Change this

set CHIPNAME cc13x2 set JRC_TAPID 0x0BB4102F set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg

to this

set CHIPNAME cc13x2 set JRC_TAPID 0x1bb7702f set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg

However you may end up with a failure to erase. Give me about 2 hours and I’ll have a YouTube video up.

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1775316960, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3HNA3DO45LX5HSXB3YAZ4QNAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZVGMYTMOJWGA . You are receiving this because you authored the thread.Message ID: @.***>

--

Marcelol52 commented 8 months ago

Change this

set CHIPNAME cc13x2 set JRC_TAPID 0x0BB4102F set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg

to this

set CHIPNAME cc13x2 set JRC_TAPID 0x1bb7702f set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg

However you may end up with a failure to erase. Give me about 2 hours and I’ll have a YouTube video up.

It is great to hear that you were able to erase the memory. At this point your should be able to change the cc1352 firmware as much as you want using the python tool. If you get the timeout error again, just do the erasing process again and you should be good to go.

Marcelol52 commented 8 months ago

here the result : telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger halt target halted due to debug-request, current mode: Thread xPSR: 0x61000000 pc: 0x1002e2ec psp: 0x20003b70 flash erase_sector 0 0 last DAP transaction stalled (WAIT) - slowing down cc26xx: Flash operation failed failed erasing sectors 0 to 87 Is it good ? Le lun. 23 oct. 2023 à 16:21, alphafox02 @.> a écrit : Change this set CHIPNAME cc13x2 set JRC_TAPID 0x0BB4102F set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg to this set CHIPNAME cc13x2 set JRC_TAPID 0x1bb7702f set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg However you may end up with a failure to erase. Give me about 2 hours and I’ll have a YouTube video up. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3HNA3DO45LX5HSXB3YAZ4QNAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZVGMYTMOJWGA . You are receiving this because you authored the thread.Message ID: @.>

The output you are sharing is telling you that nothing was erased in the memory. You should get an output like the one alphafox02 shared. Try rebooting your system and trying again. I will try to replicate the issue and let you know if I find a solution.

telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger

halt target halted due to debug-request, current mode: Thread
xPSR: 0x41000000 pc: 0x100009ac msp: 0x20000fdc
flash erase_sector 0 0 last DAP transaction stalled (WAIT) - slowing down erased sectors 0 through 87 on flash bank 0 in 2.087785s exit Connection closed by foreign host

fe8769a commented 8 months ago

I power of/ON computer . I have no more leds ON . I can't do any sequence like copy firmware on media

and the result

telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger

halt target halted due to debug-request, current mode: Thread xPSR: 0x61000000 pc: 0x1000118e msp: 0x11001ff0 flash erase_sector 0 0 last DAP transaction stalled (WAIT) - slowing down cc26xx: Flash operation failed failed erasing sectors 0 to 87

Le lun. 23 oct. 2023 à 17:48, Marcelo Arredondo @.***> a écrit :

here the result : telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger halt target halted due to debug-request, current mode: Thread xPSR: 0x61000000 pc: 0x1002e2ec psp: 0x20003b70 flash erase_sector 0 0 last DAP transaction stalled (WAIT) - slowing down cc26xx: Flash operation failed failed erasing sectors 0 to 87 Is it good ? Le lun. 23 oct. 2023 à 16:21, alphafox02 @.

> a écrit : … <#m5441878621919429515> Change this set CHIPNAME cc13x2 set JRC_TAPID 0x0BB4102F set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg to this set CHIPNAME cc13x2 set JRC_TAPID 0x1bb7702f set WORKAREASIZE 0x7000 adapter speed 4000 source [find target/ti_cc26x0.cfg However you may end up with a failure to erase. Give me about 2 hours and I’ll have a YouTube video up. — Reply to this email directly, view it on GitHub <#49 (comment) https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1775316960>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDV3HNA3DO45LX5HSXB3YAZ4QNAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZVGMYTMOJWGA https://github.com/notifications/unsubscribe-auth/AIANDV3HNA3DO45LX5HSXB3YAZ4QNAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZVGMYTMOJWGA . You are receiving this because you authored the thread.Message ID: @.>

The output you are sharing is telling you that nothing was erased in the memory. You should get an output like the one alphafox02 shared. Try rebooting your system and trying again. I will try to replicate the issue and let you know if I find a solution.

telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger

halt target halted due to debug-request, current mode: Thread xPSR: 0x41000000 pc: 0x100009ac msp: 0x20000fdc flash erase_sector 0 0 last DAP transaction stalled (WAIT) - slowing down erased sectors 0 through 87 on flash bank 0 in 2.087785s exit Connection closed by foreign host

— Reply to this email directly, view it on GitHub https://github.com/ElectronicCats/CatSniffer/issues/49#issuecomment-1775499259, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIANDVY2IVIU7IMO7QGRSPDYA2GUHAVCNFSM6AAAAAA5GP7MB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZVGQ4TSMRVHE . You are receiving this because you authored the thread.Message ID: @.***>

--