Proxmark3 community

db69

Contributor

Registered: 2019-05-21

Posts: 6

re-compiling for BlueShark

Hi,
I tried to recompile on Windows 10 (Proxspace 64 bit). Everyhing runs well until I try to connect through BT : although there are 2 BT COM ports visible in Peripheral Management (ports 8 & 9), the pm3 doesn't connect.  When trying to connect the client to COM 8, it replies with "illegal port"; on COM9 it replies "unable to communicate".  On COM 7 (physical USB serial port), it works).
When using an older 32 bit version I got from Github (iceman-32-20190501-05f43ba610d225174c923cd504e6d45a23e0a6a3) it works.
Any suggestion ?
Thanks

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: re-compiling for BlueShark

that would be you didn't put latest RRG repo compiled with BT enabled on your device,  like the instructions says....

https://github.com/RfidResearchGroup/pr … --flashing

db69

Contributor

Registered: 2019-05-21

Posts: 6

Re: re-compiling for BlueShark

I followed instructions to the letter to be sure : re-installed Proxspace, git clone RRG repo, uncommented BT add on in Platform file, Make clean Make -j8, Autobuild and Flash all.  re-installed unsigned 64 bit driver...
So I'm a little puzzled...  The add-on seems to be correctly compiled and flashed, as it creates 2 BT COM ports.  The client however does not seem to recognize them.  Is there something else in addition to the makefile.platform on client side to indicate it compiles for BlueShark ?

db69

Contributor

Registered: 2019-05-21

Posts: 6

Re: re-compiling for BlueShark

after reboot of everything once more, now the BT port is recognized, but receive a lot of error messages :

[=] Output will be flushed after every print.
         
[=] Using UART port COM8           
[=] Communicating with PM3 over FPC UART           
[=] PM3 UART serial baudrate: 115200
         
pm3 --> hf se         
[=] Checking for known tags...
         
[!] Received packet frame error variable part too short? 119/295         
[!] Received packet OLD frame payload error too short? 54/534         
[!] Received packet OLD frame payload error too short? 104/534         
[!] Received packet frame preamble too short: 3/10         
[!] Received packet OLD frame payload error too short? 531/534         
[!] Received packet OLD frame payload error too short? 508/534         
[!] Received packet OLD frame payload error too short? 16/534         
[!] Received packet OLD frame payload error too short? 505/534         
[!] Received packet OLD frame payload error too short? 19/534         
[!] Received packet OLD frame payload error too short? 509/534         
[!] Received packet OLD frame payload error too short? 15/534         
[=] You can cancel this operation by pressing the pm3 button         

I must have done something wrong, but what ?

db69

Contributor

Registered: 2019-05-21

Posts: 6

Re: re-compiling for BlueShark

redid the complete roue, and know when flashing, I receive pm3 not found message, although there is some level of communication : 2 of the red lights of the pm light up : bl bl bl bl 0 R 0 R

iceman

Administrator

Registered: 2013-04-25

Posts: 9,537

Website

Re: re-compiling for BlueShark

good, we can scratch firmware off the list. 
Now it seems its just connection between device and your laptop(?)   Try turn the glass side against your laptop bluetooth to get clear signal and test to see what works best for you.

hf search / lf search uses large transfers which is error-prone.  Try the individual info commands.   In any case, it looks like it works.