exxos's Atari, Amiga & retro forum

terriblefire wrote: 06 Jun 2020 21:11 no those are fine. Just things on the Amiga bus really.

Latest firmware seems to pull the data bus up. It needs to go HIGHZ or input.

@terriblefire

I have changed settings from input no-pull-down no-pull-up to output open drain with state set up to High. I hope this will do the job.

arkadiusz.makarenko wrote: 07 Jun 2020 15:02 @terriblefire

I have changed settings from input no-pull-down no-pull-up to output open drain with state set up to High. I hope this will do the job.

Thanks. I think i need to play around with this until i get the riser all sorted .

terriblefire wrote: 07 Jun 2020 15:08

arkadiusz.makarenko wrote: 07 Jun 2020 15:02 @terriblefire

I have changed settings from input no-pull-down no-pull-up to output open drain with state set up to High. I hope this will do the job.

Thanks. I think i need to play around with this until i get the riser all sorted .

Can you see any issues with it?

arkadiusz.makarenko wrote: 08 Jun 2020 10:01

terriblefire wrote: 07 Jun 2020 15:08

Thanks. I think i need to play around with this until i get the riser all sorted .

Can you see any issues with it?

With the setup i have i cannot get the Tf330 to see the fastram. On either the rev0 or rev1 riser. The fastram works fine on the kipper riser.

Damn.

(All seems to be working all right on my CD32)

arkadiusz.makarenko wrote: 08 Jun 2020 12:57 Damn.

(All seems to be working all right on my CD32)

I'm starting to suspect my CD32. You have fastram workng ok?

terriblefire wrote: 08 Jun 2020 13:31

arkadiusz.makarenko wrote: 08 Jun 2020 12:57 Damn.

(All seems to be working all right on my CD32)

I'm starting to suspect my CD32. You have fastram workng ok?

I did start ATK memory test on fast ram, and seems to be doing it's thing.
It is with blank (Riser) cpld in place.

Ok progress.

I switched to using a TF360 (see below) and it working sweet. May have the notport up and running too. I'll stick with this for now.
Attached is a firmware that intercepts the mouse accesses..

JOY0DAT *00A R D Joystick-mouse 0 data (vert,horiz)
JOY1DAT *00C R D Joystick-mouse 1 data (vert,horiz)

When this happens the machine will lock up waiting for the ARM to put data on the data bus.

1. needs to deal with the upper and lower byte by reading A0 from pin 24 (PC4).
2. place the data it wants on the data bus (if read) then
3. poke ACK on pin 2 (PC13) low for about 60-100ns.

Then probably you can expect to get the next part of the word immediately since the chipset always does word read/writes and we're always doing byte responses. Yes it will be 200ns slower to read the mouse. Do we care?

Inside the ARM we need to track and keep a current JOYDAT0 and JOYDAT1 with mouse/joystick movements and then feed these to the amiga when it asks for them.

Oh and ..

Pin 62 (PB9) will be low when accessing JOYDAT0
Pin 33 (PB12) will be low when accessing JOYDAT1

The interrupt pin 61 (PB8) will remain low through the whole cycle.
EDIT: Noticed that tapping DEL a few times causes a reboot with the USB keyboards.

It seems that there is a steep learning curve for me ahead :)
I might need to test your patience with this a little.

I assume joy dat format would need to be the same like in mist?

Del bug - I had to forget to clear maybe_reset variable. Will do it next time I sit down in front of IDE.