What's new

Sega Model 2B CRX Boot Leds, Errors etc

mypinballs

mypinballs

Professional
Joined
Aug 18, 2019
Messages
210
Reaction score
403
Location
Leeds UK
Looking for some info/advice on the leds for sega model 2b cry hardware. I have a non booting board that always presents the same Led sequence at boot, so i am trying to work out if theres any sanity to any of the leds or if sega just put 8 leds in it for laughs!!

Boot up sequence is

power on

- all LEds on
- all leds off
- top 4 red leds on and lower red led in-between 2 green ones (led2?)
- top 4 leds off and lower red led in-between 2 green ones on

Also, to add to the nightmare i did get it to partially start once after being on for a good few hours.

Then both green leds lit and it said

Power off and wait awhile!!
Co-Processor Error.
50E044 = Error Status

and

50E048 = Error Status


Thanks Sega for the helpful advice NOT ..... lol

Power input is all good as i built some nice new cables with the proper JST headers to the PSU. 5v checks out nice and stable and the 3.3 v is also ok.

I guess this board is scrap but i am posting here to see what else could be tried and what can be learnt.

I really wanted to run indy 500 in my daytona cabinet ha
 
Also 'model 2B cry' was a typo lol, but i think it fits pretty well so ill leave it... Hahahahah
 
So i made some progress but only very limited and 1 time the board booted to an attract screen but then crashed. There wasnt any 3d modelling going on though just the text.

It does seem very very picky about the power supply used and the voltage level

The process as checked in Mame is :

1) if the boot starts then he screen is cleared to solid blue instead of garbage
2) sometime the co processor error pops up and then is cleared
3) then a sound initialise message is displayed
4) then the legal text/warning screen appears
5) then attract starts with sega logo and insert coins/credits etc

IMG_2021.jpg
IMG_2022.jpg
IMG_2023 2.jpg





What i want to do is try to get back to the warning screen then press test and try to run some rom /ram tests to see what happens

Main board still might be scrap at this point
 
Made some more changes to the power supply and leads and i can get the sound initialize screen pretty much every time now.

Things have now changed to it i leave it off for awhile then it will boot to the legal page and then the first attract screen before crashing.

If i press the test button in time then it will load the test page but wont enter any tests, crashes on main screen

IMG_2024.jpg


I kind of feel like this board is slowly fixing itself every time i power it on etc . Seems to get further each power soak and try etc.

I wish i could get into the ram rom test and see what it says and also the TGP test.


The boot sequence i think i learned a few things

LED Boot sequences (WIP, not guaranteed accurate yet!!)

8. 7. 6. 5

O O O O - top row

O (O) O (O) - bottom row (means green) else red

4. 3. 2. 1

Top and bottom on at boot then all off
Top 4 on again then off
3 and 1 should illuminate, with 4 and 2 off

Top 8 7 6 5 should light in sequence once sound system is running?
4 & 3 TGP graphics ADSP sub processor 1 IC37?
2 & 1 TGP graphics ADSP sub processor 2 IC31?
Possibly these sets are pairs and the green light on means the sub processor is ok, the red light on means its broken, or a sub section of that processor is broken like ram etc
 
Look at an empty EPROM socket and measure the voltage.

any 42 pin socket , pin 12 or 31 gnd, pin 22 vcc

If it's less than 4.80V, it's suspected that the faults are occurring due to insufficient power.
 
man1aco said:
Look at an empty EPROM socket and measure the voltage.

any 42 pin socket , pin 12 or 31 gnd, pin 22 vcc

If it's less than 4.80V, it's suspected that the faults are occurring due to insufficient power.
Click to expand...
Thanks , yeah i've experimented with power and voltages. I confirmed the voltage at the filter board matches on various chips on the main board and also on a few rom sockets on the top board. I have adjusted power to exactly 5.05v at the board, but its doesnt solve it. Seems same from 4.85v upwards to 5.1v etc

Currently, based on leds i think it's one of the sub processors or chips within the section like a ram is causing the halt. Maybe a dead ic or a lifted pin. The red led in the set 1&2 as above always stays lit and the green led 1 does not, unlike the other side

I will get the magnifier out and see if i can see anything odd with the legs etc
 
Ok, after some more power ons and off i managed to get it to run the memory test and the tgp test. Both pass ok, but then crash at the end if you try to exit.

IMG_2029.jpg
IMG_2030.jpg


I am now wondering if the fighting vipers game i have here is only using 1 of the co-processors as the test only shows ic31, so maybe the red led, no green led at post 1&2 is because that co processor is not initialised/used

Also, as the memory test runs through fine and takes alot longer than the normal time the board would crash i am thinking its an address access issue for the main cpu somewhere. Possibly bad rom address/pin or bad rom somewhere maybe.

Also, not sure if the tests can be trusted. its abit confusing considering it dies fairly quickly if just left in test mode to

Wish there was more documentation or better tests in these games,

My next idea is to verify all roms and then maybe try another rom set to see if there are any better tests in other games.

Also need to check all jumpers in case something got moved before i got it.. And the 3 lower jumpers on the main board are a mystery.


EDIT -> here is the actual screen shot of the real pcb. Sorry i uploaded MAME screens above. (Weird that MAME fails a ram test isnt it!!??)

IMG_2035.PNG
 
Last edited:
Asure said:
Confusing, because they used the same color and not a red font.. but IC18 and IC19 in RAM test are marked as BAD.
Click to expand...
Damn, sorry, i think i uploaded some mame screens by mistake .(when i was testing things out for comparison.)

See here for the video of the memory test. Anything look out of the ordinary??

https://www.dropbox.com/scl/fi/2mzo...test.MOV?rlkey=k33u7anzmgio7jdmzdv56xlbv&dl=0

You cant exit from the test after as its crashed, but it runs the test fine to the end afaict right now
 
Last edited:
Found something interesting today. Non of the mask roms tested so far are verifying ok. At first i thought it was just 1 of the co-processor roms, but they just won't record the same read each time. I am wondering if my programmer cannot read these masked roms properly, or if something happened to them. All the normal eproms read ok so far, so the programmer works with these, but not on the 42 pin ones. Other 42 pin chips from other games work ok though

I dont see how all masked roms could have failed though, must be a red herring on the programmer.

Gonna try a new set of co-processor proms anyway to see what occurs. Graphics roms can be bad and the game should still run reliably even with messed up screens.

Interesting that most of the program roms are eproms not mask, apart from the co-processors roms... Hmmm. Also the actual files on these only use a fairly small percentage of the rom space. A 27c160 is blank for alot of it..
 
mypinballs said:
Found something interesting today. Non of the mask roms tested so far are verifying ok. At first i thought it was just 1 of the co-processor roms, but they just won't record the same read each time. I am wondering if my programmer cannot read these masked roms properly, or if something happened to them. All the normal eproms read ok so far, so the programmer works with these, but not on the 42 pin ones. Other 42 pin chips from other games work ok though

I dont see how all masked roms could have failed though, must be a red herring on the programmer.

Gonna try a new set of co-processor proms anyway to see what occurs. Graphics roms can be bad and the game should still run reliably even with messed up screens.

Interesting that most of the program roms are eproms not mask, apart from the co-processors roms... Hmmm. Also the actual files on these only use a fairly small percentage of the rom space. A 27c160 is blank for alot of it..
Click to expand...
Reseat your ROM board and the ROMs themselves. Really, I've witnessed a lot of Model 2 stacks began to exhibit weird behavior, ranging from graphical issues to non-booting, due to poor connections in the stack. Dump contact cleaner on the pins if you have to.
 
You must log in or register to reply here.
Back
Top