Astrobe Forum

Embedded Project Oberon was designed to be remotely controlled with all of the user interface on the PC. I can't envisage how it might work with the keyboard being isolated from the mouse and display. The question is more appropriate to Project Oberon Workstation. This handles all of the keyboard, m...

Constant expressions are evaluated at compile time. Decimal and hexadecimal INTEGER constants are signed integers and an integer overflow in a constant expression is trapped at compile time. For example: CONST MaxInt = 07FFFFFFFH; (* PosOverflow = MaxInt + 1; Error: integer overflow *) MinInt = 0800...

I can't think of a general way to copy the executable code of a procedure to RAM that would be both useful and reliable in the current implementation of Astrobe for Cortex-M. Note that Astrobe for RISC5 supports the dynamic loading of modules (but not isolated procedures) into RAM. What is the actua...

Thank you for your report. The problem will be addressed in the next maintenance release. In the meantime a workaround is to assign the set to a local variable before passing it as a parameter. See the attached test program which should display the string "OK". Replacing the local variable assignmen...

The free v9.1 Astrobe for Cortex-M0 Personal Edition has now been released. You can request the download here:

https://www.astrobe.com/personal.htm

v9.1 Astrobe for ARM Cortex-M0 has now been released. See What's New in Astrobe for ARM Cortex-M0 for a summary of the changes. If you are a registered user of the Professional Edition and your support period has not yet expired you are eligible for a free upgrade. Email support 'at' astrobe.com if ...

Thank you for your report. I can confirm that it is a problem and it will be fixed in the next Cortex-M0 maintenance release.

Thank you for your report. The error occurs because the SEV instruction happens to be a "related encoding" variant of the ARMv7-M IT instruction which is not yet recognised by the Astrobe disassemblers. The WFE, WFI, and YIELD instructions behave similarly. This problem will be fixed in the next rel...

Thank you for your report. The RP2040 clock initialisation statement: CONST (* XOSC_STATUS *) STABLE = 31; ... REPEAT UNTIL SYSTEM.BIT(MCU.XOSC_STATUS, STABLE); Should generate code that looks something like this: . 30 01EH 04803H ldr r0,[pc,#12] -> 44 . 32 020H 06801H ldr r1,[r0] . 34 022H 00009H m...