nesdev.com
http://forums.nesdev.com/

Membler Industries in 2015
http://forums.nesdev.com/viewtopic.php?f=4&t=12716
Page 4 of 4

Author:  Memblers [ Thu Sep 01, 2016 12:52 am ]
Post subject:  Re: Membler Industries in 2015

facepalm.. sorry man, I just accidentally mangled your post. thought I was editing mine. I need to go to bed. :roll:

edit: OK, I hit the back button to recover it and hopefully have restored it

Author:  lidnariq [ Thu Sep 01, 2016 7:53 pm ]
Post subject:  Re: Membler Industries in 2015

I must have made a typo in my previous test; with my kinda ugly memory dumper, I only ever see the same 512-byte pattern regardless of what all the higher address lines do.

Two different SST39SF040s have the same bytes at offsets $3B-$3D, so maybe that's a lot code (since it differs from Memblers's)

Author:  lidnariq [ Fri Sep 02, 2016 11:53 am ]
Post subject:  Re: Membler Industries in 2015

I wonder if those varying bytes are a date? 0E0C04 could be 2014-December-4 and 0F0601 could be 2015-June-1 ... The datecode on my two (with 0E0C04) is 1446, 46th week of 2014, or mid-November...

Author:  Memblers [ Tue Sep 06, 2016 12:05 am ]
Post subject:  Re: Membler Industries in 2015

I just had a chance to check the date, and it is 1522 on that chip. June 1st was the first day of 23rd week, that's about the right time. That's kinda cool to be able to read that in the software.

Author:  liabellen [ Mon Sep 04, 2017 9:50 am ]
Post subject:  Re: Membler Industries in 2015

This was certainly a very interesting read even though I just noticed it was a bit (very) old :)

Author:  FrankenGraphics [ Wed Jan 10, 2018 5:30 am ]
Post subject:  Re: Membler Industries in 2015

Btw, are these assumptions correct?

-Everything is physically in 32kB banks.
-The tool just takes the same 16kB block and writes it one time in each 32kB bank, at your option, to mimmic a fixed-swappable configuration.

-this means that outside of the tool as-is, one can configure custom partitions; for example:
-8kB interleaved/fixed, 24kB swappable per bank, or vice versa.
-Have a 32kB bank and then a number of banks that behave like 16-16 ones.
-basically any partition you can think of to be useful for your project.

Author:  lidnariq [ Wed Jan 10, 2018 12:25 pm ]
Post subject:  Re: Membler Industries in 2015

You are correct.

32K banking allows for a surprising amount of versatility, including emulating fixed/switchable banks that aren't a power of two.

Author:  zzo38 [ Sat Jan 27, 2018 2:59 am ]
Post subject:  Re: Membler Industries in 2015

I can note something I would have preferred to have: That the register is mapped at $1000-$1FFF and $3000-$3FFF in addition to $5000-$5FFF and $7000-$7FFF (although the $3xxx mapping will rarely if ever be used, it is still there simply due to how the logic is working), and it is written regardless of whether you read from or write to those addresses (if you read, it writes the value read).

Other than that it look like good, I think.

Author:  rainwarrior [ Sat Jan 27, 2018 3:06 am ]
Post subject:  Re: Membler Industries in 2015

zzo38 wrote:
I can note something I would have preferred to have: That the register is mapped at $1000-$1FFF and $3000-$3FFF in addition to $5000-$5FFF and $7000-$7FFF (although the $3xxx mapping will rarely if ever be used, it is still there simply due to how the logic is working), and it is written regardless of whether you read from or write to those addresses (if you read, it writes the value read).

RAM and PPU registers are mirrored there.
https://wiki.nesdev.com/w/index.php/CPU_memory_map

Author:  zzo38 [ Sat Jan 27, 2018 12:00 pm ]
Post subject:  Re: Membler Industries in 2015

rainwarrior wrote:
zzo38 wrote:
I can note something I would have preferred to have: That the register is mapped at $1000-$1FFF and $3000-$3FFF in addition to $5000-$5FFF and $7000-$7FFF (although the $3xxx mapping will rarely if ever be used, it is still there simply due to how the logic is working), and it is written regardless of whether you read from or write to those addresses (if you read, it writes the value read).

RAM and PPU registers are mirrored there.
https://wiki.nesdev.com/w/index.php/CPU_memory_map
I know that. (Those addresses would access both the RAM/PPU and the cartridge simultaneously, which can be useful, but regardless of that, it means one less bit of logic (two, if you also ignore R/W).)

Page 4 of 4 All times are UTC - 7 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/