Strange behavior w5500 with xmega on SPI [SOLVED]

Question

I am developing an another magical library for w5500. For the most of time the chip works just fine, the spi signals looks normal, but suddently my chip got bricked? whan i try to send any command the chip does not respond at all (sends only zeros, when it should write data) even why i tried read VERSIONR. the other odd thing is that before the MISO sends acorgingly 0x01, 0x02, 0x03 as a response to write request, but now i get only 0x00, 0x00, 0x08 0x00…etc? what does this 0x08 mean? here is my oscillogram: 111832×1200 99.1 KB

Eugeny · Answer

LVY: my chip got bricked Totally bricked, or it recovers after reset/power cycle? LVY: what does this 0x08 mean? No idea, but sound wrong for SPI transfer. But not all zeros means there’s something at the other end There could be numerous causes for such bad behavior - oscillator stops working, you get issue with SPI protocol, you start multibyte data transfer command and it does not finish properly etc. LVY: here is my oscillogram: You attached it in wrong way, not accessible. Try again.

Eugeny · Answer

LVY: power cycle do not do a thing. Not sure I understood - sounds like your W5500 is totally dead? There could be cases when chip is locked, and usually this condition is cleared after power off and power on.

LVY · Answer

Eugeny: sounds like your W5500 is totally dead? the oscillogram in the first post is taken right after the 8h unpowered chip. (the first packet after powering on). so it seems that chip is locked internally. (or maybe i start it up to fast or to slow? first packet is send just about 1,5s after powering on, maybe there is issue?

LVY · Answer

ok, in desperation i hookup the module to arduino uno , and upload an serwer example, and after few restarts chip unlocks itself and working again i think i can close the tread now.