Post Reply 
FRAM71B
10-08-2016, 06:59 AM (This post was last modified: 10-08-2016 11:52 AM by Erwin.)
Post: #32
RE: FRAM71B
(10-07-2016 11:21 PM)Dave Frederickson Wrote:  
(10-06-2016 04:53 AM)Sylvain Cote Wrote:  Assuming you have followed my guide, you should have the following configuration

PEEK$("2C000",32) -> "D3E4D5D69798191A1B1C9D0000000000"

I would suggest to modify it for the following

POKE("2C000","D3E4D5D69798991A1B1C9D0000000000") / power cycle

It appears that you've split main RAM into two modules by reconfiguring the F-Blocks. This is kind of like unplugging a module and plugging in different modules, but you didn't follow the rules for unplugging RAM modules, Para. 4.2.

Unconfiguring or “removing” a FRAM RAM module

1. When a RAM module is to be removed it is first converted to IRAM using the FREE PORT command. Some front-port modules, like the CMT 64K module, contained a battery that would maintain the IRAM contents. When it was later reinserted it would appear in the 71’s memory configuration as IRAM, complete with its contents. This happened to Forum member Mike in 2003 when CMT 64K module batteries still had a charge:
http://www.hpmuseum.org/cgi-sys/cgiwrap/...read=49425
Modules without a battery will lose their contents and reappear as main RAM. FRAM71/B can behave as either.
a. Battery-Backed: To unconfigure or “remove” a FRAM RAM module, first convert the module to IRAM using the FREEPORT command, then unconfigure the module by POKEing zeros into the appropriate location in the configuration string.
b. Non Battery-Backed: First, convert the module to IRAM. Determine the module’s address using MEMBUF. POKE <address>,”00000000”, which overwrites the module’s IRAM identifier, and unconfigure the module in the config string. The next time the module is configured it will be detected as unused memory and configured as RAM.

Dave

Good morning,

I hope I understand Dave's post right. Different ROM-sizes need CLAIMPORT and FREEPORT than the new POKE and therefore should be at the end of the 'whole thing'. With the FRAM71-docu, the 'Denver' presentation and the many comments I came to the following model to avoid make the SYSRAM corrupt.
Plan: JPCROM, MATHROM, 41FORTH, CURVEFIT, AMPITSTAT, DATA-ACQ, TEXT-EDITOR (or CIRCUIT) and FINANCE in the SYSTEM with the maximum amount of SYSRAM.
To configure the guest ROM (for the 64KB module too) without touching the SYSRAM. That means 144KB of SYSRAM every time (only 'loosing' possible 32KB RAM when switched to FINANCE and TEXT-EDITOR).

Am I right with this, I'm not sure about the FRAM banks, somebody a hint? Then maybe I'll start this on this weekend.

BASIC-CONFIGURATION POKE "C2000","3E4D5D69718191A1BACDDDE" (final statement after extend Sylvains intermediate guide)
Code:

Chip_#  Addr.  Configuration  Description      of        LCIM  Type   Size  Port
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_0  2C000  CONF     D                                                       
Chip_0  2C001  F-BLOCK  3     HC E0000 T41 ROM             1    ROM    32   n/a
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_1  2C002  CONF     E                                                       
Chip_1  2C003  F-BLOCK  4     16KB SC T41 ROM              1    ROM    16   5.00
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_2  2C004  CONF     D                                                       
Chip_2  2C005  F-BLOCK  5     32KB Math ROM                1    ROM    32   5.01
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_3  2C006  CONF     D                                                       
Chip_3  2C007  F-BLOCK  6     32KB JPC ROM                 1    ROM    32   5.02
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_4  2C008  CONF     9                                                       
Chip_4  2C009  F-BLOCK  7     32KB Backup IRAM             1    RAM    32   5.03
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_5  2C00A  CONF     1                                                       
Chip_5  2C00B  F-BLOCK  8     System RAM 144KB 1 of 5      0    RAM    32   5.05
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_6  2C00C  CONF     1
Chip_6  2C00D  F-BLOCK  9     System RAM 144KB 2 of 5      0    RAM    32   5.05
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_7  2C00E  CONF     1
Chip_7  2C00F  F-BLOCK  A     System RAM 144KB 3 of 5      0    RAM    32   5.05
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_8  2C010  CONF     1
Chip_8  2C011  F-BLOCK  B     System RAM 144KB 4 of 5      0    RAM    32   5.05
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_9  2C012  CONF     A
Chip_9  2C013  F-BLOCK  C     System RAM 144KB 5 of 5      1    RAM    16   5.05
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_A  2C014  CONF     D     CURVEFIT
Chip_A  2C015  F-BLOCK  D     32 KB Guest ROM              1    ROM    32   5.06
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_A  2C016  CONF     D     AMPISTAT
Chip_A  2C017  F-BLOCK  E     32 KB Guest ROM              1    ROM    32   5.07
------  -----  -------------  -------------------------- ----  -----  ----  ----

EXTENDED 1-CONFIGURATION for the DATA-ACQ 64KB module must switched to following example, 'loosing' one port? But this should'n affect the system.
For the first time installation it is necessary to CLAIMPORT 5.06 and 5.07 (free the installation for CURVFIT and AMPISTAT) FREEPORT 5.06 and ROMCOPY (with the checksum option like the doc says but this part is not clear for me, the added comments from Joe Horn says CHECKSUM is automatic)?

POKE "C2000","3E4D5D69718191A1BAC50D0" ??? that's not clear for me

Code:
view without FRAM banks
Chip_#  Addr.  Configuration  Description      of        LCIM  Type   Size  Port
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_A  2C014  CONF     5     DATA-ACQ
Chip_A  2C015  F-BLOCK  D     32 KB Guest ROM              0    ROM    32   5.06
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_A  2C016  CONF     D     DATA-ACQ
Chip_A  2C017  F-BLOCK  E     32 KB Guest ROM              1    ROM    32   5.06
------  -----  -------------  -------------------------- ----  -----  ----  ----

Switching back in the same manner: CLAIMPORT 5.06 and FREEPORT 5.06 and 5.07 then the bank-switching again.

EXTENDED 2-CONFIGURATION same for the TEXT-EDITOR (or CIRCUIT) and FINANCE module

POKE "C2000","3E4D5D69718191A1BACD1E1" ??? that's not clear for me
Code:
view without FRAM banks
Chip_#  Addr.  Configuration  Description      of        LCIM  Type   Size  Port
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_A  2C014  CONF     E     FINANCE
Chip_A  2C015  F-BLOCK  D     16 KB Guest ROM              1    ROM    16   5.06
------  -----  -------------  -------------------------- ----  -----  ----  ----
Chip_A  2C016  CONF     E     TEXT-EDITOR (CIRCUIT)
Chip_A  2C017  F-BLOCK  E     16 KB Guest ROM              1    ROM    16   5.07
------  -----  -------------  -------------------------- ----  -----  ----  ----

EDIT: the other way would be to put away 32KB from SYSRAM so there is 112KB free SYSRAM in the FRAM71 and put the TEXT-EDITOR (or CIRCUIT) and the FINANCE module in there. The sum of free memory with the 16KB base RAM would be 128KB, additional the 32KB in BACKUP IRAM. Seems to be enough to and offers the possibility to do bank switching with 3*32KB modules.

DOCU: a proposal
Theory ... mainly distributed in different threads: Docs like: Tools Some practical examples one basic to learn and one intermediate: 2 or 3 more advanced examples with FRAM bank switching, with and without TOP RAM

Program for bank-switching?

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


Messages In This Thread
FRAM71B - Hans Brueggemann - 05-22-2016, 08:26 AM
RE: FRAM71B - Sylvain Cote - 05-22-2016, 02:46 PM
RE: FRAM71B - Dave Frederickson - 05-25-2016, 07:16 PM
RE: FRAM71B - Dave Frederickson - 05-22-2016, 04:13 PM
RE: FRAM71B - Hans Brueggemann - 05-22-2016, 04:54 PM
RE: FRAM71B - Dave Frederickson - 05-22-2016, 05:14 PM
RE: FRAM71B - Hans Brueggemann - 05-22-2016, 07:09 PM
RE: FRAM71B - Dave Frederickson - 05-27-2016, 04:59 PM
FRAM71B HC ROM Feature - Dave Frederickson - 10-02-2016, 03:09 PM
RE: FRAM71B - Erwin - 10-05-2016, 10:45 AM
RE: FRAM71B - Dave Frederickson - 10-05-2016, 03:42 PM
RE: FRAM71B - Erwin - 10-05-2016, 07:36 PM
RE: FRAM71B - Dave Frederickson - 10-05-2016, 08:10 PM
RE: FRAM71B - Erwin - 10-05-2016, 08:25 PM
RE: FRAM71B - Sylvain Cote - 10-06-2016, 04:53 AM
RE: FRAM71B - Erwin - 10-06-2016, 06:24 AM
RE: FRAM71B - Dave Frederickson - 10-06-2016, 03:55 PM
RE: FRAM71B - Erwin - 10-06-2016, 05:41 PM
RE: FRAM71B - Dave Frederickson - 10-06-2016, 06:19 PM
RE: FRAM71B - Erwin - 10-06-2016, 07:43 PM
RE: FRAM71B - Dave Frederickson - 10-06-2016, 08:14 PM
RE: FRAM71B - Sylvain Cote - 10-06-2016, 07:03 PM
RE: FRAM71B - Erwin - 10-06-2016, 07:50 PM
RE: FRAM71B - Dave Frederickson - 10-07-2016, 11:21 PM
RE: FRAM71B - Sylvain Cote - 10-08-2016, 01:20 AM
RE: FRAM71B - Erwin - 10-08-2016 06:59 AM
RE: FRAM71B - Sylvain Cote - 10-07-2016, 04:45 AM
RE: FRAM71B - Erwin - 10-07-2016, 07:10 AM
RE: FRAM71B - Sylvain Cote - 10-07-2016, 03:10 PM
RE: FRAM71B - rprosperi - 10-07-2016, 01:22 PM
RE: FRAM71B - Erwin - 10-07-2016, 03:04 PM
RE: FRAM71B - Dave Frederickson - 10-07-2016, 05:54 PM
RE: FRAM71B - Dave Frederickson - 10-08-2016, 03:35 PM
RE: FRAM71B - Sylvain Cote - 10-08-2016, 06:21 PM
RE: FRAM71B - Erwin - 10-08-2016, 08:21 PM
RE: FRAM71B - Erwin - 10-23-2016, 09:07 AM
RE: FRAM71B - rprosperi - 10-23-2016, 01:25 PM
RE: FRAM71B - Erwin - 11-01-2016, 09:26 AM
RE: FRAM71B - J-F Garnier - 11-01-2016, 10:13 AM
RE: FRAM71B - Erwin - 11-01-2016, 10:48 AM
RE: FRAM71B - rprosperi - 11-01-2016, 01:42 PM
RE: FRAM71B - Erwin - 11-01-2016, 02:14 PM
RE: FRAM71B - Dave Frederickson - 11-01-2016, 03:39 PM
RE: FRAM71B - Erwin - 01-22-2017, 10:18 AM
RE: FRAM71B - Erwin - 12-30-2016, 12:26 PM
RE: FRAM71B - rprosperi - 12-30-2016, 02:49 PM
RE: FRAM71B - Dave Frederickson - 12-30-2016, 06:57 PM
RE: FRAM71B - Erwin - 01-05-2017, 07:57 PM
RE: FRAM71B - Erwin - 01-22-2017, 02:02 PM
RE: FRAM71B - Dave Frederickson - 01-22-2017, 05:30 PM
RE: FRAM71B - Erwin - 01-22-2017, 06:55 PM
RE: FRAM71B - Hans Brueggemann - 01-23-2017, 08:29 PM
RE: FRAM71B - Dave Frederickson - 01-23-2017, 09:11 PM
RE: FRAM71B - Erwin - 01-24-2017, 06:15 PM
RE: FRAM71B - Hans Brueggemann - 01-24-2017, 07:51 PM
RE: FRAM71B - physill - 11-22-2016, 10:53 PM
RE: FRAM71B - Dave Frederickson - 11-23-2016, 12:34 AM
RE: FRAM71B - physill - 11-24-2016, 05:55 PM
RE: FRAM71B - Dave Frederickson - 11-24-2016, 06:17 PM
RE: FRAM71B - Sylvain Cote - 12-30-2016, 07:55 PM
RE: FRAM71B - dayd - 01-17-2017, 09:07 AM
RE: FRAM71B - rprosperi - 01-17-2017, 03:01 PM
RE: FRAM71B - Hans Brueggemann - 01-17-2017, 09:11 PM
RE: FRAM71B - dayd - 01-22-2017, 04:22 AM
RE: FRAM71B - J-F Garnier - 01-17-2017, 05:07 PM
RE: FRAM71B - Erwin - 01-22-2017, 09:34 AM
RE: FRAM71B - Dave Frederickson - 01-22-2017, 07:06 PM
RE: FRAM71B - Erwin - 01-22-2017, 07:21 PM
RE: FRAM71B - Hans Brueggemann - 01-24-2017, 09:03 AM
RE: FRAM71B - Dave Frederickson - 01-24-2017, 04:34 PM
RE: FRAM71B - Hans Brueggemann - 01-24-2017, 07:33 PM
RE: FRAM71B - Dave Frederickson - 01-24-2017, 08:18 PM
RE: FRAM71B - Erwin - 01-25-2017, 06:54 PM
RE: FRAM71B - Hans Brueggemann - 01-25-2017, 07:47 PM
RE: FRAM71B - dayd - 02-01-2017, 10:20 PM



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