> > > I forgot to mention that it seems that HS OMAP or something is > > > ceasing the operation just few seconds after bootup. Initfs gets > > > more scripts executed but Debian from mtdblock4 hangs just in init. > > > > That is an odd statement. Are you commenting about an EMU/HS chip > > resetting during startup? > > > Not resetting but the device seems to just stop during the process. > Only idea what came to mind that probably HS OMAP in N810 WiMAX is > causing this.
This is understandable actually. Especially if you don't have some kind of reset sequence in your power chip linked up. For instance on 3430 + T2 you need to add a reset sequence script into T2's internal memory. If you don't and you have CPUFREQ (dvfs) running, you can reboot at a time when the voltage is to low. The ROM code expects a nominal (1.2v) voltage at reset time. So when the DPLL spins up you can lock up and die. BTW, this also kills the a 'reboot' command which ultimately just does a warm reset sequence with a prcm write. ... actually in 2420 there are also errata around when its safe to issue a prcm based reset, this can also get you depending on your device. This deals with the need to be in bypass at the time of the write. > > There is a secure watch dog when needs to be taken care of and if you > > program it right. Generally your initial secure driver or stub ppa > > will take care of this. > > > Secure driver at least was missing in this trial what is indeed found > in our release :-) That would do it. You need to take care of a couple bits else it won't make it. This is doubly true on 3430 as your full or stub security driver needs to do a bit more. Regards, Richard W. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
