Hello all, I dusted out my Set5 but seems time was not good with him and now the device is not working properly :< if i set the video switches to ON ON OFF OFF and connect the vga cable, i never got any image , thought my tv switched to 640x480@60hz mode if i set the video switches to OFF OFF OFF ON and connect using Audio/Video cinches. i can see for 1sec some text from the Test mode if i set the video switches to ON ON OFF ON and connect the vga cable , i get a 'unsupported signal' the power supply seems good , i have 5.2v and 11.98v (didn't check the 3.3 rail). And the scsi disc is working as i pulled it out and save the contents to my computer. any clues what it could be ? thanks in advance
Hello & Welcome, No idea specifically, but I would check the following things if not done yet: - I would check if the SCSI card in my pc sees the GD-DA & GD-M @boot - I would try to switch the devkit to OS mode (=BIOS mode) via DACheck - I would try with other self-tests (eg: rotary on 7 = simple VGA test, 6=CLX demo, ...) - I would try the DACheck tests - I would also check if DBFlash can read the version nr of all the flash roms - I would try to run a small test program on the devkit (eg a sample of the SDK) That's where I would start... after that, I would dump the bios & flash via Codescape, and reflash them to see if that changes anything. If that doesn't solve it, I would check all internal cables (and try with another VGA cable, you never know )
thanks for your help & time ! My SCSI card has troubles to recognize GD-DA & GD-M @boot. Everytime i boot the computer , it's stuck on the SCSI identification. Even when i pulled out the HD , and connected it to the internal SCSI connector , it didn't found it. I used another SCSI card to get the contents of the HD. But the only cable i have is a 68 to 50 , and that working AHA 2940 has a 50 pins external connector. I ordered a 50 to 50 pins cable. hope to get it quickly. I tried to the other test with the rotary as suggested, and using the VGA connector , i always get a ''Out of range'' on the monitor i notice the eeprom , and i wanted to dump it with my eprom programmer , but i did'nt wanted to remove the sticker to check the reference
some more tests : i tested all the rotary test using the Audio/video connection. As before , i get some display for 1 sec and then everything disapear. i set the switched as OFF OFF OFF ON if rotary is set to A , i get a message "GD-Rom not found". i'll check the connectors
SCSI card -> have a look at _this thread_, the settings of your SCSI card have to be correct to have everything working correctly (especially, starting from the last post of the 1st page, the post from Woofmute) eeprom -> no need for that, there's little chance that this is bad. The detachable eeprom contains only the selftest, not the BIOS or the 128 KB flash memory. If you really want to check this, it's enough to calculate the CRC of the contents of it by dumping it via your programmer. The chip is a ST M27C160-100F1, the same as what's used for the Naomi Bios. Normally the CRC is written on the sticker of your eeprom, eg for selftest version 0.41 it's FC52. The 2 MB bios (0x00000000 to 0x001FFFFF) & the 128 KB flash memory (0x00200000 to 0x0021FFFF) are on other chips, soldered to the motherboard, they can only be read/written to via the SDK I think. (dumping can be done via codescape, write is usually done via DBFlash or another program)
BTW, the self-check mode only outputs to VGA, cfr GetStart.txt of the SDK, so I wouldn't be surprised of unexpected behavior if you try it with a RCA cable.
I'm having issues with my dev box. The GD-M doesn't show up at all, I went through and checked to make sure my SCSI card had the same settings in the thread you linked. What could cause the GD-M to not show up? My unit seems to be stuck trying to emulate something, when it boots up it says it's checking the disk and hangs. There is nothing on the HDD when I connect it directly to the SCSI card. I did dump the two memory locations you suggested, but I don't have anything to compare the dumps to. I tried to reflash everything that was available in dbflash, and I still get the same results.
Please create a separate thread for this, I'll gladly respond to that in that thread. That way, we can have a thread specific for video issues, and one thread for GD-M issues, it will make it easier for other people in the future that might search for one of those specific issues.
Hello, Just received a new SCSI cable and as soon i reflashed using DBFlash , i got a proper video signal (wooohooo). Thanks for the help Unfortunately , there's a BUT i can not debug , as soon i try to run QckTest2 in CodeScape , i got a error. I set GD Workshop in Emulation as claimed in the doc. but it's not working :s I noticed that the GD-M doesn't appear in the Devices Management , and i can not configure a drive letter in GD Workshop ... I've installed ASPI , and i the DA Check for DA and GD-Rom are all green. Any clues ?? here's a summary of the setup thanks in advance
Fantastic ! As long as DACheck is all green, everything should be ok with the devkit for debugging. Codescape: - what kind of error do you get ? - try to put a game in the disc tray, I'm not sure for QckTest2, but some examples in the SDK need a disc inserted, otherwise it exits immediately. (Pretty stupid for a SDK, but understandable to have this kind of check for the retail game, so kind of logic they put that in the SDK too...) - try to compile another sample with CodeWarrior or another compiler, and try to debug that via CodeWarrior or Codescape Codescape & CodeWarrior takes some getting used to, so play a lot with it. Have fun
thanks ! i got everything running Weird thing , if i leave the set5 off for a few days , i get the vga problems until i reflash again & again
Brainstorming / reasons I could think of: - do you put the white slide switch back to the left after flashing it, to avoid accidental writes/... ? - the docs tell that after flashing, and after powering down the devkit, you should wait at least 30 seconds before powering the devkit up again. Cfr /Doc/PDFs/GetStart.pdf: "Wait at least 30 seconds, and then turn your dev box back on again. This wait period is important! Waiting more than 30 seconds won’t hurt; waiting less than 30 seconds might."- ? fluctuations in your power supply / electricity network ? - ? Too many hard reboots ?
