Need your opinion regarding GR8NET capabilities

Fantastic! Great work and thanks a lot for sharing! I already studied the manual, can't wait to try and to integrate it

Really impressive. I agree with Fabf, you have cloud-enabled the MSX!

That browser is pretty awesome . Also the basic extensions look perfect! Can’t wait until it is available.

As for mapper types, maybe also support the ASCII8 and ASCII16 mappers?

Regarding the timer, is it implemented in CPLD/FPGA or is it a feature of the W5100? Does it stop counting when until AB is received in the command register, or does it continue counting (the latter would be more useful I think)? Also, regarding the watchdog, I wonder for what purpose it is there, no other MSX interrupt generators have such a thing and they work well enough without it. With a 10 ms timeout, I wonder if it will be troublesome if there is disk I/O while the timer is running.

An idea, I don’t know if it would be possible, but you could consider to map ROM, RAM and LAN to a single addressing space in 4 banks, with 4 (or 3, with fixed bank 0) page select registers at 5FF0H. So, similar to a Konami mapper, but pages 0-63 for ROM, pages 64-67 for LAN, and pages 128-255 for RAM. It would give a little more flexibility. Seeing as DOS (100H), ROM (4000H) and Basic environment programs (8000H) all have different memory locations, I’m thinking such flexibility may be convenient to access the W5100 at 6000H or 8000H depending on where the user program is located. Or it may want to access the W5100 in a 16K area, or map it to page 4000H to stream a sample to SCC in page 8000H. Just thinking out loud.

Also, I presume the ROM has an ID string for easy detection? It wasn’t mentioned in the manual, I think.

Finally, UNAPI support would still be on my wishlist .

@djh1697: this cart will come pre-assembled.
@Grauw: before further implementation, I need to make hardware prototype. I am at the stage of finalizing it. Still did not find appropriate RJ45, using workaround. Timer is in FPGA. Watchdog is needed in order not to have machine hung with steady interrupt line active. Write your INT38 processing routine and "forget" to reset VDP interrupt. I think you know what I am talking about. During disk I/O interrupts are IMHO disabled, thus it should be tested further. Page mapping idea - great one, thanks. For ROM detection I need clear and standardized procedure of detection, and device type identifier. UNAPI - not now, as I said it has some device-dependent stuff in its specifications, and it needs to be cleared by the community (in other words - by all of you and by MSX standard documentation as far as possible).

nice work sir!