It does not need to be a full fledged OS, but must at least have multitasking capabilities (i.e. a scheduler).
Please mention what processor architecture it works on.
它不需要是一个完整的操作系统，但至少必须具备多任务功能(即调度程序)。请提到它使用的处理器架构。
This is a survey, so exact capabilities are not really important. Think of this as being a place to look at for possibilities when your next 8-bit embedded project comes up...
这是一项调查，所以准确的能力并不重要。当你的下一个8位嵌入式项目出现时，你可以把它看作是一个寻找可能性的地方。
I realize that most 8-bit micro do not require an OS, but just as a counter-example, Rabbit Semiconductor offers the RCM3710 processor module with 4 serial ports, a 10-BaseT ethernet port, 512K RAM and 512K Flash. All that for $39. All based around an 8-bit Z80 core.
我知道大多数8位微处理器都不需要操作系统，但是作为一个反例，兔半导体提供了RCM3710处理器模块，其中有4个串行端口，一个10个baset以太网端口，512K RAM和512K闪存。为39美元。所有基于8位Z80核心。
8-bit does NOT necessarily mean extreme resource constraint.
8位并不一定意味着极端的资源限制。
17 个解决方案
#1
4
This might be an unusual point of view, but I would strongly recommend to think twice and even thrice before deciding to use an OS for a 8-bit computer. OSes are for complex application needs, and 8-bit CPUs are not the best choice for these tasks.
这可能是一个不同寻常的观点，但我强烈建议在决定使用一个操作系统来使用8位计算机之前，要三思而后行。OSes用于复杂的应用程序需求，而8位cpu并不是这些任务的最佳选择。
I'm not saying that an OS should never be used for a 8-bit, just that there's less chance that it is the best solution.
我并不是说一个操作系统不应该被使用8比特，只是它是最好的解决方案的可能性更小。
#2
4
To those suggesting state machines in place of an OS because they have little overhead, you might want to check out Contiki. It is very small and free. It doesn't have a traditional threading model, instead it uses ProtoThreads: http://www.sics.se/~adam/pt/.
对于那些建议状态机代替操作系统的人，因为它们的开销很小，所以您可能想要检查一下连续。它非常小而且是免费的。它没有传统的线程模型，而是使用原始线程:http://www.sics.se/~adam/pt/。
ProtoThreads give you something approximating threading semantics without the overhead of a real OS with multi stacks, etc... As a bonus, you don't need any sort of OS to use them Contiki or otherwise.
原始线程给您一些近似线程语义的东西，而不需要使用多个堆栈的真实操作系统的开销等等。作为奖励，您不需要任何类型的操作系统来使用它们。
We've used them on one project with great success. They really make writing complicated code much easier.
我们在一个项目上使用了它们，取得了巨大的成功。它们确实使编写复杂的代码变得更加容易。
#3
4
I believe Contiki will work. Adam Dunkels does some really cool stuff.
我相信“连续”会起作用。Adam Dunkels做了一些很酷的事情。
It runs on a lot of platforms, including the Commodore 64.
它在许多平台上运行，包括Commodore 64。
#4
3
Rabbit Semiconductor has a port of the MicroC/OS II for their processors.
兔半导体的处理器有一个微c /OS II的端口。
#5
2
What's the goal here? Embedded OSes tend to cost a lot. (MicroC/OS II, etc)
这里的目标是什么?嵌入式操作系统的成本往往很高。(MicroC/OS II，等等)
It sounds like you may be putting OS support ahead of what I consider more important things when it comes to device selection. You should know the general design patterns for the platform you are working on. Don't try to shove PC concepts into the tinyiest of embedded chips like this.
听起来你可能会把操作系统支持放在我认为更重要的设备选择上。您应该了解正在开发的平台的总体设计模式。不要把PC的概念推到像这样的嵌入式芯片中。
OMFG... Java does NOT belong on an 8 bit processor. I actually tried that Maxix/Dallas DS80C400 chip. It had a simplified OS (read: scheduler) and TCP/IP stack baked on chip, and it looked great on the datasheet. It was a complete disaster. Slow, slow, slow!
OMFG……Java不属于8位处理器。我真的试过了，Maxix/Dallas DS80C400芯片。它有一个简化的操作系统(读:调度器)和在芯片上烤的TCP/IP栈，它在数据表上看起来很棒。这完全是一场灾难。慢,慢,慢!
I ended up with an FPGA-based soft processor and soft MAC. No OS... Worked great. Once a FIFO bug actually sent packets out so fast that every Windows PC on the network locked up solid handling interrupts (even the mouse locked) until I pulled the power on the dev board.
我最后得到了一个基于fpga的软处理器和软MAC。伟大的工作。一旦一个FIFO bug发送出去的速度如此之快，以至于网络上的每个Windows PC都锁上了固态处理中断(甚至是鼠标锁定)，直到我把电源拉到开发板上。
I've personally found it fairly difficult to write so much code for an 8 bit processor that you even NEED an OS. I'm sure some applications/situations may make it more desirable than I've seen. The only use for an OS that I've found is when you have some complex device with device drivers for a specific OS that you'd like to use, and then it's not a "general OS" question anymore.
我个人觉得为一个8位处理器写这么多代码是相当困难的，你甚至需要一个操作系统。我确信一些应用程序/情况会使它比我所看到的更令人满意。我所发现的操作系统的唯一用途是当你有一个复杂的设备，设备驱动程序是你想要使用的特定操作系统的时候，它就不再是一个“通用操作系统”的问题了。
Get familiar with the ever-so-common 1ms timer tick + "volatile char g_TASKS[]" global flag list + a simple main() loop that checks task flags and calls subroutines. State machines are your friend. You'll have a much better handle on how your system is going to run. These are the design patterns of 8 bit processors.
熟悉常见的1ms计时器tick +“volatile char g_TASKS[]”全局标记列表+一个简单的主()循环，检查任务标志和调用子例程。状态机是你的朋友。您将对系统的运行方式有更好的了解。这些是8位处理器的设计模式。
Any time you need task A to wait for task B to complete, then add a state machine state to task A, and have task B set that state... or something along those lines.
任何时候，您需要任务A等待任务B完成，然后将状态机状态添加到任务A，并让task B设置该状态…或者类似的东西。
A much more useful (IMHO) list would be of good 8 bit processors to use, not OSes. Here would be my criteria: low power, excellent debugging (OCD), excellent development environment (or just Eclipse integration), low cost, good C compiler support, and general stability of the debugging platform/debugger/etc.
一个更有用的(IMHO)列表应该是8位处理器，而不是OSes。以下是我的标准:低功耗、优秀的调试(OCD)、优秀的开发环境(或仅仅是Eclipse集成)、低成本、良好的C编译器支持，以及调试平台/调试器/等的总体稳定性。
#6
2
I have used uC/OS on an Z180 (8bit machine). I had to port to our custom banked memory model. But otherwise was great, especially having a detailed book describing all the functionality. And even though it was a RTOS, we still had to use threads etc. very sparingly.
我在Z180 (8bit机器)上使用了uC/OS。我不得不移植到我们的定制存储模型。但除此之外很好，尤其是有一本详细描述所有功能的书。虽然这是一个RTOS，但我们仍然需要非常少的使用线程。
#7
2
Back in the mid 70s I wrote, and in 1982 I stopped shipping an 8 bit OS (SDOS) for Motorola 6800/6801/6809. Those OSes came in several flavors:
回到70年代中期，我写了一篇文章，在1982年，我停止了给摩托罗拉6800/6801/6809的8位操作系统(SDOS)。这些OSes有几种口味:
- Real Time multithreaded (2Kb ROM + whatever RAM you wanted)
- 实时多线程(2Kb ROM +任意RAM)
- Single user Disk Operating System (64K memory max)
- 单用户磁盘操作系统(64K内存max)
- Multiuser Timesharing (15 users in 1Mb of RAM using 65Kb banks of memory, one per user)
- 多用户分时(1Mb内存中有15个用户使用65Kb内存，每个用户一个)
- Distributed OS (Single or Multiuser system with access to remote disks)
- 分布式操作系统(可访问远程磁盘的单个或多用户系统)
Where were you when I needed a customer :-? (I gave it up when it became clear that IBM chose Bill Gates by lightning bolt to be Microprocessor OS king).
当我需要顾客时，你在哪里?(很明显，IBM公司选择比尔•盖茨(Bill Gates)为“微处理器”(微处理器)王)的时候，我就放弃了。
#8
1
Softools also provides a OS (called TurboTask) for the Rabbit Processors.
Softools还为兔子处理器提供了一个操作系统(称为TurboTask)。
There is a library that provides basic task scheduling for the Rabbit. The library works with the Softools compiler, but not the rabbit compiler.
有一个库为兔子提供基本的任务调度。这个库使用的是Softools编译器，但不是编译器。
#9
1
There is also Uzix, for the MSX based (z80) computers, a Unix Like, Posix Compliant, multi-tasked, preemptive and with a TCP/IP stack implemented.
还有Uzix，基于MSX的(z80)计算机，一个Unix类的，Posix兼容的，多任务的，抢占式的，并且有一个TCP/IP协议栈实现。
#10
1
HI-TECH Salvo - HI-TECH Salvo features is a cooperative, event-driven, priority-based multitasking RTOS. It is for processors with severely limited RAM (< 256 bytes), works within a hardware call; return stack of 8 levels or less, supports 16 separate dynamic task priority levels, and provides inter-task communication and synchronization, ISR-to-task communication and resource sharing. It is extremely small RAM and ROM footprint, no PUSH/POP stack or stack pointer required, ROMable and extensible. Low interrupt latency, fast context switching, and portable - written in ANSI C, with minimal compiler.
高科技的Salvo -高科技Salvo特性是一个合作的、事件驱动的、基于优先级的多任务RTOS。它适用于具有严重限制RAM(< 256字节)的处理器，在硬件调用中工作;8级或更少的返回栈，支持16个独立的动态任务优先级，并提供任务间通信和同步，isrto -task通信和资源共享。它是非常小的RAM和ROM内存，不需要PUSH/POP栈或栈指针，可扩展和可扩展。低中断延迟，快速上下文切换，和可移植-用ANSI C编写，使用最小的编译器。
#11
1
Salvo - The RTOS that runs in tiny places(TM). - Salvo's modest ROM and miniscule RAM requirements mean that you can have event-driven, priority-based, multitasking applications in nearly any single-chip microcontroller, with plenty of room left for your application. With Salvo, you can: Implement new designs quickly * Enhance functionality using existing resources * Improve real-time performance * Multitask.
在小地方运行的RTOS (TM)。- Salvo有限的ROM和微型RAM需求意味着您可以在几乎任何单片机的单片机中都有事件驱动、基于优先级、多任务的应用程序，还有足够的空间留给您的应用程序。有了Salvo，您就可以:使用现有的资源来快速地实现新的设计*增强功能*提高实时性能*多任务。
#12
1
This is probably not what you want, but for MSX and Armstrad there is absolutely amazing GUI OS called SymbOS (http://www.symbos.de/). What's amazing about it, is that it was entirely made by one german guy called Prodatron (http://www.prodatron.net/). It has real multitasking and many applications what you would expect from modern OS:
这可能不是您想要的，但是对于MSX和Armstrad来说，有一个非常令人惊奇的GUI操作系统，叫做SymbOS (http://www.symbos.de/)。令人惊奇的是，它完全是由一个叫Prodatron的德国人制造的(http://www.prodatron.net/)。它有真正的多任务处理和许多应用程序你可以从现代操作系统中看到:
- SymCommander - Norton Commander clone.
- 诺顿指挥官克隆人。
- SymPlay - video player, videos have to be preprocessed, but after that they run very smooth and simultanously with other applications.
- SymPlay -视频播放器，视频必须经过预处理，但在此之后，它们运行非常流畅，并与其他应用程序进行了模拟。
- SymSee - picture viewer, again pictures must converted into CPC format first.
- 图片查看器，再次图片必须先转换成CPC格式。
- SymAmp - music player, supports tracker modules and even MP3-s with special hardware.
- SymAmp - music player，支持跟踪模块，甚至是带有特殊硬件的MP3-s。
- Calculator, Minesweeper, Control Panel etc.
- 计算器，扫雷器，控制面板等。
I've seen it demoed by it's author and the only comment from audience was "You must be grazy!". Nobody had ever seen such features on 8-bit MSX computer before.
我看到它被它的作者降职了，唯一的评论是“你一定很疯狂!”以前从来没有人在8位MSX电脑上看到过这样的功能。
#13
1
HACK-RTOS for Zilog eZ8, eZ80 and ZNEO microcontrollers
Zilog eZ8, eZ80和ZNEO微控制器的hackrtos。
#14
1
I cut my RTOS teeth on Microware's OS9 for the Motorola 6809. Brilliant for its day and made excellent use of the 6809's (then) advanced features.
我把我的RTOS牙齿放在微波炉的OS9上给摩托罗拉6809。出色的一天，并出色地使用了6809的(然后)高级功能。
#15
0
I wrote one a few years ago for the Z80 but the z80 doesn't support hardware multitasking or paging, multitasking is possible but your freedom is pretty limited you have to roll with stuff like like no absolute jumps or different start positions in different programs
我几年前写了一个Z80但Z80不支持硬件多任务处理或分页，多任务处理是可能的但你的*是非常有限的你必须在不同的程序中像没有绝对跳跃或不同的起始位置那样滚动。
#16
0
I have some difficulty in envisaging the type of 8-bit processor you're planning to use here - basically if it's anything powerful enough to run anything like an OS (an H8, for example), you'll almost certainly find that an ARM-cored micro is going to be just as cheap.
我很难想象你打算在这里使用的8位处理器的类型——基本上，如果它的功能强大到可以运行像OS(比如H8)这样的东西，你几乎肯定会发现ARM-cored微处理器将会变得同样便宜。
#17
0
I've written a round-robin scheduler for i8051 (which is much weaker than i8085/Z80) and a tiny kernel for a 16-bit TI DSP TMS320C54xx (scheduler with priorities, system calls, locks/mutexes). If you can program in assembly and can make your timer ISRs work, you can get similar basic functionality implemented and working in less than a week of work.
我已经为i8051编写了一个循环调度程序(它比i8085/Z80弱得多)和一个小内核，用于16位TI DSP TMS320C54xx(优先级，系统调用，锁/互连)。如果您可以在程序集中编程，并且可以使您的计时器ISRs工作，那么您可以在不到一周的工作时间内实现类似的基本功能。
#1
4
This might be an unusual point of view, but I would strongly recommend to think twice and even thrice before deciding to use an OS for a 8-bit computer. OSes are for complex application needs, and 8-bit CPUs are not the best choice for these tasks.
这可能是一个不同寻常的观点，但我强烈建议在决定使用一个操作系统来使用8位计算机之前，要三思而后行。OSes用于复杂的应用程序需求，而8位cpu并不是这些任务的最佳选择。
I'm not saying that an OS should never be used for a 8-bit, just that there's less chance that it is the best solution.
我并不是说一个操作系统不应该被使用8比特，只是它是最好的解决方案的可能性更小。
#2
4
To those suggesting state machines in place of an OS because they have little overhead, you might want to check out Contiki. It is very small and free. It doesn't have a traditional threading model, instead it uses ProtoThreads: http://www.sics.se/~adam/pt/.
对于那些建议状态机代替操作系统的人，因为它们的开销很小，所以您可能想要检查一下连续。它非常小而且是免费的。它没有传统的线程模型，而是使用原始线程:http://www.sics.se/~adam/pt/。
ProtoThreads give you something approximating threading semantics without the overhead of a real OS with multi stacks, etc... As a bonus, you don't need any sort of OS to use them Contiki or otherwise.
原始线程给您一些近似线程语义的东西，而不需要使用多个堆栈的真实操作系统的开销等等。作为奖励，您不需要任何类型的操作系统来使用它们。
We've used them on one project with great success. They really make writing complicated code much easier.
我们在一个项目上使用了它们，取得了巨大的成功。它们确实使编写复杂的代码变得更加容易。
#3
4
I believe Contiki will work. Adam Dunkels does some really cool stuff.
我相信“连续”会起作用。Adam Dunkels做了一些很酷的事情。
It runs on a lot of platforms, including the Commodore 64.
它在许多平台上运行，包括Commodore 64。
#4
3
Rabbit Semiconductor has a port of the MicroC/OS II for their processors.
兔半导体的处理器有一个微c /OS II的端口。
#5
2
What's the goal here? Embedded OSes tend to cost a lot. (MicroC/OS II, etc)
这里的目标是什么?嵌入式操作系统的成本往往很高。(MicroC/OS II，等等)
It sounds like you may be putting OS support ahead of what I consider more important things when it comes to device selection. You should know the general design patterns for the platform you are working on. Don't try to shove PC concepts into the tinyiest of embedded chips like this.
听起来你可能会把操作系统支持放在我认为更重要的设备选择上。您应该了解正在开发的平台的总体设计模式。不要把PC的概念推到像这样的嵌入式芯片中。
OMFG... Java does NOT belong on an 8 bit processor. I actually tried that Maxix/Dallas DS80C400 chip. It had a simplified OS (read: scheduler) and TCP/IP stack baked on chip, and it looked great on the datasheet. It was a complete disaster. Slow, slow, slow!
OMFG……Java不属于8位处理器。我真的试过了，Maxix/Dallas DS80C400芯片。它有一个简化的操作系统(读:调度器)和在芯片上烤的TCP/IP栈，它在数据表上看起来很棒。这完全是一场灾难。慢,慢,慢!
I ended up with an FPGA-based soft processor and soft MAC. No OS... Worked great. Once a FIFO bug actually sent packets out so fast that every Windows PC on the network locked up solid handling interrupts (even the mouse locked) until I pulled the power on the dev board.
我最后得到了一个基于fpga的软处理器和软MAC。伟大的工作。一旦一个FIFO bug发送出去的速度如此之快，以至于网络上的每个Windows PC都锁上了固态处理中断(甚至是鼠标锁定)，直到我把电源拉到开发板上。
I've personally found it fairly difficult to write so much code for an 8 bit processor that you even NEED an OS. I'm sure some applications/situations may make it more desirable than I've seen. The only use for an OS that I've found is when you have some complex device with device drivers for a specific OS that you'd like to use, and then it's not a "general OS" question anymore.
我个人觉得为一个8位处理器写这么多代码是相当困难的，你甚至需要一个操作系统。我确信一些应用程序/情况会使它比我所看到的更令人满意。我所发现的操作系统的唯一用途是当你有一个复杂的设备，设备驱动程序是你想要使用的特定操作系统的时候，它就不再是一个“通用操作系统”的问题了。
Get familiar with the ever-so-common 1ms timer tick + "volatile char g_TASKS[]" global flag list + a simple main() loop that checks task flags and calls subroutines. State machines are your friend. You'll have a much better handle on how your system is going to run. These are the design patterns of 8 bit processors.
熟悉常见的1ms计时器tick +“volatile char g_TASKS[]”全局标记列表+一个简单的主()循环，检查任务标志和调用子例程。状态机是你的朋友。您将对系统的运行方式有更好的了解。这些是8位处理器的设计模式。
Any time you need task A to wait for task B to complete, then add a state machine state to task A, and have task B set that state... or something along those lines.
任何时候，您需要任务A等待任务B完成，然后将状态机状态添加到任务A，并让task B设置该状态…或者类似的东西。
A much more useful (IMHO) list would be of good 8 bit processors to use, not OSes. Here would be my criteria: low power, excellent debugging (OCD), excellent development environment (or just Eclipse integration), low cost, good C compiler support, and general stability of the debugging platform/debugger/etc.
一个更有用的(IMHO)列表应该是8位处理器，而不是OSes。以下是我的标准:低功耗、优秀的调试(OCD)、优秀的开发环境(或仅仅是Eclipse集成)、低成本、良好的C编译器支持，以及调试平台/调试器/等的总体稳定性。
#6
2
I have used uC/OS on an Z180 (8bit machine). I had to port to our custom banked memory model. But otherwise was great, especially having a detailed book describing all the functionality. And even though it was a RTOS, we still had to use threads etc. very sparingly.
我在Z180 (8bit机器)上使用了uC/OS。我不得不移植到我们的定制存储模型。但除此之外很好，尤其是有一本详细描述所有功能的书。虽然这是一个RTOS，但我们仍然需要非常少的使用线程。
#7
2
Back in the mid 70s I wrote, and in 1982 I stopped shipping an 8 bit OS (SDOS) for Motorola 6800/6801/6809. Those OSes came in several flavors:
回到70年代中期，我写了一篇文章，在1982年，我停止了给摩托罗拉6800/6801/6809的8位操作系统(SDOS)。这些OSes有几种口味:
- Real Time multithreaded (2Kb ROM + whatever RAM you wanted)
- 实时多线程(2Kb ROM +任意RAM)
- Single user Disk Operating System (64K memory max)
- 单用户磁盘操作系统(64K内存max)
- Multiuser Timesharing (15 users in 1Mb of RAM using 65Kb banks of memory, one per user)
- 多用户分时(1Mb内存中有15个用户使用65Kb内存，每个用户一个)
- Distributed OS (Single or Multiuser system with access to remote disks)
- 分布式操作系统(可访问远程磁盘的单个或多用户系统)
Where were you when I needed a customer :-? (I gave it up when it became clear that IBM chose Bill Gates by lightning bolt to be Microprocessor OS king).
当我需要顾客时，你在哪里?(很明显，IBM公司选择比尔•盖茨(Bill Gates)为“微处理器”(微处理器)王)的时候，我就放弃了。
#8
1
Softools also provides a OS (called TurboTask) for the Rabbit Processors.
Softools还为兔子处理器提供了一个操作系统(称为TurboTask)。
There is a library that provides basic task scheduling for the Rabbit. The library works with the Softools compiler, but not the rabbit compiler.
有一个库为兔子提供基本的任务调度。这个库使用的是Softools编译器，但不是编译器。
#9
1
There is also Uzix, for the MSX based (z80) computers, a Unix Like, Posix Compliant, multi-tasked, preemptive and with a TCP/IP stack implemented.
还有Uzix，基于MSX的(z80)计算机，一个Unix类的，Posix兼容的，多任务的，抢占式的，并且有一个TCP/IP协议栈实现。
#10
1
HI-TECH Salvo - HI-TECH Salvo features is a cooperative, event-driven, priority-based multitasking RTOS. It is for processors with severely limited RAM (< 256 bytes), works within a hardware call; return stack of 8 levels or less, supports 16 separate dynamic task priority levels, and provides inter-task communication and synchronization, ISR-to-task communication and resource sharing. It is extremely small RAM and ROM footprint, no PUSH/POP stack or stack pointer required, ROMable and extensible. Low interrupt latency, fast context switching, and portable - written in ANSI C, with minimal compiler.
高科技的Salvo -高科技Salvo特性是一个合作的、事件驱动的、基于优先级的多任务RTOS。它适用于具有严重限制RAM(< 256字节)的处理器，在硬件调用中工作;8级或更少的返回栈，支持16个独立的动态任务优先级，并提供任务间通信和同步，isrto -task通信和资源共享。它是非常小的RAM和ROM内存，不需要PUSH/POP栈或栈指针，可扩展和可扩展。低中断延迟，快速上下文切换，和可移植-用ANSI C编写，使用最小的编译器。
#11
1
Salvo - The RTOS that runs in tiny places(TM). - Salvo's modest ROM and miniscule RAM requirements mean that you can have event-driven, priority-based, multitasking applications in nearly any single-chip microcontroller, with plenty of room left for your application. With Salvo, you can: Implement new designs quickly * Enhance functionality using existing resources * Improve real-time performance * Multitask.
在小地方运行的RTOS (TM)。- Salvo有限的ROM和微型RAM需求意味着您可以在几乎任何单片机的单片机中都有事件驱动、基于优先级、多任务的应用程序，还有足够的空间留给您的应用程序。有了Salvo，您就可以:使用现有的资源来快速地实现新的设计*增强功能*提高实时性能*多任务。
#12
1
This is probably not what you want, but for MSX and Armstrad there is absolutely amazing GUI OS called SymbOS (http://www.symbos.de/). What's amazing about it, is that it was entirely made by one german guy called Prodatron (http://www.prodatron.net/). It has real multitasking and many applications what you would expect from modern OS:
这可能不是您想要的，但是对于MSX和Armstrad来说，有一个非常令人惊奇的GUI操作系统，叫做SymbOS (http://www.symbos.de/)。令人惊奇的是，它完全是由一个叫Prodatron的德国人制造的(http://www.prodatron.net/)。它有真正的多任务处理和许多应用程序你可以从现代操作系统中看到:
- SymCommander - Norton Commander clone.
- 诺顿指挥官克隆人。
- SymPlay - video player, videos have to be preprocessed, but after that they run very smooth and simultanously with other applications.
- SymPlay -视频播放器，视频必须经过预处理，但在此之后，它们运行非常流畅，并与其他应用程序进行了模拟。
- SymSee - picture viewer, again pictures must converted into CPC format first.
- 图片查看器，再次图片必须先转换成CPC格式。
- SymAmp - music player, supports tracker modules and even MP3-s with special hardware.
- SymAmp - music player，支持跟踪模块，甚至是带有特殊硬件的MP3-s。
- Calculator, Minesweeper, Control Panel etc.
- 计算器，扫雷器，控制面板等。
I've seen it demoed by it's author and the only comment from audience was "You must be grazy!". Nobody had ever seen such features on 8-bit MSX computer before.
我看到它被它的作者降职了，唯一的评论是“你一定很疯狂!”以前从来没有人在8位MSX电脑上看到过这样的功能。
#13
1
HACK-RTOS for Zilog eZ8, eZ80 and ZNEO microcontrollers
Zilog eZ8, eZ80和ZNEO微控制器的hackrtos。
#14
1
I cut my RTOS teeth on Microware's OS9 for the Motorola 6809. Brilliant for its day and made excellent use of the 6809's (then) advanced features.
我把我的RTOS牙齿放在微波炉的OS9上给摩托罗拉6809。出色的一天，并出色地使用了6809的(然后)高级功能。
#15
0
I wrote one a few years ago for the Z80 but the z80 doesn't support hardware multitasking or paging, multitasking is possible but your freedom is pretty limited you have to roll with stuff like like no absolute jumps or different start positions in different programs
我几年前写了一个Z80但Z80不支持硬件多任务处理或分页，多任务处理是可能的但你的*是非常有限的你必须在不同的程序中像没有绝对跳跃或不同的起始位置那样滚动。
#16
0
I have some difficulty in envisaging the type of 8-bit processor you're planning to use here - basically if it's anything powerful enough to run anything like an OS (an H8, for example), you'll almost certainly find that an ARM-cored micro is going to be just as cheap.
我很难想象你打算在这里使用的8位处理器的类型——基本上，如果它的功能强大到可以运行像OS(比如H8)这样的东西，你几乎肯定会发现ARM-cored微处理器将会变得同样便宜。
#17
0
I've written a round-robin scheduler for i8051 (which is much weaker than i8085/Z80) and a tiny kernel for a 16-bit TI DSP TMS320C54xx (scheduler with priorities, system calls, locks/mutexes). If you can program in assembly and can make your timer ISRs work, you can get similar basic functionality implemented and working in less than a week of work.
我已经为i8051编写了一个循环调度程序(它比i8085/Z80弱得多)和一个小内核，用于16位TI DSP TMS320C54xx(优先级，系统调用，锁/互连)。如果您可以在程序集中编程，并且可以使您的计时器ISRs工作，那么您可以在不到一周的工作时间内实现类似的基本功能。