SchemaHD vs SDK85

FPGAs can dynamically generate logic circuits by means of configuration bit streams generated by languages such as Verilog and VHDL. The generated logic circuit cannot be changed by communication data. Therefore, it is very safe and cannot be attacked by hacking, which is a problem with CPUs, to execute arbitrary commands. In addition, the generated logic circuits are all running simultaneously, so the highest performance parallel processing is being performed. It can also generate logic circuits using configuration bitstreams at very high speed. Most of the processing that can be done by the CPU can be done by the FPGA alone. With advanced security and the highest performace, FPGAs are the perfect device for the modern age. However, it takes a lot of effort to learn languages such as Verilog and VHDL. There are other methods such as high-level synthesis from C/C++, but they require a lot of adjustments such as #pragma, and do not maximize the capabilities of the FPGA. Schematics, not programming languages, are needed to maximize the capabilities of FPGAs and to further improve developer productivity. Schematics allow you to grasp the whole picture at a glance, and can perfectly represent parallel processing. SchemaHD is to draw a circuit diagram of a logic circuit, and it's possible to do generation of Verilog HDL and a simulation. A made circuit diagram can be used by a different circuit diagram immediately. You can also install wiring easily by touch operation. A concept of interface is adopted as a terminal, so something structured of a AXI bus can also be used. A terminal it's also possible to distinguish sound argument reason, negative logic and characteristic wiring of a clock and a reset by interface, and which is different in interface, they don't seem able to connect, it is. You can input and output as a JSON file, so the made circuit diagram and interface are also capable of cooperation with other application. Verilog HDL generated from a circuit diagram contains a comment of a terminal name and an instance name, so it's capable of the correspondence which is at the time of problem occurrence. A network connection isn't needed, so it's also effective in information leak prevention. A simple simulation is offered in the present, but it's expected to enhance it early.

An emulator of the SDK-85 System Design Kit issued by Intel in the mid-seventies. The kit featured an 8085 micro processor, some basic IO chips, and a UI comprised of a hexpad and a six-digit seven-segment display. There was also a ROM plugged onto the board which contained a monitor program to enter and execute machine code on the 8085. The app emulates an 8085 and executes the monitor (shippment granted by Intel as long as the app is free and educational). The original kit leveraged the serial IO pins of the 8085 to connect a TTY as a somewhat more comfortable alternative to the hexpad/ display UI used by the monitor on startup. A wipe-left gesture shifts in a simple terminal and the monitor switches to TTY mode. To use the app one needs to get a copy of the original SDK-85 System Design Kit User‘s Manual (ask Google) and work it thru. Some knowledge of the 8085 and its instruction set is helpful as well, and being a boomer nerd who loved to program micro computers when young (and still does) is key. Intel designed the monitor to run in a loop that keeps the CPU constantly busy (on a single thread). To prevent the battery from draining the app suspends executing after 15 seconds indicated by a slightly blurred display. Tapping the centered play-pause button resumes the monitor or any other program in execution. Timeout and a few other options can be changed in the app‘s entry in Settings.