15 May 2015, 09:11 | #1 |
Registered User
Join Date: May 2013
Location: Kleppe / Norway
Posts: 258
|
CDTV addressing questions
I have been asked about making my FASTRAM board for A500(+)
CDTV friendly. Having no CDTV myself, I would need some help from the experts. As of now, my board contains 16MB of non autoconfigured SRAM, and the SPLD logic on the board opens up the following ranges (of which some can be controlled with switches): 0x200000-0x9FFFFF (8MB Z2 RAM area) 0xA00000-0xBDFFFF 0xC00000-0xDBFFFF (autoconfigured by kickstart) 0xE00000-0xE7FFFF 0xF00000-0xF7FFFF Theres also a small Gary board which patches address accesses in the ranges other than the Z2 to look like accesses to 20xxxx, hence it will generate proper non delayed #DTACK for the RAM board and side-cars, and there will be no conflicts with the Agnus address realm. This setup works quite well on A500(+) setups. CDTV on the other hand, has an address map like this (if this one is correct): 000000-0FFFFF Chip memory 100000-1FFFFF Space for extra chip memory (Megachip) 200000-9FFFFF Space for AutoConfig memory A00000-BFFFFF CIA chips C00000-C7FFFF Space for slow-fast memory C80000-DBFFFF Space DC0000-DC7FFF Power backed-up real time clock DC8000-DC87FF Non-volatile RAM DC8800-DCFFFF Space in non-volatile RAM decoded area DD0000-DEFFFF Space DF0000-DFFFFF Custom chips E00000-E7FFFF Memory card address space for front panel memory card E80000-E8FFFF AutoConfig configuration space E90000-E9FFFF First AutoConfig device, used by DMAC EA0000-EFFFFF Space for other AutoConfig devices F00000-F3FFFF CDTV ROM F40000-F7FFFF Space in CDTV ROM decoded area F80000-FBFFFF Space in Kickstart ROM decoded area (used by Kickstart 2) FC0000-FFFFFF Kickstart ROM Immediately I see I would have to stop patching the 0xF00000-F7FFFF area as FASTRAM as it will block the CDTV ROM. That area would also have to be closed on the FASTRAM-board. Would it still be ok to have FASTRAM at 0xA00000-BDFFFF if it is patched in Gary as before although the address map claims it for CIA space? My initial assumption is that the A500 CIA space that starts at 0xBFD000 is still used, only it is mirrored downwards. Other than that please comment on other possible memory conflicts I should be aware of. Thanks in advance for any help. |
15 May 2015, 11:43 | #2 | |||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
Quote:
Quote:
Quote:
|
|||
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
CDTV questions | utri007 | support.Hardware | 1 | 03 May 2014 12:54 |
Memory addressing | CmdrVimes | Coders. General | 7 | 25 October 2010 22:20 |
Memory Addressing Architecture | Zetr0 | support.Hardware | 2 | 10 July 2007 16:55 |
CDTV questions | Galahad/FLT | support.Hardware | 37 | 12 January 2007 01:49 |
Addressing modes | BippyM | Coders. General | 17 | 03 February 2005 09:57 |
|
|