-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work #1
Comments
hello, #define PIN_NUM_MISO 25 #define PIN_NUM_RST 14 |
Hi, I already used the same pins that you've showed, but don't work. |
I subscribe to this question. The same problem. The numbers of the GPIO connections and connections were checked. The request for the firmware version of the module returns "0x00". The module is in the "power down" state. |
The logic analyzer shows that the correct module commands and data come to the module terminals. So I suspect that the problem is in the module itself. |
I figured out the reason why the module did not respond to requests. |
I have added the extra functions to getting UID and serial printing all the block values. This is the link for extra added functions : https://github.com/anuragmandal/ESPIDF-INTERFACE-MFRC522?files=1 |
I tried this lib, but it doesn't work.
RC522 isn't recognized.
`I (174) cpu_start: App cpu up.
I (192) heap_init: Initializing. RAM available for dynamic allocation:
I (199) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (205) heap_init: At 3FFB2A50 len 0002D5B0 (181 KiB): DRAM
I (211) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (217) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (224) heap_init: At 400892D8 len 00016D28 (91 KiB): IRAM
I (230) cpu_start: Pro cpu start user code
I (248) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
Is connected device MFRC522 ? If yes, check the wiring again.
Restarting in 5 seconds...
Restarting in 4 seconds...
Restarting in 3 seconds...
Restarting in 2 seconds...
Restarting in 1 seconds...
Restarting in 0 seconds...
Restarting Now.
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:5756
load:0x40078000,len:0
load:0x40078000,len:13904
entry 0x40078fd8
I (28) boot: ESP-IDF v3.1-dev-386-g7d13e3f 2nd stage bootloader
I (29) boot: compile time 16:58:57
I (29) boot: Enabling RNG early entropy source...
I (35) boot: SPI Speed : 40MHz
I (39) boot: SPI Mode : DIO
I (43) boot: SPI Flash Size : 4MB
I (47) boot: Partition Table:
I (50) boot: ## Label Usage Type ST Offset Length
I (58) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (65) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (73) boot: 2 factory factory app 00 00 00010000 00100000
I (80) boot: End of partition table
I (84) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x081c0 ( 33216) map
I (105) esp_image: segment 1: paddr=0x000181e8 vaddr=0x3ffb0000 size=0x021f8 ( 8696) load
I (108) esp_image: segment 2: paddr=0x0001a3e8 vaddr=0x40080000 size=0x00400 ( 1024) load
`
The text was updated successfully, but these errors were encountered: