Dave
Hi, been following with interest, and members in creating options in keeping the Beeb alive for the next 100 yrs.
I was a first thinking using an async fifo chip connected to the ATF1508 it has enough empty pins they come in sizes of 1Kx8 would be on the rather large size would make for an interesting high water mark buffer.
then went duuu a smaller ATF1504 ? would that be enougth to have 8 Byte or 24 Byte FIFO buffer, how many macro cells would it require ?
1. Program with 2 byte buffer first, option later steps, 8byte or 24byte on a ATF1504 ? possible ?
2. Swap around use the ATF1504 as the controller-integration fast 'ns' unit, then a cheaper slower 1508 as the fifo buffer ?
small steps. question on latency and integration all come to mind.
dusted off a ATF1508 dev environment been packed away for many years,Prochip 4.0 version, and slowly learning never was an option at UNI in my time...
James
Learner
Hi, been following with interest, and members in creating options in keeping the Beeb alive for the next 100 yrs.
I was a first thinking using an async fifo chip connected to the ATF1508 it has enough empty pins they come in sizes of 1Kx8 would be on the rather large size would make for an interesting high water mark buffer.
then went duuu a smaller ATF1504 ? would that be enougth to have 8 Byte or 24 Byte FIFO buffer, how many macro cells would it require ?
1. Program with 2 byte buffer first, option later steps, 8byte or 24byte on a ATF1504 ? possible ?
2. Swap around use the ATF1504 as the controller-integration fast 'ns' unit, then a cheaper slower 1508 as the fifo buffer ?
small steps. question on latency and integration all come to mind.
dusted off a ATF1508 dev environment been packed away for many years,Prochip 4.0 version, and slowly learning never was an option at UNI in my time...
James
Learner
Statistics: Posted by HJimbo — Wed Feb 07, 2024 12:24 am