[Oberon] Hardware versus software development.

skulski at pas.rochester.edu skulski at pas.rochester.edu
Fri Oct 31 15:40:57 CET 2014


> With RISC5 you don’t touch the Oberon
> code anymore with new HW.

This is not true. The new Oberon System must be partitioned into its core
and the device drivers. The core (or kernel, if you wish) can stay intact.
But the device drivers must be adopted to the HW. The video is a good
example. In the published version it is a single bit plane. The RGB
signals are wired together. The video part is not really supporting color
because color is not present in the HW design. It is clearly not a nice
solution and the video HW needs to get modified. In fact, Nexys-4 provides
color out the box. So the Nexys version of The System needs to get
modified to use the provided video HW.

Are the driver modules part of The System? I would not argue this. The
point is that the drivers need be adjusted to the HW. In this sense one
has to touch the system. Being able to modify both the HW and the SW is
the whole point of this project in my opinion. A good introduction can be
found in the books by Pong P. Chu.

The really exciting prospect is that once you adopt the FPGA Oberon
System, you will soon be buying these books and you will very quickly
become a proficient FPGA developer, before you even notice it happenning.


More information about the Oberon mailing list