blocks|key|3028670|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3028671|只是想了解事情是如何运作的。|blockquote|3028672|3028673|3028674|事情的工作原理是CPU只是系统的一部分。没有RAM，它是无用的；没有某种形式的持久存储，它是无用的；没有某种与外界对话的IO+(例如，一个串行端口)--它是无用的。|3028675|3028676|，BIOS将扮演什么角色？|3028677|3028678|3028679|"BIOS“(或者更准确地说，系统打开时使用的某种ROM+)扮演”存储“的角色--+CPU获得初始化其他存储设备和加载更多可执行代码所需的可执行代码的一种方式。|3028680|对于您的"NOR关卡遍布数百块面包板“，您可能最终会将一个非常小的"+OS”直接放在ROM中，这样您就不必担心提供额外的持久存储；经过大约10年的奉献，您最终可能会看到最小的操作系统工作3次(在厌倦“本周哪条线路连接不好？”之前)。(连续断裂)|3028681|从某种角度来看，1位RAM将花费你4个或4个门，所以一个微不足道的512字节RAM将花费你16384或门(行/列选择逻辑更多)。这就产生了超过4000+"74LS02四倍两输入或门“芯片。如果您可以将这些芯片中的40片打包到一块面包板上，那么您将看到大约100个面包板，只是为了没有足够的RAM来运行任何操作系统。|3028682|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|U|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|V|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|W|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|Y|7|@]|8|@]|9|$]]|$1|H|3|-4|4|5|6|Z|7|@]|8|@]|9|$]]|$1|I|3|J|4|C|6|10|7|@]|8|@]|9|$]]|$1|K|3|-4|4|5|6|11|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|12|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|13|7|@]|8|@]|9|$]]|$1|O|3|P|4|5|6|14|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|15|7|@]|8|@]|9|$]]|$1|S|3|-4|4|5|6|16|7|@]|8|@]|9|$]]]|T|$]]

<blockquote>
Just trying to understand how things work.
</blockquote>
How things work is that a CPU is just one piece of a system. Without RAM it's useless, without some form of persistent storage it's useless, and without some kind of IO to talk to the outside world (e.g. a serial port maybe) it's useless.
<blockquote>
What role the BIOS will play?
</blockquote>
&quot;BIOS&quot; (or more correctly, some kind of ROM used when the system is turned on) plays the role of &quot;storage&quot; - a way for the CPU to obtain executable code that's needed to initialize other storage devices and load more executable code.
For your &quot;NOR gates spread across hundreds of breadboards&quot; you'll probably end up putting a very minimal &quot;OS&quot; directly in the ROM so that you don't have to worry about providing additional persistent storage; and with about 10 years of dedication you might eventually see your minimal OS work 3 times (before getting tired of &quot;which wire is having a bad connection this week?&quot; continual breakage).
For some perspective; 1 bit of RAM will cost you 4 NOR gates, so a measly 512 bytes of RAM will cost you 16384 NOR gates (more for row/column select logic, etc). That works out to over 4000 &quot;74LS02 Quadruple Two Input NOR Gate&quot; chips. If you can pack 40 of these chips on a breadboard then you're looking at about 100 breadboards just to end up with not enough RAM to run any OS.

blocks|key|3028761|text|操作系统可以非常简单--如果你只想让系统启动，做一些像设备和线程之类的事情，但不想要一个完整的操作系统的所有保护和功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3028762|您真正需要的是响应中断并向用户级软件发送数据就绪(缓冲输入)或设备准备就绪的信号的能力，而用户级软件可以表示(例如，通过syscalls)发送到设备(缓冲输出)或从设备获取数据。可以为一个中断处理程序(一个小型操作系统)装配数百行程序。|3028763|但是有很多系统甚至没有这样的复杂程度。一些程序微控制器简单地运行一个程序，没有中断，他们有一个主事件循环，持续检查按钮按下或其他。|3028764|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Operating systems can be very very simple — if you just want the system to boot and do a few things like devices and threads but don't want all the protections and features of a full-fledged operating system.
All you really need is the ability to respond to interrupts and signal the user level software that data is ready (buffering input) or the device is ready, and, sort of the reverse, that user level software can indicate (e.g. via syscalls) data it wants to send to devices (buffered output) or obtain from them.  That can be had with a few hundred lines of assembly for an interrupt handler, a mini os.
But there are many systems that don't even have that level of sophistication.  Some program micro controllers to simply run one program, without interrupts, they have one main event loop that continuously checks for button presses or other.

blocks|key|3028829|text|我可以向您推荐“计算结构”系列文章：https://jeelabs.org/202x/tfoc/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3028830|在每台计算机中都会有一些初始代码，但是它所做的完全取决于你！在嵌入式系统中，"bios“是一个完整的应用。|3028831|直接从焊接门走是一条漫长而艰巨的道路。我正在FPGAs上做CPU设计，我是一门课程的撰稿人，这门课程把你从逻辑的第一步带到一个完整的RISC-V+CPU和编译的C程序：|3028832|https://github.com/BrunoLevy/learn-fpga|3028833|祝好运!使用FPGA，实际上可以使用自定义设计来引导Linux：|3028834|https://github.com/enjoy-digital/litex|3028835|entityMap|0|LINK|mutability|MUTABLE|url|https://jeelabs.org/202x/tfoc/|1|2^0|I|U|0|0|0|0|0|13|1|0|0|0|12|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|N|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|I]]|W|$5|Q|R|S|C|$T|M]]]]

I can recommend you &quot;The Fabric of Computing&quot; article series: <a href="https://jeelabs.org/202x/tfoc/" rel="nofollow noreferrer">https://jeelabs.org/202x/tfoc/</a>
There will be some initial code in every computer, but what it does is entirely up to you! In embedded, the &quot;bios&quot; is the complete application.
Going straight from soldering gates is a long and arduous way. I am doing CPU design on FPGAs, and I am contributor in a course that takes you from the first steps in logic to a full RISC-V CPU with compiled C programs:
<a href="https://github.com/BrunoLevy/learn-fpga" rel="nofollow noreferrer">https://github.com/BrunoLevy/learn-fpga</a>
Good luck! With FPGAs, it is actually possible to reach booting Linux with a custom design:
<a href="https://github.com/enjoy-digital/litex" rel="nofollow noreferrer">https://github.com/enjoy-digital/litex</a>

I am trying to build a CPU from scratch (from Nor gates) in an emulator first, then on breadboard.
Just trying to understand how things work.
Now, as my CPU will be new, how would I instruct an OS, say arch linux to work with it?
What role the BIOS will play?
Will I have to write a BIOS which contains an assembler in it?
Do I need to write some program on the OS too?
So that, it starts to communicate to with my CPU.
[P.S]: I am a programmer, so pretty much have idea on how things move till assembly level.
Just want to know how the hardware level works beyond Assembly.
Or in other words, what was written on BIOS for the first ever computer?
How did it bootstrap?

If I build a new CPU, what should the BIOS contain?(Read details)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正试图从零开始构建一个CPU (从或门)在模拟器中，然后在面包板上。只是想弄清楚事情是怎么运作的。现在，由于我的CPU将是新的，我将如何指示一个操作系统，比如说arch linux来使用它？BIOS将扮演什么角色？我需要写一个包含汇编程序的BIOS吗？我也需要在操作系统上写一些程序吗？因此，它开始与我的CPU进行通信...

问如果我构建了一个新的CPU，BIOS应该包含什么？(阅读详细信息)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如果我构建了一个新的CPU，BIOS应该包含什么？(阅读详细信息)EN