Skip to content
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

Bootloop while testing the example file #2

Open
svstoichkov opened this issue Oct 22, 2023 · 4 comments
Open

Bootloop while testing the example file #2

svstoichkov opened this issue Oct 22, 2023 · 4 comments

Comments

@svstoichkov
Copy link

svstoichkov commented Oct 22, 2023

Hi, I am trying to get the example working with a Wiegand26 reader. I have D0 connected to P13 and D1 to P12. I am getting a bootloop. Here is the log:

19:36:57.651 -> ets Jun 8 2016 00:22:57
19:36:57.651 ->
19:36:57.651 -> rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
19:36:57.651 -> configsip: 0, SPIWP:0xee
19:36:57.651 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
19:36:57.699 -> mode:DIO, clock div:1
19:36:57.699 -> load:0x3fff0030,len:1184
19:36:57.699 -> load:0x40078000,len:13260
19:36:57.699 -> load:0x40080400,len:3028
19:36:57.699 -> entry 0x400805e4
19:36:58.818 -> Wiegand26 - Inicialized
19:36:58.818 -> Wiegand26 - Disconnected
19:36:58.818 -> Wiegand26 - Inicialized
19:36:58.867 -> Wiegand26 - Disconnected
19:36:58.867 -> Wiegand26 - Wiring problem
19:36:58.867 -> Wiegand2Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1).
19:36:59.150 ->
19:36:59.150 -> Core 1 register dump:
19:36:59.150 -> PC : 0x4008ab56 PS : 0x00060135 A0 : 0x80089ace A1 : 0x3ffbf06c
19:36:59.150 -> A2 : 0x3ffc57d0 A3 : 0x3ffbce0c A4 : 0x00000004 A5 : 0x00060123
19:36:59.150 -> A6 : 0x00060123 A7 : 0x00000001 A8 : 0x3ffbce0c A9 : 0x00000019
19:36:59.150 -> A10 : 0x3ffbce0c A11 : 0x00000019 A12 : 0x3ffc2334 A13 : 0x00060123
19:36:59.191 -> A14 : 0x007bf2f8 A15 : 0x003fffff SAR : 0x0000000a EXCCAUSE: 0x00000006
19:36:59.191 -> EXCVADDR: 0x00000000 LBEG : 0x400863c9 LEND : 0x400863d9 LCOUNT : 0xfffffff8
19:36:59.191 -> Core 1 was running in ISR context:
19:36:59.191 -> EPC1 : 0x400dab4f EPC2 : 0x00000000 EPC3 : 0x00000000 EPC4 : 0x00000000
19:36:59.191 ->
19:36:59.191 ->
19:36:59.191 -> Backtrace: 0x4008ab53:0x3ffbf06c |<-CORRUPTED
19:36:59.191 ->
19:36:59.191 ->
19:36:59.191 -> Core 0 register dump:
19:36:59.191 -> PC : 0x4008aceb PS : 0x00060035 A0 : 0x800896f7 A1 : 0x3ffbea1c
19:36:59.238 -> A2 : 0x3ffbf2f8 A3 : 0xb33fffff A4 : 0x0000abab A5 : 0x00060023
19:36:59.238 -> A6 : 0x00060021 A7 : 0x0000cdcd A8 : 0x0000abab A9 : 0xffffffff
19:36:59.238 -> A10 : 0x00000000 A11 : 0x00000000 A12 : 0x3ffc214c A13 : 0x00000007
19:36:59.238 -> A14 : 0x007bf2f8 A15 : 0x003fffff SAR : 0x0000001d EXCCAUSE: 0x00000006
19:36:59.238 -> EXCVADDR: 0x00000000 LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000
19:36:59.238 ->
19:36:59.238 ->
19:36:59.238 -> Backtrace: 0x4008ace8:0x3ffbea1c |<-CORRUPTED
19:36:59.238 ->
19:36:59.238 ->
19:36:59.285 ->
19:36:59.285 ->
19:36:59.285 -> ELF file SHA256: 8c79d0b6d79a0e87
19:36:59.285 ->
19:36:59.380 -> Rebooting...

I'd appreciate any help.

@jvondrus
Copy link
Owner

Hello, which board do you using?
It's looks as pin assigned problem (sharing with some internal function, like Serial RX/TX).

@svstoichkov
Copy link
Author

I use NodeMCU-32S

@jvondrus
Copy link
Owner

Try another pin combination, it's looks that P12 is not compatible with that.

@jvondrus
Copy link
Owner

jvondrus commented Nov 3, 2023

Hello, how it's looks?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants