[Oberon] Oberon Digest, Vol 127, Issue 18

[Jörg]

Hi

So far, the only officially implemented way I know to get files in and out
is via RS232.

There are at least three other ways I could think of getting files in and
out ProjectOberon:
- plug the microSSD in a PC and copy files by reading/writing the
ProjectOberon filesystem on that SSD.
  (I have a prototype of that approach running under ETHOberon on Windows)
- add files to the RISC.img before cloning that file to the microSSD.
- add an Ethernet board to ProjectOberon, implement a driver for that board
and a small TFTP server (RFC1350) for it.
  To simplify the driver there are chips available that do all of the IP
work in HW.
  (eg. https://www.sparkfun.com/products/9473, offers a 4 pin SPI interface)

br
Jörg

-----Original Message-----
From: eas lab [mailto:lab.eas at gmail.com] 
Sent: Mittwoch, 7. Januar 2015 11:58
To: ETH Oberon and related systems
Subject: Re: [Oberon] Oberon Digest, Vol 127, Issue 18

> But the ProjectOberon SW does not "speak" Ethernet nor IP.

Good!
The absurd difficulty connecting between the PC & the rPi, next to each
other,
via an *ENCRYPTED* ssh/...bla..bla, is like using the NationalRailwaySystem
[and needing a visa] to get a glass of water from your kitchen.

OnTheOtherHand if you can't get files in and out, the device/project just
dies,
instead of flying/connecting to the outside-world.

How's the SPI?
Would it be viable to adapt PO2013's work on SPI, to the working
ARMlinuxOberon,
which can then communicate with the rest of the *nix system of the rPi?
Ie. to internet, FAT-fileSystems ...everything..



== Chris Glur.

--
Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
https://lists.inf.ethz.ch/mailman/listinfo/oberon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6097 bytes
Desc: not available
Url : https://lists.inf.ethz.ch/pipermail/oberon/attachments/20150107/bf89b80c/attachment.bin