tschak909 Posted November 21, 2019 Author Share Posted November 21, 2019 right now, the firmware must be paired with its test program, as I am explicitly writing trimmed down versions to test specific commands. Timing seems to be marginal, and in order to diagnose, we'll need to bring the debugging messages out in a printable form to see what's actually going on. If there is anything I would ask of everybody in this thread. Yup, I know everybody's excited, I don't want to kill that. I do ask that everybody is patient, as we are still working out how to debug issues. In order to avoid the blorpy boot message mess that barks out the serial port when the ESP is powered on, we swap serial pins at setup(). This does mean that the debug messages go out a pair of pins that are normally unused and unconnected, and you have to have something connected to them. @Mr Robot's latest board design has a header to expose the two debug serial pins, and that will be available on the next spin. Hopefully @mozzwald can provide some info on how to connect to existing boards. If it sounds like I am keeping hands off the hardware, it's because I am.. I am deliberately concentrating on the software, and leaving the hardware work to far more competent people -Thom Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.