Linux distro on NSA325

[raumzeit]

This seems to be due to the MCU watchdog getting deactivated while the mv88f6281 watchdog gets initialized. Along with all the other hardware support, they patched this into the 2.6.31.8 kernel:

$this->bbcode_second_pass_code('', '
#if defined(CONFIG_ZYXEL_NSA325)
/* MCU tries to reset CPU every 1 minute for avoiding system hang before watchdog timer is enabled.
* If watchdog timer is enabled, then set GPIO 14 to tell MCU that do not reset CPU.
*/
regValue = MV_REG_READ(0x1010);
regValue |= BIT14;
MV_REG_WRITE(0x10100, regValue);
#endif

')

So the system is forced to reset if the mv88f6281 watchdog is initialized too late

[WarheadsSE]

Yes, I've read that part of the kernel code, and even hard-hit that WHILE in uboot. Doesn't stop it. Hence my fight with it. I know the problem The solution is being a bit of a red-headed step-child. Can't have it doing that to spinning disks after all.

[prokrypt]

I have this random (and possibly stupid) idea that if you can figure out a way to control the fan, you'll be able to stop the watchdog.
I wonder why...

[WarheadsSE]

Because they are both tied to the external MCU. However, I can't say that will do much good. I've manually hit the gpio 14 to out, high, which should trip it, but it still resets in the same time frame.

[prokrypt]

Perhaps that external MCU needs to be bitbanged into submission a certain way?

edit: s/compliance/submission/

[WarheadsSE]

That's the question..
- What is that way?
- How is it attached?
- Why doesn't it listen?

$this->bbcode_second_pass_quote('WarheadsSE', '-') What is that way?

[WarheadsSE]

Correct, you are, especially with the 325.

[d1dd1]

any news here ?

[WarheadsSE]

My home office was hit by a tree a while back. I have only begun to get it set back up fully. I will resume work on this shortly.