Demonstration of "Pentagon 128" and about TS-Conf

[PiyoTaro]

Synopsis.
"ZX Spectrum Next" can be adjusted to specification of Spectrum clone machine by TBBlue config menu or dot command.
A video of a demo program for "Pentagon 128" has been posted on official facebook since last month.
https://en.wikipedia.org/wiki/Pentagon_(computer)


By the way, adding TSConf's "Sprite and Tile" screen and two SID Sound to the core of the specification of "ZXSpectrum 128", how many LEs will the core be?
In order to make arcade style games more easily and casually, I came up with another machine as "Option core".

---
About rewriting the FPGA

Lately, I opened a "2B board" and started using it as a game machine.
I tried work to upgrade the system core from "1.00.00" to 1.00.10 or 1.00.51. When the "TBBlue" logo mark is displayed, pressing the "U" key on the PS/2 keyboard will bring up a screen to confirm the firmware recorded on the SD card. It took less than 1 minute to erase and update.
Normally, to update "FPGA", create a JIC file or rewrite it using "Quartus" application on Windows PC with USB blaster installed.
On the other hand, "ZXUno" or "TBBlue" will rewrite if you select the core on the flash on the menu screen, and since there is an Anti-brick system, it can be said that renewal of the FPGA is easy.

However, it takes time to update the core "one minute", and it is difficult to explain the Anti-brick system. I think that it is not realistic to distribute the "new machine" in the SD card of the application along with the application.

[Alcoholics Anonymous]

However, it takes time to update the core "one minute", and it is difficult to explain the Anti-brick system. I think that it is not realistic to distribute the "new machine" in the SD card of the application along with the application.

There are 32 positions in the flash to store cores. Positions 0 and 1 are reserved for the anti-brick and zx next cores respectively.

During a normal boot process, two cores are in fact loaded by the fpga. At power up, it is the anti-brick core that is loaded into the fpga and runs the boot process. The zx next core is loaded in the final step before machine reset.

If the firmware is changed on an sd card, it can be reprogrammed to load any core on machine reset so it would be very easy to distribute sd cards for other cores. The core only has to be saved into the flash (that's the one minute process you spoke about) and after that the machine could boot into that core just like the zx next is normally booted into.

[chernandezba]

not so long ago Im ported Sonic from SegaMasterSystem on Ts Configuration:
http://prods.tslabs.info/

Please give me a manual or wiki that summarizes the specifications of "sprite chip" in English!
I can also use TSConf on the FPGA machine, so I would like to create something application.

All the info it's in the previous post I made

[PiyoTaro]

not so long ago Im ported Sonic from SegaMasterSystem on Ts Configuration:
http://prods.tslabs.info/

Please give me a manual or wiki that summarizes the specifications of "sprite chip" in English!
I can also use TSConf on the FPGA machine, so I would like to create something application.

All the info it's in the previous post I made

I am reading the TSLab forum which is introduced in the reply from chernandezba.
I also found an article link from VBI on "Tile & Sprite".

Also, there is a thread of topics similar to here on the ZX-Uno Forum.
"What exactly is TS-CONF?" http://www.zxuno.com/forum/viewtopic.php?f=37&t=1871

---
However, when I bring this topic already, I am watching them.
In GitHub I found a document folder of "TS-Conf" project (quoted in the article) and the "ZX-Evolution" project in its upper directory.
I will comment on after reading a little more. Should I post before I can understand the specification of "Baseconf"?

[EtchedPixels]

It's true to the Russian spectrum scene I think - it's not got a pretty case design like the Next, but it's way more powerful in many other ways. The I/O port documentation isn't that hard to read with a translation tool.

The big differences (booting with baseconf)
- It has a real Z80 processor (3.5/7/14Mhz - wait states on 14) not an FPGA clone. FPGA is only used for the I/O side along with an ATMEGA128
- 4MB RAM as standard (I've no idea what to do with most of it!)
- Up to 512K ROM
- It leans more towards Pentagon 1024 and ATM2+ than the classic UK Speccy so some clever timing tricks work differently (and there ar e some border tricks only the Pentagon can pull off well)
- Fits a MiniITX case and PC keyboard (including software being able to get at the PS/2 directly)
- Video is based on the ATM modes (up to 640x200 multicolour, 320x200x16 colour and 80x25 text mode), with some seriously weird mappings. Somewhat better than the limited Timex modes on the Next but also nothing in baseconf equivalent to layer2 (see TSconf though) and no copper equivalent.
- IDE controller similar to NemoIDE rather than the UK Div*. Read performance is as good as DivIDE (or better than the naïve DivIDE implementation due to ULA wait states). Write is slower.
- SD card interface is slightly different arrangement of ports but much of a muchness
- Real floppy controller (Beta-disk TR-DOS style as with all Russian systems I've ever met)
- Real serial port (16x50ish)
- RTC
- 16K rather than 8K banking
- Two ZXBUS slots
- CP/M support (already existing)
- System is out (which won't be a difference much longer with luck)
- about £125 (plus customs if they remember to charge you)

Or you can boot it in ts-conf which doesn't have some of the ATM video modes but instead has tiled video, and some very powerful sprite modes. Kind of two machines in one.

[EtchedPixels]

As an aside you really want to emulate not the Pentagon 128 but the later Pentagons, and you need the disk emulation parts of it and TR-DOS stuff.

The later Pentagon allows you to map RAM bank 0 at 0000-3FFF and that is rather useful for all kinds of things.

[chernandezba]

I will comment on after reading a little more. Should I post before I can understand the specification of "Baseconf"?

Well it's not necessary you understand the baseconf specs. Baseconf and TSConf have the same hardware base (ZX Evolution) but then the two firmwares are almost completely different: they are Speccy compatible but the extensions are different between them: different extra modes, sprites&tiles only in tsconf and not in baseconf, different memory management, etc