reducing shiftout clock freq and PS2/PC interfacing ....

[Archangel]

Hello Wireless Magic,
to save yourself some agravation of having Windoze lock, have you tried booting to a command prompt only? Even better use a DOS startup disk. If your hardware is off it likely will not lock up it just won't work.

[Darrel Taylor]

It takes more than just sending keystrokes via the PS2 protocol.

When the PC is booting, the keyboard must send and receive several commands to tell the PC what it is, what mode it's using, etc.

Go to the link Sayzer gave in post #4, then click on "PS/2 Keyboard Interface".
Look at the Command Set/Initialization sections at the bottom.

It's possible to place the device in parallel with an existing keyboard, so the keyboard does all the initializing.
But if you don't want the keyboard, you'll need to do it all yourself.

Not as easy as just toggling a couple pins with the right timing.
<br>

[skimask]

When the PC is booting, the keyboard must send and receive several commands to tell the PC what it is, what mode it's using, etc.

Ahhhhhhhh.......
The O/P didn't state specifically if he/she was using the keyboard alone or in parallel...good point...
However (we've been down this road before somewhere), there should be a setting in BIOS called something like 'Halt on All Disk/Keyboard' errors or something like that and it can usually be shut off. Should take care of the freezing problem. But since the keyboard hasn't been recognized, it still won't work

[mister_e]

I confirm what Darrel's said. There's a lot of things to do before it work as expect.

I already suggested awhile back to build a PS-2 sniffer and log the whole data exchange from the boot... to the end. It's more than a stupid BIOS setting. In fact.. you have to confirm your Keyboard is there, and it's self test is passed.

Not that hard.. not that easy.

If you have any protocol analyzer or digital storage scope (PoScope, Bitcope, USBee) that will be easier.

For safety sake, you can't use Shiftin/Shiftout AS-IS. You need to toggle TRIS instead of trashing a pin to high or low.

Note: A PC may work slightly different from a Laptop.

This said.. this should be enough food for thought

[wireless magic]

ok , what we have until now is :

The code works almost perfectly when booting to a command prompt only (DOS). in BIOS i made it not to halt on keyboard errors, but this only removed the ( No keyboard or keyboard error) that appears when switching on. But still it FREEZES when trying to send a character in notepad ( in windows). why is it working over DOS but windows Freezes?

in the code i made no initialization (When the PC is booting, the keyboard must send and receive several commands to tell the PC what it is, what mode it's using, etc.) and still the DOS recognizes the data sent to the PS/2 port by the PIC.

what to do so that windows doesn't freeze?

thanks again

[Archangel]

Question:
Are you sending data from 1 p/c (notepad ) through the serial port to the PIC and then to a second P/C ? I ask, as today I was working setting up the COM link between a PC and A CNC mill and the serial software by default sends a CR and LF with every line, and you can disable that, maybe your serial program is sending that and the P/C is not expecting it. Just thinking out loud.
JS

[sayzer]

ok , what we have until now is :

The code works almost perfectly when booting to a command prompt only (DOS). in BIOS i made it not to halt on keyboard errors, but this only removed the ( No keyboard or keyboard error) that appears when switching on. But still it FREEZES when trying to send a character in notepad ( in windows). why is it working over DOS but windows Freezes?

in the code i made no initialization (When the PC is booting, the keyboard must send and receive several commands to tell the PC what it is, what mode it's using, etc.) and still the DOS recognizes the data sent to the PS/2 port by the PIC.

what to do so that windows doesn't freeze?

thanks again

It seems we will have to look at the hardware side!
Unplug mouse, and boot with KB only.
Open notepad and unplug KB, plug PIC circuit.
Send data.
IF still freezing, then post the schematic.

P.S. - Assuming (and also hoping) that after each send, you are setting your Clk and Data pins to be input pins and putting a delay like 10mS.

[wireless magic]

thank u ,
we tried it and no more freezing, and it works perfectly on notepad.
how can we avoid freezing? ( how to boot with the PIC circuit and make windows recognize it?)
i tried some initialization codes but still freezes.
is the initialization code for windows to recognize the "PIC keyboard" or for the PC to boot initially with the "PIC keyboard" connected ??