Firmware Updates
Primarily I have updated the firmwares to include RGB I2C 16x2 LCD screen but there have also been some improvements made to TZXDuino and CASDuino.
Arduitape 1.8 can be downloaded from here.
CASDuino 1.22.1can be downloaded from here.
Changes.
Added RGB I2C 16x2 LCD
Speed improvements
Improved compatibility with TOSEC Dragon CAS files
TZXDuino 1.15.1 can be downloaded from here.
Changes
Added RGB I2C 16x2 LCD
Improved UEF support
Dragon CAS file information.
This is a bit of boring technical information in regards to Dragon CAS files from TOSEC and why they didn't work before.
Unlike MSX CAS files Dragon and CoCo CAS files start with a byte hex value of 55. To be recognised as a CAS file by emulators it only needs to have one byte with hex value of 55 at the beginning. To be recognised as a Dragon/CoCo CAS file by CASDuino it requires a minimum of 8 bytes with a hex value of 55 bytes. To be recognised by a real computer it requires around a second of audio tone that's the equivalent of the tone a byte of 55 makes.
Here are some images of the Hexadecimal values of a correct CAS file.
As you can see the file contains a lot of bytes with a Hex value of 55. This file will work properly on the CASDuino and a real computer.
However the TOSEC archive of Dragon CAS files has been optimised for use with emulators which read a single Hex value of 55 and automatically fills in the missing bytes.
This is what a TOSEC CAS file can look like.
This would be recognised as a Dragon CAS file by the old version of CASDuino but does not load on a real machine.
With the new Dragon Process in the new version, using code from MAXDuino and fixed by myself, the missing bytes are added and the file should load on a real machine. This has fixed many CAS files from the TOSEC archive but there are some that are even more optimised and only have two or three bytes of Hex value 55 at the start and even these are not recognised by CASDuino. These can be fixed by inserting five or six bytes of 55 at the beginning of a file with a Hex Editor but this is only to recommended if you are brave of heart and have a backup of the CAS file.
Hope you find this information not too boring.
Primarily I have updated the firmwares to include RGB I2C 16x2 LCD screen but there have also been some improvements made to TZXDuino and CASDuino.
Arduitape 1.8 can be downloaded from here.
CASDuino 1.22.1can be downloaded from here.
Changes.
Added RGB I2C 16x2 LCD
Speed improvements
Improved compatibility with TOSEC Dragon CAS files
TZXDuino 1.15.1 can be downloaded from here.
Changes
Added RGB I2C 16x2 LCD
Improved UEF support
Dragon CAS file information.
This is a bit of boring technical information in regards to Dragon CAS files from TOSEC and why they didn't work before.
Unlike MSX CAS files Dragon and CoCo CAS files start with a byte hex value of 55. To be recognised as a CAS file by emulators it only needs to have one byte with hex value of 55 at the beginning. To be recognised as a Dragon/CoCo CAS file by CASDuino it requires a minimum of 8 bytes with a hex value of 55 bytes. To be recognised by a real computer it requires around a second of audio tone that's the equivalent of the tone a byte of 55 makes.
Here are some images of the Hexadecimal values of a correct CAS file.
However the TOSEC archive of Dragon CAS files has been optimised for use with emulators which read a single Hex value of 55 and automatically fills in the missing bytes.
This is what a TOSEC CAS file can look like.
This would be recognised as a Dragon CAS file by the old version of CASDuino but does not load on a real machine.
With the new Dragon Process in the new version, using code from MAXDuino and fixed by myself, the missing bytes are added and the file should load on a real machine. This has fixed many CAS files from the TOSEC archive but there are some that are even more optimised and only have two or three bytes of Hex value 55 at the start and even these are not recognised by CASDuino. These can be fixed by inserting five or six bytes of 55 at the beginning of a file with a Hex Editor but this is only to recommended if you are brave of heart and have a backup of the CAS file.
Hope you find this information not too boring.
Hi,
ReplyDeleteI get some errors by updateing the arduitape firmware from 1.7 to 1.8:
In file included from D:\Users\markus\Documents\Arduino\libraries\TMRpcm/TMRpcm.h:17:0,
from D:\Users\markus\Downloads\ArduiTape_v1_8\ArduiTape_v1_8\ArduiTape_v1_8.ino:8:
C:\Program Files (x86)\Arduino\libraries\SD\src/SD.h:63:7: error: 'SdVolume' does not name a type; did you mean 'FatVolume'?
SdVolume volume;
^~~~~~~~
FatVolume
C:\Program Files (x86)\Arduino\libraries\SD\src/SD.h:71:37: error: 'SD_CHIP_SELECT_PIN' was not declared in this scope
boolean begin(uint8_t csPin = SD_CHIP_SELECT_PIN);
^~~~~~~~~~~~~~~~~~
In file included from D:\Users\markus\Downloads\ArduiTape_v1_8\ArduiTape_v1_8\ArduiTape_v1_8.ino:8:0:
D:\Users\markus\Documents\Arduino\libraries\TMRpcm/TMRpcm.h:93:26: error: reference to 'File' is ambiguous
boolean searchMainTags(File xFile, char *datStr);
^~~~
In file included from D:\Users\markus\Documents\Arduino\libraries\SdFat\src/FatLib/FatLib.h:27:0,
from D:\Users\markus\Documents\Arduino\libraries\SdFat\src/SdFat.h:33,
from D:\Users\markus\Downloads\ArduiTape_v1_8\ArduiTape_v1_8\ArduiTape_v1_8.ino:7:
D:\Users\markus\Documents\Arduino\libraries\SdFat\src/FatLib/ArduinoFiles.h:122:7: note: candidates are: class File
class File : public FatFile, public Stream {
^~~~
In file included from D:\Users\markus\Documents\Arduino\libraries\TMRpcm/TMRpcm.h:17:0,
from D:\Users\markus\Downloads\ArduiTape_v1_8\ArduiTape_v1_8\ArduiTape_v1_8.ino:8:
C:\Program Files (x86)\Arduino\libraries\SD\src/SD.h:28:9: note: class SDLib::File
class File : public Stream {
^~~~
In file included from D:\Users\markus\Downloads\ArduiTape_v1_8\ArduiTape_v1_8\ArduiTape_v1_8.ino:8:0:
D:\Users\markus\Documents\Arduino\libraries\TMRpcm/TMRpcm.h:93:26: error: 'File' has not been declared
boolean searchMainTags(File xFile, char *datStr);
^~~~
Additional to the manual installed Lib TMRpcm in Version 1.1.0
Can you help me?
Bye
Markus
Solved ... wrong firmware :-)
ReplyDeleteI'm glad it was an easy fix.
DeleteTbh there is no real need to update from 1.7 to 1.8 as it will do nothing for the majority. Keeping the IDE and libraries up to date always helps though.