topic Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target in Operating System - HP-UX

NDDB Kernel/Driver debugger using RS-232 between Host and Target

John Liu — Thu, 01 Jun 2000 15:50:16 GMT

Hi, I was trying to set up the communication between host and target (both are series 700 running 11.0) using RS-232 cables. NDDB Reference Guide v2.15 says "null modem" is

Connector Pins Connector Pins
2------------------------------------3
3------------------------------------2
7------------------------------------7 <---- Is this correct?

Thanks

JohnL

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

Robert Gamble — Thu, 01 Jun 2000 16:00:43 GMT

What are your RS-232 cables connecting to on the 700's ? A serial port ? or through MUX panels ?

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

John Liu — Thu, 01 Jun 2000 16:35:10 GMT

Hi, Robert,

Here is the systems I am using:

B180L running 32bit HP-UX 11.00 as the host running the NDDB
J5000 64bit HP-UX 11.00 (2 processors) as the target. On the target, I use #ioscan -f to check the RS-232 ports, there are two such ports serviced by driver asio0, I suppose they are not MUX port because MUX port serviced by mux2 driver which is not shown when issuing ioscan -f command. My "null modem" is 7----8 (through).

Any further ideas?

Thanks

John Liu

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

Robert Gamble — Thu, 01 Jun 2000 16:45:09 GMT

Have you looked at the back of the workstations to see which physical ports your are going to cable ? Using ioscan to find the hardware path is important to make sure the associated device files are properly claimed, but you also need to determine what you are cabling, what type of connector, DB25 or DB9 ? You see where I'm going ? Hope this helps.

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

John Liu — Thu, 01 Jun 2000 16:57:58 GMT

Hi, Robert,

Physically on the back of my target (J5000) and host systems there are two ports (#1 and #2), I am using #2 as Reference Manual suggested. And I just get a "null modem" 7--8 (not 7--7) DB9 only. I never got it work using this RS-232. I did make it work using dedicated LAN communication. I really don't want to limit myself to the q4 or adb only.
Solaris make it much easier in terms of debugging my driver. HP-UX HP-UX NDDB help..

Thanks

JohnL

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

Robert Gamble — Thu, 01 Jun 2000 17:09:24 GMT

John,

Sorry, no more ideas....

Good Luck!

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

Carlos Fernandez Riera — Fri, 02 Jun 2000 11:54:33 GMT

I cant help you but:

http://devresource.hp.com is the web for developers.

Regards

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

Michael Lampi — Mon, 05 Jun 2000 18:26:27 GMT

The reference manual is correct for the pinouts. I used this on 715's for NDDB under HP-UX 10.20 for driver development.

Try getting an RS-232 breakout box and some "straight through" cables. It is much easier to play with the wiring this way rather than to try to find a null modem cable that only has the three wires mentioned.

Alternatively, you could use female-female DB-9 cables on both systems, and use paper clips to jumper from one cable to another to achieve the desired results. Once you figure out which pins sort out into the 2-3, 3-2 and 7-7 positions, insulate them from each other (with tape, etc.), and wrap the whole thing with tape.

Or, call your local cable supplier and tell 'em what you want them to make for you!

----------------------
Under HP-UX 11 you can also use dynamically loadable kernel module (DLKM) driver approach, which can also help to simplify the debugging process.

Re: NDDB Kernel/Driver debugger using RS-232 between Host and Target

John Liu — Mon, 05 Jun 2000 21:25:16 GMT

Hi, Michael,

I am using female-female DB-9 cables to hook two systems together. My question is 2-3, 3-2, 7-7 as the HP reference manual says is for DB-25 I guess. But for the DB9 pinouts are not the same as DB-25. Are you using BD-9 cable too? I got a DB-9 cable and 2-3, 3-2 are correct, it is not 7-7, it is 7-8, 8-7. When I was using this cable (7-8, 8-7) I boot at ISL> hpux -f3 /stand/vmunix I got a panic on the target system. I never made nddb work using RS-232. The panic happened in io_map_regs().

Unfortunately, my driver is not designed as DLKM.

How do you make your NDDB work using RS-232, any further suggestions?

Thank you so much.

John