FRAM71B

[Erwin]

(11-01-2016 03:39 PM)Dave Frederickson Wrote:  Understand that ROM's and IRAM's get configured after RAM. When you FREEPORT a module it moves within the address space from RAM to a higher address with the other ROM's and IRAM's. In some max RAM configurations this will cause a configuration warning just like configuring more RAM than can be addressed.

Configuring the module as ROM will, by definition, prevent it from being written.

(11-01-2016 02:14 PM)Erwin Wrote:  ... I see it in the end of the article so I have to take care to put the larger ROMs first.

That's not necessary. The 71's configuration routine takes care of that.


That said, I had no issues configuring FRAM71B as above.

Code:

>PEEK$("2C000",32)
D3E4D5D69718191A9B50D10000000000
>RUN MEMBUF
Port Dev Seq  Size Addr  Type
  0   0   0     4  70000  0  BUILT-IN RAM
  0   1   0     4  72000  0  BUILT-IN RAM
  0   2   0     4  74000  0  BUILT-IN RAM
  0   3   0     4  76000  0  BUILT-IN RAM
  5   4   0   128  30000  0  MAIN RAM
  0   5   0    16  80000  2  HPILROM
  5   0   0    16  88000  2  FTH41 ROM
  5   1   0    32  D0000  2  MATHROM
  5   2   0    32  C0000  2  JPC ROM
  5   3   0    32  B0000  1  FRAM71 TK
  5   5   0    64  90000  2  DATACQ ROM
>

Dave

Hi Dave,

The way you did it is running for me in the same way. But to put the DATA-ACQ module in this space it must be configured as IRAM and that is not possible. When I FREEd this space it does it without an error but it resides as RAM. You can try this with POKE "2C012"; "109100" and then try to FREE it. So maybe its not possible for 64k on the "end" of the FRAM? In the address space it is after the MAIN RAM.

I'm confused at the moment about this. No other have such problems solved? I'll try it in another sequence ... next time.

regards Erwin