Page 2 of 3
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 12 Apr 2021 16:26
by terriblefire
Its probably about time i merged the branch into develop
.
EDIT: Done.
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 12 Apr 2021 17:59
by amimjf
8 Bit Dreams wrote: 12 Jan 2021 23:29
There will be about 100 Delfina's available soon,
Will let You know when these pop up, if someone is interested
Interested. I've been following the a1k forum, but did not see any recent progress.
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 13 Apr 2021 18:34
by 8 Bit Dreams
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 13 Apr 2021 20:07
by amimjf
8 Bit Dreams wrote: 13 Apr 2021 18:34
These are sold out already,
That was quick, hopefully they build again.
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 13 Apr 2021 20:52
by 8 Bit Dreams
There will be a batch of bare pcbs available soon,
JEDs for MACH Chips are also available, so highly likely You'll be able to build one before Prelude pops up.🤔
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 17 Apr 2021 21:53
by arkadiusz.makarenko
As far as I understand issue with jumping mouse affects certain CD32 boards only.
Only mouse is affected, RTC is handled correctly, and it looks like only counters are affected.
Same set of TF330 works fine on one machine, but fails few others.
As far as I understand stm32 is doing its job correctly, and any changes to extend timings on each stage of process doesn't fix issue.
Therefore I assume issue is with cpld logic.
@terriblefire
If you had some time and/or will, could you have a look at
https://github.com/arkadiuszmakarenko/T ... main_top.v
and look for obvious mistakes there? Or hints what I could try? Effect is like override wasn't taking fully effect? Like PUNT was ignored every so often?
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 17 Apr 2021 22:43
by terriblefire
arkadiusz.makarenko wrote: 17 Apr 2021 21:53
As far as I understand issue with jumping mouse affects certain CD32 boards only.
Only mouse is affected, RTC is handled correctly, and it looks like only counters are affected.
Same set of TF330 works fine on one machine, but fails few others.
As far as I understand stm32 is doing its job correctly, and any changes to extend timings on each stage of process doesn't fix issue.
Therefore I assume issue is with cpld logic.
@terriblefire
If you had some time and/or will, could you have a look at
https://github.com/arkadiuszmakarenko/T ... main_top.v
and look for obvious mistakes there? Or hints what I could try? Effect is like override wasn't taking fully effect? Like PUNT was ignored every so often?
only issue i see is that things are combinatorial logic when possibly clocked logic might be better
https://www.tutorialspoint.com/differen ... al-circuit
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 26 Apr 2021 18:49
by wairnair
arkadiusz.makarenko wrote: 17 Apr 2021 21:53
As far as I understand issue with jumping mouse affects certain CD32 boards only.
Can you tell which CD32 boards could possibly be affected?
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 26 Apr 2021 21:13
by arkadiusz.makarenko
wairnair wrote: 26 Apr 2021 18:49
arkadiusz.makarenko wrote: 17 Apr 2021 21:53
As far as I understand issue with jumping mouse affects certain CD32 boards only.
Can you tell which CD32 boards could possibly be affected?
@kulamario had exactly the same setup, and it worked ok on one CD32 but didn't on other.
Re: TF CD32 Riser Revision 2 Specification, known issues and licence
Posted: 27 Apr 2021 01:04
by kulamario
wairnair wrote: 26 Apr 2021 18:49
arkadiusz.makarenko wrote: 17 Apr 2021 21:53
As far as I understand issue with jumping mouse affects certain CD32 boards only.
Can you tell which CD32 boards could possibly be affected?
both are the same revision rev3
I thought it was akiko's fault because one is rev-0 and the other is rev-A and for me it works on rev-A
after talking to alenppc we found that this is not it
because alenppc has some cd32 and rev0 and rev-A and it doesn't work on any of them