Astrobe Forum

The prototype of S2650 IcePi, my Signetics S2650 / Raspberry Pi RP2350 ICE combo retrocomputing project, worked for the first time today. The RP2350 generates the 1 MHz clock and the S2650 (an 8-bit MCU from the 1970's) executes the code. The Signetics Monitor ROM, Pipbug (or other ROM code) and the...

The latest v10.0 releases of Astrobe for RP2040 and RP2350 are now available. For more details see: What's New in Astrobe If your license support period has not yet expired you are eligible for a free upgrade. You should have already received an email with instructions on how to download the v10.0 u...

All reported problems in Astrobe for Cortex-M0, m3, m4, m7 and RP2040, RP2350 have been fixed in v10.0. The first of these have already been released and the rest should follow by the end of the month. For a summary see What's New in Astrobe

The latest v10.0 releases of Astrobe for Cortex-M0, M3, M4 and M7 are now available. What's New in Astrobe If your license support period has not yet expired you are eligible for a free upgrade. You should have already received an email with instructions on how to download the v10.0 upgrade. Email s...

Is the original source code NW's ARM compiler available, as it is for Project Oberon? Not that I'm aware of. It was rendered obsolete many years ago by the version that is included in Project Oberon. The major difference is the code generator. The RISC5 version is only just over 1000 lines of code ...

If you are configuring the pin for I2C the Astrobe GPIO module automatically enables the pull-up resistor for the pin. If you have the source code for the Astrobe GPIO module you can see how it is done there. Otherwise, for other GPIO pins, the relevant bit, PUE ( P ull- U p E nable), is identified ...

Thank you for pointing that out. I'll update the docs accordingly. At the risk of being picky, the writer of the Oberon Compiler for the ARM Processor was Niklaus Wirth. I'm merely modifying the code generator to target other Arm processors. There is no way in the world I could have done that withou...

And this strictly works with BOOLEAN CONSTs only, correct? Correct. It has always been possible to parameterise code in the way you describe - the Conditional Compilation feature just makes it less inefficient than it otherwise would be. However that was not the intended use of the feature and I wo...

Does the quoted statement mean that the nested 'IF F1 ...' gets included? Yes. If you compiled your code with v10 you would get the same code generated as if you compiled the following with v9.3: CONST T0 = TRUE; F1 = FALSE; PROCEDURE P4(); BEGIN IF F1 THEN Included() (* ?? *) END END P4;

There are four possible combinations for the values of Trace.enabled (TRUE / FALSE) and OtherTrace.enabled (TRUE / FALSE). This is shown by the following hypothetical example. None of the calls to the procedure Eliminated are generated. MODULE Elsif; CONST F1 = FALSE; F2 = FALSE; T1 = TRUE; T2 = TRU...