Properly resetting the W5100 during propeller reboot??
Hi, i was wondering if anyone knew the proper way to "reset" the W5100??
i am using "W5100.spin" for control and the "W5100.spin" module imports "Spi5100CounterPasm.spin"
my top level sets up the W5100 using DHCP, but sometimes when connections are lost, after trying a few other things i command the propeller to Reboot.
on power on the propeller executes the command:
wiz.HardReset(WIZ_RESET)
where "WIZ_RESET" == 14.
but for some reason the device will not accept an ip and will keep trying forever untill the actual power to the w5100 is cycled, this tells me there is a register somewhere i am not clearing or initializing correctly.
could someone please help me to understand what i need to clear in order for the device to be configurable by DHCP after the Prop reboots??
Cheers!
i am using "W5100.spin" for control and the "W5100.spin" module imports "Spi5100CounterPasm.spin"
my top level sets up the W5100 using DHCP, but sometimes when connections are lost, after trying a few other things i command the propeller to Reboot.
on power on the propeller executes the command:
wiz.HardReset(WIZ_RESET)
where "WIZ_RESET" == 14.
but for some reason the device will not accept an ip and will keep trying forever untill the actual power to the w5100 is cycled, this tells me there is a register somewhere i am not clearing or initializing correctly.
could someone please help me to understand what i need to clear in order for the device to be configurable by DHCP after the Prop reboots??
Cheers!
![:D :D](https://forums.parallax.com/resources/emoji/lol.png)
Comments
Also, post your code.
one thing i do notice, if i rest my finger on top of the W5100 while its trying to acquire an ip address its seems to be slightly hotter than when its actually connected and communicating. maybe theres a thermal issue caused from some kind of heavy looping somewhere???
regardless, heres the source:
(if you are going to run this code, be sure to put it into simulation mode or it will block where it tries to read in serial data)
Please see the attached unit test. This test invokes the DHCP and DNS clients followed by an HTTP request to /finance/historical and finally a reboot. The test ran for 15 minutes without error.