Astrobe Forum

Latest changes and updates: https://oberon-rtk.org/updates/2025/cn-2025-06-16

Nascent support for a new board: TinyVision Pico2-Ice, which combines an RP2350B with a Lattice Semi iCE40UP5K FPGA.

Website: https://oberon-rtk.org/
GitHub repository: https://github.com/ygrayne/oberon-rtk

Latest changes and updates: https://oberon-rtk.org/updates/2025/cn-2025-06-03

Some long overdue config file housekeeping and validation: https://oberon-rtk.org/docs/tools/config-files/

Website: https://oberon-rtk.org/
GitHub repository: https://github.com/ygrayne/oberon-rtk

It appears that Astrobe for RP2350 as well as RP2040 have a limit regarding the number of configuration files in the same directory (nine?). I couldn't find any documentation about this, but I may have missed it. All files are recognised and correctly listed in the menu. When attempting to select a ...

Another attempt:
Shouldn't this be something like this (using the same pc-offset for x):

Astrobe for RP2350 uses 'SYSTEM.VMSR(0)' in the initialisation of the FPU (module Main). This SYSTEM procedure is not documented in SYSTEM.def, but the disassembly makes its function clear: SYSTEM.VMSR(0); 02000H movs r0,#0 0EEE10A10H vmsr fpscr,r0 If there's 'SYSTEM.VMSR' there is probably 'SYSTEM....

During the compilation phase, relative paths are relative to the folder which contains the module being compiled . During the linking phase, relative paths are relative to the folder which contains the module (which imports Main) being linked . Thinking this through, it follows that we can have a s...

Latest changes and updates: https://oberon-rtk.org/updates/2025/cn-2025-06-01

Focus: library customisation, with tool support: https://oberon-rtk.org/concepts/archite ... omisation/

Website: https://oberon-rtk.org/
GitHub repository: https://github.com/ygrayne/oberon-rtk

Allow me summarise. 1) The following is the test code you have provided. I have only changed VARs to CONST in both M1.mod to easier check in the assembly file which module is actually imported. But importantly, both M1.mod have a different public interface. Structure: + Test2 + P1.mod + prog + M1.mo...

As said, I am building your test code, ie. with two modules M1 with different public interfaces. As long as I don't compile M0 directly, I can build P successfully, with M1 in 'lib' never being compiled. I attach the test code (Test2.zip). To take the test one step further, if I change M0 to MODULE ...

Mulling over this some more, in the light of the documentation, and all you said in this thread and in Relative Search Path makes me think that I should not be able to sucessfully build the test program as described in my post above. That is, with M0 compiled with reference to M1 in 'prog' (verified...