Cannot read FAT CF partition in Windows

201 views
Skip to first unread message

Zoltan Fekete

unread,
Aug 5, 2024, 2:39:38 PM8/5/24
to RC2014-Z80
Thank you for accepting me in the Group.

I have worked a lot with Z80 and CP/M 2.2 in the mid/late 1980s, but not recently. My old CP/M machine died long time ago and anyway the size and outlook of it confined it to the garage for the rest of its life, so I built an SC-126 Z180 based SBC from the Small Computer Central, along with CF-card interface.
I am running RomWBW 3.4.0 with it:
RomWBW HBIOS v3.4.0, 2023-12-31

Small Computer SC126 [SCZ180_sc126] Z8S180-N @ 18.432MHz IO=0xC0
0 MEM W/S, 2 I/O W/S, INT MODE 2, Z180 MMU
512KB ROM, 512KB RAM
ROM VERIFY: 00 00 00 00 PASS

AY: MODE=RCZ180 IO=0x68 NOT PRESENT
ASCI0: IO=0xC0 ASCI W/BRG MODE=115200,8,N,1
ASCI1: IO=0xC1 ASCI W/BRG MODE=115200,8,N,1
DSRTC: MODE=STD IO=0x0C Sat 2000-01-01 01:06:48 CHARGE=OFF
MD: UNITS=2 ROMDISK=384KB RAMDISK=352KB
FD: MODE=RCWDC IO=0x50 NOT PRESENT
IDE: IO=0x10 MODE=RC
IDE0: ATA 8-BIT LBA BLOCKS=0x007A7E40 SIZE=3919MB
IDE1: NO MEDIA
PPIDE: IO=0x20 PPI NOT PRESENT
SD: MODE=SC OPR=0x0C CNTR=0xCA TRDR=0xCB DEVICES=1
SD0: NO MEDIA
CH0: IO=0x3E NOT PRESENT
CH1: IO=0x3C NOT PRESENT
FP: IO=0x00 NOT PRESENT

Unit        Device      Type              Capacity/Mode
----------  ----------  ----------------  --------------------
Char 0      ASCI0:      RS-232            115200,8,N,1
Char 1      ASCI1:      RS-232            115200,8,N,1
Disk 0      MD0:        RAM Disk          352KB,LBA
Disk 1      MD1:        ROM Disk          384KB,LBA
Disk 2      IDE0:       CompactFlash      3919MB,LBA
Disk 3      IDE1:       Hard Disk         --
Disk 4      SD0:        SD Card           --


I tried to set up the 4G CF card to have CP/M slices and have another partition with FAT to be able to move tools, sources, etc from my Windows machine.
It failed, when I initialised the FAT partition then it destroyed the CP/M slices. I discovered on Github, that the FAT.COM included with 3.4.0 was not the right version, so I downloaded the one from 3.4.1.
Using that the result is better, but I still cannot read the content of the CF card in Windows. It shows up as an empty drive.

The partition table as follows: First and 512M partition for CP/Mm slices and then after a 1Mb gap a 384 Mb partition for FAT:
FDISK80 for RomWBW, UNA, Mini-M68k, KISS-68030, SBC-188  ----
       Version 1.1-23 created 3-June-2023
                 (Running under RomWBW HBIOS)

HBIOS unit number [0..4]: 2
Capacity of disk 2:  (  4G)  8027712      Geom 7a7e1010
Nr  ---Type- A --      Start         End   LBA start  LBA count  Size
 1    RomWBW   2e      8:0:1  1023:15:16        2048    1048576  512M
 2     FAT16   06   1023:0:1  1023:15:16     1052672     786432  384M
 3             00       *** empty ***
 4             00       *** empty ***


The FAT.COM should be the right version 0.9.9:
CP/M FAT Utility v0.9.9 (beta), 12-AOct-2023 [RomWBW HBIOS]
Copyright (C) 2019-23, Wayne Warthen, GNU GPL v3


Formatted it as I understood from the manual:
C>fat format 2:

About to format FAT Filesystem on Disk Unit #2.
All existing FAT partition data will be destroyed!!!


Continue (y/n)?

Formatting... Done


Windows disk manager shows also that I have a primary partition of 512MB and a healthy primary partition of FAT type and of 384MB.
However if I write a file on this CF card in Windows, that is invisible on CP/M, and vice-versa...

I found it strange, that I created some directories on the FAT file system with FAT MD command, which shows up. Copied one or two files in there.
Then, when in desperation I tried again from scratch, partitioning the CF card, but this time leaving a 2 Mb gap between the RomWBW partition and the FAT partition, formatted the FAT partition again, but:
- after the format, i could see my old directories and files created --> that should be impossible, because the partition was moved up by one MB!!!
- but the FAT DEL command could delete those files/directories.

So it looks if FAT FORMAT acts somewhere on the CF card, but FAT DIR, FAT DEL, FAT COPY acts somewhere else..

Can someone help me what am I doing wrong?

Thanks a lot,
Zoltan



Wayne Warthen

unread,
Aug 5, 2024, 3:06:23 PM8/5/24
to RC2014-Z80
Hi Zoltan,

It seems like what you are doing is generally correct.

When you formatted the FAT partition (prior to moving the partition), you say that it shows up as an empty drive.  That would be correct since there would not be anything in it at that point.

I can't explain what is happening after you moved the FAT partition.  Can you please post a copy of the new partition table?  Is it possible that you made the partition changes, but did not use the 'W' command in FDISK80 to write the changes?

I could be of more help if you post a complete session log.  I suggest you start over and write the hd1k_combo.img image to the disk using Windows.  Then put that disk in yout SC126 and do the FORMAT.  Then do a DIR.  The try doing a file copy.  Post your session log hered and I should be able to tell what is going wrong.

Below is a session log that I just created following the steps I suggest.  This what "should" happen.

Thanks,

Wayne

RomWBW HBIOS v3.4.0, 2024-04-20


Small Computer SC126 [SCZ180_sc126] Z8S180-N @ 18.432MHz IO=0xC0
0 MEM W/S, 2 I/O W/S, INT MODE 2, Z180 MMU
512KB ROM, 512KB RAM
ROM VERIFY: 00 00 00 00 PASS

AY: MODE=RCZ180 IO=0x68 NOT PRESENT
ASCI0: IO=0xC0 ASCI W/BRG MODE=115200,8,N,1
ASCI1: IO=0xC1 ASCI W/BRG MODE=115200,8,N,1
DSRTC: MODE=STD IO=0x0C Fri 2001-04-27 22:10:47 CHARGE=OFF

MD: UNITS=2 ROMDISK=384KB RAMDISK=352KB
FD: MODE=RCWDC IO=0x50 NOT PRESENT
IDE: IO=0x10 MODE=RC
IDE0: NO MEDIA

IDE1: NO MEDIA
PPIDE: IO=0x20 PPI NOT PRESENT
SD: MODE=SC OPR=0x0C CNTR=0xCA TRDR=0xCB DEVICES=1
SD0: SDHC NAME=SE32G BLOCKS=0x03B72400 SIZE=30436MB

CH0: IO=0x3E NOT PRESENT
CH1: IO=0x3C NOT PRESENT
FP: IO=0x00 NOT PRESENT

Unit        Device      Type              Capacity/Mode
----------  ----------  ----------------  --------------------
Char 0      ASCI0:      RS-232            115200,8,N,1
Char 1      ASCI1:      RS-232            115200,8,N,1
Disk 0      MD0:        RAM Disk          352KB,LBA
Disk 1      MD1:        ROM Disk          384KB,LBA
Disk 2      IDE0:       Hard Disk         --

Disk 3      IDE1:       Hard Disk         --
Disk 4      SD0:        SD Card           30436MB,LBA


Small Computer SC126 [SCZ180_sc126] Boot Loader

Boot [H=Help]: 4.1

Booting Disk Unit 4, Slice 1, Sector 0x00004800...

Volume "Unlabeled" [0xD000-0xFE00, entry @ 0xE600]...

CBIOS v3.4.0 [WBW]

Configuring Drives...

        A:=SD0:1
        B:=MD0:0
        C:=MD1:0
        D:=SD0:0
        E:=SD0:2
        F:=SD0:3
        G:=SD0:4
        H:=SD0:5
        I:=SD0:6
        J:=SD0:7

        1455 Disk Buffer Bytes Free

ZSDOS v1.1, 54.0K TPA

A>fat format 4:

About to format FAT Filesystem on Disk Unit #4.

All existing FAT partition data will be destroyed!!!

Continue (y/n)?

Formatting... Done

A>fat dir 4:

Directory of 4:


A>fat copy asm.com 4:

Copying...

ASM.COM ==> 4:/ASM.COM ... [OK]

    1 File(s) Copied

A>fat dir 4:

Directory of 4:

04/27/2001  22:11:20          8192  ---A  ASM.COM

A>

Zoltan Fekete

unread,
Aug 5, 2024, 4:18:33 PM8/5/24
to RC2014-Z80
Hi Wayne,

I appreciate your prompt response :)
So, copied a combo image to the CF card:
F:\>dir
 Volume in drive F has no label.
 Volume Serial Number is 2821-0DB6

 Directory of F:\

20/04/2024  20:39        51,380,224 hd1k_zrc_combo.img
               1 File(s)     51,380,224 bytes
               0 Dir(s)     350,986,240 bytes free



Then I move the card to the SC126, and reset it, and here is the session log:
The partition table is what it should be, so it seems, that I wrote it back to the disk
Here is the session log:

RomWBW HBIOS v3.4.0, 2023-12-31

Small Computer SC126 [SCZ180_sc126] Z8S180-N @ 18.432MHz IO=0xC0
0 MEM W/S, 2 I/O W/S, INT MODE 2, Z180 MMU
512KB ROM, 512KB RAM
ROM VERIFY: 00 00 00 00 PASS

AY: MODE=RCZ180 IO=0x68 NOT PRESENT
ASCI0: IO=0xC0 ASCI W/BRG MODE=115200,8,N,1
ASCI1: IO=0xC1 ASCI W/BRG MODE=115200,8,N,1
DSRTC: MODE=STD IO=0x0C Sat 2000-01-01 00:00:02 CHARGE=OFF

MD: UNITS=2 ROMDISK=384KB RAMDISK=352KB
FD: MODE=RCWDC IO=0x50 NOT PRESENT
IDE: IO=0x10 MODE=RC
IDE0: ATA 8-BIT LBA BLOCKS=0x007A7E40 SIZE=3919MB
IDE1: NO MEDIA
PPIDE: IO=0x20 PPI NOT PRESENT
SD: MODE=SC OPR=0x0C CNTR=0xCA TRDR=0xCB DEVICES=1
SD0: NO MEDIA
CH0: IO=0x3E NOT PRESENT
CH1: IO=0x3C NOT PRESENT
FP: IO=0x00 NOT PRESENT

Unit        Device      Type              Capacity/Mode
----------  ----------  ----------------  --------------------
Char 0      ASCI0:      RS-232            115200,8,N,1
Char 1      ASCI1:      RS-232            115200,8,N,1
Disk 0      MD0:        RAM Disk          352KB,LBA
Disk 1      MD1:        ROM Disk          384KB,LBA
Disk 2      IDE0:       CompactFlash      3919MB,LBA
Disk 3      IDE1:       Hard Disk         --
Disk 4      SD0:        SD Card           --


Small Computer SC126 [SCZ180_sc126] Boot Loader

Boot [H=Help]: c

Loading CP/M 2.2...

CBIOS v3.4.0 [WBW]

Formatting RAMDISK...

Configuring Drives...

        A:=MD0:0
        B:=MD1:0
        C:=IDE0:0
        D:=IDE0:1
        E:=IDE0:2
        F:=IDE0:3
        G:=IDE0:4
        H:=IDE0:5
        I:=IDE0:6
        J:=IDE0:7


        1455 Disk Buffer Bytes Free

CP/M-80 v2.2, 54.0K TPA

B>fdisk80



FDISK80 for RomWBW, UNA, Mini-M68k, KISS-68030, SBC-188  ----
       Version 1.1-23 created 3-June-2023
                 (Running under RomWBW HBIOS)

HBIOS unit number [0..4]: 2
Capacity of disk 2:  (  4G)  8027712      Geom 7a7e1010
Nr  ---Type- A --      Start         End   LBA start  LBA count  Size
 1    RomWBW   2e      8:0:1  1023:15:16        2048    1048576  512M
 2     FAT16   06   1023:0:1  1023:15:16     1060864     786432  384M

 3             00       *** empty ***
 4             00       *** empty ***
>>q
FDISK exit.


B>c:fat


CP/M FAT Utility v0.9.9 (beta), 12-AOct-2023 [RomWBW HBIOS]
Copyright (C) 2019-23, Wayne Warthen, GNU GPL v3

Usage: FAT <cmd> <parms>
  FAT DIR <path>
  FAT COPY <src> <dst>
  FAT REN <from> <to>
  FAT DEL <path>[<file>|<dir>]
  FAT MD <path>
  FAT FORMAT <drv>

CP/M filespec: <d>:FILENAME.EXT (<d> is CP/M drive letter A-P)
FAT filespec:  <u>:/DIR/FILENAME.EXT (<u> is disk unit #)

B>c:fat format 2:


About to format FAT Filesystem on Disk Unit #2.
All existing FAT partition data will be destroyed!!!

Continue (y/n)?

Formatting... Done

B>c:fat dir 2:

Directory of 2:

01/01/2000  00:23:42    <dir>       ----  SYSFILES

B>c:fat dir 2:/sysfiles/

Directory of 2:/SYSFILES


B>dir c:
C: FAT      COM
B>dir e:
NO FILE
B>fiifdir d:
D: ASM      COM : ASSIGN   COM : CLRDIR   COM : COMPARE  COM
D: COPY     COM : CPM      SYS : CPUSPD   COM : DDT      COM
D: DDTZ     COM : DUMP     COM : ED       COM : FAT      COM
D: FDISK80  COM : FDU      COM : FILEATTR COM : FILEDATE COM
D: FLASH    COM : FORMAT   COM : INITDIR  COM : LDDS     COM
D: LDP2D    COM : LOAD     COM : MBASIC   COM : MODE     COM
D: NULU     COM : PIP      COM : PUTDS    COM : RELOG    COM
D: RTC      COM : STAT     COM : SUBMIT   COM : SUPERSUB COM
D: SURVEY   COM : SYSCOPY  COM : SYSGEN   COM : TALK     COM
D: TD       COM : TIMER    COM : UNARC    COM : XM       COM
D: XSUB     COM : ZAP      COM : ZCAL     COM : ZDE      COM
D: ZPATH    COM : ZSCONFIG COM : ZSYS     SYS : ZXD      COM
B>dir j:
J: ASM      COM : ASSIGN   COM : CLRDIR   COM : COMPARE  COM
J: COPY     COM : CPM      SYS : CPUSPD   COM : DDT      COM
J: DDTZ     COM : DUMP     COM : ED       COM : FAT      COM
J: FDISK80  COM : FDU      COM : FILEATTR COM : FILEDATE COM
J: FLASH    COM : FORMAT   COM : INITDIR  COM : LDDS     COM
J: LDP2D    COM : LOAD     COM : MBASIC   COM : MODE     COM
J: NULU     COM : PIP      COM : PUTDS    COM : RELOG    COM
J: RTC      COM : STAT     COM : SUBMIT   COM : SUPERSUB COM
J: SURVEY   COM : SYSCOPY  COM : SYSGEN   COM : TALK     COM
J: TD       COM : TIMER    COM : UNARC    COM : XM       COM
J: XSUB     COM : ZAP      COM : ZCAL     COM : ZDE      COM
J: ZPATH    COM : ZSCONFIG COM : ZSYS     SYS : ZXD      COM
B>c:fat copy b:*.* 2:/

Copying...

B:ASM.COM ==> 2:/ASM.COM ... [OK]
B:CLRDIR.COM ==> 2:/CLRDIR.COM ... [OK]
B:COMPARE.COM ==> 2:/COMPARE.COM ... [OK]
B:COPY.COM ==> 2:/COPY.COM ... [OK]
B:DDT.COM ==> 2:/DDT.COM ... [OK]
B:DDTZ.COM ==> 2:/DDTZ.COM ... [OK]
B:DUMP.COM ==> 2:/DUMP.COM ... [OK]
B:ED.COM ==> 2:/ED.COM ... [OK]
B:FAT.COM ==> 2:/FAT.COM ... [OK]
B:FDISK80.COM ==> 2:/FDISK80.COM ... [OK]
B:FILEATTR.COM ==> 2:/FILEATTR.COM ... [OK]
B:FILEDATE.COM ==> 2:/FILEDATE.COM ... [OK]
B:FLASH.COM ==> 2:/FLASH.COM ... [OK]
B:INITDIR.COM ==> 2:/INITDIR.COM ... [OK]
B:LDDS.COM ==> 2:/LDDS.COM ... [OK]
B:LDP2D.COM ==> 2:/LDP2D.COM ... [OK]
B:LOAD.COM ==> 2:/LOAD.COM ... [OK]
B:MBASIC.COM ==> 2:/MBASIC.COM ... [OK]
B:NULU.COM ==> 2:/NULU.COM ... [OK]
B:PIP.COM ==> 2:/PIP.COM ... [OK]
B:PUTDS.COM ==> 2:/PUTDS.COM ... [OK]
B:RELOG.COM ==> 2:/RELOG.COM ... [OK]
B:STAT.COM ==> 2:/STAT.COM ... [OK]
B:SUBMIT.COM ==> 2:/SUBMIT.COM ... [OK]
B:SUPERSUB.COM ==> 2:/SUPERSUB.COM ... [OK]
B:TD.COM ==> 2:/TD.COM ... [OK]
B:UNARC.COM ==> 2:/UNARC.COM ... [OK]
B:XSUB.COM ==> 2:/XSUB.COM ... [OK]
B:ZAP.COM ==> 2:/ZAP.COM ... [OK]
B:ZCAL.COM ==> 2:/ZCAL.COM ... [OK]
B:ZDE.COM ==> 2:/ZDE.COM ... [OK]
B:ZPATH.COM ==> 2:/ZPATH.COM ... [OK]
B:ZSCONFIG.COM ==> 2:/ZSCONFIG.COM ... [OK]
B:ZXD.COM ==> 2:/ZXD.COM ... [OK]
B:ASSIGN.COM ==> 2:/ASSIGN.COM ... [OK]
B:MODE.COM ==> 2:/MODE.COM ... [OK]
B:RTC.COM ==> 2:/RTC.COM ... [OK]
B:SYSCOPY.COM ==> 2:/SYSCOPY.COM ... [OK]
B:XM.COM ==> 2:/XM.COM ... [OK]
B:FDU.COM ==> 2:/FDU.COM ... [OK]
B:FORMAT.COM ==> 2:/FORMAT.COM ... [OK]
B:SURVEY.COM ==> 2:/SURVEY.COM ... [OK]
B:SYSGEN.COM ==> 2:/SYSGEN.COM ... [OK]
B:TALK.COM ==> 2:/TALK.COM ... [OK]
B:TIMER.COM ==> 2:/TIMER.COM ... [OK]
B:CPUSPD.COM ==> 2:/CPUSPD.COM ... [OK]
B:CPM.SYS ==> 2:/CPM.SYS ... [OK]
B:ZSYS.SYS ==> 2:/ZSYS.SYS ... [OK]

    48 File(s) Copied

B>c:fat dir 2:

Directory of 2:

01/01/2000  00:04:16          8192  ---A  ASM.COM
01/01/2000  00:04:16          1792  ---A  CLRDIR.COM
01/01/2000  00:04:16          2560  ---A  COMPARE.COM
01/01/2000  00:04:16          6912  ---A  COPY.COM
01/01/2000  00:04:16          4864  ---A  DDT.COM
01/01/2000  00:04:18          7424  ---A  DDTZ.COM
01/01/2000  00:04:18           512  ---A  DUMP.COM
01/01/2000  00:04:18          6656  ---A  ED.COM
01/01/2000  00:04:18         43008  ---A  FAT.COM
01/01/2000  00:04:18         17024  ---A  FDISK80.COM
01/01/2000  00:04:18          4096  ---A  FILEATTR.COM
01/01/2000  00:04:20          4352  ---A  FILEDATE.COM
01/01/2000  00:04:20         13440  ---A  FLASH.COM
01/01/2000  00:04:20          2048  ---A  INITDIR.COM
01/01/2000  00:04:20          3328  ---A  LDDS.COM
01/01/2000  00:04:20          3456  ---A  LDP2D.COM
01/01/2000  00:04:20          1792  ---A  LOAD.COM
01/01/2000  00:04:20         24320  ---A  MBASIC.COM
01/01/2000  00:04:22         15616  ---A  NULU.COM
01/01/2000  00:04:22          7424  ---A  PIP.COM
01/01/2000  00:04:22         13056  ---A  PUTDS.COM
01/01/2000  00:04:22           256  ---A  RELOG.COM
01/01/2000  00:04:22          5248  ---A  STAT.COM
01/01/2000  00:04:22          1280  ---A  SUBMIT.COM
01/01/2000  00:04:22          2176  ---A  SUPERSUB.COM
01/01/2000  00:04:22          2048  ---A  TD.COM
01/01/2000  00:04:22          7808  ---A  UNARC.COM
01/01/2000  00:04:24           768  ---A  XSUB.COM
01/01/2000  00:04:24          9856  ---A  ZAP.COM
01/01/2000  00:04:24          1280  ---A  ZCAL.COM
01/01/2000  00:04:24         18560  ---A  ZDE.COM
01/01/2000  00:04:24          2176  ---A  ZPATH.COM
01/01/2000  00:04:24          5888  ---A  ZSCONFIG.COM
01/01/2000  00:04:24          6784  ---A  ZXD.COM
01/01/2000  00:04:24          3712  ---A  ASSIGN.COM
01/01/2000  00:04:24          2176  ---A  MODE.COM
01/01/2000  00:04:26          2944  ---A  RTC.COM
01/01/2000  00:04:26          2048  ---A  SYSCOPY.COM
01/01/2000  00:04:26          6784  ---A  XM.COM
01/01/2000  00:04:26          9856  ---A  FDU.COM
01/01/2000  00:04:26           640  ---A  FORMAT.COM
01/01/2000  00:04:26          1408  ---A  SURVEY.COM
01/01/2000  00:04:26          1152  ---A  SYSGEN.COM
01/01/2000  00:04:26           640  ---A  TALK.COM
01/01/2000  00:04:26          1024  ---A  TIMER.COM
01/01/2000  00:04:26          1664  ---A  CPUSPD.COM
01/01/2000  00:04:26         13824  ---A  CPM.SYS
01/01/2000  00:04:28         13824  ---A  ZSYS.SYS
01/01/2000  00:23:42    <dir>       ----  SYSFILES

B>fdisk80



FDISK80 for RomWBW, UNA, Mini-M68k, KISS-68030, SBC-188  ----
       Version 1.1-23 created 3-June-2023
                 (Running under RomWBW HBIOS)

HBIOS unit number [0..4]: 2
Capacity of disk 2:  (  4G)  8027712      Geom 7a7e1010
Nr  ---Type- A --      Start         End   LBA start  LBA count  Size
 1    RomWBW   2e      8:0:1  1023:15:16        2048    1048576  512M
 2     FAT16   06   1023:0:1  1023:15:16     1060864     786432  384M

 3             00       *** empty ***
 4             00       *** empty ***
>>q
FDISK exit.


B>

At this point, I moved the CF card back to the Windows system and image file is gone. Please note that voluem serial number has changed
f:\>dir
 Volume in drive F has no label.
 Volume Serial Number is 2821-0047

 Directory of f:\

File Not Found

f:\>


Windows disk manager shows, what is expected (see attached screenshot).

Now I am really curious.

I appreciate your help.

kind regards,
Zoltan
Diskmanager.PNG

Wayne Warthen

unread,
Aug 5, 2024, 4:43:58 PM8/5/24
to rc201...@googlegroups.com
Thank you for the complete session information -- very helpful.  Well the good news is that I see the problem.  The bad news is the issue is at the beginning of the process.

The disk image file (hd1k_combo.img) is a raw image file.  It must be written to your SD Card using a raw block transfer starting at the very beginning of the card using an appropriate tool.  It cannot be written to the SD Card with Windows File Explorer.

The RomWBW distribution includes the required tool to do this (for Windows).  It is called Win32DiskImager and is found in the Tools\Win32DiskImager directory of the distribution archive.

Insert the SD Card in your Windows machine, then start the tool.  Select the drive letter of your SD Card device and enter the filename of the disk image file.  It should look something like this:

image.png

Then click "Write".  There will be a confirmation dialog like this:

image.png

Click Yes and it should proceed to write the image to the SD Card.  When done you
should get a confirmation message like this:

image.png

At this point, you can move the SD Card to your SC126, boot, and proceed with the FAT FORMAT, etc.

Thanks,

Wayne


--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rc2014-z80/be516131-c927-4577-be48-debc182c2589n%40googlegroups.com.

Zoltan Fekete

unread,
Aug 5, 2024, 5:28:43 PM8/5/24
to rc201...@googlegroups.com
Thanks again,

Well, I did not get it first, that you actually wanted me to burn a disk image to the CF card and boot from it.
I did it.
I used Rufus, that is the tool I use for similar purposes and it was successful.
As you can see from the log below, I could boot from the CF image. I could format the FAT partition. I created a directory, copied files over to that directory and I could successfully list the files. Actually mounting that card on Windows, I could get the directory and files I copied from CP/M.
So, it is a success so far.
Does it tell me, that I would need to install the latest FW image onto the system (or keep booting from the CF card).
I do have spare flash chips, but I do not have a dedicated programmer. With some work I could build one, but there must be an easier way. Do you have a more or less safe process to do it, given that the SC126 has two flash sockets, though they are jumper selectable.
As far as i am concerned, I need to RomWBW flash in place to be able to start up the system.
Once the system is booted up from CF card, I could run the flash updater. Can I update in place? Or can I swap the jumper over to the other socket? I assume no, as you use bank switching heavily. What is your suggested process?

Please see the session log:

Restarting System...


RomWBW HBIOS v3.4.0, 2023-12-31

Small Computer SC126 [SCZ180_sc126] Z8S180-N @ 18.432MHz IO=0xC0
0 MEM W/S, 2 I/O W/S, INT MODE 2, Z180 MMU
512KB ROM, 512KB RAM
ROM VERIFY: 00 00 00 00 PASS

AY: MODE=RCZ180 IO=0x68 NOT PRESENT
ASCI0: IO=0xC0 ASCI W/BRG MODE=115200,8,N,1
ASCI1: IO=0xC1 ASCI W/BRG MODE=115200,8,N,1
DSRTC: MODE=STD IO=0x0C Sat 2000-01-01 00:01:00 CHARGE=OFF

MD: UNITS=2 ROMDISK=384KB RAMDISK=352KB
FD: MODE=RCWDC IO=0x50 NOT PRESENT
IDE: IO=0x10 MODE=RC
IDE0: ATA 8-BIT LBA BLOCKS=0x007A7E40 SIZE=3919MB
IDE1: NO MEDIA
PPIDE: IO=0x20 PPI NOT PRESENT
SD: MODE=SC OPR=0x0C CNTR=0xCA TRDR=0xCB DEVICES=1
SD0: NO MEDIA
CH0: IO=0x3E NOT PRESENT
CH1: IO=0x3C NOT PRESENT
FP: IO=0x00 NOT PRESENT

Unit        Device      Type              Capacity/Mode
----------  ----------  ----------------  --------------------
Char 0      ASCI0:      RS-232            115200,8,N,1
Char 1      ASCI1:      RS-232            115200,8,N,1
Disk 0      MD0:        RAM Disk          352KB,LBA
Disk 1      MD1:        ROM Disk          384KB,LBA
Disk 2      IDE0:       CompactFlash      3919MB,LBA
Disk 3      IDE1:       Hard Disk         --
Disk 4      SD0:        SD Card           --


Small Computer SC126 [SCZ180_sc126] Boot Loader

Boot [H=Help]: d


Unit        Device      Type              Capacity/Mode
----------  ----------  ----------------  --------------------
Char 0      ASCI0:      RS-232            115200,8,N,1
Char 1      ASCI1:      RS-232            115200,8,N,1
Disk 0      MD0:        RAM Disk          352KB,LBA
Disk 1      MD1:        ROM Disk          384KB,LBA
Disk 2      IDE0:       CompactFlash      3919MB,LBA
Disk 3      IDE1:       Hard Disk         --
Disk 4      SD0:        SD Card           --


Boot [H=Help]: h

  L           - List ROM Applications
  D           - Device Inventory
  R           - Reboot System
  I <u> [<c>] - Set Console Interface/Baud code
  V [<n>]     - View/Set HBIOS Diagnostic Verbosity
  <u>[.<s>]   - Boot Disk Unit/Slice

Boot [H=Help]: 2

Booting Disk Unit 2, Slice 0, Sector 0x00000800...


Volume "Unlabeled" [0xD000-0xFE00, entry @ 0xE600]...

CBIOS v3.4.0 [WBW]

Formatting RAMDISK...

Configuring Drives...

        A:=IDE0:0

        B:=MD0:0
        C:=MD1:0
        D:=IDE0:1
        E:=IDE0:2
        F:=IDE0:3
        G:=IDE0:4
        H:=IDE0:5
        I:=IDE0:6
        J:=IDE0:7

        1455 Disk Buffer Bytes Free

CP/M-80 v2.2, 54.0K TPA

A>dir
A: ASM      COM : DDT      COM : DUMP     COM : ED       COM
A: HELP     COM : HELP     HLP : LIB      COM : LINK     COM
A: LOAD     COM : MAC      COM : PIP      COM : RMAC     COM
A: STAT     COM : SUBMIT   COM : XSUB     COM : ZSID     COM
A: README   TXT : ASSIGN   COM : CPUSPD   COM : FAT      COM
A: FDU      COM : FDU      DOC : FORMAT   COM : MODE     COM
A: RTC      COM : SURVEY   COM : SYSCOPY  COM : SYSGEN   COM
A: TALK     COM : HTALK    COM : TBASIC   COM : TIMER    COM
A: TUNE     COM : XM       COM : ZMP      COM : ZMP      HLP
A: ZMP      DOC : ZMXFER   OVR : ZMTERM   OVR : ZMINIT   OVR
A: ZMCONFIG OVR : ZMD      COM : VGMPLAY  COM : CPM      SYS
A: CLRDIR   COM : COMPARE  COM : CRUNCH   COM : CRUNCH28 CFG
A: DDTZ     COM : DDTZ     DOC : EX       COM : FDISK80  COM
A: FIND     COM : FLASH    COM : FLASH    DOC : MBASIC   COM
A: NULU     COM : PMARC    COM : PMEXT    COM : RMXSUB1  COM
A: SUPERSUB COM : SUPERSUB DOC : TDLBASIC COM : UNARC    COM
A: UNARC    DOC : UNCR     COM : UNZIP    COM : UNZIP    DOC
A: WDATE    COM : XSUB1    COM : ZAP      COM : ZDE      COM
A: ZDE      DOC : ZDENST   COM : ZMRX     COM : ZMTX     COM
A: KERCPM22 COM : BBCBASIC COM : BBCBASIC TXT : BBCDIST  MAC
A: BBCDIST  SUB : GENHEX   COM : LS       COM : LSWEEP   COM
A>fat


CP/M FAT Utility v0.9.9 (beta), 12-AOct-2023 [RomWBW HBIOS]
Copyright (C) 2019-23, Wayne Warthen, GNU GPL v3

Usage: FAT <cmd> <parms>
  FAT DIR <path>
  FAT COPY <src> <dst>
  FAT REN <from> <to>
  FAT DEL <path>[<file>|<dir>]
  FAT MD <path>
  FAT FORMAT <drv>

CP/M filespec: <d>:FILENAME.EXT (<d> is CP/M drive letter A-P)
FAT filespec:  <u>:/DIR/FILENAME.EXT (<u> is disk unit #)

A>
A>
A>dir c:
C: ASM      COM : CLRDIR   COM : COMPARE  COM : COPY     COM
C: DDT      COM : DDTZ     COM : DUMP     COM : ED       COM
C: FAT      COM : FDISK80  COM : FILEATTR COM : FILEDATE COM
C: FLASH    COM : INITDIR  COM : LDDS     COM : LDP2D    COM
C: LOAD     COM : MBASIC   COM : NULU     COM : PIP      COM
C: PUTDS    COM : RELOG    COM : STAT     COM : SUBMIT   COM
C: SUPERSUB COM : TD       COM : UNARC    COM : XSUB     COM
C: ZAP      COM : ZCAL     COM : ZDE      COM : ZPATH    COM
C: ZSCONFIG COM : ZXD      COM : ASSIGN   COM : MODE     COM
C: RTC      COM : SYSCOPY  COM : XM       COM : FDU      COM
C: FORMAT   COM : SURVEY   COM : SYSGEN   COM : TALK     COM
C: TIMER    COM : CPUSPD   COM : CPM      SYS : ZSYS     SYS
A>fat


CP/M FAT Utility v0.9.9 (beta), 12-AOct-2023 [RomWBW HBIOS]
Copyright (C) 2019-23, Wayne Warthen, GNU GPL v3

Usage: FAT <cmd> <parms>
  FAT DIR <path>
  FAT COPY <src> <dst>
  FAT REN <from> <to>
  FAT DEL <path>[<file>|<dir>]
  FAT MD <path>
  FAT FORMAT <drv>

CP/M filespec: <d>:FILENAME.EXT (<d> is CP/M drive letter A-P)
FAT filespec:  <u>:/DIR/FILENAME.EXT (<u> is disk unit #)

A>fat format 2;;:


About to format FAT Filesystem on Disk Unit #2.
All existing FAT partition data will be destroyed!!!

Continue (y/n)?

Formatting... Done

A>fat dir 2:

Directory of 2:


A>fdiaask80



FDISK80 for RomWBW, UNA, Mini-M68k, KISS-68030, SBC-188  ----
       Version 1.1-23 created 3-June-2023
                 (Running under RomWBW HBIOS)

HBIOS unit number [0..4]: 2
Capacity of disk 2:  (  4G)  8027712      Geom 7a7e1010
Nr  ---Type- A --      Start         End   LBA start  LBA count  Size
 1    RomWBW   2e      8:0:1  1023:15:16        2048    1048576  512M
 2     FAT16   06   1023:0:1  1023:15:16     1050624     786432  384M

 3             00       *** empty ***
 4             00       *** empty ***
>>q
FDISK exit.


A>fat dir 2:

Directory of 2:


A>fat md 2:\sysfiles


A>fat dir 2:

Directory of 2:

01/01/2000  00:08:36    <dir>       ----  SYSFILES

A>fat copy a:*.* 2:/sysfiles/

Copying...

A:ASM.COM ==> 2:/SYSFILES/ASM.COM ... [OK]
A:DDT.COM ==> 2:/SYSFILES/DDT.COM ... [OK]
A:DUMP.COM ==> 2:/SYSFILES/DUMP.COM ... [OK]
A:ED.COM ==> 2:/SYSFILES/ED.COM ... [OK]
A:HELP.COM ==> 2:/SYSFILES/HELP.COM ... [OK]
A:HELP.HLP ==> 2:/SYSFILES/HELP.HLP ... [OK]
A:LIB.COM ==> 2:/SYSFILES/LIB.COM ... [OK]
A:LINK.COM ==> 2:/SYSFILES/LINK.COM ... [OK]
A:LOAD.COM ==> 2:/SYSFILES/LOAD.COM ... [OK]
A:MAC.COM ==> 2:/SYSFILES/MAC.COM ... [OK]
A:PIP.COM ==> 2:/SYSFILES/PIP.COM ... [OK]
A:RMAC.COM ==> 2:/SYSFILES/RMAC.COM ... [OK]
A:STAT.COM ==> 2:/SYSFILES/STAT.COM ... [OK]
A:SUBMIT.COM ==> 2:/SYSFILES/SUBMIT.COM ... [OK]
A:XSUB.COM ==> 2:/SYSFILES/XSUB.COM ... [OK]
A:ZSID.COM ==> 2:/SYSFILES/ZSID.COM ... [OK]
A:README.TXT ==> 2:/SYSFILES/README.TXT ... [OK]
A:ASSIGN.COM ==> 2:/SYSFILES/ASSIGN.COM ... [OK]
A:CPUSPD.COM ==> 2:/SYSFILES/CPUSPD.COM ... [OK]
A:FAT.COM ==> 2:/SYSFILES/FAT.COM ... [OK]
A:FDU.COM ==> 2:/SYSFILES/FDU.COM ... [OK]
A:FDU.DOC ==> 2:/SYSFILES/FDU.DOC ... [OK]
A:FORMAT.COM ==> 2:/SYSFILES/FORMAT.COM ... [OK]
A:MODE.COM ==> 2:/SYSFILES/MODE.COM ... [OK]
A:RTC.COM ==> 2:/SYSFILES/RTC.COM ... [OK]
A:SURVEY.COM ==> 2:/SYSFILES/SURVEY.COM ... [OK]
A:SYSCOPY.COM ==> 2:/SYSFILES/SYSCOPY.COM ... [OK]
A:SYSGEN.COM ==> 2:/SYSFILES/SYSGEN.COM ... [OK]
A:TALK.COM ==> 2:/SYSFILES/TALK.COM ... [OK]
A:HTALK.COM ==> 2:/SYSFILES/HTALK.COM ... [OK]
A:TBASIC.COM ==> 2:/SYSFILES/TBASIC.COM ... [OK]
A:TIMER.COM ==> 2:/SYSFILES/TIMER.COM ... [OK]
A:TUNE.COM ==> 2:/SYSFILES/TUNE.COM ... [OK]
A:XM.COM ==> 2:/SYSFILES/XM.COM ... [OK]
A:ZMP.COM ==> 2:/SYSFILES/ZMP.COM ... [OK]
A:ZMP.HLP ==> 2:/SYSFILES/ZMP.HLP ... [OK]
A:ZMP.DOC ==> 2:/SYSFILES/ZMP.DOC ... [OK]
A:ZMXFER.OVR ==> 2:/SYSFILES/ZMXFER.OVR ... [OK]
A:ZMTERM.OVR ==> 2:/SYSFILES/ZMTERM.OVR ... [OK]
A:ZMINIT.OVR ==> 2:/SYSFILES/ZMINIT.OVR ... [OK]
A:ZMCONFIG.OVR ==> 2:/SYSFILES/ZMCONFIG.OVR ... [OK]
A:ZMD.COM ==> 2:/SYSFILES/ZMD.COM ... [OK]
A:VGMPLAY.COM ==> 2:/SYSFILES/VGMPLAY.COM ... [OK]
A:CPM.SYS ==> 2:/SYSFILES/CPM.SYS ... [OK]
A:CLRDIR.COM ==> 2:/SYSFILES/CLRDIR.COM ... [OK]
A:COMPARE.COM ==> 2:/SYSFILES/COMPARE.COM ... [OK]
A:CRUNCH.COM ==> 2:/SYSFILES/CRUNCH.COM ... [OK]
A:CRUNCH28.CFG ==> 2:/SYSFILES/CRUNCH28.CFG ... [OK]
A:DDTZ.COM ==> 2:/SYSFILES/DDTZ.COM ... [OK]
A:DDTZ.DOC ==> 2:/SYSFILES/DDTZ.DOC ... [OK]
A:EX.COM ==> 2:/SYSFILES/EX.COM ... [OK]
A:FDISK80.COM ==> 2:/SYSFILES/FDISK80.COM ... [OK]
A:FIND.COM ==> 2:/SYSFILES/FIND.COM ... [OK]
A:FLASH.COM ==> 2:/SYSFILES/FLASH.COM ... [OK]
A:FLASH.DOC ==> 2:/SYSFILES/FLASH.DOC ... [OK]
A:MBASIC.COM ==> 2:/SYSFILES/MBASIC.COM ... [OK]
A:NULU.COM ==> 2:/SYSFILES/NULU.COM ... [OK]
A:PMARC.COM ==> 2:/SYSFILES/PMARC.COM ... [OK]
A:PMEXT.COM ==> 2:/SYSFILES/PMEXT.COM ... [OK]
A:RMXSUB1.COM ==> 2:/SYSFILES/RMXSUB1.COM ... [OK]
A:SUPERSUB.COM ==> 2:/SYSFILES/SUPERSUB.COM ... [OK]
A:SUPERSUB.DOC ==> 2:/SYSFILES/SUPERSUB.DOC ... [OK]
A:TDLBASIC.COM ==> 2:/SYSFILES/TDLBASIC.COM ... [OK]
A:UNARC.COM ==> 2:/SYSFILES/UNARC.COM ... [OK]
A:UNARC.DOC ==> 2:/SYSFILES/UNARC.DOC ... [OK]
A:UNCR.COM ==> 2:/SYSFILES/UNCR.COM ... [OK]
A:UNZIP.COM ==> 2:/SYSFILES/UNZIP.COM ... [OK]
A:UNZIP.DOC ==> 2:/SYSFILES/UNZIP.DOC ... [OK]
A:WDATE.COM ==> 2:/SYSFILES/WDATE.COM ... [OK]
A:XSUB1.COM ==> 2:/SYSFILES/XSUB1.COM ... [OK]
A:ZAP.COM ==> 2:/SYSFILES/ZAP.COM ... [OK]
A:ZDE.COM ==> 2:/SYSFILES/ZDE.COM ... [OK]
A:ZDE.DOC ==> 2:/SYSFILES/ZDE.DOC ... [OK]
A:ZDENST.COM ==> 2:/SYSFILES/ZDENST.COM ... [OK]
A:ZMRX.COM ==> 2:/SYSFILES/ZMRX.COM ... [OK]
A:ZMTX.COM ==> 2:/SYSFILES/ZMTX.COM ... [OK]
A:KERCPM22.COM ==> 2:/SYSFILES/KERCPM22.COM ... [OK]
A:BBCBASIC.COM ==> 2:/SYSFILES/BBCBASIC.COM ... [OK]
A:BBCBASIC.TXT ==> 2:/SYSFILES/BBCBASIC.TXT ... [OK]
A:BBCDIST.MAC ==> 2:/SYSFILES/BBCDIST.MAC ... [OK]
A:BBCDIST.SUB ==> 2:/SYSFILES/BBCDIST.SUB ... [OK]
A:GENHEX.COM ==> 2:/SYSFILES/GENHEX.COM ... [OK]
A:LS.COM ==> 2:/SYSFILES/LS.COM ... [OK]
A:LSWEEP.COM ==> 2:/SYSFILES/LSWEEP.COM ... [OK]

    84 File(s) Copied

A>fat dir 2:/sysfiles/

Directory of 2:/SYSFILES

01/01/2000  00:09:28          8192  ---A  ASM.COM
01/01/2000  00:09:28          4864  ---A  DDT.COM
01/01/2000  00:09:28           512  ---A  DUMP.COM
01/01/2000  00:09:28          6656  ---A  ED.COM
01/01/2000  00:09:28          7168  ---A  HELP.COM
01/01/2000  00:09:28         23552  ---A  HELP.HLP
01/01/2000  00:09:28          7168  ---A  LIB.COM
01/01/2000  00:09:30         15744  ---A  LINK.COM
01/01/2000  00:09:30          1792  ---A  LOAD.COM
01/01/2000  00:09:30         11776  ---A  MAC.COM
01/01/2000  00:09:30          7424  ---A  PIP.COM
01/01/2000  00:09:30         13568  ---A  RMAC.COM
01/01/2000  00:09:30          5248  ---A  STAT.COM
01/01/2000  00:09:30          1280  ---A  SUBMIT.COM
01/01/2000  00:09:30           768  ---A  XSUB.COM
01/01/2000  00:09:32         10240  ---A  ZSID.COM
01/01/2000  00:09:32          7808  ---A  README.TXT
01/01/2000  00:09:32          3712  ---A  ASSIGN.COM
01/01/2000  00:09:32          1664  ---A  CPUSPD.COM
01/01/2000  00:09:32         42880  ---A  FAT.COM
01/01/2000  00:09:32          9856  ---A  FDU.COM
01/01/2000  00:09:34         19072  ---A  FDU.DOC
01/01/2000  00:09:34           640  ---A  FORMAT.COM
01/01/2000  00:09:34          2176  ---A  MODE.COM
01/01/2000  00:09:34          2944  ---A  RTC.COM
01/01/2000  00:09:34          1408  ---A  SURVEY.COM
01/01/2000  00:09:34          2048  ---A  SYSCOPY.COM
01/01/2000  00:09:34          1152  ---A  SYSGEN.COM
01/01/2000  00:09:34           640  ---A  TALK.COM
01/01/2000  00:09:34          1152  ---A  HTALK.COM
01/01/2000  00:09:34          2816  ---A  TBASIC.COM
01/01/2000  00:09:34          1024  ---A  TIMER.COM
01/01/2000  00:09:36          4736  ---A  TUNE.COM
01/01/2000  00:09:36          6784  ---A  XM.COM
01/01/2000  00:09:36         16000  ---A  ZMP.COM
01/01/2000  00:09:36           512  ---A  ZMP.HLP
01/01/2000  00:09:36         21120  ---A  ZMP.DOC
01/01/2000  00:09:36         19072  ---A  ZMXFER.OVR
01/01/2000  00:09:38         16256  ---A  ZMTERM.OVR
01/01/2000  00:09:38          5120  ---A  ZMINIT.OVR
01/01/2000  00:09:38         12288  ---A  ZMCONFIG.OVR
01/01/2000  00:09:38         20864  ---A  ZMD.COM
01/01/2000  00:09:38          3072  ---A  VGMPLAY.COM
01/01/2000  00:09:40         13824  ---A  CPM.SYS
01/01/2000  00:09:40          1792  ---A  CLRDIR.COM
01/01/2000  00:09:40          2560  ---A  COMPARE.COM
01/01/2000  00:09:40          6144  ---A  CRUNCH.COM
01/01/2000  00:09:40          5248  ---A  CRUNCH28.CFG
01/01/2000  00:09:40          7424  ---A  DDTZ.COM
01/01/2000  00:09:42         29952  ---A  DDTZ.DOC
01/01/2000  00:09:42          5632  ---A  EX.COM
01/01/2000  00:09:42         17024  ---A  FDISK80.COM
01/01/2000  00:09:42         10368  ---A  FIND.COM
01/01/2000  00:09:42         13440  ---A  FLASH.COM
01/01/2000  00:09:42          8064  ---A  FLASH.DOC
01/01/2000  00:09:44         24320  ---A  MBASIC.COM
01/01/2000  00:09:44         15616  ---A  NULU.COM
01/01/2000  00:09:44         10368  ---A  PMARC.COM
01/01/2000  00:09:44         12928  ---A  PMEXT.COM
01/01/2000  00:09:44           128  ---A  RMXSUB1.COM
01/01/2000  00:09:46          2176  ---A  SUPERSUB.COM
01/01/2000  00:09:46          4992  ---A  SUPERSUB.DOC
01/01/2000  00:09:46         14848  ---A  TDLBASIC.COM
01/01/2000  00:09:46          7808  ---A  UNARC.COM
01/01/2000  00:09:46         23424  ---A  UNARC.DOC
01/01/2000  00:09:48          8576  ---A  UNCR.COM
01/01/2000  00:09:48          8704  ---A  UNZIP.COM
01/01/2000  00:09:48          3584  ---A  UNZIP.DOC
01/01/2000  00:09:48          2816  ---A  WDATE.COM
01/01/2000  00:09:48          1024  ---A  XSUB1.COM
01/01/2000  00:09:48          9856  ---A  ZAP.COM
01/01/2000  00:09:50         18560  ---A  ZDE.COM
01/01/2000  00:09:50         47872  ---A  ZDE.DOC
01/01/2000  00:09:50         10624  ---A  ZDENST.COM
01/01/2000  00:09:52         31488  ---A  ZMRX.COM
01/01/2000  00:09:52         24832  ---A  ZMTX.COM
01/01/2000  00:09:52         29696  ---A  KERCPM22.COM
01/01/2000  00:09:54         14848  ---A  BBCBASIC.COM
01/01/2000  00:09:54         15360  ---A  BBCBASIC.TXT
01/01/2000  00:09:54          5376  ---A  BBCDIST.MAC
01/01/2000  00:09:54           256  ---A  BBCDIST.SUB
01/01/2000  00:09:54           768  ---A  GENHEX.COM
01/01/2000  00:09:54          1280  ---A  LS.COM
01/01/2000  00:09:56         16000  ---A  LSWEEP.COM

A>^C

Kind regards,
Zoltan


Wayne Warthen

unread,
Aug 5, 2024, 6:36:44 PM8/5/24
to RC2014-Z80
Hi Zoltan,

On Monday, August 5, 2024 at 2:28:43 PM UTC-7 Zoltan Fekete wrote:
Well, I did not get it first, that you actually wanted me to burn a disk image to the CF card and boot from it.
I did it.
I used Rufus, that is the tool I use for similar purposes and it was successful.
As you can see from the log below, I could boot from the CF image. I could format the FAT partition. I created a directory, copied files over to that directory and I could successfully list the files. Actually mounting that card on Windows, I could get the directory and files I copied from CP/M.
So, it is a success so far.

Yes, the session log below looks fine.

Does it tell me, that I would need to install the latest FW image onto the system (or keep booting from the CF card).

Not sure I understand your question.  You are running the current firmware and the current CF Card image.  You can boot an OS from ROM or from disk.  Either way is fine.  Once you have a working disk (as you do), I recommend booting from disk.  It is helpful to have the additional files on A: drive that are provided by a disk boot.  There is no specific reason to update your firmware at this point unless you want to test the Development Snapshots.
 
I do have spare flash chips, but I do not have a dedicated programmer. With some work I could build one, but there must be an easier way. Do you have a more or less safe process to do it, given that the SC126 has two flash sockets, though they are jumper selectable.
As far as i am concerned, I need to RomWBW flash in place to be able to start up the system.
Once the system is booted up from CF card, I could run the flash updater. Can I update in place? Or can I swap the jumper over to the other socket? I assume no, as you use bank switching heavily. What is your suggested process?

There is a tool to update the ROM in-situ.  It is called FLASH.COM and is included on the CP/M disk drive.  It will reprogram the ROM using a file on disk.  You can get the new firmware file to your disk by using the FAT filesystem.  Copy the new firmware file to the FAT filesystem on your Windows PC.  Move it to the SC126.  Then use FAT COPY to copy the ROM image to a CP/M drive.  Then use FLASH to reprogram the ROM.

Yes, you do need a working ROM to boot the system, so reprogramming the ROM in-situ has some risk.  If something goes wrong, your system could be unbootable.  Some people have used the dual ROM sockets of the SC126 to avoid this.  After RomWBW boots, it is running from RAM.  So, you can "switch" the ROMs while the SC126 is running.  This allows you to boot on one ROM, then switch to the other ROM before running FLASH.  This allows you to reprogram the alternate ROM and not jeopardize the working boot ROM.

Switching ROMs on a running system is not officially supported, so YMMV.  This is a somewhat advanced technique, so proceed carefully if you decide to try it.

I would also recommend reviewing Chapter 7 Upgrading of the RomWBW User Guide.  It covers upgrading and provides more detail.

Thanks, Wayne

MartinR

unread,
Aug 6, 2024, 10:36:39 AM8/6/24
to RC2014-Z80
Hi Zoltan -

I'm sorry that I can't help with your CF issue, but you do have the best person available to help you.

I have an SC126, booting from uSD rather than CF, but I can confirm that I routinely use the FLASH.COM utility to update a flash chip, and not necessarily the one which I booted the system from. For example, I always keep the latest 'stable' release of RomWBW in one flash chip and then frequently update the second flash chip with the dev versions of RomWBW. I have never had a problem with corrupting a flash chip. Switching chip and write-protect 'on the fly' seems to work fine. I've never had a problem.

Note that I always ensure that the chips are physically write-protected, and only un-protect the one I intend to write to just for the duration of the write. I do this so often that I have now replaced the SC126 jumper block with little toggle switches (such as the one the SC126 uses for power). 

Good luck - 


MartinR

Zoltan Fekete

unread,
Aug 6, 2024, 1:47:22 PM8/6/24
to rc201...@googlegroups.com
  Hi Wayne,

Thanks again for spending time with educating the FNGs :)

Does it tell me, that I would need to install the latest FW image onto the system (or keep booting from the CF card).
Not sure I understand your question.  You are running the current firmware and the current CF Card image.  You can boot an OS from ROM or from disk.  Either way is fine.  Once you have a working disk (as you do), I recommend booting from disk.  It is helpful to have the additional files on A: drive that are provided by a disk boot.  There is no specific reason to update your firmware at this point unless you want to test the Development Snapshots.
You are right: booting from the CF card gives me much more space for programs, etc. I am not arguing that.
However, I do not understand while setting up using my burned in FW v3.4.0 failed. According to the change log the only difference between 3.4.0 and 3.4.1 is the updated FAT.COM, which I took from the repo and Xmodem-ed to the RAM disk. It would be nice to understand the reason, nothing else.

Regarding upgrading the FW in place, I might give it a try. I replace my SCM ROM with an blank Flash and once the system booted, I switch over to it. then try to run FLASH.COM. Sounds like a good experience in case I am forced to do it for one reason or another. :)

I was happy to see Kermit and Wordstar in the combo image - nice memories from the time I was a student.

My next project will be to add an FDC (strong candidate is the RC-2014 WDC-37C65 based one) - I have a NOS 8" half-height Shugart drive, can't wait to hear the noise of seek and head up and down, when assembling something especially with list file and x-ref generation.
I am also thinking of building a flash programmer on an SC724 breakout board (with 3xaddress latches, data and control signals directly on the bus with some buffers if I have too much time). I was thinking to modifying the FLASH.COM to support it or writing something from scratch.

If there is anything useful, potential value comes out of those, I will share in the group.

Cheers,
Zoltan



--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

Wayne Warthen

unread,
Aug 6, 2024, 2:00:16 PM8/6/24
to RC2014-Z80
Hi Zoltan,

On Tuesday, August 6, 2024 at 10:47:22 AM UTC-7 Zoltan Fekete wrote:
Does it tell me, that I would need to install the latest FW image onto the system (or keep booting from the CF card).
Not sure I understand your question.  You are running the current firmware and the current CF Card image.  You can boot an OS from ROM or from disk.  Either way is fine.  Once you have a working disk (as you do), I recommend booting from disk.  It is helpful to have the additional files on A: drive that are provided by a disk boot.  There is no specific reason to update your firmware at this point unless you want to test the Development Snapshots.
You are right: booting from the CF card gives me much more space for programs, etc. I am not arguing that.
However, I do not understand while setting up using my burned in FW v3.4.0 failed. According to the change log the only difference between 3.4.0 and 3.4.1 is the updated FAT.COM, which I took from the repo and Xmodem-ed to the RAM disk. It would be nice to understand the reason, nothing else.

Ah, I see what you are saying.  Yes, since you are running 3.4.0, you could update your ROM to 3.4.1 so that the FAT.COM on the ROM disk is the corrected version.  Since the FAT.COM on the hard disk image was always correct, you could just make sure to run the hard disk version.

Regarding upgrading the FW in place, I might give it a try. I replace my SCM ROM with an blank Flash and once the system booted, I switch over to it. then try to run FLASH.COM. Sounds like a good experience in case I am forced to do it for one reason or another. :)

Yes, as long as you are careful, there is minimal chance of corrupting your working boot ROM.  This would be a good way to upgrade to 3.4.1.  Alternatively, if you get XModem or KERMIT working, you could just transfer the disk image to a hard disk drive and run FLASH on that.

I was happy to see Kermit and Wordstar in the combo image - nice memories from the time I was a student.

I also have fond memories of both.  Back in the day, I wrote one of the original version of Kermit for Windows.  It still runs on Windows 11. 😀

My next project will be to add an FDC (strong candidate is the RC-2014 WDC-37C65 based one) - I have a NOS 8" half-height Shugart drive, can't wait to hear the noise of seek and head up and down, when assembling something especially with list file and x-ref generation.
I am also thinking of building a flash programmer on an SC724 breakout board (with 3xaddress latches, data and control signals directly on the bus with some buffers if I have too much time). I was thinking to modifying the FLASH.COM to support it or writing something from scratch.

If there is anything useful, potential value comes out of those, I will share in the group.

Sounds great.  Be aware that FLASH.COM is a product of Will Sowerbutts.  He maintains this project at the flash4 GitHub Page.  I recommend coordinating any changes to that tool with him.

Thanks, Wayne

Zoltan Fekete

unread,
Aug 8, 2024, 5:56:53 AM8/8/24
to rc201...@googlegroups.com
Hi MartinR,

Thanks for confirming that writing firmware in the spare socket on the SC126 actually works. I have not tried it yet, but will do.
You mentioned SD-card. 
Can you guide me on that please: I am aware that the SC126 has SD/SPI ports. Are you using some commercially available SD card adapter. I guess some sort of level shifter is at least required, most SD cards are using 3.3V logic, while the SC126 has 5V (HCT) logic.

Thanks, 
Zoltan

--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.

MartinR

unread,
Aug 8, 2024, 6:42:50 AM8/8/24
to RC2014-Z80
Hi Zoltan -

Yes - definitely - swapping ROMs on the SC126 'on the fly' works reliably for me and I've done it regularly for the last 18+ months in order to do upgrades of RomWBW.

I use a 6-pin plug-in micro-SD module plugged directly into P2 on the SC126. The socket is labelled 'SPI SD Card'. When I bought my SC126 kit from SCC I added the optional adaptor as I knew I would need it. No level-separate shifters are required - the module does everything necessary, and no configuration of it was necessary. RomWBW recognises it as SD0: at boot, and once I'd loaded it with one of the disk images supplied with RomWBW it works as expected. I'm currently using it with a 64GByte Kingston uSD card that I had spare, and have lots of CP/M slices as well as a large FAT partition in order to exchange files with my Windows11 PC.

Steve Cousins lists these modules as an SC303 under 'Accessories' in his online stores, and they are low cost at 2GBP. See: https://small-computers-direct.square.site/product/sc303-micro-sd-card-adapter/6?cp=true&sa=false&sbp=false&q=false&category_id=5L72I4SJE6JBRTC3D3C6OEPA You can readily find similar modules on eBay, Amazon etc, again for very small cost - but I've not used one myself as I've been using the one Steve supplied for 18+ months without issue. 

I hope this helps. I've been using my SC126 with a micro-SD and RomWBW for a while and have found it it to be very stable and reliable.

All the best -


MartinR

Zoltan Fekete

unread,
Aug 8, 2024, 8:11:12 AM8/8/24
to rc201...@googlegroups.com
Thanks MartinR,
I seem to have overlooked that... No big drama, I have CF card, which is now working - thanks to the help received from Wayne -, but I have ordered a few of those adapters from eBay now.
Kind regards,
Zoltan

MartinR

unread,
Aug 8, 2024, 8:37:26 AM8/8/24
to RC2014-Z80
Hi Zoltan - 

Pleased that it's all coming together for you. Have fun!!

All the best -


MartinR

Reply all
Reply to author
Forward
0 new messages