Prove the ftdi (and the android driver for it) by just using it outside of mcomm to download a big file from a pc to the android device, change it's name, and upload back to the pc, and then compare the files. I don't know if any android terminal emulators support xmodem or zmodem or kermit, nor how to do the equivalent of "cmp" on windows except by installing cygwin and running "cmp" the same as on linux or mac, so you have to fill in some blanks there.
If you can do that and the two copies of the file match, then you have proven both the ftdi cable and the android driver being used on it. Then I'd try using dlplus or laddiealpha instead of mcomm to install a dos and test download a file to the M100. Then you have proven the M100 and your serial cable too. So far it actually sounds like you already proved all the parts just by getting dosses installed and running at all. That already excercises all parts, the M100's ram, the M100's serial port, the home made serial cable, the usb adapter, the usb adapters driver and os on the server. It may be down to simple usage details where you didn't give enough detail. For instance, that message is perfectly normal in Teeny if you didn't type a valid teeny command, which is easy to do. But the message is showing you the syntax and format of a valid teeny command. Under the C must be one of the following single letter commands: LSKQ Under the FFFFFF.XX must be a filename of 1 to 6 characters, followed by one of the few valid extensions like .BA .DO .CO So to download TEST.DO from the tpdd, you have to type exactly: L [space] T E S T . D O [enter] TS-DOS has no such strict command syntax, but any files must must still conform to the same format. ts-dos might possibly display a file that doesn't conform, but probably can't actually download it. I don't know about the other tpdd servers, but dlplus has a verbose option which shows the actual commands and responses on screen as it's being used. That may provide some hint when it hangs. Though I don't think it shows any low level serial line debugging. -- bkw On Jan 2, 2018 11:50 AM, "Jonathan Yuen" <[email protected]> wrote: Hi, Hit send without checking-- the error message from tiny was FFFFFF.XX (six F's) Jonathan [email protected] ________________________________________ Från: M100 [[email protected]] för Jonathan Yuen [ [email protected]] Skickat: den 2 januari 2018 17:41 Till: [email protected] Ämne: [M100] mcomm difficulties Hello, I've been playing with mcomm, but it seems to give some trouble. There are enough hacked together pieces in the chain of devices that I am not sure where to start. I'm running it on a Samsung S4 but the I9502 version (sold only in China) and Lineage OS (Android 7.1.2) I have a USB on the go adapter and an FTDI USB adapter, but the latter was bought on ebay from some place in Asia. When I plug it into my Linux box, lsusb reports this for the adapter: Bus 003 Device 004: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO) The Null modem was made with a soldering iron the the connections are the ones listed in the mcomm documentation. I have tried to bootstrap both tiny and ts-dos into a model 100. Both seem to load OK, but have trouble running. Tiny gives me an error FFFF.XX (C=KLSQ) I have to use the reset button to get out. TS-DOS gives me a menu that seems OK (it reports the files in the M100 or in the virtual disk), but it hangs when I try to download a file. I have 29638 bytes free after a cold boot, 25878 after loading tiny, and 23733 after loading ts-dos. Not sure where to start. I thought if I had either tiny or ts-dos in the m100, I could try things like Laddie Alpha or dlplus, but I'm not sure if the programs are loading OK. I have run 'LOAD *COM:981E* as well to get the BASIC program for making ts-dos or tiny but I'm not sure what the listing should be. Jonathan [email protected]
