Frequently Asked Questions

Q: Is Humble© real?

A: Yes.

Q: What is it?

A: Four short answers: 1 - It is a re-architecture of the 41 year old microprocessor & software operating system based personal computer. 2 - It is concurrent multiprocessing without conventional microprocessor and software. 3 - It is a new way to write software programs as hardware programs. 4 - It is an enabling technology.

Q: Can I license Humble© for resale?

A: Yes. See License Agreement and License Fee Schedule.

Q: Can I purchase boards directly from ECS?

A: Yes.

Q: Can I purchase complete ready to go systems directly from ECS?

A: No, not yet. Complete system sales are intended but not available as of this date. See Investor Opportunity.

Q: Can ECS merge my company's circuits together with Humble© for us?

A: Yes, but it depends much more as to the value of doing so for both companies . . . It may not make sense for one or the other or both companies. Contact ECS to discuss.

Q: Can I write and implement windowing programs and applications on (in) Humble©

A: Yes.

Q: Do I receive source code with a developers kit?

A: No and Yes. The whole of the design is made available as a black-box or as cores with an Application Program Interface (API). The intention is to allow others to use it, build on top of it (add to it) or subtract from it. This allows reuse and combining with any other intellectual property. So the intention is to license the core design to many customers for related and unrelated use. Access to a Library of components is also provided.

Q: Is the source an "open source"?

A: Yes and no. The initial Humble© motherboard is an "open" design (all manufacturing details are disclosed, BOM, gerbers, etc.), the main chip is "open", and the related compilers, languages and development tools are all wide "open" and have been for at least 15-20 years. Most would agree it can't be more wide open. The competition is substantial and many companies are better funded . . . Some initial protection is reasonable, wise and warranted. So the Humble© intention is to introduce the source as a protected core while everything else is wide open. So it's closed enough to protect the innovation, yet wide open making it tremendously useful. Consider Humble© has been in development for > 4 years and has consumed considerable expense. To be successful over the long term, developers must be able to sufficiently use it and understand it proving its worth and utility. If you disagree with our Humble© intention please consider some other solution for your product needs. See the End User License Agreement (EULA) and/or Developers Source License Agreement (SLA).

Q: Why not offer the source as completely open?

A: See the answers provided for the previous question plus three more herein. One, the nature of the Humble© innovation is such that it compresses and compounds the already highly detailed and complex workings of a windowing operating and file system. Hence, if the source code were offered as completely open the number of questions generated would consume our present development resources preventing further progress whatsoever. Two, the largest companies would be in the best position to leverage it, while being able to obtain it for free. Three, not offering it completely open puts the smallest developers on a level field with the largest per se . . . re-revolutionizing computing. So collectively for all these reasons consider building upon the Humble© innovation via the Application Programming Interface.

Q: Does Humble© use a microprocessor as its foundation of and for operation?

A: No. Humble© uses what was before the microprocessor as its foundation. Consider there is something greater than the microprocessor here. For example while a microprocessor is single threaded in the sense of the number of programs actually executing at any given clock cycle (though many may be resident in memory and in various stages of execution), Humble© uses an unlimited nexus of multiple simultaneous logic, each nexus capable of branching depending upon execution required by the user. The first revision of Humble© runs approximately 7 programs simultaneously incorporating more than 1000 low level processes simultaneously allowing up to 10 smoothly switched simultaneous 100 MByte conversations in concert with other simultaneous non-conversational functionality. These numbers perhaps small are not limited by concept, nor by present technology, nor by architecture, they simply result as a consequence of bare actual PC functions which in turn are sensible numbers sufficient for proof of concept so as to run a PC.

Q: Does Humble© run Linux or MS-Windows?

A: No. Humble© is a re-architecture of the personal computer combining the functions of a conventional microprocessor and conventional windowing operating system onto one chip without actual utilization of either. Present limitations of the microprocessor and its paired operating system are circumvented through re-architecture thereof. Humble's distinctive features are direct consequence of re-architecture and are not possible with a conventional uP and o/s.

Q: Can I run x86 programs on Humble©?

A: No. However, because Humble© resides in a fully reprogrammable (on the fly) core, it is possible that a company experienced with x86 could implement a conventional x86 core as a tandem-switchable-alternate for bridging "the old" with "the new" . . . allowing x86 with Humble© in the future per se. For clarity, Humble© does not presently run any x86 programs. Consider the word 'presently' and consider that for Humble© to truely establish itself in the long term as a fundamental alternative to x86 microprocessor based systems, it should and must be introduced and stand alone without a microprocessor, and without x86 program compatibility so others may begin to see the nature of the innovation. This may help others to realize its enabling potential. For example it conjures up the notion of computing without a microprocessor and conventional operating system . . . Then and only then does it begin to make sense to add hooks into Humble© to run or emulate conventional programs . . .

Q: If it doesn't run x86 programs and it doesn't run Linux or MS-Windows anything what good is it?

A: Short Answer - If a user can perform all the same kinds of tasks he wants-needs-desires, does it really matter what brand name of operating system is inside? If he can do all the kinds of things he wants to do without complaint(s) or exceptions, pun intended :) , is it not-useful? Longer Answer - The same question could be posed toward Sun or Apple products . . . The Apple corporation is a tremendously successful international company and only recently has the company considered changing some of their products so they can run x86 programs. So clearly running x86 programs is desirable (in present market context) but it is not required if and when affordable new technology arrives surpassing the performance and potential of the x86 architecture, while leaving the door open for its legacy to continue. Alternatives to existing products are often criticized fiercely until they become the existing incumbent product. Then they are criticized even more! ☺ Humble© is clearly not for the faint of heart designer or those without depth of understanding. If your company's expertise is solely software, or a mix of software and hardware, perhaps this is your cue that there is yet still another and perhaps better solution, becoming available. Perhaps its time for your company to begin learn how to write software that describes hardware . . . As of this writing complete Humble© PCs are not mature enough to compete directly with the existing incumbent marketplace products. Humble© is just emerging. Humble© is just now being introduced. The Developers kit itself is both initial product and proof of the concept. So it is still very early . . . It is in a PC form that we refer to as "Very Bare but Recognizable". While many features and benefits exceed marketplace products, the application suite is genuinely very bare. So its value is best understood by those with present and future vision with an ability to assess the opportunity it presents. Hence, Humble's best immediate fit is within embedded systems both related and unrelated to PCs in concert with development of a next revision full featured Humble© PC . . .

Q: Is Humble© programmable like existing computers?

A: Yes and no. Humble© programs may be installed and uninstalled, loaded and unloaded . . . Humble's 'hardware' operating system is loaded at turn on. It is reprogrammable in the sense of one time at turn on a new version may be loaded. Regarding the 'no' part of this answer, existing computer 'hardware' is not reprogrammable and is fixed without any option what-so-ever for changing it. While this is not typically a problem, Humble offers flexibility over and above 'existing computers' by allowing reprogramming of both hardware and software, or just one or just the other . . .

Q: What good is a hardware operating system if you can't change it (reprogram it)?

A: Humble's hardware operating system is loaded at turn on. It is reprogrammable in the sense of one time at turn on a new version may be loaded. So o/s upgrades and changes can be accomplished.

Q: What good is a hardware program if you can't change it (reprogram it)?

A: Programs may be installed and uninstalled, loaded and unloaded . . . Like the o/s, programs are reprogrammable in the sense of one time at turn on a new version may be loaded. So program upgrades and changes can be accomplished.

Q:If the o/s and programs can be loaded, can't a virus also be loaded?

A:No (w/ 99.9% or higher confidence). Please be patient for the explanation why this is so -- Let's take a step back for perspective on the existing computer virus problem. . . Why isn't it solvable with existing microprocessor based computers? Minimally, the answer is that for existing computers the entire o/s and programs are not write protected and nor can they be with any benefit thereof. When any program is running, it has access and control of nearly the entire machine and can do what-ever the author has intended. Before any program including the o/s (program) begins to run, it must begin from somewhere (a.k.a. boot). If it is a 'boot-virus' it can do whatever it wants including disabling the o/s from blocking any intended malicious action(s), thereby allowing control of all the machine without exception. A simple virus program can destroy or change any part of the operating system (program) or application programs and/or user data because programs (on disk) all appear the same to a running program as read/writable objects (data). In short with existing computers, viruses will remain a perpetual problem because there is no real root solution possible. So microprocessor based computers have one huge hole that can never be completely closed. Although this is undesirable and unintentional, and many good protective programs have been developed, it is a perpetual consequence of all microprocessor-program-fetched-operating systems. . . As we the users have experienced, viruses can be somewhat patched as they are discovered (after the fact in some instances while before in others not yet infected). . . So in the case of Humble© we remove the o/s from the microprocessor. To prove the point we go a step further and remove the whole microprocessor. Humble© doesn't load or fetch or architect the o/s as a running program. Although it loads at turn on, it loads from non-removable write protected flash memory. This protected non-removable media is not associated with user media and/or drives/ports. Saying this another way, while Humble© loads its personality upon turn on, it doesn't load it from a floppy or hard disk or other unprotected r/w media. Humble©'s fixed protected flash memory (on the motherboard) is not accessible by programs during run time. During run time it is not writable by itself or other running programs. Presently a separate, special programming interface is required for changes. This method allows upgrades to the o/s while preventing virus entry altogether into the o/s. So, by intentional design it is not possible for a user program (virus) to disable or overwrite any part or portion of the on chip silicon-based-operating-system and/or silicon-based-programs. Certainly it can be argued that virus entry is possible through the special programming interface. While possible, use of the special programming i/f typically will occur once or a small number of times typically at the manufacturer or an affiliate. So clearly this is not a wide open point of entry (as is the case with present microprocessor based computers). Further, detection/presence of a virus requires that the same virus would have been provided by the manufacturer/affiliate etc., hence reducing the probability of occurrence. So the problem becomes dramatically reduced to one of quality control within the field of control of a manufacturer. Assuming this case of entry, the virus cannot be spread to other Humble© computers but compromises only the one affected, so the virus isn't contagious, it isn't virulent. In fact it is self limiting . . . self quarantined etc. . . at least among other interconnected Humble© computers. To say this one more time, other Humble© computers are not affected. So while it is not 100% impossible, the chance of occurrence is tremendously reduced. We suggest reduced by as much as 99.9%. Correspondingly, the chance of a hacker getting caught in this scenario is tremendously increased, while limiting the potential harm. Still assuming a case of virus entry, the solution is simple, simply revert to the previous known good version of the operating system. So with Humble©, data is still at risk, but the operating system and programs are no longer at risk, hence improving reliability . . . as a consequence of design.

Q: Is Humble© clear of the existing patents by various computer companies including Microsoft, Intel, and AMD?

A: Yes. Although it has not been tested in the courts, it is a complete re-write from scratch upon a first of its kind architecture. Further, because it does not use a microprocessor as its core nor use or require any of the brand name or non-brand name operating systems, it is presently believed it is clear of all patent infringement and licensing agreements what-so-ever.

Q: How does it work?

A:) It works. It rests upon understanding from of old. As mentioned above, "there is something greater than the microprocessor here". To say this another way with bare honesty and sincerity, consider reading the whole Good Book (all the words, quietly to yourself) then consider reading all of the questions and answers provided herein, then you too will know how it works . . . If upon reading the whole Good Book (all the words) and this FAQ, you still don't know then keep asking until you receive . . .☺

Q: What is the meaning of the word Humble? First and foremost it has the meaning you already know. When I humble myself I see the same world in a different way. Second, it is an acronym that means Hardware Unified Multiple Branch Logic Engine.

Q: What is meant by Hardware unified?

A: A conventional uP and o/s performs its operation through software control of hardware. Therefore we assert the software unifies all operations. All commands are input ultimately to software and all actions/results are consequences of decisions made in (by) software. Alternatively, hardware unification allows user commands to enter directly into hardware with decisions made directly by hardware. Thereby relegating storage of instructions on a Hard disk (fetched to a local memory cache), then decoded and executed as a legacy optional method for general purpose computing. In other words history will begin to record that instructions no longer need to be fetched from memory (or a disk) . . . when using a Humble© PC.

Q: What is meant by Multiple Branch Logic Engine?

A: Generally speaking, a conventional single uP with its o/s performs single branching. From any one instruction to another the conventional uP and o/s typically can only branch from one instruction-point to another (within a program), or one instruction within a program to one instruction within another program. Humble© allows point to multi-point, process to multi-process, and also program to multi-program branching with simultaneous execution and symmetrical or asymmetrical return. These are all performed without accessing a disk for instructions (with its associated delay).

Q: Is Humble© a RISC or CISC architecture?

A: Given that both are terms typically describing kinds of microprocessors and/or kinds of Instruction Set Computer architectures, and Humble© doesn't use a microprocessor, and nor is it a variation of a microprocessor, and nor does it have an Instruction Set . . . no, it is neither RISC nor CISC.

Q: If it's not RISC or CISC what is it?

A: Rephrasing the question -- Can either of these terms be loosely applied? or perhaps some other similar term be defined and applied to help explain and further understanding of the Humble© architecture with respect to instruction set computers? No and yes respectively. While RISC and CISC refer to kinds of 'Instruction Set Computers', implied in this terminology is a constancy or fixing of what is then defined as 'the set of instructions', wide or narrow, simple or complex, etc. . So consider that Humble© does not 'fix' or 'set' as a constant 'the set of instructions'. Nor does it fix or even generically define instructions, nor does it set bit-widths to a constant and nor does it 'fetch' instructions from a memory for execution. So its not an 'Instruction Set Computer' that when described (in hardware) performs as a computer and while there is no actual instruction set, it can be argued there are shadows or hints thereof, though not fixed nor fetched in any of the conventional nor historical sense of instructions what-so-ever. So let us be the first to coin a new term NISC, wherein NISC is henceforth defined as 'Non-Instruction Set Computer'. So generally speaking Humble© is a NISC.

Q: Can you explain NISC further?

A: Yes. A NISC computer is 'Not' an 'Instruction Set Computer' (NISC) that performs as a computer without an actual instruction set. A NISC architecture neither fixes nor fetches in any of the conventional nor historical sense of instructions what-so-ever. NISC does not require instructions to be stored, fetched, decoded and executed as conventional RISC & CISC. We fully recognize the difficulty this explanation portends to the reader (and even perhaps the potential humor☺) understanding the idea of a Non-Instruction Set Computer☺ in a world of 'Instruction Set Computers' . Please realize this explanation is genuine, serious and accurate while intending to protect the Humble© innovation herein. For the reader with depth of understanding this explanation should more-than begin to communicate the practical, useful, and financial opportunity.

Q: Can RISC or CISC be combined with Humble© NISC? Is there any benefit of doing so?

A: Yes. RISC and CISC architectures can be enhanced with Humble© NISC for the obvious reason that Humble© NISC does not need to fetch instructions and is not limited or constrained to an instruction-set as previously described. In other words Humble© NISC on top of RISC and/or Humble© NISC on top of CISC would seem to allow reuse of the respective pre-existing RISC and CISC code. The reverse wherein RISC or CISC is run on top of NISC is certainly also possible but doesn't make much sense and wastes most of NISCs benefits. Stated another way Humble© NISC seems to be what is needed at the top as the basis for operating systems that desire to control many CISC software programmed microprocessors. When Humble© is combined with CISC we would call it Humble© CISC (HCISC).

Q: Is Humble© NISC a Dataflow architecture?

A: As per Wikipedia, the definition of Dataflow is shaded as comprising Software Dataflow, Hardware Dataflow, Concurrency Dataflow, and Dataflow Diagrams. While to some it may seem like it might be dataflow, no it is not. Humble© NISC doesn't allow data to flow through it anymore than do RISC or CISC architectures. Humble© similarly remains user-control-switched but instead runs hardware programs rather than software programs to perform tasks, so it is not a dataflow architecture.

Q: What is meant by Multiple Simultaneous 100MByte conversations?

A: Consider one bus capable of transferring data in one direction at speeds from 0 to 100 MBytes per second. Now provide an integer multiple of busses with different end points (ports) wherein each bus is capable of transferring 0 to 100MBytes per second independent of any other. Humble© allows all combinations of operation that make sense for the overall functionality up to the maximum speed. Further, where full duplex (simultaneous 2-way) conversation is required, Humble© supports this too. Switching is present only when required, so when no conversations are required, the busses are quiet minimizing power consumption.

Q: What is meant by Instant On|Off?

A: When the power is turned on there is no 'Boot' time of the o/s or programs, Humble© is ready in approximately 1 second. When the power is turned off there is no turn off time. Humble© turns off in less than 1 second. An exception to this at present is some wait time for accessing the Hard Drive (for data only) if one or more is present. A hard drive is not required for operation. Since Humble© programs are not fetched from a disk there is no need for a disk from an o/s and program perspective. In other words Humble© o/s, drivers, and programs are non-volatile. Certainly when used as a PC, Humble© user-data will likely be stored on some kind of external media including hard disk. So, if the user has unsaved data, certainly time is required to retrieve and/or save user data.

Q: What is meant by Familiar windowing Interface?

A: Although this should be self explanatory, Humble© initially presents its windowing interface as similar to others available. Humble© start bars, pop up and pull down menus, thumbnails, mouse-overs, etc. are intentionally similar so as to feel somewhat familiar, though re-written from scratch upon a new architecture. Because of the fundamental architectural differences, Humble's future-potential windowing Interface is without many of the present limitations . . .

Q: The windowing Interface looks more like MS-Windows than Apple or Sun, is there any relationship, what's the scoop?

A: The Humble© author has used MS-Windows like many others since MS-Windows 3.0 (and prior) and has been favorably influenced by it and is a fan of the company but has no relationship with the company any more than any other MS-Windows user. So Humble's look is intentionally similar from a user perspective so as to communicate to both computer users and companies considering application development upon Humble©, its present-readiness and future-potential toward completeness in the marketplace. Given it is a complete re-write from scratch upon a new architecture all-together, including windowing programs and related display graphics, it is believed there is no infringement. If we have infringed we apologize and please let us know how, where, and why, as soon as possible . . . We hope this look is received as flattering and favorable to others and again we intend and believe there is no infringement. We genuinely and sincerely apologize if anyone is offended. We hope it is received in a favorable manner as it is intended. Rather than being offended , consider becoming a Humble© customer. It is said in the early days of the MS company, MS offered to develop for IBM, we offer the same to all, big and small to begin considering allowing Humble© to power their next system . . .

Q: Given Humble© doesn't need a microprocessor to perform as a PC, does Humble© obsolete the microprocessor?

A: Short answer -- No, absolutely not. It is wildly foolish to suggest so. Longer answer -- Humble© is a genuine alternative, thereby respectfully challenging future use of the microprocessor. Certainly the present installed code-base for PCs is beyond huge. So it seems more likely in the near and long term that Humble© may serve in tandem to extend the microprocessor legacy. In some cases only (with a lot of decision dependencies) it is theoretically possible to replace it altogether. However, it is wildly foolish to believe this will happen. So we merely suggest considering inclusion of Humble© toward extending legacy operating systems and programs.

Q: Does Humble© obsolete Linux?

A: No, absolutely not. However, if you have a Linux specialty, consider developing and extending your skills toward application development upon Humble© . . .

Q: What about the rest of the user interface?

Presently (1) mouse and (1) keyboard are advertised. Humble© 's architecture does seem to accommodate toward multiple mice and multiple keyboards for multiple users into one computer. However, this translates to additional user-specific requirements upon the operating system (not yet included), but none-the-less reasonable and possible to implement within Humble© . Minimum wired device support is provided first to prove the innovation-architecture. Wireless devices are extensions of the basics and are presently an opportunity for others to add . . . Humble© supports addition of optical and voice recognition interfaces. Hence these are also present (feasible) opportunities for others to add.

Q: What is meant by O/S and Programs immune from viruses?

A: Humble©'s O/S, drivers, and base set of programs reside as hardware so there is no chance or possibility of a boot sector error or boot sector virus or any other threaded, trojan horse, program-virus wreaking havoc upon these. However, a Humble© PC as a whole and/or its programs may still be hi-jacked by an unauthorized user (in terms of username and password). But they may not be modified or destroyed because they are coded into hardware. So Humble© provides no openings for viruses. Stated another way, Humble© closes the significant openings and main threats to the O/S and programs. This said, there still remains an opening (threat) to stored user data. Humble© simply cannot prevent data corruption via unauthorized or malicious users . . .

Q: What is meant by seamless-smooth-Fusion?

A: The conventional PC supports multi-media but user experience is poor and inconsistent. Significant delays due to loading and/or buffering, crashing, stuck graphics preventing use of the rest of the computer, etc. plague the experience. In some cases it seems the longer a PC is used and the more programs that are installed and the more that are opened and running, the greater the likelihood of crashing or slowing to such a degree that it's often not worth waiting for. Some users begin to fear updating or loading anything new as potentially causing worse operation. Although there are well known reasons and solutions to each of these experiences, the legacy of this experience still persists resulting in a want for smooth use experience satisfying the broad-general-user-community. Users want to talk on the phone while surfing the web while switching back and forth to many and various program-applications without waiting 5, 10, 20, 30 seconds, sometimes minutes just for the screen to update . . . Other users want to simultaneously watch TV or a video, or at least switch through the channels while listening to Radio or recording on a CD. While others want to mix gaming . . . Humble©'s architecture enables programs, interface ports, etc. to run simultaneously assuming sensibility thereof. Humble© sensibly notifies of contention for the same end point resources, removes the DRAM memory buffering bottleneck, and eliminates program-instruction traffic on busses altogether. Hence, Humble© has all the architectural features for seamless-smooth-switching of many different simultaneous applications.

Q: What is meant by Low Power?

A: Humble© runs at 1/10 clock speed with respect to a 1 GigaHertz metric. Some microprocessors run as fast as 4 GHz. With respect to 100MHz, a 1/40th frequency ratio arises in favor of Humble©. Since power is directly proportional to frequency Humble© reduces the carbon footprint of the processor portion of a 4GHz PC by as much as 97.5%. Because this is presently an estimate (though a good one) we are reducing the claim to a 50% number. Humble© also includes automatic power down features where ever they make sense. Humble© is a static synchronous design allowing clocks to be turned off to whole areas when not required. Humble© circuits switch upon user demand and are quiet otherwise so as to consume the least power. Humble© does not contain multiple microprocessors such as the 80 processor Intel research chip recently mentioned in technology-news, so its power is generally much less. However as more and more applications become written for Humble© and its relative core size grows, power consumption will increase. For a similar feature set to a typical PC, Humble© provides approximately a 50% reduction in overall power . . . From a silicon viewpoint with each shrink of technology, power consumption decreases.

Q: Is Humble© a personal computer?, What is Humble©?

A: Foremost it is an acronym that is intended to convey a dual meaning. The first is the same one you already know. The technical meaning is Hardware Unified Multiple Branch Logic Engine. So its a word and an acronym. As it is applied to computing, Humble© refers to the construction of the core. While the word 'core' in technology speak typically refers only to the hardware core or microprocessor, we are applying (redefining) the term here more generally wherein there is not an actual microprocessor required in the case of Humble© (though it is possible to include or operate one or more). For clarity herein no microprocessor is included in Humble©. Further, there also exists a 'core' in technology speak referring to the construction of the software. So Humble© collectively refers to the construction of both hardware and software considered as one-construction rather than two separated constructions . . . When applied to the context of personal computers we say Humble© PC. Essentially it is a practical implementation of unity or "one" upon hardware that historically was hardware and software. So as a word it may be applied to other non-computer products, but its utility is exemplified quite well in the form of a computer . . . See answer to RISC/CISC question above too . . .

Q: Is Humble© a cell phone?

A: No. However, Humble© as a basis for a next generation cell phone does seem to improve the internet (ip interface and functionality) connection while allowing other simultaneous application-features without common s/w - microprocessor disadvantages. Humble© supports inclusion of simultaneous telephony. In other words with the addition of transmit-receive interfaces (ports), telephone call(s) may start, persist, end, while any other application-operation or combinations of application operations are active each without interfering with the other . . .

Q: Does the Humble© PC have an internet browser?

A: Yes and no. The ip protocol stack (TCP/IP) is mostly complete, however, the entire browser function is still in development.

Q: How does the Humble© PC connect to the internet?

A: The developers kit includes IPMoE (Internet Protocol Module over Ethernet). So the initial method intended is via Ethernet connection through an ADSL modem or FIOS telephone line (e.g. a Verizon broadband connection). All other kinds of connections including cable modems and wireless connections are presently opportunities for others to add.

Q: What is meant by Humble© in relation to Robotics?

A: With some exceptions, present day robots tend not to perform high complexity, multiple functions with smooth simultaneity. For example we clearly don't see 'ns-4' or 'ns-5' like robots walking around as seen in the movie I-Robot (2004, featuring Will Smith). Typically when this has been attempted, significant performance, co-ordination, and functional-reliability problems glaringly appear, exemplifying the massively huge problems pitfalls and consequential decision making delays within their respective computer-architecture (typically microprocessor based) . . . It seems to us a robot based on the Humble© PC NISC architecture should be able to speak and listen and walk simultaneously etc. etc. etc. It seems an application whose architectural engine has arrived. See definition of NISC above.

Q: What is meant by Humble© in relation to Automotive?

A: Hard Disk drives are problematic in shake-rattle-and-pothole environments. They are not well suited and are prone to error with possible catastrophic failure, or at least, erratic operation. Therefore, conventional software operating systems that depend upon a hard drive for their main program and applications are not well suited . . . Alternatively a Flash drive (w/no moving parts) may be used as the main storage for the o/s, programs and data. So the mechanical hurdle is overcome. However, the practical and developmental aspects of merging the present windowing operating systems (of all brands) with complete automotive electronics doesn't make sense for a plethora of other reasons. First and foremost the nature of combining the present software based windowing operating system with true real time circuitry is not a natural and easy pursuit. While possible, the existing methods used for each are somewhat far apart. Even if we take a little liberty and assume these problems can be overcome, how well will the end product work? If we assume it will function as well as a typical home PC is this enough? Is this satisfactory? The answer has been available for quite a while -- No. For example while writing this section our home PC connected to the web running XP with all of its known updates got stuck and wouldn't even respond to Ctl+Alt+Delete or its power button. So, it had to be unplugged altogether in hopes of recovery which it did. While this is the exception to normal use and is tolerable at home for a web connection, it is absolutely unsatisfactory when operating automobile functions at any speed including stopped. Comparatively, Humble© seems well suited for use as the user-cabin-computer and also for integrated computer modules for the engine, transmission, emission control systems with an option to integrate (combine) all these functions together lowering total manufacturing cost . . .and overcoming all of the reliability issues.

Q: What is meant by Humble© in relation to Integrated MultiMedia?

A: Audio, voice, and video whether combined or separate, whether sourced from the same media or different media, Humble's ability to run multiple simultaneous conversations smoothly, predictably, and reliably, with minimum buffering, seems to make sense. If one conversation encounters an error it doesn't adversely affect, interrupt, or interfere with others . . . Each conversation (typically initiated from a program) can be stopped, reset, and restarted.

Q: What is meant by Humble© in relation to voice recognition?

A: Because literally any kind of port or interface can be incorporated into a Humble© PC without slowing it down, applications like voice recognition (in addition to everything aforementioned) become practical features waiting for inclusion . . .

Q: What language is Humble© written in?

A: Humble© is written in VHDL.

Q: What does the word VHDL stand for?

A: VHDL is an acronym that means VHSIC High-Level Description Language. VHSIC means Very High Speed Integrated Circuit. VHSIC was a Department of Defense program in the 1980s. The VHDL language was born out of that project.

A: Xilinx ISE Foundation 10.1i

A: ModelSim XE III 6.2g

Q: Can I use other languages?

A: Yes, other open languages include System-C and Verilog.

Q: Can you provide references to VHDL literature?

A: See VHDL bibliography

A: A Field Programmable Gate Array (FPGA). Specifically Xilinx Virtex 4.

Q: Can I use a different FPGA?

A: Yes and No. Presently most of the Humble©'s cores themselves include Xilinx cores. Through redesign of Humble©'s cores, any FPGA can be supported. If the reader is from one of the other companies, please contact us so we may begin the process.

Q: Aren't FPGAs too expensive to compete with microprocessors?

A: No. For example during the recent 3 years the cost of the entire Humble Motherboard including Virtex FPGA decreased by approximately 50%. History records, as each next (new) series (density) becomes manufacturable, the previous becomes less expensive to manufacture. In other words, Moore's law applies equally to FPGAs as microprocessors. So, the relative cost continues to reduce in tandem for all the same reasons. What was once too expensive is no longer. With each technology advancement they have become more capable and less expensive just like everything else . . . It is just as the visionaries of our time and before have said, . . . the hardware will continue to tend toward zero dollars. Further, the Xilinx company has advertised $27.00 for the Virtex 4 VLX 25.

A: No. Generally speaking, Humble© is technology independent so that it may be retargeted if a particular FPGA becomes unavailable for whatever reason . . . However, the present Humble© development board specifically uses a Xilinx Virtex4.

A: Consider that Humble© is Intellectual Property first that happens to realize its potential in Hardware. So consider from a business perspective it is more likened to software . . .

Q: Why hasn't this been done before?

A: Short answer - It is a very difficult problem. Longer answer - Complexity is very very high. The present day conventional operating system consists of more than 1 million lines of code not counting application programs. The microprocessor it runs upon consists similarly of millon(s) of transistors. Complexity compounds when the two are enjoined. Research in the area of computing tends to assume 'the state of the art' (the present enjoinment) as the starting point upon which to further build-improve. With this approach, complexity compounds exponentially further making the problem only more difficult . . . Billions of dollars have been invested. So it is easy to begin to see how difficult it is to suggest any re-architecture what-so-ever except something perhaps novel or minor. Hence, most researchers have been looking for an easy pathway using the same h/w-s/w set or close-derivatives thereof. Historically no competing combinations of h/w and s/w have been able to deliver the general purpose functionality of the microprocessor based PC. Historically, the microprocessor is now approximately 41 years old and it was developed in part to compete with electromechanical systems. Pausing here for a moment consider there was a time when there was no microprocessor and no windowing operating system, yet they were developed. So if the slate is wiped clean today, and we re-architect from scratch and we build upon the foundation that was before the microprocessor would we choose that which we have otherwise inherited? . . . For everything it can do we say -- yes (and it does many things extremely well), but because of its limitations we say no. If for no other reason, because our expectations for what seems possible are no less now versus those of 1968 (and our wild-eyed enthusiasm though occasionally dampened is at least the same or more☺. . .). In other words, in 1968 man was still enthusiastically trying to get to the moon, now it is 41 years later, we've been there, we may go back again, we are already doing much more but would like to do a whole lot more . . . or at least enable future generations to do so . . . So, Humble© starts with our 2009 forward looking wants-needs-desires as system design requirements rather than 1968s design limitations (now realized) and then re-solves how to get there . . . Now having received this new solution (that is not new), we then begin to see how it may be possible to run the new with the old in tandem . . . In other words, this problem, once seemed nearly impossible to solve until we rediscovered what was before . . . which in of itself is extremely difficult yet simple.☺ . . .

A: Yes and no. Since it doesn't need a hard disk drive and folds the display adapter and clock chip functions inside there are potential savings. Although it doesn't use a microprocessor it does use a Field Programmable Gate Array (FPGA). The cost of this FPGA chip is very similar to the cost of a microprocessor chip although comparison is somewhat difficult due to dramatic internal differences. Consider that both are produced on state of the art foundries and are subject to similar market pricing forces so they tend to similar Average Selling Prices (ASPs). With a long term perspective, the cost of a Humble© PC is anticipated as very similar with the same downward price pressure. In terms of user wants needs and desires it seems Humble© enables potential for price advantage if microprocessor based PCs do not experience a significant breakthrough. In the event microprocessors do experience a significant breakthrough the two alternatives are again somewhat at cost parity.

Q: What is included in the developers kit?

A: See Humble PC Development System

Q: I read the list of what is included in the Developers Kit but want more of an explanation -

A: The developers kit is intended to make available the present state of the Humble PC for others to build upon it, adding and subtracting as their requirements demand. Some developers do not intend for their application to be available to the open market (such as projects related to defense). However, other developers will intend to make their applications available to the open market (such as those intending a word processor or game other universal use application). In both cases the developers kit attempts to include everything needed to "hook into" or onto Humble©. The design is organized as a top level with the various peripheral interfaces (cores) as ports. If one or more ports are not required for your requirements, they may be subtracted from the design via something called a Generic Switch found in the port map of the top level. This has the effect of reducing utilization which may be valuable for some projects . . . Similarly if Humble© is to be a small part of your overall project, it may be included as a component within your next level up of hierarchy. If you are not already familiar with hardware design, please go get the knowledge thereof and then come back . . . as this explanation may already not make sense to you. If you are already familiar then so far it should be clear and this should help answer the question.

Q: Is the developers kit a ready to go personal computer?

A: No. Although it can to many things a commercially available personal computer can do, there is much it cannot do (yet). Of those things it cannot do many have hooks already in place, are planned for inclusion, but simply not complete (yet). So, the developers kit gives an excellent foothold in many and various ways. It provides an opportunity for others across the entire spectrum of applications where it may sometimes seem there is little or no (opportunity) . . . It demonstrates present and future capability in the light and form of a recognizable but very bare computing platform.

Q: So is it a 'gadget' ?

A: Short answer yes and no. Longer answer -- The initial Humble© announcement and corresponding version announces proof of concept, introduces Humble© and makes it available for others to begin using it. It proves there is another way. It demonstrates beyond a doubt that an entire computer per se can be constructed without a microprocessor and without "software" as is conventionally accepted. This initial version is re-useable in its present form, allowing adding and subtracting to/from its core(s) for many and various applications specifically rPSoC (re-Programmable System on Chip), PC and non-PC related. So in this sense it's not a gadget . . . However, with respect to 'a finished product ready for the masses' conventional marketplace PC as the measure, the answer is clearly yes. So hopefully you will realize the nature and value of the innovation and perhaps will begin seeing Humble© as having already closed the gap between gadget and non-gadget for some applications but certainly not all . . . therein enabling a 'Huge opportunity' for others . . .

Q: When will it be able to compete with conventional PCs in the marketplace?

A: The answer depends completely upon licensing and development system sales as the means to provide additional capital toward further development progress. Assuming sufficient capital, a version competing in the marketplace could be available in roughly three years, probably closer to five years, more or less.

Q: Why introduce Humble now if it isn't complete and fully ready?

A: We are approximately on schedule. Our business plan was to do exactly as we are doing. Introduce Humble© at a point wherein PC functionality is bare but recognizable . . . This allows others to begin thinking, considering, developing and using it while hopefully providing additional capital for us to extend Humble's© features toward a fully functional PC.

A: Start a new company or revitalize an existing company based around Humble©. Consider innovating a new product or migrate an existing product to Humble©. Become a seller or distributor or developer. Purchase a Developers Kit and Licensing Agreement. Start writing applications or games for the Humble© PC. Migrate or develop peripherals for the Humble© PC. If you are an FPGA manufacturer, contact us and tell us what tools and evaluation boards are available for your products.

A: It should be apparent from the prior questions and answers. To briefly summarize -- We humbly admit we do not know the future. We simply see Humble© as an improved foundation for general purpose electronic computing both related and unrelated to PCs. With respect to the same, PC and non-PC products, we see Humble© mainly as an extender of legacy microprocessor based operating systems and programs with enabling potential for replacement altogether. When mature we see Humble© products revolutionizing and unleashing the potential of electronic products, in-as-much-as we see the same revolutionizing and unleashing of the minds of those developing them. We see Humble© as solving many long standing wants, needs, and desires of end consumers as they look toward combining features and benefits of the many and various products into as few as possible . . . We see Humble© as unifying Hardware and Software both sensibly and practically. After saying all of this we humbly admit again no one knows the future, so the best we can do is to continue moving toward Understanding with a capital U. In this sense Humble unifies two big pieces wherein the two are the hardware(microprocessor) and its software(operating system, programs). As you already know Humble© does so without reusing a microprocessor nor conventional software program operating system. So it seems what was two separate pieces has become one . . . So it simply makes sense.

Q: I read the entire FAQ and my question(s) were not listed and/or were not answered.

A: Please submit your question(s) to Gregg.Macdonald@ecs-pc.com

Copyright 2008 Electronic Compute Systems, Inc.. All rights reserved. This material may not be published, broadcast or rewritten without permission. We encourage requests for permission. Please contact Gregg.Macdonald@ecs-pc.com

Copyright © 2003 Electronic Compute Systems, Inc. Last modified: 02/12/10

Copyright © 2003 Electronic Compute Systems, Inc.
Last modified: 02/12/10