How HWINFO detecting this or other SIO? It's done by reading internal configuration registers? I now reading datasheet and here it is written that for access to those registers, SIO must be put to configuration mode.
hasat wrote on 2020-05-10, 16:21:How HWINFO detecting this or other SIO? It's done by reading internal configuration registers? I now reading datasheet and here it is written that for access to those registers, SIO must be put to configuration mode.
That's what HWiNFO does too, then it reads CR D register, which however returns 0xFF on your system (per datasheet it should be 0x63).
You can do a simple test via the DEBUG tool in DOS:
o 3F0 55o 3F0 55o 3F0 Di 3F1
I tested this commands with debug and it's like you write - content received from 3F1 port is 0xFF. But it appears, like SIO not enter to configuration mode: I checked state of other registers and received result was always 0xFF.
hasat wrote on 2020-05-10, 17:43:I tested this commands with debug and it's like you write - content received from 3F1 port is 0xFF. But it appears, like SIO not enter to configuration mode: I checked state of other registers and received result was always 0xFF.
Are you sure it's a FDC37C663 ?
Or it might be using a different port. It might be 370, but there I'm not getting anything either.
Interesting is that 0x2E seems to return something. But not sure if this isn't the chipset and that's causing the crash..
Exact printing on chip is FDC37C663QF P . Port 370 also not work.
hasat wrote on 2020-05-10, 18:41:Exact printing on chip is FDC37C663QF P . Port 370 also not work.
The datasheet says to write 0x44 instead of 0x55 for 664. Could you try that? I would be:
o 3F0 44o 3F0 44o 3F0 Di 3F1
OK, I'll try it when I have time in a week.
report and log for the IBM Blue Lightning BL3 on the ALi PANDA board. Unfortunately I had to remove the VLB graphics card because the upgrade board covers both VLB slots.
HWiNFO identifies the CPU as an IntelSX2, 62.6 MHz - which not right. Should be an IBM 486BL3 running at 3x25 = 75 MHz. You can get CPU register information from the configuration file in CTCHIP34 (attached). I also have some pages from a booked scanned which go over these registers if you need it.
I ran HWiNFO with all 3 CPU methods disabled. Is there one in particular I should use? EDIT: All but method 3 cause HWiNFO to exit.
Plan your life wisely, you'll be dead before you know it.
feipoa wrote on 2020-05-15, 11:21:report and log for the IBM Blue Lightning BL3 on the ALi PANDA board. Unfortunately I had to remove the VLB graphics card because the upgrade board covers both VLB slots.
HWiNFO identifies the CPU as an IntelSX2, 62.6 MHz - which not right. Should be an IBM 486BL3 running at 3x25 = 75 MHz. You can get CPU register information from the configuration file in CTCHIP34 (attached). I also have some pages from a booked scanned which go over these registers if you need it.
I ran HWiNFO with all 3 CPU methods disabled. Is there one in particular I should use? EDIT: All but method 3 cause HWiNFO to exit.
Thanks! Well, this is quite a mystery to me ...
These CPUs don't support CPUID instruction and AFAIK they should have an unique CPU ID value passed after RESET. To retrieve this, one of the Reset methods would need to work and provide the CPU ID value. Did Method3 perhaps return something? If not, then I might be quite lost here, at least on this board/BIOS where none of those methods seem to work 🙁
I checked the configuration file, but not sure how to access the registers mentioned. It says "MODE=RDMSR", but I doubt this CPU supports RDMSR as it doesn't even support the CPUID instruction.
The scanned document will be very handy!
Method 3 did not yield anything other than IntelSX2 62.6. The BIOS is not BL3 aware. Probably all boards which are using a BL3 upgrade will be unaware of the BL3.
I'll send you the scanned pages privately.
Plan your life wisely, you'll be dead before you know it.
Looks like I was wrong and this CPU indeed supports MSRs (undocumented).. Very interesting 😀
feipoa wrote on 2020-05-15, 11:36:Method 3 did not yield anything other than IntelSX2 62.6. The BIOS is not BL3 aware. Probably all boards which are using a BL3 upgrade will be unaware of the BL3.
I'll send you the scanned pages privately.
OK, not sure if this is going to work, but let's try this build:
[build pulled, newer available]
Mumak wrote on 2020-05-10, 19:39:The datasheet says to write 0x44 instead of 0x55 for 664. Could you try that? I would be: […]
hasat wrote on 2020-05-10, 18:41:Exact printing on chip is FDC37C663QF P . Port 370 also not work.
The datasheet says to write 0x44 instead of 0x55 for 664. Could you try that? I would be:
o 3F0 44o 3F0 44o 3F0 Di 3F1
Hi,
today i tested this and nothing changed, registers in SIO still inaccessible. Also tested some other combinations and nothing worked. Hmm... 🙁
hasat wrote on 2020-05-16, 19:33:Mumak wrote on 2020-05-10, 19:39:The datasheet says to write 0x44 instead of 0x55 for 664. Could you try that? I would be: […]
hasat wrote on 2020-05-10, 18:41:Exact printing on chip is FDC37C663QF P . Port 370 also not work.
The datasheet says to write 0x44 instead of 0x55 for 664. Could you try that? I would be:
o 3F0 44o 3F0 44o 3F0 Di 3F1Hi,
today i tested this and nothing changed, registers in SIO still inaccessible. Also tested some other combinations and nothing worked. Hmm... 🙁
Thanks. That's pretty weird, but since I restarted work in DOS a while ago I've seen so many oddities that I'm no longer surprised.
Don't know what else to try...
Found now in datasheet, SIO can be locked (CR1, bit 7). "A low level on this bit disables the reading and writing of CR0-CRF". Maybe BIOS after configure SIO set this bit low.
hasat wrote on 2020-05-16, 20:05:Found now in datasheet, SIO can be locked (CR1, bit 7). "A low level on this bit disables the reading and writing of CR0-CRF". Maybe BIOS after configure SIO set this bit low.
Oh indeed, I missed this. Quite possible, that would explain it. In such case there's nothing I can do to identify it 🙁
Latest report and debug for the IBM BL3 from the 15 May 2020 build.
Plan your life wisely, you'll be dead before you know it.
feipoa wrote on 2020-05-17, 10:00:Latest report and debug for the IBM BL3 from the 15 May 2020 build.
Wow, it worked 😀 CPU name correct, clock as well 😀
Wondering what happened that it suddenly started to work...
I tested great frankenstein AGP/PCI-E/PCI Asrock P4/Core 2 MB - 4CoreDual-VSTA
https://www.asrock.com/mb/via/4coredual-vsta/
I have two issues:
Pentium E5500 - detected as TDP 130W, it has 65W.
Sata - only 1 of 2 Sata SSD drives detected and i got crash during detection, i had to use hard reset. I used on board Sata controller.
There are screenshots and log.
Im old goal oriented goatman, i care about facts and freedom, not about egos+prejudices. Hoarding=sickness. If you want respect, gain it by your behavior. I hate stupid SW limits, SW=virtual world, everything should be possible if you have enough raw HW.
ruthan wrote on 2020-05-17, 13:26:I tested great frankenstein AGP/PCI-E/PCI Asrock P4/Core 2 MB - 4CoreDual-VSTA https://www.asrock.com/mb/via/4coredual-vsta/ […]
I tested great frankenstein AGP/PCI-E/PCI Asrock P4/Core 2 MB - 4CoreDual-VSTA
https://www.asrock.com/mb/via/4coredual-vsta/I have two issues:
Pentium E5500 - detected as TDP 130W, it has 65W.
Sata - only 1 of 2 Sata SSD drives detected and i got crash during detection, i had to use hard reset. I used on board Sata controller.There are screenshots and log.
Have you run it perhaps under an EMM / V86 / VM manager?
