Networking for HDOS (update)

222 views
Skip to first unread message

Douglas Miller

unread,
Apr 5, 2023, 8:29:39 AM4/5/23
to SEBHC

I have been making some progress lately on the subject of providing a networking tool for HDOS. The direction I'm going is to make a utility similar to ftp, and provides a command shell from which one can connect to CP/NET servers and transfer files. I'm not sure if anyone on this list is an regular user of ftp, let alone likes it, but the model seems to fit what is needed.

Here is the beginnings of a document for what I'm building: https://github.com/durgadas311/hdos-net/blob/master/doc/HDOS-ftp.pdf

I have working binaries for WIZCFG, and FTP (not all commands implemented yet) here: https://github.com/durgadas311/hdos-net/tree/master/bin

Information on using WIZCFG is in this document: https://github.com/durgadas311/cpnet-z80/blob/master/doc/CPNET-WIZ850io.pdf

Information on setting up a server is here: https://github.com/durgadas311/cpnet-z80/blob/master/doc/CpnetSocketServer.pdf

I've been able to run some basic testing, using WIZnet on the H8xSPI adapter (simulated):

S: sy1:ftp 0
HDOS FTP-Lite version 0.1
Connected to 00
ftp> status
Server 00, Remote A:, Local SY0:
ftp> dir
DDT.COM        NETSTAT.COM    NVRAM.COM      CPNETSTS.COM   MAIL.COM     
NDOS.SPR       COPY.COM       CPNETLDR.COM   SRVSTAT.COM    DSKRESET.COM
LOGOFF.COM     XSUBNET.COM    CCP.SPR        STAT.COM       TR.COM       
ENDLIST.COM    LOGIN.COM      WIZDBG.COM     NETWORK.COM    PIP.COM      
LOCAL.COM      SNIOS.SPR      WIZCFG.COM   
ftp> quit
Disconnected from 00

S:


norberto.collado koyado.com

unread,
Apr 5, 2023, 10:07:23 AM4/5/23
to se...@googlegroups.com

WOW!  Great progress.

 

Norberto

--
You received this message because you are subscribed to the Google Groups "SEBHC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/9cb2947a-1e85-569f-5720-0413bea7706e%40gmail.com.

glenn.f...@gmail.com

unread,
Apr 5, 2023, 5:22:37 PM4/5/23
to se...@googlegroups.com

Great progress!

 

You were thinking about single line commands to send and retrieve files (like VGET and VPUT for the VDIP).  I guess once you have a general ftp capability that could be a next step?

 

 

 

From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Douglas Miller
Sent: Wednesday, April 5, 2023 8:30 AM
To: SEBHC <se...@googlegroups.com>
Subject: [sebhc] Networking for HDOS (update)

 

I have been making some progress lately on the subject of providing a networking tool for HDOS. The direction I'm going is to make a utility similar to ftp, and provides a command shell from which one can connect to CP/NET servers and transfer files. I'm not sure if anyone on this list is an regular user of ftp, let alone likes it, but the model seems to fit what is needed.

--

Douglas Miller

unread,
Apr 5, 2023, 5:28:48 PM4/5/23
to se...@googlegroups.com

The problem with single line commands like VGET/VPUT is that each one needs all the networking code in it, and needs to perform network connect/disconnect every time they run. It just seemed like the ftp model was a better fit, where you connect to the server, run a lot of commands/transfers/etc (i.e. have a "session"), then disconnect. One larger program rather than many (not quite as) large programs. I don't have any conclusive proof that this model is better, though.

Douglas Miller

unread,
Apr 5, 2023, 8:55:40 PM4/5/23
to se...@googlegroups.com

Made a lot of progress this evening. Have all the commands I wanted to include working (at least superficially). Still doing more testing, and need to add some features like trapping Ctrl-C so that I can gracefully disconnect from the server (in case the user is too impatient to type "quit"). I'm still not clear on just what a CTLC routine should do, or how to handle that in C (need to override the default C/80 trap). There are probably a few rough edges, and I may not notice them until someone else hits them.

I'm not sure how many of the H8xSPI WIZnet boards are out there, but here is a way to use that on HDOS now, and hopefully provide an easier way to get files in and out of HDOS. Once the SDCard version is available, perhaps more will be looking to try the network, too.

FYI, CP/NET over WIZnet is already available for Heath CP/M and MMS CP/M 3.

glenn.f...@gmail.com

unread,
Apr 5, 2023, 9:13:40 PM4/5/23
to se...@googlegroups.com

Interesting. I was just looking at handling Ctrl-C interrupt in C/80 for a different reason.  The manual talks about a CtlB() routine, but 1) I haven’t been able to get that to work, and 2) it doesn’t trap Ctrl-C

 

The very first code executed in INIT (the prelude code executed before passing off to main()) sets the control-C handler:

 

$INIT:    LXI          H,exic

                MVI       A,3

                DB          255,33                   ß this is actually SCALL .CTLC

 

Where:

 

exic:       DB          255,7                     ß this is actually SCALL .CLRCO – clear console buffer

                JMP       exit

 

So Ctrl-C simply causes the program to clear the console buffer and exit.

 

It appears that one has to modify CLIBRARY.ASM to insert your own Ctrl-C handler…

 

And great work Doug!  I guess now I’ll have to build that Wiznet board! (I’ve got one somewhere)

 

  • Glenn

Douglas Miller

unread,
Apr 5, 2023, 9:35:06 PM4/5/23
to se...@googlegroups.com

I tried this and it appears to be working. I just override the CTLC setting that C/80 does.

    675 static abort() {
    676         printf("Ctl-C\n");
    677         cclose();
    678         ndown();
    679 #asm
    680         db      255,7   ; SCALL CLRCO
    681 #endasm
    682         exit(1);
    683 }
    684
    685 static setctlc() {
    686         abort;
    687 #asm
    688         mvi     a,3
    689         db      255,33  ; SCALL CTLC
    690 #endasm
    691 }

I call "setctlc()" from main().

Glenn Roberts

unread,
Apr 5, 2023, 9:47:07 PM4/5/23
to se...@googlegroups.com
Looks good. Clever way to put the address of abort() in HL. I guess I thought the compiler would complain…

Sent from my iPad

On Apr 5, 2023, at 9:35 PM, Douglas Miller <durga...@gmail.com> wrote:



Douglas Miller

unread,
Apr 5, 2023, 9:50:01 PM4/5/23
to se...@googlegroups.com

Yeah, it's a real hack but gets the job done. I forget when I first heard of that trick - sometime in the blurry 1980's. I have a bunch of Kaypro code littered with that trick.

Glenn Roberts

unread,
Apr 5, 2023, 9:54:28 PM4/5/23
to se...@googlegroups.com
It’s a documented (in the manual) feature but I never thought to try a routine name… great!

Sent from my iPad

On Apr 5, 2023, at 9:50 PM, Douglas Miller <durga...@gmail.com> wrote:



Douglas Miller

unread,
Apr 7, 2023, 5:15:27 PM4/7/23
to se...@googlegroups.com

Latest updates include an FTPPIP command that is a short-cut for doing a simple file transfer, when you already know the specific source and destination (and have no interest in browsing server directories, etc). Documentation and binaries are updated in the repo: https://github.com/durgadas311/hdos-net

norberto.collado koyado.com

unread,
Apr 7, 2023, 8:34:50 PM4/7/23
to se...@googlegroups.com

Just let me know when to jump start the WiZnet board again to test out HDOS.

 

Thank you for enabling such feature to share files from a common pool. Can we still boot HDOS in a diskless system as I do with CP/M3?

 

Norberto

 

From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Douglas Miller

Sent: Friday, April 7, 2023 2:15 PM
To: se...@googlegroups.com

Douglas Miller

unread,
Apr 7, 2023, 8:45:03 PM4/7/23
to se...@googlegroups.com

Booting HDOS over the network is going to take more work. That would require that HDOS actually support networking, which it does not. I'm not sure what it takes to make an HDOS image for booting over the network, even if it does not support networking (diskless). CP/M tends to be "standalone" and so the network boot just drops the image into memory and goes. I think HDOS depends more on the conditions of the system prior to boot, like depending on residuals from the ROM.

I've been testing on my simulator, so it would be good to have someone try it on real hardware, just to be sure.

norberto.collado koyado.com

unread,
Apr 7, 2023, 9:08:27 PM4/7/23
to se...@googlegroups.com

OK! I will get my board back online. I will need to review on how to enable it as it has been a while. Once I get CP/M3 working again, then I can switch to HDOS testing.

 

As I was using my old iMac with Java to copy/read files from it and it is in storage now, what I need, to do the same with Windows 10?

 

Thanks,

Douglas Miller

unread,
Apr 7, 2023, 9:30:51 PM4/7/23
to se...@googlegroups.com

For windows you'll want to add the "cpnetserver_nosys" property to the config file. Starting the server should be mostly the same, especially if you have the config file and CpnetSocketServer.jar in the same directory. "java -jar CpnetSocketServer.jar conf=<config-file>". I can also setup my "public" server for you access. I'm guessing your WIZnet board's nvram still has it's setup saved, so probably nothing extra to do there.

Do you have your old config file? If not, we can construct a new one.

norberto.collado koyado.com

unread,
Apr 7, 2023, 11:49:55 PM4/7/23
to se...@googlegroups.com

The WiZnet board has the last known used configuration.

norberto.collado koyado.com

unread,
Apr 8, 2023, 12:29:51 AM4/8/23
to se...@googlegroups.com

I installed board and was able to download the last known configuration. Let me work in getting Windows 10 working first as the storage server for WiZnet.

 

norberto.collado koyado.com

unread,
Apr 8, 2023, 3:43:58 AM4/8/23
to se...@googlegroups.com

CpnetSocketServer is working fine on Windows 10. Thanks. Config file and log file when connected with CP/M3 attached.

 

On HDOS I cannot connect to the server on socket 0:. With CP/M3 I can connect without any issues.

 

 

With CP/M3, I can copy files to the windows server, but I cannot do a dir. I know this worked fine on the iMac

 

C> DIR P:  ; FAILS TO DISPLAY THE DIRECTORY

SYSTEM FILE(S) EXIST

 

C>DIR P:[FULL] ; WORKS FINE

 

C> P:=C:*.*[V] ; WORKS FINE and all files saved to the windows server

 

C> B:=P:*.*[V]  ; MULTIPLE FILES COPY FROM SERVER FAILS

ERROR: FILE NOT FOUND  - P:?????????.??

 

C>PIP B:=P:WT.SUB[V] ; SINGLE FILE COPY FROM SERVER WORKS FINE

 

 

 

Thanks,

Norberto

config-file.txt
cpnet00.log

norberto.collado koyado.com

unread,
Apr 8, 2023, 3:50:46 AM4/8/23
to se...@googlegroups.com

CP/M3 Network Status:

Douglas Miller

unread,
Apr 8, 2023, 7:26:30 AM4/8/23
to se...@googlegroups.com

The problem with displaying files on CP/M 3 is due to Windows vs. iMAC/Linux. For Windows servers, you'll need to add "cpnetserver_nosys" to your server config file.

On HDOS, I used to occasionally see that "Server unknown" error, but it was transient (and I thought I fixed it). On starting FTP and getting the error, try the command "open 0" to retry the connection. If that does not connect you, we'll have to work on debugging that - probably a timing error (which is odd as I think the new code, written in C, is slower and should not timeout as soon as ASM code in CP/M 3). If trying the "open 0" again does fix it, I'll also want to work on why it doesn't get it the first time.

norberto.collado koyado.com

unread,
Apr 8, 2023, 3:28:16 PM4/8/23
to se...@googlegroups.com

I do have the “cpnetserver_nosys” in the config-file. See attached file for review for any missing parameters.

 

The ftp 0 command or “open 0” does not start the Wiznet IP connection on the board. Once I boot HDOS and type ftp 0 , I cannot ping the Wiznet controller from the laptop.

 

A workaround is to do the following:

  1. From the H8 console “H8: Boot WW-0: ; This will start the Wiznet IP connection. I just wait to timeout and then proceed to boot HDOS.
    1. I need a command in HDOS similar to NDOS3 to start the Wiznet controller within HDOS.

 

Once booted into HDOS, I can connect to the Server, but cannot do a dir. It is not hung as I can do a Control-C to exit. I mapped in CP/M3 Network P:=C: and I see on status “Remote A:”. I created an “a” folder but still cannot do a dir. It just stays there waiting for something…

 

I have somewhere a wireless Raspberry Pi, perhaps that will be the easy way to get the Java working properly with Linux as Windows cpnet java server is not working properly or needs some fine tuning.

 

Here is a trace:

 

.

config-file.txt

Douglas Miller

unread,
Apr 8, 2023, 3:37:55 PM4/8/23
to se...@googlegroups.com

Wait, did you run "WIZCFG R" on HDOS? You'll need to do that after RESET/boot in order to configure the WIZnet chip. The WIZnet chip losses it's configuration every time you RESET. FTP and FTPPIP do not program the WIZnet chip.

Another thing to do is to look at the messages printed by CpnetSocketServer. They show connect and disconnect, and also an init message when the client sends the first message. You can also start the server with the "debug" option to get more verbose messages (java -jar CpnetSocketServer.jar conf=<cfg-file> debug).

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

norberto.collado koyado.com

unread,
Apr 8, 2023, 4:01:38 PM4/8/23
to se...@googlegroups.com

The “"WIZCFG R" fixed the issue. Thanks.

 

The log file is showing the following:

 

CpnetSocketServer v1.2

Using config in config-file.txt

Server 00 Listening on 10.0.0.221 port 31100 debug true

Connection from 10.0.0.60 (31100)

SID mismatch 3f != 00

Disconnected from 10.0.0.60 (ff)

Connection from 10.0.0.60 (31100)

 

I do not see the SID mismatch message when running CP/M3.

 

Norberto

 

From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Douglas Miller
Sent: Saturday, April 8, 2023 12:38 PM
To: se...@googlegroups.com
Subject: Re: [sebhc] Networking for HDOS (update)

 

Wait, did you run "WIZCFG R" on HDOS? You'll need to do that after RESET/boot in order to configure the WIZnet chip. The WIZnet chip losses it's configuration every time you RESET. FTP and FTPPIP do not program the WIZnet chip.

norberto.collado koyado.com

unread,
Apr 8, 2023, 4:05:50 PM4/8/23
to se...@googlegroups.com

Every time I do the “ftp> dir”, it disconnects from the server.

 

CpnetSocketServer v1.2

Using config in config-file.txt

Server 00 Listening on 10.0.0.221 port 31100 debug true

Connection from 10.0.0.60 (31100)

 

Note: Here is when I do "ftp> dir"

 

SID mismatch 3f != 00

Disconnected from 10.0.0.60 (ff)

 

From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of norberto.collado koyado.com
Sent: Saturday, April 8, 2023 1:02 PM
To: se...@googlegroups.com

Douglas Miller

unread,
Apr 8, 2023, 4:10:37 PM4/8/23
to se...@googlegroups.com

Let me see if I introduced a bug somewhere. that "3f" is suspiciously like a '?' which is part of the search pattern.

norberto.collado koyado.com

unread,
Apr 8, 2023, 4:16:45 PM4/8/23
to se...@googlegroups.com

On CP/M3 when I do the “C> DIR P:” and get “ SYSTEM FILE(S) EXIST” only message, here is the trace for such command. Hopefully you can figure out the issue.

 

CpnetSocketServer v1.2

Using config in config-file.txt

Server 00 Listening on 10.0.0.221 port 31100 debug true

Connection from 10.0.0.60 (31100)

Remote 10.0.0.60 is ef

Creating HostFileBdos 00 device with root dir C:/Wiznet_Server/

00 00 ef 62 00:6a 00 00 00...

01 ef 00 62 00:00 00 00 00...

00 00 ef 11 25:00 00 01 3f...

01 ef 00 11 20:00 00 46 54...

00 00 ef 12 01:00 00 46 54...

01 ef 00 12 20:01 00 46 54...

00 00 ef 12 01:01 00 46 54...

01 ef 00 12 20:02 00 57 49...

00 00 ef 12 01:02 00 57 49...

01 ef 00 12 00:ff 00 57 49...

Douglas Miller

unread,
Apr 8, 2023, 4:28:49 PM4/8/23
to se...@googlegroups.com

Looks like you're using a very old copy of the server. I've made certain the the github version is the latest, give that a try:

https://github.com/durgadas311/cpnet-z80/blob/master/contrib/CpnetSocketServer.jar

norberto.collado koyado.com

unread,
Apr 8, 2023, 4:41:22 PM4/8/23
to se...@googlegroups.com

This new version fixed the issue with CP/M3. Now CP/M3 is working great over the network. Thanks!

 

On HDOS still broken and it disconnects when doing the “ftp> dir” command.

 

CpnetSocketServer v1.3

Using config in config-file.txt

Server 00 Listening on 10.0.0.221 port 31100 debug true

Connection from 10.0.0.60 (31100)

SID mismatch 3f != 00

Disconnected from 10.0.0.60 (ff)

 

 

Douglas Miller

unread,
Apr 8, 2023, 4:43:58 PM4/8/23
to se...@googlegroups.com

I tried that on my simulator, both HDOS2 and HDOS3, and it works. But this is Linux running the server code. I hope there's not some issue with Windows JAVA Socket library scrambling the messages. Did running the new server with "debug" and the HDOS FTP produce any more output?

norberto.collado koyado.com

unread,
Apr 8, 2023, 4:54:59 PM4/8/23
to se...@googlegroups.com

That is all I get when doing the “ftp> dir” command. I reconnected and tried again with same results. It works fine with CP/M3. Can you share your config-file to compare?

 

pnetSocketServer v1.3

Using config in config-file.txt

Server 00 Listening on 10.0.0.221 port 31100 debug true

Connection from 10.0.0.60 (31100)

SID mismatch 3f != 00

Disconnected from 10.0.0.60 (ff)

Connection from 10.0.0.60 (31100)

SID mismatch 3f != 00

Disconnected from 10.0.0.60 (ff)

 

I’m trying to find the wireless Raspberry Pi board. I’m downloading:

 

Raspberry Pi OS with desktop

  • Release date: February 21st 2023
  • System: 32-bit
  • Kernel version: 5.15
  • Debian version: 11 (bullseye)

Douglas Miller

unread,
Apr 8, 2023, 4:56:46 PM4/8/23
to se...@googlegroups.com

The fact that it works for CP/M 3 seems to suggest that Windows is OK, but I'm trying to find an explanation. You are running HDOS 2 on the H67? Perhaps I need to try that to see if something is corrupting the program image.

norberto.collado koyado.com

unread,
Apr 8, 2023, 4:58:58 PM4/8/23
to se...@googlegroups.com

Let me try on the CF card using Rick’ HDOS image.

norberto.collado koyado.com

unread,
Apr 8, 2023, 5:24:06 PM4/8/23
to se...@googlegroups.com

Booting from CF controller HDOS3 Rick’s image, produces same results.

 H8: Boot FF-0:1 ; boots HDOS 3.

 

CpnetSocketServer v1.3

Using config in config-file.txt

Server 00 Listening on 10.0.0.221 port 31100 debug true

Connection from 10.0.0.60 (31100)

SID mismatch 3f != 00

Disconnected from 10.0.0.60 (ff)

 

 

Douglas Miller

unread,
Apr 8, 2023, 5:52:37 PM4/8/23
to se...@googlegroups.com

Let me see if I can reproduce it here, and track it down.

Douglas Miller

unread,
Apr 8, 2023, 6:17:54 PM4/8/23
to se...@googlegroups.com

I'm not able to reproduce any problems here, using an H67 HDOS2 image I got recently (not sure if from Norberto or Glenn). What CPU are you running on? What clock speed is set?

One last-ditch effort might be to get a core dump (vdump3). When it is hung on the dir command, press RESET and boot vdump3.

I had a thought about running HDOS on the Z180. If HDOS used any of the "undocumented" Z80 instructions, it will cause a TRAP which might not be handled by HDOS. But, I don't think HDOS is using that many Z80 instructions - probably just the basic I/O extensions and probably just in the H67/H37 drivers.

On 4/8/23 16:23, norberto.collado koyado.com wrote:

norberto.collado koyado.com

unread,
Apr 8, 2023, 6:23:15 PM4/8/23
to se...@googlegroups.com

I did more stress testing with CP/M3 and it is bullet proof. Very reliable.

Douglas Miller

unread,
Apr 9, 2023, 6:50:04 AM4/9/23
to se...@googlegroups.com

Any chance something (FTP.ABS) got corrupted when transferring to the H8? We have occasionally seen corruption via USB/VDIP.

Glenn Roberts

unread,
Apr 9, 2023, 7:14:51 AM4/9/23
to se...@googlegroups.com
Fwiw I’ve never seen a file get corrupted in USB/VDIP transfer via the Vinculum utilities. If you ever see this and can provide any details I’d like to understand what happened and correct the problem.

Sent from my iPad

On Apr 9, 2023, at 6:50 AM, Douglas Miller <durga...@gmail.com> wrote:



<image001.jpg>

Douglas Miller

unread,
Apr 9, 2023, 7:17:57 AM4/9/23
to se...@googlegroups.com

I believe the cases were more like something corrupted the USB stick, or corrupted the file before copying to USB. Maybe a bad USB stick.

Douglas Miller

unread,
Apr 9, 2023, 9:00:27 AM4/9/23
to se...@googlegroups.com

Norberto,

I added the 'sum' command to the repo (https://github.com/durgadas311/hdos-net/blob/master/bin/sum.abs) and posted the computed checksums for the current programs (https://github.com/durgadas311/hdos-net/blob/master/checksums). With those, you should be able to confirm that the programs made it all the way to HDOS without corruption.

norberto.collado koyado.com

unread,
Apr 9, 2023, 2:17:50 PM4/9/23
to se...@googlegroups.com

Douglas,

 

Nice utility to have. The computed checksum matches your website checksums for the files already downloaded onto HDOS. I’m using the Z80 V4 board with 512KB of RAM @ 2MHz. Attached is the vdump3 output file.

 

Norberto

 

 

COREDUMP.OUT

norberto.collado koyado.com

unread,
Apr 9, 2023, 2:33:19 PM4/9/23
to se...@googlegroups.com

New vdump3 file as I forgot to enable the 512KB board.

 

Norberto

COREDUMP.OUT

Douglas Miller

unread,
Apr 9, 2023, 4:48:33 PM4/9/23
to se...@googlegroups.com

Looks like your ROM config does not have the H8-512K memory enabled, so it did not save the low memory contents. Some of the variables I want to look at are in what would have been saved memory.

I was side-tracked, so am only starting to look at it now. If you can make another dump with the ROM config setting H8-512K set to 'Y', that would help.

norberto.collado koyado.com

unread,
Apr 9, 2023, 4:55:08 PM4/9/23
to se...@googlegroups.com

Yes that is correct and it is enabled now. Latest file attached.

COREDUMP.OUT

Douglas Miller

unread,
Apr 9, 2023, 6:56:50 PM4/9/23
to se...@googlegroups.com

Thanks, that dump is clearer. I've looked through the stack and buffers, and don't see anything wrong with the data that *should* have been sent. I'm working on a theory about some unexpected behavior of the WIZnet chip, and will work up a test version to see if that fixes it. I need to step away for now, though.

norberto.collado koyado.com

unread,
Apr 9, 2023, 7:36:42 PM4/9/23
to se...@googlegroups.com

Found the Raspberry Pi wireless card, loaded the Linux OS, and configured Java. CP/M3 works great, but HDOS is still doing the same thing.

 

My windows is using this version of Java

 

 

The Raspberry Pi is using Java version “1.8.0_312”. Which version of Java are you using?

Douglas Miller

unread,
Apr 9, 2023, 7:47:28 PM4/9/23
to se...@googlegroups.com

I'm currently thinking that there is some undocumented behavior of the WIZnet causing this. The HDOS code puts the data into the TxFIFO in several chunks, then issues the SEND command (the CP/NET SNIOS puts the data in one large chunk). So, the HDOS code updates the TxFIFO write pointer several times, while CP/NET does that only once (per SEND). The documentation implies that the SEND command uses the TxFIFO *read* pointer as it's starting point, but what you're seeing looks as if it is using the previous value of the *write* pointer (or somehow the read pointer is getting updated without the SEND command). This would seem to be a significant bug to me, if it is what is happening. Perhaps the next step is for me to add some custom debug to CpnetSocketServer to see if we can capture more data, then work on the theory that the WIZnet is misbehaving.

norberto.collado koyado.com

unread,
Apr 9, 2023, 7:48:38 PM4/9/23
to se...@googlegroups.com

Or send me your server ip address and port number to try HDOS.

 

I did try to open your server, but it failed: 96.42.194.246 12545 0

 

Norberto

Douglas Miller

unread,
Apr 10, 2023, 6:10:32 PM4/10/23
to se...@googlegroups.com

I found a posting on the WIZnet forum that confirms my suspicion, and explains what the W5500 is doing. Looks like at least one other person has tried what I did and ran into this problem. I updated my simulator to behave according to that description of Tx FIFO pointers, and can reproduce Norberto's issue. I then applied (and tested) a fix and updated the repo at https://github.com/durgadas311/hdos-net.

Ref: https://forum.wiznet.io/t/topic/5010

This raises the same question, though, about the Rx FIFO pointer registers. I don't find any discussions about that, so we'll just have to see if new problems arise with this fix. I'm also working on some changes to better handle the situation where the remote end disconnects abruptly like this, which should error out rather than hang.


On 4/9/23 18:36, norberto.collado koyado.com wrote:

norberto.collado koyado.com

unread,
Apr 10, 2023, 11:24:54 PM4/10/23
to se...@googlegroups.com

.A little more better. At least it doesn’t hang on dir. I create drive “a” with CP/M3 and the dir commands failed to show drive content.

 

I was trying to use the put and get commands and I cannot get the syntax correct. I need some examples for FTP.

 

Also I did try ftppip but it fails to write properly. It created fine the filename at the server.

 

It seems that it does not understand the cpnet server directory to be able to read/write files.

 

 

 

Norberto

 

Douglas Miller

unread,
Apr 11, 2023, 7:41:18 AM4/11/23
to se...@googlegroups.com

I'm guessing that the RX_RD FIFO pointer has the same odd behavior as the TX_WR FIFO pointer. I'll make a similar change to the pointer handling.  I haven't found any confirmation of this behavior, but it seems reasonable to assume they designed both RX and TX the same.

I've pushed a new version to the repo.

When using ftp, you first set local and remote drives, using 'lcd' and 'cd' commands respectively (you can use 'ldir' and 'dir' to inspect those). The 'status' command shows you remote and local drive names. Then you use the command "get <file-spec>" to copy files from the current remote drive to the current local drive. Similarly, use "put <file-spec>" to copy files from the local drive to remote. The "<file-spec>" is your typical 8+3 file specification, possibly containing wildcards. It does NOT have a drive prefix.

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

norberto.collado koyado.com

unread,
Apr 11, 2023, 10:44:26 AM4/11/23
to se...@googlegroups.com

Thanks Douglas and this version worked fine.

 

 

From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Douglas Miller
Sent: Tuesday, April 11, 2023 4:41 AM
To: se...@googlegroups.com
Subject: Re: [sebhc] Networking for HDOS (update)

 

I'm guessing that the RX_RD FIFO pointer has the same odd behavior as the TX_WR FIFO pointer. I'll make a similar change to the pointer handling.  I haven't found any confirmation of this behavior, but it seems reasonable to assume they designed both RX and TX the same.

Douglas Miller

unread,
Apr 11, 2023, 2:09:14 PM4/11/23
to se...@googlegroups.com

Thanks for testing this for me!

norberto.collado koyado.com

unread,
Apr 11, 2023, 3:22:13 PM4/11/23
to se...@googlegroups.com
I will do more testing to be sure the data integrity is preserved.
From: se...@googlegroups.com <se...@googlegroups.com> on behalf of Douglas Miller <durga...@gmail.com>
Sent: Tuesday, April 11, 2023 11:09:11 AM
To: se...@googlegroups.com <se...@googlegroups.com>

norberto.collado koyado.com

unread,
Apr 11, 2023, 11:30:19 PM4/11/23
to se...@googlegroups.com

Tested back and forth moving a lot of files without any issues. Also, tested some files and they ran fine, so no integrity  issues. So far so good.

 

 

 

Thanks,

Norberto

Terry Smedley

unread,
Apr 13, 2023, 12:39:29 PM4/13/23
to SEBHC
Douglas:

I will be attempting to startup HDOS networking in an H8 environment very similar to what Norberto has described.  I've verified the SPI functions of the WizNET board, but am awaiting the WIZ850io module (expected tomorrow).  The server side will temporarily be a Windows 10 desktop.  I've copied Norberto's config file for Win10.

Just FYI that there's another of your WizNET cards will be entering service.   Thanks for all of this work!

tas

Douglas Miller

unread,
Apr 13, 2023, 12:57:39 PM4/13/23
to se...@googlegroups.com

Great! be sure and let me know if you run into problems or have questions.

For review, the documentation is at:

https://github.com/durgadas311/cpnet-z80/blob/master/doc/CpnetSocketServer.pdf
https://github.com/durgadas311/cpnet-z80/blob/master/doc/CPNET-WIZ850io.pdf
https://github.com/durgadas311/hdos-net/blob/master/doc/HDOS-ftp.pdf

You'll need to run "wizcfg r" to copy the WIZnet configuration from nvram to the WIZ850io after booting HDOS. You'll need to first set the configuration in the nvram using 'wizcfg' (one time). Help on using 'wizcfg' is in the CPNET-WIZ850io document.

norberto.collado koyado.com

unread,
Apr 13, 2023, 2:30:47 PM4/13/23
to se...@googlegroups.com
Douglas, can you add a command in HDOS to erase all the files at the server and the ability to delete a single file?
Sent: Thursday, April 13, 2023 9:57:36 AM
To: se...@googlegroups.com <se...@googlegroups.com>

Douglas Miller

unread,
Apr 13, 2023, 5:49:15 PM4/13/23
to se...@googlegroups.com

I had left that out for safety concerns, waiting to see if anyone asked for it.

I have now added a "delete" command to FTP.ABS, and if you use any wildcards it will prompt for confirmation (Y/YES). Updated the document, too.

norberto.collado koyado.com

unread,
Apr 13, 2023, 6:56:59 PM4/13/23
to se...@googlegroups.com
I asked as I can delete files on the server when using CPM/3. We should have the same capabilities as well on HDOS. Thank you and I will retest the new ftp file tonight.
Sent: Thursday, April 13, 2023 2:49:11 PM

Douglas Miller

unread,
Apr 13, 2023, 7:01:23 PM4/13/23
to se...@googlegroups.com

Well, we won't be able to do everything you can do in CP/NET. CP/NET is a (fairly) complete networking solution. All we're providing for HDOS (at this time) is a file transfer capability, and I've added a few convenience commands to the FTP.ABS part of that solution.

norberto.collado koyado.com

unread,
Apr 13, 2023, 9:22:11 PM4/13/23
to se...@googlegroups.com

This is better than nothing. Thank you for enabling HDOS over the network for file transfer. We need to enable the H89 to be able to move data between the H8 and the H89 over the network using the file server.

 

Will it be possible for the H8 to connect to another H8 and see each other drives for data transfer? Or it will be too complicated to do? Just curios

 

Norberto

Douglas Miller

unread,
Apr 13, 2023, 9:35:33 PM4/13/23
to se...@googlegroups.com

We could come up with some sort of peer-to-peer solution, for example like what one does with kermit (or I guess xmodem). We could also run MP/M on one of the systems, but that's probably not what you want as I'm guessing you want to exchange files between two systems, then go back to "normal" operation using the files just transferred.

It should be possible for one of the two systems to run the equivalent of CpnetSocketServer (only in the form of a .ABS). For example, on one system run FTPSERVR.ABS and on the other run FTP.ABS - for the duration of the file exchanges.

norberto.collado koyado.com

unread,
Apr 13, 2023, 11:03:05 PM4/13/23
to se...@googlegroups.com

The delete command worked fine and thank you. 😊

Terry Smedley

unread,
Apr 19, 2023, 5:04:55 PM4/19/23
to SEBHC
This is a quick recap of my WizNET startup experience.  It doesn't take the place of the very complete documentation that Douglas has provided.  It's not meant to be an argument for the use of WizNET over other network alternatives.  The WizNET board and software are available now, so I gave them a try.  I generally live in the HDOS world, so my findings don't include the use of WizNET with CP/M, which is an even more robust implementation than what is described here.

If you want the Reader's Digest summary of my findings:  WizNET for HDOS on the H8 is EASY to implement, EASY to use, and FAST at transferring data.  It just works!  With the few hardware constraints noted at the end of my summary, WizNET started up as published with little to do except assign a couple of IP addresses and a port.  If this was a Siskel & Ebert movie review, it would be "Two Enthusiastic Thumbs Up!"

Why would you want to use a network connection to the H8?

Most important to me:
1) Make file backups simple enough that I would do them regularly
2) Make it easy to exchange files with others by eMail attachment

Of course, both of those things can be done by other methods.  Glenn's USB utilities have been my "goto" method for file exchange, but plugging and unplugging the USB key can be inconvenient.  I wanted to try a network solution, which promised no more USB key swapping.

If you have more than one H8, you could also use the WizNET server as a central repository for common files.  Then with some "check out/in" discipline, you could develop on multiple machines without having to mechanically ferry changes between multiple H8s.

Is it difficult to setup a server?

Nope!  Douglas has made this Eazy-Peazee.  You don't need a dedicated server box, and you don't need a special OS - you just need Java (which you probably already have).  You can run it on your desktop PC, whether that be Mac, Windows, or Linux.  I've run the server-side .jar on MacOS, Windows 7, Windows 10, and a Win7 VM on Server 2016.  The only networking you need to know is:  the IP address of the host running the server and the port number you want to use.  If you're running a firewall on your desktop, you need to know how to open the firewall for incoming connections on the port you choose.

A very small ASCII-editable configuration file holds the networking information.  To run the server, you invoke the JAVA .jar with a command line like:

"java -jar CpnetSocketServer.jar conf=config-file.txt"

You can use whatever methods your desktop OS supports to automate the startup, or maybe you just want to run the server when you need it.  That's it for setting up the server.  If you've already got Java loaded, the whole startup process takes just minutes.

How difficult is the H8 (network client) setup?

About as difficult as the server setup.  You need to assign an available IP address for the client (it does not use DHCP), and you need to remember the IP configuration you gave your server.  A setup program on the H8 stores that information in NVRAM on the WizNET card so you don't need to reenter it once you've initially loaded it into NVRAM.

With the server .jar running and the WizNET card plugged into your (wired) network, you use an H8 program that looks a lot like FTP to connect to the server and transfer files.  If you haven't used FTP before, it's about as simple as it can be:

GET {filename} retrieves a file from the server and writes it to the local H8 disk
PUT {filename} .... well, I think you can guess what that does

Wildcards can be used, and you can navigate through directory trees on both the server and H8.  Since HDOS 2.0 on the H8 doesn't support directories, that means being able to select any mounted disk device for file transfer operations.

How would I use a WizNET connection to backup my H8?

How about "PUT *.*"?  Copies everything from an HDOS disk device to a directory on the server.  Since you can have multiple directories on the server side, you could keep separate backups for multiple HDOS disk devices (or keep independent HDOS and CP/M backups).  I no longer have an excuse for skipping development file backups.

How difficult is it to build the WizNET board?

The v1.0 board is half-sized, and the component count is relatively light.  I had no difficulty sourcing any of the components.  There are a few components you can omit if you are trying to save money or time (the LED bar graph and its associated driver IC, and a 5v to 3.3v level translator IC might be optional depending upon your use case).  For the Blinkenlights crowd, the LED bar graph provides some entertaining visuals of received data.

If one or more of these conditions apply to you, you probably want to wait for the next generation WizNET board that Douglas and Norberto are finalizing now:
Use a Trionyx Z-H8 2/4MHz CPU
        Plan to use a Z180 CPU in the future
Use I/O wait states (from any source, including the System Support I or HA-8-3 clone boards)
Want to run at CPU speeds above 8MHz

If those conditions don't apply to you, the v1.0 board is available now and it works beautifully for the "no wait state, 8MHz or less" use case.











Glenn Roberts

unread,
Apr 19, 2023, 6:06:11 PM4/19/23
to se...@googlegroups.com
This is great info Terry, thanks for taking the time to write this up!

In my case the “master” copy of any developmental file would reside on the PC where I can edit it, sync with GitHub, back it up and do other things like upload to SEBHC.org or email it.  So it sounds like I could edit the file on the PC, save my edits, then use a GET command on the H8 to grab it, compile and run, right? Then once I have a good .ABS file I could PUT that back on the server for safekeeping? No more sneaker net with flash drives…?!

Sent from my iPad

On Apr 19, 2023, at 5:04 PM, Terry Smedley <terry....@gmail.com> wrote:

This is a quick recap of my WizNET startup experience.  It doesn't take the place of the very complete documentation that Douglas has provided.  It's not meant to be an argument for the use of WizNET over other network alternatives.  The WizNET board and software are available now, so I gave them a try.  I generally live in the HDOS world, so my findings don't include the use of WizNET with CP/M, which is an even more robust implementation than what is described here.

Terry Smedley

unread,
Apr 19, 2023, 6:13:35 PM4/19/23
to SEBHC
Glenn:

Yup!  The server-side files just reside in a directory of your choosing on your desktop OS, so you can edit, sync, eMail them just like any other file on your PC.  There's the usual issue of end-of-line handling differences between different operating systems, but you've already noted several ways to deal with that.

Douglas also put together a "FTPPIP.ABS" program that more closely resembles the VPIP/VPUT/VGET utilities.  I haven't (yet) experimented with it.

tas

Terry Smedley

unread,
Apr 20, 2023, 1:03:44 AM4/20/23
to SEBHC
Further on HDOS backup to WizNET server.

Douglas has a "FTPPIP.ABS" utility (inspired by Glenn's VPIP, I believe) that makes HDOS backup to the network a one-line affair:

FTPPIP.ABS [10]a:=SY0:*.*

is an example command line that will copy all files from HDOS device SY0: to WizNET server [10], directory a: 

HDOS file backups are so easy that I really have zero excuses for not regularly protecting my data.

tas


On Wednesday, April 19, 2023 at 3:06:11 PM UTC-7 Glenn Roberts wrote:

norberto.collado koyado.com

unread,
Apr 27, 2023, 1:14:39 AM4/27/23
to se...@googlegroups.com

WizNET board that Douglas and Norberto are finalizing now:
                Use a Trionyx Z-H8 2/4MHz CPU

        Plan to use a Z180 CPU in the future

                Use I/O wait states (from any source, including the System Support I or HA-8-3 clone boards)
                Want to run at CPU speeds above 8MHz

We successfully tested the changes required to run such network board with the HA-8-3 clone along with the Z80/Z180 CPU boards at high speeds. Also, we will be adding two SD cards to be able to boot HDOS and Heath CP/M as well.  Rick, I will need your help again. 😊

 

It is going to be a full size board and layout is completed and soon will order some boards to test out the new improvements.

 

Attached is a picture of such board.

 

Thanks,

Norberto

H8-WizNet-SD-Controller.JPG

norberto.collado koyado.com

unread,
Apr 30, 2023, 6:20:58 PM4/30/23
to se...@googlegroups.com

Updates:

 

I prototyped the SD card circuit into our current WizNet board and it booted fine CP/M3. Once I get some debug boards I will need Rick’s and Joe’s help “again” to enable HDOS and Heath CP/M to boot from such SD card. The minimum supported SD card capacity is 4GB as we only support LBA and not BUA sector addressing. I tested with 128GB and no issues as they are cheaper. You can buy 2-pcs of Micro-SD 128GB in Amazon for $20.00.

 

Supported by Z180, Z80 V4, and 8080A V1 32KB V2.0 monitor boards. With Rick/Joe help we can add support for Heath 8080A and Heath Z80 boards in the near future.

 

Storage solutions that we have working:

  1. H67/Z67-IDE+
  2. H37 Floppy controller
  3. H17 Floppy controller
  4. H8-DUAL-CF-Controller (Thanks to Rick and Joe for enabling HDOS and Heath CP/M).
  5. H8-WizNet-DUAL-SD-Controller (CP/M3 for now)
  6. VDIP1

 

In the near future H47 floppy controller using a single SD card to support 4 drives of 1.2MB each. This is to complete Heathkit of supported storage boards for HDOS/3 and HEATH CP/M for the H8 system. It will be nice to borrow an H8 H47 controller to speed-up development.

 

Pictures below:

 

Tested with: https://www.adafruit.com/product/254.  We will be supporting different breakout boards which you can buy from Amazon. As all MICRO-SD breakout boards pin out are not the same, we will provide a personality board for each one or you can create your own custom one.

 

 

 

 

 

More to come…

 

Norby

 

 

From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of norberto.collado koyado.com
Sent: Wednesday, April 26, 2023 10:14 PM
To: se...@googlegroups.com

glenn.f...@gmail.com

unread,
Apr 30, 2023, 8:20:45 PM4/30/23
to se...@googlegroups.com

That’s quite a smorgasbord of storage options!  On the H47: I understand high density floppy drives (5.25” 1.2M & 3.5” 1.44 M?) can emulate (electronically) the older 8” drives? Will that be an option on the new controller board?

image001.jpg
image002.jpg
image003.png
image004.png

Mark Garlanger

unread,
Apr 30, 2023, 9:44:51 PM4/30/23
to se...@googlegroups.com

The H47 card is not a controller, but an interface card. So it won't be able to handle actual drives. It is basically a glorified parallel port interface. The Remex master 8" drive has its own processor and controller chip on it. So that part would have to be recreated, in order to use real drives.

Mark

norberto.collado koyado.com

unread,
Apr 30, 2023, 10:59:37 PM4/30/23
to se...@googlegroups.com

As Mark mentioned, it will be difficult to re-create a board that will control 3.5” floppies at 1.44MB capacity like the REMEX controller did for the 8” drives. It will be like combining the H47 + H37 ó 3.5” floppy drives onto a single board and have a Z80 @ 10MHz talk to the H47 and the H37 controller to read/write to the 3.5” floppy drives.

 

This is what I envision:

  1. Duplicate original H47 Disk Interface  without the serial ports and just the H47 interface. I hope that the Heath H47 schematics do not have any wiring errors as it will be hard to debug.
  2. Once we have the H47 Disk Interface working by using the logic analyzer and test scripts, then I can proceed to connect a Microcontroller with an SD card to emulate 4 drives. The microcontroller will be just getting commands from the H8 computer and providing a response back. This new Microcontroller board can also interface with the original Heath H47 Disk Interface and it should work.
  3. If I get the H47 command structure working properly, then HDOS/3 and CP/M should work out of the box.

 

Norberto

 

From: se...@googlegroups.com <se...@googlegroups.com> on behalf of Mark Garlanger <garl...@gmail.com>
Date: Sunday, April 30, 2023 at 6:44 PM
To: se...@googlegroups.com <se...@googlegroups.com>
Subject: Re: [sebhc] Networking for HDOS (update)

 

The H47 card is not a controller, but an interface card. So it won't be able to handle actual drives. It is basically a glorified parallel port interface. The Remex master 8" drive has its own processor and controller chip on it. So that part would have to be recreated, in order to use real drives.

 

Mark

 

 

Image removed by sender.

Image removed by sender.

 

From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Douglas Miller
Sent: Tuesday, April 11, 2023 4:41 AM
To: se...@googlegroups.com
Subject: Re: [sebhc] Networking for HDOS (update)

 

I'm guessing that the RX_RD FIFO pointer has the same odd behavior as the TX_WR FIFO pointer. I'll make a similar change to the pointer handling.  I haven't found any confirmation of this behavior, but it seems reasonable to assume they designed both RX and TX the same.

I've pushed a new version to the repo.

When using ftp, you first set local and remote drives, using 'lcd' and 'cd' commands respectively (you can use 'ldir' and 'dir' to inspect those). The 'status' command shows you remote and local drive names. Then you use the command "get <file-spec>" to copy files from the current remote drive to the current local drive. Similarly, use "put <file-spec>" to copy files from the local drive to remote. The "<file-spec>" is your typical 8+3 file specification, possibly containing wildcards. It does NOT have a drive prefix.

 

On 4/10/23 22:24, norberto.collado koyado.com wrote:

.A little more better. At least it doesn’t hang on dir. I create drive “a” with CP/M3 and the dir commands failed to show drive content.

 

I was trying to use the put and get commands and I cannot get the syntax correct. I need some examples for FTP.

 

Also I did try ftppip but it fails to write properly. It created fine the filename at the server.

 

It seems that it does not understand the cpnet server directory to be able to read/write files.

 

 

Image removed by sender.

norberto.collado koyado.com

unread,
May 8, 2023, 12:47:35 AM5/8/23
to se...@googlegroups.com

For the new/updated WizNet/SDC controller, I decided to layout different PM’s for the different types of SD breakout boards outlined in the attached documentation. We have one more pending test before ordering some proto boards to test all the new changes.

 

For example:

 

 

 

 

H8 Storage solutions:

    1. H67/Z67-IDE+
    2. H37 Floppy controller
    3. H17 Floppy controller
    1. H8-DUAL-CF-Controller (Thanks to Rick and Joe for enabling HDOS and Heath CP/M). Works with MMS CP/M3.
    2. H8-WizNet-DUAL-SD-Controller (CP/M3 for now – In development)
    3. VDIP1 (Supported by HDOS2/3, Heath/MMS CP/M)
    4. H47 Remix Disk Interface – Heath HDOS2/3 and Heath CP/M (In development)
    5. H8-8MB RAM DISK (In development)

    Thanks,

    Norberto

    sdcard-physical.pdf

    norberto.collado koyado.com

    unread,
    May 24, 2023, 1:01:05 AM5/24/23
    to se...@googlegroups.com

    I think we resolved all the issues with the SPI clock and the SD breakout boards on the H8-WizNet-DUAL-SD-Controller.

     

    The H8 has been running stress on the SD cards at 16MHz without any issues, using CP/M3 and Z180 CPU.

     

    Here is a picture of the proto board with both SD cards.

     

     

    Norberto

    Joseph Travis

    unread,
    May 24, 2023, 9:01:08 AM5/24/23
    to se...@googlegroups.com
    Credit where credit is due.  Rick is solely responsible for bringing up HDOS and CP/M on the CF boards.  I supported his efforts through testing / debugging (and maybe some moral support) along with writing the documentation.

    Joe

    norberto.collado koyado.com

    unread,
    May 24, 2023, 10:49:41 AM5/24/23
    to se...@googlegroups.com

    I will need both support to enable HDOS and Heath CP/M on the dual SD card board once I get some proto boards.

     

    Norberto

     

    From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Joseph Travis
    Sent: Wednesday, May 24, 2023 6:01 AM
    To: se...@googlegroups.com
    Subject: Re: [sebhc] Networking for HDOS (update)

     

    Credit where credit is due.  Rick is solely responsible for bringing up HDOS and CP/M on the CF boards.  I supported his efforts through testing / debugging (and maybe some moral support) along with writing the documentation.

     

    Joe

     

     

     

    From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Douglas Miller

    From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Douglas Miller


    Sent: Tuesday, April 11, 2023 4:41 AM
    To: se...@googlegroups.com
    Subject: Re: [sebhc] Networking for HDOS (update)

     

    I'm guessing that the RX_RD FIFO pointer has the same odd behavior as the TX_WR FIFO pointer. I'll make a similar change to the pointer handling. I haven't found any confirmation of this behavior, but it seems reasonable to assume they designed both RX and TX the same.

    I've pushed a new version to the repo.

    When using ftp, you first set local and remote drives, using 'lcd' and 'cd' commands respectively (you can use 'ldir' and 'dir' to inspect those). The 'status' command shows you remote and local drive names. Then you use the command "get <file-spec>" to copy files from the current remote drive to the current local drive. Similarly, use "put <file-spec>" to copy files from the local drive to remote. The "<file-spec>" is your typical 8+3 file specification, possibly containing wildcards. It does NOT have a drive prefix.

     

    On 4/10/23 22:24, norberto.collado koyado.com wrote:

    .A little more better. At least it doesn’t hang on dir. I create drive “a” with CP/M3 and the dir commands failed to show drive content.

     

    I was trying to use the put and get commands and I cannot get the syntax correct. I need some examples for FTP.

     

    Also I did try ftppip but it fails to write properly. It created fine the filename at the server.

     

    It seems that it does not understand the cpnet server directory to be able to read/write files.

     

     

     

    Norberto

    Richard Davis Jr.

    unread,
    May 24, 2023, 1:04:12 PM5/24/23
    to se...@googlegroups.com
    Norberto,

    Should be fairly easy since I already did the CF board.

    Rick


    Douglas Miller

    unread,
    May 24, 2023, 1:23:54 PM5/24/23
    to se...@googlegroups.com

    The SDCard protocol is significantly more complicated than CF. You should not need to initialize the card if it was the boot device, which saves you some complexity.

    Reply all
    Reply to author
    Forward
    0 new messages