I am looking for a PCIe card for WinXP debugging

[Dietmar]

@Gelip

 

Yes to all.

The other cards have also other drivers.

So, this one is with best chance

Dietmar

[Gelip]

@Dietmar

Why is the integrated port on COM2 and not COM1? Did you set it up yourself?

16 hours ago, Dietmar said:

This is the only card, where in Flags:  not "Busmaster" is listed, only fast devsel and IRQ.

Check with command lspci -s 02:00.0 -vv if BusMaster is - or +

16 hours ago, Dietmar said:

Lindy 2S 16C950 is also connected via PCI bridge

But the card doesn't have a PCI bridge, it's a motherboard's PCI bridge right?

Do you have a different motherboard? Maybe on another motherboard the card will be connected without a PCI bridge and then the modified kdcom.dll will work?

Try another PCIe slot, e.g. x16 - is it connected then without a PCI bridge?

Edited February 1, 2022 by Gelip

[Dietmar]

@Gelip

The COM2 port is crazy setting on this board from Biostar z690A for the onboard COM port.

ALL devices have the same notation, connected through PCI bridge,

which I think simple means, that they sit in an Pcie-slot.

I think, that the real problem is in ntldr.

Did you make a try with freeldr from Reactos? In some kind it is the better choice,

have a nice day

Dietmar

[Gelip]

3 minutes ago, Dietmar said:

ALL devices have the same notation, connected through PCI bridge,

In both PCIe x16 slots ??? Enable the integrated graphics card and the Lindy PCIe card insert a PCIe x16 slot in place of the GeForce graphics card Is it then also connected via the PCI bridge?

Have you tried with a different motherboard?

[Dietmar]

@Gelip

Without graphikcard this board does not boot, even you can see the Bios and change all there.

The graphikcard GT730 is also connected over pci-to-pci bridge.

The same for the Lindy card. Driver for this pci-to-pci bridge is pci.sys .

The onboard COM port is connected via ISA-PCI bridge.

Only the Sata is direct connected to Pci, no bridge

Dietmar

 

[Gelip]

44 minutes ago, Dietmar said:

The graphikcard GT730 is also connected over pci-to-pci bridge.

What ???  Your motherboard is not good.

My AMD PCIe graphics card are connected directly to the PCI Express Root - no PCI bridge:

Edited February 1, 2022 by Gelip

[Dietmar]

@Gelip

 

What driver has your PCI Express Root

Dietmar

[Gelip]

12 minutes ago, Dietmar said:

What driver has your PCI Express Root

pci.sys from Microsoft

[Dietmar]

@Gelip

For me the same.

So, PCI Express Root is just another name for pci-to-pci bridge

Dietmar

[Gelip]

5 minutes ago, Dietmar said:

So, PCI Express Root is just another name for pci-to-pci bridge

Show your GeForce graphics card in device manager - Devices by connection view

[Dietmar]

[Gelip]

Ok, you have pci bridge and pcie express root for me, but that's not the point.

The depth of the number of bridges the PCIe card is connected to is important. Take a look at these screenshots:

My ExpressCard RS232 have 3 branches:

My PCIe RS232 card have 4 branches:

Edited February 1, 2022 by Gelip

[Dietmar]

@Gelip

Not easy to understand, how they managed the PCIe lines on the Biostar z690A board.

Because all USB is direct connected to the PCI Bus (without any bridge) via Device Manager,

but when you look at this layout, all USB goes through the z690 chipset.

The same is true for the Sata connector: On top of my device manager pic you can see, that

it is direct connected to the PCI bus. But again on this z690 diagramm you can see, that all Sata goes through

the z690 chipset. And maybe, that XP does not list correct in Device Manager, which device is connected via Pci-to-Pci bridge and what not. Hm, is there a test for Pci-to-Pci bridge or direct connected to PCI bus?

And if yes, what is the difference, Busmaster?!

Dietmar

Edited February 1, 2022 by Dietmar

[Gelip]

@Dietmar

Show PCIe Lindy card in device manager - view by connection

[Dietmar]

@Gelip

I did this already in Pic in Post here up "This card Lindy 2S 16C950 is also connected via PCI bridge"

Dietmar

[Gelip]

@Dietmar

Yes, but the screenshot does not show where the PCI Bus is - like the branch depth

Show branches from PCI bus to PCIe Lindy

P.S. Don't take a screenshot of the entire desktop, just the window itself with Alt + Print Screen

Edited February 1, 2022 by Gelip

[Dietmar]

@Gelip

The pci bus depth for the Lindy card is exact as it is for your working PCIeExpress card. No extra bridge chip on Lindy card.

I found this:

"The upper two slots (from CPU) will run in PCIe Gen 5.0 mode, and the lower full-length PCIe slot (from PCH) is Gen 4.0."

No difference in XP device manager, if I put the Lindy Serial card in Slot2 (direct connected to cpu) or in Slot3 (via chipset)

Dietmar

Edited February 1, 2022 by Dietmar

[Gelip]

Please make screenshots with Alt+PrintScreen not entire desktop !

Instead of using ibb.co use the wincert forum mechanism choose files

Edited February 1, 2022 by Gelip

[Gelip]

@Dietmar

I decided to check if my PCIe SER5427A card works, for example, in MS-DOS. I downloaded drivers for DOS. There is a SUNDOS.EXE program doing the same as the debug e 40:0 xx xx but port COM1 not work properly (in Putty I have bushes).

From the README.TXT file for DOS I learned that the baudrate speed set in DOS is 8 times greater in reality:

 C. PCI serial card are drived by a higher CLK (14.7456 Mhz), 
      thus the actual baudarate is 8 times higher than the BIOS/DOS baudrate 
      setting. The below table shows the relation.


*** Clock=14.7456 Mhz for all non-remapable port  ***

      Item   Actual Baudrate    BIOS/DOS setting    Remark
      =====  ================   =================   ==================
       1       921600                    115200
       2       460800                     57600
       3       230400                     28800     Non BIOS standard
       4             115200               14400     Non BIOS standard
       5              57600                7200     Non BIOS standard
       6              38400                4800 
       7              19200                2400  
       8               9600                1200
       9               4800                 600     Non BIOS standard
      10               2400                 300
      11               1200                 150 
      12                300                37.5     Non BIOS standard

So that the card works correctly in DOS is enough:

• boot PC from MS-DOS (tested 6.22)
• run sundos.exe or debug e 40:0 00 40 (4000h is I/O address my card)
• set baudrate to 4800 - mode com1:48,n,8,1,n
• on second PC run Putty, serial with baudrate 38400 (see README.TXT table)
• now port COM1 work OK e.g. ctty com1 (ctty con for back to local console)
• works also GRUB4DOS (grub.exe)
  serial --unit=0 --speed=4800
  terminal serial (terminal console to back to local console)

So I thought Windbg to work enough in Boot.ini set /baudrate=4800 and in Windbg 38400 but this f..k does not work

WTF is going on

Edited

At this point, I was only testing WinXP SP3

Edited February 3, 2022 by Gelip

[infuscomus]

please share your boot.ini

[Gelip]

@infuscomus

In boot.ini I have many entries with different baudrates

Edited February 3, 2022 by Gelip

[Gelip]

@Dietmar @infuscomus

Yeeeeeeeaaaaaaaaaaa!!!

It finally worked ! Tested debug WinXP SP2 64-bit

1. If the PC has a integrated COM port on the motherboard, turn it off in the bios
2. I plugged my PCIe RS232 Sunix SER5427A card into the PCIe x1 slot
3. Check I/O port my card in Debian or Windows with pciutlis - lspci -s xx:xx.x -v, my card has D000
4. Mod kdcom.dll x64 in offset 1024 change F803 to 00D0 (little endian)
5. Replace kdcom.dll in WINDOWS\system32 on debuged PC
6. We set up debug in boot.ini:

   /debug /debugport=COM1: /baudrate=14400

7. On host PC run WinDbg baudrate 115200
8. Boot debugged PC to MS-DOS 6.22 with tools debug.exe and grub.exe (GRUB4DOS)
9. Insert I/O addres to memory 40:0 for COM1 (my is D000) (or simply run sundos.exe)
   debug
   -e 40:0 00 D0
   -q
10. Run GRUB4DOS (grub.exe)
11. Boot WinXP (menu.lst):

    default 0
    timeout 5
    
    title Boot WinXP
    map (hd0) (hd1)
    map (hd1) (hd0)
    map --hook
    find --set-root /ntldr
    chainloader /ntldr

P.S. If on a computer with WinDbg we have a modern PCIe card with an RS232 port that allows higher speeds, then you can set the maximum to what both PCIe cards allow, for me you can do this:

boot.ini - 57600 & WinDbg 460800

Edited February 3, 2022 by Gelip

[Dietmar]

@Gelip

Waaaoohh:)))))))!!!!!!!! I tried such a lot with Windbg and did not reach this.

And the Admins from Microsoft wrote in a Blog,

that it is impossible!

For me is still unclear, what you make other than me before.

Have you tested, that it really depends only on the different Baud rates on both compis?

This for Windbg working card is the card with the bridge, right?

I try in the afternoon also, have a nice day

Dietmar

 

Edited February 2, 2022 by Dietmar

[Gelip]

6 hours ago, Dietmar said:

Have you tested, that it really depends only on the different Baud rates on both compis?

For my Card PCIe Sunix SER5427A yes - incompatible speed baudrate in BIOS/DOS

6 hours ago, Dietmar said:

This for Windbg working card is the card with the bridge, right?

Yes, this card have PCI bridge ASMedia

Edited February 2, 2022 by Gelip

[Gelip]

@Dietmar

Yess. Tested with WinXP SP2 32-bit - works

Edited February 2, 2022 by Gelip