MSX terminal

صفحة 2/2
1 |

بواسطة Briqunullus

Champion (405)

صورة Briqunullus

31-08-2021, 10:53

What you are showing is nothing short of amazing. I'm very curious of where this will lead. File transfer would be great, I'm almost envisioning some sort of containerization. Drop a piece of software on the MSX and let it run...

Anyway, what if I want to have a little play with this myself? Could this be done with a Rookiedrive cartridge as well?

بواسطة Grauw

Ascended (10061)

صورة Grauw

31-08-2021, 12:17

Very cool stuff. I think there is a lot of potential for improving development and testing workflows with real machines.

بواسطة Pencioner

Scribe (1460)

صورة Pencioner

31-08-2021, 16:15

Briqunullus wrote:

Anyway, what if I want to have a little play with this myself? Could this be done with a Rookiedrive cartridge as well?

RD will be supported. Me too waiting for release Smile

بواسطة sdsnatcher73

Prophet (2229)

صورة sdsnatcher73

31-08-2021, 17:13

If this (at some point) could work over network / wifi as well that would be even cooler! I guess it’s just a matter of time…

بواسطة S0urceror

Master (186)

صورة S0urceror

01-09-2021, 17:12

Briqunullus wrote:

File transfer would be great, I'm almost envisioning some sort of containerization. Drop a piece of software on the MSX and let it run...

You can do this now by using the bin2hex program. This translates the binary to an Intel Hex file. Compilers like sjasm or sdcc also can generate them. You can then paste IHX into MSX memory and run it with the Go command.

Grauw wrote:

I think there is a lot of potential for improving development and testing workflows with real machines.

That's why I made it. With the process described above and a smart Makefile you can create the IHX, send it across over serial, run the code. I will try to make a proof of concept to see how this works. If we can also inject breakpoints and hook it to my customised Dezog debugger we can do this all from Visual Code.

Pencioner wrote:

RD will be supported. Me too waiting for release Smile

I uploaded all the code yesterday to my Github in various repositories. I'll pack them up and generate a RookieDrive compatible ROM as well. Btw. I am thinking about changing my IO ports to the same ones as the RD. This way I do not have to create two builds. I will then also update the CPLD code of the MSXUSB cartridge to make it RookieDrive compatible.

بواسطة Pencioner

Scribe (1460)

صورة Pencioner

01-09-2021, 18:41

S0urceror wrote:

I am thinking about changing my IO ports to the same ones as the RD. This way I do not have to create two builds. I will then also update the CPLD code of the MSXUSB cartridge to make it RookieDrive compatible.

Good point, there's really no need for different ports, and the changes wouldn't take much time

UPD: i see in github: "This compiles into a MacOS, Teensy and MSX target." - and there i have a question - does it mean that you can connect to MSX-es - use one with a serial device running serial communication software and connect to one with MSX USB device running terminal ROM ?

بواسطة Briqunullus

Champion (405)

صورة Briqunullus

01-09-2021, 21:30

S0urceror wrote:

You can do this now by using the bin2hex program. This translates the binary to an Intel Hex file. Compilers like sjasm or sdcc also can generate them. You can then paste IHX into MSX memory and run it with the Go command.

Yeah, you are showing this in the demo. This is quite rudimentary though, I was thinking on a larger scale. Where you run a script to configure the MSX just the way you need to.

But I may be carried away a bit too much here. It's just that the concept fascinates me a lot. Remote debugging would be equally awesome. Keep up the good work, and the possibilities will be beyond imagination.

S0urceror wrote:

I uploaded all the code yesterday to my Github in various repositories. I'll pack them up and generate a RookieDrive compatible ROM as well. Btw. I am thinking about changing my IO ports to the same ones as the RD. This way I do not have to create two builds. I will then also update the CPLD code of the MSXUSB cartridge to make it RookieDrive compatible.

I only asked about Rookiedrive because of availability. Or do you have plans to sell your own cartridge?

بواسطة ducasp

Champion (460)

صورة ducasp

02-09-2021, 00:10

S0urceror wrote:

You can already now paste the text of an Intel Hex file in the Monitor. This places the file in memory. Then you can save it to disk.

For a more simpler way of doing things I intend to implement also the ability to (b)load/(b)save from the USB device in BASIC. Like: LOAD “USB:TEST.BAS” or BLOAD “USB:TEST.BIN”,R

Or implement the XModem in the Monitor to upload and save directly to a file.

https://github.com/ducasp/MSX-Development/tree/master/UNAPI/...

Feel free to fork it and create a version for that... XMODEM and (a lot, lot, lot better) Y-Modem and (even better) Y-Modem G is already built-in... Only for file receiving, but shouldn't be quite difficult to adapt it to send files as well, just didn't invest time into it as most BBSs nowadays do not accept file upload anyway. It already is working on VT-MSX mode if MSX1 and ANSI Color w/ IBM PC fonts on MSX 2 and better, and creating a version of https://github.com/ducasp/MSX-Development/blob/master/UNAPI/... for your serial port/driver should be all you need, there is a build definition for AOFossil (BaDCaT) and that version do not require a server address to connect to, perhaps that helps you (if you want, of course). Code is not prime time as far as readability goes (I've took a few shortcuts and occupied extra space of code for the sake of being a tad bit faster), but if it serves you well, you can have the X/Y Modem receiving as easy as 1 - 2 -3 :)

صفحة 2/2
1 |