Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cbmvax!daveh From: daveh@cbmvax.commodore.com (Dave Haynie) Newsgroups: comp.sys.amiga Subject: Re: A2630 board Message-ID: <10438@cbmvax.commodore.com> Date: 30 Mar 90 00:17:44 GMT References: <2002@crash.cts.com> Reply-To: daveh@cbmvax (Dave Haynie) Organization: Commodore, West Chester, PA Lines: 75 In article <2002@crash.cts.com> hawk@pnet01.cts.com (John Anderson) writes: > I just purchased your 68030 board through the student discount offered by >Commodore. It is very slick and I am very impressed. I have your SetCPU >program also but there are a few questions and problems. You obviously have excellent taste in both hardware and software. >Ok, the first question is abou the caching and burst mode. Should I set the >instruction cache *and* the data cache, neither, or either, same question >about the burst modes. I-Cache is perfectly safe to use. The D-Cache is not likely to be a problem with the hard disk controller, but unless the driver explicitly does cache dumps after DMA, there's always a potential problem with data caching. The only driver I know of that flushes the cache where appropriate is the A2091 driver. Data caching also causes trouble with BridgeCards. There's a utility out called CacheCard which will let you modify the cachability of any expansion card, allowing the data cache and the bridge card to co-exist. SetCPU V1.6 (available Real Soon Now) will also adjust things for the BridgeCard. >Two: When I use the CARDROM option like this "CARDROM s:CardROMList" ... >Am I doing anything wrong there... What you really may need is a CARDROM entry for the autoboot card. The 2090 itself doesn't have any ROM, so SetCPU won't try to build a translated ROM image for it. You need to know more about the autoboot card, like its manufacturer and product codes. The SetCPU instructions explain how to build your own entry in the CardROMList file. >.. and can I do the same for the 2630 ROMS & my 2 meg 16 bit RAM ROMS & my >bridgeboard ROMs? You don't need it for any of those. The A2630 ROMs only get used prior to booing. The 16 bit RAM doesn't have any ROM on it, and the BridgeBoard's ROM is only used by the PC side of things. >Three: The KICKROM command doesn't work with Kickstart 1.1, but it does with >1.2 and 1.3, I do "SetCPU KICKROM df0: CONFIG 0" (I've also tried CONFIG 1, >and CONFIG 2, but they don't work either). I don't know of any problem with 1.1. If you have normal autobooting devices, you may have trouble with 1.2 (though some of the autoboot cards for 2090s use a different autoboot technique that actually works under 1.2). Using 1.1 may be annoying, since the expansion.library wasn't around, so none of your expansion stuff will work. If your autoboot card works under 1.2, I would guess that's what's causing the problem booting 1.1. I do know that 1.1 will work OK with 68030s, though there was some problem with FPU context that might mess up operation of the FPU. >And finally Four: Does the 32 bit RAM map itself into $200000 and map the >2 megs of 16 bit RAM into $400000? Yeah, the 32 bit memory is the first autoconfig device, and so currently it'll show up at $00200000. >What does MergeMem (the command in the system drawer of workbench) do to the >two memory section (af anything at all). The largest still says around 1.8 >megs even when I use meremem and type "avail". MergeMem will merge the two memory lists. You won't really see anything much happen with that if you use "SetCPU FASTROM" or similar, since SetCPU locates it's ROM image at the end of 32 bit memory to avoid fragmentation, which is a good idea if you're mainly concerned about fragging 32 bit memory, but a bad idea if you want lots of contiguous memory. Try "SetCPU FASTROM HEAD" and things will look more merged. -- Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy Too much of everything is just enough