This faq will be useful: https://synthiam.com/Tutorials/FAQ.aspx#5

Or this: https://synthiam.com/Tutorials/FAQ.aspx#9

Solved

OK, Great! Glad your up and running. However please share what the solution was. It would be nice to see what it finally turned out to be.

My EZB sometimes freezes, shuts down the WIFI and the red LED on it turns on. However I'm not using a i2c port. What causes this on my setup is when I try to send a command through a UART port without it being initiated or a command that is not structured right. I have to power cycle the EZB, reconnect and make sure the Uart port is initiated or the command is written properly.

I thought maybe you were trying to send a corrupt command through the i2c port. My other guess would be a bad cable or connection. confused

Dave, all ezb's and electronics will freeze if using a peripheral that has not been initialized, not just yours - so that's normal. There's a very short and simple logical process that needs to be executed before a peripheral is active. Think of it as remembering to put the key in the lock before twisting. The order of events is necessary to initialize the hardware. That wakes up and configures the hardware. Without doing so, the hardware will lock up.

You will see this most often with communication hardware - because communication "waits" for something to happen. The same would apply if I told you to wait for ever to read these 5 words: Apple, orange, chicken, Sky,

Thanks for the education. Good to know. I figured it was something like this. I wasn't reporting on an issue, just comparing simular behavior. It's good to see it explained in an understandable way though. Thanks!

Did you like my joke at the end? I was proud of that wit!

@Dj Ok... what's the last word?... gotta' know!... Apple, orange, chicken, Sky, ? Hurry before I timeout...

That's the thing - you will never time out as a hardware peripheral