Yes, another bugfix in the CPU emulation.

It can probably be worked around, in p1_w:
m_maincpu->space(AS_PROGRAM).write_byte(0, 0xff);