Astrobe Forum

Thank you for your report - the whole issue of import ordering, re-importing and aliasing is very complex. e.g. another workaround for this example is to change the order of imports in SysCall to: IMPORT ReadyQueue, Types; The IMPORT system was extensively refactored a year or so ago in an attempt t...

I've created an index using Adobe Acrobat in the Signetics 2650 Microprocessor user manual PDF file. You can download a copy from the S2650 section of my Astrobe website:
https://www.astrobe.com/S2650/

OK - now read the Nexys-A7 Reference Manual. If you still do not understand why the .xcd file is not involved you should be able to get help on the Digilent Forum.

Internally the menu items are ordered with the single digit 0..9. Hence only the first ten items in a folder should be displayed. If the folder contains more than ten valid items selecting item 1 0, 1 1, 1 2 etc. will result in the config file numbered 1 being loaded. This problem will be fixed in t...

The RISC5 RAM interface is described in Chapter 17 The processor's environment in the book Project Oberon - The Design of an Operating System, a Compiler, and a Computer . Although the details are different, the basic principles of the design for the Artix 7 FPGA on the Digilent Nexys board are the ...

Sorry - support is not provided for "undocumented features".

OK - thanks. A couple of points: 2) You said that "the following code results in the error: 'Module M1 - wrong version". Correction - I should have said: "the following code can result in the error: 'Module M1 - wrong version" 4) As I understand, the build system a) performs separate compilations fo...

I'm sorry - you've lost me. Are you now saying it is all working as it should?

If not and problems only arise if there are two or more modules with the same name in the current list of search paths I can try and modify the system to report that as an error.

In your original example M1 in lib is identical to M1 in prog which is not a realistic scenario. It wouldn't matter which one is picked up by the linker. In a valid example of what I believe you are trying to test / demonstrate, the public interface of the modules (i.e. the exported items) would nee...

A build results in zero or more separate compilations, each with their own, possibly different, set of relative search paths. If all of the compilations succeed, it is followed followed by a link with its own set of relative search paths. During the compilation phase, relative paths are relative to ...