[Oberon] Oberon board availability

[Skulski, Wojciech]

Joerg:

>Perhaps not widely known, but in Oberon you can ask the RISC5 processor to
>reveal its version. But not even this internal versioning was incremented in
>the Verilog code.

this brings up the issue of code maintenance, archiving, and version control. One good official repository may help solve such problems. Otherwise we are relying on e-mails and the word of mouth. I just asked whether Chris used the most recent official compiler which is now the same between Experimental Oberon and the NW version. I hope he did, but I would not be surprised if the version slipped back to before the EO/NW merger. 

I do not want to pick on anyone. It is just the reason why the bad people invented version control. Maybe the good people can adopt bad people's solutions? What do you think?
W.

PS: in my own HDL production use a date register which can be read by the CPU. I encode it by hand, which is not a big burden compared with all the other FW headaches.

-- rev  yyyyy  mmmm   ddddd  Bit fields 2 + 5 + 4 + 5 = 16 bits
-- rev  year   month  day    in binary
--  00  Year 15 = 01111  Dec (12) = 1100  Day (20) = 10100
--                                                      rrYYYYYmmmmDDDDD
CONSTANT FW_REVISION: STD_LOGIC_VECTOR(15 downto 0) := "0001111110010100";

________________________________________