virtualabs / btlejack

Bluetooth Low Energy Swiss-army knife
MIT License
1.87k stars 196 forks source link

Garbage on the command line while determining channel map #81

Open MKesenheimer opened 1 year ago

MKesenheimer commented 1 year ago

When sniffing with btlejack, I get garbage on the command line while determining the channel map:

btlejack -v -f 0x5065621d
BtleJack version 2.1

[i] Detected sniffers:
 > Sniffer #0: fw version 2.1
 > Sniffer #1: fw version 2.1
 > Sniffer #2: fw version 2.1

[i] Synchronizing with connection 0x5065621d ...
✓ CRCInit = 0x927d26
| Determining channel map@> b'c=1'
/ Determining channel map@> b'c=25'
/ Determining channel map@> b'_'
- Determining channel map@> b'_'
\ Determining channel map@> b'c=2'
/ Determining channel map@> b'c=26'
| Determining channel map@> b'_'
/ Determining channel map@> b'_'
@> b'c=3'
@> b'c=13'
@> b'c=27'
@> b'_'
@> b'_'
@> b'_'
/ Determining channel map@> b'c=4'
| Determining channel map@> b'c=28'
- Determining channel map@> b'_'
/ Determining channel map@> b'_'
| Determining channel map@> b'c=5'
| Determining channel map@> b'c=29'
/ Determining channel map@> b'_'
/ Determining channel map@> b'_'
\ Determining channel map@> b'c=6'
\ Determining channel map@> b'_'
@> b'c=30'
@> b'_'
@> b'c=14'
@> b'c=7'
@> b'_'
| Determining channel map@> b'_'
@> b'c=31'
/ Determining channel map@> b'_'
- Determining channel map@> b'c=8'
- Determining channel map@> b'_'
/ Determining channel map@> b'c=32'
\ Determining channel map@> b'_'
/ Determining channel map@> b'c=9'
@> b'c=33'
@> b'c=15'
@> b'_'
@> b'_'
/ Determining channel map@> b'_'
\ Determining channel map@> b'c=34'
| Determining channel map@> b'_'
\ Determining channel map@> b'c=35'
@> b'c=10'
@> b'_'
@> b'c=16'
@> b'_'
/ Determining channel map@> b'_'
- Determining channel map@> b'c=36'
| Determining channel map@> b'_'
/ Determining channel map@> b'c=11'
@> b'_'
@> b'c=17'
\ Determining channel map@> b'_'
/ Determining channel map@> b'_'
- Determining channel map@> b'c=18'
- Determining channel map@> b'_'
\ Determining channel map@> b'_'
\ Determining channel map@> b'c=19'
| Determining channel map@> b'_'
/ Determining channel map@> b'c=20'
- Determining channel map@> b'_'
\ Determining channel map@> b'c=21'
/ Determining channel map@> b'_'
| Determining channel map@> b'c=22'
/ Determining channel map@> b'_'
- Determining channel map@> b'c=23'
\ Determining channel map@> b'_'

Is this normal behavior?

virtualabs commented 1 year ago

Well, the -v option was introduced to provide a more verbose output including some debug messages coming from the firmware that runs on the Micro:bit... And yes, it messes up with the normal output. Just remove -v and everything should be allright !

Note to self: rename -v option to --debug or something similar