This is the extended version of the RAPID #5 sheet. Since space is limited and I wanted the RAPIDs to be a single sheet, easily read in under a minute I have created this page with things that I cannot fit in the sheet- links and images!
This is not a comprehensive representation of what happens in the Discord- there is too much going on to capture it all. Hopefully this will provide a bit more context and important links to the events covered in the RAPID sheets.
COCO Bring Up
* COCO: bring up via cassette port!
* TCH – FSK encoder allows FN to create audio on the fly (cassette input)
* using CMOC as a compiler to build coco disk images
* CMOC is a 6809-generating cross-compiler for a large subset of the C language
One of the first boots on the COCO from FujiNet
Proto Board designed by hideehoo (ChrisT)
I think the silkscreen work is done. Part numbers and/or component values have been added. I’ve also added ground planes to most of the unused areas of all layers. I ran into an issue with parts availability for the 3.3vdc voltage regulator so it’s been changed. Also, because of voltage drop-off concerns, with the voltage regulators, almost all of the components take their power from the unregulated +10vdc from the 1090/1 board via the two voltage regulators. The advantage here is also a reduced parts count and, since you need a 1090/1 anyhow, I don’t think it’s a big deal. I’ll review it on and off over the next day or so. Unless I find an issue to change, this is the board I am ordering.
The FujiNet 1090 Board designed by reifsnyderb
JeffP continues tweaks to the 68k firmware – nearing prototype
• PIO using DMA for multiple DCDs and floppy
• trying to get a prototype board design and PCBs to continue dev
AppleFN layout from Chris Tersteeg
FujiNet Library Sample Apps
Fenrock: I've made httpbin an example application for using network library in fujinet-apps. It's working on Apple2 and Atari. Interestingly the CRLF handling isn't working (you can see 9b in the atari hex dump output, and in A2 it's 0d but I'm specifying LF (0x0a) in the call to network_open, so I need to debug that). The code does: * JSON queries (which are GET but in JSON mode) * PUT/DELETE/POST * Adding http headers to requests * network_read to show doing a normal GET (I will add a network_http_get as a proxy next release).
httpbin for Atari (left) and Apple2 (right)
Current httpbin for Atari
Current httpbin for Apple2
The new FujiNet-PC (aka virtual fujinet) has been integrated into AppleWin a popular Apple2 emulation app for Windows (runs in Linux and OSX via wine). This is a huge step forward for Apple2 FujiNet develpment- now developers can work on FN apps without having any physical hardware. The AppleWin app recognizes a SLIP device in a slot, and the SLIP device connects to the FujiNet-PC running on the system. They transport the SmartPort packets over SLIP between AppleWin and FujiNet.
It was a close collaboration between OliverS and Mark (fenrock) in discord….
fenrock: I’m pretty close on finishing the AppleWin SP over Slip though on FujiNet-PC and AppleWin sides. Getting and replying to requests. Just debugging a few things.fenrock: First Device Count request! IWM FujiNet based on SmartportSD v1.15 Attempting connection to 127.0.0.1:1985 Connected to target 20:55:58.724587 > SPI configured for smartport I/O IWM GPIO configured Request data: 0000 00 00 00 00
fenrock: there’s tons in there that I feel can be reworked to SLIP only, but I won’t touch it now, just getting enough until everything is in one code base as I see @apc is busy in this area too, so don’t want anyone having a merge hell
Oliver Schmidt: Exactly! When (and only when) both SP-over-SLIP is established and the FN-PC merge is done, we should have a close look and refactor the IWM stuff in a way that makes sense for both the existing CBus code and the new SP-over-SLIP code!
AppleWin running and enumerating the SmartPort devices via FujiNet-PC – over SLIP
AppleWin was forked and the enhancements to make it work with SLIP are in the FujiNet Project:
Info about the Serial Line Internet Protocol
That wraps up this January RAPID. I’m trying to keep these short and concise, which is hard given the amount of work and collaboration going on in the Discord. If any of this interests you we are always looking for help in any way- coding, testing, building, documenting- consider hopping onto the Discord and just say hello.
A table of Happy Apples