Wiki editing discussion

Pagina 63/90
56 | 57 | 58 | 59 | 60 | 61 | 62 | | 64 | 65 | 66 | 67 | 68

Van Manuel

Ascended (16958)

afbeelding van Manuel

10-03-2020, 21:28

@rderooy: sure, that can be true, but it doesn't give us any knowledge about this particular case. So, let's not speculate or guess, but just say we don't know.

Van Grauw

Ascended (9335)

afbeelding van Grauw

10-03-2020, 22:52

Held high means connected to 5v.

Van Piter Punk

Master (220)

afbeelding van Piter Punk

10-03-2020, 23:14

sdsnatcher73 wrote:
Piter Punk wrote:

The Philips models with NEC marked PCB's are from Kyocera. Don't know if Kyocera third-partied only the PCBs manufacture or the all assembly to NEC.

I’m not saying you are wrong but am really interested in your source of that information. I think it’s odd that Philips would turn to two OEMs with such similar models but it’s not impossible of course. Kyocera turning to NEC for producing boards is also not unheard of, but having a NEC logo on the board more likely means NEC designed the board not just produced it.

I don't have any document with this information written on it. But:

  1. NEC have their own gate-array ICs, it was very unusual to design a main board around the Kyocera one, unless it was an order from Kyocera;
  2. Also, the BIOS ROM, with the Microsoft Copyright marked in it, were from Kyocera;
  3. There is a better documented Philips-Kyocera appliance that also have its boards silked as NEC.

The last item you can confirm here, take a look at CDI-182 boards. This CD-i player was built in joint venture with Philips and Kyocera, and the boards are marked as NEC.

As I said before, don't know if Kyocera third-partied only the manufacture or all the machine assembly to NEC. I guess the former is most probable.

The CDI-182 is from 1988, so it looks that somewhere in the mid-eighties Kyocera turns to NEC to, at least, manufacture the PCB for some of their products.

sdsnatcher73 wrote:

Either way the VG8235 was listed in the Wiki as being produced by NEC, that would be wrong than if your statement holds.

Yes, that is what I believe.

Van gdx

Prophet (3739)

afbeelding van gdx

11-03-2020, 01:20

Grauw wrote:

Held high means connected to 5v.

I think these pins have to connected to pin 16 of SCART.

https://books.google.co.jp/books?id=6dgWB3-rChYC&pg=PA70

Van Eugeny_Brychkov

Paragon (1169)

afbeelding van Eugeny_Brychkov

12-03-2020, 07:48

What "Turbo-R" table column means in this table?

Is it possible to define what

Quote:

indicates that the Memory Mapper is able to initialise its pages at start itself

exactly means? At what start event? Power cycle? Hard reset? Soft reset? Jump to address 0?
I need the definition to identify if checkmark can be put into the column to identify compatibility. At present GR8NET behaves the same as Carnivore 2, but does not have checkmark for it, and I do not know why there's such a difference and why it was decided this way.

In general, this table seems needs revision.

Van sd_snatcher

Prophet (3348)

afbeelding van sd_snatcher

12-03-2020, 10:58

Mapper auto-initialization means that it initializes it’s the Mapper registers by hardware on hard-reset.

Should be needless to mention, but power-up implies a mandatory hard-reset.

Yes, the corollary is that the soft-reset won’t be covered on MSX1. For that you need to modify the MSX1 BIOS.

Van Eugeny_Brychkov

Paragon (1169)

afbeelding van Eugeny_Brychkov

13-03-2020, 08:10

sd_snatcher wrote:

Should be needless to mention, but power-up implies a mandatory hard-reset.

IMHO quality wiki must not rely on assumptions. I modified the explanation of the citerion for the mapper self-initialization.
FYI: I am focusing on it because I have got a question from our community. So there're colleagues who need clarifications on the subject.

Question still unanswered, what "Turbo-R" column means? Turbo will not use any mapper other than its internal for primary RAM anyway, so what's the sense of this column?

Van Grauw

Ascended (9335)

afbeelding van Grauw

13-03-2020, 08:49

I regularly use mappers in my turboR witg VGMPlay, when it needs more than 256K or 512K, it is important to know if a mapper is incompatible with it.

Van Eugeny_Brychkov

Paragon (1169)

afbeelding van Eugeny_Brychkov

13-03-2020, 08:50

Grauw wrote:

I regularly use mappers in my turboR witg VGMPlay, when it needs more than 256K or 512K, it is important to know if a mapper is incompatible with it.

How it can me incompatible? What is the special in Turbo-R that mapper, designed according to MSX standard, will not work properly in it?

Van Grauw

Ascended (9335)

afbeelding van Grauw

13-03-2020, 08:56

Idk, slight differences in bus timing? Fact is that not all are compatible.

I think in a (Dutch) article in MCCM Digital KC explained some of the hurdles they encountered. It's the same article where they open sourced their mapper design, linked from the wiki page.

Pagina 63/90
56 | 57 | 58 | 59 | 60 | 61 | 62 | | 64 | 65 | 66 | 67 | 68