Hi,
we have a customer who has a Rls23 (NTDK20AB CPU with NTDK34AA_R10 Flashboot) and in this system the CPU has damaged.
My colleague has brought a newest NTDK20FA CPU, and he installed the Rls 23 software, and after that he put the NTDK34AA_r10 (Rls23) Flashboot to the NTDK20FA CPU. (The original was NTDK34FA_R06) I know it is not compatible, but he did it already.
Since that time - before the "Power up self test passed" message - the processor rebooting cyclically,
and not react to the Control-I or to the FBUG (NTDK34FA CPU) :
Meridian Small System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34AA_r10 dev2.43
Reset Reason: C0, 0 - Reset due to Power Up
SRAM: 128 kBytes
DRAM: 16 MBytes, speed=60 ns
Security ID:XXXXXXXX type: NT_STD
Backup Flash: 1572 kBytes
Program Store: 32 MBytes
Flash Drive: 8 MBytes
Expansion board #1 installed.
Expansion board #2 not installed.
Ethernet MAC address: 00.00.75.4A.72.01
PCMCIA card installed in drive A.
PCMCIA card not installed in drive B.
*** To invoke install setup program from PCMCIA enter CONTROL-I ***
Executing power up self tests
Meridian Small System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34AA_r10 dev2.43
Reset Reason: A0, 0 - Reset due to H/W Watchdog
SRAM: 128 kBytes
DRAM: 16 MBytes, speed=60 ns
Security ID:XXXXXXXX type: NT_STD
Backup Flash: 1572 kBytes
Program Store: 32 MBytes
Flash Drive: 8 MBytes
Expansion board #1 installed.
Expansion board #2 not installed.
Ethernet MAC address: 00.00.75.4A.72.01
PCMCIA card installed in drive A.
PCMCIA card not installed in drive B.
*** To invoke install setup program from PCMCIA enter CONTROL-I ***
Executing power up self tests
Meridian Small System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34AA_r10 dev2.43
Have you any suggestion how could we put back the NTDK34FA_R06 Flashboot, and boot up the NTDK20FA CPU ?
I erased the Security ID from the messages, but i don't know why we can't see the System ID while the Dongle is there on the CPU ?
Thanks in advance
Zoltán
we have a customer who has a Rls23 (NTDK20AB CPU with NTDK34AA_R10 Flashboot) and in this system the CPU has damaged.
My colleague has brought a newest NTDK20FA CPU, and he installed the Rls 23 software, and after that he put the NTDK34AA_r10 (Rls23) Flashboot to the NTDK20FA CPU. (The original was NTDK34FA_R06) I know it is not compatible, but he did it already.
Since that time - before the "Power up self test passed" message - the processor rebooting cyclically,
and not react to the Control-I or to the FBUG (NTDK34FA CPU) :
Meridian Small System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34AA_r10 dev2.43
Reset Reason: C0, 0 - Reset due to Power Up
SRAM: 128 kBytes
DRAM: 16 MBytes, speed=60 ns
Security ID:XXXXXXXX type: NT_STD
Backup Flash: 1572 kBytes
Program Store: 32 MBytes
Flash Drive: 8 MBytes
Expansion board #1 installed.
Expansion board #2 not installed.
Ethernet MAC address: 00.00.75.4A.72.01
PCMCIA card installed in drive A.
PCMCIA card not installed in drive B.
*** To invoke install setup program from PCMCIA enter CONTROL-I ***
Executing power up self tests
Meridian Small System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34AA_r10 dev2.43
Reset Reason: A0, 0 - Reset due to H/W Watchdog
SRAM: 128 kBytes
DRAM: 16 MBytes, speed=60 ns
Security ID:XXXXXXXX type: NT_STD
Backup Flash: 1572 kBytes
Program Store: 32 MBytes
Flash Drive: 8 MBytes
Expansion board #1 installed.
Expansion board #2 not installed.
Ethernet MAC address: 00.00.75.4A.72.01
PCMCIA card installed in drive A.
PCMCIA card not installed in drive B.
*** To invoke install setup program from PCMCIA enter CONTROL-I ***
Executing power up self tests
Meridian Small System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34AA_r10 dev2.43
Have you any suggestion how could we put back the NTDK34FA_R06 Flashboot, and boot up the NTDK20FA CPU ?
I erased the Security ID from the messages, but i don't know why we can't see the System ID while the Dongle is there on the CPU ?
Thanks in advance
Zoltán