I know this is an old thread, but it has some useful information in it, so I’ll append rather than starting my own for now.
We seem to be having the same problem here, and I’ve used the information Balkanaut provided and attempted to characterise the problem further.
We’ve had several prototype and pre-production units out in test in Australian plants, and this week we were meant to send some off to plants in Canada and Brazil for evaluation, and hopefully start getting some orders in. However we are getting the same sort of failure to start problems, which is a real show-stopper.
Our system uses USB, so we are using COM1 for debugging, with the LPMODE link open. This seems to be an essential part of the problem. On power-up a system will usually boot correctly, but occasionally it won’t start. When this happens, neither repeated RESET or power-cycling will get it going. Whether we get a good boot or not seems a bit random, I don’t know if it is the 70% : 30% ratio Balkanaut reports, but it is certainly more likely than not to boot ok, but when it fails then it fails many times in a row.
Hopefully the problem has been resolved by now, if so I’d really like to hear about it. If not, here is what I have found.
Following on Balanaut’s good information, I’ve been running test after test while monitoring the COM1 port via TeraTerm.
When we get a good boot, we see:
Ready.
Estimated Network RAM usage: 129667 (bytes)
ip address from interface info: 192.168.1.200
mac addrress from interface info: 0.1a.f1.0.42.d
EMX
Version: 4.1.8.0
Debug: COM1
LCD: 320x240
IP: 192.168.1.200
MAC: 00.1A.F1.00.42.0D
Managed heap size: 13041664
Custom heap size: 1048576
.NetMF v4.1.2821.0
EMX, Build Date:
Dec 22 2011 16:27:20
ARM Compiler version 410561
TinyCLR (Build 4.1.2821.0)
Starting…
Created EE.
Started Hardware.
followed by some MSdbg info in binary or another baud rate, then info on loading of libraries and assemblies, including the application, followed by
Ready.
and the system starts. running.
When we get a bad boot, we get nothing at all. No diagnostics, no messages, nothing. Hit RESET, still nothing. Power off, batteries out. Power up again. Still nothing.
However, if I hold Up/Down/Select when I reset or power cycle, I get the GHI loader prompt, same if I enter the %%%%. And if I hold Up/Down, I get the TinyBooter.
From either of these, reset or power cycle still goes to the “locked up” state, nothing happening. But entering R from the GHI loader, or pressing Select from the TinyBooter, results in the application starting up!
From this I assume that the system is proceeding through the GHI Loader and TinyBooter, but no further. It isn’t going on to load the application, but it also isn’t giving the TinyBooter prompt. Something is causing it to lock in this state, something that isn’t cleared by reset or power-down.
That the application is still in a runnable state is shown by the fact that either GHI Loader or TinyBooter can run it when manually prompted. And after this is done, we are generally back to staring up normally each time, at least for a while.
Hopefully the above may be enough of a clue to diagnose the problem, if not let me know what more would help.
Gus, you mentioned you suspected a floating pin in Balkanaut’s case, which pin could be responsible for these symptoms?
Thanks for any help,
David