Difference: McForth (6 vs. 7)

Revision 72019-01-17 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 150 to 150

Mass storage

Added:

>
> Forth without mass storage (blocks, screens) is a sad thing. A SD-Card interface could be a solution but this is an overkill for a small Forth system.

Changed:

<
<

Serial Communication by Input/Output Ports (switches and LEDs)

Another solution could be to use part of the Membership Card's input/output ports (Switches/LEDs). e.g. Serial Peripheral Interface, MSC is the SPI master, the host is the slave:

>
>

EEPROM Serial Communication

Added:

>
> Serial Peripheral Interface SPI, MC is the SPI master, the host is the slave. e.g. AT25M02 SPI EEPROM 2Mbit (256 KiB, $3) or 25LC512 (64 KiB, $1.50). DIL8 Package. 256 KiB seems very small in today's terms where storage is measured in GiB, but I think it's more than enough for a small Forth system.

Changed:

<
< CLK MSC ->- host MOSI MSC ->- host MISO MSC -<- host SS MSC ->- host or other peripherals (optional)

>
> CLK MC ->- host MOSI MC ->- host MISO MC -<- host SS MC ->- host or other peripherals (optional)

Deleted:

<
< You loose two LEDs and one switch.

Changed:

<
<

Serial EEPROM

e.g. AT25M02

SPI EEPROM 2Mbit (256 KiB)

Raspberry emulating SPI EEPROM

On RaspiElf switches/LEDs are already connected to Raspi's GPIOs. No need for additional hardware.

>
>

Serial EEPROM Connected to Centronics Connector (Switches and LEDs)

Sharing the LED and Switch port, you loose two LEDs and one switch. Conflict with the bootstrap loader, some sort of disable EEPROM needed e.g. switch or jumper.

SPI	MC (Master)	AT25xxx (Slave)	Interface
MISO	J2.9 IN7 SWITCH7	2 SO	direct
MOSI	J2.11 O7 LED7	5 SI	direct
CLK	J2.10 O6 LED6	6 SCK	direct
CS		1 CS	Pullup 10 k, switch to GND
	P4.3 VDD	8 VCC	+5V
	"	3 WP	+5V
	"	7 HOLD	+5V
	21 GND	4 GND	GND

Raspberry Pi can emulate SPI EEPROM. On RaspiElf the switches/LEDs are already connected to Raspi's GPIOs. No need for additional hardware. But I have to write an SPI server for the Raspberry Pi.

Serial EEPROM patched on MC PCB

SPI Mode 0, data is always latched in on the rising edge of SCK and always output on the falling edge of SCK.

SPI	MC (Master)	AT25xxx (Slave)	Interface
MISO	/EF2	2 SO	direct
MOSI	D0	5 SI	direct
CLK	TPB & N1 (OUT2)	6 SCK	wired AND; Pullup 10 k, 2 1N4148
CS		1 /CS	GND
		8 VCC	+5V
		3 /WP	+5V
		7 /HOLD	+5V
		4 GND	GND

Kermit/ZModem

What about using KERMIT or ZMODEM protocol for the file transfer and use the file system on the host? No need to add additional hardware (SD-card

Changed:

<
< is anyway to modern You could use an old CP/M or even a PDP11 as host.

>
> is anyway to modern You could use an old CP/M or even a PDP11 as host. The C-Kermit Local Server mode, e.g. MC can read/write the blocks as files block.0, block.2, block.255.

https://github.com/utoh/pygmy-forth/blob/master/extras/kermit/pfkerm.doc

View topic | History: r25 < r24 < r23 < r22 | More topic actions...