Jump to content

kl99

Members
  • Content Count

    1,032
  • Joined

  • Last visited

  • Days Won

    3

kl99 last won the day on August 24 2019

kl99 had the most liked content!

Community Reputation

901 Excellent

About kl99

  • Rank
    Stargunner

Profile Information

  • Gender
    Male
  • Location
    Vienna, Austria

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. >9000 - >947F initial header at >9000 was not found yet. the part from >9050 to >9093 is a list of data words defining the XML Table. i will fix those missing pieces once I completed the issues in the known matching memory areas. >9480 - >98FF >9900 - >9DFF >9D80 - A1FF >A200 - >A67F here we have still a missing piece, therefore at this stage all empty ("00") on the compiled side. again, once all known matching memory locations are without any differences I can start searching for this piece again. >A680 - AAFF >AB00 - AF7F >AF80 - B3FF this memory area is still is work in progress. the non matching parts are within trinsics2.asm, but its length is already correct. here we have another missing piece from >B348 to >B4DD. >B400 - B87F the big yellow part is the continued missing piece from the last page. some inconsistencies within crunchs.asm. >B880 - BCFF mostly empty still.
  2. Hi FP, not sure what you exactly mean. But there is no need to have the actual hardware in order to talk about a certain system. Both the TI-99/8 and the TI-99/2 systems are nicely emulated in MAME, even though these computers were never released to the market and got canceled when the engineering lab still worked on finishing them. Any hardware or software or tools talk is welcome about machines falling in this subforum category.
  3. Hi John! Will be there. Trying to prepare and share a video today.
  4. The yellow parts are mostly not defined, because I didn't find matching source code files. There is still some uglyness, but we are getting there. >9000 - >947F >9480 - >98FF >9900 - >9DFF >9D80 - A1FF >A200 - >A67F >A680 - AAFF >AB00 - AF7F >AF80 - B3FF >B400 - B87F >B880 - BCFF (longer now, therefore more yellow than earlier)
  5. here is one documentation of getting RGB out on Tomy Pyuta devices, partely using F18A https://sions-papa.blogspot.com/2012/10/tms9918rgb.html
  6. Here is the PCB order for a replacement keyboard PCB, might be working with Pyuta only though. https://www.beep-shop.com/ec/products/detail/4976
  7. Hi, ROM0 might be different between a japanese Tomy Pyuta and an american Tomy Tutor. Afaik there are only dumps available for the American Tomy Tutor. There are japanese emulators that somehow must have those ROMS integrated (extra files or integrated within their executable like Classic99).
  8. last state before ending the weekend. big work week ahead. so don't expect too many updates. it is astounding how much percentage of the Tomy Tutor ROM1 is covered by xb source code, originating from Texas Instruments. >9000 - >947F >9480 - >98FF >9900 - >9DFF >9D80 - A1FF >A200 - >A67F >A680 - AAFF >AB00 - AF7F >AF80 - B3FF >B400 - B87F >B880 - BCFF
  9. Latest status: >9000 - >947F >9480 - >98FF >9900 - >9DFF >9D80 - A1FF >A200 - >A67F >A680 - AAFF >AB00 - AF7F >AF80 - B3FF >B400 - B87F >B880 - BCFF
  10. To help understanding: Left side is the Tomy Tutor ROM1 dump. Right side is the binary that is generated by using an TMS9900 assembler (XDT99 by @ralphb) on the TI Extended Basic ROM Source code files (thanks to @RXB for their preservation). The TI Extended Basic ROM Source code files did get minimally adapted, but there is no other sources involved in generating the binary on the right side. The goal is to have a binary identical output across the whole thing to prove that Tomy Tutor BASIC comes from the TI Extended Basic ROM.
  11. after some work on the first part >9000 looks nicer now. >9000 - >947F
  12. Just to share the current state. The XB source code files were adapted to compile towards their Tomy Tutor location, as far as I discovered their locations. Here is the list with their currently assumed AORGs COPY "xml359.asm" * >90A4 COPY "cpt.asm" * >9136 COPY "bassups.asm" * >9176 COPY "parses.asm" * >9416 COPY "parses2.asm" * COPY "getputs.asm" * >9BF0 COPY "cifs.asm" * >9C2C COPY "nud359.asm" * >9C84 COPY "strings.asm" * >9E74 COPY "speeds.asm" * >A03A COPY "fornexts.asm" * >A140 COPY "scrolls.asm" * >A3E0 COPY "scans.asm" * >A5C6 COPY "delreps.asm" * >A748 COPY "mvdns.asm" * >A7AA COPY "cns359.asm" * >A7E4 COPY "cns3592.asm" * COPY "trinsics.asm" * >AC70 COPY "trinsics2.asm" * COPY "crunchs.asm" * >B4E0 COPY "ref359.asm" * >B9EE ERAM (short for expansion ram I assume) related source code I couldn't find in the Tomy Tutor ROM1. I therefore removed "mvups.asm", "greads.asm", "gwrites.asm", "vgwites.asm", "gvwites.asm" from compiling, also all instructions to cover ERAM were typically skipped in the ROM1, so removing those same lines from the XB source code files made the compiled output with more matching bytes. Also I didn't find yet the rather big "subprogs.asm", "subprogs2.asm" in the Tomy Tutor ROM1, there is no CALL support in its BASIC (or let's say done differently), so maybe it is not in there at all. The scratchpad RAM seems to be at F000-F0FF instead of 8300-83FF. I only did work on ROM1 so far, which is known to contain BASIC. ROM1 is from >8000 to >BFFF. I didn't find any matching ASSEMBLY in >8000->8FFF yet, maybe there is the GPL, so the visual comparison starts from >9000. White parts are matching on binary level, yellow parts are wrong or only at the wrong location. The more white you see in the visual diff, the more bytes from the Tomy Tutor ROM1 have the same value at the same location as the compiled binary of this XB Source code. Some parts are already very white. Even in the almost white parts there are jumps towards other addresses, those target locations are referred via their LABEL name in the XB assembly source code, not via absolute addresses. If the LABEL is still defined at another location, then the instruction to jump to that LABEL at the moment still contains another absolute address in its compiled form. Matching content, but at different locations still shows as yellow. So if a whole 1Kilobyte block is off by two bytes, but matching, it never the less shows yellow. The binary length of some compiled source code files might extend the actual length in ROM1, making some parts in memory being overlapped. Such things will solve, once the individual files are adapted to the Tomy Tutor version. Remember any instructions to read GROM or wait for GROM are not necessary in the Tomy world and were removed, so I need to find them and repeat the developers activities from 40 years back. In short, yellow color doesn't mean, that the Tomy Tutor Basic is different from XB Basic and was not coming from it, only that my version of the XB source code is not yet binary matching in those segments. There might be some instructions missing or too much or sorted different to fix the length of things. >9000 - >947F >9480 - >98FF >9900 - >9DFF >9D80 - A1FF >A200 - >A67F >A680 - AAFF >AB00 - AF7F >AF80 - B3FF >B400 - B87F >B880 - BCFF
  13. Thanks for your help jedimatt42! Can you share the commands on how to compile your tools sourcecode to an executable? I mean the python compilation of the tool. Just made a big milestone. I was able to compile the original XB Rom Sourcecode for both rom banks using xdt99 into their binaries that were released on Module as TI Extended Basic (v1.10). The compiled version matches the Module dumps in all 16384 bytes. I had to adapt the original XB rom source code (thanks to RXB) only minimally. xdt99 doesn't seem to accept the character $ within the labelname, however this was widely used. Three lines had to get an additional space before their comment to not be treated as an operand. And the two control files that COPY all other files from the same rom got their TI device reference (COPY "DSK6.EQUATES") changed to reference the PC device filepath (COPY "equates.asm") instead. That was it. Now that I know how to compile these source codes I can adapt the AORGs to compile them towards their Tomy Tutor locations to verify all above statements.
  14. TOMY using Texas Instruments XB Source Files: FROM - TO LENGTH >9C2C - >9C83 >0058 CIFS >9E74 - >A037 >01C4 STRINGS >A140 - >A3DF >02A0 FORNEXTS >A7E4 - >AB12 >0330 CNS359 >AB13 - >AC71 >015E CNS3592 >AC72 - >B345 >06D4 TRINSICS,TRINSICS2 >B4E0 - >B8F1+ >0412 + CRUNCHS (last data bytes not identical, hard to specify last byte)
×
×
  • Create New...