NEC V60

From Wikipedia, the free encyclopedia
(Redirected from NEC V80)
Jump to navigation Jump to search
NEC V60 / V70 / V80 / AFPP
File:NEC V60 die.jpg
Die shot of NEC V60 microprocessor
Name "V60 D70616" in bottom center
General information
LaunchedV60: 1986
V70: 1987
V80: 1989
AFPP: 1989
Common manufacturer
Performance
Max. CPU clock rateV60: 16 MHz
V70: 20/25 MHz
V80: 25/33 MHz
AFPP: 20  MHz
Data widthV60: 16 (int. 32)
V70: 32
V80: 32
Address widthV60: 24 (int. 32)
V70: 32
V80: 32
Virtual address width32 Linear[1]
Cache
L1 cacheV80: 1K/1K
Architecture and classification
ApplicationEmbedded systems,
minicomputers,
arcade games
Technology nodeV60: 1.5/1.2 μm
V70: 1.5/1.2 μm
V80: 0.8 μm
AFPP: 1.2 μm
Microarchitecture"V60/V70", "V80"
Instruction setNEC V60-V80[1]
Extensions
  • V80: atomic
Number of instructionsV60/V70: 119
V80: 123
Physical specifications
Transistors
  • V60: 375K
    V70: 385K
    V80: 980K
    AFPP: 433K
Co-processorAFPP (μPD72691)
Packages
  • V60: 68-pin PGA
    V60: 120-pin QFP
  • V70: 132-pin PGA
  • V70: 208-pin QFP
  • V80: 280-pin PGA
  • AFPP: 68-pin PGA
Products, models, variants
Product code names
  • μPD70616R-16
  • μPD70615GD-16
  • μPD70632R-20
  • μPD70632R-25
  • μPD70632GD-20
  • μPD70832R-25
  • μPD70832R-33
  • μPD72691R-20
History
PredecessorV20-V50
SuccessorV800 Series

The NEC V60[1][2] is a CISC microprocessor manufactured by NEC starting in 1986. Several improved versions were introduced with the same instruction set architecture (ISA), the V70 in 1987, and the V80 and AFPP in 1989. They were succeeded[3] by the V800 product families, which is currently produced by Renesas Electronics.

The V60 family includes a floating-point unit[4] (FPU) and memory management unit (MMU) and real-time operating system (RTOS) support for both Unix-based user-application-oriented systems[5] and ITRON–based hardware-control-oriented embedded systems. They can be used in a multi-cpu lockstep fault-tolerant mechanism named FRM. Development tools included Ada certified system MV-4000, and an in-circuit emulator (ICE).

The V60/V70/V80's applications covered a wide area, including circuit switching telephone exchanges, minicomputers, aerospace guidance systems,[6] word processors, industrial computers, and various arcade games.

Introduction

[edit | edit source]

NEC V60[2][1] is a CISC[7] processor manufactured by NEC starting in 1986.[8] It was the first 32-bit general-purpose microprocessor commercially available in Japan.[9]

Based on a relatively traditional design for the period,[10][11][12][13][14] the V60 was a radical departure from NEC's previous, 16-bit V–series processor, the V20-V50,[15] which were based on the Intel 8086 model,[7] although the V60 had the ability to emulate the V20/V30.[1]: §10 

According to NEC's documentation, this computer architectural change was due to the increasing demands for, and the diversity of, high-level programming languages. Such trends called for a processor with both improved performance, achieved by doubling the bus width to 32 bits, and with greater flexibility facilitated by having a large number of general-purpose registers.[2][1] These were common features of RISC chips.[16] At the time, a transition from CISC to RISC seemed to bring many benefits for emerging markets.

Today, RISC chips are common, and CISC designs—such as Intel's x86 and the 80486—which have been mainstream for several decades, internally adopt RISC features in their microarchitectures.[17][18] According to Pat Gelsinger, binary backward compatibility for legacy software is more important than changing the ISA.[19]

Overview

[edit | edit source]

Instruction set

[edit | edit source]

The V60 (a.k.a. μPD70616) retained a CISC architecture.[20] Its manual describes their architecture as having "features of high-end mainframe and supercomputers", with a fully orthogonal instruction set that includes non-uniform-length instructions, memory-to-memory operations that include string manipulation, and complex operand-addressing schemes.[1][2][16]

Family

[edit | edit source]

The V60 operates as a 32-bit processor internally, while externally providing 16-bit data, and 24-bit address, buses. In addition, the V60 has 32 32-bit general-purpose registers.[1]: §1  Its basic architecture is used in several variants. The V70 (μPD70632), released in 1987, provides 32-bit external buses. Launched in 1989, the V80 (μPD70832)[21] is the culmination of the series: having on-chip caches, a branch predictor, and less reliance on microcode for complex operations.[22]

Software

[edit | edit source]

The operating systems developed for the V60-V80 series are generally oriented toward real-time operations. Several OSs were ported to the series, including real-time versions of Unix and ITRON.[23][24]

Because the V60/V70 was used in various Japanese arcade games, their instruction set architecture is emulated in the MAME CPU simulator.[25] The latest open-source code is available from the GitHub repository.[26]

FRM

[edit | edit source]

All three processors have the FRM (Functional Redundancy Monitoring) synchronous multiple modular lockstep mechanism, which enables fault-tolerant computer systems. It requires multiple devices of the same model, one of which then operates in "master mode", while the other devices listen to the master device, in "checker mode". If two or more devices simultaneously output different results via their "fault output" pins, a majority-voting decision can be taken by external circuits. In addition, a recovery method for the mismatched instruction—either "roll-back by retry" or "roll-forward by exception"—can be selected via an external pin.[27][28][1]: §11 [21][29][30]: §3–229, 266 

Pin Name I/O Function
BMODE (FRM) Input Select the normal bus (master) mode or FRM operating (checker) mode
BLOCK (MSMAT) Output Master output requesting bus lock, i.e. freezing bus operation
Checker output indicating a mismatch has been detected
BFREZ Input Assertion for freezing bus operation
RT/EP Input Selecting input for "roll-back by retry" or "roll-forward by exception"

V60

[edit | edit source]

The work on V60 processor began in 1982 with about 250 engineers under the leadership of Yoichi Yano,[31] and the processor debuted in February 1986.[32] It had a six-stage pipeline, built-in memory-management unit, and floating-point arithmetic. It was manufactured using a two-layer aluminum CMOS process technology, under a 1.5 μm design rule, to implement 375,000 transistors on a 13.9 × 13.8 mm2 die.[8][33] It operates at 5 V and was initially packaged in a 68-pin PGA.[34] The first version ran at 16 MHz and attained 3.5 MIPS.[33] Its sample price at launch was set at ¥100,000 ($588.23). It entered full-scale production in August 1986.[33]

File:VR Virtua Racing.jpg
Sega Virtua Racing based on Sega Model 1
(External Link)

Sega employed this processor for most of its arcade game sets in the 1990s; both the Sega System 32 and the Sega Model 1 architectures used V60 as their main CPU. (The latter used the lower-cost μPD70615 variant,[35] which doesn't implement V20/V30 emulation and FRM.[36][37]) The V60 was also used as the main CPU in the SSV arcade architecture—so named because it was developed jointly by Seta, Sammy, and Visco.[38] Sega originally considered using a 16 MHz V60 as the basis for its Sega Saturn console; but after receiving word that the PlayStation employed a 33.8 MHz MIPS R3000A processor, instead chose the dual-SH-2 design for the production model.[39]

In 1988, NEC released a kit called PS98-145-HMW[40] for Unix enthusiasts. The kit contained a V60 processor board that could be plugged into selected models of the PC-9800 computer series and a distribution of their UNIX System V port, the PC-UX/V Rel 2.0 (V60), on 15 8-inch floppy disks. The suggested retail price for this kit was 450,000 Yen.[40] NEC-group companies themselves intensively employed the V60 processor. Their telephone circuit switcher (exchange), which was one of the first intended targets, used V60. In 1991, they expanded their word processor products line with Bungou Mini (文豪ミニ in Japanese) series 5SX, 7SX, and 7SD, which used the V60 for fast outline font processing, while the main system processor was a 16 MHz NEC V33.[41][42] In addition, V60 microcode variants were employed in NEC's MS-4100 minicomputer series, which was the fastest one in Japan at that time.[43][44][45]

V70

[edit | edit source]
File:UPD70632GD-20 V70 01.JPG
V70 (μPD70632GD-20) in QFP packaging, mounted on Jaleco Mega System32 PWB

The V70 (μPD70632) improved on the V60 by increasing the external buses to 32 bits, equal to the internal buses. It was also manufactured in 1.5 μm with a two-metal layer process. Its 14.35 × 14.24 mm2 die had 385,000 transistors and was packaged in a 132-pin ceramic PGA. Its MMU had support for demand paging. Its floating-point unit was IEEE 754 compliant.[29] The 20 MHz version attained a peak performance of 6.6 MIPS and was priced, at launch in August 1987, at ¥100,000 ($719.42). The initial production capacity was 20,000 units per month.[46] A later report describes it as fabricated in 1.2-micrometer CMOS on a 12.23 × 12.32 mm2 die.[21] The V70 had a two-cycle non-pipeline (T1-T2) external bus system, whereas that of the V60 operated at 3 or 4 cycles (T1-T3/T4).[21][2] Of course, the internal units were pipelined.

The V70 was used by Sega in its System Multi 32[47] and by Jaleco in its Mega System 32. (See the photo of the V70 mounted on the latter system's printed circuit board.)[48]

File:H-IIA F17 launching AKATSUKI.jpg
Liftoff of H-IIA Flight 17, part of whose payload was the Akatsuki spacecraft (Venus Climate Orbiter)

JAXA embedded its variant of the V70, with the ITRON RX616 operating system, in the Guidance Control Computer of the H-IIA carrier rockets, in satellites such as the Akatsuki (Venus Climate Orbiter), and the Kibo International Space Station (ISS) module.[6][49][50] The H-IIA launch vehicles were deployed domestically, in Japan, although their payloads included satellites from foreign countries. As described in JAXA's LSI (MPU/ASIC) roadmap, this V70 variant is designated "32bit MPU (H32/V70)", whose development, probably including the testing (QT) phase, was "from the middle of 1980s to early 1990s".[51]: 9 [52] This variant was used until its replacement, in 2013, by the HR5000 64-bit, 25 MHz microprocessor, which is based on the MIPS64-5Kf architecture,[53] fabricated by HIREC, whose development was completed around 2011.[54][55][56]

"Space Environment Data Acquisition" for the V70 was done at the Kibo-ISS exposed facility.

Item Part No. SEE (Single Event Effect)
Monitored Item 		Result[57]
V70-MPU NASDA
38510/92101xz		 SEU (Single Event Upset)
SEL (Single Event Latch-up)		 Not observed
(—2010/9/30)

V80

[edit | edit source]

The V80 (μPD70832)[21] was launched in the spring of 1989. By incorporating on-chip caches and a branch predictor, it was declared NEC's 486 by Computer Business Review.[58][59] The performance of the V80 was two to four times than that of the V70, depending on application. For example, compared with V70, the V80 had a 32-bit hardware multiplier that reduced the number of cycles required to complete an integer-multiplication machine-instruction from 23 to 9. (For more detailed differences, see the hardware architecture section below.) The V80 was manufactured in a 0.8-micrometer CMOS process on a die area of 14.49 × 15.47 mm2, implementing 980,000 transistors. It was packaged in a 280-pin PGA, and operated at 25 and 33 MHz with claimed peak performances of 12.5 and 16.5 MIPS, respectively. The V80 had separate 1 KB on-die caches for both instructions and data. It had a 64-entry branch predictor, a 5% performance gain being attributed to it. The launch prices of the V80 were cited as equivalent to $1200 for the 33 MHz model and $960 for the 25 MHz model. Supposedly, a 45 MHz model was scheduled for 1990,[59] but it did not materialize.

The V80, with μPD72691 co-FPP and μPD71101 simple peripheral chips, was used for an industrial computer running the RX-UX832 real-time UNIX operating system and a X11-R4-based windowing system.[60][61]

AFPP (co-FPP)

[edit | edit source]

The Advanced Floating Point Processor (AFPP) (μPD72691) is a co-processor for floating-point arithmetic operations.[62] The V60/V70/V80 themselves can perform floating-point arithmetic, but they are very slow because they lack hardware dedicated to such operations. In 1989, to compensate V60/V70/V80 for their fairly weak floating-point performance, NEC launched this 80-bit floating-point co-processor for 32-bit single precision, 64-bit double precision, and 80-bit extended precision operations according to IEEE 754 specifications.[4][21] This chip had a performance of 6.7 MFLOPS, doing vector-matrix multiplication while operating at 20 MHz. It was fabricated using a 1.2-micrometer double-metal layer CMOS process, resulting in 433,000 transistors on an 11.6 × 14.9 mm2 die.[4] It was packaged in a 68-pin PGA. This co-processor connected to a V80 via a dedicated bus, to a V60 or V70 via a shared main bus, which constrained peak performance.[21]

Hardware architecture

[edit | edit source]

The V60/V70/V80 shared a basic architecture. They had thirty-two 32-bit general-purpose registers, with the last three of them commonly used as stack pointer, frame pointer, and argument pointer, which well matched high level language compilers' calling conventions.[29][63] The V60 and V70 have 119 machine instructions,[29] with that number being extended slightly to 123 instructions for the V80. The instructions are of non-uniform length, between one and 22 bytes,[1] and take two operands, both of which can be addresses in main memory.[21] After studying the V60's reference manual, Paul Vixie described it as "a very VAX-ish arch, with a V20/V30 emulation mode (which[...] means it can run Intel 8086/8088 software)".[64]

The V60–V80 has a built-in memory management unit (MMU)[8][62] that divides a 4-GB virtual address space into four 1-GB sections, each section being further divided into 1,024 1-MB areas, and each area being composed of 256 4-KB pages. On the V60/V70, four registers (ATBR0 to ATBR3) store section pointers, but the "area tables entries" (ATE) and page tables entries (PTE) are stored in off-chip RAM. The V80 merged the ATE and ATBR registers—which are both on-chip, with only the PTE entries stored in external RAM—allowing for faster execution of translation lookaside buffer (TLB) misses by eliminating one memory read.[21]

The translation lookaside buffers on the V60/70 are 16-entry fully associative with replacement done by microcode. The V80, in contrast, has a 64-entry 2-way set associative TLB with replacement done in hardware. TLB replacement took 58 cycles in the V70 and disrupted the pipelined execution of other instructions. On the V80, a TLB replacement takes only 6 or 11 cycles depending on whether the page is in the same area; pipeline disruption no longer occurs in the V80 because of the separate TLB replacement hardware unit, which operates in parallel with the rest of the processor.[21]

All three processors use the same protection mechanism, with 4 protection levels set via a program status word, Ring 0 being the privileged level that could access a special set of registers on the processors.[21]

All three models support a triple-mode redundancy configuration with three CPUs used in a byzantine fault–tolerance scheme with bus freeze, instruction retry, and chip replacement signals.[21][28] The V80 added parity signals to its data and address buses.[21]

String operations were implemented in microcode in the V60/V70; but these were aided by a hardware data control unit, running at full bus speed, in the V80. This made string operations about five times faster in the V80 than in the V60/V70.[21]

All floating-point operations are largely implemented in microcode across the processor family and are thus fairly slow. On the V60/V70, the 32-bit floating-point operations take 120/116/137 cycles for addition/multiplication/division, while the corresponding 64-bit floating-point operations take 178/270/590 cycles. The V80 has some limited hardware assist for phases of floating-point operations—e.g. decomposition into sign, exponent, and mantissa—thus its floating-point unit was claimed to be up to three times as effective as that of the V70, with 32-bit floating-point operations taking 36/44/74 cycles and 64-bit operations taking 75/110/533 cycles (addition/multiplication/division).[21]

Operating systems

[edit | edit source]

Unix (non-real-time and real-time)

[edit | edit source]

NEC ported several variants of the Unix operating system to its V60/V70/V80 processors for user-application-oriented systems, including real-time ones. The first flavor of NEC's UNIX System V port for V60 was called PC-UX/V Rel 2.0 (V60).[65] (Also refer to external link photos below.) NEC developed a Unix variant with a focus on real-time operation to run on V60/V70/V80. Called Real-time UNIX RX-UX 832, it has a double-layered kernel structure, with all task scheduling handled by the real-time kernel.[5] A multiprocessor version of RX-UX 832 was also developed, named MUSTARD (Multiprocessor Unix for Embedded Real-Time Systems).[66] The MUSTARD-powered computer prototype uses eight V70 processors. It utilizes FRM function, and can configure and change the configuration of master and checker upon request.[67][68]

ITRON (real-time)

[edit | edit source]

For hardware-control-oriented embedded systems, the ITRON-based real-time operating system, named RX616, was implemented by NEC for the V60/V70.[27][23] The 32-bit RX616 was a continuous fork from the 16-bit RX116, which was for the V20-V50.[46][24]

FlexOS (real-time)

[edit | edit source]

In 1987, Digital Research, Inc. also announced that they were planning on porting FlexOS to the V60 and V70.[69]

CP/M and MS-DOS (legacy 16-bit)

[edit | edit source]

The V60 can also run CP/M and MS-DOS programs (ported from the V20-V50 series) using V20/V30 emulation mode.[33] According to a 1991 article in InfoWorld, Digital Research was working on a version of Concurrent DOS for the V60 at some point; but this was never released, as the V60/V70 processors were not imported to the US for use in IBM PC compatibles.[70]

Development tools

[edit | edit source]

C/C++ cross-compilers

[edit | edit source]

As part of its development tool kit and integrated development environment (IDE), NEC had its own C-compiler, the PKG70616 "Software Generation tool package for V60/V70".[71] In addition, GHS (Green Hills Software) made its native mode C compiler (MULTI), and MetaWare, Inc. (currently Synopsys, via ARC International) made one, for V20/V30 (Intel 8086), emulation mode, called High C/C++.[72][18]: acknowledgement  Cygnus Solutions (currently Red Hat) also ported GCC as a part of an enhanced GNU compiler system (EGCS) fork,[73] but it seems not to be public.[74][75]

As of 2018, the processor-specific directory necv70 is still kept alive in the newlib C-language libraries (libc.a and libm.a) by RedHat.[76] Recent maintenance seems to be done on Sourceware.org. The latest source code is available from its git repository.[77]

MV-4100 Ada 83–certified system

[edit | edit source]

The Ada 83–certified "platform system" was named MV-4000, certified as "MV4000". This certification was done with a target system, that utilized the real-time UNIX RX-UX 832 OS running on a VMEbus (IEEE 1014)–based system with a V70 processor board plugged in. The host of the cross compiler was an NEC Engineering Work Station EWS 4800, whose host OS, EWS-US/V, was also UNIX System V–based.[78][79][80][81]

The processor received Ada-83 validation from AETECH, Inc.,[78] running the Ada Compiler Validation Capability tests.[82]

System Name Certificate Number Compiler Type HOST Machine HOST OS TARGET Machine TARGET OS
NEC Ada Compiler System for EWS-UX/V to V70/RX-UX832, Version 1.0 910918S1.11217 Base NEC EWS4800/60 EWS-UX/V R8.1 NEC MV4000 RX-UX832 V1.6
NEC Ada Compiler System for EWS-UX/V(Release 4.0) to V70/RX-UX832 Version Release 4.1 (4.6.4) 910918S1.11217 Derived EWS4800 Superstation RISC Series EWS-UX/V(R4.0) R6.2 NEC MV4000 RX-UX832 V1.63
MV-4000 Features[79]
System bus: IEEE1014 D1.2/IEC821 Rev C.1 (8-slot)
Expansion bus: IEC822 Rev C or V70 cache bus (6-slot)
Built-in 100M byte (formatted) 3.5-inch SCSI hard disk
Built-in 1M-byte 3.5-inch floppy disk drive 1
Expansion SCSI (1 ch)
EMI evaluation: VCCI - 1 kind

Evaluation board kits

[edit | edit source]

NEC released some plug-in evaluation board kits for the V60/V70.

Parts No. Descriptions Remarks
EBIBM-7061UNX V60 coprocessor slave board with Unix for PC-XT/AT w/ PC-UX/V Rel 2.0 (V60)
PS98-145-HMW V60 coprocessor slave board with Unix for NEC PC-9801 w/ PC-UX/V Rel 2.0 (V60)
EBIBM-70616SBC V60 single board computer for Multibus I
A part of MV-4000 V70 single board computer for VMEbus Ada 83 certified

In-circuit emulator

[edit | edit source]

On-chip software debug support with the IE-V60

[edit | edit source]

NEC based its own full (non-ROM and non-JTAG) probe-based in-circuit emulator, the IE-V60, on the V60, because V60/V70 chips themselves had emulator-chip capabilities. The IE-V60 was the first in-circuit emulator for V60 that was manufactured by NEC. It also had a PROM programmer function.Section 9.4, p. 205[2] NEC described it as a "user friendly software debug function". The chips have various trapping exceptions, such as data read (or write) to the user specified address, and 2 break-points simultaneously.Section 9[1]

External bus status pins

[edit | edit source]

The external bus system indicates its bus status using 3 status pins, which provide three bits to signal such conditions as first instruction fetch after branch, continuous instruction fetch, TLB data access, single data access, and sequential data access. Section 6.1, p. 114 [2]

ST[2:0] Description
111 Instruction fetch
011 Instruction fetch after branch
101 "TLB" data access
100 "System base (interrupt & exception vector) table" data access
011 Single data access
010 Short-path data access (Skipped address by read-after-write)
001 Sequential data access

Debugging with V80

[edit | edit source]

These software and hardware debugging functions were also built into the V80. However, the V80 did not have an in-circuit emulator, possibly because the presence of such software as real-time UNIX RX-UX 832 and real-time ITRON RX616 rendered such a function unnecessary. Once Unix boots up, there is no need for an in-circuit emulator for developing either device drivers or application software. What is needed is a C compiler, a cross compiler, and a screen debugger—such as GDB-Tk—that works with the target device,.

HP 64758

[edit | edit source]

Hewlett-Packard (currently Keysight) offered probing-pod-based in-circuit emulation hardware for the V70, built on their HP 64700 Series systems,[83][84] the successor to the HP 64000 Series, specifically the HP 64758.[85][86][83] It enables trace function like a logic analyzer. This test equipment also displays disassembled source code automatically, with trace data display and without an object file,[83] and displays high-level language source code when the source code and the object files are provided and they were compiled in DWARF format. An interface for the V60 (10339G) was also in the catalog,[86] but the long probing-pod cable required "special grade qualified" devices, i.e. the high-speed grade V70.

HP 64758: Main units, sub-units, and hosted interface

Product Description
64758A V70 20 MHz Emulator with 512KB of emulation memory
64758AX One-Time-Update
64758B V70 20MHZ Emulator with 1MB of emulation memory
64758G V70 20 MHz Emulation Subsystem, 512KB
64758H V70 20 MHz Emulation Subsystem, 1MB
64758S V70 (uPD70632)–hosted User Interface

Software options

Product Description
64879L V70 Assembler/Linker, Single-user License
64879M V70 Assembler/Linker, Media & Manuals
64879U V70 Assembler/Linker Multi-user license

Hardware options

Product Description
B3068B V70-Hosted Graphical User Interface
10339G NEC V60 Interface
E2407A NEC V70 Interface

Failings

[edit | edit source]

Strategic failure of the V80 microarchitecture

[edit | edit source]

In its development phase, the V80 was thought to have the same performance as the Intel 80486,[87] but they ended up having many different features. The internal execution for each instruction of the V80 needed at least two cycles, while that of i486 required one. The internal pipeline of the V80 seemed buffered asynchronous, but that of i486 was synchronous. In other words, the internal microarchitecture of V80 was CISC, but that of i486 was RISC. Both of their ISAs allowed long non-uniform CISC instructions, but the i486 had a wider, 128-bit internal cache memory bus, while that of V80 had a 32-bit width. This difference can be seen on their die photos.[21][18][22][17] The design was fatal from the performance point of view, but NEC did not change it. NEC might have been able to redesign the physical design, with the same register-transfer level, but it did not.

Lack of commercial success

[edit | edit source]

The V60-V80 architecture did not enjoy much commercial success.[32]

The V60, V70, and V80 were listed in the 1989 and 1990 NEC catalogs in their PGA packaging.[88][89] A NEC catalog from 1995 still listed the V60 and V70 (not only in their PGA version but also in a QFP packaging, and also included a low-cost variant of the V60 named μPD70615, which eliminated V20/V30 emulation and FRM function), alongside their assorted chipsets; but the V80 was not offered in this catalog.[36] The 1999 edition of the same catalog no longer had any V60-V80 products.[90]

Successors

[edit | edit source]

The V800 series

[edit | edit source]

In 1992, NEC launched a new model, the V800 Series 32-bit microcontroller; but it did not have a memory management unit (MMU).[91] It had a RISC-based architecture, inspired by the Intel i960 and MIPS architectures, and other RISC processor instructions, such as JARL (Jump and Register Link) and load–store architecture.

At this time, the enormous software assets of the V60/V70, such as real-time Unix, were abandoned and never returned to their successors, a scenario Intel avoided.

The V800 Series had 3 major variants, the V810, V830, and V850 families.[92][3][93]

The V820 (μPD70742) was a simple variant of the V810 (μPD70732), but with peripherals.

The designation V840 may have been skipped as a designation because of Japanese tetraphobia (see page 58[36]). One Japanese pronunciation of "4" means "death", thus avoid names evoking such as Death-watch Shi-ban (the number 4 – Shi-ban) Bug (死番虫, precisely "deathwatch beetle").

As of 2005, it was already the V850 era, and the V850 family has been enjoying great success.[94] As of 2018, it is called the Renesas V850 family and the RH850 family, with V850/V850E1/V850E2 and V850E2/V850E3 CPU cores, respectively. Those CPU cores have extended the ISA of the original V810 core;[95] running with the V850 compiler.[96]

Modern software-based simulation

[edit | edit source]

MAME

[edit | edit source]

Because the V60/V70 had been used for many Japanese arcade games, MAME (for "Multiple Arcade Machine Emulator"), which emulates multiple old arcade games for enthusiasts, includes an CPU simulator for their instruction set architecture.[25] It is a kind of an instruction set simulator, not for developers but for users.

It has been maintained by the MAME development team. The latest open-source code, written in C++, is available from the GitHub repository.[97] The operation codes in the file optable.hxx are exactly the same as those of the V60.[1]

See also

[edit | edit source]

References

[edit | edit source]
  1. ^ a b c d e f g h i j k l Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  2. ^ a b c d e f g Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  3. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  4. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  5. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  6. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  7. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value). Google Books
  8. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  9. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  10. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  11. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  12. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  13. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  14. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  15. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  16. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  17. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  18. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  19. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  20. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  21. ^ a b c d e f g h i j k l m n o p Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  22. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  23. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  24. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  25. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  26. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  27. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  28. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  29. ^ a b c d Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  30. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  31. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  32. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  33. ^ a b c d Dataquest, "Japanese Semiconductor Industry Service", 1st Quarter 1986, p. 18 (pdf p. 44 in this multi-volume archive)
  34. ^ Dataquest, "Japanese Semiconductor Industry Service", 1st Quarter 1987, p. 18 (pdf p. 182 in this multi-volume archive)
  35. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  36. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  37. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  38. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  39. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  40. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  41. ^ Bungou Mini 5RX on YouTube with "high speed outline font smoothing" TV CM
  42. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  43. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  44. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  45. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  46. ^ a b Dataquest, "Japanese Semiconductor Industry Service", 2nd Quarter 1987, p. 21 (pdf p. 223 in this multi-volume archive)
  47. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  48. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  49. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  50. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  51. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  52. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  53. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  54. ^ HAYASHI, N. Guidance Control Computer for Launch Vehicle, NEC Technical Journal, Vol. 6, No. 1/2001, pp. 145-148
  55. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  56. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  57. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  58. ^ NEC LAUNCHES V80 ANSWER TO INTEL's 80486 - Computer Business Review, 1989-03-15 Balcklist:www.cbronline.com/news/nec_launches_v80_answer_to_intels_80486
  59. ^ a b NEC MAY HAVE THE EDGE WITH ITS 930,000 TRANSISTOR V80 ANSWER TO INTEL'S 80486 - Computer Business Review, 1989-04-06 Balcklist:www.cbronline.com/news/nec_may_have_the_edge_with_its_930000_transistor_v80_answer_to_intels_80486
  60. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  61. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  62. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  63. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  64. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  65. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  66. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  67. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  68. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  69. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  70. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  71. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  72. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  73. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  74. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  75. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  76. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  77. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  78. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  79. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  80. ^ History-of-48series Archived 2016-03-03 at the Wayback Machine (refers to the EWS 4800 NEC computers)
  81. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  82. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  83. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  84. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  85. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  86. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  87. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  88. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  89. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  90. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  91. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  92. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  93. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  94. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  95. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  96. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  97. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).

Further reading

[edit | edit source]
  • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
[edit | edit source]
Retrieved from "http://70.231.62.181/index.php?title=NEC_V60&oldid=6991176#V80"