So this seem inexplicable :<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
| tempted by the recent changes to qi, I flashed<br>
| qi-s3c2442-andy_28eb5ac9c9426e5f.udfu<br></div>
| <<a href="http://people.openmoko.org/andy/qi-s3c2442-andy_28eb5ac9c9426e5f.udfu" target="_blank">http://people.openmoko.org/andy/qi-s3c2442-andy_28eb5ac9c9426e5f.udfu</a>>to<div><br>
| my FR - but after that I was not able to boot anymore, neither with<br>
| NAND or NOR! Only switching battery, charger & usb-connection numerous<br>
| times and trying again yielded two successful NOR bootmenus in about 80<br>
| tries, the second of which I gladly took to reflash U-boot.<br>
|<br>
| Any explanation how this can happen ? I thought NOR could in no way be<br>
| harmed by flashing?<br>
<br></div>
I would guess the problems are the known ones around low battery on<br>
GTA02, when you charged enough to get a stable boot you would have been<br>
equally fine to go on with Qi if that's the case.</blockquote><div><br>Actually the battery was 100% full ( double checked before and immediately after regaining access, so this is ruled out.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
NOR boot can theoretically be affected by some things like inherited PMU<br>
state but in fact on GTA02 I use NOR U-Boot to update Qi during<br>
development and there's no problems. Besides there's nothing funny<br>
about Qi PMU settings.<br><div></div></blockquote><div> That's how I updated, too , so then I really wonder what had happened - and how to get back in a sane state should this happen again!<br></div></div><br>Stefan<br>