Thomson TO8 minimal file selector (WIP)

[gilles]

use at your own risk (at least save your HXCSDFE.CFG file...)

FAT32 support has some limitations (no library used). FAT is not used, so only one cluster for root directory is supported.
Subdirectories not yet supported.

Tested with 1.6.x and 1.7.x firmwares Rev C and a TO8D.

comments and bug reports are welcome

[update]
www.alternative-system.com/files/AUTOBOOT.HFE
www.alternative-system.com/files/HXCSDFE.CFG

[Jeff]

use at your own risk (at least save your HXCSDFE.CFG file...)

FAT32 support has some limitations (no library used). FAT is not used, so only one cluster for root directory is supported.
Subdirectories not yet supported.

Tested with 1.6.x and 1.7.x firmwares Rev C and a TO8D.

comments and bug reports are welcome

[update]
www.alternative-system.com/files/AUTOBOOT.HFE
www.alternative-system.com/files/HXCSDFE.CFG

Nice !

[gilles]

I also tested the image with a flashed Gotek on a TO8D.

It works OK (with HFE images) but I have questions:
_ will the old 8kb config file format be supported in all next versions of HxC firmwares? (I see that an 8kb config file is still in the Amstrad fileselector dir).
_ is it normal that the "main" firmware version found in the zip archive is old from May 2018 where newer versions can be found in "previous" directory?

[Jeff]

I also tested the image with a flashed Gotek on a TO8D.

It works OK (with HFE images) but I have questions:
_ will the old 8kb config file format be supported in all next versions of HxC firmwares? (I see that an 8kb config file is still in the Amstrad fileselector dir).

yes it should.

_ is it normal that the "main" firmware version found in the zip archive is old from May 2018 where newer versions can be found in "previous" directory?

This is because i release most firmwares in the WIP folder. The "main" firmware is just the last one completely tested. The full validation process take some hours so when i release a firmware not completely tested, i push it into the WIP folder. This is necessary to have a faster development cycle and to be able to provide a "certified"/"stable" firmware when needed.

Btw about gotek there is this service now :
https://hxc2001.com/custom_fw/
you can tweak the direct access interface

[gilles]

tweaking direct access will be a last chance option.
It could be interesting in the config file but a custom firmware should be avoided if possible, otherwise nobody will be able to use the fileselector.
The new version also supports TO9.

[Jeff]

tweaking direct access will be a last chance option.
It could be interesting in the config file but a custom firmware should be avoided if possible, otherwise nobody will be able to use the fileselector.
The new version also supports TO9.

Why " otherwise nobody will be able to use the fileselector." ?
I don't understand.

[gilles]

if for one plateform I need to generate a custom firmware, I will also have to keep this firmware somewhere with the fileselector (or instructions to generate a custom firmware with corrects parameters). If not, users will just test the program and think it does not work. It's OK for distributors that will flash the gotek and (re)sell the whole but It's better to stick to official firmware if possible.

Anyway for thomson the default is OK, it was not easy for TO8/TO9+ but it works now.

en video (low res) pour le TO9
https://youtu.be/LkO4w1q59xk

[Jeff]

FYI the Direct access protocol has some new functions :

Code: Select all

03 February 2019 : Firmware STM32 USB HxCFloppyEmulator v3.1.36.1a ( -> In the "Next_WIP_Alpha_Firmware_And_Tools" Folder !)

	- Direct access mode : New functions
		- Select mode (0x5) :
			Mode 0 - Flash sector access mode (Default)
			Mode 1 - Plain text browser, Entries format : "IIII;T;SSSSSSSS;File name\r\n"
			IIII = Object ID (ASCII HEX Number).
			T = Type -> 'F'=FILE, 'D'=DIRECTORY
			SSSSSSSS = File Size  (ASCII HEX Number).
			Mode 2 - Slot list mode.
		- Change Objects list ID base (0x6) (Plain text browser).
		- Select/Enter Object (0x7) (Plain text browser - Image/Directory selection or File tranfert mode).
		- Set file base offset (0x8) (File transfer mode).
		- Get current selected image (0x9).
		- Select file with path (0xA) (Select image with a plain text file path).

		- MFM & FM support. (see the customization page : https://hxc2001.com/custom_fw/)

		With these new direct access API functions small file selector/browser/swapper/loader can be developed without
		the need of any FAT32 library on resource-limited machines.
		The protocol specification document will be updated soon at this address :
		https://hxc2001.com/download/floppy_drive_emulator/SDCard_HxC_Floppy_Emulator_Direct_Access_mode.pdf

https://hxc2001.com/download/floppy_dri ... rmware.zip

https://hxc2001.com/download/floppy_dri ... _notes.txt

[gilles]

Ok this is the kind of function that will help a lot.
A check (is an image good) may also help.
Will this also be implemented in PIC firmwares at some point?