On Wed, Mar 1, 2017 at 10:41 AM, Matthijs van Duin matthijsvanduin@gmail.com wrote:
On 1 March 2017 at 04:36, Michael Mrozek EvilDragon@openpandora.org wrote:
Am Tue, 28 Feb 2017 20:14:45 +0100 hat Matthijs van Duin matthijsvanduin@gmail.com geschrieben:
I already had observed that there is some "memory effect" which has something to do with how fast and in which sequence power is (re)applied and so far I thought that the Palmas backup (supercap) has something to do with it.
Ah there's a supercap too? I hadn't even stopped to think about that one.. I've quite often seen strange memory effects, or "bistability" of some sort where it either boots fine (into u-boot at least) repeatedly, or utterly fails (often even without any message on console) repeatedly.
Hm, that's very weird and we should try to find out what happens here.
I agree. I've been working on getting the early debug console for SPL working (u-boot's equivalent to earlycon) so we can get console output at any time. It's not working yet, but I'm fairly sure I know why so I'll give that another try.
I've also tried to do that and the best I've managed is what I've sent with patch 0003 to get it just after setup_early_clocks(), so there's something needed in that function.
It doesn't really sound like a hardware instability issue if the hardware works fine once you managed to boot it up.
No, I really have no idea yet what's going on there, or which stateful components are involved (since problems even seem to be somewhat persistent across power cycling by long-pressing the power button).
Note that I'm also however suffering from plain instability, I've never been able to run Linux for very long.
Hmm that's not good, I thought only my broken board is suffering from that. I do always get the "U-Boot SPL" message though, where it hangs after that is random ranging from just after printing the "U-Boot SPL" line to somewhere in the middle of kernel booting.
GraÅžvydas