OVL0306 for 4 hours now

[rpneal44]

I've been stuck in OVL0306 for right at 4 hours now. I suspect I'm going to have to schedule an INI. What'd I do wrong, folks??? I have a CS1K, Rel 7.5 on which I was doing some PRI maintenance. Essentially I whad replaced a TMDI card, enbl the DCH then the DGTL loop. I then went to LD 48 to enable the TMDI (probably did this backwards), I got this:

>ld 48
LNK000
.enl tmdi 44 0 2
MSDL006

.
TMDI108 TMDI 44 0 2 T1E1 BASE

TMDI300 44 0 2 FROM: SYS DSBL - SELF TESTING TO: SYS DSBL - SELFTESTS PASSE
D
TIME: 09:32:52

TMDI300 44 0 2 FROM: SYS DSBL - SELFTESTS PASSED TO: SYS DSBL - BOOT LOADIN
G
TIME: 09:32:52

OVL021 IDLE

SDL100 BUSY

OVL021 IDLE

SDL100 BUSY

OVL021 BKGD

SDL100 BUSY

TIM000 09:32 18/12/2012 CPU 1

SDL000 T1E1 (TMDI 44 0 2), VERSION 19, BKGD MODE.
18/12/2012 09:32:57 LOG0006 CLAN: Slot: 2, Card Type: TMDI (66), Signaling Type:
A10 (2), Map Type: 1

XMI002 44 0 2 TMDI

TMDI300 44 0 2 FROM: SYS DSBL - BOOT LOADING TO: ENBL
TIME: 09:32:56

SDL7117 0000004B 00000003 0000A55A

TMDI108 TMDI 44 0 2 DITI

LNK000
.enl tmdi 17
MSDL001

.enl tmdi 44 0 2
MSDL006

.enl tmdi 14
MSDL001

.
TRK136 48 0 10 3
*
.*
.*
.*
ABORTING DOWNLOAD...

>ld 48

OVL306


Phil, the Phriendly Phone Man

 

[BkMesser]

It looks like it is stuck somewhere in the firmware download. I have had to ini older releases to get the tty back.

 

[Reusser]

An INI will clear and will probably be the end result.

In the mean time try this

LD 48 susp <-- this will suspend (hopefully) whatever it is stuck trying to do. As soon as you exit load it may start again.

When you get into LD 48
Disable TMDI
to a rst tmdi 44 0 2
wait about 5 min then
enl tmdi 44 0 2 fdl

 

[janaya]

and is you use the susp portion of the command, it will eventually ini anyways. Sometimes you just gotta kick it.

 

[janaya]

I should clarify. If you use it continuously before you can schedule your INI, it will eventually INI on itself. Happened to me a couple time on 7.5.

 

[Firebird Scrambler]

Unable to access any overlays on call server, OVL306 given on TTY. This was the result of a failed FDLU to an M3903 telset in my case, I suspect pertinent to all M3900 range of phones however.
After accessing load 32 by using the suspension command and an FWVU is run against the affected TN you get 'PSDL IS NOT IDLE' message

Fix:
Use the suspend command to access ld 32, use fdlc to cancel the suspended command, disable & enable the affected card and re-commence a subseqent FDLU.
This time, in my case, the download was successful.

OVL0306 This Overlay can not be active during Peripheral Software Download (PSDL).
Action:
1. Wait until PSDL is complete.
2. Use the SUSP command to suspend the PSDL and load the required program
(LD xx SUSP). Use SUSP with caution.
You may have to LD 32 again after using the SUSP command to gain full access


All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[curtismo]

I had the latter issue (lockup during M3900 fw upgrade) right after upgrading to 7.5 - but only when trying to upgrade 3905 sets. After having to INI twice (why not try it again ) to free up rhe TTY ended up just doing each of them as forced (FDLF).