* * * UPDATE!!! * * *
There is a problem with this new IOS with the MBASIC Basic interpreter. The "GPELED.BAS", "RTC.BAS" and "USERLED.BAS" example programs don't work anymore. It seems that the way MBASIC does some I/O checks using the new virtual serial port interferes with others virtual I/O ports. Further analysis is required...
* * * UPDATE 2 * * *
I think to have found the origin... now thinking to a possible solution...
* * * UPDATE 3 * * *
The new SD image (SD-S220718-R260119-v2.zip) is out in the Files section. It fixes the MBASIC issue for CP/M 3 and 2.2. Please update your SD image.
* * * * * *
Because some people requested to use the XMODEM protocol to exchange files through the serial port, I've added the support for this protocol into CP/M 2.2 and CP/M 3 (banked only).
XMODEM needs a full 8 bit binary data transfer, and this is not possible with the CON port (the CP/M port used for the console) with a "legacy" CP/M system installation because the CP/M Alteration Guide says to strip the eight parity bit when reading a byte from the console input.
More, because the Z80-MBC2 uses a virtual serial port without handshaking there is also a timing problem when dealing with the 128 bytes packets used by the XMODEM protocol.
So the support to the XMODEM protocol has requested changes in the IOS and in the CP/M BIOS, and also in the Arduino core to extend the serial input buffer.
Please note that with the new IOS the default speed of the serial port is now 115200 bps.
To have the XMODEM support active, before the update of the new IOS firmware and the new SD image (see in the Files section), you have to manually create a new "board variant" in the Arduino IDE and then change the default Rx input buffer size to 128 bytes in the "core" of this new variant.
If you aren't interested into the XMODEM support, you can simply update the IOS and the new SD image as usual without the need to create the new board variant. In this case the XMODEM will not work in the receive direction, but only in the send direction (from the Z80-MBC2 to a PC with a terminal emulator).
HOW MANUALLY CREATE A NEW BOARD VARIANT (LINUX)
In the following I'll assume an Arduino IDE 1.8.5 installation on a linux host and the MightyCore ver. 1.0.8. Anyway I've tried to make the procedure enough general to be used for other versions too.
The first thing is find the directory where the MightyCore is located.
If you have installed Arduino IDE 1.8.5 and then installed the MighyCore with the Board Manager with the usual .json "pointer", the MightyCore is located in the "~/.arduino15/packages/MightyCore" directory:
Now you must locate the "~/.arduino15/packages/MightyCore/hardware/avr/1.0.8/cores" directory (note that the "1.0.8" part of the directory name depends on the MightyCore version, and so can be a different number if you have a different version of the MighyCore):
Note 1: note the ".arduino15" name with the dot, you must enable the hidden files view to see it with a the linux GUI.
Note 2: the name of the folder here depends on the MightyCore version, and so can be a different name (as MCUdude_corefiles or whatever it is) if you have a different version of the MighyCore. In any case you must duplicate it and rename it as explained in the following.
In this directory there is an other "MightyCore" (or whatever it is) folder. You must duplicate it and rename it exactly as "MightyCore_Z80MBC2":
Now go into the new copied folder MightyCore_Z80MBC2:
Locate the file "HardwareSerial.h" and open it with an editor:
Go to line 43 (may be a little different number on other versions) and change the value 64 with 128 as shown in the following image:
then save the file.
In the following image there is the same file related to the version 2.0.1 of MightyCore and already edited (see line 53):
Now go back to the "~/.arduino15/packages/MightyCore/hardware/avr/1.0.8" directory:
Locate the file "boards.txt" and open it with an editor. This file is divided in various "sections". Each section is the description of a board variant. In the MightyCore each board variant is a different supported Atmega MCU. In the following image there is the starting of the Atmega32a section. Find it in the file (it starts at about line 440) :
and copy it in a new file "temp.txt" on your desktop folder for further editing:
Now you have to change every occurrence of the string "32." at the beginning of the lines with the string "32Z80MBC2." (mind the dot!). Do not use a "change all" approach, but check every change carefully.
At the end the temp.txt file should be like this one:
Now change the comment at line 2 as in the following image:
Now change the string "Atmega32" at the right of the variable "32Z80MBC2.name=" at about line 5 with the string "ATmega32 (Z80-MBC2)" as in the following image:
and change the string "MightyCore" (or whatever it is) at the right of the variable "32Z80MBC2.build.core=" at about line 17 with the string "MightyCore_Z80MBC2" as in the following image:
Save the file temp.txt, select all the content and copy it into boards.txt after the Atmega32a section (and before the Atmega16a section):
now save the file boards.txt. All done!
To check if you have done it right, open Arduino IDE. In the "Tools -> Board" menu now you should select the "Atmega32 (Z80-MBC2)" board variant:
Choosing this one the Rx buffer will be 128 bytes large, allowing the XMODEM support. Now you can compile the new IOS and upload it.
Note that the new IOS checks if this extended buffer is active, and in this case will print a status line during the boot phase:
In the drive A: of the CP/M 2.2 and 3 disk set of the new SD image, I've already copied the right XMODEM utility to use:
HOW MANUALLY CREATE A NEW BOARD VARIANT (WINDOWS)
The corresponding directory where MightyCore is installed is: C:\Users\<user_name>\AppData\Local\Arduino15\packages\MightyCore, where <user_name> is your user name under windows.
Given that, follow the guide for linux (is the same procedure).