Started by Duke, 09:36, 07 May 16
0 Members and 4 Guests are viewing this topic.
Quote from: TotO on 17:54, 11 June 16If the X-MEM conflict is related to the ROM part, you should try to set the jumper to NO for disabling them.
Quote from: dirtybb on 18:00, 11 June 16I tried here but it doesn't work. When M4 and XMEM both plugged, with XMEM rom jumper set to "No", CPC (6128) reset in loops.
Quote from: Duke on 16:45, 11 June 16If you have the time, it would be useful if you put a regular rom like maxam at ie. pos 14 on the M4 board (and no other rom at that pos in xmem) and disable the M4 rom itself.Does it boot and will maxam work?
Quote from: Duke on 18:11, 11 June 16Is this with external power supply connected to either M4 or MX4, or using internal power supply ? (just in case)
Quote from: Duke on 16:45, 11 June 16@Maniac Thanks for the comprehensive tests.It'll be hard for me to debug since I don't have C4CPC nor XMEM.When M4 rom is disabled in config, all the running code is exactly the same on the M4 board(ie. you would still be able to use the rom board function) except it doesn't try to map the rom containg M4 z80 part (and thus not driving the datalines).I'll have a think about your post. If you have the time, it would be useful if you put a regular rom like maxam at ie. pos 14 on the M4 board (and no other rom at that pos in xmem) and disable the M4 rom itself.Does it boot and will maxam work?
Quote from: Duke on 18:55, 11 June 16I can easily move the rom range, but all cas_* hooks (for native file I/O) would be overwritten by AMSDOS/PARADOS if not lower, unless there is a method to disable rom 7 in XMEM.
Quote from: Duke on 18:55, 11 June 16@DirtybbNot sure what the problem is, since we now have two conflicting tests, what CPC you use for the test? (also a CPC+?)
Quote from: gerald on 18:15, 11 June 16The XMEM (like most oster ROM extension), when connected will drive the bus during access to ROM in they slot range.ROM access is indicated by ROMEN low and the ROM selection in range 1-6,8-31 (0-6,8-31 in boot mode to override the basic/system ones)This will happen whatever the content of the ROM is, be it 'empty' or valid.So when using the M4 with an XMEM the only available slots are slot 7(that you cannot override on a 6128), and slot after 32(not initialised).The only way to make this work would be : - remove the ROM device from the xmem so it cannot drive the data bus and create a data contention. The xmem will be act as a RAM extension only.- or use a MotherX4 like card that chain the ROMEN/ROMDIS so the order of the connector decide the priority of the ROM extension.About C4CPC and plus ROM mapping :- after booting, the C4CPC will behave like a regular cartridge, unless you knock at the uC door via strict order reading within the ROM.- 32 ROM in a cartridge are mapped from upper ROM slot 128 to slot 160, with slot 128 mirrored as lower ROM, slot 129 as upper ROM 0 and slot 130 as upper slot 7 (or 0, if EXT signal is grounded)- the cartridge will obey the ROMDIS signal for every slot, so you can mask any ROM with an external interface.A problem may happen if :- you unintentionally knock at the C4CPC uC door (4 consecutive read in specific upper rom slot), and try to read/execute from a ROM within the cartridge- the RAMDIS signal you send is too short and the C4CPC is corrupting the data you send. The ROMDIS sould be as long as the ROMEN, which is as long a the MREQn/RDn signal from the Z80 + the combinatorial delay.
Quote from: TotO on 19:02, 11 June 16The X-MEM is always disabled when ROM7 is set. (physicaly used for the alternate FW)But, you should install a ROM into the X-MEM lower range for doing your CAS_* hooks, ... (lost one and won 32)
Quote from: SRS on 22:28, 12 June 16Now just speculating:could this board be used as mega-copro ? calculation sprites/grafix/mandelbrot and giving cpc access to the results ? If, how so ?
Quote from: Maniac on 21:31, 12 June 16I'll try and test this later but I have limited time today due to real life otherwise will take a look tomorrow after work! Thanks for your continued efforts to make it as compatible as possible.One nice feature I'd quite like to see in the web interface would be the ability to enable/disable ROM slots. Would that be possible please?
Page created in 0.139 seconds with 53 queries.