A simpler mouse adapter for the Amstrad Plus?

Started by Cwiiis, 15:34, 11 November 22

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

GUNHED

Remember AMX Stop Press! They showed how good a joystick compatible mouse really can do.
http://futureos.de --> Get the revolutionary FutureOS (Update: 2022.03.09)
http://futureos.cpc-live.com/files/LambdaSpeak_RSX_by_TFM.zip --> Get the RSX-ROM for LambdaSpeak :-) (Updated: 2021.12.26)

Bryce

Yes, but from a hardware perspective they didn't do anything different. It's the software on the CPC that decides how good the mouse feels.

Bryce.

GUNHED

Sure. That's what I always tell. Everything depends on the software.
Therefore I talked about a joystick compatible mouse (any!) and mentioned the particular software.
http://futureos.de --> Get the revolutionary FutureOS (Update: 2022.03.09)
http://futureos.cpc-live.com/files/LambdaSpeak_RSX_by_TFM.zip --> Get the RSX-ROM for LambdaSpeak :-) (Updated: 2021.12.26)

Prodatron

Like an acceleration parameter which works for joystick compatible mouses quite good as well.
It's probably one of the reasons why joystick compatible mouses could feel and be used like proportional mouses, if you are not experienced in the real difference and learn to handle them in this way.

You cannot view this attachment.

GRAPHICAL Z80 MULTITASKING OPERATING SYSTEM

Cwiiis

I've been debugging and trying to verify and understand more - as far as I can tell, everything is wired how I intended to wire it and behaving as I would expect. The chip select on the LS240 is being pulsed correctly and all the output pins go where I expect and are what I'd expect to see (pulled high, waiting to be grounded). Really, the only thing that isn't doing its job appears to be the PIC. It's receiving power and the clock looks good on CLKOUT (I assume it's meant to look like a sine wave and not a square wave?), but it doesn't appear to be communicating with the mouse at all.

So my thought is either I've not flashed the PIC correctly or that perhaps I've not understood the circuit and wired something incorrectly. Regarding the latter, it's not like there's a whole lot I could get wrong, so I'm still suspecting that it isn't flashed correctly or there's something wrong with the clock and I don't understand what it should look like.

Something I wonder about; I've tied RA4 on the PIC to ground - as I understand the circuit, this should permanently enable auto-detect. Though even if that was wrong, I'd have thought the side-effect would be no mouse wheel (which won't work until I connect X7 from the keyboard connector anyway, iiuc), not the entire thing not working?

I suppose I could try to make the flashing circuit and follow the exact steps from the wiki page rather than using MPLAB, but it feels like I'm clutching at straws somewhat now... Does anyone have any suggestions?

Bryce

Can't you read back the PIC content and confirm that's it's programmed? The HEX file doesn't lock the code, it should be readable.

Bryce.

Cwiiis

Quote from: Bryce on 14:07, 02 December 22Can't you read back the PIC content and confirm that's it's programmed? The HEX file doesn't lock the code, it should be readable.

Bryce.
Yes, and I can confirm that it is what I'd expect - the program code is from 0x0-0x1af and the rest is filled with 3FFF. MPLAB verification says it's correct and there aren't any errors during programming. I also verified the flags reflect what's said in the wiki too, and it does.

Cwiiis

On the off-chance, I tried the 1.0 firmware given I based my circuit on the diagram of the PS/2 circuit, but no change in behaviour. I guess I should learn enough about PIC programming to just write a small debug program to check that the circuit is ok by flashing LED patterns... But I'll exhaust a few more easier, brute-force methods first.

Powered by SMFPacks Menu Editor Mod