MSX USB | MSX Resource Center (Pagina 21/24)

Van foody

Champion (469)

04-07-2021, 00:31

It is done. I will buy it. This is my solution then.

Van issalig

Rookie (22)

28-07-2021, 11:31

Hi, thanks for sharing the project.
I am new to the MSX world and I am working on a minified pcb with plcc sockets and exposed headers for future development (as soon as everything works I will update my fork). Board will be 5 cm high.

I have some doubts about the bill of materials, is the cpld epm7064 or epm7032? SLC44 or LC44?
The memory could it be SST39SF040-70 or SST39SF040-55?

P.S.: I also opened a github issue but I think posting it here can be seen by more people.

Van issalig

Rookie (22)

28-07-2021, 15:04

Souceror answered me on github issue but I post it also here in case other people is having the same question.

The CPLD is a EPM7064 in a PLCC-44 housing. The flash you can use anyone that is compatible to the pins. Basically every flash that conforms to the JEDEC standard you can use. Only in programming the flash you have to use another routine. If you program in a separate programmer then this is not an issue.

Van S0urceror

Master (210)

03-08-2021, 21:43

MSXUSB now turns your MSX into a serial terminal.

Simply connect your MSX via an USB cable to your PC, Mac or Linux machine and a new serial port is detected. Then start Putty, Minicom or Screen and get a connection to the Monitor program.

This Monitor allows you to send Intel Hex dumps of binary data and execute them. A great way to embed your MSX in your modern debugging workflow.

Check out the video on YouTube.

This works also on the RookieDrive with the software from my GitHub.

N.B. if you connect two powered devices you have to take special care, use a data-only USB cable, or check the instructions under the video.

Van issalig

Rookie (22)

02-10-2021, 19:52

Hi, I am still building my own msxusb. All the components finally arrived.
I have a VG8020 (which I guess it should work with MSXUSB, right?)
I have programmed CPLD with file https://github.com/S0urceror/MSX-USB/blob/master/hardware/qu...
Rom is flashed with https://github.com/S0urceror/MSX-USB/blob/master/software/fl...
CH376 jumper is in Parallel position
I am using a USB sd card reader/writer
SD Card is formated to FAT16 with 256Mb and contains NEXTOR.SYS and COMMAND2.COM from https://github.com/S0urceror/MSX-USB/tree/master/software/dist

If I insert the SDCARD the following happens:
+UNAPI initialised
+MSXUSB cartridge found
.
And it is blocked here

Other times, a fast "-No USB device connected\" appears for some ms and then "No enough memory"

Any hint?

Van S0urceror

Master (210)

02-10-2021, 20:39

Well, the PCB, Flash and CH376s seem to work otherwise you would not have gotten this far. But I see it does not successfully finish the device discovery.

The driver supports USB storage bulk only devices with the SCSI command set. Can you check with the lsusb command on Mac, Linux or with my MSX version what it reports for class and subclass id?

Btw this is the most common storage device class used by flash drives, external harddisks and cdroms. Check with a simple USB stick first.

Van issalig

Rookie (22)

02-10-2021, 21:13

lsusb says this
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only

Here is the full description
Bus 003 Device 012: ID 090c:6200 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) microSD card reader
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x090c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.)
idProduct 0x6200 microSD card reader
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 255
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 255

Van issalig

Rookie (22)

03-10-2021, 11:06

I have changed USB device (following advices from S0urceror) and now it looks it is closer to work

But cannot call usbfiles to check the files.

I will keep on working on it.

Van issalig

Rookie (22)

14-10-2021, 19:16

I tried with FILES and also did not work.
Also tried with a FAT12 and 16MB that is the one that Nextor supports for MSX1 <=64kb with no effect.
I suspect it must be something related to Nextor and MSX1 with 64kb but I am totally lost regarding Nextor.

Does anyone have a hint?

Van S0urceror

Master (210)

17-10-2021, 20:07

issalig wrote:

Does anyone have a hint?

Issalig, I am sorry you cannot get it working. It looks like MSXUSB does recognise the device you tried last. Then it jumps into Basic without going to Nextor/DOS. That is weird.

If your USB flash device is formatted as FAT12 with MSXDOS.SYS and COMMAND.COM on it then it should work. Don't know if you also have to hold 1 during boot to force Nextor in DOS1 mode. I think that is automatic.

I have been a bit too busy with my other MSX project. Desiging a replacement PCB for a HB-F1XD. After that I'll investigate further and let you know if I find the issue.