FRAM71B

[Erwin]

(01-24-2017 08:18 PM)Dave Frederickson Wrote:  Hi Hans,

POKE"2C000","109100" > Okay. A little different because I want a 64k IRAM.
ON/OFF > Okay. Reports around 83k RAM.
POKE"30000","CAFE" > Okay.
PEEK$("30000",4) > Gives "8D72", not "CAFE". Expected behavior.
SET CN2-4
POKE"30000","CAFE" > Okay.
PEEK$("30000",4) > Gives "CAFE".

FREEPORT(5) works as expected.
Remove CN2-4 and PORT(5) is write-protected as expected.

Now here's the embarrassing part, did I really copy the Data Acq ROM to the IRAM? That configuration is lost and now I'm not so sure.

In any case, thanks, Hans, for the reminder about write protection on Banks 0 and 1.

Regards, Dave

Hi both,

I tried this memory block too. Set the J4-2 and

Code:

POKE"2C000","109100" > for 64k IRAM and then DATA-ACQ ROM.

ROMCOPY DATACQ:TAPE TO :PORT(5);ROMSIZE=65536 [ENTER]

>SHOWPORT
0.05  16384  2
5     65536  1
0      4096  0
0.01   4096  0
0.02   4096  0
0.03   4096  0
>
>RUNMEMBUF
Port Dev Seq  Size Addr  Type
  0   0   0     4  30000  0
  0   1   0     4  32000  0
  0   2   0     4  34000  0
  0   3   0     4  36000  0
  0   5   0    16  F0000  2
  5   0   0    64  D0000  1

So testing the DATA-ACQ ROM

Code:

>RUNSETUP
Reading the HP3421...
Edit File Verify Quit?F
Get New Save Main?M
Edit File Verify Quit?Q
Done

Code:

Peek$("D0000",8) shows ”B3DDDDDE”
Then: POKE"D0000","0000000" > remove IRAM ends with 'illegal access' cause of HW protecting possibility?

POKE"2C000","50D100" > for 64k IRAM to ROM.
Peek$("2C000",8) shows ”50D10000” but type is still on '1' cause of the error before and maybe cause of the hard configured write protection

So I opend open J4-2 ON7OFF

Code:

>RUNMEMBUF
Port Dev Seq  Size Addr  Type
  0   0   0     4  30000  0
  0   1   0     4  32000  0
  0   2   0     4  34000  0
  0   3   0     4  36000  0
  0   5   0    16  F0000  2
  5   0   0    64  D0000  2

now type is '2'

Code:

>VER$
HP71:2CDCC RCPY:E HPIL:1B INST:A TCNV:A FMT:A

Testing DATA-ACQ-ROM is OK again. So it seems this is a possible way to use this space and it is still there. Testing 'memory lost' - program is running so it's all OK.

best regards
Erwin