MIFARE data display not updated or cleared | Mifare卡界面数据区无法被清空 #28

Kadalia · 2022-03-12T09:19:51Z

Hello,
Nice work ... no ... great work !!
But, I have a minor issues.
The "clear" data button from "File" section is not working. (it works fine for keys).
The "load" data button doesn't update the Data list display.
v0.2.4 Compiled for ARM
Thank you !

wh201906 · 2022-03-12T10:13:40Z

Thanks for your feedback!

The "clear" data button from "File" section is not working. (it works fine for keys).

Yes I reproduced this bug. I will fix it in the next release. If you need to fix it on your own, open the mainwindow.cpp in src/ui/, find MainWindow::on_MF_File_clearButton_clicked(), then replace the code at line 718

else if(ui->MF_File_keyButton->isChecked())

with

else if(ui->MF_File_dataButton->isChecked())

wh201906 · 2022-03-12T10:17:38Z

The "load" data button doesn't update the Data list display.

I can't reproduce this bug. Both the binary data file and the text data file can be loaded on V0.2.4. Did you choose "Data" in the "File" section before loading the data?

Kadalia · 2022-03-12T10:23:06Z

Thank you !
Clear Data button is now working.
The Load button also ... hummm ... I was tired :-)
Closing

wh201906 · 2022-03-12T10:25:38Z

@Kadalia Does the "Load" button work after the fix?

Kadalia · 2022-03-12T10:45:05Z

Yes :-) I thing it was working before the fix already

wh201906 · 2022-03-12T10:45:52Z

Ok

Add deploy helper(unfinished)

Pebrok · 2022-10-16T09:24:48Z

Hi,
I'm still stuck on MAc with the app not connecting to the Proxmark3, even though the terminal app can connect to it.
I changed the file path as recommanded, but nothing happens. What am I missing?

wh201906 · 2022-10-16T10:00:00Z

How about checking Keep the client active even the PM3 hardware is disconnected

Pebrok · 2022-10-16T16:04:52Z

Hi, thanks for your reply. I did, but still no connection. 1-Should I change something on the client path, on top? what path should I put? To which file : proxmark3GUI.app or what else ? (I am on Mac) 2-For the config file : should i link to « config_official.json" or to "config_rrgv4.13.json » ? It does work with terminal, so the connection is working… It drives me crazy. Thanks for your help. [cid:DE5C69D7-9F7B-464A-B663-90966FBE2C95] ***@***.******@***.***> Le 16 oct. 2022 à 12:00, Self Not Found ***@***.******@***.***>> a écrit : How about checking Keep the client active even the PM3 hardware is disconnected — Reply to this email directly, view it on GitHub<#28 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIWFSNHHR2RO7RAWG4XFYLWDPG2VANCNFSM5QRUP3XA>. You are receiving this because you commented.Message ID: ***@***.***>

wh201906 · 2022-10-17T15:37:43Z

1-Should I change something on the client path, on top? what path should I put? To which file : proxmark3GUI.app or what else ? (I am on Mac)

The client path is the same as the command to open proxmark3. If you start proxmark3 in terminal by typing proxmark3 or path/to/the/proxmark3, then you should type it into the Client Path

2-For the config file : should i link to « config_official.json" or to "config_rrgv4.13.json » ?

The current config_rrgv4.13 should be fine.

Pebrok · 2022-10-18T19:26:57Z

Hi Still stuck wit no connection of the pm3 I changed what you said. As I am using terminal, I only put pm3 (the word I used to connect to my Pm3 on terminal) Any other idea? Do you see anything missing? Is there any files I should put in the same folder? [cid:2FB6BA58-EBD3-49A7-9281-701948403A07] Le 17 oct. 2022 à 17:37, Self Not Found ***@***.******@***.***>> a écrit : 1-Should I change something on the client path, on top? what path should I put? To which file : proxmark3GUI.app or what else ? (I am on Mac) The client path is the same as the command to open proxmark3. If you start proxmark3 in terminal by typing proxmark3 or path/to/the/proxmark3, then you should type it into the Client Path 2-For the config file : should i link to « config_official.json" or to "config_rrgv4.13.json » ? The current config_rrgv4.13 should be fine. — Reply to this email directly, view it on GitHub<#28 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIWFSNYZ55BUKHSEOBVQX3WDVXFFANCNFSM5QRUP3XA>. You are receiving this because you commented.Message ID: ***@***.***>

wh201906 · 2022-10-19T02:27:26Z

Since I don't have a Mac, I can't test what happens. However, I guess this GUI works with v4.14831 on macOS because someone has run it and post the screenshot in README.
Can you get proxmark3.log in the directory of executable? Does it reports any errors or warnings?

Pebrok · 2022-10-19T09:58:59Z

Hi, and thanks again for your help. Here is my log from yesterday: -it doesn't seem to follow the path I'm giving on the setting page (to the config_rrgv4.13.json file). It is on a path I can't find. (./proxmark3) [=] Session log /Users/cedricchadapaux/.proxmark3/logs/log_20221018.txt [=] Output will be flushed after every print. [+] loaded from JSON file /Users/cedricchadapaux/.proxmark3/preferences.json [=] Using UART port tty.usbmodemiceman1 [!] ERROR: invalid serial port tty.usbmodemiceman1 [?] Try the shell script `./pm3 --list` to get a list of possible serial ports [=] Session log /Users/cedricchadapaux/.proxmark3/logs/log_20221018.txt [+] loaded from JSON file /Users/cedricchadapaux/.proxmark3/preferences.json [=] Using UART port /dev/tty.usbmodemiceman1 [=] Session log /Users/cedricchadapaux/.proxmark3/logs/log_20221018.txt [+] loaded from JSON file /Users/cedricchadapaux/.proxmark3/preferences.json [=] Using UART port /dev/tty.usbmodemiceman1 [!!] ERROR: cannot parse command line. We got /dev/tty.usbmodemiceman1 as port and now we got also: /dev/tty.usbmodemiceman1 [=] Session log /Users/cedricchadapaux/.proxmark3/logs/log_20221018.txt [+] loaded from JSON file /Users/cedricchadapaux/.proxmark3/preferences.json [=] Using UART port /dev/tty.usbmodemiceman1 [=] Session log /Users/cedricchadapaux/.proxmark3/logs/log_20221018.txt [+] loaded from JSON file /Users/cedricchadapaux/.proxmark3/preferences.json [=] Using UART port /dev/tty.usbmodemiceman1

…

________________________________ De : Self Not Found ***@***.***> Envoyé : 19 octobre 2022 02:27 À : wh201906/Proxmark3GUI ***@***.***> Cc : Pebrok ***@***.***>; Comment ***@***.***> Objet : Re: [wh201906/Proxmark3GUI] MIFARE data display not updated or cleared | Mifare卡界面数据区无法被清空 (Issue #28) Since I don't have a Mac, I can't test what happens. However, I guess this GUI works with v4.14831 on macOS because someone has run it and post the screenshot in README. Can you get proxmark3.log in the directory of executable? Does it reports any errors or warnings? — Reply to this email directly, view it on GitHub<#28 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIWFSPSLRWMKGYJURROVW3WD5MBTANCNFSM5QRUP3XA>. You are receiving this because you commented.Message ID: ***@***.***>

wh201906 · 2022-10-19T12:15:01Z

Could you please clean the log, then run the GUI, then post the new log there?

Pebrok · 2022-10-21T18:41:49Z

I am already on V4.14831 Here is the terminal connexion info: [=] Session log /Users/XXXX/.proxmark3/logs/log_20221021.txt [+] loaded from JSON file /Users/XXXX/.proxmark3/preferences.json [=] Using UART port /dev/tty.usbmodemiceman1 [=] Communicating with PM3 over USB-CDC ██████╗ ███╗ ███╗█████╗ ██╔══██╗████╗ ████║╚═══██╗ ██████╔╝██╔████╔██║ ████╔╝ ██╔═══╝ ██║╚██╔╝██║ ╚══██╗ ██║ ██║ ╚═╝ ██║█████╔╝ ╚═╝ ╚═╝ ╚═╝╚════╝ [ Iceman ❄️ ] Release v4.14831 - Frostbit [ Proxmark3 RFID instrument ] [ CLIENT ] RRG/Iceman/master/v4.14831 2022-01-11 19:17:19 compiled with............. Clang/LLVM Apple LLVM 13.1.6 (clang-1316.0.21.2) platform.................. OSX / x86_64 Readline support.......... present QT GUI support............ present native BT support......... absent Python script support..... absent Lua SWIG support.......... present Python SWIG support....... absent [ PROXMARK3 ] firmware.................. PM3 GENERIC I don’t have any proxmark3.log file in my Mac. Le 19 oct. 2022 à 04:27, Self Not Found ***@***.******@***.***>> a écrit : Since I don't have a Mac, I can't test what happens. However, I guess this GUI works with v4.14831 on macOS because someone has run it and post the screenshot in README. Can you get proxmark3.log in the directory of executable? Does it reports any errors or warnings? — Reply to this email directly, view it on GitHub<#28 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIWFSPSLRWMKGYJURROVW3WD5MBTANCNFSM5QRUP3XA>. You are receiving this because you commented.Message ID: ***@***.***>

wh201906 · 2022-10-22T01:43:10Z

Can you find the log file at <somewhere>/.proxmark3/logs/log_<date>.txt?

Pebrok · 2022-10-22T07:56:25Z

Hi, I finally found the log file (hidden on Mac…) [+] loaded from JSON file /Users/xxxx/.proxmark3/preferences.json [=] Using UART port /dev/tty.usbmodemiceman1 [=] Communicating with PM3 over USB-CDC [ Proxmark3 RFID instrument ] [ CLIENT ] RRG/Iceman/master/v4.14831 2022-01-11 19:17:19 compiled with............. Clang/LLVM Apple LLVM 13.1.6 (clang-1316.0.21.2) platform.................. OSX / x86_64 Readline support.......... present QT GUI support............ present native BT support......... absent Python script support..... absent Lua SWIG support.......... present Python SWIG support....... absent [ PROXMARK3 ] firmware.................. PM3 GENERIC [ ARM ] bootrom: RRG/Iceman/master/v4.14831 2022-01-11 19:17:19 os: RRG/Iceman/master/v4.14831 2022-01-11 19:17:19 compiled with GCC 10.2.1 20201103 (release) [ FPGA ] LF image built for 2s30vq100 on 2020-07-08 at 23:08:07 HF image built for 2s30vq100 on 2020-07-08 at 23:08:19 HF FeliCa image built for 2s30vq100 on 2020-07-08 at 23:08:30 [ Hardware ] --= uC: AT91SAM7S512 Rev B --= Embedded Processor: ARM7TDMI --= Internal SRAM size: 64K bytes --= Architecture identifier: AT91SAM7Sxx Series --= Embedded flash memory 512K bytes ( 53% used ) Le 22 oct. 2022 à 03:43, Self Not Found ***@***.******@***.***>> a écrit : Can you find the log file at <somewhere>/.proxmark3/logs/log_<date>.txt? — Reply to this email directly, view it on GitHub<#28 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABIWFSIUI2PS3IVRU3HRTZLWENBDRANCNFSM5QRUP3XA>. You are receiving this because you commented.Message ID: ***@***.***>

wh201906 · 2022-10-23T14:17:52Z

The log seems fine. Does the GUI shows Connected at first, then changes to Disconnected?

Pebrok · 2022-10-23T18:26:36Z

Not, it has never shown "connected". Do you think I should change the path to the driver , same as the one the proxmark3 uses, and to the Json file? Or else? xxx Le 23 oct. 2022 à 16:18 +0200, Self Not Found ***@***.***>, a écrit :

…

The log seems fine. Does the GUI shows Connected at first, then changes to Disconnected? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

wh201906 · 2022-10-24T03:00:31Z

I think the log shows the client works properly. I don't know what else can be wrong.

Kadalia closed this as completed Mar 12, 2022

wh201906 added a commit that referenced this issue Mar 12, 2022

Fix bug #28

5a0f0d3

Add deploy helper(unfinished)

wh201906 added the bug Something isn't working label Apr 3, 2022

wh201906 changed the title ~~MIFARE data display not updated or cleared~~ MIFARE data display not updated or cleared | Mifare卡界面数据区无法被清空 Apr 3, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MIFARE data display not updated or cleared | Mifare卡界面数据区无法被清空 #28

MIFARE data display not updated or cleared | Mifare卡界面数据区无法被清空 #28

Kadalia commented Mar 12, 2022

wh201906 commented Mar 12, 2022 •

edited

Loading

wh201906 commented Mar 12, 2022 •

edited

Loading

Kadalia commented Mar 12, 2022

wh201906 commented Mar 12, 2022

Kadalia commented Mar 12, 2022

wh201906 commented Mar 12, 2022

Pebrok commented Oct 16, 2022

wh201906 commented Oct 16, 2022

Pebrok commented Oct 16, 2022 via email

wh201906 commented Oct 17, 2022

Pebrok commented Oct 18, 2022 via email

wh201906 commented Oct 19, 2022

Pebrok commented Oct 19, 2022 via email

wh201906 commented Oct 19, 2022

Pebrok commented Oct 21, 2022 via email

wh201906 commented Oct 22, 2022

Pebrok commented Oct 22, 2022 via email

wh201906 commented Oct 23, 2022

Pebrok commented Oct 23, 2022 via email

wh201906 commented Oct 24, 2022

MIFARE data display not updated or cleared | Mifare卡界面数据区无法被清空 #28

MIFARE data display not updated or cleared | Mifare卡界面数据区无法被清空 #28

Comments

Kadalia commented Mar 12, 2022

wh201906 commented Mar 12, 2022 • edited Loading

wh201906 commented Mar 12, 2022 • edited Loading

Kadalia commented Mar 12, 2022

wh201906 commented Mar 12, 2022

Kadalia commented Mar 12, 2022

wh201906 commented Mar 12, 2022

Pebrok commented Oct 16, 2022

wh201906 commented Oct 16, 2022

Pebrok commented Oct 16, 2022 via email

wh201906 commented Oct 17, 2022

Pebrok commented Oct 18, 2022 via email

wh201906 commented Oct 19, 2022

Pebrok commented Oct 19, 2022 via email

wh201906 commented Oct 19, 2022

Pebrok commented Oct 21, 2022 via email

wh201906 commented Oct 22, 2022

Pebrok commented Oct 22, 2022 via email

wh201906 commented Oct 23, 2022

Pebrok commented Oct 23, 2022 via email

wh201906 commented Oct 24, 2022

wh201906 commented Mar 12, 2022 •

edited

Loading

wh201906 commented Mar 12, 2022 •

edited

Loading