Post Reply 
[FRAM71] Pre-Production Batch
02-08-2015, 04:28 PM (This post was last modified: 02-08-2015 04:34 PM by Dave Frederickson.)
Post: #17
RE: [FRAM71] Pre-Production Batch
(02-07-2015 06:55 PM)Hans Brueggemann Wrote:  In a recent e-mail, Dave Frederickson pointed out to me that it would be nice to be able to access all 512kB of FRAM, by using some sort of bank switching scheme. i find this idea quite intriguing and FRAM71's FPGA still has ample amount of free logic available (as per V.421) to handle such a task. alas... i'm short on ideas of how to implement that to gain maximum use from such a feature. when looking at the used FRAM address space (nibble addresses),
00000-1FFFF is reserved for diagnostic/alternate O/S,
20000-2BFFF is unused,
2C000-2C01F is reserved for Memory Configuration,
2C020-2FFFF is unused,
30000-FFFFF is reserved for the 0..12 configurable Memory Chips.
that gives basically the range 20000-2BFFFF as a possible candidate for bankswitching.
so, what can we do with that? is it worth a try in the light of the amount of FRAM already available?
what's your take on this, valued users?

It's not the system address space I was suggesting be utilized, but the FRAM memory itself. Currently the 512k FRAM is divided into 16-32k "Chips", 13 of which are available for configuration as RAM or (truly write-protected) ROM. Two are reserved for the SYSRAM feature and the last is unused. What I'm suggesting is that another configuration register, like the 0x2C000 register, perhaps at address 0x2C020, but only 16 bits in length, be created. Each bit would correspond to a 32k Chip in FRAM and if set, that Chip would be "Enabled". The rules would be:
  1. Up to 13 bits can be set at one time, corresponding to Chips 12 - 0.
  2. The two least significant bits are reserved for SYSRAM and are always zero

By manipulating the bits the "active" Chips can be switched making different ROM configurations possible without reloading an image. It should be possible to load an alternate O/S into the 64k SYSRAM and configure the other 14-32k Chips into RAM or ROM.

For example, if 0x2C020 is loaded with 0xF000 and that would enable the 0xF0000 block of FRAM. This would be mapped into Chip 12 and 32k ROM1 could be load into it. If 0x2C020 were loaded with 0x8000 that would enable the 0xE0000 block of FRAM and 32k ROM2 could be load into it. The significant difference is that the set bits in 0x2C020 determine which blocks of FRAM get mapped to Chips, so 0xE0000 become Chip 12, also. By manipulating the bit in 0x2C020 either ROM1 or ROM2 can be enabled.

Another example, load 0x2C020 with 0xFFF8 enabling 13 blocks of FRAM starting at 0x30000 and load 0x30000 with ROM1. Load 0x2C020 with 0xFFFB enabling 13 blocks of FRAM starting at 0x20000 with the 32k block at 0x30000 disabled. Memory at 0x20000 gets mapped to Chip 0 and ROM2 can get loaded into FRAM at 0x20000. Now 14-32k blocks of FRAM can be utilized for RAM or ROM, with the limitation of only 13 of those being enabled at one time.

The FRAM configuration registers at 0x2C000 would need to be moved to the NVRAM in the FPGA, if they're not already there.

Does that make sense? It's important to understand that FRAM memory would get mapped to Chips which then get mapped to 71B address space by the 71's O/S during the power-on memory configuration.

Dave
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
ROM Images - Dave Frederickson - 12-10-2014, 03:51 AM
IRAM vs ROM - Dave Frederickson - 12-13-2014, 06:36 PM
ROMCOPY - Dave Frederickson - 12-20-2014, 08:59 PM
[FRAM71] Bankswitching? - Hans Brueggemann - 02-07-2015, 06:55 PM
RE: [FRAM71] Pre-Production Batch - Dave Frederickson - 02-08-2015 04:28 PM
v430 beta - Dave Frederickson - 02-16-2015, 06:09 AM
RE: [FRAM71] Pre-Production Batch - cruff - 02-11-2015, 11:45 PM
v430 beta - Dave Frederickson - 02-17-2015, 05:14 AM
v430 beta - Dave Frederickson - 02-27-2015, 05:20 AM
1MByte FRAM71 - Dave Frederickson - 03-14-2015, 09:18 PM
RE: [FRAM71] Pre-Production Batch - Gene - 03-15-2015, 02:04 AM
V501 Firmware woes - Hans Brueggemann - 04-23-2015, 07:12 PM
Eagerly awaiting mine - cruff - 04-24-2015, 12:40 AM
RE: [FRAM71] Pre-Production Batch - cruff - 04-24-2015, 12:53 PM
Received my FRAM71 today! - cruff - 04-25-2015, 07:03 PM
RE: [FRAM71] Pre-Production Batch - cruff - 04-26-2015, 12:27 PM
RE: [FRAM71] Pre-Production Batch - Erwin - 10-04-2016, 08:28 PM
MEMBUF - Dave Frederickson - 05-13-2015, 02:50 AM
FRAM71 V502 - Hans Brueggemann - 05-16-2015, 04:02 PM
RE: [FRAM71] Pre-Production Batch - Erwin - 01-02-2016, 08:13 AM
RE: [FRAM71] Pre-Production Batch - Oulan - 06-03-2015, 02:10 PM
RE: [FRAM71] Pre-Production Batch - Oulan - 06-03-2015, 03:47 PM
RE: [FRAM71] Pre-Production Batch - Oulan - 06-05-2015, 09:44 AM
RE: [FRAM71] Pre-Production Batch - Oulan - 06-08-2015, 07:13 AM
FlashPRO - Dave Frederickson - 06-11-2015, 03:42 PM
RE: [FRAM71] Pre-Production Batch - cruff - 06-13-2015, 12:04 PM
RE: [FRAM71] Pre-Production Batch - cruff - 06-15-2015, 11:22 PM
Blinkin' Lights - Dave Frederickson - 07-15-2015, 03:07 AM
FRAM71 LED - Hans Brueggemann - 07-16-2015, 11:47 AM
RE: [FRAM71] Pre-Production Batch - Andres - 01-25-2016, 10:40 PM
RE: [FRAM71] Pre-Production Batch - Erwin - 10-04-2016, 08:46 PM
RE: [FRAM71] Pre-Production Batch - Erwin - 10-04-2016, 09:04 PM



User(s) browsing this thread: 2 Guest(s)