TF CD32 Riser Revision 2 Design Complete

[terriblefire]

Do you think that bad RTC output can crash booting to Workbench?

Unlikely i would say its more likely some weirdness happening when TF330 uses fastmem.

[arkadiusz.makarenko]

Do you think that bad RTC output can crash booting to Workbench?

Unlikely i would say its more likely some weirdness happening when TF330 uses fastmem.

Forgot about that TF330 can introduce those issues.

Is there anyway to detect this? Like by checking PUNT?

[terriblefire]

Unlikely i would say its more likely some weirdness happening when TF330 uses fastmem.

Forgot about that TF330 can introduce those issues.

Is there anyway to detect this? Like by checking PUNT?

There is a PUNT IN from the expansion slot. the CPLD should shut up when it sees this asserted and not decode.

This is why i split PUNT_IN and PUNT_OUT. Its why the Analogic risers dont work well.

[arkadiusz.makarenko]

Forgot about that TF330 can introduce those issues.

Is there anyway to detect this? Like by checking PUNT?

There is a PUNT IN from the expansion slot. the CPLD should shut up when it sees this asserted and not decode.

This is why i split PUNT_IN and PUNT_OUT. Its why the Analogic risers dont work well.

I will add this, and lets see what will happen.

[terriblefire]

There is a PUNT IN from the expansion slot. the CPLD should shut up when it sees this asserted and not decode.

This is why i split PUNT_IN and PUNT_OUT. Its why the Analogic risers dont work well.

I will add this, and lets see what will happen.

If something like this is not present then any attempt to access 40bfe001 will cause both the ARM and the SDRAM to respond. etc

[arkadiusz.makarenko]

I will add this, and lets see what will happen.

If something like this is not present then any attempt to access 40bfe001 will cause both the ARM and the SDRAM to respond. etc

It did! Thank you. Boots every time now.
I was again barking at wrong tree.
I had to get my head round verilog to combine both states. Still some date/time is not read correctly. I need to do better job in translating values of arm RTC to what Amiga expects (boring, and time consuming staff).

But it is time to slowly start looking at mouse support?

[terriblefire]

If something like this is not present then any attempt to access 40bfe001 will cause both the ARM and the SDRAM to respond. etc

It did! Thank you. Boots every time now.
I was again barking at wrong tree.
I had to get my head round verilog to combine both states. Still some date/time is not read correctly. I need to do better job in translating values of arm RTC to what Amiga expects (boring, and time consuming staff).

But it is time to slowly start looking at mouse support?

Yeah i would do mouse next because issues will show up fast.

[arkadiusz.makarenko]

It did! Thank you. Boots every time now.
I was again barking at wrong tree.
I had to get my head round verilog to combine both states. Still some date/time is not read correctly. I need to do better job in translating values of arm RTC to what Amiga expects (boring, and time consuming staff).

But it is time to slowly start looking at mouse support?

Yeah i would do mouse next because issues will show up fast.

Still have some bug in verilog, as I still clash with tf330 somwhere.

[chucky]

yes that have happend

[terriblefire]

Still have some bug in verilog, as I still clash with tf330 somwhere.

Run the complete memory detection in diagrom to see issues.