For every address line you ignore, you get additional "mirrors" of your IDE adapter in the address space. Whether this is problematic or not depends on if there already is other hardware at the mirror address. In particular, if you don't decode A14 and A15 in an IDE adapter, you get mirrors at 0xF040xx, 0xF080xx, 0xF0C0xx. That might be okay, unless you have some third-party HW that resides at one of these addresses.LarryL wrote: Thu Jun 27, 2024 1:21 pm Still not sure if I can work without A14 & A15 to reuse these inputs for IDE port selection and enable/disable…
Can all registered uses please login, even just for a few minutes..
It helps build a picture where our "good traffic" is coming from..
Thanks :)
It helps build a picture where our "good traffic" is coming from..
Thanks :)
two IDE adapters inside ST
Re: two IDE adapters inside ST
Re: two IDE adapters inside ST
thanks, understood...czietz wrote: Thu Jun 27, 2024 5:08 pm For every address line you ignore, you get additional "mirrors" of your IDE adapter in the address space. Whether this is problematic or not depends on if there already is other hardware at the mirror address. In particular, if you don't decode A14 and A15 in an IDE adapter, you get mirrors at 0xF040xx, 0xF080xx, 0xF0C0xx. That might be okay, unless you have some third-party HW that resides at one of these addresses.
I doubt that there is "somewhere" an overview, what 3rd party HW is using which addresses?
OK, I will try some searching...
maybe switching to a different CPLD and do full address decoding would be best...
