- WRERR was putting the CAN character in register C to send. However, it needs to be in register A. Fixed here. Credit and thanks to HubertH for finding this and providing the fix.
- Post-processing of disk-hosted ROMs such as FZ80 and ZRC has been modified to handle custom user configurations.
- Standardized all distribution ROM names to end in _std.
- ROM Applications document has been consolidated into the Applications document
- Martin has done a significant overhaul of the Applications document
Co-Authored-By: MartinR <174514335+martinr-uk@users.noreply.github.com>
- Will Sowerbutts provided an updated flash4 v1.3.9
- Modified HBIOS to be more proactive about disabling interrupts on systems with interrupts disabled to avoid issues with applications that turn them on.
- Updated NABU default configuration to run under interrupt mode 2.
Co-Authored-By: Will Sowerbutts <will@sowerbutts.com>
Based on input from Martin R, the console takeover mechanism has been modified to require that the space bar be pressed twice in a row on the character unit desiring to be the console. This reduces the chance of a spurious console takeover due to garbage input on serial ports.
- If enabled by AUTOCON config setting, you can press <space> at any character device to take over the console at the boot loader prompt.
- Correction to SIOSEEK documentation in System Guide. Thanks and credit to Martin R.
- Credit and thanks to Martin R for providing a substantial list of suggested fixes and improvements to the User Guide. I have done my best to address them -- others will require more time and will hopefully be addressed in the future.
Driver Device Type ID's have been stored in the upper nibble. However, running out of ID's, I have changed them to occupy the entire byte.
This is a breaking change, so I have updated the minor version number to maintain integrity between components. So, v3.3 will never become a stable release and I am moving directly to v3.4.
- The build process was enhanced by Dean Jenkins to support the Raspberry Pi. Note that the Propeller firmware will not be generated by a RPi build. See Issue #358.
- Initial support for USB storage via CH375/6.