Made several changes to the previous prototype V1.3 design, and now have another set of sample boards for testing being manufactured by JLCPCB - scheduled to arrive around the end of this week. BTW, the SD card issue I was seeing from day one, has been solved, and came down to human error as well as an incompatible SD card.

What's Changed?

The Cassette Motor Control line has now been buffered and switched out of circuit when FujiNet is powered OFF, and the SD Card Detect Switch is now being sensed by IO12 on the ESP32, and will eventually see future support in the firmware (Now Implemented in firmware version 0.5.879c407c).

This will be my last prototype, with the design already proven out by previously modding a V1.3 board. However I simply couldn't resist putting a bit of polish on the process, and doing one last board run with all the V1.5 changes in place. I also need a few boards for others to test so as to prove out the design, so having boards that incorporated all the changes was a prerequisite.

This time around I also wanted to properly pay homage to AtariAge members Mr Robot and mozzwald. Mr Robot deserving a call out for sourcing the switches, SD socket, and LED holders. And for the direction I got from his excellent PCB layouts that came before. And of course a big acknowledgement also goes to mozzwald the creator of the hardware design being used in the standard Atari FujiNet devices, which served as both my guide and inspiration. And a shout out to the rest of the FujiNet team for a wonderful game changing innovation known simply as FujiNet (visit FujiNet.online)

So the intention is to get a few of these out to the 576NUC+ Beta Test and Development Team, and let them run it through the ringer in order to shake out any bugs. Assuming that all goes well with that, then Mr Robot will take back the reins and proceed with the final production designs. There will be more to it then just FujiNet, so keep a look out for any posts he makes concerning that.

This new SIO interface circuit which is being proven out in this final V1.5 design, has been released into the public domain, and it is hoped that it'll see future use in other FujiNet related projects.

- Michael

In all cases, pressing control in combination with the arrow keys will temporarily reverse the present mode. So if you press CTRL+Arrows when in the normal 'PS/2 mode', that will produce symbols instead of cursor movement. Whereas if in 'Atari mode', will result in moving the cursor, with symbols only being rendered when no control key is pressed in combination.

Using SHIFT in combination with the PS/2 arrow keys produces the same symbols as the stock Atari keyboard, no matter which arrow mode you are currently in. SHIFT+CTRL when pressed with the PS/2 arrow keys, will not produce a character but instead mimic the same key codes as produced by the stock Atari keyboard for this same combination of keys.

The Insert key when pressed by itself will insert space to the right of the cursor, and when pressed with SHIFT, will insert extra blank lines below the cursor.

The Delete key when pressed by itself will delete characters or space to the right of the cursor, and when pressed with SHIFT, will delete lines below the cursor.

Home when pressed with either SHIFT or CTRL will clear the screen and home the cursor to the upper left. When pressed alone, will invoke a 1200XL function of simply homing the cursor to the left on whatever line it was on without clearing the screen.

End will invoke a 1200XL function to move the cursor to the far left of whatever line it was on.

PgUp (Page-Up) will invoke a 1200XL function and move the cursor directly up to the top left of the screen.

PgDn (Page-Down) will invoke a 1200XL function and move the cursor to the bottom left of the screen.

Those last 4 special navigation keys (Home, End, PgUp, PgDn) can be very useful when utilized in an Atari program,  especially anything that requires the user to navigate a menu. For a good example, check out the customized SDrive Control Program or AtariAge member flashjazzcat's SIDE Loader and the Uno Cart contributions. Also FJC's The Last Word makes good use of these keys.

As FujiNet continues to mature, it would be nice to see more of these  special navigation keys play a roll in navigating the TNFS directories in a similar way to the examples given above.

- Michael

Because of changes that were required in the first prototype, and then getting a bit more inspiration from a recent DIY THT build project, I decided to create a new hybrid prototype that would allow either a ESP32 SMT module or ESP32 THT DEVKITC to be utilized.

Note: Although the silk screen shows a ESP32 part number with a '-IE' suffix, the cheaper version with an '-E' suffix can be substituted instead. The only difference is that the '-IE' version has both an IPEX and PCB antenna, whereas the '-E' only has a PCB antenna. Keep in mind that the one with the IPEX connector has this selected by default, and needs to be modded to use the PCB antenna instead by moving resistor R14 to the R15 position (refer to diagram - click to enlarge).

This board is currently being manufactured by JLCPCB in China, and has an expected completion date for this coming Monday.

When I get at least one board assembled and tested, I'll be sure to post the updated schematics, as well as my observations. So far I can tell you that it incorporates the same SIO interface as its predecessor, using a 74LS07 and a 74HCT4066. This new interface has been working very well, and appears to have solved the audio noise issues.

- Michael

Thanks to AtariAge member mozzwald (creator of the original FujiNet hardware), it was brought to my attention that pull-up resistors should be used on 3 of the 4 signal lines of the SD card. This article goes into more detail about that.

So today I added the resistors and once again held my breath and attempted to access the SD card on my FujiNet device - No dice still not working. It was wishful thinking that it would, but with other people's units working without pull-ups, I wasn't surprised. No matter, the pull-up resistors will still be added in my design.

Next I re-flowed the solder at the ESP32 connections, but that also failed to correct the situation. When probing the signal lines with a scope I saw no activity, and the CS line remained high, which is the normal idle state. It's almost like there's no one awake inside.

At this point I can only surmise that my ESP32 possibly has at least one I/O pin that is damaged. And since it's not easy to replace, I'll be looking at a 2nd build with a fresh board and new parts.

In the meantime I've been fine tuning the design, and moved it up to Version 1.2.

Another thing I discovered, was that the information I had gotten for my USB/Serial cable was incorrect, which was why I thought I needed to swap the RX and TX pins. So that's been restored to the way it was shown in the very first schematic, matching the prototype PCB that was based upon that.

Next I really didn't like where the ADC VREF voltage divider was getting its positive voltage from (SIO), so I moved it over to the regulated 3.3V bus... EDIT: I totally misunderstood the purpose of the voltage divider. In actuality it is being used to sense voltage coming from the Atari in order to determine if it's powered ON or OFF. The voltage divider simply brings the 5V of the Atari down to a level that's safe for the ESP32 to look at by one of its ADC inputs. So I have restored the original voltage divider in my schematic and renamed the wire label as VSENSE instead of VREF. The schematic download has been updated with this change.

I also decided to reduce the size of the programming header, as well as eliminate the SIO-Thru header and only pass along the PS/2 and power related signals via a 5-pin header. The PS/2 connections are present in case I wish to develop an active Wireless USB to PS/2 converter, which is something that is definitely on my wish list.

And for the final touch, the resistor array has been expanded to include the three SD related signals, thus actively pulling them up to 3.3V.

Hopefully the next time I write about this specific FujiNet prototype it will be to discuss the successful operation of the SD card.

- Michael

I ran into a few snags after assembling the first mostly THT NUC FujiNet prototype. The main problem off the start was that the 3.3V regulator was intended for a 5V input which didn't bode well with our diminished power supply due to the Schottky diodes that are inline with both the USB 5V and the 576NUC+ power. Specifically I wasn't seeing a high enough voltage feeding the ESP32 module as a result.

Once that problem got resolved by spec'ing a LDO (Low Drop-Out) voltage regulator. Then the only issue remaining was that the SD Card wasn't working, and in fact it still doesn't, but that will be pushed down the road until another day. However the network side of things works great as can be seen below. I was able to quickly log-in to my WiFi router, and then added a couple of existing TNFS server addresses, subsequently I was able to download a game via the internet and run it. It was quite fun and absolutely amazing all at the same time!

However the freshly assembled board did require a few more tweaks...

The series resistor for the SIO-Audio had to be increased from 470 ohms to 100K because the NUC already has a fairly high gain on that audio in port, making the SAM software speech synthesizer way too loud.

I also didn't like the look or the inconsistency of the first LEDs being used, and changed them all over to a diffused NTE version instead. Since these are very high efficiency, I was able to increase the current limiting resistors to 2K for all three of them, which matched the brightness of the dual green LED's on the NUC main board. What's also rather nice is that they all look the same when not lit, having a frosted white appearance, and best of all they are inexpensive at about 14 cents a piece.

During the initial firmware flashing I had discovered an error on which pin was designated as TX and which one was RX on the programming header. They need to be swapped. Luckily the programming cable I'm using broke out each wire independently making it easy to fix the issue, and get the ESP32 programmed (PL2303TA Cable Buy Link).

By the way, I also discovered that the program select header (PGM) was not needed, since the 'A' button works in its place.

Flashing Procedure for this Specific FujiNet Board

1. Turn OFF FujiNet power switch.
2. Connect USB/Serial cable between FujiNet and the computer.
3. Press and hold the 'A' button.
4. Turn ON the FujiNet power switch.
5. When you see both the white and blue LEDs light up release the 'A' button.
6. You are now ready to download the new firmware.
7. Start the FujiNet Flashing app, and after selecting the serial port associated with the cable, press the Flash FujiNet Firmware button and let it do it's thing (this takes a while).

And finally we get to the real reason I was so keen on redesigning the SIO to ESP32 interface circuit, and that has to do with a random but very noticeable noise experienced during certain sequences in shutdown and restart that has been observed in several versions of the FujiNet hardware. Disconnection of the SIO-audio input has been integrated into the new interface design in an attempt to minimize or eliminate the problem. So far the noise hasn't been seen in the initial tests of this new prototype. Or at least I haven't experienced the right conditions that will make it reveal itself (fingers crossed).

Now all I need to do is get that pesky SD card to work.

During my troubleshooting I did a continuity check of all the connections between the SD card socket and the ESP32, but so far everything looks correct. Although I haven't entirely ruled out operator error, as in my docs may not match up with reality concerning what pins do what on the socket. The datasheet for the SD card socket I'm using is really piss poor concerning the pin definitions.

That's it for now. I'll be sure to report back in when I solve the SD card problem.

- Michael

Well some like to say 3rd times a charm, but in my case it looks like the 4th run of boards is going to claim that prize.

The road traveled in this project was much longer than I had envisioned when I first started out, thinking this was going to be an easy and quick turn around. But as they say, all good things require time and hard work in order to accomplish, and that has certainly been the case here as well. We lost a few members of the Beta Team along the way. One because of my mishandling of what was expected, and the other because of personal issues. The drop-in FujiNet adapter board is still in the works, but I think that will get sorted out before the public release of this project. So all in all I think things have been going quite well.

And now for a look at the first assembled board straight out of the sample batch. Pretty much a 99.99% perfect fit for all of the components. Only had to leave out one By-Pass IC decoupling capacitor (lower right corner) which had a lead soldered too darn close to one of the SMT chips on the bottom side. Because of the lack of space to put it elsewhere, it will be removed from the design all together. Since the board has a good distribution of these capacitors, and being a 4-layer board with inner power planes, the loss of one decoupling capacitor is not seen as an issue.

On this go around, all SMT ICs have been resized to SOIC proportions, thus allowing for fairly easy, although skilled hand soldering. This was done not only for my sanity, but also as a prelude to public release of the PCB gerbers for DIY. Yeah you heard that right, I will be going back on what I said and release this to the public. However this is definitely a do it at your own risk, no guarantee proposition. So I better not hear a bunch of whining about people's boards not working after they've done the assembly, since I know the board design does work when assembled properly. If you don't posses expert level soldering skills, and prior SMT experience, please steer far away from taking on this project.

The production boards will be identical to what you see above, albeit missing the by-pass capacitor that had clearance issues. The version number will stay the same, since the sample boards will remain with the beta test group members, and the change is relatively minor. Oh and that improper bottom side board ID label will get corrected as well

The Gerber files, BOM, and various flashing files for the PICs, PLDs, and OS ROM will all be released to the public in approximately 2-3 months. However a couple of people that are opting to build and sell these boards in a fully assembled and tested state will get a head start on this aspect.

- Michael

The reality is that this board can only use the newest V2.5J firmware due to the lack of connection to 4 of the 6 key scan counter bits on the Pokey chip. For a better idea as to why these bits are not connected on this particular TK-II board version please check out the ARROW2JOY-XLD page for the details.

All other TK-II boards besides this one and the ARROW2JOY-XLD can use either the V2.4 or V2.5J firmware, depending upon what features you want to have. See the Manual for more info on those differences.

Edit: I just wanted to add that the PokeyMax FPGA based replacement product might not be 100% compatible with the V2.5J firmware. So until that issue is completely resolved, it would be better to stick to an original Pokey when only V2.5J firmware is a possibility. Despite what you may see elsewhere (eBay), NOS Pokey chips can still be purchased for $20 from BEST Electronics.

- Michael

Just checked the JLCPCB site today, and the good news is that the boards have completed the production phase and are now awaiting pick-up by DHL.

Based on previous boards that I've gotten from them in the past, the shipping should only take 2-3 days. So if all goes well I should see them arrive no later than this Friday. Then comes the most exciting part of assembling and testing at least one of each over the weekend.

- Michael

Mr Robot had been seeing a persistent although random noise occurrence during deactivation of the FujiNet. This combined with the fact that I nor the other members of the beta test team were able to deal with the very tiny SMT parts being used on the last iteration of the NUC-FujiNet board design, set me up with a new project. This project turned into a mission about making some SIO to ESP32-WROVER interface circuit changes that had been in discussion for quite some time, hopefully solving the audio noise issue, while also creating a board that even I could assemble.

The reason for another PCB run in lieu of doing a point to point wired breadboard for prototyping  and proving out the changes, was that in this day and age of cheap PCBs, bread-boarding is no longer the best way to prototype designs. And although this board looks all the part of a final PCB layout, it really isn't, and only serves to hopefully advance the FujiNet interface circuit, as well as give me and others something we can actually assemble by hand, while furthering our education on how the NUC and FujiNet need to play together in the best possible way.

Why the odd shape and the bigger than needed board?
This board was patterned after the previous board designed by Mr Robot that is meant to drop into the 576NUC+, lining up the switches, LEDs and such with the front and rear panels of the custom NUC enclosures he's designed. Mimicking that previous board footprint insured that it could be used in a similar enclosure if so desired, and gave me lots of room to layout the chips and traces for a very easy routing of the PCB.

What has fundamentally changed in the interface circuit design, is that all SIO signals are now disconnected from the WROVER module via the the ON/OFF switch SW1, including the SIO Audio-IN. Isolation of all the WROVER digital outputs are still handled via a 74LS07 open drain hex buffer which has been retained from the previous design. However for all the WROVER inputs as well as the Audio output, they now get their isolation via a 74HCT4066 quad analog switch having all the individual analog switch enables also coming from SW1. So in all cases the SIO signals get disconnected either through the 74LS07 or the 74HCT4066 chips when SW1 is placed in it's OFF position.

Wherever possible, thru-hole components were implemented, making for a more DIY friendly assembly. Exceptions: the WROVER solderable module was retained instead of opting for a break-out version, since a few of us beta testers already had these on hand. And the SMT SD socket was also kept, although it's relatively easy to solder. Finally because there wasn't an appropriate thru-hole replacement for the USB Serial Bridge chip (CP2102N-QFN24), I opted to go with an external FTDI (USB to Serial) cable connection to facilitate WROVER programming. An even cheaper option for this cable is to be found in the PL2303TA based cables that sell for very cheap on eBay, essentially rendering a similar USB to Serial function, assuming the Prolific driver is installed (already present in most Linux distributions).

As I write this blog entry, sample boards are currently being manufactured by JLCPCB in China, and should be arriving late next week. When that happens, one board will get assembled and tested with the hopes that the new ideas it encompasses will actually work as proposed. Whatever is learned will then be applied to a final version of Mr Robot's FujiNet board.

Exciting times ahead,
- Michael

TKNUC V1.4 Firmware

Today I'll cover a bit more about the special function 'hot' keys when using the PS/2 keyboard with the NUC.